Well, looks like a bit more than just installing zen is required, at least on my machine.
Had a bit of a panic situation this morning when back at my desk (2 monitor setup) after a week off and the nVidia card wouldn’t load any longer. Turns out that all of my kernel extra modules were missing:
Not a big deal because I am now back on the regular kernel and back in business. But as an eager learner :-), what do I have to do to get all these modules linked to the Zen kernel?
By the way, after running Zen for a week I can’t tell a difference between Zen and the regular kernel.
Here is the result of one benchmark test comparing linux-zen an linux-hardened. My guess is that the result is more or less the same for the other kernels as well
Did a bit of research on this but without any luck. Does anyone have an idea why off the three kernels I have installed only one, 5.8.x, has got the extramodules folder?
For LTS to be a true backup kernel I would need all those modules available for LTS as well.
Thanks guys, I need to read up on this some more, switching to dkms seems like a pretty fundamental change which I need to better understand before I ruin my current install
nVidia and vBOX seem to be covered, last one I need is bbswitch.
==> dkms install --no-depmod -m vboxhost -v 6.1.12_OSE -k 5.8.7-arch1-1
==> dkms install --no-depmod -m bbswitch -v 0.8 -k 5.8.7-zen1-1-zen
==> dkms install --no-depmod -m nvidia -v 450.66 -k 5.4.63-1-lts
==> dkms install --no-depmod -m nvidia -v 450.66 -k 5.8.7-zen1-1-zen
==> dkms install --no-depmod -m bbswitch -v 0.8 -k 5.4.63-1-lts
==> dkms install --no-depmod -m nvidia -v 450.66 -k 5.8.7-arch1-1
Good news! Module version 450.66 for nvidia.ko.xz
exactly matches what is already found in kernel 5.8.7-arch1-1.
DKMS will not replace this module.
You may override by specifying --force.
Good news! Module version 450.66 for nvidia-modeset.ko.xz
exactly matches what is already found in kernel 5.8.7-arch1-1.
DKMS will not replace this module.
You may override by specifying --force.
Good news! Module version 450.66 for nvidia-drm.ko.xz
exactly matches what is already found in kernel 5.8.7-arch1-1.
DKMS will not replace this module.
You may override by specifying --force.
==> dkms install --no-depmod -m vboxhost -v 6.1.12_OSE -k 5.4.63-1-lts
==> dkms install --no-depmod -m vboxhost -v 6.1.12_OSE -k 5.8.7-zen1-1-zen
==> dkms install --no-depmod -m bbswitch -v 0.8 -k 5.8.7-arch1-1
==> depmod 5.8.7-arch1-1
==> depmod 5.4.63-1-lts
==> depmod 5.8.7-zen1-1-zen
Well if you don’t need any other extramodules, and use only the dkms packages and kernels that come directly from the repos, then I think you don’t have to worry.
dkms can sometimes get complicated if you 1) use a custom kernel, 2) use clang compiler and 3) want to sign your extramodules.
EDIT: semi off-topic:
Funnily enough, in some cases (custom kernel) you can have both dkms and the extramodule installed, in which case the extramodule takes precedence.
Looks like there is a bit more to dkms, as this morning when I put my laptop in it’s dock my primary screen, which is attached via the nVidia card, goes dark after a few minutes?
In fact, both screens will go dark for a second and then only the secondary screen will come back.
Rebooted twice now with the same results. Nothing obvious in journalctl.
The strange thing is that I can see a cursor, and the cursor will move on both screens in parallel but none of the application windows on the primary screens show. I can try to drag them over to the working second screen and will catch one by chance.
Maybe it’s Plasma or X which is struggling with the screen reset…
Coincidentally a new nVidia dkms driver arrived this morning so maybe this bug is because of the new nVidia driver and not the switch to dkms. I’ll report back once I know more.
Update: Had a few more crashes yesterday, some so bad that I couldn’t even rescue the machine with REISUB. After another bad one this morning I decided to roll back step by step, starting with the nVidia driver.
Installed the standard nVidia driver and didn’t have a crash all morning. Yesterday I was able to reliably crash the machine just be plugin in a USB device. Today things seem to be back to normal.
Interestingly yay didn’t ask me if I want to replace the dkms driver but simply installed. Means I don’t even know what I am running now? Is there a way to determine if I am running dkms or standard driver?