Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wrong resolution during boot #2284

Closed
cryptix opened this issue Aug 31, 2016 · 15 comments
Closed

wrong resolution during boot #2284

cryptix opened this issue Aug 31, 2016 · 15 comments
Labels
C: other hardware support P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@cryptix
Copy link

cryptix commented Aug 31, 2016

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:
share

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)

@andrewdavidwong andrewdavidwong added T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. C: other labels Sep 1, 2016
@andrewdavidwong andrewdavidwong added this to the Release 3.2 milestone Sep 1, 2016
@cryptix
Copy link
Author

cryptix commented Sep 12, 2016

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

Any other ideas?

@alorgill
Copy link

Issue persists on my X220 Qubes version 3.2

@cryptix
Copy link
Author

cryptix commented Jan 7, 2017

#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
Copy link
Author

cryptix commented Jan 8, 2017

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

@andrewdavidwong
Copy link
Member

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

@DrWhax
Copy link

DrWhax commented Jan 13, 2017

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
Copy link

jaja654 commented Mar 10, 2017

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
Copy link

jaja654 commented Mar 10, 2017

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
Copy link
Member

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

Please feel free to submit a PR.

@jaja654
Copy link

jaja654 commented Mar 11, 2017

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.

@ghost
Copy link

ghost commented Aug 28, 2018

I am experiencing exactly same issue with 4.0 installed on ThinkPad X220. Also boot goes black afterward and computer seemes to freeze. I can't read anything with that corrupted fonts.

@andrewdavidwong
Copy link
Member

Moving to 4.0 milestone based on most recent report.

@andrewdavidwong andrewdavidwong added hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. labels Sep 2, 2020
@andrewdavidwong
Copy link
Member

@ofendio, are you still affected by this?

@ghost
Copy link

ghost commented Sep 3, 2020

Hi, it's not current anymore.

@andrewdavidwong
Copy link
Member

Closing this as resolved. If you believe the issue is not yet resolved, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen this. Thank you.

@andrewdavidwong andrewdavidwong removed the needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. label Sep 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: other hardware support P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

6 participants