Anyone else having similar experience? This is the first time something like that happened in a decade of using the latest stable kernel release (in my experience, it's actually been stable for all that time except for 6.10).
Anyone else having similar experience? This is the first time something like that happened in a decade of using the latest stable kernel release (in my experience, it's actually been stable for all that time except for 6.10).
Again, I was surprised by the number of firmware and driver issues since RNDA1/2/3 have been around for years now.
I also had an AMDGPU system. 5600X, AMD 6800 GPU, Fedora 40. -> now win11 (which has so much cruft out of the box I am considering nuking it and going back haha)
First there was the bug that broke Chromium based apps when using SELinux. https://lore.kernel.org/all/30fc5b38165e4eda57d640eca76b7df1...
Then 6.10.6 didn't want to boot.
Usually I run into issues two or three times a year. I guess this time around they just happened to be a little closer together.
Never had such an issue before.
Even the latest Linux kernel 6.11 still have same issues (atleast for me)
Resume from sleep stopped working, and boot started taking minutes. Going through logs I was able to figure out it was probably usb related, and that sleep worked if you were patient enough to wait for a timeout, but the issue persisted with all cables unplugged. The error code was something along the lines of failing to provide enough power for a device, I suspected my new speakers despite them having dedicated wall outlet power (usb audio despite being on the motherboard AFAIK)
Long story short someone in a thread somewhere suggested unplugging from the wall for 10 min and to my surprise it worked - I guess it cleared the fault somehow and it hasn't reoccurred (yet). Might be worth a try.
If I boot from kernel version 6.5, suspend works fine. Hold shift while your machine is booting and the grub menu will allow you to select a different kernel version.
https://kernelci.org/ is a big one, Linaro has theirs https://lkft.linaro.org/, Intel has multiple farms, Collabora works relentlessly with GitLab integration https://www.collabora.com/news-and-blog/news-and-events/patc......
The kernel is very much tested before a release with gigantic automated labs on real hardware.
So what went wrong?
Honestly, I'd love to set up this kind of thing, but I've not seen a job for it that doesn't need C expertise:(
intel_gpu_top showed both Video and VideoEnhance markers signaling hardware decode as inactive, and all commenters on message boards that I came across essentially came to the same conclusion, that it doesn't work at least at the time I as trying a few months ago. I think it was that Chromium devs don't support it and block it from functioning in the code because of this or that upstream dependency not being stable.
Key thing is to make sure you are playing back supported codecs when checking for hw decode. E.g YouTube randomly forces av1 on clients and some older hardware don't support hw decode for it.
Also some distros like Fedora and OpenSUSE ship with partial codec support in their installation media.
An easy way to make sure you have all the right drivers in place is to test this in one of the Chromium flatpaks.
Though I have to state hardware video playback is not yet officially supported and it has broken a lot over the past due to this fact and the quality of the different GPU drivers in question here. The Chromium devs don't explicitly block vaapi on Intel hardware.
In this past year, I've since moved to Windows after like 7 years of constantly messing and tweaking Linux to kinda sorta almost for some stretch of time get all the things to work after spending hours looking for the right configuration. Look at how long this thread is, for example[0]. Or here most saying it still doesn't work[1] and the flags constantly change. Before Linux I was about 6 yrs on Mac. I hadn't used Windows for so long, it actually felt weird to have so much hardware and software support for anything I ever need to use.
I'll take your word for it that Chromium sometimes uses hardware decoding now. But as you say, and they should put that slogan on a T-shirt: "Linux on Desktop: not officially supported and it has broken a lot over the past due to lack of support and quality of driver". I wouldn't really characterize that as "have no problem using". It feels nice to have a system that just works without all that hassle and tweaking so I can just get actual work done, or watch Youtube efficiently without brittle configuration, no window manager bugs etc.
[0] https://bbs.archlinux.org/viewtopic.php?id=244031&p=40
[1] https://www.reddit.com/r/linux/comments/1ey4n2k/heres_how_to...
There were problems on earlier kernels, but they were mostly fixed by a firmware update. Kernel already had support by that time.
This isn't the first time I've had problems with the stable kernel, though. A while back I had problems, also graphics related, with Intel i915 (my onboard graphics that I used before I got the AMD card). It took a while but it eventually got fixed. I haven't looked to see if there's a bug tracked for the AMD problem.
After I upgraded to a 7900XT it worked again.
What was wrong? What actually happened was that on bootup, the amdgpu driver would panic and fault during boot exactly when fsck was happening, and the framebuffer would be stuck forever. So it just looked like a filesystem issue but in reality my graphics output was merely fubar; the system itself was otherwise fine tnough.
This is reliable and reproducible for me; it always faults at almost the exact same spot at boot every time, for this kernel version at least. In reality amdgpu has been unreliable for me for 5+ releases at this point on a card less than like 7 years old.
Really considering moving over to a small cheap nvidia card and just running Nouveau instead. At least then I might have a reliable framebuffer.