Bluetooth not working on Asus B650E-I

Axios

infinitymdm I forgot to ask have you ever tried removing bluez and
shutting down and rebooting reinstalling Bluez then rebooting again. (There is madness to the reboot)

infinitymdm

Axios This is good command puts alot common info in one place.
uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth

Here's the output for that:

marcus@summit ~ $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
Linux summit 6.3.4-237.current #1 SMP PREEMPT_DYNAMIC Sat May 27 21:01:26 UTC 2023 x86_64 GNU/Linux
0a:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I225-V [8086:15f3] (rev 03)
	DeviceName: Intel I225-V LAN
	Subsystem: ASUSTeK Computer Inc. Ethernet Controller I225-V [1043:87d2]
	Kernel driver in use: igc
0b:00.0 Network controller [0280]: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:0616]
	Subsystem: Foxconn International, Inc. MT7922 802.11ax PCI Express Wireless Network Adapter [105b:e0cd]
	Kernel driver in use: mt7921e
0c:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43f7] (rev 01)
Bus 009 Device 002: ID 045e:02fe Microsoft Corp. Xbox Wireless Adapter for Windows
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 002: ID 0493:4170 MAG Technology Co., Ltd ARC AMP DAC
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 003: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 006 Device 002: ID 05e3:0626 Genesys Logic, Inc. Hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 006: ID 0bda:5418 Realtek Semiconductor Corp. BillBoard Device
Bus 005 Device 005: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
Bus 005 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 005 Device 003: ID 7274:0001 richard.titmuss Torn
Bus 005 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 003 Device 002: ID 0b05:1a5c ASUSTek Computer, Inc. USB Audio
Bus 003 Device 005: ID 0489:e0e2 Foxconn / Hon Hai Wireless_Device
Bus 003 Device 004: ID 046d:c539 Logitech, Inc. Lightspeed Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2516:014d Cooler Master Co., Ltd. ARES
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[    6.407362] Bluetooth: Core ver 2.22
[    6.407371] NET: Registered PF_BLUETOOTH protocol family
[    6.407372] Bluetooth: HCI device and connection manager initialized
[    6.407374] Bluetooth: HCI socket layer initialized
[    6.407375] Bluetooth: L2CAP socket layer initialized
[    6.407376] Bluetooth: SCO socket layer initialized
[    6.719830] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.719833] Bluetooth: BNEP socket layer initialized
[    8.482249] Bluetooth: hci0: Opcode 0x c03 failed: -110
[ 1424.106982] Modules linked in: xone_gip_gamepad(O) ff_memless snd_seq_dummy snd_hrtimer snd_seq uvcvideo uvc videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videodev videobuf2_common hid_logitech_hidpp bnep btusb btrtl btbcm btintel bluetooth ecdh_generic hid_logitech_dj snd_hda_codec_hdmi intel_rapl_msr snd_hda_intel mt7921e intel_rapl_common snd_intel_dspcfg mt7921_common snd_usb_audio snd_hda_codec mt76_connac_lib eeepc_wmi asus_nb_wmi edac_mce_amd asus_wmi snd_usbmidi_lib mt76 snd_hda_core xone_dongle(O) kvm_amd snd_rawmidi battery mac80211 xone_gip(O) snd_hwdep snd_seq_device ledtrig_audio kvm snd_pcm joydev sparse_keymap mc irqbypass platform_profile cfg80211 snd_timer wmi_bmof igc snd i2c_designware_pci ptp rfkill i2c_designware_core k10temp libarc4 pps_core soundcore i2c_ccgx_ucsi evdev tpm_crb tpm_tis tpm_tis_core tpm acpi_cpufreq rng_core button sch_fq_codel fuse i2c_dev configfs i2c_piix4 hid_generic usbhid hid amdgpu iommu_v2 drm_buddy gpu_sched drm_ttm_helper ttm i2c_algo_bit drm_display_helper cec
[    0.323518] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.327801] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-7f] only partially covers this bridge
[    4.470616] [drm] Loading DMUB firmware via PSP: version=0x02020017
[    4.470909] [drm] Found VCN firmware Version ENC: 1.26 DEC: 2 VEP: 0 Revision: 0
[    4.470913] amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware
[    4.951518] [drm] Loading DMUB firmware via PSP: version=0x05000500
[    4.951782] [drm] Found VCN firmware Version ENC: 1.24 DEC: 2 VEP: 0 Revision: 0
[    4.951784] amdgpu 0000:0e:00.0: amdgpu: Will use PSP to load VCN firmware
[    6.278388] mt7921e 0000:0b:00.0: WM Firmware Version: ____000000, Build Time: 20230509203655
bluetooth             839680  14 btrtl,btintel,btbcm,bnep,btusb
ecdh_generic           16384  1 bluetooth
rfkill                 40960  8 asus_wmi,bluetooth,cfg80211

Now off to try uninstalling Bluez. Here's hoping something works!

infinitymdm

So, about that Bluez reinstall... seems like it would definitely break my DE. I went for a reinstall instead, but I may give uninstalling a try here in a bit once I work up the courage. Here's what I did:

marcus@summit ~ $ sudo eopkg rm bluez
The following list of packages will be removed
in the respective order to satisfy dependencies:
gvfs-goa budgie-weathershow-applet sdl2-mixer sdl2-ttf ffmpegthumbnailer flatpak picard gnome-session gnome-control-center steam citra budgie-screensaver sdl2-mixer-32bit baobab networkmanager-openconnect gstreamer-1.0-libav budgie-screenshot-applet libwebkit-gtk5 eog libgnome-desktop libadwaita gnome-calendar yuzu gnome-calculator mutter file-roller libgdata gnome-terminal libvte libportal wireplumber sdl2-gfx-32bit sdl2-gfx sdl2-net budgie-control-center libcolord-gtk gnome-online-accounts libwebkit-gtk41 evolution-data-server sdl2-net-32bit networkmanager-openvpn gnome-bluetooth-1-common gnome-bluetooth-1 xdg-desktop-portal qt6-multimedia gnome-bluetooth libgtksourceview5 pipewire-32bit network-manager-applet libnma sdl2-image-32bit sdl2-image ibus libgtk-4 python3-qt5 qt5-connectivity libwebkit-gtk gstreamer-1.0-plugins-bad chromaprint ffmpeg sdl2-ttf-32bit sdl2-32bit sdl2 budgie-desktop-branding-fortitude-plus budgie-desktop-branding-fortitude budgie-desktop-branding budgie-desktop gnome-settings-daemon mpv-libs pipewire bluez 
Do you want to continue? (yes/no)n
Package removal declined
marcus@summit ~ $ sudo eopkg it bluez --reinstall
Total size of package(s): 1.07 MB
Downloading 1 / 1
Package bluez found in repository Unstable
bluez-5.66-42-1-x86_64.eopkg [cached]
Installing 1 / 1
bluez-5.66-42-1-x86_64.eopkg [cached]
Installing bluez, version 5.66, release 42
Extracting the files of bluez
Installed bluez
 [✓] Syncing filesystems                                                success
 [✓] Updating dynamic library cache                                     success
 [✓] Reloading systemd configuration                                    success
 [✓] Updating manpages database                                         success
 [✓] Reloading udev rules                                               success
 [✓] Applying udev rules                                                success

infinitymdm

Ok, didn't take long for me to work up the courage. Uninstalled bluez (and most of my DE with it), rebooted, logged into a non-GUI session, used eopkg to rollback the previous change, and rebooted once more. No change. (Though perhaps I should have shut down instead of rebooting... will have to give that another try.)

brent

The following list of packages will be removed
in the respective order to satisfy dependencies:
gvfs-goa budgie-weathershow-applet sdl2-mixer sdl2-ttf ffmpegthumbnailer flatpak picard gnome-session gnome-control-center steam citra budgie-screensaver sdl2-mixer-32bit baobab networkmanager-openconnect gstreamer-1.0-libav budgie-screenshot-applet libwebkit-gtk5 eog libgnome-desktop libadwaita gnome-calendar yuzu gnome-calculator mutter file-roller libgdata gnome-terminal libvte libportal wireplumber sdl2-gfx-32bit sdl2-gfx sdl2-net budgie-control-center libcolord-gtk gnome-online-accounts libwebkit-gtk41 evolution-data-server sdl2-net-32bit networkmanager-openvpn gnome-bluetooth-1-common gnome-bluetooth-1 xdg-desktop-portal qt6-multimedia gnome-bluetooth libgtksourceview5 pipewire-32bit network-manager-applet libnma sdl2-image-32bit sdl2-image ibus libgtk-4 python3-qt5 qt5-connectivity libwebkit-gtk gstreamer-1.0-plugins-bad chromaprint ffmpeg sdl2-ttf-32bit sdl2-32bit sdl2 budgie-desktop-branding-fortitude-plus budgie-desktop-branding-fortitude budgie-desktop-branding budgie-desktop gnome-settings-daemon mpv-libs pipewire bluez

wow that took some guts. the outcome could be a successful rollback, total fubar, partial fubar, pretty horrible fubar. Out of those 4 I own that last 3 so congrats on 1.
I wonder---in regards to this experiment--if the reboot as opposed to complete shutdown would have made a difference...I wish I knew the true difference. One's a lightning-fast power-off and one is a true power-off? How would that have effected Bluez?
what a long strange trip, as they sang...

infinitymdm

brent if the reboot as opposed to complete shutdown would have made a difference...I wish I knew the true difference. One's a lightning-fast power-off and one is a true power-off? How would that have effected Bluez?

My very limited understanding is that Bluetooth hardware has some complex interactions with system power because of the many low-power states it can be in. Doing a full shutdown (and removing power for good measure - maybe even going as far as removing the CMOS battery) can help clear up any residual charge in the circuits, and get things into a goodish state again.

WetGeek

brent I wonder---in regards to this experiment--if the reboot as opposed to complete shutdown would have made a difference...I wish I knew the true difference.

Years ago I noticed that there IS a difference, and after experiencing that difference enough times, I concluded that a reboot restarts just the OS, and a shutdown and restart also includes all the peripherals. I was trying to figure out why a network issue was affected by a complete shutdown, but not a reboot.

No idea what that has to do with the present context. Perhaps the radio isn't shut down and restarted by a reboot?

brent

infinitymdm as far as removing the CMOS battery

this ^ and re-situating the jumper pins sheath with a needlenose pliers on the back of a HDD (if applicable) have performed miracles for me. seems so old school now. it does---as fact---reset many things back to happy. It truly does not clear any charges with a reboot, I agree.

Axios

In the case of bluetooth chips its a register based Meaning that all the commands issued to it by
a write cycle of the os settings are stored in the bluetooth chip so when you boot the software reads those values.
If you remove power from the chip and power it up again the data you stored is read again.
Sometimes a glitch or other unkown reason the registers can get fubar so who knows whats in the registers
and then a chip reset is done setting it back to factory defaults.

Doing what he said is really more for the internals of chips sometimes they can get funky inside.
The concept is basically the same thing your doing when your changing your bios settings.

The bluez deal was basically they did an update to it in may and ran across removing and reinstall it fixed
bluetooth for some ppl.
The remove and power down ect prob not needed and maybe not good idea.
But one can do a chip reset to get it back to factory defaults

Axios

But I might note the bluetooth chip will retain its settings without power
(And they can go bad they are usually rated for like 100,000 write cycles)
(Reading the chip does not effect anything)

Axios

brent This is interesting
(If his module Mac address is truly set to all zeros Linux dont like it)
or How the heck it would happen in first place but hey its computers anything is poss.
(Guess this Is why I keep windows around for stupid stuff...lol)
https://macaddresschanger.com/invalid-bluetooth-address
I just wonder

brent

Axios in windows at least you get one mac addy reset then no more (says the article). Then this short article ends with 'proof of concept' gitlab code to reverse this course of zeroed out address. Could invalid address have something to do with this problem I wonder? I consider that very interesting.
edit:
bluetoothd[...]: No address available for hci0 or bluetoothd[...]: No Bluetooth address for index 0
have we seen that yet in this thread? too tired to scroll to top🙂

infinitymdm

Axios brent I just want to say that you guys have been awesome. Thanks so much for your help so far. I'm sure that eventually we'll get this figured out.

I'll take a look at that mac address reset code (hopefully over the weekend, though my schedule has gotten pretty full lately) and consider giving it a try.

Axios

brent New Index: 00:00:00:00:00:00 (Primary,USB,hci0) [hci0] 0.749501
The no address is prob what causing it not to work but I dont know where its not coming from.
And since thats invalid mac address it will cause issues
Found that little article interesting and informative

brent

Axios the code is there for the experimenting and @infinitymdm has endured all the hammering with great humor🙂...
"This project is a proof of concept example only.
The code demontrates sending commands to CSR bluetooth adapter (to change it's address) using libusb functions instead of hci calls.

Usage: fix_bricked_bt VID PID BD_ADDR

Arguments: VID, PID - USB device identifiers BD_ADDR - New bluetooth address

Example: fix_bricked_bt 0x0a12 0x0001 11:22:33:44:55:66

Building Run make to build the program. libusb-1.0 headers and libraries required to be installed on your system (debian/ubuntu - "libusb-1.0-0-dev" package)"
😲

Axios

infinitymdm I looked online A guy could do it but it would be a beast to replace the board
prob not for the faint hearted. (Under the silver metal shield the antenna brackets are attached to it whole thing comes out gotta remove mother board ect ect ect geez they couldnt make it simple)

I dunno did alot of kernel module reading and fixes mediatek did I came to the conclusion maybe in the next 2
kernel cycles maybe it will get fixed. If thats the issue. (that I am looking at)

But it wouldnt hurt to look at that wont do any harm. Might tell us alittle more. (Mac add)
I did learn something tho My codeing is wayyyyyyyy rusty when you get that deep..lol
gave me a headache..rofl

Axios

WetGeek You are correct reboot=Soft pwr off=hard,soft
they do act different sometimes.
Kinda hard to tell tho what they effect sometimes so I just pwr down if issues arise.
Soft reboot is always easier on equipment tho.

Hmmm I dont run windows 10 getting ready sometime to wipe it off lenovo thinkpad
But I did notice that strange behavor Harvey just described kinda thought thats what it was
I dont go past win7...lol

Harvey

In a reboot (warm boot) devices are not always "let go". If a computer is shutdown and it is a true shutdown (By default in Windows 10+, shutdown is actually a sleep state), the device is "let go" and when you next power on (cold boot) everything is reinitialised without getting stuck in some prior state.

brent

Axios Kinda hard to tell tho what they effect sometimes so I just pwr down if issues arise.

toward what you said and Harvey said and Wetgeek said (re: the science/sequence of powering down), if indeed that is valid, which it probably is...then I wonder if it is possible (dmesg? journalctl?) to audit the 'let go' state versus the still ticking state? edit: to see who's chatty

In a soft reboot whatever is talking/not talking to the bluetooth will continue talking/not talking and a hard boot all communicaion is let go then reestablishes on boot..

..so what does this mean? We can rule hard vs. soft out right now. Right? I forget? (op already tried i think)
Are we down to two factors now?
Is this what we are down to infinitymdm you think?:
1) the hardware and software aren't talking and we don't know why
or
2) basic incompatibility (kernel etc)

infinitymdm

Axios A guy could do it but it would be a beast to replace the board
prob not for the faint hearted.

I used to repair smartphones. Stuff like this is a walk in the park by comparison 😛

Axios I dunno did alot of kernel module reading and fixes mediatek did I came to the conclusion maybe in the next 2
kernel cycles maybe it will get fixed. If thats the issue. (that I am looking at)

I think that would fall under the "Do nothing, and wait for a miraculous fix from the penguin gods" troubleshooting option. That's promising, though - could you link to the patches you're looking at? I might just build the kernel with those patches if it isn't too in-depth.

Axios

infinitymdm Uh I hate to even say this with all the bookmarks and stuff I cant find it
I wasnt ignoring you.
I guess I didnt hit the save key.
Wanted to look at it some more myself will keep looking

Axios

brent I think its little of both those but I dont know which is the main offender
Kernal,mt7922,firmware appears to me its getting in a hung state (appears not to be stuck there)
(After my research think device driver)

They have error (And codes are different) for not communicating and those kinda things so I think its working up to the point its doesnt.
But when it reaches that point it gets hung up.
Power down or reboot we start over again sheesh
Will prob be one ah ha moments when it does work.

« Previous Page Next Page »