Installation of Qubes OS 4.0.3 requires the black screen workaround [0],
after that almost everything works fine.
The only issue is the minidisplay output not working at all, but I'm
convinced it's a UEFI/BIOS upgrade related issue, as it started happening
right after the update to 2.54 BIOS
Please read more carefully next time -- "Since I don't have Google
account which seems to be required to view the initial discussion (*as
linked in the first post of the thread*)". The first post says
"continuing from discussion at [link to Google groups]" without
explaining anything...
On 9/18/20 1:25 AM, Ondřej Fiala wrote:
Thank you for the reply! Since I don't have Google account which seems to be
required to view the initial discussion (as linked in the first post of the
thread), could you please give me a brief summary of what the core issue is?
On Sep 17, 2020 23:19,
I'm not completely new to Qubes OS and have it installed on inferior
machines before but due to hardware limitations always reverted back to
something lighter. This time though i have a pretty decent machine, it runs
windows in RAID0 and I have a 2230 form factor m.2 ssd with no raid and
this
On Tuesday, 15 September 2020 at 01:13:13 UTC+8 m.fernande...@gmail.com
wrote:
> The cloud-based aspect of Chromebooks means that in those situations where
> you don't consider you have much local on-site security, you can gain extra
> security by keeping things in the cloud, and using cloud
>test to change it back to RAID mode and see. Put back on ACPI if it
doesn't help.
I tried to set up rapid (rst raid) but nothing has changed
> Trying acpi = force is a good idea.
tried, but it didn't help.
Actually this problem arose before this summer when I had to change the cpu
fan and
