[RESOLVED] Dots-as-you-type not working on LUKS screen

Framework Laptop 13 Linux
1

OS: Fedora Linux 43 (Workstation Edition) x86_64
Host: Laptop 13 (AMD Ryzen AI 300 Series) (A5)
Kernel: Linux 6.17.8-300.fc43.x86_64
BIOS VER: 03.04

  1. Laptop slowed to a crawl
  2. Before it completely locked up, I was able to check top CPU PIDs and one of them was firmware updater
  3. Then the laptop completely froze, so I tried REISUB but I don’t think I have SysRq enabled, so I just held down the power button.
  4. After the first reboot, everything worked like normal and I got in the OS and edited some kernel params to enable the SysRq key.
  5. After the next reboot, I was having issues with entering the LUKS key because I thought the machine was frozen, but it turns out that just the screen was frozen and I could still enter input and press enter and it would continue
  6. I also tried using an external USB keyboard, same result.

I think maybe something I did messed with the LUKS screen since I don’t get that visual feedback anymore. I also can’t even hit Esc to switch back to the systemd bootup log. Nothing happens.

Ideas?

2 Likes
2

Yep I have the same issue here, Seems related to the 6.17.8-300.fc43.x86_64 update from yesterday. I can rollback to the previous kernel since I use Fedora Silverblue and that fixes the typing not showing up on the LUKS screen.

1 Like
3

Glad I’m not the only one and that you noticed it from the update as well. Not sure where to submit the bug report for this. Fedora?

1 Like
4

I had a bluetooth issue after an update that I posted both here and on the Fedora community forum. Can’t hurt.

If this is kernel related though, the fix will have to come from the kernel itself though.

5

Just noticed one thing during booting with the kernel update, it throws the following error:

RDSEED32 is broken. Disabling the corresponding CPUID bit.

Not sure if that would be causing the LUKS password screen not refreshing or not but the error doesn’t show up with the old kernel.

EDIT: I get the same error on my Framework Desktop after updating the kernel but the LUKS screen works so I guess this is unrelated.

6

Quick update: This is not limited to Framework machines and it looks like it could be related to a RDSEED bug in AMD cpus after all.

From what I understand (someone with more knowledge than me can jump in and correct me) the mitigation on Silverblue (for example) is:

sudo rpm-ostree kargs --append='clearcpuid=rdseed'

but it doesn’t seem to fix the LUKS screen problem, only prevent the exploit related to the bug I guess.

EDIT: Ok now I think I understand what is going on. Something in the LUKS password screen is relying on RDSEED32. The new kernel tests for the mitigation of the problem that was reported to AMD and because it doesn’t find it (a fix should come around 11/25) is prints the error message and disables the functionality in the CPUID bit which causes the LUKS screen to mis-behave.

So that kernel boot argument is only necessary if you are running an old kernel which doesn’t display this error message and disables the CPUID bit by itself.

7

…and for full disclosure here is the thread on Fedora’s forums discussing this:

2 Likes
8

Thank you, following that thread too now. I did notice that I started seeing that second image in that thread as well.

Since my system is workable right now, I’m just going to wait for a fix.

1 Like
9

I’m also having this issue with the same device.

10

I’m still experiencing this issue on my Framework 13 (AMD AI 300 Series) with Fedora 43 with all software updates applied as of today (Nov. 30th).

I’d just like to add something I hadn’t seen mentioned before or elsewhere. I am able to see the dots on the LUKS screen just fine from an external display (1080p-HDMI) and keyboard. I can also see the update progress animation as expected this way.

The display update issue (frozen screen) seems to only happen with the internal screen and keyboard on the laptop itself.

2 Likes
11

I dodged this issue by loading kernel 6.17.7-300.fc43.x86_64

I’m staying with that one until I have certainty the issue has been resolved.

I got a BIOS update today - not sure what was in it.

1 Like
12

Seems to be fixed on 6.17.9

4 Likes
13

Yep. Fixed for me too with 6.17.9.

I don’t think the AMD microcode has a fix yet but the kernel code that drives the LUKS screen is fixed.

2 Likes
14

Great, fixed for me as well. Looks like it didn’t have anything to do with whatever was making gdm crash on my machine.

Oh well

1 Like
15

Thank you for this thread, have the same issue (error during boot, luks dots not showing up but still taking input)

just started yesterday (ryzen AI 9, Framework 13, aurora immutable fedora). Will poke around fedora thread more

I’m on 6.17.8 kernel and 6.17.9 is reported fix, so i think it’s just waiting bit longer for me