[Help]: probe with driver mt7925u failed with error -110 (Netgear A9000, works after unplug/plug)

[gsicilia82]

Checklist

• I acknowledge that support is provided on a best-effort basis.
• I acknowledge that the authors and contributors to this repository cannot be held responsible for the results of my use of any information contained in or linked from this repository.

uname

Linux slimbook 6.18.1-061801-generic #202512121839 SMP PREEMPT_DYNAMIC Fri Dec 12 19:19:06 UTC 2025 x86_64 GNU/Linux

lsusb

Bus 008 Device 007: ID 0846:9072 NetGear, Inc. Wireless_Device

rfkill

0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no 2: phy2: Wireless LAN Soft blocked: no Hard blocked: no

dkms

---

iw

phy#2
        Interface wlx289401bca631
                ifindex 8
                wdev 0x200000001
                addr 28:94:01:bc:a6:31
                ssid Unifi52
                type managed
                channel 36 (5180 MHz), width: 160 MHz, center1: 5250 MHz
                txpower 3.00 dBm
                multicast TXQ:
                        qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                        0       0       0       0       0       0       0       0               0
phy#1
        Unnamed/non-netdev interface
                wdev 0x100000002
                addr 20:0d:3d:9c:70:9b
                type P2P-device
        Interface wlp2s0
                ifindex 2
                wdev 0x100000001
                addr 20:0d:3d:9c:70:9b
                type managed
                multicast TXQ:
                        qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                        0       0       0       0       0       0       0       0               0

What happened?

Hello again, after getting to work 6GHz connections, I focused on the issue, that the Netgear A9000 is not directly working after boot. Only with unplug / plug-in again it is loaded and works well. Also booting without dongle and plug-in after boot process works. However, how can I get it to work immediatley during boot process?

During boot, I get this error message into dmesg:

[    2.505608] usb 8-1.3: reset SuperSpeed USB device number 4 using xhci_hcd
[    2.535797] input: HD-Audio Generic HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:08.1/0000:04:00.1/sound/card0/input9
[    2.535908] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:04:00.6/sound/card1/input12
[    2.535962] input: HD-Audio Generic HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:08.1/0000:04:00.1/sound/card0/input10
[    2.569670] mhi mhi0: Wait for device to enter SBL or Mission mode
[    2.744721] mt7925u 8-1.3:1.0: probe with driver mt7925u failed with error -110

With Google / Gemini / ChatGPT and Grok, I tested different methods:

• usbreset device after boot
• unbind/bind device after boot
• blacklist driver and load manually after boot
• disable USB autosuspend
• Power Off/On USB-Hub with uhubctl

It doesn't matter, what I tested usually after loading the driver, I get same error as shown above. Only unplug and re-plug the device helps. I get same issue on boot, when the device is connected directly on Notebook instead to the USB-Hub.

How can I solve this issue? The device is conncted on my usb-hub and I decided to plug-in the whole switch after boot, this works too. However, I would prefer to solve this issue in a "clean" way.

[morrownr]

Hi @gsicilia82

I have seen similar reports over the years with adapters with different chips and drivers. It is not common but it happens. I suspect a timing issue. Here is a link to the Main Menu:

https://github.com/morrownr/USB-WiFi

Scroll down to the end, under number 12, and click on:

USB Ports can be a source of problems with USB WiFi adapters

That file contains a lot of information. Recommend that you work your way through the file and try one change at a time followed by a reboot to see if the change helps. If it does not help, then revert and try another. Let me know how it goes.

[afreakk]

I've got the same issue with the same A9000, did you find a workaround that fixed it for you?

[gsicilia82]

Unfortunately, I could not solve it.

[bjlockie]

Turn off scatter gather.

[afreakk]

Turn off scatter gather.

How do you do that? The interface never appears (after a boot, it does after plugging out and in again)

[morrownr]

Hi @afreakk

I assume you looked at the USB Ports... document that I listed above.

With that said, let's see what happens when you unload and reload the driver after boot:

The driver name is mt7925u for the following:

To unload a driver in Linux, use the command sudo modprobe -r <module_name>, and to reload it, use sudo modprobe <module_name>. Make sure to replace <module_name> with the actual name of the driver you want to manage.

If you see consistent good results with the above then we can see up a little script to run on boot.

[afreakk]

I've tried 2 different USB-ports, will try another.
Don't have a screen on the server im trying to use the wifi-adapter on, so havent done any BIOS changes yet.

When doing the modprobe i get the following output in dmesg:

[10311.340374] usbcore: deregistering interface driver mt7925u
[10320.698210] usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
[10320.931617] mt7925u 2-2:1.0: probe with driver mt7925u failed with error -110
[10320.931715] usbcore: registered new interface driver mt7925u

[morrownr]

@afreakk

Time to dig deeper.

Could this be related to the mt7925 firmware? Yes, but that is only one possibility. However, Mediatek released new
firmware files in November and then again in December. That is a hint that something urgent happened. I have a guide
on the Main Menu for updating firmware. Here is a direct link:

https://github.com/morrownr/USB-WiFi/blob/main/home/How_to_Install_Firmware_for_Mediatek_based_USB_WiFi_adapters.md

Let me know if that helps.

Also, I try to be careful with using AI as it/they make a lot of mistakes when it comes to computer stuff but I think this
reply is worth posting:

In Linux-based systems, a "probe with driver [name] failed with error -110" message typically indicates a
connection timeout (ETIMEDOUT). This means the kernel driver tried to communicate with a hardware
device, but the device did not respond within the expected timeframe. 

Common Causes
Hardware Unresponsiveness: The device (e.g., a Wi-Fi card, USB controller, or GPU) is in a "stuck" power
state or has failed.

Insufficient Power: The device isn't receiving enough power to complete its initialization handshake.

Firmware Mismatch: The loaded firmware is incompatible with the current hardware revision or kernel version.

Fast Boot/Hibernation Issues: If dual-booting with Windows, the "Fast Startup" feature can leave
hardware in a state that Linux cannot properly re-initialize. 

Recommended Troubleshooting Steps

Perform a Cold Boot: Shut down the computer completely, unplug the power cable (and remove the
battery if possible), then hold the power button for 30 seconds to drain residual electricity. This often
resets hardware that has entered an unresponsive state.

Disable Windows Fast Startup: If you have a Windows partition, disable "Fast Startup" in Control Panel
> Power Options > Choose what the power buttons do. This ensures the hardware is fully released for
the Linux driver to probe.

Check BIOS/UEFI Settings:

Ensure Secure Boot is disabled if you are using third-party or proprietary drivers (like NVIDIA).

Look for "Above 4G Decoding" or "PCIe Generation" settings and try toggling them if the error persists.

Verify Firmware/Kernel Compatibility: Run dmesg | grep -i error to see if there are associated messages
about missing firmware files (e.g., .bin files for Wi-Fi or Bluetooth).

Try a Different Kernel: If the error started after a system update, try booting into an older kernel version
from the GRUB boot menu to see if the issue is a regression in the new driver. 

[morrownr]

@afreakk

Hold on...

I was just able to duplicate this. Yes, I have a Netgear A9000.

How I duplicated it was by updating the mt7925 firmware on one of my testing machines. The current version of the firmware, which is what I updated to, is 20251210. The version that was working fine was dated July. Do you know how to back up to the July version?

Yes, this is something that needs to be reported and I can handle that once we have confirmed the situation.

[morrownr]

Well, the July version is working right now. I am out of time to work this for now. Hope to continue when able.

[gsicilia82]

I checked my firmware with current modprobe issue:

ethtool -i wlx289401bca631:

driver: mt7925u
version: 6.18.1-061801-generic
firmware-version: ____000000-20250721232943
expansion-rom-version: 
bus-info: 8-1.3:1.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

Then, I updated to latest firmware to check if something changes. With current files from repo, I updated to version ____000000-20251210093025. However, I get same modprobe -110 issue during boot or with modprobe -r mt7925u as before. Nothing changed for me by updating fw as I was already running on July version.

Now, I will try the thing with scatter gather...

[gsicilia82]

mt7925u has no option related to scatter-gather. Gemini recommended to disable this option on "base" module mt76_usb. Disabling scatter gather on this module changed nothing, still same issue on boot or after reloading module...

My "way" to disable scatter-gather:
sudo nano /etc/modprobe.d/mt7925u.conf
enter
options mt76_usb disable_usb_sg=1

sudo update-initramfs -u
reboot

[afreakk]

For me it seems to work after reboot when i used this firmware:

[nix-shell:~]# ethtool -i wlp0s20f0u4
driver: mt7925u
version: 6.12.63
firmware-version: ____000000-20250526153043
expansion-rom-version:
bus-info: 2-4:1.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

But I had to replug after first reboot after this firmware was used. but then subsequent reboots worked

Edit: No, wait, I dont think it did. it was only cause i was using poweroff, not reboot that it worked

[morrownr]

@afreakk

This is strange. I had never had a problem here on several systems and then I decided to try some things to see if I could help with this issue now I can't fix this on the test system.

When this happens I see a line in dmesg that ends with -110 which, if I remember correctly, that means a response is not happening in time.

We have some non-Mediatek devs that are doing a real shakedown of the mt7925u driver right now as you can see at:

https://patchwork.kernel.org/project/linux-wireless/list/?series=&submitter=&state=*&q=mt76&archive=both&delegate=

I don't have time right now but maybe in a week, I may try some of those patches to see if there is a fix in there.

[uxsoft]

I have the same issue, I've tried to change the USB settings based on the guide linked and didn't help.