Re: [qubes-users] Installing in UEFI (Ryzen 1800X, ASRock Fatal1ty X370 Professional Gaming)

2018-02-01 Thread Willem D
On Thursday, 1 February 2018 13:40:24 UTC+2, awokd  wrote:
> On Thu, February 1, 2018 10:21 am, Willem D wrote:
> 
> To workaround the problem, try using Refind. To actually debug it, I think
> Qubes is using a modified version of Fedora 25's installer. Does that one
> work on your system? Not aware of any log files that get generated that
> early (especially if it can't find a file system interface).

I just tried Fedora 25 Live x86_64 (workstation), to my surprise it worked. I 
had to add "nomodeset" to boot parameter. It turns out the GeForce GT 1030 does 
not have modesetting support yet. I will remove that card in future Qubes tests.

Going to read up on Refind and leaving this here for reference: 
https://www.qubes-os.org/doc/uefi-troubleshooting/

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/4128473c-3112-4f46-a917-8dbebb817085%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Installing in UEFI (Ryzen 1800X, ASRock Fatal1ty X370 Professional Gaming)

2018-02-01 Thread Willem D
Hi All,

I tried installing Qubes 4.0-rc3 in UEFI mode using a USB drive. After POST I 
see 4 options* regardless of what option I choose the message "Couldn't obtain 
the File System Protocol Interface" flashes very quickly on my screen and the 4 
options are displayed on the screen again.

I found the report on Github: 
https://github.com/QubesOS/qubes-issues/issues/2838 which describes the same 
issue as I have. I would like to debug the problem, but I require assistance 
with that.

I was able to test media and install Qubes when booting in legacy mode. I do 
however require my system to run in UEFI mode. It might be possible to force 
the OS to boot in UEFI mode after installing in legacy, however I would rather 
try to find the cause of the problem and improve the experience for others with 
the same issue.

I am able to start Fedora 27's anaconda installer in UEFI mode using the same 
hardware.

*options:
"Test media and install Qubes R4.0-rc3"
"Install Qubes R4.0-rc3"
"Troubleshooting - verbose boot and Install Qubes R4.0-rc"
"Rescue a Qubes system"

Hardware:
CPU: AMD Ryzen 7 1800X
M/B: ASRock Fatal1ty X370 Professional Gaming
RAM: 32GB G.SKill F4-3200C14D-32GTZ TridentZ Series
GPU: 2GB GeForce GT 1030
GPU: 8GB Radeon RX 480 GDDR5 256bit PCI-E 3.0 
SSD: 500GB Samsung 960 EVO NVMe M.2 PCI-E 3.0

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ae34f348-7f86-4fb3-a043-27f67b378e14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.