GPD Win Max 2 2024 version, -AMD8840U iommu error dom0

User Support Hardware Issues
1

Before I ask here, I searched on GitHub regarding the same issues and I found an issue that has been solved already so it is not very useful.
This is my first time installing qubes so take it into consideration.
My issue is that when I try to install Qubes I get this:

    9 1234567(XEN) Xen call trace:↴
    8 (XEN)    [<ffff82d0403adff8>] R amd_iommu_prepare+0x288/0x390↴
    7 (XEN)    [<ffff82d0403ae119>] S amd_iommu_init+0x19/0x3c0↴
    6 (XEN)    [<ffff82d0403ae746>] S pci_amd_iommu.c#iov_detect+0x26/0x70↴
    5 (XEN)    [<ffff82d0403b24ac>] S iommu_setup+0x3c/0x230↴
    4 (XEN)    [<ffff82d0403d3562>] S __start_xen+0x1672/0x264a↴
    3 (XEN)    [<ffff82d040275724>] S __high_start+0x94/0xa0↴
    2 Panic on CPU0:↴
    1 Xen BUG at drivers/passthrough /and/iommu_init.c:1386↴

I don’t know how to actually get the complete log as it just reboots after 5 seconds and when I tried to check the grub.cfg by mounting on another linux machine and checking it I get this:

nvim /media/EFI/BOOT/grub.cfg
set default="1"

function load_video {
  insmod efi_gop
  insmod efi_uga
  insmod video_bochs
  insmod video_cirrus
  insmod all_video
}

load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod part_msdos
insmod ext2
insmod chain

set timeout=60
### END /etc/grub.d/00_header ###
.
.
.
menuentry 'Install Qubes OS R4.2.3 using kernel-latest (6.10.10-1.qubes.fc37)' --class qubes --class gnu-linux --class gnu --class os {
    multiboot2 /images/pxeboot/xen.gz console=none
    module2 /images/pxeboot/vmlinuz-6.10.10-1.qubes.fc37 inst.repo=hd:LABEL=QUBES-R4-2-3-X86-64 plymouth.ignore-serial-consoles quiet
    module2 /images/pxeboot/initrd-6.10.10-1.qubes.fc37.img
}
2

Did you enable IOMMU in BIOS?

3

Check your iso hash, reburn the ISO to usb. Try again. Also try with a second usb drive. Confirm the chipset of the model you got. List the version of the firmware you have since there’s an updated version. This is likely not a firmware issue and I got it to install without any bios modifications.

4

Yes, when I disabled though I managed to arrive to a point to install Qubes but ofc it says to not proceed if you are not a developer etc.

5

I have checked the ISO and it is the same as in DIGESTS.
I can try another usb and I will update here with the chipset etc.

6

What CPU do you have? AMD Ryzen 7 8840U or AMD Ryzen 5 8640U?

Maybe the same issue as here:

7

I just rechecked the ISO in the usb and it has a different digest today.
output:

➜ sudo dd if=/dev/sdc bs=1M count=$(stat -c %s ./Qubes-R4.2.3-x86_64.iso) iflag=count_bytes | sha256sum
[sudo] password for theimiz:
6590+1 records in
6590+1 records out
6910355456 bytes (6,9 GB, 6,4 GiB) copied, 316,731 s, 21,8 MB/s
7387b0eb4e7aea598becedf28f20989864ee1898d9d6defeadf223afd2a91b48  -

The correct should be:

ba904df79a70b334a2ce40ee27105316 *Qubes-R4.2.3-x86_64.iso
b879f101957cd757b90a4a9414d691f1a1df7edb *Qubes-R4.2.3-x86_64.iso
46a0dce03b72d8c222dc28c8bd164f4f37bc9c6ce2d66a266c9a064733ba2690 *Qubes-R4.2.3-x86_64.iso

Is this possible? how can it change from one day to the other, after trying to boot?

8

Did you connect this USB when you were in Windows?

9

Yes as at first the FN + F7 wasn’t working and it booted to windows.
Then I managed to find that it needs only F7 to go in bios

10

Then it’s expected:

11

So I have tried to reburn the usb, checked it with DIGESTs and is the same.
I used another usb too, burn it, correct digest.

Nothing changed still same error.
Regarding firmware:

Bios 0.41
Proc: AMD Ryzen 7 8840U w/ Radeon 780 Graphics
Speed 33.3 Ghz

What else from firmware info is needed?

12

How can I change the grub.cfg to not reboot after 5 seconds on the verbose option?
I prefer to do it directly on the usb from another linux device, before I put it in the GPD.
This is not very helpful: Autostart troubleshooting | Qubes OS

13

Try to add panic=0 kernel command line option and noreboot=1 Xen command line option:

14

Thanks at least now I am at the same as before.
the x2apic-mode=mixed is added at the same options too?

15

Not sure what do you mean by this.

16

like

multiboot2 line panic=0 noreboot=1  x2apic-mode=mixed

Or does it go elsewhere?

17

Add noreboot=1 at the end of the line starting with multiboot2.
Add panic=0 at the end of the first line starting with module2.

1 Like
18

I have no idea why this occurs.

I know when I first got the device, I never ran Windows.

I don’t know if I even did anything in the bios. I probably set the date and time. There are IOMMU settings, you want those on, you want virtualization settings on. Some of them may be set to “auto” and I changed them to just on because I use virtualization so much that I figured it should just be on and don’t give the bios a choice. I didn’t go into the complex settings in Alt + F5 and wouldn’t do this prior to installation. I also completely wiped Windows using a live linux USB using gnome-disks and rewrote the data with 0s multiple times because I hate Windows so much.

Let me know if you get it to work somehow.

Is Secure Boot still on? You mentioned using Windows. I never ran Windows on the device so as to avoid tainting it with Microsoft. I probably turned Secure Boot off if it was on to begin with.

19

What CPU do you have? AMD Ryzen 7 8840U or AMD Ryzen 5 8640U?

20

8840