Posts by rkershenbaum

This is not specifically related to the USB wired Ethernet driver problems, since it also occurs with the built-in wired and wireless interfaces (without a USB network interface installed). But I also opened a ticket on the UI hang issue here:

[BUG] After manually switching network interfaces, UI hangs for several minutes · Issue #8669 · LibreELEC/LibreELEC.tv

Describe the bug After manually switching network interfaces, the LE user interface hangs for about three minutes How to reproduce Steps to reproduce the…

github.com

...and one here:

I know this isn't the highest priority problem, but just to keep it in the queue, I opened a ticket here:

Update: I still have a RTL8153 adapter, so I tested it on an Rpi5 with unmodified LE 11.0.6 and with the LE 12 nightly-20240222-96ea547.

On the official LE 11 instance, the RTL8153 adapter came up automatically across boots and worked as expected.

On the LE 12 nightly, it required unplugging and replugging to come up following each reboot. Howver, unlike the AX88179 adapters, it did retain its settings (connect-automatically=off, static IP address, etc.) across a boot.

So the failure of the RTL8153 adapter to activate automatically across boots seems to have been introduced in LE 12. (I can live with this, since I don't use it all the time.)

As expected, the AX88179 adapter didn't activate on either unmodified LE 11 or unmodified LE 12, even after unplugging and replugging.

Unless I've screwed something up again (which is always possible), the Rpi4 and Rpi5 seem to behave differently. On the Rpi4, the eth1 interface comes up automatically after a boot or power cycle -- but loses its settings. On the Rpi5, the interface does not appear after booting, but will appear after unplugging and replugging the adapter, or after issuing "ifconfig eth1 up".

Bedroom:~ # ifconfig
eth0      Link encap:Ethernet  HWaddr D8:3A:DD:CA:E7:C7
          inet addr:192.168.1.142  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4723 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1489 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2383059 (2.2 MiB)  TX bytes:247794 (241.9 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:81 errors:0 dropped:0 overruns:0 frame:0
          TX packets:81 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15944 (15.5 KiB)  TX bytes:15944 (15.5 KiB)
Bedroom:~ # ifconfig eth1 up
Bedroom:~ # ifconfig
eth0      Link encap:Ethernet  HWaddr D8:3A:DD:CA:E7:C7
          inet addr:192.168.1.142  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9425 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5804 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3539023 (3.3 MiB)  TX bytes:1402100 (1.3 MiB)
          Interrupt:110

eth1      Link encap:Ethernet  HWaddr 20:7B:D2:D2:B1:6B
          inet addr:192.168.1.81  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:56 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:18427 (17.9 KiB)  TX bytes:10837 (10.5 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:91 errors:0 dropped:0 overruns:0 frame:0
          TX packets:91 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16749 (16.3 KiB)  TX bytes:16749 (16.3 KiB)

Ok...playing around with this some more...

I can get the eth1 interface to come alive after a reboot by unplugging it and plugging it back in. However, it loses all its settings, and defaults back to "connect automatically" and "dhcp". I want to use manual static IP addresses on both interfaces, and I want the eth1 interface to not connect automatically. When I want to use it, I will disable the eth0 instance, and enable the eth1 instance. (As I've mentioned, this results in a 1-5 minute UI hang.)

This is progress, though....

Oops...user error...I hadn't set up the rules file correctly on the Pi4.

Quote from chewitt

See what happens with "ifconfig eth1 up" .. it might take a while to get an address via DHCP

On the Pi5, the interface immediately came up. On the Pi4, I got:

ifconfig: ioctl 0x8913 failed: No such device

Both are running LE12 nightly. The Pi5 had been up a couple of hours longer.

One more data point: When I power-cycle the Pi5, the AX88179 interface does not come up at the completion of the boot. But as soon as I unplug it from the USB3 port and plug it back in, it comes alive.

That procedure doesn't work (for some reason) on the Pi4. Still getting "no such device" after a reboot, and after unplugging and replugging the interface.

Over three hours now with no eth1 link showing.

After an hour, no eth1 interface showing with ifconfig.

Lsusb output matches yours.

Bedroom:~ # lsusb -t
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/2p, 480M
    |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 001: Dev 002, If 0, Class=Vendor Specific Class, Driver=ax88179_178a, 5000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/2p, 480M
    |__ Port 001: Dev 002, If 0, Class=Vendor Specific Class, Driver=mceusb, 12M
    |__ Port 002: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 002: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 002: Dev 003, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M

Thanks for staying on this! Sorry it's been such a PITA.

I'll give this a try on my systems, and see what happens.

Quote from chewitt

mglae I've seen that one. It's mostly discussing problems where the adapter can't be used correctly whereas in our case it simply doesn't probe and load the driver (so not getting that far). The cbc_mbim stuff looks related to a USB-C dock.

rkershenbaum Are these ASIX adapters a simple Ethernet adapter or are they the Ethernet portion of a USB-C dock?

chewitt Just simple Ethernet adapters. This exact model:

https://www.amazon.com/dp/B00MYTSN18?ref=ppx_yo2ov_dt_b_product_details&th=1

Quote from chewitt

Update the RPi5 to https://chewitt.libreelec.tv/testing/LibreE…h64-11.80.0.tar with the ASIX adapter connected and share the log URL from "journalctl | paste" please. I've made the drivers built-in to the kernel (=y) instead of using loadable modules (=m). That's not necessarily the right fix, but takes udev (which I think is the issue) out of the equation temporarily.

Looks like the ASIX interface still didn't come up. There is no eth1 interface available. Here's the journalctl log:

https://paste.libreelec.tv/holy-heron.log

Let me know if there's anything else I can do to help diagnose this.

I've noticed that the procedure for enabling the RTL8153 adapter, described here in post #4, has to be redone anytime LE is updated. So not an ideal solution.

I'm hoping the AX88179-based adapters can be made to work.

Just for completeness...here's the dmesg output from the stable 11.06 version on Rpi5:

https://paste.libreelec.tv/apparent-gator.log

...and stable 11.06 on Rpi4:

https://paste.libreelec.tv/relevant-maggot.log

Although I don't want to run it in production, I also tried OSMC on Rpi4, and the AX88179 adapter seems to come up normally on that distribution.

Here you go. "dmesg | paste" from Rpi5 running the 11.80 test version, with the AX88179 adapter physically installed, but not creating the eth1 device.

https://paste.libreelec.tv/oriented-mastodon.log

Sorry, forgot the share the dmesg | paste. Here it is:

https://paste.libreelec.tv/relative-hedgehog.log

Although there's a "failed" indication, the AX88179 adapter does come up and seems to work ok.

I'm still seeing the 1-5 minute total unresponsiveness from the UI after I switch between eth0 and eth1. This is the debug log showing that:

https://paste.libreelec.tv/next-turkey.log

Thanks again for your work on this -- and everything LE-related!

Quote from chewitt

Code

echo "softdep ax88179_178a pre: cdc_mbim" > /storage/.config/modprobe.d/ax88179_178a-fix.conf
reboot

^ see if that resolves the errors? (found in https://github.com/FreddyXin/ax88…ment-1208448522)

Unfortuntely, it didn't on the Rpi5. The Ugreen adapter still doesn't come alive after the boot. (I applied this to the 11.80 test version.)