This Linux Kernel Was Killing Laptop Screens!!

Do you want to bring some fun and danger back to running Linux, well Linux kernel 5.19.12 was completely borked on 12th gen intel laptops and in some cases was even killing the screens.

==========Support The Channel==========

==========Resources==========

=========Video Platforms==========

==========Social Media==========

==========Credits==========
🎨 Channel Art:
Profile Picture:

#Linux #Framework #intel #OpenSource #LinuxDesktop #FOSS

🎵 Ending music

DISCLOSURE: Wherever possible I use referral links, which means if you click one of the links in this video or description and make a purchase I may receive a small commission or other compensation.

[BrodieRobertson]

This issue seems to be consistent on 12th gen but I've been seeing more people report this issue on older platforms, if you're using Intel 10th gen onwards it seems like you should just skip this kernel version altogether just to be extra safe

[CMDRSweeper]

I have the outmost respect for the Linux kernel developers, about 4 years ago I had bi daily kernel panics on my Arch server that didn't resolve with updates.
So I sat down, filed a bug report and included what I could get off the kernel panic, submitted it to the Arch Linux tracker, fully expecting it to be expelled as I guessed it was related to my ancient Core 2 CPU I was using, and how many run Arch on such old hardware?

Anyways, the issue was apparently found, shipped upstream and came in a kernel patch and until that system was retired a couple of months ago, it was rock stable again!

[sat]

That's why we need rolling release distros. Someone should test new things

[AQDuck]

Flashback to the day I decided to install Arch and just a few hours prior a new kernel had released that KP'd 3rd gen Intel laptop CPUs (believe it was 5.8, don't quote me on that). It was fixed within hours.
Ever since that incident I've always kept an LTS kernel as backup.

[somesalmon]

After I updated my kernel to this version on gentoo I had noticed a couple days later that this version was removed and I had no idea why. Thankfully my hardware wasn't affected but I was curious why, thanks for the update :) I upgraded to the 6.0.0 kernel a little bit ago anyway but it's interesting stuff

[excidium]

Speaking of display bugs, I had some serious ones on my 17'' Samsung CRT some years ago. One day I sat down to use the computer and there was a weird chemical smell coming from the monitor. I lifted it and there was like half an ant colony under its base, with eggs and everything. I figure they were moving to another anthill and stopped there for the night because it was cozy and warm.

[KinHallen]

The october arch iso is also using the faulty kernel as well, avoid it if using an Intel laptop.

[Aura_Mancer]

This is why I use the lts version of the kernel. If I ever encounter a need to use the non-lts version, I'll switch, but for now it seems I'll stay in lts. I like to provide bug reports and all, but I can't exactly have the kernel be an issue in a machine I use for studying

[LetrixAR]

Now that you mentioned misconfigured X settings at the start:
A few days ago, I configured a dummy display for X that I could use in VNC or RDP so I could connect from a VM that was made with Single GPU passthrough, meaning that there was no display session. It didn't work so I stopped trying and continued my day.
Next day, I went to turn on my PC just to find out that nothing was being displayed, and what made this more scary, was that rebooting my PC wouldn't turn it back on and the only way to do it, was by unplugging it for a few minutes and then it would turn on again.
I ended up booting into live Arch, deleting that dummy display and everything was back to normal.

Something similar happend when I did a Hackintosh. If I restarted my PC from macOS, it would not turn on unless I unplugged it and waited for a few minutes to try again.

[somethingelse]

I have the framework 11th gen laptop (i5) and noticed it after an update with Fedora.
Immediately reverted the Kernel and it fixed itself. Gonna keep the Kernel locked for the time being and update sometime in the near future...if I remember lol

[patiencedvrx]

It wasn't just 12th gen. My 11th gen laptop did this too on Fedora. I had to run 5.19.11 to fix it as well.

[jeremyandrews]

Being an Arch user is pretty much being a "canary in the coal mine" for every other Linux user.

[tranthien]

Nice. Just updated to 5.19.14 after a random flicker on my Intel laptop, thanks for the info.

[unfa]

Arch users - testing catastrophic updates so you don't have to.

I use Arch btw.

[StarsOfPleiades]

Some warning for people who wants to test OpenMandriva Rome (their rolling release branch) because the Gold Candidate ISO shipped with the kernel version 5.19.12.

The solution is use the Silver Candidate then just update the system to install the 6.0.0 kernel.

[llpolluxll]

I'm losing it with the random "RIP INTEL" on the whiteboard behind you.

[DominikZogg]

11gen was also broken, display get off on lock and could not recover (reset needed), no issue with .11 or .13 (fedora, HP Elitebook 830 G8)

[viktoras]

Yep, I noticed it straight away on Fedora and my Lenovo T14 Gen3 - I hope they sort the CPU scheduler soon, this thing is running hot and drains the battery in 30 - 40 min at the moment

[TheEzemikedirnt]

My father has Arch on an Asus laptop, he ran out of bluetooth and I could never solve it for him.
A few months ago one of the latest kernel left him unable to use the keyboard.
With reverting to a previous kernel he was back to normal.
It is incredible how these things happen more often with Asus and lenovo that with others,
I have an Acer aspire I never had a problem

[kdcadet]

This sort of thing is why I don't include the testing keyword for my kernels (I'm on Gentoo). My hardware is relatively new, but I have realized I don't need testing branch kernels and the potential headaches that come with that. I'm still on 5.15 and quite content to wait until the next LTS kernel release.