This is a bad idea, unless you have bleeding edge hardware that is not supported by LTS kernel, which is rare
Each user should have the LTS kernel installed an ready to go IMHO as a backup, paricularly running the mainline kernel, which is always prone to teething problems like this.
This mainline kernel update it was nvidia drivers, last kernel update it was virtualbox.
I prefer to just use the mainline kernel. Yes there were virtualbox issues last time but again it’s not the fault of the kernel same as the nvidia problem. I don’t think it’s a bad idea it’s just the way i roll!
Since kernel 5.9 was released, there have been 2 Nvidia dkms updates. Before those the system refused to boot with kernel 5.9.1. Booted fine with kernel-lts. Latest kernel working fine now. At least as far as I can tell. I don’t use Cuda, Nvenc or similar extras.
uname -a
Linux DesktopEOS 5.9.1-arch1-1 #1 SMP PREEMPT Sat, 17 Oct 2020 13:30:37 +0000 x86_64 GNU/Linux
yay -Qs nvidia
local/egl-wayland 1.1.5-1
EGLStream-based Wayland external platform
local/lib32-libvdpau 1.4-1
Nvidia VDPAU library
local/lib32-nvidia-utils 455.28-1
NVIDIA drivers utilities (32-bit)
local/libvdpau 1.4-1
Nvidia VDPAU library
local/libxnvctrl-390xx 390.138-1
NVIDIA NV-CONTROL X extension, 390xx legacy branch
local/nvidia-390xx-dkms 390.138-7
NVIDIA driver sources for linux, 390xx legacy branch
local/nvidia-390xx-settings 390.138-1
Tool for configuring the NVIDIA graphics driver, 390xx legacy branch
local/nvidia-390xx-utils 390.138-3
NVIDIA drivers utilities
local/nvidia-installer-db 2.4.9-1
Database for the script to setup nvidia drivers in EndeavourOS
local/nvidia-installer-dkms 3.3.8-1
Script to setup nvidia drivers (dkms version) in EndeavourOS
local/opencl-nvidia-390xx 390.138-3
OpenCL implemention for NVIDIA
I recognized that there is an error massage referring to unability to load kernel modules during boot. One is supposed to check systemctl status systemd-modules-load.service. Will have to dig a little deeper. That message didn’t appear (as far as I remember) before kernel 5.9 arrived. That’s the case on both of my systems (Desktop and Netbook).
I have the same problem as Trekkie, kernel modules not loading at boot after the update to 5.9 with Deepin EOS. Deepin had some updates at the same time.
After noticing the error on boot, I checked the journal and it appears to be systemd related:
Oct 25 07:24:48 odin systemd[1]: Failed to start Load Kernel Modules.
Oct 25 07:24:48 odin systemd-modules-load[260]: Failed to insert module ‘vfs_monitor’: Invalid argument
I can’t find the configuration file that relates to vfs-monitor and the systemd modules that are loaded so I am clueless as to how to fix this, other than using timeshift back to an old configuration.
I looked for the configuration file mentioning vfs-monitor in /etc/, /run/, /usr/local/lib/, and /usr/lib/ but no result so I guess nothing has been modified through a .conf file. Is this definitely a kernel problem?