Closed powderluv closed 4 years ago
Also there is a weird case where I was able to boot up with the USB device inserted and wifi still wouldn't work but it started working once the ethernet cable was connected (I was still pinging the Wifi Interface)
Looks like there is an interference if you are connected via 2.4GHz. Switching to 5G solved the issue.
Thanks
Setup wifi and ping it from another device. Plugin a usb3 device. Your ping will stop until you unplug it.
[1194970.642530] usb 2-1: new SuperSpeed Gen 1 USB device number 13 using xhci_hcd [1194970.663389] usb 2-1: New USB device found, idVendor=1a6e, idProduct=089a, bcdDevice= 1.00 [1194970.663406] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [1195129.257710] usb 2-1: USB disconnect, device number 13
PING 192.168.1.94 (192.168.1.94): 56 data bytes 64 bytes from 192.168.1.94: icmp_seq=0 ttl=64 time=87.477 ms 64 bytes from 192.168.1.94: icmp_seq=1 ttl=64 time=291.265 ms 64 bytes from 192.168.1.94: icmp_seq=2 ttl=64 time=257.235 ms 64 bytes from 192.168.1.94: icmp_seq=3 ttl=64 time=136.405 ms 64 bytes from 192.168.1.94: icmp_seq=4 ttl=64 time=14.718 ms 64 bytes from 192.168.1.94: icmp_seq=5 ttl=64 time=43.916 ms 64 bytes from 192.168.1.94: icmp_seq=6 ttl=64 time=20.869 ms 64 bytes from 192.168.1.94: icmp_seq=7 ttl=64 time=17.380 ms 64 bytes from 192.168.1.94: icmp_seq=8 ttl=64 time=15.561 ms 64 bytes from 192.168.1.94: icmp_seq=9 ttl=64 time=15.213 ms 64 bytes from 192.168.1.94: icmp_seq=10 ttl=64 time=45.855 ms Request timeout for icmp_seq 11 Request timeout for icmp_seq 12 Request timeout for icmp_seq 13 Request timeout for icmp_seq 14 Request timeout for icmp_seq 15 Request timeout for icmp_seq 16 Request timeout for icmp_seq 17 Request timeout for icmp_seq 18 64 bytes from 192.168.1.94: icmp_seq=11 ttl=64 time=8012.002 ms 64 bytes from 192.168.1.94: icmp_seq=12 ttl=64 time=7011.518 ms 64 bytes from 192.168.1.94: icmp_seq=13 ttl=64 time=6093.284 ms
I have tried two different USB3 devices (one of which is the Google Coral Edge TPU) and both demonstrate the same behaviour. I checked if the USB is getting enumerated as an ethernet interface but that isn't the case.
This works ok on a raspbian 32bit image