Hi,

I thought it would be useful to others out there to share my experience in 
getting Qubes R4.0.3 up and running on a System76 Darter Pro (darp6) 
laptop. The installation worked seamlessly, but quite a lot of work was 
needed to get Qubes fully functional.

1) Replace the wifi card

The installed wifi card (Intel Wireless-AC 9560) does not work with Qubes 
R4.0.3 + Xen 4.13.1 due to some sort of Xen/Qubes bug, see this thread 
<https://github.com/QubesOS/qubes-issues/issues/5615>. Buy an Intel 
Wireless-AC 9260 card and install it following the instructions in the 
system76 
Darter Pro manual 
<https://github.com/system76/docs/blob/gh-pages/service-manuals/pdfs/Darter/darp6-service-manual.pdf>
.

Instead of buying a new Wifi card, you can try applying the patch outlined 
in the thread linked to above and compiling your own kernel, but I have not 
tried that. I unsuccessfully tried newer kernels and multiple iwlwifi 
firmware versions, and in the end just bought a new wifi card

2) Ethernet no-strict-reset

The sys-net Qube will fail on start ("Unable to reset PCI device"). In Qube 
Manager, under sys-net settings, go to the Devices tab, and Configure 
strict reset for PCI devices. Then apply the no-strict-reset policy to 
26:00.1 Ethernet Controller Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller.

3) Upgrade the dom0 kernel to enable keyboard function keys

The system76 keyboard mappings (LED backlight control, etc) don't work with 
the default kernel (4.19.94). Now that you have internet access, install 
the latest stable kernel (5.6.16), which includes the system76 drivers, in 
dom0:

dom0$ sudo qubes-dom0-update kernel-latest

4) Use latest kernel for sys-net

While you're at it, install the latest stable VM kernel and configure the 
sys-net VM to use it.

dom0$ sudo qubes-dom0-update kernel-latest-qubes-vm

I'm not sure this is strictly necessary, but it works fine.

5) Make screen turn back on after suspend

At this point, the laptop will not recover after closing the lid and 
suspending it; when you open the lid, the laptop appears to leave the 
suspend mode (the LEDs on the front flash in the normal operating pattern), 
but the screen remains blank and you are forced to turn the laptop off by 
holding the power button. This is caused by the Thunderbolt port, for some 
reason. You need to remove the thunderbolt module from dom0 before suspend 
and reload it after resuming.

In theory, you should be able to do this by creating a file in 
/lib/systemd/system-sleep.

dom0$ sudo vim /lib/systemd/system-sleep/thunderbolt.sleep

  #!/bin/sh
  if [ "${1}" == "pre" ]; then
    sudo rmmod thunderbolt
  elif [ "${1}" == "post" ]; then
    sudo modprobe thunderbolt
  fi

dom0$ sudo chmod +x thunderbolt.sleep

I find this to be unreliable, however -- sometimes it isn't called. 
Instead, I rmmod thunderbolt in dom0 after booting the laptop, and then 
only load it when needed. Any suggestions for a better way of doing this?

6) Make wifi come back after suspend

To make the wifi connection come back after suspend / resume, add iwlmvm 
and iwlwifi (on separate lines) to /rw/config/suspend-module-blacklist in 
the sys-net vm. This will remove the modules from the kernel before 
suspend, and reload them after restore.

I haven't tested bluetooth or the built-in microphone and camera. Feel free 
to chime in if you have this laptop or have any suggestions.

Oliver

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/cd9fe2d7-c66f-4e5a-9ea6-ee2e2cdca95do%40googlegroups.com.

Reply via email to