You are not logged in.
when I do
KERNELVERSION="5.1.7-matsumoto"
dkms install -k "$KERNELVERSION" --verbose vboxhost/6.0.8_OSEit creates
/lib/modules/$KERNELVERSION/kernel/misc/vboxdrv.ko.xz
/lib/modules/$KERNELVERSION/kernel/misc/vboxnetadp.ko.xz
/lib/modules/$KERNELVERSION/kernel/misc/vboxnetflt.ko.xz
/lib/modules/$KERNELVERSION/kernel/misc/vboxpci.ko.xz
instead of uncompressed modules
and because they are compressed loading those modules failed
this used to work a couple of weeks ago, I may have updated either dkms or virtualbox (or both) but I don't remember
any idea why is this happening???
Offline
You don't have to "remember", it's all in your pacman.log. Check there to see what was updated when.
What are you trying to achieve in the first place? Why are you running dkms manually, instead of letting pacman and its hooks do it for you and why do you need uncompressed modules?
Offline
Hey twelveeighty!
thanks for replying, Sorry for the delay, a lot of work in here.
I need to run dkms manually because I compile my kernel often. I thought my kernel was fine and didn't mention it earlier in my first post. VB and dkms haven't changed in weeks. One the other handI have compiled other kernels using the current versions of VB and dkms, what made me realized that my latest kernel is the culprit (even though I don't see how this is affect the creation of VB modules) any idea about how ti fix this?
Offline
@juanp_1982 62879?
Offline
Hi loqs!
thanks for the link! I appreciate it, I'll downgrade dkms :-)
Offline