Do you have a reference for that? I don't think that's true.
I can run Qubes OS without problems with UEFI on other hardware, and there is even UEFI troubleshooting guidance at https://www.qubes-os.org/doc/uefi-troubleshooting/ - which doesn't mention lack of support for EFI...
-joe
Thanks, Mike. In my case I can't even install Qubes in EFI mode because the installer won't run; and installing Qubes in Legacy mode will lead to an empty .cfg file. I'll take another stab at it tonight.
-joe
I have installed Qubes 3.2 successfully on my Thinkpad T470p
(20J6CTO1WW). This machine is pretty similar to the T470, except
that is has a quad-core i7 CPU. It runs perfectly and all Qubes
functionality is available on that machine. The installation,
however, was not an easy task.
1. Booting: UEFI is not a problem for the Qubes installer, but
you must pay attention on how you created the bootable install
media. Just using dd is not sufficient. I had to use the
livecd-tools from Fedora to create the install media. After
creating the media I had to manually set the partition label to
BOOT using the dosfslabel utility. Otherwise, I was unable to boot
from the media. It was not necessary to fall back to legacy boot
or to mess around with the Grub configuration.
--
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...@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/CAJmbC%3DEVMcAMKEXLGPooXa-kQt7_vuUDigozex%2Bq4iUSARykoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Pull request: https://github.com/QubesOS/qubes-doc/pull/490
Hi,
I have managed to keep everything pretty standard in my installation on my T470p.
* Turn off SecureBoot
* dd iso (qubes 4.0) to USB-stick
* add rEFInd to another USB-stick
* boot on the rEFInd USB-stick and start the installer.
I struggle with TPM, but I figure that I should go through the guide over here: https://github.com/tklengyel/xen-uefi to sign the xen-efi and get TPM.
Regards
Josef
No, but I have what seems like another data point. On my Lenovo
T520 under UEFI, trying to boot the 4.0rc3 installer produces
similar symptoms: whichever option I choose from the grub menu,
the screen goes blank briefly (I didn't measure, but probably
<2sec), then comes back to the grub menu. Repeat ad nauseam.
But if I try the same thing from EFI Shell (version 1, because my
UEFI firmware's too old to support version 2), I get this:
Read failed for initrd.img: Device error
fs1:\EFI\BOOT> # i.e. it comes right back to the shell prompt
And sure enough, when I try again from grub, I can *sometimes*
see a very brief flash of purple before the grub menu returns. I
suspect that Qubes/Xen is displaying the same message, but then
grub is clearing the screen too quickly for me to read it.
Details:
- Hardware: Lenovo T520, model 4239-CTO (this laptop was bought
in 2012, and has been happily running Ubuntu in UEFI mode
ever since)
- BIOS: 8AET56WW (1.36 ) 12/06/2011
- I think the UEFI version is 2.0, but not totally sure
- TPM *disabled* (one thing at a time, y'know?)
- I'm not using USB, but rather a real DVD+R, burned directly
from the (signature-verified) .iso
- I've verified the DVD media against the original .iso image
*after* seeing these symptoms, which suggests it isn't an
actual media error
So, two things:
- If this is helpful (and it's a solvable problem), awesome!
- I'd suggest adding a "Hit <ENTER> to continue" (perhaps with
timeout) after a failed boot attempt, to keep any error
message on screen for a while
> I wonder if Fedora netinst iso (_not_ Live iso) boot on such new
> hardware, after directly dd-ing it to USB stick. Can you check that?
I already have :-) Fedora 27 netinst (again, signature-verified
and burned to optical media) boots successfully. I aborted the
installer at its first (language) prompt. I was't sure which
Fedora version 4.0rc3 contains, so picked the newest; if you'd
like me to test an older one, please let me know -- or if you
need more information (including a reboot to verify the UEFI
version).
- Eric
--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/TEmVIozLJh0/unsubscribe.
To unsubscribe from this group and all its topics, 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/c0576e3b-9a58-458f-92fb-3dda8540033f%40googlegroups.com.
(Just learning Google Photo, Google+, gmail, etc., for purposes of this post. Until now I've been able to avoid them :-/ )
- Eric
I tried to install Qubes 3.2 on a T470s without success. I have the version with the Intel graphics. I did everything in Legacy Mode (no EFI). It does boot but the X server cannot start. Text installation did not work.
Stephan Marwedel says in this thread he managed to install 3.2. How?
I cannot wait for version 4 to come in January or later and installing RC version is risky since I need the laptop for work and no migration path from RC to candidate is guaranteed by the Qubes OS team.
Any help will be highly appreciated!
Hi,
I would try my path, download rEFInd to another usb-stick and boot the installer from there.
The only file you need is the EFI-file: https://sourceforge.net/projects/refind/
Also, that is an interesting data point as well, the bootx64.efi loader on the usb install works if it is started through rEFInd.
Cheers
Josef
--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/TEmVIozLJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@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/f44e144a-c45e-43a0-84f0-1ca61905bce8%40googlegroups.com.
Could you explain to me why using EFI would solve the problem of the X server not starting?
Sorry, I missed that part of your reply. I was answering both of you :)
I'll see if I can get Qubes 3.2 running on my T470p in the weekend if there's time. My collegue ended up with 4.0 with legacy boot to get everything working, so I just started from there. Using it for critical work and so far it's quite stable.
Regards
Josef
Thank you for your reply.
Could you explain to me why using EFI would solve the problem of the X server not starting?
--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/TEmVIozLJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@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/84284e0a-7269-44d7-ab95-98395b9330a8%40googlegroups.com.
I hope I will not encounter too much bugs with it and be able to work. It seems okay for the few hours I had to use it and even more resistant to usb devices being physically disconnected without detaching them than 3.2.
What if CSM enabled and legacy bios mode if you have it?
Did you solve this?
I would open a new thread, but you got the correct mailing list.