Ok I will explain to help others. Qubes seems not to like usb Wi-Fi adapters, so I set up an Ethernet connection.
1 Like
@Cad, thatâs awesome that you were able to get at least some kind of internet connection.
Just out of curiosity, does your sys-usb Devices tab look like this (i.e. USB controllers passed through from dom0 into a Qube)?:
Iâm sorry for bringing it up again, but if it doesnât, then this is why it wasnât working before 
It looks similar. I only have 3 controllers though. Iâve found that Qubes seems to periodically drop usb devices. It loses my printer and my Bluetooth dongle too. I guess someone coded that in to stop usb attacks but itâs really a pain in the neck.
That sounds really weird, and definitely in the realm of a bug.
The printer? As in, a cable printer, with no wireless communication between your machine and the printer�
Ok, that one is extremely out-of-place⌠
No, there wouldnât be anything in a USB qube that does anything like that. usbguard is in dom0 though, but if your USB controllers are in dom0 instead of sys-usb, then you wouldnât even be able to pass the devices through in the first place, so my guess is that itâs not thatâŚ
My hunch would say that the USB devices might have a sleep/suspend function that Qubes OS is not acknowledging, and then when it comes to actually using them, they are not âwoken upâ first, resulting in the sys-usb kernel assuming theyâve been removed.
Well, something along those lines, anywayâŚ
The output of dmesg in sys-usb would probably show was was happening when your devices âdisappearââŚ
In any case, itâs not great for you not being able to use your machine the way youâve been accustomed to.
Iâll bet. That sounds awful.
Is there any chance youâd be interested in filing a bug report?
One of us will happily file one on your behalf if we can get some more info about your hardware, because you shouldnât have to put up with thisâŚ
Iâm pretty sure there have been quite a few users who have experienced similar things, itâs just that youâre one of the few who decided to actually say something about it (which deserves a lot of respect).
So a bug report would definitely go a long way in getting this fixed
1 Like
Iâll look into it when I have time. Thank you for the help.
Is it possible, @alzer89 that his experience is related to the frequent complaints about webcameras & sys-usb? That increasing the RAM (the minimum the VM expects starting up) to a value which some have suggested is abnormally high (like 1GB) might alleviate? Maybe @Cad, if you wanted to test that theory out you could check the situations with those usb devices after padding any sys-usb VM with a small increment of memory (limiting it to a reasonable amount for testing of say 1GB)?
I went ahead and reinstalled Fedora 36 (the entire operating system, not just the fedora vm on cubes) so I could get through the fall semester without messing with Qubes everyday trying to get it to work. I will probably try to reinstall over the holiday between semesters to see if I can get Qubes to work then. Ill get back to you guys in a few months.
1 Like
Depending on what system resources the device firmware asks for, thatâs definitely a possibility.
Itâs always worth a try. Just as putting swiotlb=8192 or a higher value into the sys-usb kernelopts which seems to be what AX201 Wifi 6 modules need to work (for some reason)âŚ
Either way, itâs incredibly peculiar that devices just âdisappearââŚ