wrong resolution during boot

[cryptix]

Qubes OS version

R3.1 and R3.2-rc3

---

Expected behavior:

Readable boot messages.

Actual behavior:

The text is readable in the bootloader menu and for a second when the XEN EFI LOADER... does its thing.. than it switches to this:

Steps to reproduce the behavior:

Use a Lenovo x220 and try to boot one of the .iso's. I tried the verbose mode and various kernel flags like nomodeset, vga=ask and other fixed values for resolutions that should work but none of them seem to take effect.

(edit: system info link to thinkwiki.org)

[cryptix]

I will test if this also happens through the external monitor connection later this week.

Any other ideas?

[cryptix]

I will test if this also happens through the external monitor connection later this week.

Any other ideas?

[alorgill]

Issue persists on my X220 Qubes version 3.2

[alorgill]

Issue persists on my X220 Qubes version 3.2

[cryptix]

#1771 makes me think that some people are able to use qubes on their x2**?

I wasn't able to get into the installer yet. Also tried on a friends x220, same problem. We also tried attaching an external monitor over VGA. Same problem.

[cryptix]

#1771 makes me think that some people are able to use qubes on their x2**?

I wasn't able to get into the installer yet. Also tried on a friends x220, same problem. We also tried attaching an external monitor over VGA. Same problem.

[cryptix]

I just tried 3.2 and now it works for me...

[cryptix]

I just tried 3.2 and now it works for me...

[andrewdavidwong]

Thanks, @cryptix. Is it still occurring for you, @alorgill?

[andrewdavidwong]

Thanks, @cryptix. Is it still occurring for you, @alorgill?

[DrWhax]

I had this same issue on an x201, which was related to VT-d, which wasn't playing nicely with the installer. Disabling VT-d for the installer and after installation re-enabling VT-d worked fine for me.

[DrWhax]

I had this same issue on an x201, which was related to VT-d, which wasn't playing nicely with the installer. Disabling VT-d for the installer and after installation re-enabling VT-d worked fine for me.

[jaja654]

I also had the same issue on a ThinkPad T410 with Qubes 3.2, and good news, there is a solution!

After hours of duckduckgo-ing I found out that indeed, if I turn off VT-d in the BIOS, I can see the installer. But having that security feature is a must, so don't do that, instead simply add iommu=no-igfx to the end of your XEN boot command line in GRUB. Again, not the linux kernel command line, but the XEN command line. This turns off iommu only for the graphic card, but that's not a big deal, it is connected to the trusted dom0 anyway. (Or that's what I read.)

So in the GRUB menu press e or <tab> while the counter goes down, you are now in edit mode. Go down to the XEN command line, module /xen-something.gz blabla console=none blabla and add iommu=no-igfx to the end (separated by a <space>). It should be a couple lines above the kernel line (module /vmlinuz blabla). Press <control>-x to boot.

After install you have to add this to GRUB permanently. From dom0 terminal:
run sudo nano /etc/default/grub
add iommu=no-igfx into the GRUB_CMDLINE_XEN_DEFAULT="..." statement (between the " marks).
run sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Reboot to check.

Perhaps this info could be added to some official Qubes install documentation, seems to be a common problem with the intel graphics solution of the era. (Still very usable machines with VT-x, VT-d, TPM, TXT, ...)

[jaja654]

I also had the same issue on a ThinkPad T410 with Qubes 3.2, and good news, there is a solution!

After hours of duckduckgo-ing I found out that indeed, if I turn off VT-d in the BIOS, I can see the installer. But having that security feature is a must, so don't do that, instead simply add iommu=no-igfx to the end of your XEN boot command line in GRUB. Again, not the linux kernel command line, but the XEN command line. This turns off iommu only for the graphic card, but that's not a big deal, it is connected to the trusted dom0 anyway. (Or that's what I read.)

So in the GRUB menu press e or <tab> while the counter goes down, you are now in edit mode. Go down to the XEN command line, module /xen-something.gz blabla console=none blabla and add iommu=no-igfx to the end (separated by a <space>). It should be a couple lines above the kernel line (module /vmlinuz blabla). Press <control>-x to boot.

After install you have to add this to GRUB permanently. From dom0 terminal:
run sudo nano /etc/default/grub
add iommu=no-igfx into the GRUB_CMDLINE_XEN_DEFAULT="..." statement (between the " marks).
run sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Reboot to check.

Perhaps this info could be added to some official Qubes install documentation, seems to be a common problem with the intel graphics solution of the era. (Still very usable machines with VT-x, VT-d, TPM, TXT, ...)

[jaja654]

Also for future reference my VGA from lspci:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
and it is an "Intel Corporation 5 Series/3400 Series Chipset".

[jaja654]

Also for future reference my VGA from lspci:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
and it is an "Intel Corporation 5 Series/3400 Series Chipset".

[andrewdavidwong]

Perhaps this info could be added to some official Qubes install documentation

Please feel free to submit a PR.

[andrewdavidwong]

Perhaps this info could be added to some official Qubes install documentation

Please feel free to submit a PR.

[jaja654]

Will do, once I figure out how to get it working with anti evil maid.
Booting with tboot I get a different kind of graphic glitch, vertical lines. Pressing esc to go to text console works however, so I see the secret unsealing works. Too bad it messes up graphics.

[jaja654]

Will do, once I figure out how to get it working with anti evil maid.
Booting with tboot I get a different kind of graphic glitch, vertical lines. Pressing esc to go to text console works however, so I see the secret unsealing works. Too bad it messes up graphics.