Realtek 2.5gbit usb ethernet(RTL8156B) problem

Hi there,

I cannot re-connect after reboot when using Realtek 2.5gbit usb ethernet(RTL8156B). I need to unplug and plug in again to get the connection up. Any solution for this problem?

Thanks a lot for helping.

KC

I use the following platform
ASUS P8H77-I motherboard
i7-3770 CPU @ 3.40GHz
Firmware Version: 23.05.2 r23630-842932a63d
Kernel Version: 5.15.137
package: kmod-usb-net-rtl8152 ver 5.15.137-1

This is the relevant Kernal log

[    6.187871] usbcore: registered new interface driver cdc_ether
[    6.210161] cdc_ncm 4-1:2.0: MAC-Address: c8:4d:44:26:a2:89
[    6.212395] cdc_ncm 4-1:2.0: setting rx_max = 16384
[    6.214622] cdc_ncm 4-1:2.0: setting tx_max = 16384
[    6.217030] cdc_ncm 4-1:2.0 eth5: register 'cdc_ncm' at usb-0000:00:14.0-1, CDC NCM, c8:4d:44:26:a2:89
[    6.219834] usbcore: registered new interface driver cdc_ncm
[    6.227683] PPP generic driver version 2.4.2
[    6.230180] NET: Registered PF_PPPOX protocol family
[    6.233925] kmodloader: done loading kernel modules from /etc/modules.d/*
[    7.742987] pps pps0: new PPS source ptp0
[    7.744713] ixgbe 0000:05:00.0: registered PHC device on eth2
[    7.867052] 8021q: adding VLAN 0 to HW filter on device eth2
[    7.869058] br-lan: port 1(eth2) entered blocking state
[    7.870771] br-lan: port 1(eth2) entered disabled state
[    7.873304] device eth2 entered promiscuous mode
[    8.023057] pps pps1: new PPS source ptp1
[    8.025258] ixgbe 0000:05:00.1: registered PHC device on eth3
[    8.149156] 8021q: adding VLAN 0 to HW filter on device eth3
[    8.151570] br-lan: port 2(eth3) entered blocking state
[    8.153808] br-lan: port 2(eth3) entered disabled state
[    8.156498] device eth3 entered promiscuous mode
[    8.162699] RTL8211E Gigabit Ethernet r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
[    8.479769] r8169 0000:07:00.0 eth4: No native access to PCI extended config space, falling back to CSI
[    8.484022] r8169 0000:07:00.0 eth4: Link is Down
[    8.486209] br-lan: port 3(eth4) entered blocking state
[    8.488404] br-lan: port 3(eth4) entered disabled state
[    8.490682] device eth4 entered promiscuous mode
[    8.492913] br-lan: port 3(eth4) entered blocking state
[    8.495050] br-lan: port 3(eth4) entered forwarding state
[    8.497229] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[    8.500515] br-lan: port 4(eth5) entered blocking state
[    8.502696] br-lan: port 4(eth5) entered disabled state
[    8.504913] device eth5 entered promiscuous mode
[    8.661040] pps pps2: new PPS source ptp2
[    8.663244] ixgbe 0000:03:00.1: registered PHC device on eth1
[    8.787089] 8021q: adding VLAN 0 to HW filter on device eth1
[    8.789366] br-lan: port 3(eth4) entered disabled state
[    8.791720] br-lan2: port 1(eth1) entered blocking state
[    8.793850] br-lan2: port 1(eth1) entered disabled state
[    8.796460] device eth1 entered promiscuous mode
[    8.945084] pps pps3: new PPS source ptp3
[    8.947085] ixgbe 0000:03:00.0: registered PHC device on eth0
[    9.071047] 8021q: adding VLAN 0 to HW filter on device eth0
[    9.073210] br-lan: port 4(eth5) entered blocking state
[    9.075276] br-lan: port 4(eth5) entered forwarding state
[   11.035609] r8169 0000:07:00.0 eth4: Link is Up - 1Gbps/Full - flow control off
[   11.037780] br-lan: port 3(eth4) entered blocking state
[   11.039850] br-lan: port 3(eth4) entered forwarding state
[   12.777089] ixgbe 0000:05:00.1 eth3: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[   12.779561] br-lan: port 2(eth3) entered blocking state
[   12.781644] br-lan: port 2(eth3) entered forwarding state
[   13.935783] ixgbe 0000:03:00.0 eth0: NIC Link is Up 10 Gbps, Flow Control: None
[   13.938096] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Reboot completed but connection down

unplug the usb-ethernet adapter

[   50.868604] usb 4-1: USB disconnect, device number 2
[   50.870762] cdc_ncm 4-1:2.0 eth5: unregister 'cdc_ncm' usb-0000:00:14.0-1, CDC NCM
[   50.873069] br-lan: port 4(eth5) entered disabled state
[   50.875419] device eth5 left promiscuous mode
[   50.877404] br-lan: port 4(eth5) entered disabled state

plug in the usb-ethernet adapter again

[   68.585390] usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
[   68.645729] cdc_ncm 4-1:2.0: MAC-Address: c8:4d:44:26:a2:89
[   68.647795] cdc_ncm 4-1:2.0: setting rx_max = 16384
[   68.649854] cdc_ncm 4-1:2.0: setting tx_max = 16384
[   68.652142] cdc_ncm 4-1:2.0 eth5: register 'cdc_ncm' at usb-0000:00:14.0-1, CDC NCM, c8:4d:44:26:a2:89
[   68.652598] br-lan: port 4(eth5) entered blocking state
[   68.656912] br-lan: port 4(eth5) entered disabled state
[   68.659010] device eth5 entered promiscuous mode
[   68.661128] br-lan: port 4(eth5) entered blocking state
[   68.663128] br-lan: port 4(eth5) entered forwarding state
[   68.665233] br-lan: port 4(eth5) entered disabled state
[   72.464843] br-lan: port 4(eth5) entered blocking state
[   72.466831] br-lan: port 4(eth5) entered forwarding state

connection now up

Disclaimer: I don't have this (or similar) USB ethernet cards myself, but…

As far as I understand it, this card can operate in two different operations modes:

  • 'driver-less' via a generic cdc_ncm kernel module, as you're doing right now
  • using the real hardware driver, which would be r8152

cdc_ncm is more of a kludge, than a real solution here - so you might want to look into r8152 instead, this involves removing cdc_ncm and including/ loading r8512 instead. For testing, I'd suggest to start with a fresh OpenWrt 'installation' booted from USB stick (doesn't affect your currently installed system, so you can experiment). OpenWrt/main snapshots with kernel v6.1 might be preferred (as-in necessary) to support this relatively new chipset (depending on your actual USB IDs, you might have to go even newer).

Decide - problem making usb card or rock solid pcie one? I never had any problems with pcie card with pfsense or openwrt. Ahh one time only with openwrt and old intel quad pro 1000 card, with pcie bridge and two dual port eth chips, pain in ass with openwrt, but with opnsense/ pfsense absolutly no single problem...

Thanks for the suggestions. As I am completing new to openwrt. Could you point me to internet resources on how to do it?

nevermind edit
probably best to do what slh says and try a newer version of openwrt

Thanks a lot. Problem solved after using this version

Firmware Version: OpenWrt SNAPSHOT r25773-766ec55966 / LuCI Master git-24.089.54606~0ecb5ed
Kernel Version: 6.1.82

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