Re: [qubes-users] Bootloop

[awokd]

keylogger...@gmail.com:
> Bootloop on AMD 1950x,titanx maxwell after entering fde password.
>
If it only started when you updated the kernel, set the default back to
the prior version in xen.cfg or grub.cfg.

[awokd]

keylogger...@gmail.com wrote on 6/2/19 9:39 AM:
> If I dont use fde during install it works fine and boots to the config qubes.
>
There is or was a bug with the FDE password not working right if
selecting a non-US keyboard as part of the install. When you say
bootloop, what happens after entering the password? Try leaving the
keyboard on the default for the install.

[awokd]

keylogger...@gmail.com wrote on 6/2/19 1:52 PM:
> It would do nothing after entering the correct password when typed in us layout. It still had the password screen and the progression bar would still move but once it reached the end it would be stuck their and gave no errors on the console. Just that Plymouth starting and then staring cyptosetup for luk device Id.
>
It behaves the same way if you enter a wrong password. Try entering it 3
times. If you still want to test, maybe try a very simple encryption
password. If possible, also let the installer automatically configure
your partition layout. I don't know of an easy way to view logs at that
point in the boot process.

[Sphere]

That's not a bootloop, it's simply that you are stuck at the phase where you have to unlock the drive's encryption

If you can't get past that then maybe there's a problem with your keyboard? Reinstall qubes and put an easy/short encryption pass first then maybe the problem resides with your keyboard.

I've never encountered this problem before the feedback I can give is pretty limited but I stick with the usual default keyboard layout.