search

QubesOS / qubes-issues

The Qubes OS Project issue tracker
https://www.qubes-os.org/doc/issue-tracking/
541 stars 48 forks source link

Installation media black screen #5165

Closed ravi0lii closed 4 months ago

ravi0lii commented 5 years ago

Qubes OS version Tested with R4.0.1 and R4.0.2-rc1

Affected component(s) or functionality The installer does not work as expected. See the section "Brief summary" for more information.

Brief summary When I boot the ISO, which is flashed on my USB, using UEFI (can't switch it to Legacy), I just get some text and after that a black screen. The last text I get is some information about hardware vulnerabilities and then I get the text: Xen is relinquishing VGA console. After that, my screen gets black from the top to the bottom and nothing happens.

To Reproduce

  1. Flash Qubes R4.0.1 or 4.0.2-rc1
  2. Boot the stick using UEFI boot
  3. Wait a bit until some text appears
  4. After that, the screen turns black. The last text is Xen is relinquishing VGA console.

Expected behavior The installer should start and everything should work fine.

Actual behavior A black screen appears after some text.

Screenshots Screenshot of the text

Additional context My laptop: Acer Spin 5

Solutions you've tried Tried reflashing the stick using dd and etcher with different Qubes verions (4.0.1 and 4.0.2-rc1).

Relevant documentation you've consulted Did not found any relevant stuff on the docs

Related, non-duplicate issues

5074 seems to have a similar problem, but I don't know if this could be related to my problem.

JarrahG commented 5 years ago

I see you've linked the issue I have been having. Let's check whether it's the same thing. Could you edit the BOOTX64.cfg file on your R4.0.2-rc1 ISO to have the following boot line:

[qubes-verbose]
options=console=vga efi=no-rs iommu=no-igfx loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan vga=current,keep guest_loglvl=all
#noexitboot=1
#mapbs=1
kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-20190628-x86_64 i915.alpha_support=1 nouveau.modeset=0 iommu=no-igfx console=hvc0 acpi=off
ramdisk=initrd.img

For information on how to make this edit, see the top of this page: https://www.qubes-os.org/doc/uefi-troubleshooting/ The other information on that page may actually solve your problem, if you haven't attempted it yet.

This should give us the output required to determine whether it's the same thing. But even if it's not, it should tell us more of what the problem is.

ravi0lii commented 5 years ago

I see you've linked the issue I have been having. Let's check whether it's the same thing. Could you edit the BOOTX64.cfg file on your R4.0.2-rc1 ISO to have the following boot line:

[qubes-verbose]
options=console=vga efi=no-rs iommu=no-igfx loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan vga=current,keep guest_loglvl=all
#noexitboot=1
#mapbs=1
kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-20190628-x86_64 i915.alpha_support=1 nouveau.modeset=0 iommu=no-igfx console=hvc0 acpi=off
ramdisk=initrd.img

For information on how to make this edit, see the top of this page: https://www.qubes-os.org/doc/uefi-troubleshooting/ The other information on that page may actually solve your problem, if you haven't attempted it yet.

This should give us the output required to determine whether it's the same thing. But even if it's not, it should tell us more of what the problem is.

So I updated the BOOTX64.cfg according to you, now the following stuff happens:

ravi0lii commented 5 years ago

So actually I was able to get a terminal now. Here's the generated rdsosreport.txt.

marmarek commented 5 years ago

Looks like USB stick isn't properly detected:

[   12.904381] localhost kernel: usb 1-4: new high-speed USB device number 2 using xhci_hcd
[   18.024800] localhost kernel: usb 1-4: device descriptor read/64, error -110
[   33.896433] localhost kernel: usb 1-4: device descriptor read/64, error -110
[   34.120377] localhost kernel: usb 1-4: new high-speed USB device number 3 using xhci_hcd
[   34.236417] localhost kernel: usb 1-4: device descriptor read/64, error -71
[   34.456396] localhost kernel: usb 1-4: device descriptor read/64, error -71
[   34.566437] localhost kernel: usb usb1-port4: attempt power cycle
[   35.194387] localhost kernel: usb 1-4: new high-speed USB device number 4 using xhci_hcd
[   35.196290] localhost kernel: usb 1-4: Device not responding to setup address.
[   35.406538] localhost kernel: usb 1-4: Device not responding to setup address.
[   35.614373] localhost kernel: usb 1-4: device not accepting address 4, error -71
[   35.729395] localhost kernel: usb 1-4: new high-speed USB device number 5 using xhci_hcd
[   35.731261] localhost kernel: usb 1-4: Device not responding to setup address.
[   35.934527] localhost kernel: usb 1-4: Device not responding to setup address.
[   36.142753] localhost kernel: usb 1-4: device not accepting address 5, error -71
[   36.144582] localhost kernel: usb usb1-port4: unable to enumerate USB device

Try a different one...

NewNeonNeo commented 5 years ago

I'm having the same issue... Xen is relinquishing VGA console.

I tried booting from VM and installing directly on my PC. If i disabled EFI in VirtualBox I can boot, and install but obv not everything works without EFI. I've tried v4 R1, R2 and R2 with an updated kernel. Same for V3

After modifying the BOOTX64.cfg file to include all the lines @JarrahG suggested. I'm now seeing much more text . Here is the last information I see before the console starts sending dracut-initqueue[482]: Warning: dracut-initqueue timeout - starting timeout scripts

image

If anyone is able to tell me how to access the error log from emergency mode I will upload them aswell!

marmarek commented 5 years ago

but obv not everything works without EFI

This isn't obvious at all. You should have exactly the same features regardless of EFI or legacy.

in VirtualBox

That's important detail. Qubes within other virtual machine most likely won't be able to utilize hardware virtualization extensions, which are necessary for Qubes 4.x. Look for nested virtualization, if your VirtualBox can do it (AFAIR only some recent version and only on AMD), then should be ok. Otherwise, you'll have more troubles down the line, like sys-net not starting.

The sceenshot suggests issues with USB controller (emulated by virtualbox?). And there is a hint about pci=biosirq kernel option. Try that.

NewNeonNeo commented 5 years ago

but obv not everything works without EFI

This isn't obvious at all. You should have exactly the same features regardless of EFI or legacy.

Well EFI disabled I can install Qubes boot and run , only problem, like you mentioned is sys-net is not starting...

Look for nested virtualization, if your VirtualBox can do it (AFAIR only some recent version and only on AMD), then should be ok. Otherwise, you'll have more troubles down the line, like sys-net not starting.

image

image

It is 3rd gen ryzen 7, in theory it supports Nested virtualization.

The sceenshot suggests issues with USB controller (emulated by virtualbox?). And there is a hint >about pci=biosirq kernel option. Try that.

I get the same output with or without pci=biosirq set. It dosn't recognize the flag is set and keeps telling me to enable it

****UPDATEE

IMG_20191013_235448

With everything I've learned from this thread I tried installing to my laptop again. Notice the line with CPU jitter...I read from here. that adding modprobe.blacklist=nouveau rd.driver.blacklist=nouveau would solve that issue but so far no luck.

[qubes-verbose] options=console=vga efi=no-rs iommu=no-igfx loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan vga=current,keep guest_loglvl=all #noexitboot=1 #mapbs=1 kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-20190811-x86_64 i915.alpha_support=1 modprobe.blacklist=nouveau rd.driver.blacklist=nouveau iommu=no-igfx console=hvc0 acpi=off ramdisk=initrd.img

Kernel looks like this...Any suggestions?

bakchus commented 4 years ago

I've had the same issue. Only problem is that you are using USB sticks bigger than 8GB.. I have created with gparted primary partition with size only 7,5GB, format=fat32 and it works, without editing of config file...

mu2718 commented 4 years ago

Indeed, bakchus solution solved it for me! Thanks!

afzlodhi commented 4 years ago

I need help

I am getting “XEN IS RELINQUISHING VGA CONSOLE” I get blank screen I have tried @JarrahG suggestions and recreated the ISO file for USB. It goes directly to windows I have NVIDIA card on HP i5 machine

ravi0lii commented 4 years ago

I need help

I am getting “XEN IS RELINQUISHING VGA CONSOLE” I get blank screen I have tried @JarrahG suggestions and recreated the ISO file for USB. It goes directly to windows I have NVIDIA card on HP i5 machine

Did you also try every other step in this thread?

andrewdavidwong commented 4 years ago

Please note that qubes-issues is not a help forum. Please address support requests to the qubes-users mailing list instead. Please see our issue reporting guidelines for more information about this. Thank you for your understanding.

lattice0 commented 3 years ago

@bakchus can you give more details? How to do these things on the USB stick and then dd the qubes iso image?

Hello @mu2718? How did you do?

lattice0 commented 3 years ago

neverdmind, I sucessfully created the partition as said and with the right size but the same error persisted

mu2718 commented 3 years ago

Make sure to chose a USB thumb drive smaller or equal to 8GB. Then it worked with 'dd' imaging the iso to the block device. Cheers

Lucas Zanela notifications@github.com schrieb am So., 29. Nov. 2020, 20:24:

neverdmind, I sucessfully created the partition as said and with the right size but the same error persisted

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/QubesOS/qubes-issues/issues/5165#issuecomment-735441869, or unsubscribe https://github.com/notifications/unsubscribe-auth/AL5UNCMUAMHNET3GGNAU3K3SSKNYDANCNFSM4IDCAL4Q .

lattice0 commented 3 years ago

@mu2718 did it but didn't fix the problem for me. Made sure to dd to /dev/...1 not /dev/... but still got the same problem.

mu2718 commented 3 years ago

Hi Lucas, actually I did the opposite and it worked, wrote it to the device, not a partition: sudo dd status=progress if=name-of.iso of=/dev/sdb Hope you are luckier with that.

Am Mo., 30. Nov. 2020 um 21:00 Uhr schrieb Lucas Zanela < notifications@github.com>:

@mu2718 https://github.com/mu2718 did it but didn't fix the problem for me. Made sure to dd to /dev/...1 not /dev/... but still got the same problem.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/QubesOS/qubes-issues/issues/5165#issuecomment-736009651, or unsubscribe https://github.com/notifications/unsubscribe-auth/AL5UNCKATKCTGY5M5RQ55W3SSP2URANCNFSM4IDCAL4Q .

madman708 commented 3 years ago

Hi @mu2718, I created an 7.5GB primary partition of by 32GB USB drive, I flashed qubes os R4.0.4-rc1-x86_64 in ISO9660 through dd as you mentioned, but the problem is still same, If i boot the USB in efi mode i get blank screen after startup in legacy boot it gives me the same error as pane dead.

Let me know what i'm missing here, I'm using ryzen 3700x, RTX 2060 AMP card.

kmfreder1 commented 3 years ago

I had something very similar happen to me on my first attempt at installing Qubes this afternoon. My USB stick is much larger than 8GB. Is this 8GB mentioned in the docs somewhere? I will try again with an 8GB USB. I am pretty eager to give this OS a spin. Sounds pretty awesome.

andrewdavidwong commented 3 years ago

I had something very similar happen to me on my first attempt at installing Qubes this afternoon. My USB stick is much larger than 8GB. Is this 8GB mentioned in the docs somewhere?

Yes, here:

https://www.qubes-os.org/doc/installation-troubleshooting/#trouble-installing-from-usb-stick

kmfreder1 commented 3 years ago

@andrewdavidwong Thank you for pointing that out. I had missed that. I am still working through the UEFI issues to get past the black screen but if I make it through https://www.qubes-os.org/doc/uefi-troubleshooting/ without finding a solution, I'll be sure to ask further questions on the qubes-users mailing list. ;)

kmfreder1 commented 3 years ago

So, I did manage to find a way around this black screen issue in order to install Qubes, per https://groups.google.com/g/qubes-users/c/NwUFSCkp1dE/m/-K9_3oPGBgAJ by connecting an HDMI monitor. That's what it took in my case. Then, to get the laptop screen working, I ran all updates and then "qubes-dom0-update kernel-latest". Wish I would have caught the HDMI thing earlier...would have saved me a lot of time. Now to take QubesOS for a test drive!

Skybeat commented 3 years ago

Hello,

I wonder if there is already a reliable solution for this. I have the same problem with the black screen. Is there already a stable solution to be able to carry out the installation? None of the tips in this issue helped me.

[qubes-verbose] options=console=vga efi=attr=uc smt=0 noexitboot=1 mapbs=1 kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0.4-x86_64 i915.alpha_support=1 ramdisk=initrd.img

to

`[qubes-verbose]

options=console=vga efi=attr=uc smt=0

options=console=vga efi=no-rs iommu=no-igfx loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan vga=current,keep guest_loglvl=all

noexitboot=1

mapbs=1

kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0.4-x86_64 i915.alpha_support=1

kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0.4-x86_64 i915.alpha_support=1 nouveau.modeset=0 iommu=no-igfx console=hvc0 acpi=off ramdisk=initrd.img`

rebuilt.

Unfortunately nothing helped. The last lines on the screen for me is the following ( if I use the changed BOOTX64.cfg):

Can any one please help?

Thank you

balmhood commented 3 years ago

I know this an old bg but I am facing the exact same as the OP, also on an ACER machine (4 years old). I have also tried the `

noexitboot=1

mapbs=1`

commenting but also get stuck at the dracut-initqueue[482]: Warning: dracut-initqueue timeout - starting timeout scripts Ravioli, did you ever manage to fix this ?

DemiMarie commented 3 years ago

I believe there is a flag to tell Xen to keep control of the VGA console, which could provide more debug info.

marmarek commented 3 years ago

Yes, add vga=,keep to the xen.gz in grub. I recommend also removing quiet option from the linux kernel (vmlinuz line). You'll get a bit of mess on the screen, but may yield some useful info.

DemiMarie commented 3 years ago

vga=,keep`

Extra comma?

marmarek commented 3 years ago

It's intentional, the first parameter (empty here) is the mode to set.

GitAntoinee commented 3 years ago

Any news? I have the same problem on my lenovo l340 Edit: I booted the installation media in legacy mode first instead of UEFI and the black screen was gone.

najtin commented 2 years ago

Same issue on Ryzen 7 5800U, also tried the HDMI port with no success. Also only UEFI as a boot option.

thepuregene commented 2 years ago

Same issue for me too Ryzen 7 5800H. There is no BOOTX64.cfg file. I think the https://www.qubes-os.org/doc/uefi-troubleshooting/ guide is outdated. I am trying R4.1 in UEFI mode. Tried V4.0.4 also, same error. I tried on my other older i7 laptop booting working like a charm in UEFI for both versions of Qube. If there are any updated guides pls inform

alt3r-3go commented 2 years ago

@marmarek, I think I have a root cause and a solution to at least a subset of this kind of situations (black screen after "relinquishing VGA console"). I had the same problem with my Alder Lake/12th gen Intel CPU-based laptop (Optimus-based setup with an additional NVidia card) and it turned out to be a combination of the following:

  1. The i915 video driver doesn't support that iGPU yet
    1. I don't remember whether i915.force_probe helped to at least display something, but in any case there's a separate issue of heavy artfacts unless an intel X.Org driver is used (similar to #4782), which is not easily configurable in the installer environment anyway
  2. The nouveau driver crashes on that dGPU (RTX 3080, they claim some initial modesetting support, but it didn't fly)
  3. Kernel, when booting tries to use the efifb driver to re-use the UEFI-configured video buffer - which would have helped in this case - but fails with an error stating that the buffer address is incorrect

As a result, the installer actually boots, but the screen is blank. I've realized that when I was able to "keyboard-only" switch to one of the consoles and issue commands, e.g. reboot.

The solution is to apply these two patches (available in the latest 5.17 branch, but not in 5.10 that's used in the installer/dom0 by default): patch1, patch2, full list in context (the last two patches in the list, as of today).

I've tested this by building my own ISO and installing from that. The redrawing is very slow, but at least it did allow me to get Qubes installed and after that installing kernel 5.16 (which has some support in i915) + configuring X.Org to use the intel driver (as discussed in #4782) made it usable enough for now.

So I think including those two patches in the upcoming 4.1.1 update could be a good idea and help some folks trying to install Qubes. What do you think? I can send a PR if needed - would you be interested?

tzwcfq commented 2 years ago

@alt3r-3go, Intel Alder Lake integrated GPU already works in newest Qubes 4.1 ISO builds with kernel-latest. I had the same issue and the ISO from here worked for me: https://qubes.notset.fr/iso/

alt3r-3go commented 2 years ago

Right, but I didn't want to use those ISOs (I know they are kind of official, but then not exactly per my understanding, so I didn't want to go there...) and the official installer uses kernel 5.10.x.

Plus, these two patches fix an actual bug and by doing that enable the kernel to automatically use the UEFI-preconfigured video buffer via efifb, which will pay off by providing a viable fallback at the next encounter with a glitchy driver or unsupported HW.

tzwcfq commented 2 years ago

If Qubes 4.1.1 release will still have kernel version 5.10 then these patches would help.

DemiMarie commented 2 years ago

So I think including those two patches in the upcoming 4.1.1 update could be a good idea and help some folks trying to install Qubes. What do you think? I can send a PR if needed - would you be interested?

Not @marmarek, but a PR would be great. If these are marked for stable, then picking up a new release in the 5.10.x series would also work.

alt3r-3go commented 2 years ago

@DemiMarie thanks, I'll send a PR during the upcoming weekend, most likely. I think these patches aren't planned for 5.10, but I'll double-check.

alt3r-3go commented 2 years ago

Didn't work out this weekend, but I think I should be able to find the time this week.

alt3r-3go commented 2 years ago

The PR is in, but there seems to be some problem with the CI infra.

andrewdavidwong commented 1 year ago

Is this still a problem?

andrewdavidwong commented 4 months ago

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