Qubes 4.3 rc3 : graphical problem at first boot after installation (no configuration process possible)

[intoqubes]

Hi folks,

I’m stuck in the (post)installation of Qubes 4.3 rc3.
Installation brought no errors, installer told me to reboot.
The problem arises then, at booting the first time on the fresh install, before the configuration process. The screen is totally unusable, as on the picture.

I aldready browsed the topics here and on a search engine, but found nothing. As I’m not very skilled in linux, I don’t know what to do to identify the problem, and so I need your help.

Some infos:

• I aldready had Qubes 4.2.4 running on this computer (I removed it and cleaned the SSD before trying to install 4.3rc3)
• installation on the internal SSD 512Go NVMe
• Qubes Iso double checked (signatures, hashes…), copied on a USB key via 2 methods : Gnome Disks (restore disk image) ; dd as stated in the Qubes documentation ; both brings the same problem
• USB medium checked at start up, before installing ; no errors (or didn’t I had time to see them ?)

I’ll send any other needed info. Please just tell me which commands to run for getting them, or which logs to send (and where to find them).
For the moment, I had to install another OS for working on the computer. I will try again installing Qubes as soon as I have some advice.

So, how can I do to get Qubes 4.3 working ?

Thanks !

[KitsuneNoBaka]

nVidia?

[intoqubes]

No, I don’t think so

Machine:
  Type: Laptop System: HP product: Victus by HP Gaming Laptop 15-fb0xxx

CPU:
  Info: model: AMD Ryzen 5 5600H with Radeon Graphics bits: 64

Graphics:
  Device-1: AMD Navi 24 [Radeon RX 6400/6500 XT/6500M] vendor: Hewlett-Packard 
  Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series] vendor: Hewlett-Packard
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: eDP-1 mapped: eDP model: ChiMei InnoLux
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Graphics (renoir LLVM 15.0.6 DRM 3.49
    6.1.0-40-amd64) direct-render: Yes

Boot Mode: UEFI

[KitsuneNoBaka]

qvm-pci ls dom0

and check Cezanne PCI address

then block this address in grub, like in this thread:

Create a Gaming HVM

Hardware To have an ‘HVM’ for gaming, you must have A dedicated GPU. By dedicated, it means: it is a secondary GPU, not the GPU used to display dom0. In 2023, ‘Nvidia’ and ‘Amd’ GPU work. Not tested with Intel GPUs. External GPU using thunderbolt work (Create a Gaming HVM - #8 by solene) A lot of patience. GPU passthrough is not trivial, and you will need to spend time debugging. A screen available for the gaming ‘HVM’. (It can be a physical monitor or just to have multiple cables conne…

[edit] changed Navi 24 na Cezanne

PS: I’m wrong - Navi 24 need to be disabled and so searched for

[intoqubes]

Thanks for fast answers, much appreciated

How can I get the adress ? For the moment I run another debian based linux OS (I had to install it for daily work, witing for qubes to run again). Is it possible to have this info after the installation, and before rebooting in the configuration process ?

EDIT : Please forgive me my begginer level, the more precisions I’ll have the better it will be

EDIT 2 : lspci in tha actual OS gives me a lot of cezanne results ; only one starts with VGA compatible : is it this one to block ?

When i’ll have this info confirmed, when to edit the grub ?

[KitsuneNoBaka]

Ok.
Yes. It’s VGA needed but I’ve turned everything out, search for Navi 24 or 6500M, because discrete gpu need to dissabled, not igpu.

sudo nano /etc/default/grub

in line with GRUB_CMDLINE_LINUX at the beginning you need add options.

That’s my line:

GRUB_CMDLINE_LINUX="rd.luks.uuid=luks-9332d67c-72fb-49bc-9a3b-5dc3f6e4db3d rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles 6.6.36-1.qubes.fc37.x86_64 x86_64 rhgb quiet"

add rd.qubes.hide_pci= with your PCI address
that’s what my line looks like after modification (00:1f.6 is my igpu so it would disable every gfx I have, that’s why search for Navi 24):

GRUB_CMDLINE_LINUX="rd.luks.uuid=luks-9332d67c-72fb-49bc-9a3b-5dc3f6e4db3d rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap rd.qubes.hide_pci=00:1f.6 plymouth.ignore-serial-consoles 6.6.36-1.qubes.fc37.x86_64 x86_64 rhgb quiet"

then update grub in uefi

sudo grub2-mkconfig -o /boot/grub2/grub.cfg

[intoqubes]

OK,
It seems this is the line I need :
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] (rev c3)

Big question, as a newbie, before I proceed :

When exactly should I edit the grub file ? Step by step please. I will install Qubes on the internal SSD. I think I will have to edit the file BEFORE restarting (or I will miss the configuration steps, because of the graphic problem), but how can I achieve this ? Should I first type “c” a the first grub prompt after the install (and before the config process) complete the configuration process, and somehow later edit the grub file with sudo nano ?

[KitsuneNoBaka]

Aren’t you’ve checked PCI devices on installed qubesos?

If you have no access to text running OS then you can edit grub temporally.
During boot, when grub will show, hit e - it will put you in the live grub edit.
Edit the line and hit F10 to boot. It will boot with changes.
If this repair your boot, then you need make it permanent.
So in a system open terminal in dom0 and then edit as in my previous post.

[intoqubes]

On previous Qubes 4.2.4 installation, I don’t remember I had to block the Navi 24 device (I’m pretty sure I didn’t had to).

I have a backup of nearly every qubes I had, maybe I can find the previous grub file inside ? (Well, I think dom0 is not backed up, except /home)

I gonna try right now as you said, installing, and then typing e when grub appears.

I

[KitsuneNoBaka]

Hm…
It might be that 4.3 with newer drivers make your hybrid graphics hi-wire.
It might be, since Navi 24 is first VGA, that display output is connected to it, but when dom0 loads then Cezanne is loaded as well by Xorg and magic happens. Or any other way.

[intoqubes]

Hey,

Back with good news, the mods you proposed worked, many thanks for that !
Last question, will I miss this NAvi 2 component (and what is it for ?) or should I let the grub pci-hide as this ?

I’m now facing other problems with sys-usb and USB keys/ssd, I’m going to open a new post.

[KitsuneNoBaka]

It’s discrete gpu.
For normal operations, especially in desktop you have no use for that.
You might try to do HVM qube and pass it to that qube to check if you use it for gaming or LLM.
I’ve posted you a guide for that - Qubes 4.3 rc3 : graphical problem at first boot after installation (no configuration process possible) - #4 by KitsuneNoBaka

[intoqubes]

ok, that’s not my goal, I think I gonna let it as this

thanks for the help !

(and if ever you have little more time, here is where I asked for USB troubles : Problems with sys-usb, affecting usb keys/ssd in appVM on a fresh updated 4.3rc3 install )