Kernel Update to 6.12.25-1.qubes.fc37 Broke Phone Internet Tethering on Android

User Support Hardware Issues
1

Just putting out there my USB Tethering Issue with Android phone after an update in case it might help someone else.

My USB tethering with an Android phone stopped working after updating Qubes OS 4.2.:

  • Fresh Qubes OS 4.2 install, (trying to fix the tethering issue actually) and the USB tethering worked initially.

  • Applied Dom0 update (kernel 6.12.25-1.qubes.fc37) and Debian 12 template update.

  • Tethering worked after Dom0 update but failed immediately after Debian 12 update upon restarting sys-usb and sys-net.

  • Rolled back sys-usb and sys-net to kernel 6.6.77-1.fc37 via Qubes Manager fixed tethering.

  • Wi-Fi from the same phone worked as a fallback throughout.

Sorry, but I’m not really savvy enough to provide much more info. I also don’t want to break tethering again messing around too much but here are the USB tethering drivers in sys-net with the working kernel (6.6.77-1.fc37):

rndis_host             24576  0
cdc_ether              24576  1 rndis_host
usbnet                 61440  2 rndis_host,cdc_ether
mii                    16384  1 usbnet

Anyone else seen similar USB tethering issues with kernel update to 6.12.25-1?

1 Like
2

I wonder if this might help explain an issue I am having with a USB controller that is passed through to an HVM and it suddenly stopped working after a reboot? The system in question hadn’t been rebooted in a couple of months and then when rebooted the USB ports that are passed through all fail to work.

Looking in the dmesg logs of the HVM, all I can see is a message about “can’t setup: -110” and then the USB bus gets de-registered. I am guessing my issue is probably another symptom of the kernel issue you are referencing.

1 Like
3

Sounds very similar to what happened to me. I have been using the same setup with little to no issues for a couple of years. Updates come and go, no issues etc. Then sometime in May I believe I ran an update and it broke my tethering but I wasn’t paying attention to the how and why. Ended up doing a fresh install with my same old (4.1 I think) version of Qubes. That fixed it temporarily until an update ran and I had a power outage forcing reboot which broke tethering again. That led me to trying fresh install of 4.2 and my above fix by selecting earlier kernel in Qubes Manager. Quick and easy fix (maybe temporary) after many hours of trying a million other things far beyond my capabilities to fix it. Hope this helps.

2 Likes