RE: [suse-amd64] suse 9 amd 64, gftp+kdvi problems
However, some odd things began to pop up: gftp (which I love) crashes. I tried to reinslall from the rpms on the CDs of the non-64 bit version of suse 9.0, which I also have. (I thought maybe the dvd disc was corrupted.) It failed too. xftp crashes. (The text-based ftp however works.) Another program I use a lot, kdvi (kde's dvi previewer for latex documents), also crashes:-(. I've recently been having problems wth kmail, and had to switch over to mozilla. I'm not sure if that's related though.
I've had similar problems, though I do not use these programs -- the only one I remember offhand was xscreensaver crashing [and taking X with it]. I know SUSE does not recommend this, but I fixed the problem in every case by downloading the source and recompiling. Also, switching to a 2.6.x kernel fixed a lot of strange crashes and kernel panics. If you're going to compile source yourself, you'll need to be aware of the following changes to the `./configure && make && make install` process: * run `./configure --prefix=/usr/local --libdir=/usr/local/lib64 --x-libraries=/usr/X11R6/lib64` * after this, edit ./libtook and add "/lib64 /usr/lib64 /usr/local/lib64" to sys_lib_search_path_spec and to sys_lib_dlsearch_path_spec There is probably a way to do that last one automatically, but I've been too lazy to look for it ;) _m _________________________________________________________________ Check out the coupons and bargains on MSN Offers! http://shopping.msn.com/softcontent/softcontent.aspx?scmId=1418
"Michael Mondragon" <mammon_@hotmail.com> writes:
I know SUSE does not recommend this, but I fixed the problem in every case by downloading the source and recompiling. Also, switching to a
That would mean that either: - one of our local patches is broken - your binary on the disk is broken (check with rpm -Va the md5sums) - you used a different compiler than we did - but we ship the same that we use... I'm really surprised that recompilation helped... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Sat, 24 Jan 2004 19:06:35 +0100 Andreas Jaeger <aj@suse.de> wrote:
"Michael Mondragon" <mammon_@hotmail.com> writes:
I know SUSE does not recommend this, but I fixed the problem in every case by downloading the source and recompiling. Also, switching to a
That would mean that either: - one of our local patches is broken - your binary on the disk is broken (check with rpm -Va the md5sums) - you used a different compiler than we did - but we ship the same that we use...
I'm really surprised that recompilation helped...
... - or it was a placebo effect. Not uncommon in software testing. -Andi
Thanks to everyone for all the suggestions. I did try downloading gftp and recompiling. The configure file complained that it couldn't find some things. The last few lines were checking for pkg-config... no *** The pkg-config script could not be found. Make sure it is *** in your path, or set the PKG_CONFIG environment variable *** to the full path to pkg-config. *** Or see http://www.freedesktop.org/software/pkgconfig to get pkg-config. checking for glib-config... no checking for GLIB - version >= 1.2.3... no *** The glib-config script installed by GLIB could not be found *** If GLIB was installed in PREFIX, make sure PREFIX/bin is in *** your path, or set the GLIB_CONFIG environment variable to the *** full path to glib-config. configure: error: gFTP needs GLIB 1.2.3 or higher I installed pkg-config and set the PKG_CONFIG variable. This time configure+make worked. But gftp still failed: tinah:/home/wdj/downloads/gftp-2.0.16 # /opt/gnome/bin/gftp gFTP Warning: Skipping line 221 in config file: entropy_source gFTP Warning: Skipping line 224 in config file: entropy_len (gftp-gtk:28835): Gtk-CRITICAL **: file gtkwidget.c: line 4101 (gtk_widget_get_style): assertion `GTK_IS_WIDGET (widget)' failed (gftp-gtk:28835): Gtk-CRITICAL **: file gtkwidget.c: line 4101 (gtk_widget_get_style): assertion `GTK_IS_WIDGET (widget)' failed Segmentation fault Is this related to a nvidia driver problem? If not, does anyone know what the problem is? If it is a problem with the nvidia gforce3 chipset , can't I install the patch at http://www.ussg.iu.edu/hypermail/linux/kernel/0309.2/0447.html instead of recompiling the kernel? If so, how? (It doesn't look like a bash script to me, so I'm clueless, but it seems easier than recompiling the kernel.) - David Michael Mondragon wrote:
However, some odd things began to pop up: gftp (which I love) crashes. I tried to reinslall from the rpms on the CDs of the non-64 bit version of suse 9.0, which I also have. (I thought maybe the dvd disc was corrupted.) It failed too. xftp crashes. (The text-based ftp however works.) Another program I use a lot, kdvi (kde's dvi previewer for latex documents), also crashes:-(. I've recently been having problems wth kmail, and had to switch over to mozilla. I'm not sure if that's related though.
I've had similar problems, though I do not use these programs -- the only one I remember offhand was xscreensaver crashing [and taking X with it].
I know SUSE does not recommend this, but I fixed the problem in every case by downloading the source and recompiling. Also, switching to a 2.6.x kernel fixed a lot of strange crashes and kernel panics. If you're going to compile source yourself, you'll need to be aware of the following changes to the `./configure && make && make install` process:
* run `./configure --prefix=/usr/local --libdir=/usr/local/lib64 --x-libraries=/usr/X11R6/lib64`
* after this, edit ./libtook and add "/lib64 /usr/lib64 /usr/local/lib64" to sys_lib_search_path_spec and to sys_lib_dlsearch_path_spec
There is probably a way to do that last one automatically, but I've been too lazy to look for it ;)
_m
_________________________________________________________________ Check out the coupons and bargains on MSN Offers! http://shopping.msn.com/softcontent/softcontent.aspx?scmId=1418
Is this related to a nvidia driver problem?
Almost certainly not
If it is a problem with the nvidia gforce3 chipset , can't I install the patch at http://www.ussg.iu.edu/hypermail/linux/kernel/0309.2/0447.html instead of recompiling the kernel? If so, how? (It doesn't look like a bash script to me, so I'm clueless, but it seems easier than recompiling the kernel.)
You could certainly try that. There have been many changes from the 2.4 kernel to the 2.6; this patch is just one of them. If you try the patch and it doesn't work, then we'll know that it's some OTHER change in 2.6 that made the (positive) difference. Actually, installing the 2.4 patch is harder than just moving to the 2.6.1 kernel. But here's how you would do it: 1. Download the exact version of the 2.4 kernel as described in the patch e-mail. It may not exist anymore because it was apparently a pre-release version. But you could try the 2.4.23 sources from kernel.org 2. Apply the patch to that kernel source code using the patch program. 3. Re-compile the kernel as you would have before. This time, copy the configuration file from your current 2.4 kernel. 4. Install. You'll have to either compile in the right drivers (i.e. change the default SuSE configuration), or figure out how to make an initrd RAMDisk. The end result would not necessarily solve your problems (although it probably would). But it really is harder, since it contains extra steps over just compiling the 2.6.1 kernel. Maybe you would like to try my pre-compiled 2.6.1 kernel. It's worth a shot. As long as you don't remove your old kernel or your old GRUB configuration (/boot/grub/menu.lst), you can always just use the old one again by rebooting. -- Bob
In response to problems with the nFORCE3 Chipset on the K8 Triton Motherboards, I'm making available 64-bit binaries for the Linux 2.6.1 kernel that I compiled for my own machine. It's available at: http://home.earthlink.net/~bob.fischer17/ The README file is below. Best of luck, -- Bob ============================================================= This is a Linux-2.6.1 kernel, compiled for use with SuSE 9.0. It should work if you're booting off of ext3 or ReiserFS IDE filesystems. It is provided as a convenience for those who do not wish to compile the kernel. All software included herein is subject to the terms of the GNU General Public License, and is available in source code form at www.kernel.org --------------------------- This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. ----------------------- Installation Instructions ========================= 1. Untar the file: su cd / tar xvfz /<your-pathname-here>/linux-2.6.1.tar.gz WARNING: THIS COULD OVERWRITE IMPORTANT FILES, DEPENDING ON YOUR CURRENT SYSTEM CONFIGURATION. BEFORE YOU UNTAR, MAKE SURE IT WILL NOT OVERWRITE ANY FILES. YOU CAN DO THIS BY EXAMINING THE CONTENTS OF THE TAR FILE: tar tvfz /<your-pathname-here>/linux-2.6.1.tar.gz 2. Configure the GRUB Bootloader. If you're using LILO, configuration works some other way... a) Run YaST->System->Boot Loader Configuration b) Click on "Available Sections", then "Edit" c) Click on "Linux", then "Add". When asked if you wish to clone the selected selection 'Linux', say "Yes". d) On the "Section Name" line, set a name of "SuSE64-2.6.1" (or any name you like) e) On the "kernel" line, change "boot/vmlinuz" to "boot/vmlinuz-2.6.1". Leave everything else unchanged. f) Remove the "initrd" line. g) Click "OK", "Finish", etc. to save your bootloader configuration. The file /boot/grub/menu.list.new shows the kind of entry that SHOULD result in the /boot/grub/menu.list file by the above-mentioned actions with YaST. 3. Reboot!
Hello all: I configured my amd64 linux machine with gigabyte motherboard as a dual boot - it boots both suse 9.0, 32 bit version, and suse 9.0, 64 bit version. So far as I can see, the 32 bit version works perfectly. kdvi functions, gftp does. The 64 bit version does not work perfectly. kdvi crashes after loading the dvi file and gftp won't even start. There were *lots* of other problems with the 64 bit version, too many to list. I conclude that the 2.4.21 kernel is not the problem. Am I wrong? If I'm right, anyone have an idea on what *is* the problem? - David Joyner
participants (5)
-
Andi Kleen -
Andreas Jaeger -
Bob Fischer -
David Joyner -
Michael Mondragon