[Solved, kinda]Nvidia driver problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Having already removed akmod-nvidia, I booted with kernel
2.6.29.6-217.2.3.fc11.x86_64, which was the only one still working and
just did:

yum remove kmod-nvidia*

yum install kmod-nvidia

which took care of dependencies. So, not only was:

kmod-nvidia-2.6.29.6-217.2.3.fc11.x86_64.x86_64
                           185.18.31-1.fc11

removed, but also:

xorg-x11-drv-nvidia.x86_64        185.18.31-1.fc11
xorg-x11-drv-nvidia-libs.x86_64   185.18.31-1.fc11

How those packages ever got to my system, I have no idea. I never enabled
rpmfusion-nonfree-updates-testing. (Maybe somebody at rpmfusion is keeping
a low profile for supplying these as dependencies with akmod?)

Now, kernel 2.6.29.6-217.2.8 works, kernel 2.6.29.6-217.2.7 which never
worked and I considered destroyed by my experiments with akmod, still
doesn't work, and kernel 2.6.29.6-217.2.3, which always worked flawlessly,
now doesn't work. Maybe, I should have booted to kernel 2.6.29.6-217.2.8
and worked from a terminal for the remove/install operations, but I still
find it strange that the .3 kernel, which always worked fine with the
185.18.14-3.fc11 Nvidia modules, doesn't work anymore with the same
modules.

Though the Nvidia drivers now seem to work very well with the .8 kernel, I
have those error messages:

boot message:

Enabling the nvidia driver: /etc/rc.d/init.d/functions: line 513 :1298
Segmentation fault "$@"


dmesg | grep nvidia

nvidia: module license 'NVIDIA' taints kernel.
nvidia 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
nvidia 0000:01:00.0: setting latency timer to 64
nvidia-config-d[1300]: segfault at 7f5ac4000000 ip 0000003e7dc799a4 sp
00007ffffb6f0448 error 4 in libc-2.10.1.so[3e7dc00000+164000]

Note that I got the boot message, that otherwise only flashes by, with the
icon at the bottom of the login screen. It would have been impossible to
read this message if the boot process had not terminated at the login
screen. The "I" for interactive set-up has absolutely no effect and Shift
pg-up doesn't get you to the previous boot messages screen. Those are not
always present in dmesg or /var/log/messages and might prove helpful for
troubleshooting.

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux