LibreELEC.tv
LibreELEC.tv copied to clipboard
LibreELEC
[BUG] LE12 on Rpi5 - RTL8153-based USB3.0 to wired ethernet adapter doesn't come up across a boot
Describe the bug
RTL8153-based USB3.0 to wired ethernet adapter doesn't come up across a boot. It does not appear in Settings/LibreELEC/ Connections. Unplugging it and replugging it causes it to activate until the next reboot.
How to reproduce
Steps to reproduce the behavior:
- Plug a RTL8153-based Ethernet adapter into a USB 3.0 port on Rpi5.
- Check that it is active in the settings screen
- Reboot the Rpi5
- Check the settings screen and note that the eth1 interface is not there.
- Unplug and replug the adapter.
- Note that the eth1 interface now appears in the setting scren.
Information
- LibreELEC Version: LibreELEC-RPi5.aarch64-12.0-nightly-20240222-96ea547
- Hardware Platform: Rpi5
Log file
https://paste.libreelec.tv/happy-bonefish.log
The problem does not exist in LE 11.0.6, but appears to have been introduced in LE 12.
I had a similar problem on rpi4 with a normal ubuntu. It turned out that the vendor implemented two usb modes for the RTL8153-based device:
- Ethernet device (vid: 0bda, pid: 8153)
- CD Rom drive (vid: 0bda, pid: 8152)
The CD rom mode is thought to be used for installing windows drivers and to avoid shipping an additional mini cd. [1] If the adapter is plugged before boot, the cd rom mode is active and no network device driver will be loaded.
To fix that, you for example could apply a udev rule which simply ejects the cdrom and reloads the usb device as per [2]. That worked fine for me.
I'm not familiar with LibreELEC in detail, but I guess there is some way to add udev rules. If no experienced developer jumps in, I could also have a look into where to add it.
[1] https://forums.raspberrypi.com/viewtopic.php?t=336517#p2021375 [2] https://forums.raspberrypi.com/viewtopic.php?t=336517#p2022215
It would be helpful to see the output of
lsusb
with adapter plugged before boot (non-working) and adapter plugged after boot (working). Then we could find the correct usb pids for the udev rule.
Actually , it's the other way around --
After boot = non-working:
login as: root
root@libreelec's password:
##############################################
# LibreELEC #
# https://libreelec.tv #
##############################################
LibreELEC (community): nightly-20240224-9992601 (RPi5.aarch64)
LibreELEC:~ # ifconfig
eth0 Link encap:Ethernet HWaddr D8:3A:DD:CA:DE:2B
inet addr:192.168.1.144 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5099 errors:0 dropped:0 overruns:0 frame:0
TX packets:1803 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2822509 (2.6 MiB) TX bytes:386593 (377.5 KiB)
Interrupt:110
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14406 (14.0 KiB) TX bytes:14406 (14.0 KiB)
LibreELEC:~ # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0471:060c Philips (or NXP) Consumer Infrared Transceiver (HP)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 003: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
LibreELEC:~ #
`
After unplugging and replugging (working):
`LibreELEC:~ # ifconfig
eth0 Link encap:Ethernet HWaddr D8:3A:DD:CA:DE:2B
inet addr:192.168.1.144 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13792 errors:0 dropped:0 overruns:0 frame:0
TX packets:2026 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3504477 (3.3 MiB) TX bytes:494651 (483.0 KiB)
Interrupt:110
eth1 Link encap:Ethernet HWaddr 4C:E1:73:42:54:E9
inet6 addr: fe80::4ee1:73ff:fe42:54e9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:929 errors:0 dropped:0 overruns:0 frame:0
TX packets:83 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:69704 (68.0 KiB) TX bytes:42751 (41.7 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:84 errors:0 dropped:0 overruns:0 frame:0
TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:17626 (17.2 KiB) TX bytes:17626 (17.2 KiB)
LibreELEC:~ # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0471:060c Philips (or NXP) Consumer Infrared Transceiver (HP)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 004: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 005: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
This is with the workaround described installed that's described here (udev rule):
https://io.24hoursmedia.com/tech-notes/help-my-rpi4-thinks-my-usb-ethernet-is-a-storage-device
Without that, the device does show in lsusb as RTL8151 instead of RTL8153. IIRC, with the udev rule installed, the device does come up across a boot -- but only on the Rpi4, and not on the Rpi5, running the same nightlies.
Ref: https://forum.libreelec.tv/thread/28119-usb3-to-gigabit-ethernet-adapter-on-rpi4-5-troubles/
