[r4.3rc1] I dont see qubes Q screen at grub boot time

User Support General
1

I don’t see graphic background (disk password screen) when I try to boot with any kernels above 5.12+
It feel like something with graphic initialization somewhere around grub. Anything changed?

Because of this I can not boot with this fresh kernels. Today, tried with kernel-latest and it fill the same. I don’t see graphic and system can not boot and stop at the step of plymough-wait…

I can swith (Alt+F*) consoles.

2

Did you try to click on F1 when you see the disk password screen?

3

Nothing changed.
And at the end of boot proccess I see
lightdm
and
plymought-quit-wait (stuck here)

at other console: status of lightdm service (active)

When I try to sudo lightdm I get `Failed to use bus name org.fredesktop.DisplayManager, do you have appropriate permissions?

But again… lightdm (seems) already loaded, but I do not see image… the same as I don’t see it at disk password screen…

4

Did you mean kernel 6.12+ and not 5.12+?
Maybe it’s a hardware-specific issue that is not related to Qubes OS. Try to boot Fedora Live with the same kernel version that is not working in Qubes OS.

5

yes, sorry 6.12 is ok
6.15+ problematic…

6

any chance to fix this until release?
all last kernel have issues with graphic. It’s is stack at plymough-wait

7

Since it’s getting stuck on plymouth, have you tried disabling it? You can do it by adding rd.plymouth=0 plymouth.enable=0 to kernel parameters in grub before booting

You could also make console verbose by removing the quiet parameter while at it, just in case.

8

@otter2 almost the same. without quiet I don’t see any error and with plymouth disable system stop loading at some point. I can switch tty terminals, but graphical env. don’t load.

Something with gui init (from the point when system should show Q image with password request)

9

Can you log in the tty? If yes than it’s great! You can start troubleshooting by reading logs with journalctl

10

yes, i can. But I don’t see anything at the logs… It’s something at grub I think… when first graphic initialization done. @otter2

11

Just an idea: Do you have 2 graphics outputs?

I have one computer where grub and text consoles are on first GPU, but GUI login is on the other. If it is a laptop, then maybe a hot key can switch to the other output - like internal/ external monitor. Maybe even one card has multiple ports.

Some notes:

  • If you see ctrl-alt-f2, ctrl-alt-f3 login, then grub has finished and the Dom0 kernel is running. Did you change any grub kernel parameters, except for taking away quiet and Plymouth?
  • If ctrl-alt-f1 is black then maybe there is another GPU with the graphics, or no graphics.
  • If you see lightdm is started, and no error, then Xorg has started. You can look in /var/log/Xorg.0.log - normally there are details of the driver and device it is using.
  • xrandr -q can show the outputs used. If you use it in tty, then maybe you need DISPLAY=:0 xrandr -q or use the --display argument (I forgot exactly…)
  • man xrandr will explain how to switch outputs.
  • There could also be graphics driver problems…
  • If you find your hardware in the HCL, then maybe someone reported the same problem. We cannot give a lot of help if we do not know such details as motherboard and GPU…
1 Like
12

@phceac Yes, I have nvidia and intel gpu on this notebook.

possible…

This is my efi grub2 config
module2 /vmlinuz-6.17.5-100.fc41.x86_64 placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-2a1a2858-194e-469d-8c80-2c04ad07e3e7 rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles rd.driver.pre=btrfs rhgb quiet nouveau.modeset=0 rd.driver.blacklist=nouveau rd.qubes.hide_all_usb

This is what I found in boot.log

        Starting .[0;1;39mqubes-vm@sys-whonix.service.[0m - Start Qubes VM sys-whonix...

         Starting .[0;1;39msystemd-user-sessions.service.[0m - Permit User Sessions...

[.[0;32m  OK  .[0m] Finished .[0;1;39msystemd-user-sessions.service.[0m - Permit User Sessions.

[.[0;32m  OK  .[0m] Started .[0;1;39mcrond.service.[0m - Command Scheduler.

         Starting .[0;1;39mlightdm.service.[0m - Light Display Manager...

         Starting .[0;1;39mplymouth-quit-wait.service.[0m - Hold until boot process finishes up...

 1Help      2UnWrap    3Quit       4Hex        5Goto       6          7Search     8Raw        9Format    10Quit

And at the same time Xorg logs are very limited. I see only logs for 6.12 kernel (my last working kernel) and no longs for new kernels. I will try on next boot with 6.15+ kernels to look here also.
So, not sure that Xorg started.

13

I had the same issue with 4.2.x.

You can try a flight without sight:

Wait a few seconds after starting to boot from grub: Mostly about 10s were enough.

Then type your disk password and it will start.

You shouldn’t give the wrong password. I often was lost thereafter and had to do a reboot by power button.