RTL8153B Support on 22.03.4

Hi,

I am using a Pi4B with a Ethernet hat:

I was able to get this working before on 21.03? (I think, it was a long time ago) using a patched RTL8152 (RTL8153B) Driver.
Possibly this one by @amteza: Update kmod-usb-net-rtl8152 Driver to avoid USB 3.0 to Gigabit LAN issues? - #7 by Ark

I update to 22.03.4 and cannot seem to find a kernel module that works with this hat in order to enable the ethernet port (the USB ports work just fine).

i've tried the kmod-usb-net-rtl8152 module with all of the dependencies I can think of as well as several other rtl modules/usb modules on both 22.03.04, 22.03.3 and 21.06/21.04. Nothing I can find seems to be able to get it working.

lsusb still returns nothing with the usb->ethernet bridge

Anyone got any ideas, short of figuring out how to build a custom new driver module.

Regards

Obvious question, but did you plug in the USB jumper block that comes with the board to link the top board to the Pi? Do the USB ports on the HAT work?

Even with no drivers installed, the 8153 should be listed on the bus.

Yup, its plugged in.

Regards

LSUSB returns this:

root@OpenWrt:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux 5.4.215 xhci-hcd xHCI Host Controller
Bus 001 Device 003: ID 2109:2817 VIA Labs, Inc.          USB2.0 Hub
Bus 001 Device 002: ID 2109:3431  USB2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux 5.4.215 xhci-hcd xHCI Host Controller

Does lsusb show the hub chip, the 8153, and any device that you plug into one of the USB user ports on the new board?

If I plug in a keyboard to one of the ports on the hub it shows up

root@OpenWrt:~# lsusb
Bus 001 Device 005: ID 046d:c31c Logitech USB Keyboard
Bus 002 Device 001: ID 1d6b:0003 Linux 5.4.215 xhci-hcd xHCI Host Controller
Bus 001 Device 003: ID 2109:2817 VIA Labs, Inc.          USB2.0 Hub
Bus 001 Device 002: ID 2109:3431  USB2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux 5.4.215 xhci-hcd xHCI Host Controller

The 8153B itself is getting warm so its getting power.

Run lsusb -t for more details. It's interesting that nothing is showing up as USB3.

The basic kernel USB drivers will detect and enumerate any devices on the USB bus. This has to work before any chip-specific drivers can take effect.

root@OpenWrt:~# lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=, Driver=hub/4p, 480M
        |__ Port 1: Dev 3, If 0, Class=, Driver=hub/4p, 480M

If I plug in a USB Device to the daughterboard (I grabbed a blue yeti mic as it was the first thing to hand)

root@OpenWrt:~# lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=, Driver=hub/4p, 480M
        |__ Port 1: Dev 3, If 0, Class=, Driver=hub/4p, 480M
            |__ Port 1: Dev 7, If 0, Class=, Driver=, 480M
            |__ Port 1: Dev 7, If 1, Class=, Driver=, 480M
            |__ Port 1: Dev 7, If 2, Class=, Driver=, 480M
            |__ Port 1: Dev 7, If 3, Class=, Driver=, 480M

That is the hub on the top board but it is not running USB3 like it should. The jumper should have the extra pins for USB3 and they need to make contact in both ports.

Not always a good sign. That can mean that the chip is burned out.

True, but it was working a few months/year back when I last played with it and has been in a box since.

I vaguely remember having fun with this before and needing a patched? driver like I said - but i dont remember the output from lsusb at the time.

Sorry, mate. I'm not sure I can help this time.

No worries, just wondered if you had a driver package kicking around. Was worth an ask.

1 Like

Quick update on this,

I ordered a new hat, plugged it into my existing install and it worked just fine. So it is indeed that the chip had died sometime in the last few months while being stored in a box.

1 Like

Forgot to post this:
This is what lsusb returns with a working hat + drivers installed. The realtek chip didnt show up without drivers though.

root@OpenWrt:~# lsusb
Bus 002 Device 003: ID 0bda:8153 Realtek USB 10/100/1000 LAN
Bus 001 Device 003: ID 2109:2817 VIA Labs, Inc.          USB2.0 Hub
Bus 001 Device 002: ID 2109:3431  USB2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux 5.10.176 xhci-hcd xHCI Host Controller
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc.          USB3.0 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux 5.10.176 xhci-hcd xHCI Host Controller

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.