PSA: don't upgrade to linux kernel 5.19.12

Has anyone reported this to Framework or seen that they are aware of the issue?

1 Like

Wrong tree.

1 Like

The fc37 just denotes that it was build for Fedora 37. The 300 is the package version which is the version of the actual packaged RPM. Usually if there is the change to the packaging done by the packager and not the sources the package version is incremented so that the updated package will propagate. Apparently for the kernel, things are slightly different. See this reddit post for an explanation.

What does “Wrong tree.” mean? Framework has a good working relationship with Fedora. I’m asking if there is any chance of continued collaboration on this issue.

1 Like

The bug’s reportedly already fixed in 6.0, so it’s really just a waiting game. FWIW people on laptops that aren’t from Framework are also having this problem, so this isn’t something special to Framework, but a bug introduced in the Intel graphics drivers.


Can confirm, just compiled 6.0 of the Clear Linux kernel and it’s working fine on my Arch install.


DO NOT USE 5.19.12.

Intel devs are saying it can potentially damage lcd panels:

After looking at some logs we do end up with potentially bogus
panel power sequencing delays, which may harm the LCD panel.

The patches are being reverted and a new stable release will be out soon.


Also to confirm, I was running the 6.0rc7 linux-mainline on Arch w/o a problem and I’m now updated to the official 6.0 release w/o any issues as well.

Linux 5.19.13 is out, and I can confirm it’s working fine.


@Jake_Bailey I don’t see it, but I assume it’ll show up soon.

1 Like

Whooooooo boy. This just bit me on F36.

To quickly recover:

Hold the power button down to turn the unit off, then turn it back on. You have to be quick and catch the GRUB boot loader. The default (naughty) kernel will be up top (in this case 5.19.12-200.fc36 on a F36 system). You want to down arrow one time to get to the previous kernel (5.19.11-200.fc36 for me), and hit enter. Your system will boot like normal. Now the trick is going to be making your previous kernel the default for a while. It’s actually not too bad.

Log into your system, open up a terminal and type:

sudo grubby --default-index

It should return 0 on a normal day. We’re going for abnormal. Let’s get a list of kernels!

sudo grubby --info=ALL

You’ll get some output. Notice that the most recently installed kernel is most likely index=0, and the previous one is most likely index=1. We’re going to tell it to use index=1 by default.

sudo grubby --set-default-index=1

It will tell you the new default is /boot/loader/entries/someweirdguid-5.19.11-200(more kernel version barf, etc.) with index 1…

After that you should be able to reboot without worrying about that pesky 5.19.12 business… At least until the next kernel update. :slight_smile: I hope this helps someone who stumbles upon this topic in a panic. These situations can be pretty scary for folks the first time it happens to them.


Hello there.

Any chance you could check if systemctl hibernation resumes without a black screen on your side ?
I would really appreciate it.

Thanks Aggraxis for this info.

After thinking the problem wasn’t showing up in the Fedora 37 beta with kernel 5.19.12 (as in my previous post), the screen started to flicker on power off, which then took about 30 seconds. So it’s now reverted to 5.19.11-300.fc37 for the moment.

But /dev won’t have been mounted and pacman downgrade would fail.

as @5uie1 said, Runlevel 3 (multi-user mode with networking) and black listing i915 module works as intended.

# linux   /vmlinuz-linux root=UUID=[some-random-uuid] rw  loglevel=3
// after
linux   /vmlinuz-linux root=UUID=[some-random-uuid] rw 3 module_blacklist=i915 loglevel=3
1 Like

FYI this was fixed in the 5.19.13 kernel as well: Regression on 5.19.12, display flickering on Framework laptop - Jerry Ling

now closing the loop and self-referencing the thread that was in the email :wink:


Confirming that 5.9.13-arch1-1 is now working. No trouble with the display.


Just got my framework and i was so excited at the first moment. Then i downloaded a fresh arch iso with the 5.19.12 kernel … you can’t imagine how disappointed i was for half a hour, thankfully i found this thread :joy:


:wave: Fedora peeps, 5.19.13 is fully available via standard update. :raised_hands:


Nice, we made it to :smiley:

5.19.14 has just dropped too.

1 Like

I just got the update for 5.19.13 in Fedora 36, and it automatically it set my default-index back to 0 during installation.

1 Like