Bug #2816

cannot boot with linux-libre kernel 5.7.2-1 and cryptsetup

nona - 16 days ago - . Updated 10 days ago.

% Done:




I have cryptsetup when I boot. For a long time, I have not been able to see the prompt to input the password, but I can still boot (it's there, I just don't see it). I upgraded my system yesterday, and when I tried to boot today, I realised that the computer would not boot; it would not move from the blank screen that I regularly see.

I restarted the computer, and added `nomodeset' to the linux-libre kernel line of GRUB. That allowed me to boot, but I cannot log-in to a graphical interface. I restarted again and tried without the `nomodeset' with linux-libre-lts, but I could not boot.

After adding `nomodeset' to the linux-libre kernel again, I downgraded linux-libre to 5.6.12-1 and was able to boot in my regular and unorthodox method (blank screen, type in my cryptsetup password blindly).

I don't know what information is required, but I have an AMD Ryzen 2500 which comes embedded with a Vega 8 graphics card. My kernel line is

linux    /vmlinuz-linux-libre-lts root=<<my-root>> rw  cryptdevice=<<my-device>> resume=<<my-resume>> spec_store_bypass_disable=on quiet splash fbcon=font:TER16x32

the specs from lspci for my Grahpics card are

[AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd]

the specs for my cpu from lscpu are

AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca



Updated by bill-auger 12 days ago

  • Assignee set to Megver83

Updated by bill-auger 12 days ago

this looks to me pretty much of a duplicate of #1750 which was posted two years ago by the same person - that one is still open marked: 'info-needed'

nona -

is this essentially the same problem as #1750? - is it the same ryzen computer? - if so, we should close this ticket and continue the discussion with #1750 - otherwise, you noted in #1750 that the original problem was fixed, so maybe this is a different problem, and #1750 should be closed instead


Updated by nona 11 days ago

No, bill, it's not the same issue. It is the same computer. The behaviour now is that the system does NOT take my password unless I downgrade. As I mentioned:

...For a long time, I have not been able to see the prompt to input the password, but I can still boot...

About bug #1750, I still don't know why it is still marked as info needed, if I already provided everything which was requested, and nobody has asked me for more. I guessed it was not a priority.



Updated by Megver83 11 days ago

do you have the same problem without cryptsetup?


Updated by nona 11 days ago

  1. This only happens after I install linux-libre 5.7.2-1-x86_64
  2. I can boot with `nomodeset' with linux-libre 5.7.2-1-x86_64
  3. I can go back to 5.6.12-1.x86_64 or linux-libre-lts 5.4.41-1_x86_64
    I guess that the answer is yes.

My whole disk is encrypted. I hope that there is a way to test this without uninstalling my whole system (including my personal files and configuration).


Updated by bill-auger 11 days ago

the first thing i would try is to remove "quiet splash fbcon=font:TER16x32" from the grub command - that may reveal some information, either with or without nomodeset

i have seen it suggested, that if some laptops have a black screen while booting, you can shine a flashlight on the screen and you may see that the display is actually working but the backlight is off


Updated by nona 11 days ago

Hi, bill.

  1. Removing `quiet splash' shows some messages before the rest of the messages are suppressed.
  2. With `nomodeset' I see the whole list of messages in the boot process
  3. `fbcon=fontÑTER16x32' makes no difference except in the font size
  4. Leaving the kernel line as it is with 5.6.12-1-x86_64 and 5.7.2-1-x86_64, I know that the screen is on (backlight is not interfering in any way)
  5. It seems that 5.7.2-1-x86_64 disables my keyboard
    1. If I install 5.6.12-1-x86_64, I can hit [CTRL] + [ALT] + [DEL] to restart the computer
    2. with 5.7.2-1-x86_64, [CTRL] + [ALT] + [DEL] does nothing
  6. As in #1750, I can still see (without `quiet splash' or with `nomodeset') the message
    AMD-Vi: Unable to read/write to IOMMU perf count



Updated by bill-auger 10 days ago

On Sat, 27 Jun 2020 15:01:27 +0000 wrote:

It seems that 5.7.2-1-x86_64
disables my keyboard

when i rebooted a few moments ago, kernel 5.7.2-gnu-1, my
keyboard was not working either - even the caps-lock key
would not toggle the LED

i have two keyboards and im not sure if that made any
difference; i did not try the other one at first - i
waited at the login prompt for about a minute, then i
pressed a key on the other keyboard, then they were
both working


Updated by nona 10 days ago

That is super interesting. I currently do not have an external keyboard, but seems like a step forward. Let me know if I can help :) . May be if I play around with the `mkinitcpio.conf' hooks? I have these right now:

HOOKS=("base" "udev" "keyboard" "keymap" "autodetect" "modconf" "block" "consolefont" "encrypt" "lvm2" "resume" "filesystems" "fsck" "shutdown")


Updated by bill-auger 10 days ago

do you have a USB wifi or anything else plugged in? - i also
noticed that the USB wifi thingy would not activate - i had to
unplug it and plug it in again to get the system to recognize

i dont know that there is any good suggestion in that - just
a clue perhaps - maybe just try booting with nothing extra
plugged in, and wait 5 minutes before trying to log in - just to
see if it maybe will accept the keyboard input eventually


Updated by nona 10 days ago

Nope, nothing is plugged in. I tried the hint about the 5 minutes, but still nothing. Thanks.

Also available in: Atom PDF