December 20, 2019 6:05 PM, 
( wrote:
On Friday, December 20, 2019 at 9:29:55 AM UTC-5, Claudia wrote:
 December 19, 2019 12:13 AM, "Claudia" < (javascript:false)> 

        > This is R4.1 build 20191013
> It works pretty well, definitely better than 4.0, but there are some weird 
> boot issues. If I let it
> boot with everything as default, it will boot loop before reaching the disk 
> password screen. I
...Looks like rd.qubes.hide_all_usb is what's causing it to crash. When I 
remove it, it boots fine with the graphical splash and passphrase prompt. 
Another AMD Ryzen user mentioned having the same problem a while back. 
Something about AMD's IOMMU grouping of USB controllers, or something.

Unfortunately, (my understanding is) that exposes the dom0 to the USB ports. 
Even if you have a sys-usb, dom0 is still exposed temporarily on boot.
Thanks for the tip. I actually thought removing that parameter just simply 
disabled USB Qube functionality and attached all devices to dom0, but I guess 
that's only when sys-usb is not running. Once sys-usb is running, it takes over 
the USB controllers from dom0, I guess. It's just that they're exposed before 
sys-usb starts, in that case.

It would be nice to have working, but I've never had a USB Qube before, even on 
my old machine, so I haven't lost anything. I don't use a lot of USB devices, 
and it's not a big part of my threat model. I'll play around with it when I 
have a chance.

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 view this discussion on the web visit

Reply via email to