Ax88179a Not Working Mac

[Julia Dodoo]

Thisfixed it for me. I upgraded to Sierra and my USB 3.0 + Gigabit device stopped working. I tried reinstalling the drivers from Unitek with no luck. Once I installed the drivers from =pItemdetail&PItemID=131;71;112 then it worked. I haven't run diagnostics to see if it is getting appropriate speeds or anything of that nature, but it seems fine so far.

Should the USB3 component be correct, then you can proceed to troubleshooting performance. Also note that the tree view mentions other devices, and unless your device is the only one working through the root_hub, then your device might not have full bandwidth available.

Made another test, flashed a brand new image with the latest updates to a new sd card and made an iperf test between the jetson and another computer. The max speed was 511Mbits/s. Same iperf test showed 940Mbits/s on Rpi4. The other thing that I was thinking, is that I use an NVME SSD with an m.2 converter in the pci slot. Can it happen that if the Jetson detects a connection on the pci lane, it halfes the speed on the usb bus?

I'm using this ethernet dongle as a libvirt macvtap passhtrough to a VM. It's been working great until the last month or so. Around a month ago it would just randomly stop working with the following error:

1. I did try another ax88179 usb adapter in a different computer and eventually got the same error

2. I think the last stable kernel for this adapter was 5.17.x

3. yes, but on the other laptop i tested nothing else was plugged into the usb ports.

4. No power saving tools

4. autosuspend is not enabled, but i will give that kernel parameter a try

5. Didn't see anything out of the ordinary

rakotomandimby, I am almost certain that is a bad cable and is unrelated to the thread. Those are very low level USB messages indicating the device won't even enumerate on the bus -- this is way before the system can can even tell what the device is and what driver to use.

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday

Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing

---

How to Ask Questions the Smart Way

Since 5.18.15 (and still in 5.18.16), whenever my laptop suspends then my entire home network goes down (and my family start screaming). My laptop is connected to a dock which is connected via ethernet network to my main home router. When the laptop suspends, it puts that connection in some odd state which locks up that router (and thus disables the attached wifi access point which most of my family rely on). If I disconnect the ethernet cable, or the dock cable to the laptop, or wake up my laptop, then the router and network immediately recover. I have switched back to good 5.18.14 a few times to prove where the bug was introduced. I just discovered this forum thread so tried loqs kernel and find that fixes the bug also.

It only happens when using the dock ethernet connection. If I disconnect the dock network cable but keep the dock connected and then use a USB ethernet dongle connected directly to the laptop then the problem does not occur.

With regards to my post above, I later found I had an error in my testing and that loqs kernel did not fix my problem and so my issue is unrelated to this thread. @loqs, after fixing my test process, I bisected the kernel between 5.18.14 and 5.18.15 and found the offending commit so raised a bug at _bug.cgi?id=216333.

and reboot, all packages, including linux-firmware, are up to date, problem still persists.

It started with the updates during the last week, it was working fine before that.

Can't really pinpoint it to a kernel version or a version of linux-firmware, but currently its broken.

Why can you not pinpoint it? What were the results from your downgrading the just the kernel to a known good version? Similarly for linux-firmware. Then for both. Then for the full system to a known good date.

I thoguht this might be a firmware issue, too.

Rebooted into Ubuntu 23 livestick, there the error ocurred, too.

Rebooted back into arch and the error seems to be gone. (after several reboots)

Maybe this is another Issue with UEFI or USB controller (got no logs regarding these points).

For now it works again, very strange.

Maybe the UEFI of thinkpad x390 is buggy and doesn't do a proper usb reset.

I am running macOS Catalina 10.15.3 with a USB-C hub from Minix, which has an ethernet port. Inside is an AX88179 chip for which I installed the correct driver. When I start my MacBook or when I plug in my USB-C hub everything works fine. The interface is called 'AX88179 USB 3.0 to Gigabit Ethernet 2'

However, after a few minutes the connection stops working. In the network overview it shows the green dot with 'connected'. When I use the 'Renew DHCP Lease' option the dot becomes orange with the 'Self-assigned IP' message. I see a wrong subnet mask and get an IP that is not within the network (169.254.44.151). The cable is running straight to my modem/switch. WiFi is working just fine all the time.

The problem then is the adapter and not your Mac. Steer clear of off-brand products and look for adapters that use quality chipsets like Anker USB Ethernet Adapters (I personally use this brand due to their reliability and warranty; 18 months). Generically speaking, look for chipsets from known, market leaders like Intel, Broadcom, Qualcom, Texas Instruments, etc. Chances are, the WiFi adapter used by Apple for its AirPort adapter is a Broadcom.

I already had the modified USB drivers installed and added this one to /lib/modules/ and ran the insmod commands. However, my interface just not show up in either in the web console or in the terminal when I use the ifconfig command.

I looked at a number of web pages but they seem to want you to run lsusb or edit /etc/network/interfaces, neither of which exist on the DSM. On the other hand, I did learn that I should run "ifconfig -a" to see all interfaces and the USB NIC does show up there.

Did you have any success with the instructions to make the config persistent through reboots? This version of Linux does not seem to have the /etc/networking/ and /etc/init.d/ directories. I'm also wondering how the two insmod commands will get executed through the reboot.

2). I also get The operation failed. Please log in to DSM again and retry. (221) error when trying to open Control Panel / Networking in the DSM. I guess this is one reason the real Synology box is so expensive. Support is included!

Done everything in this thread to get this driver working with DSM 5.1 (5022.2) and it works uptil the point I do 'ifconfig eth1 up' at which point the Xpenology reboots as soon as I issue the command.

I replaced the adapter in use by the virtual switch with an old Anker USB3 adapter I have which uses a Realtek driver, and that instantly worked across all the virtual adapters, so I know the config is working as expected just not the USB3-E1000.

As an update, I have just got the Asix support team to be able to recreate the setup and they have been able to replicate the problem. They are now going to look at fixing it in the next release of the driver.

Unfortunately, like others here it seems ethernet issues may persist with MacOS and the Razer Core X Chroma. I didn't know about the issues prior to buying and installing but when I installed I went straight to v2.16 via Homebrew `brew cask install asix-ax88179` (tap homebrew/cask-drivers) since I noticed Razer's download was for ASIX OEM driver v2.14.

My current set up is with a Radeon RX 5700 XT, the 2020 MBP 13" is a four TB3 model, the laptop is connected via Razer's provided 0.7m passive-TB3 cable, the Core X CAT6 is wired directly to a Synology RT2600AC, the other USB devices connected (Magic Keyboard, Logitech mouse, Creative E5 DAC/AMP) all work without issue. The GPU itself seems to work without issue as well.

Running speedtest[.]net seems to be enough to cause the ethernet connection to drop, it fails, DNS queries fail, and the upload portion of the test fails. Reseat the CAT6, refresh, run the test again, fails again.

Also, depending on your network setup, i'd try connecting the Core X ethernet directly into your modem. I've seen Synology's cause some very bizarre and unforeseen things before, i would try and remove as much network equipment between the Core X and the internet, from the equation as possible.

I decided to start going the other route, swapping for a non-Chroma with a dock (ideally daisy chained for single cable convenience despite any perf hit). So I ended up buying a Belkin Thunderbolt 3 Dock Pro, testing now, everything seems to be working well. I also considered OWC's 14-port TB3 dock, looks like it might also be a reasonable option along with CalDigit. OWC is nice enough to even mention the chipsets used in the dock.

Anyway, with the Belkin and Chroma combo: all 4 USB devices work, ethernet shows up as USB 10/100/1000 LAN in System Report and the connection is stable, the Core X Chroma eGPU is daisy-chained via the TB3 downstream port and that appears stable as well.

When the connection is dropped all network traffic is dropped, it's as if the cable is no longer connected. I didn't test with the modem since the Speedtest was enough to trigger things as was a large file transfer to my old MBP. I did test and confirm a system to system connection fails.

3a8082e126