Hello. The loader bar is at max and nothing is working. I’m very new to all this technical stuff and have no clue what has happened. I’m EXTREMELY appreciative of any help you have to offer - thank you!
Please help. So confused. Thank you!!!
Might you have input the wrong password a few (all the) times? If that’s the case, you system may be waiting for a timeout to expire before dropping into a recovery shell.
(If that happens, it looks scary, don’t panic and reboot. 
)
I really really appreciate your answer Gonzalo.
But that is not it. As the password box then goes away and the loading bar goes all the way. When I input a wrong password the white password box stays. So I know it is not a password issue.
1 Like
Is it a new Qubes OS installation and you’re stuck on loading right afterr the installation was completed or were you able to boot the Qubes OS without this problem before but this started to happen after you did something?
If it worked before then what did you do during your last successful Quebs OS boot that could cause this? (Maybe dom0 update or you’ve changed some configuration in dom0?)
You can try to disable the qubes autostart at boot to boot in dom0 and then try to start the qubes manually and see if the qubes will be able to start successfully:
Your response is appreciated more than you know, I have been extremely confused and stressed. Am I correct in saying that I need to first select “Advanced options for Qubes (with Xen hypervisor)? If so I am unable to select that as my keyboard has no up or down button. (60% keyboard). I am able to go to “UEFI Firmware settings” using the FN and WASD keys, but not to the middle option being Advanced options. Once again thank you so much!
Also, this happened on my first boot. I was never able to fully login and use Qubes.
You don’t need to go to the “Advanced options for Qubes (with Xen hypervisor)", you need to edit the default GRUB boot menu option but to edit it you’ll need the arrow keys.
Does Fn+WASD not work as arrow keys in GRUB menu for you?
1 Like
Once again, I really really appreciate your response - you don’t even know how much it means to me boss. If this works I’m down to send you some crypto for your troubles. Any who, which line should I edit? I’m assuming you mean the “‘e’ to edit the commands before booting” option? If so which option do I edit. Once again, thank you.
Edit the default (e.g. first) GRUB boot option and the line starting with module2.
It’s described in the guide that I linked:
Press the
Ekey on the first prompt (or your custom prompt). Then, press the down arrow key multiple times to reach the line starting withmodule2.
Also , I am unable to go up and down in the GRUB menu, but I am able to go to the end of a line of code. But not up and down.
Does Fn+WASD not work as arrow keys in GRUB menu for you?
No sir they don’t. At least not to go up and down!
Okay thanks, I’m where I need to be but I just can’t go down! Is there some sort of command I can do?
Also if I must, I will just buy a keyboard with up and down arrows - do you recommend that?
Maybe you can try to use Fn + IJKL if Fn + WASD is not working for you.
Or search information about your keyboard model to see which keys are acting as arow keys before OS boot.
If nothing works then I guess you’ll need to get the keyboard with arrow keys.
Do you have access to any keyboard that does have arrow keys? They’re kind of important…
It sounds like GRUB is interpreting those key combinations as Home, End, PgUp and PgDn. Yeah, you either need to remap your keys temporarily on your keyboard (if there’s an option to do so), or use another keyboard, preferably a full-sized one…
What @apparatus means is this:
- You turn your computer on
- As soon as you see the GRUB menu, press E
- You will then see the options for that particular GRUB entry.
- You will need to go down to the really long one (the one containing
vmlinux) and then at the end, put the following text:
rd.qubes.skip_autostart
This will prevent any qubes from starting automatically on boot (which most likely is the cause of your issue).
4a. If you want to be able to see what is happening, go to that same line and delete the words plymouth and quiet. That will show the systemd journal on the screen, providing you with a full log of what’s failing, if anything.
- Once you have done that, press Ctrl + X to boot the machine.
If this still doesn’t get you to the xfce-greeter screen (the user login screen), then let us know, and we will see what to do next…
2 Likes
With some computers, typing in password is twitchy. Can do a repeat of characters, like the key was held down too long.
Do a power-up, click f8, and actually see what the password you have typed in.
Hey! Your response is super appreciated as I really wanna figure this out. So I purchased. A new keyboard and I tried this - “rhgb quiet usbcore.a/uthorized_default=0 qubes.skip_autostart” and unfortunately I’m still stuck in an infinite loading screen.
I tried this and the password is correct, thank you for your response its greatly appreciated