Is there some way to make dkms NOT try to install/load a driver?
mark, with an old NVidia card that is *NOT* supported by anything newer than 174, and *certainly* not by the "generic" xorg x11 nvidia driver
m.roth@5-cent.us wrote:
Is there some way to make dkms NOT try to install/load a driver?
mark, with an old NVidia card that is *NOT* supported by anything newer than 174, and *certainly* not by the "generic" xorg x11 nvidia driver
why dkms? use nvidia-x11-drv-173xx and kmod-nvidia-173xx from elrepo, the kmod is kabi-tracking.
m.roth@5-cent.us wrote:
Is there some way to make dkms NOT try to install/load a driver?
mark, with an old NVidia card that is *NOT* supported by anything newer than 174, and *certainly* not by the "generic" xorg x11 nvidia driverwhy dkms? use nvidia-x11-drv-173xx and kmod-nvidia-173xx from elrepo, the kmod is kabi-tracking.
That's the one I think I'm using. Somehow, when I did my most recent update, to kernel 2.6.18-164.11.1.el5, or whenever it did an X update, I lose track, it installed dkms-nvidia-x11-drv. I want to prevent that update from occurring in the future... and I may need to do it on some users' systems, also with older nvidia cards.
mark
On Thu, Mar 18, 2010 at 11:13 AM, m.roth@5-cent.us wrote:
why dkms? use nvidia-x11-drv-173xx and kmod-nvidia-173xx from elrepo, the kmod is kabi-tracking.
That's the one I think I'm using. Somehow, when I did my most recent update, to kernel 2.6.18-164.11.1.el5, or whenever it did an X update, I lose track, it installed dkms-nvidia-x11-drv. I want to prevent that update from occurring in the future... and I may need to do it on some users' systems, also with older nvidia cards.
Try uninstalling the dkms stuff using yum like so:
yum remove dkms-nvidia-x11-drv
If you do not have any other dkms-dependent packages, you should remove all dkms-xxx.
Akemi
On Thu, Mar 18, 2010 at 11:13 AM, m.roth@5-cent.us wrote:
why dkms? use nvidia-x11-drv-173xx and kmod-nvidia-173xx from elrepo, the kmod is kabi-tracking.
That's the one I think I'm using. Somehow, when I did my most recent update, to kernel 2.6.18-164.11.1.el5, or whenever it did an X update, I lose track, it installed dkms-nvidia-x11-drv. I want to prevent that update from occurring in the future... and I may need to do it on some users' systems, also with older nvidia cards.
Try uninstalling the dkms stuff using yum like so:
yum remove dkms-nvidia-x11-drv
Did that, and it tried again. I finally had to rerun the build/install of the 173 package.
If you do not have any other dkms-dependent packages, you should remove all dkms-xxx.
Mmmm... I was afraid to do that, not being sure what else it loads. However, if I rpm -qa | grep dkms, I only see dkms itself. I also see links in /etc/rc?.d to the /etc/init.d/dkms_autoinstaller, so I just used chkconfig to turn it off. That should fix me.
But what else does dkms install? What's it there for, that it came in? Is it on by default, or did some recent update (the last month or so) turn it on?
mark
On Thu, Mar 18, 2010 at 12:37 PM, m.roth@5-cent.us wrote:
If you do not have any other dkms-dependent packages, you should remove all dkms-xxx.
Mmmm... I was afraid to do that, not being sure what else it loads. However, if I rpm -qa | grep dkms, I only see dkms itself.
In that case, you can safely remove dkms.
yum remove dkms
After doing that, please show us the output of:
ls -l `find /lib/modules -name nvidia.ko`
Akemi
Akemi wrote:
On Thu, Mar 18, 2010 at 12:37 PM, m.roth@5-cent.us wrote:
If you do not have any other dkms-dependent packages, you should remove all dkms-xxx.
Mmmm... I was afraid to do that, not being sure what else it loads. However, if I rpm -qa | grep dkms, I only see dkms itself.
In that case, you can safely remove dkms.
yum remove dkms
The chkconfig stop ought to take care of its accidentally running.
After doing that, please show us the output of:
ls -l `find /lib/modules -name nvidia.ko`
How 'bout find /lib/modules -name nvidia.ko -ls? 30965907 0 lrwxrwxrwx 1 root root 48 Mar 18 09:48 /lib/modules/2.6.18-164.2.1.el5/weak-updates/nvidia.ko -> /lib/modules/2.6.18-164.11.1.el5/extra/nvidia.ko 31031730 0 lrwxrwxrwx 1 root root 48 Mar 18 09:48 /lib/modules/2.6.18-164.6.1.el5/weak-updates/nvidia.ko -> /lib/modules/2.6.18-164.11.1.el5/extra/nvidia.ko 31064673 0 lrwxrwxrwx 1 root root 48 Mar 18 09:48 /lib/modules/2.6.18-164.9.1.el5/weak-updates/nvidia.ko -> /lib/modules/2.6.18-164.11.1.el5/extra/nvidia.ko 30704811 12004 -rw-r--r-- 1 root root 12270160 Jan 22 10:36 /lib/modules/2.6.18-164.10.1.el5/extra/nvidia.ko 30736857 11192 -rw-rw-r-- 1 root root 11437204 Jan 15 09:50 /lib/modules/2.6.18-164.10.1.el5/kernel/drivers/video/nvidia/nvidia.ko 31096947 0 lrwxrwxrwx 1 root root 48 Mar 18 09:48 /lib/modules/2.6.18-164.10.1.el5/weak-updates/nvidia.ko -> /lib/modules/2.6.18-164.11.1.el5/extra/nvidia.ko 30770916 11180 -rw-r--r-- 1 root root 11424810 Mar 18 10:09 /lib/modules/2.6.18-164.11.1.el5/kernel/drivers/video/nvidia.ko
mark
On Thu, Mar 18, 2010 at 12:56 PM, m.roth@5-cent.us wrote:
ls -l `find /lib/modules -name nvidia.ko`
How 'bout find /lib/modules -name nvidia.ko -ls? 30965907 0 lrwxrwxrwx 1 root root 48 Mar 18 09:48 /lib/modules/2.6.18-164.2.1.el5/weak-updates/nvidia.ko -> /lib/modules/2.6.18-164.11.1.el5/extra/nvidia.ko 31031730 0 lrwxrwxrwx 1 root root 48 Mar 18 09:48 /lib/modules/2.6.18-164.6.1.el5/weak-updates/nvidia.ko -> /lib/modules/2.6.18-164.11.1.el5/extra/nvidia.ko 31064673 0 lrwxrwxrwx 1 root root 48 Mar 18 09:48 /lib/modules/2.6.18-164.9.1.el5/weak-updates/nvidia.ko -> /lib/modules/2.6.18-164.11.1.el5/extra/nvidia.ko 30704811 12004 -rw-r--r-- 1 root root 12270160 Jan 22 10:36 /lib/modules/2.6.18-164.10.1.el5/extra/nvidia.ko 30736857 11192 -rw-rw-r-- 1 root root 11437204 Jan 15 09:50 /lib/modules/2.6.18-164.10.1.el5/kernel/drivers/video/nvidia/nvidia.ko 31096947 0 lrwxrwxrwx 1 root root 48 Mar 18 09:48 /lib/modules/2.6.18-164.10.1.el5/weak-updates/nvidia.ko -> /lib/modules/2.6.18-164.11.1.el5/extra/nvidia.ko 30770916 11180 -rw-r--r-- 1 root root 11424810 Mar 18 10:09 /lib/modules/2.6.18-164.11.1.el5/kernel/drivers/video/nvidia.ko
It's a mess. :-(
You have missing symlinks (If you run the original command, you'd see red-blinking lines). nvidia.ko built by dkms is still there, etc.
If I were you, I would completely remove dkms and all nvidia.ko and symlinks above. Then do a clean install of the kmod package ( http://elrepo.org/tiki/kmod-nvidia-173xx ).
Akemi
On Thu, Mar 18, 2010 at 12:56 PM, m.roth@5-cent.us wrote:
ls -l `find /lib/modules -name nvidia.ko`
How 'bout find /lib/modules -name nvidia.ko -ls? 30965907 0 lrwxrwxrwx 1 root root 48 Mar 18 09:48 /lib/modules/2.6.18-164.2.1.el5/weak-updates/nvidia.ko ->
<snip>
It's a mess. :-(
That's after I did a yum remove of the 184 (I think it was).
You have missing symlinks (If you run the original command, you'd see red-blinking lines). nvidia.ko built by dkms is still there, etc.
If I were you, I would completely remove dkms and all nvidia.ko and symlinks above. Then do a clean install of the kmod package ( http://elrepo.org/tiki/kmod-nvidia-173xx ).
Don't need that - I've got NVIDIA-Linux-x86_64-173.14.20-pkg2.run from NVidia, I think, and I run that, and it rebuilds the drivers.
I'll clean the leftover junk; that's a good idea, though. Thanks.
mark
m.roth@5-cent.us wrote:
On Thu, Mar 18, 2010 at 12:56 PM, m.roth@5-cent.us wrote:
ls -l `find /lib/modules -name nvidia.ko`
How 'bout find /lib/modules -name nvidia.ko -ls? 30965907 0 lrwxrwxrwx 1 root root 48 Mar 18 09:48 /lib/modules/2.6.18-164.2.1.el5/weak-updates/nvidia.ko ->
<snip> > It's a mess. :-(
That's after I did a yum remove of the 184 (I think it was).
You have missing symlinks (If you run the original command, you'd see red-blinking lines). nvidia.ko built by dkms is still there, etc.
If I were you, I would completely remove dkms and all nvidia.ko and symlinks above. Then do a clean install of the kmod package ( http://elrepo.org/tiki/kmod-nvidia-173xx ).
Don't need that - I've got NVIDIA-Linux-x86_64-173.14.20-pkg2.run from NVidia, I think, and I run that, and it rebuilds the drivers.
The reason 2 people suggested you use the elrepo nvidia package(s) is so you don't have to rebuild the driver from the nvidia installer every time you update your kernel.
The elrepo kmod-nvidia packages are kABI-tracking so will work seamlessly across kernel updates - will even work seamlessly for 5.5 when that is released too. So it's install once and forget, couldn't be easier.
Furthermore, elrepo has the latest version of your driver (173.14.25) and you will continue to receive updates automatically through yum rather than having to manually update the driver from nvidia (if you were to even notice a new version has been released).
-
Akemi Yagi -
m.roth＠5-cent.us -
Ned Slider -
Nicolas Thierry-Mieg