You are not logged in.
lsmod | grep 7925
cat /proc/cmdline
There's no way the module gets loaded if it's actually in the module_blacklist
Offline
lsmod | grep 7925 cat /proc/cmdline
There's no way the module gets loaded if it's actually in the module_blacklist
Nothing shows up for lsmod.
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=32067a24-7d1c-4c31-95d6-c78e9cd84779 rw rootflags=subvol=@ cryptdevice=UUID=421b087a-ffd0-4f74-aee6-8585a71e6ef4:root rootfstype=btrfs loglevel=3 acpi_enforce_resources=lax clearcpuid=514 module_blacklist=mt7925e
I can turn on BT in my DE and it begins to function and am able to connect to it.
dmsg logs after enabling in DE:
[32061.141656] Bluetooth: hci0: HW/SW Version: 0x00000000, Build Time: 20241104133214
[32063.010327] Bluetooth: hci0: Device setup in 1836990 usecs
[32063.010332] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[32063.184452] Bluetooth: hci0: AOSP extensions version v1.00
[32063.184459] Bluetooth: hci0: AOSP quality report is supported
I also connected a BT controller to it.
I figured the DE BT gui would not see any BT devices or the device would not even function. Ah well-- I'll just make sure that BT is disabled in the DE.
Last edited by archbusby (2024-12-29 03:41:56)
Offline
lspci -knn
lsusb -tv
Offline
lspci -knn lsusb -tv
lspci -knn:
https://0x0.st/8sVf.txt
09:00.0 Network controller [0280]: MEDIATEK Corp. Device [14c3:7925]
Subsystem: Foxconn International, Inc. Device [105b:e112]
Kernel modules: mt7925e
cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=32067a24-7d1c-4c31-95d6-c78e9cd84779 rw rootflags=subvol=@ cryptdevice=UUID=421b087a-ffd0-4f74-aee6-8585a71e6ef4:root rootfstype=btrfs module_blacklist=mt7925e loglevel=3 acpi_enforce_resources=lax clearcpuid=514
lsusb -tv:
http://0x0.st/8sVO.txt
Last edited by archbusby (2024-12-29 17:27:42)
Offline
mt7925e isn't used, but your bluetooth is
|__ Port 009: Dev 003, If 0, Class=Wireless, Driver=btusb, 480M
ID 0489:e124 Foxconn / Hon Hai
|__ Port 009: Dev 003, If 1, Class=Wireless, Driver=btusb, 480M
ID 0489:e124 Foxconn / Hon Hai
|__ Port 009: Dev 003, If 2, Class=Wireless, Driver=btusb, 480M
ID 0489:e124 Foxconn / Hon Hai
which was recently added to mt7925, https://www.spinics.net/lists/linux-blu … 15985.html
Try
module_blacklist=btusb
Offline
mt7925e isn't used, but your bluetooth is
module_blacklist=btusb
Does this disable all bluetooth devices that use this driver?
I'm thinking it does...
here is the device when plugged in via USB:
/: Bus 007.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
|__ Port 001: Dev 005, If 0, Class=Hub, Driver=hub/4p, 480M
ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
|__ Port 001: Dev 006, If 0, Class=Wireless, Driver=btusb, 12M
ID 2357:0604 TP-Link
|__ Port 001: Dev 006, If 1, Class=Wireless, Driver=btusb, 12M
ID 2357:0604 TP-Link
Offline
Does this disable all bluetooth devices that use this driver?
Yes - wasn't that the point?
Offline
Does this disable all bluetooth devices that use this driver?
Yes - wasn't that the point?
I was trying to disable the mt7925e, only.
Offline
Are you actually sure you're using the mt7925e based one (assuming you've multiple and mt7925e is blocked)?
Do you still have freezes after suspending the system?
rfkill
Offline
Are you actually sure you're using the mt7925e based one (assuming you've multiple and mt7925e is blocked)?
Do you still have freezes after suspending the system?rfkill
I've been only troubleshooting with one. After you suggested blacklisting btusb, I started using the USB dongle.
rfkill:
ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 blocked unblocked
this is with mt7925e blacklisted.
When I plugin the usb BT dongle:
ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 blocked unblocked
1 bluetooth hci1 unblocked unblocked
interestingly enough, blueberry only functions on the hci0 device. So, if i
rfkill block 0
the BT gui disables and doesn't interact with the hci1 device.
Maybe I need a different bluetooth manager. My DE is cinammon.
With hci0 blocked (mt7925e) and hci1 unblocked, suspend works fine.
Last edited by archbusby (2024-12-31 17:13:46)
Offline
See whether https://www.projectgus.com/2014/09/blac … rom-linux/ rids you of the undesired device (w/o blacklisting btusb, but you'll probably still have to blacklist mt7925e)
Offline
See whether https://www.projectgus.com/2014/09/blac … rom-linux/ rids you of the undesired device (w/o blacklisting btusb, but you'll probably still have to blacklist mt7925e)
Thanks for the link, seth. That is something to save for later.
I created a rules file with the following line:
# MT8725e should be disabled
# 09:00.0 Network controller [0280]: MEDIATEK Corp. Device [14c3:7925]
# Subsystem: Foxconn International, Inc. Device [105b:e112]
# Kernel modules: mt7925e
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", ATTRS{idProduct}=="e124", ATTR{authorized}="0"
I also removed the blacklist in the kernel command line.
The bt device no longer shows up when using rfkill, udevadm, or lsusb -tv.
Now, I need to figure out what happened to the wi-fi side of the MT7925 device. It used to work in previous kernel versions (6.12.1) and now it is considered to be unclaimed. It used to be functional when I installed this motherboard as I needed to downloard the rt8125 drivers for the ethernet chipset (November 2024).
So, something screwing going on, now that the driver is missing. Maybe this'll get resolved in 6.13?
*-network UNCLAIMED
description: Network controller
product: MEDIATEK Corp.
vendor: MEDIATEK Corp.
physical id: 0
bus info: pci@0000:09:00.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm cap_list
configuration: latency=0
resources: memory:dca00000-dcbfffff memory:dcc00000-dcc07fff
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8125
v: 9.014.01-NAPI port: e000 bus-ID: 08:00.0
IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: MEDIATEK vendor: Foxconn driver: N/A port: N/A bus-ID: 09:00.0
Offline
Now, I need to figure out what happened to the wi-fi side of the MT7925 device.
lspci -k
lsmod | grep mt7925e
mpdprobe -v mt7925e
mpdprobe -c | grep -v alias | grep mt7925e
Offline
Now, I need to figure out what happened to the wi-fi side of the MT7925 device.
lspci -k lsmod | grep mt7925e mpdprobe -v mt7925e mpdprobe -c | grep -v alias | grep mt7925e
I got it working. Thanks. I forgot I had a blacklist file in modprobe.d. The last command reminded me that I did that.
Offline
Kernel 6.12.8 seems to have resolved the BT issue.
Offline
Kernel 6.12.8 seems to have resolved the BT issue.
Can confirm. With 6.12.8, wake from Sleep working again with BT enabled.
Offline