Unable to install Qubes : Black Screen - reboot - several EFI parameters tested w/ success

1,646 views
Skip to first unread message

iamnotan...@gmail.com

unread,
Jan 14, 2017, 11:28:59 AM1/14/17
to qubes-users
Hi all

I'm not able to install Qubes 3.2 on my workstation.
The install process go to the menu while booting on a usb key.
Then if i choose install .black screen then rebooting ..got back to same menu.

I've tried different parameters with grub presented in :
https://www.qubes-os.org/doc/uefi-troubleshooting/

1) chainloader line add /mapbs /noexitboot.
==> it reboot after doing ctrl +x .. going back to same install menu :(

2) At the end of chainloader line add -- efi=attr=uc
==> idem.

I've checked Intel VT is enabled in my computer, and tried both PC ROM Priority : with EFI Compat Rom and with Legacy Rom
=> idem.

Some specs here :
Processor 4x Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
Memory 8141MB

BIOS
Date 11/01/2012
Vendor American Megatrends Inc. (www.ami.com)
Version 3602

MBoard
Name P8P67 PRO
Vendor ASUSTeK Computer INC

Disk ATA Samsung SSD 850


Thanks !

podmo

unread,
Jan 16, 2017, 5:16:55 PM1/16/17
to qubes-users
iamnotan...@gmail.com wrote:
>
> I'm not able to install Qubes 3.2 on my workstation.
> The install process go to the menu while booting on a usb key.
> Then if i choose install .black screen then rebooting ..got back to same
> menu.
>
Does some text flash on screen very briefly, something about ACPI
EndEntire? It might help to hold down Enter on the install option to see
it.
I think it's caused by buggy EFI firmware so can suggest what worked for
me but can't guarantee it will address your specific bugs. I was able to
work around this on one of my systems by burning the Qubes installer to a
DVD instead. Another option is to boot with Refind (use the USB image)
http://www.rodsbooks.com/refind/getting.html and then use that to boot the
Qubes installer off USB.


Ted Brenner

unread,
Jan 16, 2017, 9:43:54 PM1/16/17
to podmo, qubes-users
I saw this too. Bizarrely, if I went to the command prompt, then typed quit, it then took me to a GUI screen and I was able to go forward from there. 



--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscribe@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/70f4b7ce968ffe306263cd25ef37f778.webmail%40localhost.
For more options, visit https://groups.google.com/d/optout.



--
Sent from my Desktop

Ted Brenner

unread,
Jan 17, 2017, 2:37:36 PM1/17/17
to podmo, iamnotan...@gmail.com, qubes-users
Woops, my reply left off iamnotanumber666. Adding them back.

iamnotan...@gmail.com

unread,
Jan 17, 2017, 4:10:55 PM1/17/17
to qubes-users, po...@sigaint.org

Thanks answering.
I'll try with Refind, and let you know.
But as speaking of my issue someone told me too that my p may be too old for that (no VT-d afaik), anyway i'll check the cpu and MB specs.

podmo

unread,
Jan 17, 2017, 4:36:52 PM1/17/17
to qubes-users
Replying to my own email so everything's in one spot. One last thing I
forgot, on another system I needed to append efi=no-rs to the options=
line in xen.cfg. I think this disables EFI runtime services entirely apart
from the initial boot sequence. Not sure of any other ramifications but
Qubes seems to be running fine. For example:

In /boot/efi/EFI/qubes/xen.cfg, set the options= lines like
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M efi=no-rs

You should be able to do something similar in the installer options; see
the Dell section that talks about efi=attr=uc on
https://www.qubes-os.org/doc/uefi-troubleshooting/.

I think Qubes 4.0 is going to use an updated version of Xen that contains
patches to work around some (probably not all!) of these system specific
EFI firmware bugs. If none of this works you could try to install in
legacy mode instead of EFI if you haven't already or wait until 4.0 ships
and try it.





Reply all
Reply to author
Forward
0 new messages