I just tested it on A version, all good. I'm concerned about B.
Open two shells, one for logread -f and another one for
then try 3 instead of 1.
I just tested it on A version, all good. I'm concerned about B.
Open two shells, one for logread -f and another one for
then try 3 instead of 1.
Sure.
Unfortunately, vendor firmwares are often optimised for their own vendor driver. Or vice versa. So there could be a speed penalty when using class drivers. And you don't get all the ethtool knobs, like manual speed/duplex settings etc.
But if the speed is good, the firmware doesn't crash, and all you need is autoneg, then there is no reason not to use the cdc-ncm or cdc-ether drivers with this device.
@detroit - I was able to test. I got it working thanks to @AndrewZ by using the ‘echo’ method in the startup file, detailed above.
One additional thing you might want to do with USB / USB-C network adapters is add a ‘usbquirks” to your grub.cfg file. Context and more info here:
(see last two posts in the thread.)
https://forum.openwrt.org/t/solved-realtek-r8152-nic-issues-on-x86-64/226989/9?u=justanotherenduser
Quick update — this is now working in my custom 25.12.x build after adding kmod-usb-net-cdc-ncm and kmod-usb-net-cdc-ether .
A few data points from the working setup:
$ ip link show
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP qlen 1000
$ lsmod | grep -E 'asix|ax88179|cdc_ncm|cdc_ether|usbnet|mii'
cdc_ether 12288 1 cdc_ncm
cdc_ncm 24576 0
usbnet 24576 4 cdc_ncm,cdc_ether,ax88179_178a,asix
$ lsusb
Bus 002 Device 002: ID 0b95:1790 ASIX AX88179B
From /sys/kernel/debug/usb/devices , the adapter is selecting config #2 and binding via cdc_ncm :
T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=5000 MxCh= 0
P: Vendor=0b95 ProdID=1790 Rev= 2.00
S: Manufacturer=ASIX
S: Product=AX88179B
S: SerialNumber=[redacted]
C:* #Ifs= 2 Cfg#= 2 Atr=a0 MxPwr=184mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=0d Prot=00 Driver=cdc_ncm
I:* If#= 1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=01 Driver=cdc_ncm
So in this case, the missing piece in the failing image was that the CDC NCM / CDC Ethernet modules were not included. Once those were added, the expected interface was created.
Thank you all for your prompt replies! I didn't have to do any manual intervention after flashing the new custom build.
Package list used for the working build:
apk-mbedtls base-files bcm27xx-gpu-fw bcm27xx-utils ca-bundle dnsmasq dropbear
e2fsprogs firewall4 fstools kmod-fs-vfat kmod-nft-offload kmod-nls-cp437
kmod-nls-iso8859-1 kmod-sound-arm-bcm2835 kmod-sound-core kmod-usb-hid libc
libgcc libustream-mbedtls logd mkf2fs mtd netifd nftables odhcp6c
odhcpd-ipv6only partx-utils ppp ppp-mod-pppoe procd-ujail uci uclient-fetch
urandom-seed cypress-firmware-43455-sdio brcmfmac-nvram-43455-sdio
kmod-brcmfmac wpad-basic-mbedtls kmod-i2c-bcm2835 kmod-spi-bcm2835
kmod-i2c-brcmstb kmod-i2c-designware-platform kmod-spi-dw-mmio
kmod-hwmon-pwmfan kmod-thermal kmod-usb-net-lan78xx kmod-usb-net-rtl8152
kmod-r8169 luci luci-app-attendedsysupgrade kmod-usb-net-asix
kmod-usb-net-asix-ax88179 kmod-mii usbutils
kmod-usb-net-cdc-ether kmod-usb-net-cdc-ncm
I really appreciate you putting an extra effort trying to reproduce it and then fix it. thank you!