Neither my akmod-nvidia works, nor dkms for VirtualBox

DennyCrane · #1 14th December 2008, 02:29 PM

I'm still on Fedora 9...

I believe I have two extra kernel modules -- the one for nvidia, and the one for VirtualBox. akmod-nvidia is apparently the preferred method for taking care of nvidia, but it doesn't work for me (apparently it is a known problem without current fix: http://forums.fedoraforum.org/showth...=188241&page=8). Currently I have to manually download the latest kmod package any time the kernel is update. (I don't understand why since I have installed the "meta" package which claims it will keep track and download the latest kmod, too.)

But also, VirtualBox says dkms should do the job, so I had installed it, but it doesn't work. I believe I've asked before if there is some configuration I'm supposed to do (other than the command vbox says to run), but have not been able to find such info.

BTW, here's what VirtualBox says -- The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root. Users of Ubuntu or Fedora should install the DKMS package at first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. -- I have installed dkms, but I always have to manually enter the command they note in order to recompile.

So, I finally took the time to restart a few times to transcribe some of the messages that come up in rhgb (does anyone happen to know if there is a more convenient way to see these messages (i.e. a log)?), hopefully they will prove useful in resolving my problems?:

Quote:

/etc/rc5.d/s04dkms-autoinstaller: line 82: /var/lib/dkms/nvidia/173.14.12-1.fc9/source/dkms.conf: No such file or directory

later:

Quote:

Starting VirtualBox kernel module [Failed]
(No suitable module for running kernel found)

Any help?

DennyCrane · #2 14th December 2008, 02:38 PM

Oh, forgot to include some info ...

the file noted -- /var/lib/dkms/nvidia/173.14.12-1.fc9/source/dkms.conf -- there is a broken symlink at /var/lib/dkms/nvidia/173.14.12-1.fc9/source that ponits to /usr/src/nvidia-173.14.12-1.fc9 ... ???

Also, regarding the VirtualBox message -- "or there is a permission problem with /dev/vboxdrv" -- actually, I was going to say I think I've checked the permissions before .. but that file doesn't exist (I'm assuming because it wasn't compiled?)

DennyCrane · #3 15th December 2008, 12:11 AM

Does this work for anyone else, or no?

***Hlingler*** · #4 15th December 2008, 12:17 AM

This is an odd problem. Verify the integrity of all affected packages (*nvidia*, dkms, *vbox*, etc.):
rpm -V ...

V

DennyCrane · #5 15th December 2008, 12:27 AM

This?:

Code:

[username@machinename ~]$ rpm -V dkms
.......T  c /etc/dkms/framework.conf
[username@machinename ~]$ rpm -V VirtualBox
S.?.....    /usr/lib/virtualbox/VBoxHeadless
S.?.....    /usr/lib/virtualbox/VBoxSDL
S.?.....    /usr/lib/virtualbox/VirtualBox
[username@machinename ~]$ rpm -V akmod-nvidia
[username@machinename ~]$ rpm -V kmod-nvidia
[username@machinename ~]$ rpm -V xorg-x11-drv-nvidia
[username@machinename ~]$ rpm -V xorg-x11-drv-nvidia-libs
prelink: /usr/lib/nvidia/tls/libnvidia-tls.so.173.14.15: section file offsets not monotonically increasing
S.?.....    /usr/lib/nvidia/tls/libnvidia-tls.so.173.14.15
[username@machinename ~]$

***Hlingler*** · #6 15th December 2008, 12:30 AM

This is not right; I see:
~]$ rpm -V dkms
~]$

Nothing=no problems. The VBox stuff will go away if you run 'rpm -v ...' as root. The "prelink" stuff is cruft - ignore it.

Re-install dkms and try again.

V

DennyCrane · #7 15th December 2008, 12:48 AM

I've actually tried reinstalling dkms and some of the other packages numerous times. The message still appears during boot, but ...

Code:

[root@machinename ~]# rpm -V dkms
[root@machinename ~]#

***Hlingler*** · #8 15th December 2008, 01:18 AM

The broken sym-link is probably a left-over from a nvidia-x11-drv-173.14.12-1.fc9 RPM that you had installed at one time. You don't have two different nvidia drivers installed, right? You do have all current/matching kernel-devel and latest kernel-headers installed, correct??

V

DennyCrane · #9 15th December 2008, 01:23 AM

I am quite sure I only have one nvidia driver, and I am positive I have kernel-2.6.27.7-53, along with kernel-devel-2.6.27.7-53, and kernel-headers-2.6.27.7-53

DennyCrane · #10 15th December 2008, 01:24 AM

Does it matter that my kernel and kernel-devel say i686, while my kernel-headers says i386?

***Hlingler*** · #11 15th December 2008, 01:25 AM

Out of ideas at the moment, sorry. Although I'm beginning to reconsider upgrading to F10....

V

Quote:

Does it matter that my kernel and kernel-devel say i686, while my kernel-headers says i386?

No. Perfectly copacetic.

DennyCrane · #12 15th December 2008, 01:30 AM

Alright, thanks for trying :-)

robatino · #13 21st December 2008, 07:39 PM

I'm also wondering whether any configuration is necessary for dkms and VirtualBox. I tried it a while back and still had to run the setup command manually. Now that I'm running Fedora 10 and VB 2.1.0, I'll reinstall dkms and watch what happens when the next kernel is installed.

DennyCrane · #14 21st December 2008, 07:42 PM

Quote:

Originally Posted by robatino

I'm also wondering whether any configuration is necessary for dkms and VirtualBox. I tried it a while back and still had to run the setup command manually. Now that I'm running Fedora 10 and VB 2.1.0, I'll reinstall dkms and watch what happens when the next kernel is installed.

It drives me nuts that I only get to test this when it "breaks" again (i.e. when each kernel comes out). I've tried living without VirtualBox for several days at a time, but then I finally give in and run the command

***Firewing1*** · #15 21st December 2008, 08:10 PM

<semi-offtopic>
Btw, sorry about the akmods probem - I completely forgot about that. I'll look into it later (next weekend) once Christmas + exams are over

Firewing1