[arch-general] Cannot tether from Android using USB or bluetooth
Hello fellow Arch Linux users, I recently tried to use USB tethering, without success. The interface just won't come up. I enabled the usb tethering on the phone, but ip link didn't show any new interface: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 28:d2:44:6c:0b:f8 brd ff:ff:ff:ff:ff:ff 3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 7c:7a:91:21:19:39 brd ff:ff:ff:ff:ff:ff 5: wwp0s20u4i6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 02:15:e0:ec:01:00 brd ff:ff:ff:ff:ff:ff (wwp0s20u4i6 is my builtin modem interface) journalctl -k tells me the following: myhost kernel: usb 1-1: device descriptor read/64, error -110 myhost kernel: usb 1-1: new low-speed USB device number 37 using xhci_hcd myhost kernel: usb 1-1: device descriptor read/64, error -71 myhost kernel: usb 1-1: device descriptor read/64, error -110 myhost kernel: usb 1-1: new low-speed USB device number 38 using xhci_hcd myhost kernel: usb 1-1: Device not responding to setup address. myhost kernel: usb 1-1: Device not responding to setup address. myhost kernel: usb 1-1: device not accepting address 38, error -71 myhost kernel: usb 1-1: new low-speed USB device number 39 using xhci_hcd myhost kernel: usb 1-1: Device not responding to setup address. myhost kernel: usb 1-1: Device not responding to setup address. myhost kernel: usb 1-1: device not accepting address 39, error -71 myhost kernel: usb usb1-port1: unable to enumerate USB device myhost kernel: usb 1-1: new high-speed USB device number 40 using xhci_hcd myhost kernel: cdc_acm 1-1:1.1: ttyACM3: USB ACM device myhost kernel: usb 1-1: USB disconnect, device number 40 myhost kernel: cdc_acm 1-1:1.1: failed to set dtr/rts myhost kernel: usb 1-1: new high-speed USB device number 41 using xhci_hcd myhost kernel: rndis_host 1-1:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-1, RNDIS device, aa:bb:cc:dd:ee:ff myhost kernel: rndis_host 1-1:1.0 enp0s20u1: renamed from usb0 myhost kernel: usb 1-1: USB disconnect, device number 41 myhost kernel: rndis_host 1-1:1.0 enp0s20u1: unregister 'rndis_host' usb-0000:00:14.0-1, RNDIS device myhost kernel: usb 1-1: new low-speed USB device number 43 using xhci_hcd The important stuff seems to be here: rndis_host 1-1:1.0 enp0s20u1: renamed from usb0 usb 1-1: USB disconnect, device number 41 rndis_host 1-1:1.0 enp0s20u1: unregister 'rndis_host' usb-0000:00:14.0-1, RNDIS device usb 1-1: new low-speed USB device number 43 using xhci_hcd The interface comes up but its immediately down, for some weird reason. I can't reproduce the problem every time. Anyone can point me on how to debug this further? Regards, -- Alfredo Palhares GPG/PGP Key Fingerprint 68FC B06A 6C22 8B9B F110 38D6 E8F7 4D1F 0763 CAAD
Do you maybe have android-udev installed? If so try removing that package.
On 08/24/2015 02:13 PM, Alfredo Palhares wrote:
I enabled the usb tethering on the phone, but ip link didn't show any new interface:
<snip>
The important stuff seems to be here: rndis_host 1-1:1.0 enp0s20u1: renamed from usb0 usb 1-1: USB disconnect, device number 41 rndis_host 1-1:1.0 enp0s20u1: unregister 'rndis_host' usb-0000:00:14.0-1, RNDIS device usb 1-1: new low-speed USB device number 43 using xhci_hcd
The interface comes up but its immediately down, for some weird reason. I can't reproduce the problem every time.
On my phone (Nexus 4 running CM 12.1 nightlies which are based on Android 5.1), activating USB tethering creates another Ethernet device. The USB disconnect message is disturbing and generally indicates hardware problems. Furthermore, it sounds like this issue is intermittent. This smells of hardware problems. I recommend cleaning the MicroUSB port if it looks dirty. Unfortunately, there is generally no easy way to do this without disassembling the phone. Personal anecdote: My phone's MicroUSB port (same Nexus 4) once got dirty enough to the point where the data pins no longer worked. However, the charge pins *did* work. I ended up taking the phone apart to clean the MicroUSB port. I'm still using that phone to this day. :-) --Kyle
participants (3)
-
Alfredo Palhares
-
Kyle Terrien
-
Neven Sajko