I had the same problem (booting directly into the installer), and chose instead
to go directly into the provided root shell and mount the Qubes root partition
from there. You can also go into /boot/efi/EFI.
--
You received this message because you are subscribed to the Google Groups
On Saturday, September 22, 2018 at 8:45:28 AM UTC-4, awokd wrote:
> > On Friday, September 21, 2018 at 7:14:33 AM UTC-4, awokd wrote:
> >>> Hello all,
> >>>
> >>> After a recent dom0 update froze my Qubes 3.2 system I'd been using for
> >>> the past year and a half, I upgraded to Qubes 4.0 on the
On Friday, September 21, 2018 at 7:14:33 AM UTC-4, awokd wrote:
> > Hello all,
> >
> > After a recent dom0 update froze my Qubes 3.2 system I'd been using for the
> > past year and a half, I upgraded to Qubes 4.0 on the same Samsung EVO 850
> > SSD. My PC has a Gigabyte AORUS GA-Z270X-Gaming 7
stfun...@gmail.com:
> On Friday, September 21, 2018 at 7:14:33 AM UTC-4, awokd wrote:
>>> Hello all,
>>>
>>> After a recent dom0 update froze my Qubes 3.2 system I'd been using for the
>>> past year and a half, I upgraded to Qubes 4.0 on the same Samsung EVO 850
>>> SSD. My PC has a Gigabyte
On Friday, September 21, 2018 at 7:14:33 AM UTC-4, awokd wrote:
> > Hello all,
> >
> > After a recent dom0 update froze my Qubes 3.2 system I'd been using for the
> > past year and a half, I upgraded to Qubes 4.0 on the same Samsung EVO 850
> > SSD. My PC has a Gigabyte AORUS GA-Z270X-Gaming 7
stfun...@gmail.com:
> Hello all,
>
> After a recent dom0 update froze my Qubes 3.2 system I'd been using for the
> past year and a half, I upgraded to Qubes 4.0 on the same Samsung EVO 850
> SSD. My PC has a Gigabyte AORUS GA-Z270X-Gaming 7 (rev. 1.0) motherboard
> running the latest UEFI
