UE200 USB to Ethernet Adapter not initializing in boot
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- linux, raspberry-pi, ubuntu
- Domain
- embedded-iot, networking, operating-systems
Research direction
No source file or test is named. Start by reproducing the boot-time failure with the UE200 connected, then compare the provided dmesg and lsusb output with the successful unplug-and-replug case across the listed operating systems and kernels. Done means identifying the initialization failure and documenting or implementing a verified fix.
Written by the indexing model from the issue text.
Description
Describe the bug
I have USB to Lan adapter from TP link https://tinyurl.com/kptfvtrp which used to work perfectly fine around 6-8 months ago in Ubuntu Server 20.04 running Raspberry PI 4B (4GB RAM) and I recently tried to connect it to same hardware and OS and it fails to show the interface. It doesn't show up in lsusb but if unplug and plug it it works fine what could be the problem?
To reproduce
Connect UE200 from TPlink before boot and then boot
Expected behaviour
Supposed to be initailzed during boot
Actual behaviour
Not initializing during boot
System
- RPi 4B (4GB)
- Raspberry Pi reference 2024-03-15
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, f19ee211ddafcae300827f953d143de92a5c6624, stage2 - May 24 2024 15:30:04
Copyright (c) 2012 Broadcom
version 4942b7633c0ff1af1ee95a51a33b56a9dae47529 (clean) (release) (start) - Linux raspberrypi 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux
Logs
dmesg
[ 2.535403] usb 1-1.3: new full-speed USB device number 5 using xhci_hcd
[ 2.615603] usb 1-1.3: device descriptor read/64, error -32
[ 2.807586] usb 1-1.3: device descriptor read/64, error -32
[ 2.999391] usb 1-1.3: new full-speed USB device number 6 using xhci_hcd
[ 3.079588] usb 1-1.3: device descriptor read/64, error -32
[ 3.271585] usb 1-1.3: device descriptor read/64, error -32
[ 3.991400] usb 1-1.3: new full-speed USB device number 7 using xhci_hcd
[ 3.991629] usb 1-1.3: Device not responding to setup address.
[ 4.227594] usb 1-1.3: Device not responding to setup address.
[ 4.435387] usb 1-1.3: device not accepting address 7, error -71
[ 4.519396] usb 1-1.3: new full-speed USB device number 8 using xhci_hcd
[ 4.519629] usb 1-1.3: Device not responding to setup address.
[ 4.727670] usb 1-1.3: Device not responding to setup address.
[ 4.935901] usb 1-1.3: device not accepting address 8, error -71
lsusb (While connected during boot)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0eef:0005 D-WAV Scientific Co., Ltd WS170120
Bus 001 Device 003: ID 0461:0010 Primax Electronics, Ltd HP PR1101U / Primax PMX-KPR1101U Keyboard
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
(After unlpugging and replugging)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 2357:0602 TP-Link USB 10/100 LAN
Bus 001 Device 004: ID 0eef:0005 D-WAV Scientific Co., Ltd WS170120
Bus 001 Device 003: ID 0461:0010 Primax Electronics, Ltd HP PR1101U / Primax PMX-KPR1101U Keyboard
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Additional context
I tried this in Ubuntu 20.04, 22.04 and Raspbian Lite (64Bit) and also downgraded the kernel version but the issue still persists while it is running perfectly in the OS i installed during Nov/Dec 2023
- Dominant language
- No language data
- Stars
- 5.6k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/firmware
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
raspberrypi/firmware#2042 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/firmware#2040 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
raspberrypi/firmware#2039 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
raspberrypi/firmware#2038 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
raspberrypi/firmware#2037 · 4 comments ·
All issues in raspberrypi/firmware
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
espressif/esp-iot-solution#786 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100