In my spare time I figured I would see if I could get Qubes running on a Lemur Pro that has just been sitting around. Or at least how far I can get, anyway. I don’t intend to annoy anyone here by asking you to fix it for me, I’m just documenting my journey here in case anyone cares to read or comment about it. There’s a high probably I haven’t figured obvious things out as I’ve never run Qubes before.
Anyway, Qubes 4.0.3 installs and runs just fine. The onboard Intel 9560 wireless adapter does not get detected, which is totally expected. So I proceed to connect a usb ethernet adapter and then get updates going. But first that means I need to point the firewall to sys-usb:
$ qvm-prefs --set sys-firewall netvm sys-usb $ qvm-service --enable sys-usb network-manager # then restart sys-usb
I’m jumping straight to bleeding edge since this is new hardware:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel-latest kernel-qubes-vm
Sweet, after a reboot uname shows Linux 5.8. And the good news is that sys-net
lspci now shows a wireless adapter’s name in the list. Running
ip address doesn’t show the wireless network interface. I think that means udev doesn’t know about the new wireless interface. I’m guessing I’ll need to brush up on Fedora style sysconfig stuff to see how I can convince it to add the interface. So that’ll be my next step after a small break.
The only other defect I’ve noticed so far is that the system doesn’t hibernate when I close it, even after updating to kernel 5.8. I’ll see about tackling that if/when I get networking working.