[SOLVED] vboxdrv not found after emerge @module-rebuild

[starsky]

Hi,

I recently upgraded kernel to: 6.1.53-gentoo-r1

To be honest I did not run virtualbox for some time. And I realized that I have to upgrade the kernel modules:

So I did as always:

Code: Select all

emerge --ask @module-rebuild
depmod -a
modprobe vboxdrv

But this time I got an error:

Code: Select all

modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/6.1.53-gentoo-x86_64

I checked for the .ko file

Code: Select all

find /lib/modules/$(uname -r) -type f -name '*.ko*'|grep vbo
/lib/modules/6.1.53-gentoo-x86_64/kernel/drivers/virt/vboxguest/vboxguest.ko
/lib/modules/6.1.53-gentoo-x86_64/kernel/drivers/gpu/drm/vboxvideo/vboxvideo.ko

Indeed there is no vboxdrv.ko

Now I started to wonder, why is that. Because

Code: Select all

 emerge --ask @module-rebuild 

went without errors.

I checked the build log and I found such entry:

Code: Select all

Install app-emulation/virtualbox-modules-7.0.10 into /var/tmp/portage/app-emulation/virtualbox-modules-7.0.10/image

I checked that the file was there

Code: Select all

/var/tmp/portage/app-emulation/virtualbox-modules-7.0.10/image/lib/modules/6.1.53-gentoo-r1-x86_64/misc/vboxdrv.ko

But never made to

Code: Select all

/lib/modules

Do you know what is going on? Cause I am a bit confused.

[alamahant]

What is the output of

Code: Select all

ls /lib/modules/6.1.53-gentoo-x86_64/misc
and
ls -l /usr/src/linux

Try explicitly emerging

Code: Select all

emerge -1av app-emulation/virtualbox-modules

This is what i got

Code: Select all

[ebuild  N     ] app-emulation/virtualbox-modules-7.0.10:0/7.0::gentoo  USE="strip -dist-kernel -modules-sign" 701 KiB

Total: 1 package (1 new), Size of downloads: 701 KiB

Would you like to merge these packages? [Yes/No] y
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) app-emulation/virtualbox-modules-7.0.10::gentoo
>>> Installing (1 of 1) app-emulation/virtualbox-modules-7.0.10::gentoo
>>> Completed (1 of 1) app-emulation/virtualbox-modules-7.0.10::gentoo
>>> Jobs: 1 of 1 complete                           Load avg: 0.89, 0.36, 0.53
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.
lake ~ # find /lib/modules/$(uname -r) -type f -name '*.ko*'|grep vbo
/lib/modules/6.3.0-gentoo/misc/vboxnetflt.ko.zst
/lib/modules/6.3.0-gentoo/misc/vboxnetadp.ko.zst
/lib/modules/6.3.0-gentoo/misc/vboxdrv.ko.zst

[Ionen]

Odds are you simply built it against the wrong kernel.

See eselect kernel list, is 6.1.53-gentoo-x86_64 selected? (ls -l /usr/src/linux from above post would also point this out)

[starsky]

Odds are you simply built it against the wrong kernel.

See eselect kernel list, is 6.1.53-gentoo-x86_64 selected? (ls -l /usr/src/linux from above post would also point this out)

You are right. I did not notice it.

I compiled 6.1.53-gentoo-r1 kernel and set it via eselect etc.
What I did not notice is that 6.1.53-gentoo stayed on top of the list in grub as a default option.
So I was booting wrong kernel.

Thanks, so much. Such an easy mistake, but so difficult to notice.

[freke]

Odds are you simply built it against the wrong kernel.

See eselect kernel list, is 6.1.53-gentoo-x86_64 selected? (ls -l /usr/src/linux from above post would also point this out)

You are right. I did not notice it.

I compiled 6.1.53-gentoo-r1 kernel and set it via eselect etc.
What I did not notice is that 6.1.53-gentoo stayed on top of the list in grub as a default option.
So I was booting wrong kernel.

Thanks, so much. Such an easy mistake, but so difficult to notice.

Yes - grub doesn't sort the -r releases properly

[sMueggli]

Yes - grub doesn't sort the -r releases properly

What do you mean? I do not have any problems with Grub and the newest kernel is always on top after recreating the grub.cfg.

[freke]

Yes - grub doesn't sort the -r releases properly

What do you mean? I do not have any problems with Grub and the newest kernel is always on top after recreating the grub.cfg.

Sorry - I think I mixed up.... iirc it's the eclean that doesn't register the -r releases properly.

EDIT:
I actually stand by my first comment

Running 6.1.59 and now just installed 6.1.59-r1 - 6.1.59 stays at the top of grub.cfg, the r1-kernel is number two in the list.
That's only an issue with revisions - new versions are properly at top.