I’ve switched internal wifi/bluetooth on and attached the device to sys-net but it doesn’t appear in lspci, lsusb, or Network Manager. What am I missing?
1 Like
The Qualcomm Atheros AR9462 (QCNFA222) and Intel AX200(NGW) are only detected by Qubes OS after LUKS decryption if its respective hardware kill switch permits power to the component, and in case of the latter, only with a recent version of PureBoot containing the firmware jail.
The device does appear in Qubes Devices after switching “on” the kill switch. It just doesn’t seem to appear anywhere else after attaching it to sys-net.
1 Like
I vaguely recall a GitHub issue mentioning this behaviour years ago, but I am not very interested in searching for it at the moment. I suggest following the exact conditions I have provided above, starting with rebooting your Librem 14, and see if you are able to produce a successful result. You do not need to attach the Wi-Fi/Bluetooth card to sys-usb in order to attain network connectivity.
If I reboot with the switch enabled then the wifi device does appear in lspci. Is that the expected behavior in Qubes? No enabling and disabling with the switch after boot? Does the camera/mic switch work the same way?
Even though the wifi device appears in lspci I can’t figure out how to use it in Network Manager. When I create a new connection in Network Manager there are no devices in the Device dropdown under the Wi-Fi tab.
1 Like
Yes, correct, no. After logging in, the only required action left is selecting an SSID from the Network Manager’s dropdown menu. There is nothing else to configure and everything should work out of the box.
Even though the wifi device appears in lspci in dom0, the only device that appears anywhere in Network Manager is the ethernet adapter. It’s also worth mentioning that in the GUI dialog that allows you to attach devices to qubes, the wifi device is only identified with its hardware address unlike all the other devices I’ve seen which appear there with their name. Any ideas?
1 Like
Yes, here are a few to start:
- Boot any Linux distribution on a Live USB to determine whether the Wi-Fi/Bluetooth module is actually functioning or not.
- In Qubes OS, use Ethernet to update
dom0and all other templates, especially the defaultVM forsys-net, then restart your Librem 14 to see if Qubes OS is able to successfully detect the hardware in Network Manager.
Otherwise, provide information about the Wi-Fi/Bluetooth module itself, Coreboot payload version, and Qubes OS version.