Hello everyone,
I lost a somewhat important file from a software crash in an appvm.
Within the VM, I couldn't find a way to recover it. I copied the appvm
filesystem containers ('private.img', 'private-cow.img',
'private-cow.img.old').
As I understand it, 'private-cow.img' contains the old
Set the following kernel options on the installer usb media:
Comment out noexitboot=1 and mapbs=1
(https://www.qubes-os.org/doc/uefi-troubleshooting/)
Blacklisted nouveau (https://www.qubes-os.org/doc/uefi-troubleshooting/)
Set i915.force_probe=*
Set the following kernel options on the installer usb media:
Comment out noexitboot=1 and mapbs=1
(https://www.qubes-os.org/doc/uefi-troubleshooting/)
Blacklisted nouveau (https://www.qubes-os.org/doc/uefi-troubleshooting/)
Set i915.force_probe=*
Hi I'm here to report how Qubes works on my 6-year-old laptop after 1-month of
installation. In short, it can take longer time to start-up VMs (inevitable for
my 8Gb RAM), but once a VM is on, softwares within it run smoothly. I once
received a warning like "not enough memory to start a new
Hi Ben,
thank you for this HCL report. It is now part of this pull request:
https://github.com/QubesOS/qubes-hcl/pull/59
... and will be visible on the website soon!
/Sven
--
public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54
Hi Ben,
you wrote:
Installed in legacy mode - will try another install at some point to see
if I can get UEFI working.
Thank you for your HCL report! Are you aware that there was a thread
about this machine in 2019?
https://groups.google.com/g/qubes-users/c/WMc88pfT-hM/m/4r7sS6d7BQAJ
Maybe examine a previously working connection's WiFi tab & the Device line
for uniqueness. The trouble is variability of reference, I think. Say you
see wlan0 or wifi0 plus a MAC? Try changing that to simply the device's
MAC (no snappy name, this is part of what I suspect the problem is), just
