xircon
21
Found it!!! An entry in grub (or tbh several), removed and working. All as a result of trying to get sway running (and I did, just really badly 
).
These entries:
GRUB_CMDLINE_LINUX_DEFAULT="rd.driver.blacklist=nouveau nohpet nvidia-drm.modeset=1 resume=UUID=ba983a7c-9d2a-4b9f-88bb-8879c19eae00 loglevel=3 nowatchdog nvme_load=YES"
## Changed to:
GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID=ba983a7c-9d2a-4b9f-88bb-8879c19eae00 loglevel=3 nowatchdog"
And it works. These entries did not affect the previous version, so I assumed they were not a problem
1 Like
Interesting. I used hpet=disable , and I can’t find the nohpet option in the kernel-parameters.txt documentation…
GRUB_CMDLINE_LINUX_DEFAULT="iommu=pt random.trust_cpu=on nvidia-drm.modeset=1 nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1 amd_pstate.shared_mem=1 hpet=disable tsc=unstable loglevel=3 quiet"
xircon
23
Just a cursory search I cannot remember where I saw that (Have reinstated as I realised it was not part of the problem).
xircon
24
1 Like
I’m going to go by the kernel documentation rather than a page that makes an unreferenced assertion:
1 Like
