So no idea what the exact fail combo is, but I am fully updated, and working, on a clean install. Installed Fedora 31 Cinnamon from USB. Rebooted, I have only kernel 5.3.7-301 Removed dnf dragora GUI sudo dnf remove dnfdragora* -y Rebooted. Upgraded all but grub2 sudo dnf upgrade --refresh -y --exclude grub2* Rebooted, not I now have kernel 5.3.13-300 available and default. Upgraded grub2 sudo dnf upgrade --refresh -y, I did receive the above SELinux errors again, they may be normal? Rebooted, system working normally.

@black3dynamite said in Blank Screen After Fedora 30 Update to 5.3.5 Kernel on Dell Inspiron Laptop: @scottalanmiller said in Blank Screen After Fedora 30 Update to 5.3.5 Kernel on Dell Inspiron Laptop: @black3dynamite said in Blank Screen After Fedora 30 Update to 5.3.5 Kernel on Dell Inspiron Laptop: @scottalanmiller said in Blank Screen After Fedora 30 Update to 5.3.5 Kernel on Dell Inspiron Laptop: @notverypunny said in Blank Screen After Fedora 30 Update to 5.3.5 Kernel on Dell Inspiron Laptop: I've lost track of which distros are using which backends for graphics, but could it be related to xorg vs wayland or something along those lines? Seems kinda of likely, but can't track it down. Your desktop environment is Cinnamon? Fedora Workstation and I believe RHEL 8 and CentOS 8 that uses GNOME3 is about the only distros that defaults to wayland. It is, yes. F30 with Cinnamon. The F31 that worked was Gnome 3. Are you planning on trying F31 with Cinnamon? And it worked fine. Doing the F31 update fixed it.

We use ghost adapters to allow EDID hi res with no head attached, I wonder if there is one that forces 640x480? I'll search around...

Alright, I took another approach at this. Looking directly at the source for different kernels over at kernel.org I can see that the NVMe driver has SR-IOV support from kernel version 4.8. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/nvme/host/pci.c?h=v4.8#n2015 It's very interesting for virtualized workloads because SR-IOV means you can assign the NVMe disk to different VMs directly and bypass the hypervisor. This is the same for NICs at 10/25/40/100 gigabit. There will be a significant performance drop if you don't use SR-IOV.

@fateknollogee said in Fedora 27: Kernel upgrade to 4.14.8-300....no boot: @black3dynamite said in Fedora 27: Kernel upgrade to 4.14.8-300....no boot: @fateknollogee said in Fedora 27: Kernel upgrade to 4.14.8-300....no boot: Server is Lenovo RD640 o/s: Fedora 27 installed kernel: 4.13.9.300 Tried upgrading to 4.14.8-300...the system gets to the grub screen where I can see both available kernels...screen goes black...after waiting a few minutes, I ctrl-alt-del, reboot, choose 4.14..9-300 Anyone have a Lenovo server with upgraded kernel? I've experienced the boot issue while using 4.14.11, I had to turn off Kernel Page Table Isolation (KPTI). What flavor of hardware? On my very old lab server running Hyper-V 2012 R2. Hardware: PowerEdge 2950 CPU: Intel Xeon E5430 VM: Fedora 27

It's neat because it is a rare test where basically only the kernel is different. So you really get to see Linux vs. NTKernel rather than artefacts of the entire stack.

Not worth the effort for the case. Thanks for the help guys.

My Linux is better than your Linux.

Classic Curtis.

The boost to copy operations for NFS is pretty nifty.

@scottalanmiller said: (Windows 10 is kernel NT 6.4.) Windows 10 is kernel version 10. They changed it after one of the major consumer previews were released.