[SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

skiwi · 2025-06-20 12:08:59

Background
I am using a Minisforum AI X1 Pro mini-PC with an integrated Mediatek MT7925 Wi-Fi/Bluetooth card. The Wi-Fi functionality works under GNOME NetworkManager, it is very slow (see same issue here, https://bbs.archlinux.org/viewtopic.php?id=300490). Bluetooth is not working at all. The same hardware works fine on Windows. To quickly install Arch, I actually jus swapped the SSD from my laptop to this new mini PC.

System Details:

OS: Arch Linux (fully updated with pacman -Syu)
Kernel Version: 6.15.2-arch1-1
Desktop Environment: GNOME with NetworkManager
Device: Mediatek MT7925 (PCIe)

Relevant Terminal Outputs:

PCIe device recognized and using correct kernel module

% sudo lspci -k | grep -A 3 -i mediatek
pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted
c3:00.0 Network controller: MEDIATEK Corp. Device 7925
Subsystem: Quectel Wireless Solutions Co., Ltd. Device 8005
Kernel driver in use: mt7925e
Kernel modules: mt7925e

bluetooth service running

● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Fri 2025-06-20 14:49:45 CEST; 51min ago
Invocation: eea2f931004d4547bfca790b76807121
Docs: man:bluetoothd(8)
Main PID: 8604 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 28251)
Memory: 708K (peak: 2.1M)
CPU: 19ms
CGroup: /system.slice/bluetooth.service
└─8604 /usr/lib/bluetooth/bluetoothd
Jun 20 14:49:45 legion systemd[1]: Starting Bluetooth service...
Jun 20 14:49:45 legion bluetoothd[8604]: Bluetooth daemon 5.83
Jun 20 14:49:45 legion systemd[1]: Started Bluetooth service.
Jun 20 14:49:45 legion bluetoothd[8604]: Starting SDP server
Jun 20 14:49:45 legion bluetoothd[8604]: Bluetooth management interface 1.23 initialized

Bluetooth controller missing a controller device

% bluetoothctl info
Missing device address argument
No default controller available

Question
Has anyone else successfully used the Mediatek MT7925 Bluetooth on Arch Linux and can share some insight ? How can I better debug this ? Are there kernel parameters or bios settings I should look into ?

Related Posts

See this post (I started a new one because it's labeled SOLVED because some switched to different hardware)
https://bbs.archlinux.org/viewtopic.php?id=300490
Is it a buggy driver update ?
https://bbs.archlinux.org/viewtopic.php?id=305794
Someone seems to have it working but I don't see much detail on this page.
https://wiki.archlinux.org/title/ASUS_Zenbook_UM5606

Any help or guidance would be greatly appreciated. Thank you in advance!

Last edited by skiwi (2025-07-01 11:46:35)

Sander · 2025-06-20 23:59:46

I'm in the same boat. My ASRock Nova X870E WiFi motherboard has the same MediaTek MT7925 WiFi adapter, which is supposed to also provide bluetooth.

WiFi is actually working fine for me (not slow at all), but there is no trace of any kind of bluetooth support, it's as if it doesn't exist.

I'm on the same kernel (6.15.2-arch1-1), also with GNOME + NetworkManager, on a fresh Arch install (a few days old).

Thanks for sharing the related posts, I've been digging into this as well, but with no tangible results so far. Luckily I also have a USB dongle, which I'm using instead for now.

skarp · 2025-06-21 21:03:20

same issue errors:
archlinux-pc kernel: usb 3-7: device descriptor read/64, error -71
archlinux-pc kernel: usb 3-7: device not accepting address 9, error -71
archlinux-pc kernel: usb 3-7: device not accepting address 10, error -71
archlinux-pc kernel: Bluetooth: hci1: HW/SW Version: 0x00000000, Build Time: 20250526153203
archlinux-pc kernel: Bluetooth: hci1: Execution of wmt command timed out
archlinux-pc kernel: Bluetooth: hci1: Failed to send wmt patch dwnld (-110)
archlinux-pc kernel: Bluetooth: hci1: Failed to set up firmware (-110)
archlinux-pc kernel: Bluetooth: hci1: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.

camlperr · 2025-06-23 14:53:41

Have this card, and it is not the first issue I have seen with it. Intending to experiment with different cards soon. However, I can report that this Bluetooth issue in particular only began in Linux 6.15.2. Rolling back to 6.15.1 resolved the issue, or has seemed to (I do not reboot very often). Have not yet tried 6.15.3.

skiwi · 2025-06-24 19:03:01

The last system update may have solved this. There have been quite some updates to mediatek drivers on the kernel about 5 days ago before 6.15.3.
https://git.kernel.org/pub/scm/linux/ke … p&q=mt7925

Note the message on the archlinux front page about manual intervention.

Update: After reboot, still the same issue.

% uname -r
6.15.3-arch1-1

Via Ethernet I get 3.0 Gbps, via Mediatek / Wifi I get 10 Mbps and no bluetooth.

Last edited by skiwi (2025-06-24 19:17:35)

nealxm · 2025-06-25 17:54:23

I am also on a minisforum pc using the latest kernel having issues with both bluetooth and wifi.

Sander · 2025-06-29 17:26:59

Sander wrote:

I'm in the same boat. My ASRock Nova X870E WiFi motherboard has the same MediaTek MT7925 WiFi adapter, which is supposed to also provide bluetooth.

FWIW, this is now working as intended for me on 6.15.4-arch2-1.

Afmer · 2025-06-29 20:16:42

I was helped with the problem by this comment
https://www.reddit.com/r/archlinux/comm … are_button

Wyllas · 2025-06-30 01:47:16

Afmer wrote:

I was helped with the problem by this comment
https://www.reddit.com/r/archlinux/comm … are_button

I was very skeptic, but it worked after trying many other things.

I also had multiple (around 5) "device descriptor read/64 error -110" on boot and theyre all gone now.

TLDR: Unplugged the desktop, waited 10s, plugged it back and there was no more errors.

Last edited by Wyllas (2025-06-30 01:47:53)

seth · 2025-06-30 08:01:31

This is actually somewhat normal for MT, you're forcing a hard reset of the chip, but @skiwi also

The same hardware works fine on Windows.

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

And please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

qlum · 2025-06-30 20:16:40

Not on a laptop but stumbled upon this thread.
Can confirm it works, unplug the power for 10 seconds, Bluetooth will work again. (Will say in my case did not use Windows in 2025 at all)

Last edited by qlum (2025-06-30 20:17:36)

skiwi · 2025-07-01 01:44:12

This doesn't seem to work yet for me. I think the error is different in my case. Main error message seems to be "Bluetooth: hci0: Opcode 0x0c03 failed: -16". I don't see any timeouts.

Updated the system, did many reboots, disabled window fast-start, left the device unplugged for a full night but still no BT.

% bluetoothctl power on
No default controller available
% sudo dmesg | grep -i hci0
[    4.805648] Bluetooth: hci0: Opcode 0x0c03 failed: -16
% sudo modprobe -r btusb; sleep 1; sudo modprobe btusb                                     
% sudo dmesg | grep -i hci0                           
[    4.805648] Bluetooth: hci0: Opcode 0x0c03 failed: -16
[   70.838620] Bluetooth: hci0: Opcode 0x0c03 failed: -16
% uname -r
6.15.4-arch2-1

% inxi -Na -E
Network:
  Device-1: MEDIATEK vendor: Quectel Wireless Solutions driver: mt7925e
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: c3:00.0
    chip-ID: 14c3:7925 class-ID: 0280
  Device-2: Realtek RTL8125 2.5GbE driver: r8169 v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: f000 bus-ID: c4:00.0 chip-ID: 10ec:8125
    class-ID: 0200
  Device-3: Realtek RTL8125 2.5GbE driver: r8169 v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: e000 bus-ID: c5:00.0 chip-ID: 10ec:8125
    class-ID: 0200
  Device-4: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1.3:4
    chip-ID: 0bda:8153 class-ID: 0000 serial: 001000001
Bluetooth:
  Device-1: Quectel Wireless Solutions Wireless_Device driver: btusb v: 0.8
    type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:4
    chip-ID: 2c7c:7009 class-ID: e001 serial: 000000000
  Report: btmgmt ID: hci0 rfk-id: 5 state: up address: N/A

I think it may be the device ID is not listed in the btusb.c kernel module and may simply not be supported yet.

I don't see this chip-id in btusb.c https://git.kernel.org/pub/scm/linux/ke … ?h=v6.15.4

A fix like this might work

https://forum.endeavouros.com/t/mediate … d/39841/26

Last edited by skiwi (2025-07-01 02:22:33)

seth · 2025-07-01 06:52:18

16 is however EBUSY… please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

skiwi · 2025-07-01 07:45:56

http://0x0.st/80rb.txt

seth · 2025-07-01 08:13:32

Jul 01 09:36:01 legion kernel: usb 3-5: new high-speed USB device number 4 using xhci_hcd
Jul 01 09:36:01 legion kernel: usb 3-5: New USB device found, idVendor=2c7c, idProduct=7009, bcdDevice= 1.00
Jul 01 09:36:01 legion kernel: usb 3-5: New USB device strings: Mfr=5, Product=6, SerialNumber=7
Jul 01 09:36:01 legion kernel: usb 3-5: Product: Wireless_Device
Jul 01 09:36:01 legion kernel: usb 3-5: Manufacturer: MediaTek Inc.
Jul 01 09:36:01 legion kernel: usb 3-5: SerialNumber: 000000000
…
Jul 01 09:36:01 legion systemd[1]: Finished Remount Root and Kernel File Systems.
…
Jul 01 09:36:02 legion kernel: Bluetooth: Core ver 2.22
…
Jul 01 09:36:02 legion systemd[1]: Starting Load/Save RF Kill Switch Status...
Jul 01 09:36:02 legion kernel: usbcore: registered new interface driver btusb
Jul 01 09:36:02 legion kernel: Bluetooth: hci0: Opcode 0x0c03 failed: -16
…
Jul 01 09:36:02 legion kernel: mt7925e 0000:c3:00.0: HW/SW Version: 0x8a108a10, Build Time: 20250526152947a
Jul 01 09:36:02 legion kernel: mt7925e 0000:c3:00.0: WM Firmware Version: ____000000, Build Time: 20250526153043

Seems BT fails before mt7925e loads - does it help to move mt7925e into the initramfs to maybe get it to load earlier?

Does your logitech dongle operate in BT mode?

skiwi · 2025-07-01 08:35:31

Interesting catch about the dongle. I've changed the replaced the logitech USB dongle (for a mouse while lacking BT) with a wired mouse and added mt7925e to initramfs.
Bluetooth is still failing with the same error though.

https://0x0.st/80r_.txt

seth · 2025-07-01 09:04:22

Yup, you'lll likely be waiting for https://lists.openwall.net/linux-kernel/2025/06/06/739 to hit.

skiwi · 2025-07-01 11:46:01

That should be it. It seems that's on the master branch of the BT kernel driver since June 12th.
I'll close this topic as resolved, I expect this will come out soon with the next update of btusb.

https://git.kernel.org/pub/scm/linux/ke … t.git/log/

embrangler · 2025-07-01 17:12:54

Hey all,

I am not on archlinux, as I'm on another linux distro. I was watching this thread as I have the same chip (pid/vid 2c7c/7009)

I was able to resolve my issue today using this repo - https://github.com/dekomote/btusb-mt792 … 3024861567

It would be nice if the next update of btusb comes soon, but meanwhile I hope this helps others!

nealxm · 2025-07-09 17:54:05

my apologies for continuing the discussion after it's been marked solved. i am still having trouble with my mt7925e, both bluetooth and wifi. here is my `journalctl -b` output: http://0x0.st/8Ghh.txt

i've tried adding all the firmware manually to `/usr/lib/firmware/mediatek/mt7925` but i'm not sure how to update btusb.

my apologies again if i have misunderstood anything in this thread, thanks in advance for your time

seth · 2025-07-10 16:31:48

Wifi looks ok?

Jul 09 11:08:37 kepler systemd-networkd[514]: eth0: Interface name change detected, renamed to enp194s0.
Jul 09 11:08:37 kepler systemd-networkd[514]: enp194s0: Configuring with /etc/systemd/network/20-wired.network.
Jul 09 11:08:37 kepler systemd-networkd[514]: enp194s0: Link UP
Jul 09 11:08:37 kepler kernel: mt7925e 0000:c1:00.0: enabling device (0000 -> 0002)
Jul 09 11:08:37 kepler kernel: mt7925e 0000:c1:00.0: ASIC revision: 79250000
Jul 09 11:08:37 kepler kernel: mt7925e 0000:c1:00.0: HW/SW Version: 0x8a108a10, Build Time: 20250526152947a
Jul 09 11:08:37 kepler kernel: mt7925e 0000:c1:00.0: WM Firmware Version: ____000000, Build Time: 20250526153043
Jul 09 11:08:38 kepler systemd[1]: Listening on GnuPG network certificate management daemon for /etc/pacman.d/gnupg.
Jul 09 11:08:38 kepler iwd[678]: Wireless daemon version 3.9
Jul 09 11:08:38 kepler iwd[678]: station: Network configuration is disabled.
Jul 09 11:08:38 kepler systemd[1]: Reached target Network.
Jul 09 11:08:38 kepler systemd[794]: Listening on GnuPG network certificate management daemon.
Jul 09 11:08:38 kepler iwd[678]: Wiphy: 0, Name: phy0
Jul 09 11:08:38 kepler iwd[678]:         Permanent Address: b4:2f:03:ab:82:f0
Jul 09 11:08:38 kepler iwd[678]:         2.4GHz Band:
Jul 09 11:08:38 kepler iwd[678]:                 Bitrates (non-HT):
Jul 09 11:08:38 kepler iwd[678]:                          1.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                          2.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                          5.5 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         11.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                          6.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                          9.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         12.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         18.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         24.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         36.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         48.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         54.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                 HT Capabilities:
Jul 09 11:08:38 kepler iwd[678]:                         HT40
Jul 09 11:08:38 kepler iwd[678]:                         Short GI for 20Mhz
Jul 09 11:08:38 kepler iwd[678]:                         Short GI for 40Mhz
Jul 09 11:08:38 kepler iwd[678]:                 HT RX MCS indexes:
Jul 09 11:08:38 kepler iwd[678]:                         0-15
Jul 09 11:08:38 kepler iwd[678]:                 HE Capabilities
Jul 09 11:08:38 kepler iwd[678]:                         Interface Types: ap
Jul 09 11:08:38 kepler iwd[678]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Interface Types: station
Jul 09 11:08:38 kepler iwd[678]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:         5GHz Band:
Jul 09 11:08:38 kepler iwd[678]:                 Bitrates (non-HT):
Jul 09 11:08:38 kepler iwd[678]:                          6.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                          9.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         12.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         18.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         24.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         36.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         48.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         54.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                 HT Capabilities:
Jul 09 11:08:38 kepler iwd[678]:                         HT40
Jul 09 11:08:38 kepler iwd[678]:                         Short GI for 20Mhz
Jul 09 11:08:38 kepler iwd[678]:                         Short GI for 40Mhz
Jul 09 11:08:38 kepler iwd[678]:                 HT RX MCS indexes:
Jul 09 11:08:38 kepler iwd[678]:                         0-15
Jul 09 11:08:38 kepler iwd[678]:                 VHT Capabilities:
Jul 09 11:08:38 kepler iwd[678]:                         160 Mhz operation
Jul 09 11:08:38 kepler iwd[678]:                         Short GI for 80Mhz
Jul 09 11:08:38 kepler iwd[678]:                         Short GI for 160 and 80 + 80 Mhz
Jul 09 11:08:38 kepler iwd[678]:                         Max RX MCS: 0-9 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max TX MCS: 0-9 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                 HE Capabilities
Jul 09 11:08:38 kepler iwd[678]:                         Interface Types: ap
Jul 09 11:08:38 kepler iwd[678]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Interface Types: station
Jul 09 11:08:38 kepler iwd[678]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:         6GHz Band:
Jul 09 11:08:38 kepler iwd[678]:                 Bitrates (non-HT):
Jul 09 11:08:38 kepler iwd[678]:                          6.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                          9.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         12.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         18.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         24.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         36.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         48.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                         54.0 Mbps
Jul 09 11:08:38 kepler iwd[678]:                 HE Capabilities
Jul 09 11:08:38 kepler iwd[678]:                         Interface Types: ap
Jul 09 11:08:38 kepler iwd[678]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Interface Types: station
Jul 09 11:08:38 kepler iwd[678]:                         Max HE RX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE TX <= 80MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE RX <= 160MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:                         Max HE TX <= 160MHz MCS: 0-11 for NSS: 2
Jul 09 11:08:38 kepler iwd[678]:         Ciphers: BIP-CMAC-256 BIP-GMAC-256 BIP-GMAC-128 CCMP-256
Jul 09 11:08:38 kepler iwd[678]:                  GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128
Jul 09 11:08:38 kepler iwd[678]:                  TKIP
Jul 09 11:08:38 kepler iwd[678]:         Supported iftypes: station ap p2p-client p2p-go p2p-device
Jul 09 11:08:38 kepler iwd[678]: udev interface=wlan0 ifindex=3
Jul 09 11:08:39 kepler iwd[678]: event: state, old: disconnected, new: autoconnect_quick
Jul 09 11:08:39 kepler systemd-networkd[514]: wlan0: Link UP
Jul 09 11:08:39 kepler systemd-networkd[514]: wlan0: Configuring with /etc/systemd/network/25-wireless.network.
Jul 09 11:08:39 kepler iwd[678]: udev interface=wlan0 ifindex=4
Jul 09 11:08:39 kepler iwd[678]: event: connect-info, ssid: monkeynet, bss: 4a:af:97:f7:f6:6f, signal: -65, load: 0/255
Jul 09 11:08:39 kepler iwd[678]: event: state, old: autoconnect_quick, new: connecting (auto)
Jul 09 11:08:40 kepler systemd-networkd[514]: wlan0: Connected WiFi access point: monkeynet (4a:af:97:f7:f6:6f)
Jul 09 11:08:40 kepler iwd[678]: event: state, old: connecting (auto), new: connected
Jul 09 11:08:40 kepler systemd-networkd[514]: wlan0: Gained carrier
Jul 09 11:08:40 kepler systemd-networkd[514]: wlan0: DHCPv4 address 192.168.68.65/22, gateway 192.168.68.1 acquired from 192.168.68.1
Jul 09 11:08:40 kepler systemd-timesyncd[491]: Network configuration changed, trying to establish connection.
Jul 09 11:08:41 kepler systemd-networkd[514]: wlan0: Gained IPv6LL
Jul 09 11:08:41 kepler systemd-timesyncd[491]: Network configuration changed, trying to establish connection.
Jul 09 11:08:44 kepler systemd-timesyncd[491]: Network configuration changed, trying to establish connection.

But you've the same BT chip so you'll have to wait fot that patch or try the (unvetted) dkms driver from #19

nealxm · 2025-07-10 23:12:40

I didn't realize the btusb update wasn't out yet, apologies. Where will that update be packaged when it does come out, does running the normal `pacman -Syu` just take care of it?

Yeah WiFi seems fine in the logs, however I only get around 500 KiBps. I have Windows 11 installed on the system in a different partition and it gets around 150 MiBps down. Just curious where the discrepancy is.

seth · 2025-07-11 07:16:59

You'll get the patch once it hits the released kernel.

I have Windows 11 installed on the system in a different partition and it gets around 150 MiBps down. Just curious where the discrepancy is.

I have Windows 11 installed on the system

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

mt7925e.disable_aspm=1

https://wiki.archlinux.org/title/Kernel_parameters

https://wiki.archlinux.org/title/Networ … _interface

And please open a new thread for this (unless it's actually just the hibernating windows)

nealxm · 2025-07-11 13:11:30

i will try all this. thank you so much for your time!

Arch Linux

#1 2025-06-20 12:08:59

[SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#2 2025-06-20 23:59:46

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#3 2025-06-21 21:03:20

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#4 2025-06-23 14:53:41

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#5 2025-06-24 19:03:01

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#6 2025-06-25 17:54:23

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#7 2025-06-29 17:26:59

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#8 2025-06-29 20:16:42

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#9 2025-06-30 01:47:16

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#10 2025-06-30 08:01:31

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#11 2025-06-30 20:16:40

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#12 2025-07-01 01:44:12

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#13 2025-07-01 06:52:18

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#14 2025-07-01 07:45:56

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#15 2025-07-01 08:13:32

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#16 2025-07-01 08:35:31

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#17 2025-07-01 09:04:22

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#18 2025-07-01 11:46:01

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#19 2025-07-01 17:12:54

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#20 2025-07-09 17:54:05

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#21 2025-07-10 16:31:48

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#22 2025-07-10 23:12:40

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#23 2025-07-11 07:16:59

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

#24 2025-07-11 13:11:30

Re: [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

Board footer