On Sunday, February 16, 2020 at 12:07:51 PM UTC+1, aihey wrote:
>
> > Looks like your Dell is a Ryzen with integrated AMD graphics, correct?
>
> that's right: it's a AMD Ryzen 5 3500U with Radeon Vega Mobile
>
> > Don't think the kernel included Qubes 4.0.3 has video drivers for it. To
> confi
aihey:
I spent a yesterday afternoon looking into this. I built Qubes 4.1 (stable
version) following the instructions in
https://www.qubes-os.org/doc/qubes-builder/. I did this on the actual machine
and had to re-install the OS with Fedora 31 as the building tool didn't support
my original O
> Have you tried to installing Qubes OS 4.1 both in UEFI and in legacy mode
> without success... ?
Yes, tried both UEFI and legacy modes and both of these failed. Only difference
was the GRUB dialog- in UEFI was black+white and in legacy with a blue coloured
background.
‐‐‐ Original Messa
Have you tried to installing Qubes OS 4.1 both in UEFI and in legacy mode
without success... ?
--
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+unsubs
> Looks like your Dell is a Ryzen with integrated AMD graphics, correct?
that's right: it's a AMD Ryzen 5 3500U with Radeon Vega Mobile
> Don't think the kernel included Qubes 4.0.3 has video drivers for it. To
> confirm, you could try to install in text mode and see if you get further.
> You s
'aihey' via qubes-users:
> Unfortunately this has not worked for me but thanks for your suggestion.
>
> Does anyone happen to know if the installation messages are saved somewhere?
> I would like to find out what triggers the installation to freeze (it all
> happens very quickly before it goes b
Unfortunately this has not worked for me but thanks for your suggestion.
Does anyone happen to know if the installation messages are saved somewhere? I
would like to find out what triggers the installation to freeze (it all happens
very quickly before it goes blank).
‐‐‐ Original Message ‐‐
My Dell is newer and simply doesn't have legacy boot. I know that the
altered parameter is used during boot because it was the only thing I
changed to make my installations turn from failures to successes.
--
You received this message because you are subscribed to the Google Groups
"qubes-user
Thank you for your comment. Did you run this in UEFI or legacy mode? Also, how
do you check that the parameters defined in BOOTX64.cfg are being used during
boot? In legacy mode the parameters appear different from what is defined in
the config file (you can check/edit the boot command by pressi
Fellow Dell Inspiron user here,
Your problems are different from mine, and I'm no expert, but maybe the
simple solution that worked for me might work for you:
Mount the ANACONDA partition of the Qubes boot USB, then edit BOOTX64.cfg
so that kernel parameters include 'nouveau.modeset=0'
--
You
10 matches
Mail list logo
