ODROID-XU4 ASIX AX88772B stopped working on recent kernel

This forum is for supported devices using an ARMv7 Samsung SoC.

ODROID-XU4 ASIX AX88772B stopped working on recent kernel

Postby netoholic » Sun Sep 11, 2016 1:06 pm

Hi, like it happened some time ago on the C1, USB ethernet network devices with ASIX AX88772B are no longer working with current kernel package linux-odroid-xu3 3.10.103-2. While on the C1 current kernel seems fixed and ASIX is working again, package version linux-odroid-xu3 3.10.96.X was last known to work with ASIX AX88772B.
netoholic
 
Posts: 2
Joined: Thu Jun 16, 2016 2:01 pm

Re: ODROID-XU4 ASIX AX88772B stopped working on recent kerne

Postby moonman » Sun Sep 11, 2016 7:03 pm

"Doesn't work" is too generic. Do you have any logs?
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3314
Joined: Sat Jan 15, 2011 3:36 am

Re: ODROID-XU4 ASIX AX88772B stopped working on recent kerne

Postby sdrider » Fri Sep 16, 2016 4:53 am

I was just posting a similar issue in the Software > Armv7 forum when I decided to do some extra searching before posting and ran across this post. So I'll add my info here since I think I've hit a similar issue.

---

I have an odroid-xu4 that serves as my home router. It has 3 ethernet devices: the on-board gigabit, a USB gigabit ethernet and a USB 100Mb ethernet.

My last update was 2015-08-23 and it was running kernel 3.10.102-3-ARCH armv7l. I just updated tonight and as part of the update the kernel was changed to 3.10.103-2-ARCH armv7l.

A new problem since the update is the 100mb ethernet USB device (a trendnet TU2-ET100) is no longer visible to the system. However, the on-board and gigabit USB devices work fine. By not visible, I mean it is not brought online on kernel bootup. Another problem, while lsusb runs fine, lsusb -v will hang indefinitely. Neither ^C or ^Z will break the hang - a kill -9 to the lsusb process from a separate terminal will, though.

I can see the kernel change was added with this commit and I see this commit in the hardkernel repository that removes USB debugging. But also plenty of other changes between 102 and 103 over the ~3 weeks since I last updated too, so it may not be related.

The device is not seen by the kernel at all on boot - at least, nothing is reported to syslog. I did see this message when I unplugged and plugged back in the 100Mb USB device:

[ 229.231633] [c2] usb 1-1: USB disconnect, device number 2

and searching the entire boot log reveals only one other message related to usb 1-1:

[ 3.179865] [c6] usb 1-1: new high-speed USB device number 2 using s5p-ehci

But no messages related to the device being detected or used as a network interface. I also tried switching the 100Mb USB dongle over to the spare 2nd USB3 port on the odroid, but that didn't help or print any messages to the syslog at all about the kernel detecting a new USB device.

Here's the output of lsusb:

Code: Select all
> lsusb
Bus 006 Device 002: ID 0bda:8153 Realtek Semiconductor Corp.
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 2357:0601
Bus 004 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0b95:7720 ASIX Electronics Corp. AX88772
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


USB 6 device 2 is the on-board gigabit (works fine)
USB 4 device 3 is the Gigabit USB dongle (works fine)
USB 1 device 2 is the Trendnet 100Mb dongle that no longer works, which matches the ASIX AX88772 description from the OP
sdrider
 
Posts: 29
Joined: Sat Aug 10, 2013 3:56 am

Re: ODROID-XU4 ASIX AX88772B stopped working on recent kerne

Postby sdrider » Fri Sep 16, 2016 5:02 am

I can also confirm that downgrading back to 3.10.102-3-ARCH and rebooting has fixed the issue - the USB device and network interface are working again using the 3.10.102 kernel.
sdrider
 
Posts: 29
Joined: Sat Aug 10, 2013 3:56 am

Re: ODROID-XU4 ASIX AX88772B stopped working on recent kerne

Postby sdrider » Wed Oct 19, 2016 1:40 am

Just following up on this issue: I noticed newer kernels had been released since this was reported. I went ahead and tested an upgrade since I had a safe rollback strategy if things didn't work, and I can confirm the issue is resolved as of kernel 3.10.103-5-ARCH.
sdrider
 
Posts: 29
Joined: Sat Aug 10, 2013 3:56 am


Return to Samsung

Who is online

Users browsing this forum: No registered users and 3 guests