I have the following to do troubleshooting but none of it are working. =======================================================================On a Raspberry Pi 4 Model B running Ubuntu 24.04, the problem is usually not the ASIX driver itself — it is most often one of these:
insufficient USB power, missing linux-modules-extra, kernel regression on ARM64, bad USB3 negotiation with the Pi 4 controller. The Pi 4 USB stack is more sensitive with AX88179 adapters than x86 PCs. Run these in order. First confirm the USB device is even enumerating: lsusb You want to see something like: Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 If NOTHING appears when plugging/unplugging: this is usually power or USB negotiation, not a missing driver. Then watch kernel logs live while plugging it in: sudo dmesg -w Plug the adapter in and look for: new SuperSpeed USB device USB disconnect device descriptor read/64 error reset SuperSpeed USB device Those messages are important. Then verify the driver exists: modinfo ax88179_178a If it says: modinfo: ERROR: Module ax88179_178a not found install extra modules: sudo apt update sudo apt install linux-modules-extra-raspi then reboot. On Ubuntu ARM images for Pi, linux-modules-extra-raspi is often missing by default. Then load manually: sudo modprobe ax88179_178a Check whether the interface appears: ip link You should get something like: enx001122334455 If the adapter appears in lsusb but no network interface appears, check whether the wrong driver attached: lsusb -t If you see: Driver=cdc_ncm instead of: Driver=ax88179_178a force rebinding: sudo modprobe -r cdc_ncm sudo modprobe -r usbnet sudo modprobe ax88179_178a then unplug/replug. A VERY common Raspberry Pi 4 issue with AX88179 is USB3 instability. Try ALL of these: Force USB2 mode temporarily Add to: sudo nano /boot/firmware/config.txt Add: usb_max_current_enable=1 and: dtoverlay=dwc2,dr_mode=host Then reboot. Also test: blue USB3 port vs black USB2 port, powered USB hub, different USB cable, direct connection without dock. If you see repeated disconnect/reconnect in dmesg, it is almost certainly power or USB PHY negotiation. Another important Raspberry Pi 4 workaround: Update EEPROM/firmware: sudo rpi-eeprom-update sudo apt full-upgrade then reboot. You can also try a newer kernel: sudo apt install linux-image-raspi or OEM/HWE stack: sudo apt install linux-oem-24.04 Finally, some cheap AX88179 clones are actually counterfeit chipsets that break on ARM Linux while working on Windows/macOS. The exact USB ID from lsusb matters. Paste these outputs if you want precise diagnosis: uname -a lsusb lsusb -t ip link sudo dmesg | tail -100 If the adapter is completely invisible in Network settings and no new interface appears, the key question is: does the Pi detect the USB device at the hardware level? or does enumeration fail before the driver loads? Run these exactly and paste the output: uname -a lsusb lsusb -t ip link sudo dmesg | tail -100 Meanwhile, here are the most likely Raspberry Pi 4 + Ubuntu 24.04 causes and fixes. 1. Missing kernel modules (VERY common on Ubuntu Pi) Install all extra modules: sudo apt update sudo apt install linux-modules-extra-raspi Then: sudo reboot After reboot: sudo modprobe ax88179_178a Check: ip link 2. USB power issue (extremely common on Pi 4) AX88179 adapters can draw more power than the Pi 4 USB ports reliably provide. Symptoms: device appears/disappears, nothing in Network panel, repeated USB resets in dmesg, works on PC but not Pi. Try: powered USB hub, official Pi PSU, different USB3 cable, black USB2 port instead of blue USB3 port. This alone fixes many AX88179 problems. 3. Ubuntu ARM kernel regression Ubuntu 24.04 ARM kernels have had USB ethernet regressions. Try a newer kernel: sudo apt install linux-oem-24.04 or: sudo apt full-upgrade Then reboot. 4. Force-load the driver manually Check whether the module exists: find /lib/modules/$(uname -r) -name '*ax88179*' If you see something like: kernel/drivers/net/usb/ax88179_178a.ko then force load: sudo modprobe usbnet sudo modprobe mii sudo modprobe ax88179_178a Check for interface: ip a 5. Wrong driver binding Check: lsusb -t If the adapter is using: cdc_ncm or generic usbnet instead of ax88179_178a, do: sudo modprobe -r cdc_ncm sudo modprobe -r usbnet sudo modprobe ax88179_178a Then unplug/replug. 6. Device not enumerating at all If lsusb does NOT show any ASIX device: driver is irrelevant, the Pi never sees the hardware. This usually means: insufficient power, bad cable, faulty adapter, incompatible USB dock, USB controller negotiation issue. Test: directly connected, no hub/dock, another USB port, another PSU, another OS like Raspberry Pi OS. If it works in Raspberry Pi OS but not Ubuntu, then this is almost certainly an Ubuntu kernel issue rather than hardware failure. 7. Check if NetworkManager is hiding it Sometimes the interface exists but is unmanaged. Check: nmcli device If you see the interface as unmanaged: sudo nano /etc/NetworkManager/NetworkManager.conf Ensure: [ifupdown] managed=true Then: sudo systemctl restart NetworkManager The most useful output now is: lsusb sudo dmesg | tail -100 Those two commands usually identify the exact failure immediately. Get smarter responses, upload files and images, and more. On a Raspberry Pi 4 Model B running Ubuntu 24.04, the problem is usually not the ASIX driver itself — it is most often one of these: insufficient USB power, missing linux-modules-extra, kernel regression on ARM64, bad USB3 negotiation with the Pi 4 controller. The Pi 4 USB stack is more sensitive with AX88179 adapters than x86 PCs. Run these in order. First confirm the USB device is even enumerating: lsusb You want to see something like: Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 If NOTHING appears when plugging/unplugging: this is usually power or USB negotiation, not a missing driver. Then watch kernel logs live while plugging it in: sudo dmesg -w Plug the adapter in and look for: new SuperSpeed USB device USB disconnect device descriptor read/64 error reset SuperSpeed USB device Those messages are important. Then verify the driver exists: modinfo ax88179_178a If it says: modinfo: ERROR: Module ax88179_178a not found install extra modules: sudo apt update sudo apt install linux-modules-extra-raspi then reboot. On Ubuntu ARM images for Pi, linux-modules-extra-raspi is often missing by default. Then load manually: sudo modprobe ax88179_178a Check whether the interface appears: ip link You should get something like: enx001122334455 If the adapter appears in lsusb but no network interface appears, check whether the wrong driver attached: lsusb -t If you see: Driver=cdc_ncm instead of: Driver=ax88179_178a force rebinding: sudo modprobe -r cdc_ncm sudo modprobe -r usbnet sudo modprobe ax88179_178a then unplug/replug. A VERY common Raspberry Pi 4 issue with AX88179 is USB3 instability. Try ALL of these: Force USB2 mode temporarily Add to: sudo nano /boot/firmware/config.txt Add: usb_max_current_enable=1 and: dtoverlay=dwc2,dr_mode=host Then reboot. Also test: blue USB3 port vs black USB2 port, powered USB hub, different USB cable, direct connection without dock. If you see repeated disconnect/reconnect in dmesg, it is almost certainly power or USB PHY negotiation. Another important Raspberry Pi 4 workaround: Update EEPROM/firmware: sudo rpi-eeprom-update sudo apt full-upgrade then reboot. You can also try a newer kernel: sudo apt install linux-image-raspi or OEM/HWE stack: sudo apt install linux-oem-24.04 Finally, some cheap AX88179 clones are actually counterfeit chipsets that break on ARM Linux while working on Windows/macOS. The exact USB ID from lsusb matters. Paste these outputs if you want precise diagnosis: uname -a lsusb lsusb -t ip link sudo dmesg | tail -100 If the adapter is completely invisible in Network settings and no new interface appears, the key question is: does the Pi detect the USB device at the hardware level? or does enumeration fail before the driver loads? Run these exactly and paste the output: uname -a lsusb lsusb -t ip link sudo dmesg | tail -100 Meanwhile, here are the most likely Raspberry Pi 4 + Ubuntu 24.04 causes and fixes. 1. Missing kernel modules (VERY common on Ubuntu Pi) Install all extra modules: sudo apt update sudo apt install linux-modules-extra-raspi Then: sudo reboot After reboot: sudo modprobe ax88179_178a Check: ip link 2. USB power issue (extremely common on Pi 4) AX88179 adapters can draw more power than the Pi 4 USB ports reliably provide. Symptoms: device appears/disappears, nothing in Network panel, repeated USB resets in dmesg, works on PC but not Pi. Try: powered USB hub, official Pi PSU, different USB3 cable, black USB2 port instead of blue USB3 port. This alone fixes many AX88179 problems. 3. Ubuntu ARM kernel regression Ubuntu 24.04 ARM kernels have had USB ethernet regressions. Try a newer kernel: sudo apt install linux-oem-24.04 or: sudo apt full-upgrade Then reboot. 4. Force-load the driver manually Check whether the module exists: find /lib/modules/$(uname -r) -name '*ax88179*' If you see something like: kernel/drivers/net/usb/ax88179_178a.ko then force load: sudo modprobe usbnet sudo modprobe mii sudo modprobe ax88179_178a Check for interface: ip a 5. Wrong driver binding Check: lsusb -t If the adapter is using: cdc_ncm or generic usbnet instead of ax88179_178a, do: sudo modprobe -r cdc_ncm sudo modprobe -r usbnet sudo modprobe ax88179_178a Then unplug/replug. 6. Device not enumerating at all If lsusb does NOT show any ASIX device: driver is irrelevant, the Pi never sees the hardware. This usually means: insufficient power, bad cable, faulty adapter, incompatible USB dock, USB controller negotiation issue. Test: directly connected, no hub/dock, another USB port, another PSU, another OS like Raspberry Pi OS. If it works in Raspberry Pi OS but not Ubuntu, then this is almost certainly an Ubuntu kernel issue rather than hardware failure. 7. Check if NetworkManager is hiding it Sometimes the interface exists but is unmanaged. Check: nmcli device If you see the interface as unmanaged: sudo nano /etc/NetworkManager/NetworkManager.conf Ensure: [ifupdown] managed=true Then: sudo systemctl restart NetworkManager The most useful output now is: lsusb sudo dmesg | tail -100 Those two commands usually identify the exact failure immediately. Get smarter responses, upload files and images, and more. M Rusli <[email protected]> 01:55 (4 hours ago) to bcc: appledevelopermrusli If the USB Ethernet adapter appears but NetworkManager cannot enable it, the problem is usually one of these on Ubuntu 24.04 ARM/Raspberry Pi: driver loaded incorrectly, interface stuck DOWN, NetworkManager not managing it, USB link flapping/resetting, bad ASIX firmware compatibility. Run these commands first. Check whether the interface exists: ip link Look for something like: enx001122334455 Then try bringing it up manually: sudo ip link set enx001122334455 up (replace with your actual interface name) If you get: Operation not permitted or Device not ready or it immediately goes DOWN again, then this is usually driver or USB instability. Next check the driver attached: ethtool -i enx001122334455 You want: driver: ax88179_178a If it says: cdc_ncm usbnet or something else, force the correct driver: sudo modprobe -r cdc_ncm sudo modprobe -r usbnet sudo modprobe ax88179_178a Then unplug/replug the adapter. Now restart NetworkManager: sudo systemctl restart NetworkManager Then: nmcli device If the USB Ethernet shows as: unmanaged unavailable or disconnected try explicitly enabling it: sudo nmcli device set enx001122334455 managed yes sudo nmcli device connect enx001122334455 If NetworkManager says: device not available or activation failed watch kernel logs live while enabling: sudo journalctl -kf Then in another terminal: sudo nmcli device connect enx001122334455 Look for: USB resets, link down/up loops, tx timeout, firmware errors, Failed to read reg index, device descriptor read error. On Raspberry Pi 4, repeated resets usually mean: insufficient USB power, unstable USB3 negotiation, bad cable/hub. A VERY common fix for AX88179 on Pi 4 is forcing USB2 mode temporarily. Edit: sudo nano /boot/firmware/config.txt Add: dtoverlay=dwc2,dr_mode=host Then reboot. Also test: black USB2 port instead of blue USB3, powered USB hub, official Pi PSU. Another important fix: Install missing firmware/modules: sudo apt update sudo apt install linux-modules-extra-raspi linux-firmware Then reboot. If the interface exists but cannot be activated, also check whether MAC address randomization is breaking it: sudo nano /etc/NetworkManager/conf.d/no-random.conf Add: [device] wifi.scan-rand-mac-address=no Restart NM: sudo systemctl restart NetworkManager Most useful outputs now: ip link ethtool -i <interface> nmcli device journalctl -k -b | tail -100 Especially the ethtool -i result — that tells whether the correct ASIX driver is actually controlling the adapter. Check step-by-step whether the ASIX USB Ethernet adapter is: detected by USB, attached to the correct driver, visible to NetworkManager, blocked by firmware/power issues. 1. Check USB detection Run: lsusb You should see something like: 0b95:1790 ASIX Electronics Corp. AX88179 If you do NOT see ASIX: the Pi does not detect the hardware, this is USB/power/cable/hub related, not NetworkManager. 2. Check whether the ASIX driver is loaded Run: lsmod | grep ax88179 Expected: ax88179_178a usbnet mii If nothing appears, load manually: sudo modprobe ax88179_178a Then verify: lsmod | grep ax88179 3. Check whether the Ethernet interface exists Run: ip link Look for something like: enx001122334455 or: eth1 If NO new interface appears: driver failed, or USB resets are happening. Check logs: sudo dmesg | grep -Ei 'ax88179|usb|eth' 4. Check which driver controls the adapter Replace the interface name below with yours. Example: ethtool -i enx001122334455 Expected: driver: ax88179_178a If it says: cdc_ncm usbnet or anything else, then the wrong driver attached. Fix: sudo modprobe -r cdc_ncm sudo modprobe -r usbnet sudo modprobe ax88179_178a Then unplug/replug the adapter. 5. Check whether NetworkManager sees it Run: nmcli device You should see something like: DEVICE TYPE STATE enx001122334455 ethernet disconnected Possible states: State Meaning disconnected good, detected unavailable driver/link issue unmanaged NM ignoring device unavailable USB/driver problem 6. Enable the interface in NetworkManager Replace with your interface name: sudo nmcli device set enx001122334455 managed yes Then: sudo nmcli device connect enx001122334455 If successful: Device successfully activated 7. If NetworkManager says “device unavailable” Bring interface UP manually: sudo ip link set enx001122334455 up Then retry: sudo nmcli device connect enx001122334455 8. Check firmware/modules installed on Ubuntu Pi Install missing packages: sudo apt update sudo apt install linux-modules-extra-raspi linux-firmware usbutils ethtool Then reboot: sudo reboot 9. Watch live logs while enabling Open terminal 1: sudo journalctl -kf Open terminal 2: sudo nmcli device connect enx001122334455 Watch for: USB reset errors, disconnect/reconnect loops, tx timeout, power errors. 10. VERY common Raspberry Pi 4 fix Try: black USB2 port instead of blue USB3, powered USB hub, official Raspberry Pi PSU. AX88179 adapters often fail on Pi 4 USB3 power negotiation. 11. Force NetworkManager to manage all ethernet devices Edit: sudo nano /etc/NetworkManager/NetworkManager.conf Ensure this exists: [main] plugins=ifupdown,keyfile [ifupdown] managed=true Save. Restart NM: sudo systemctl restart NetworkManager 12. Final diagnostic command Run this full command and paste output if still broken: echo "=== LSUSB ==="; lsusb; echo "=== DRIVER ==="; lsmod | grep ax88179; echo "=== IP LINK ==="; ip link; echo "=== NMCLI ==="; nmcli device; echo "=== DMESG ==="; sudo dmesg | tail -50 That will identify exactly where the failure happens. ** Description changed: Hi The usb 3.0 asix 88179 driver did not work and no driver available with Ubuntu desktop and Ubuntu server 24.04.5 that need to be fix. - The network settings cannot seems to work. And need to be fix - immediately. + The network settings cannot seems to work. The usb asix 88179 ethernet + option cannot be enable to turn on via the gnome gui network settings. + And need to be fix immediately. This also cannot work on raspberry pi SBC computer. Currently i am running on Raspberry pi 4. Can you guys please fix the problem immedaiately. The old kernel the asix88179_178a driver reside at /lib/modules/5.15.0-1061-raspi/kernel/drivers/net/usb/asix88179_178.ko Once do the ubuntu software upgrade the new kernel for driver ax88179_178a driver reside at /lib/modules/5.15.0-1098-raspi/kernel/drivers/net/usb/88179_178a.ko - Thank you. Regards Rusli -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2151736 Title: asix 88179_178a driver not detected with ubuntu 24.04.5 for both ubuntu server and ubuntu desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2151736/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
