I am experiencing similar issues. NVIDIA GPU and Linux-Zen kernel here.
I tried an update without the kernel update, and I still have issues…
I also tried re-installing the NVIDIA drivers and problems persist. I think there is currently an issue with the NVIDIA driver and the latest kernel, but I can’t be sure. I see “flip event timeout on head0” errors relating to NVIDIA-DRM on startup and a bunch of bluetooth errors which look like red herrings.
The system still boots up eventually, but it takes ages.
RTX 2080
Ryzen 5800X
Once booted, everything appears to be fine, so far…but it takes ages to get there.
I updated my BIOS to see if that helps, but it doesn’t…same problem.
Problem for me is definitely either NVIDIA driver related or it’s the latest Linux-Zen kernel.
I should point out that the DRM errors I see happen before any desktop environment is loaded. It just sits there for ages spitting out the same error until eventually I get a login screen. Then everything seems to be fine…occasionally, it’ll just hang there indefinitely.
I’m almost 100% sure it’s an NVIDIA driver bug with the latest kernel.
mhwd-kernel -li
Currently running: 6.6.4-AMD-znver3 (linux-amd-znver3)
The following kernels are installed in your system:
local/linux-zen 6.6.3.zen1-1
local/linux-amd-znver3 6.6.v.4-1
Please do not post here in the forum, like in chat forums like Telegram.
As long as no one has responded to your post, you can edit your post.
Ok noted, but if you don’t post in a linear fashion, it’s hard for people to follow the timeline of the thread if they weren’t here when the thread was started. That’s why forums are threaded.
Yeah jank forum modding. I originally participated in another thread.
I work in tech / dev and deal with threaded tickets all the time. Its way easier to assist someone if you have the thread organized in a linear fashion. Even if it makes the thread massive because you can read it top to bottom and not have to bounce back to the top to read edits…it also allows outsiders to bring themselves up to speed a lot quicker…more importantly you know not just what someone has tried you also know why and when and how they got there…way less ambiguous.
You branch out at junctures…say there are two options to try. That creates two new threads to follow. Eventually when a solution is reached you prune the dead branches and you have a single timeline that leads to the correct solution.
I’ve been working this way for 20 years and it has never steered me wrong.
With this setup, you can end up with loads of potential solutions that people will try in various different orders that may result in a solution, but you won’t know why.
I think you’re right. You think you’re right. Forum Mods think you’re wrong. Guess who wins the shoot-out?
That makes sense, and is what was originally meant.
This is very much an International Linux users forum. Many users need to resort to translation software–or what they learned in a language school–and it’s not uncommon for translations that include conceptual ideas, especially, to be mis-translated or difficult to grasp.
The other user that reported this issue tried the LTS kernel and reported no improvement, so another kernel such as the linux-hardened might be worth a try. If you feel your Nvidia driver could be a cause then perhaps you might want to test out the free Nvidia driver.
Thanks for the pointers. The open driver seems to work, but that just narrows the problem down to the NVIDIA driver. The open driver isn’t actually a fix.
I think either I have to wait for a newer kernel that handles the problem, or I need to wait for a newer NVIDIA driver. In the meantime, I’ll hold off updating those packages.
