I want to use the TP-Link Archer T4U Plus, and I worked hard to install the driver using the default template and added the USB device to sys-net, but now sys-net and sys-usb won’t start. Please tell me what I should do to use the USB Wi-Fi adapter.
Hi kzlz
If you remove the USB device from sys-net, can you then start sys-usb and sys-net?
I had to install Qubes with sys‑net with USB. That was the easiest way to get my USB adapter working. In other cases I wasn’t able to solve the problem.
I use the default setup with a sys-net and sys-usb- so when I use a USB adapter for WiFi, I just plug it in and tell sys-usb to attach the device to sys-net.
Hi! I wanted to get some more details about the process you followed to install the Wi-Fi adapter. Could you tell the specific commands you used to install the driver? Additionally, which template did you use? Are you able to restore the sys-net and sys-usb to their original state before to the driver installation?
no. both doesn’t work. i have this message
got empty response from qubesd. see jornalctl in dom0 for details.
I used the following commands within the Debian template according to this page.
sudo apt install linux-headers-generic build-essential git
cd rtw88
sudo dkms install $PWD
sudo make install_fw
sudo cp rtw88.conf /etc/modprobe.d/
Hi kzlz
How did you do:
?
Can you revert that change? – and if so: will sys-usb and sys-net then start?
got empty response from qubesd. see jornalctl in dom0 for details.
No. I tried reverting the settings, but a message like the above appeared, and now neither sys-usb nor sys-net can be started or forcibly stopped.
??
Yes. I had exactly the same problem after installing that driver GitHub - lwfinger/rtw88: A backport of the Realtek Wifi 5 drivers from the wireless-next repo. in Fedora 42 template. sys‑net stopped starting
To better understand what’s happening, please open the dom0 terminal and run the command journalctl | tail -2000. It would be helpful if you could paste all the output to the Pastebin or GitHub so we can read that it’s really happening.
I cloned a Debian template and followed the instructions in the GitHub repository to install the driver. The cloned qube appears to be working fine. However, since I don’t have physical hardware of the Wi-Fi adapter, I can’t test its functionality.
1 Like
To terminate the Qube immediately, open the Qube Manager and select both sys-net and sys-usb. Right-click and select the ‘Kill’ option, or directly reboot your machine.
Some questions: Does the Qube template where you installed the driver work properly? Also, on the GitHub repository, there’s a section dedicated to uninstalling the driver have you tried it?
As Chris mentioned, please tell us how you added the device to sys-net. QubesOS has a few ways of doing that (even more with r4.3) and they can cause different issues.
After deleting sys-net and recreating it, it started working. However, sys-usb remains in a yellow state and does not change. I added the device from the Qubes Manager settings.
How did you solve the problem?
I couldn’t solve this problem. I bought a USB adapter with Linux‑kernel support and I’m using it now
If you added the device through the Qubes Manager then you probably passed through a whole USB interface. Try reverting that and attaching the adapter itself through the Devices Widget in your tray
1 Like
I deleted sys-usb and created it from the CLI, and it worked. It failed when I tried it from the GUI.
For now, sys-net and sys-usb have returned. Now, back to the original question: how do I use an external USB Wi-Fi adapter? Should I connect it to sys-net from the system tray?
1 Like