No display at all after starting to boot machine

User Support General
1

Hello all

I really hope someone can help me cos this is a bit serious.

I just got in, put my qubes machine on and selected the boot menu to get into qubes. I get the graphics there so I can tell from that there is no issue with my display equipment. After I choose the qubes os from the menu it just goes.to a black screen, no dialogue box to decrypt my hard disk or anything.

If I put the type the key in the disk drive light shows activity.and I can hear the drive working but there is nothing on the screen.

Would really appreciate help as I use this machine for work.

Thanks in advance

1 Like
2

Update
I managed to get in by going to the advanced options on the boot menu and selecting a previous version of the hypervisor.

It would be nice if it just worked like it did prior to the latest dom0 update, which I remember I updated last night, any workarounds or commands I need to run? Now I’m able to interact with my system I can give more technical info

1 Like
3

What’s the Xen and kernel version that works for you and that’s not working for you?
Maybe you can try to remove the kernel that is not working for you and update the dom0 again so it’ll be reinstalled in case there was an issue during the installation.

1 Like
4

Have the same issue on 2 machines, last kernel works fine.
Another 2 machines boot but still get a black screen after they enter xscreensaver…

Pretty sure something in last latest update is broken.

1 Like
5

Try to switch to another TTY using Ctrl+Alt+F2 and if you see the console then try to login and check the logs to see what is failing.

1 Like
6

What is the machine hardware (CPU/GPU)?
I’ve been experiencing this since kernel 6.10.7 (6.10.6 and earlier works), same for the 6.6 series starting with 6.6.48.

1 Like
7

Didn’t try that. Will just use the older kernel until the next update. Will do some debugging if that’s also broken

1 Like
8

All systems are Zen 1-3
The 2 system that’t don’t boot have gtx 1060/70
The 2 system that boot have a rx5000/ APU

1 Like
9

I also have a GTX 1070.

It has probably been fixed upstream with this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=46040ea8a6a58e5645d91ffa3ead7ed8fd633d56

nouveau:

  • fix GP10x regression on boot

The next kernel release should include it.

3 Likes
10

any fix for this? or should i manually do something here?

11

This fix should be present in the kernel-latest 6.11:
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.11

Try to install kernel-latest in dom0 and boot with it.

12

It’s still not fixed, unfortunately.
I’ve been building my kernels with the buggy commit reverted and have never had a problem since. For normal users, I guess keeping the latest working kernel is the only solution, unless a revert patch is added to the Qubes kernel repository until it is properly fixed (@marmarek).

13

Did kernel 6.11.2 not work for you as well?
Based on the changelog the fix should be present there.

14

I’ve tried every stable release since 6.10.7, it never worked for me unless I reverted the original buggy commit. I tried booting the latest kernel available in the qubes repo (6.11.6) today and still get the same thing. I’m currently on 6.11.7 with the reverted commit and it works fine.

1 Like
15

linux kernel 6.6.54 and 6.6.48 still cause the same issues. 6.6.42 is the only one that works now.

if the next kernel upgrade doesnt fix this and i chose to go ahead with the upgrade, my qubes will no longer be accessible (the last 3 kernels are only available in the grub menu)

I wouldnt have thought it would take this long to fix :frowning:

I have not been able to use my GPU at all since the 6.6.48

16