PDA

View Full Version : Updating Kernel causes crash....



Karunes
9th October 2007, 10:09 PM
Hi!

I'd like to preface my request for help by stating that I usually do my best to solve my problems by myself before going to the community.

First, the system.

3800+ Athlon X2 <Am2>
Nforce 4 Chipset on Gigabyte mainboard
Nvidia 8800GTS
kernel 2.6.21-1.3194 (x64)

Every time I try to upgrade to this Kernel (a requirement for the livna nvidia driver) I get a black screen shortly after Udev completes.

kernel-2.6.22.9-91.fc7

What log files do I need to post? I'd like to see where it is crashing, exactly. Though it seems like it crashed it two different locations, as once it almost made it to the login screen.

Is there an Nvidia driver that works for the kernel that I am currently using?

Thank you for taking the time to read this, I really appreciate it.

bseltzer
9th October 2007, 10:46 PM
Hi!

I'd like to preface my request for help by stating that I usually do my best to solve my problems by myself before going to the community.

First, the system.

3800+ Athlon X2 <Am2>
Nforce 4 Chipset on Gigabyte mainboard
Nvidia 8800GTS
kernel 2.6.21-1.3194 (x64)

Every time I try to upgrade to this Kernel (a requirement for the livna nvidia driver) I get a black screen shortly after Udev completes.

kernel-2.6.22.9-91.fc7

What log files do I need to post? I'd like to see where it is crashing, exactly. Though it seems like it crashed it two different locations, as once it almost made it to the login screen.

Is there an Nvidia driver that works for the kernel that I am currently using?

Thank you for taking the time to read this, I really appreciate it.

I know there are folks who prefer the livna NVIDIA drivers, but I've always had good luck with the vendor's downloadable installer/drivers. The latest version is 100.14.19 and should work for any 2.6.20 or better kernel.

[ EDIT ]

My bad... Be sure you get the 100.14.19 specifically for Linux AMD64/EM64T

[ EDIT/]

Regards,
Bert

Karunes
9th October 2007, 10:53 PM
Thanks for the response.

I've been really skiddish to try those drivers. Mainly because of this article. https://www.redhat.com/archives/fedora-devel-list/2006-February/msg01178.html

Maybe I'll give it a shot.

bseltzer
9th October 2007, 11:10 PM
Thanks for the response.

I've been really skiddish to try those drivers. Mainly because of this article. https://www.redhat.com/archives/fedora-devel-list/2006-February/msg01178.html

Maybe I'll give it a shot.

FWIW.....

Well, the DRI thing is a non-issue, at least with the current NVIDIA supplied drivers. BTW, the article you reference is a bit too old, in my opinion, to be taken too seriously. I've heard all the arguments back and forth about the repository supplied drivers vs the vendor supplied drivers, and frankly my experience indicates it's really a matter of preference. I've use the NVIDIA drivers since RH 8, and never had a lick of trouble with them, even with all the demands of our new composite desktops. I have also tried the livna drivers and gotten equal performance and reliability out of them. But there is the occasional lag between the drivers at the livna repo and kernels at the fedora repos, and I confess to being too impatient not to be annoyed by that.

Now, the ATI stuff, well... we don't want to go there :rolleyes:

Regards,
Bert

Karunes
10th October 2007, 12:42 AM
I keep getting this after installing the Nvidia drivers.



X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Fedora Core 7 Red Hat, Inc.
Current Operating System: Linux karunes.linus 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
Build Date: 11 June 2007
Build ID: xorg-x11-server 1.3.0.0-9.fc7
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/dev/null", Time: Tue Oct 9 16:11:11 2007
(++) Using config file: "/tmp/tmpsrDvz-xorg.config"

Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x6d) [0x48b99d]
1: /lib64/libc.so.6 [0x3b57230630]
2: /lib64/ld-linux-x86-64.so.2 [0x3b5620a2f2]
3: /lib64/ld-linux-x86-64.so.2 [0x3b56210d66]
4: /lib64/ld-linux-x86-64.so.2 [0x3b5620cda6]
5: /lib64/ld-linux-x86-64.so.2 [0x3b5621061c]
6: /lib64/libdl.so.2 [0x3b57a00f9a]
7: /lib64/ld-linux-x86-64.so.2 [0x3b5620cda6]
8: /lib64/libdl.so.2 [0x3b57a0150d]
9: /lib64/libdl.so.2(dlopen+0x31) [0x3b57a00f11]
10: /usr/bin/Xorg(DLLoadModule+0x56) [0x467b76]
11: /usr/bin/Xorg(LoaderOpen+0x17d) [0x4656dd]
12: /usr/bin/Xorg [0x466b5b]
13: /usr/bin/Xorg(LoadModule+0x24) [0x4673b4]
14: /usr/bin/Xorg(xf86LoadModules+0x8b) [0x46253b]
15: /usr/bin/Xorg(InitOutput+0x514) [0x463534]
16: /usr/bin/Xorg(main+0x275) [0x434625]
17: /lib64/libc.so.6(__libc_start_main+0xf4) [0x3b5721dab4]
18: /usr/bin/Xorg(FontFileCompleteXLFD+0x229) [0x433ad9]

Fatal server error:
Caught signal 11. Server aborting

I'll keep tinkering. Any ideas on why the newer kernel is crashing?