Page 1 of 1
RTL8822BE/AX200 Bluetooth trouble
Posted: Thu Feb 13, 2025 6:28 am
by andre
Hi, everybody!
I have Lenovo Thinkpad E595 laptop, and I use MX Linux at live usb. Everything works fine except Bluetooth.
This laptop has RTL8822BE combined WiFi/Bluetooth module. I use Bluetooth with JBL520 earphones.
What is problem:
sometime I able to use Bluetooth for 5 ... 10 ... 30 minutes;
sometime it fails at startup or when I point cursor to BT icon at taskbar or when I try to search for bt devices.
But more often I can't use it.
When it fails BT icon disappears from taskbar, and only restart can help... (but usually need to boot to Windows,
power off, and then boot to MX..)
My system info:
Code: Select all
Snapshot created on: 20250210_1212
System:
Kernel: 6.1.0-21-amd64 [6.1.90-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/antiX/vmlinuz quiet nosplash splasht lang=en_US kbd=us
tz=Europe/Bucharest persist_root splasht
Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
dm: LightDM v: 1.32.0 Distro: MX-23.5_x64 Libretto May 19 2024 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: LENOVO product: 20NF001YRT v: ThinkPad E595 serial: <superuser required>
Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20NF001YRT serial: <superuser required> UEFI: LENOVO v: R11ET49W (1.29)
date: 11/22/2023
Battery:
ID-1: BAT0 charge: 31.1 Wh (74.6%) condition: 41.7/45.3 Wh (92.2%) volts: 12.4 min: 11.1
model: SMP 01AV446 type: Li-poly serial: <filter> status: charging cycles: 986
CPU:
Info: model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen/Zen+
note: check gen: 1 level: v3 note: check built: 2019 process: GF 12nm family: 0x17 (23)
model-id: 0x18 (24) stepping: 1 microcode: 0x8108109
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 384 KiB
desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1368 high: 1400 min/max: 1400/2300 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1390 2: 1360 3: 1237 4: 1391 5: 1391 6: 1387
7: 1388 8: 1400 bogomips: 36729
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_rstack_overflow mitigation: safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP: disabled; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
vendor: Lenovo ThinkPad E595 driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm
built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: eDP-1
empty: DP-1,DP-2,HDMI-A-1 bus-ID: 05:00.0 chip-ID: 1002:15d8 class-ID: 0300 temp: 58.0 C
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99")
Monitor-1: eDP-1 mapped: eDP model: Lenovo 0x40ba built: 2018 res: 1920x1080 hz: 60 dpi: 142
gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: max: 1920x1080
min: 640x480
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Vega 10 Graphics (raven LLVM 15.0.6 DRM
3.49 6.1.0-21-amd64) direct-render: Yes
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Lenovo ThinkPad E595
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.1
chip-ID: 1002:15de class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo ThinkPad E595
driver: snd_pci_acp3x v: kernel alternate: snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x pcie:
gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo ThinkPad E595 driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.1.0-21-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo ThinkPad E595
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 02:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: down mac: <filter>
IF-ID-1: amn0 state: unknown speed: 10 Mbps duplex: full mac: N/A
IF-ID-2: pan1 state: unknown speed: -1 duplex: unknown mac: <filter>
IF-ID-3: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 1.43 TiB used: 1.16 TiB (81.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: HFM512GDHTNG-8710B size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 80020C00 temp: 42.9 C scheme: MBR
ID-2: /dev/sda maj-min: 8:0 vendor: A-Data model: SU650 size: 953.87 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 630B scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Cruzer Fit size: 29.25 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
file: /live/boot-dev/swap-file
Sensors:
System Temperatures: cpu: 58.0 C mobo: N/A gpu: amdgpu temp: 58.0 C
Fan Speeds (RPM): fan-1: 0 fan-2: 0
Repos:
Packages: pm: dpkg pkgs: 2155 libs: 1067 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mirror.23m.com/mx-packages/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/tailscale.list
1: deb [signed-by=/usr/share/keyrings/tailscale-archive-keyring.gpg] https://pkgs.tailscale.com/stable/debian bookworm main
Active apt repos in: /etc/apt/sources.list.d/virtualbox.list
1: deb [arch=amd64 signed-by=/usr/share/keyrings/oracle_vbox_2016.gpg] http://download.virtualbox.org/virtualbox/debian bookworm contrib
Info:
Processes: 303 Uptime: 1h 50m wakeups: 13 Memory: 23.22 GiB used: 3.1 GiB (13.4%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
I tried to use 6.1.0-31 kernel, but that didn't helped.
dmesg | grep 8822 output:
Code: Select all
[ 492.715797] rtw_8822be 0000:04:00.0: enabling device (0000 -> 0003)
[ 492.817346] rtw_8822be 0000:04:00.0: firmware: direct-loading firmware rtw88/rtw8822b_fw.bin
[ 492.817373] rtw_8822be 0000:04:00.0: Firmware version 27.2.0, H2C version 13
[ 495.559391] Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8822
[ 495.561369] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_fw.bin
[ 495.569229] bluetooth hci0: firmware: direct-loading firmware rtl_bt/rtl8822b_fw.bin
[ 495.569259] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_config.bin
[ 495.576884] bluetooth hci0: firmware: direct-loading firmware rtl_bt/rtl8822b_config.bin
As I understand Bluetooth module internally connected to USB bus. I checked
dmesg|grep usb ouptut:
Code: Select all
[ 1.015078] usbcore: registered new interface driver usbfs
[ 1.015088] usbcore: registered new interface driver hub
[ 1.015114] usbcore: registered new device driver usb
[ 1.330164] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[ 1.330167] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.330170] usb usb1: Product: xHCI Host Controller
[ 1.330172] usb usb1: Manufacturer: Linux 6.1.0-21-amd64 xhci-hcd
[ 1.330174] usb usb1: SerialNumber: 0000:05:00.3
[ 1.330726] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 1.330756] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01
[ 1.330759] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.330761] usb usb2: Product: xHCI Host Controller
[ 1.330763] usb usb2: Manufacturer: Linux 6.1.0-21-amd64 xhci-hcd
[ 1.330765] usb usb2: SerialNumber: 0000:05:00.3
[ 1.332154] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[ 1.332156] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.332159] usb usb3: Product: xHCI Host Controller
[ 1.332161] usb usb3: Manufacturer: Linux 6.1.0-21-amd64 xhci-hcd
[ 1.332163] usb usb3: SerialNumber: 0000:05:00.4
[ 1.332678] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[ 1.332708] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01
[ 1.332711] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.332713] usb usb4: Product: xHCI Host Controller
[ 1.332715] usb usb4: Manufacturer: Linux 6.1.0-21-amd64 xhci-hcd
[ 1.332717] usb usb4: SerialNumber: 0000:05:00.4
[ 1.592282] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[ 1.592292] usb 1-3: new high-speed USB device number 2 using xhci_hcd
[ 1.743975] usb 1-3: New USB device found, idVendor=0781, idProduct=5571, bcdDevice= 1.00
[ 1.743982] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.743985] usb 1-3: Product: Cruzer Fit
[ 1.743987] usb 1-3: Manufacturer: SanDisk
[ 1.743990] usb 1-3: SerialNumber: 4C530001261029110553
[ 1.772710] usb 3-1: New USB device found, idVendor=0bda, idProduct=b023, bcdDevice= 2.10
[ 1.772723] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.772730] usb 3-1: Product: Bluetooth Radio
[ 1.772737] usb 3-1: Manufacturer: Realtek
[ 1.772743] usb 3-1: SerialNumber: 00e04c000001
[ 1.912293] usb 3-2: new high-speed USB device number 3 using xhci_hcd
[ 2.040153] usb-storage 1-3:1.0: USB Mass Storage device detected
[ 2.040354] scsi host1: usb-storage 1-3:1.0
[ 2.040471] usbcore: registered new interface driver usb-storage
[ 2.041784] usbcore: registered new interface driver uas
[ 2.071644] usb 3-2: New USB device found, idVendor=5986, idProduct=2113, bcdDevice=54.22
[ 2.071655] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.071661] usb 3-2: Product: Integrated Camera
[ 2.071666] usb 3-2: Manufacturer: SunplusIT Inc
[ 14.949503] usb 3-2: Found UVC 1.00 device Integrated Camera (5986:2113)
[ 14.967454] input: Integrated Camera: Integrated C as /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2/3-2:1.0/input/input16
[ 14.967543] usbcore: registered new interface driver uvcvideo
[ 15.118683] usbcore: registered new interface driver btusb
when Bluetooth fail happens I observe next:
Code: Select all
[ 1655.085295] usb 3-1: USB disconnect, device number 2
[ 1655.086725] usb usb3-port1: couldn't allocate usb_device
[ 1655.086755] usb 3-2: USB disconnect, device number 3
also I catched this output when BT fails, but icon didn't disappear:
Code: Select all
[ 63.028614] usb 3-2: Failed to query (GET_CUR) UVC control 2 on unit 2: -19 (exp. 2).
May be MX gure have some idea?
UPD: RTL8822BE module was replaced by INTEL AX200, but problem remain (
Re: RTL8822BE Bluetooth trouble
Posted: Thu Feb 13, 2025 7:55 am
by j2mcgreg
For that machine, I would be using the AHS version of MX 23 and at least the Liquorix 6.9.12-2 kernel. There's ample evidence here in the forums that Ryzen based machines perform much better with a Liquorix kernel and that glitches found with the default Debian kernels are eliminated.
Re: RTL8822BE Bluetooth trouble
Posted: Thu Feb 13, 2025 8:11 am
by andre
j2mcgreg wrote: Thu Feb 13, 2025 7:55 am
For that machine, I would be using the AHS version of MX 23 and at least the Liquorix 6.9.12-2 kernel. There's ample evidence here in the forums that Ryzen based machines perform much better with a Liquorix kernel and that glitches found with the default Debian kernels are eliminated.
Thank you for advice! At least I have now direction!
Re: RTL8822BE Bluetooth trouble
Posted: Sat Feb 15, 2025 12:19 pm
by andre
According to advice of
2mcgreg tried MX23.0_AHS and MX23.5_AHS with 6.12.8-1-liquorix kernel. Nothing changed
I tried
lsusb it shows my module:
Code: Select all
Bus 003 Device 002: ID 0bda:b023 Realtek Semiconductor Corp. RTL8822BE Bluetooth 4.2 Adapter
but then it disappears...
Re: RTL8822BE Bluetooth trouble
Posted: Sun Feb 16, 2025 3:35 am
by andre
Tried
6.12.12-2-liquorix-amd64 kernel. Same story
...
BT worked after connect, I started watch video, and again module disappeared:
Code: Select all
[ 939.180366] Bluetooth: hci0: Resetting usb device.
[ 939.343401] usb 3-1: reset full-speed USB device number 2 using xhci_hcd
[ 939.343416] usb 3-1: hub failed to enable device, error -108
[ 939.456352] usb 3-1: reset full-speed USB device number 2 using xhci_hcd
[ 939.456369] usb 3-1: hub failed to enable device, error -108
[ 939.569342] usb 3-1: reset full-speed USB device number 2 using xhci_hcd
[ 939.979340] usb 3-1: device not accepting address 2, error -108
[ 940.091339] usb 3-1: reset full-speed USB device number 2 using xhci_hcd
[ 940.508325] usb 3-1: device not accepting address 2, error -108
[ 940.508427] usb 3-1: USB disconnect, device number 2
[ 940.510404] usb usb3-port1: couldn't allocate usb_device
Re: RTL8822BE Bluetooth trouble
Posted: Fri Feb 21, 2025 12:56 pm
by andre
Hello, community! So last information if somebody have interest). Assuming that this is a hardware problem, a new WiFi module was purchased -
AX200. But after installing the new module, the old problem remained. That is, the problem is not in the module drivers... It looks like a problem with USB. Here is dmesg outptut, I catch it when bluetooth icon was ok and I just switch on my JBL520 earphones.
After that bluetooth icon disappeared..
Code: Select all
1828.140317] xhci_hcd 0000:05:00.4: xHCI host not responding to stop endpoint command
[ 1828.140349] xhci_hcd 0000:05:00.4: xHCI host controller not responding, assume dead
[ 1828.140366] xhci_hcd 0000:05:00.4: HC died; cleaning up
[ 1828.140484] usb 3-1: USB disconnect, device number 2
[ 1828.141723] usb usb3-port1: couldn't allocate usb_device
[ 1828.141748] usb 3-2: USB disconnect, device number 3
[ 1838.345049] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1838.345069] ata1.00: Entering active power mode
[ 1838.357408] ata1.00: configured for UDMA/133
[ 1838.370204] sd 0:0:0:0: [sda] Starting disk
I tried to restart the xHCI USB device:
Code: Select all
echo -n "0000:05:00.4" > /sys/bus/pci/drivers/xhci_hcd/unbind
echo -n "0000:05:00.4" > /sys/bus/pci/drivers/xhci_hcd/bind
but that didn't help.
Any idea,
please
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Fri Feb 21, 2025 1:08 pm
by CharlesV
Going to suggest to try turning off suspend / timeout of the BT.
You can turn off 'timeouts' for BT devices as follows:
edit /etc/bluetooth/input.config setting the following under general :
In mine these are remarked out, supposed to default to 0 .. but try setting it to 0 ( you could optionally set it to say 90 min and then see if it affects how the mouse works. Possibly set to say 5 min for testing and see what happens ? )
more info on the issue here:
viewtopic.php?p=810638#p810638
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Fri Feb 21, 2025 1:58 pm
by andre
CharlesV wrote: Fri Feb 21, 2025 1:08 pm
Going to suggest to try turning off suspend / timeout of the BT.
You can turn off 'timeouts' for BT devices as follows:
edit /etc/bluetooth/input.config setting the following under general :
...
Thank you! Will try.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 12:29 pm
by andre
Hello, community!
CharlesV wrote: Fri Feb 21, 2025 1:08 pm
Going to suggest to try turning off suspend / timeout of the BT.
...
No changes...
Main problem that I can't use Bluetooth at all. Only seldom, after reboot after windows use, I can use Bluetooth for some time, But when it fails even reboot doesn't helps(((
I tried also to use antiX live usb and there is same issue.
A can't find better alternative than MX linux.
Maybe there is a possibility to get paid support?
I'm in despair(((. Help please!
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 12:52 pm
by Eadwine Rose
We do not offer paid support.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 1:04 pm
by CharlesV
Please post your updated QSI .
And for a workaround, I am going to suggest that you purchase this adapter and see if you can get stable using it. I have four or five users with this in place, works nicely and they dont have issues with it.
https://www.amazon.com/ASUS-USB-BT500-B ... BNG7F?th=1
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 1:23 pm
by j2mcgreg
@andre
Have you tested your Bluetooth device(s) against another computer to eliminate it / them as the problem source?
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 2:02 pm
by andre
Please post your updated QSI .
Code: Select all
Snapshot created on: 20250225_0958
System:
Kernel: 6.1.0-21-amd64 [6.1.90-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/antiX/vmlinuz quiet nosplash splasht lang=en_US kbd=us tz=Europe/Moscow
persist_root from=usb norepo splasht vcard=on
Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
dm: LightDM v: 1.32.0 Distro: MX-23.5_x64 Libretto May 19 2024 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: LENOVO product: 20NF001YRT v: ThinkPad E595 serial: <superuser required>
Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20NF001YRT serial: <superuser required> UEFI: LENOVO v: R11ET49W (1.29)
date: 11/22/2023
Battery:
ID-1: BAT0 charge: 27.1 Wh (65.0%) condition: 41.7/45.3 Wh (92.1%) volts: 12.3 min: 11.1
model: SMP 01AV446 type: Li-poly serial: <filter> status: charging cycles: 1023
CPU:
Info: model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen/Zen+
note: check gen: 1 level: v3 note: check built: 2019 process: GF 12nm family: 0x17 (23)
model-id: 0x18 (24) stepping: 1 microcode: 0x8108109
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 384 KiB
desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1507 high: 1691 min/max: 1400/2300 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 1676 2: 1690 3: 1691 4: 1289 5: 1689 6: 1679
7: 1132 8: 1214 bogomips: 36728
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_rstack_overflow mitigation: safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP: disabled; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
vendor: Lenovo ThinkPad E595 driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm
built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: eDP-1
empty: DP-1,DP-2,HDMI-A-1 bus-ID: 05:00.0 chip-ID: 1002:15d8 class-ID: 0300 temp: 57.0 C
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99")
Monitor-1: eDP-1 mapped: eDP model: Lenovo 0x40ba built: 2018 res: 1920x1080 hz: 60 dpi: 142
gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: max: 1920x1080
min: 640x480
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Vega 10 Graphics (raven LLVM 15.0.6 DRM
3.49 6.1.0-21-amd64) direct-render: Yes
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Lenovo ThinkPad E595
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.1
chip-ID: 1002:15de class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo ThinkPad E595
driver: snd_pci_acp3x v: kernel alternate: snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x pcie:
gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo ThinkPad E595 driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.1.0-21-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo ThinkPad E595
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 02:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel modules: wl pcie: gen: 2 speed: 5 GT/s
lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlan0 state: up mac: <filter>
IF-ID-1: amn0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives:
Local Storage: total: 1.43 TiB used: 1.26 TiB (88.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: HFM512GDHTNG-8710B size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 80020C00 temp: 49.9 C scheme: MBR
ID-2: /dev/sda maj-min: 8:0 vendor: A-Data model: SU650 size: 953.87 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 630B scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Cruzer Fit size: 29.25 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
file: /live/boot-dev/swap-file
Sensors:
System Temperatures: cpu: 57.0 C mobo: N/A gpu: amdgpu temp: 56.0 C
Fan Speeds (RPM): fan-1: 3300 fan-2: 3300
Repos:
Packages: pm: dpkg pkgs: 2230 libs: 1110 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
3: deb http://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/dropbox.list
1: deb [arch=i386,amd64 signed-by=/etc/apt/keyrings/dropbox.asc] http://linux.dropbox.com/debian bookworm main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mirror.23m.com/mx-packages/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/owncloud-client.list
1: deb https://download.owncloud.com/desktop/ownCloud/stable/latest/linux/Debian_12/ /
Active apt repos in: /etc/apt/sources.list.d/tailscale.list
1: deb [signed-by=/usr/share/keyrings/tailscale-archive-keyring.gpg] https://pkgs.tailscale.com/stable/debian bookworm main
Active apt repos in: /etc/apt/sources.list.d/virtualbox.list
1: deb [arch=amd64 signed-by=/usr/share/keyrings/oracle_vbox_2016.gpg] http://download.virtualbox.org/virtualbox/debian bookworm contrib
Info:
Processes: 332 Uptime: 2h 5m wakeups: 3 Memory: 23.22 GiB used: 4.97 GiB (21.4%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 2:12 pm
by andre
j2mcgreg wrote: Sat Mar 08, 2025 1:23 pm
Have you tested your Bluetooth device(s) against another computer to eliminate it / them as the problem source?
No. But I tested it with other distros: Ubuntu and Debian (at live USB), and whey both worked fine there. Also both
modules works fine at Windows.
I also tried antiX live USB, but there is
same problem as at MX.
Suppose it is not hardware problem?
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 2:35 pm
by anticapitalista
Try adding load=all at the live boot menu.
Seems like there might be a missing module in the live init.gz
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 3:18 pm
by j2mcgreg
andre wrote: Sat Mar 08, 2025 2:12 pm
j2mcgreg wrote: Sat Mar 08, 2025 1:23 pm
Have you tested your Bluetooth device(s) against another computer to eliminate it / them as the problem source?
No. But I tested it with other distros: Ubuntu and Debian (at live USB), and whey both worked fine there. Also both
modules works fine at Windows.
I also tried antiX live USB, but there is
same problem as at MX.
Suppose it is not hardware problem?
Since both Debian and Ubuntu use SystemD and antiX and MX (by default) do not, maybe enabling SystemD in MX is the answer?
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 3:37 pm
by CharlesV
@andre what is this in your boot options?
from=usb norepo
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 3:40 pm
by dolphin_oracle
Dumb question. Is there a difference in the Bluetooth if a different usb port is used for the live usb? Or possibly is the port going to sleep ? If the Bluetooth is on the usb bus perhaps disabling usb port power down in tlp settings would help.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 3:41 pm
by CharlesV
and also in a terminal run and post results please
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 3:42 pm
by dolphin_oracle
CharlesV wrote: Sat Mar 08, 2025 3:37 pm
@andre what is this in your boot options?
from=usb norepo
from=usb handoffs from a disc to a live usb in situations where an actual disc boots. norepo disables auto selection of a repo based on time zone. Handy if you manually pick a repo.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 08, 2025 3:42 pm
by CharlesV
dolphin_oracle wrote: Sat Mar 08, 2025 3:42 pm
CharlesV wrote: Sat Mar 08, 2025 3:37 pm
@andre what is this in your boot options?
from=usb norepo
from=usb handoffs from a disc to a live usb in situations where an actual disc boots. norepo disables auto selection of a repo based on time zone. Handy if you manually pick a repo.
Great info thank you!
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 09, 2025 5:33 am
by andre
j2mcgreg wrote: Sat Mar 08, 2025 3:18 pm
andre wrote: Sat Mar 08, 2025 2:12 pm
j2mcgreg wrote: Sat Mar 08, 2025 1:23 pm
Have you tested your Bluetooth device(s) against another computer to eliminate it / them as the problem source?
No. But I tested it with other distros: Ubuntu and Debian (at live USB), and whey both worked fine there. Also both
modules works fine at Windows.
I also tried antiX live USB, but there is
same problem as at MX.
Suppose it is not hardware problem?
Since both Debian and Ubuntu use SystemD and antiX and MX (by default) do not, maybe enabling SystemD in MX is the answer?
Probably. At this moment I in progress of installing MX to hard drive. As I understand I can't use SystemD at live usb with persistance..
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 09, 2025 5:40 am
by andre
CharlesV wrote: Sat Mar 08, 2025 3:37 pm
@andre what is this in your boot options?
from=usb norepo
I think I had selected this option at advanced menu during startup.. I had some problem due to ISP censorship.. But I haven't problem to access repos..
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 09, 2025 5:48 am
by andre
dolphin_oracle wrote: Sat Mar 08, 2025 3:40 pm
Dumb question. Is there a difference in the Bluetooth if a different usb port is used for the live usb? Or possibly is the port going to sleep ? If the Bluetooth is on the usb bus perhaps disabling usb port power down in tlp settings would help.
I don't think so. I tried to disable all power savings using tlp, but that didn't help. I also tried different ports and different flash drives..
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 09, 2025 5:53 am
by andre
CharlesV wrote: Sat Mar 08, 2025 3:41 pm
and also in a terminal run and post results please
Code: Select all
$ btmgmt info
Index list with 0 items
At this moment BT is
gone, I will check later when l catch BT
alive.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 09, 2025 6:13 am
by andre
CharlesV wrote: Sat Mar 08, 2025 1:04 pm
Please post your updated QSI .
And for a workaround, I am going to suggest that you purchase this adapter and see if you can get stable using it. I have four or five users with this in place, works nicely and they dont have issues with it.
https://www.amazon.com/ASUS-USB-BT500-B ... BNG7F?th=1
Thank you for advice!
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 09, 2025 10:16 am
by andre
anticapitalista wrote: Sat Mar 08, 2025 2:35 pm
Try adding load=all at the live boot menu.
Seems like there might be a missing module in the live init.gz
@anticapitalista, can you please advice how to do that? I tried to do that at boot menu, but didn't find such option.. Also I tried 'MX Boot Options'.., but it doesn't save it..:
I added
lload=all at Kernel parameters, but looks I am at wrong directions
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 09, 2025 10:57 am
by dolphin_oracle
You are running a live usb. There is a live usb option for load=all. Just select that when you boot.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 09, 2025 12:14 pm
by andre
CharlesV wrote: Sat Mar 08, 2025 3:41 pm
and also in a terminal run and post results please
So, I catched BT working..
BT service was stopped, i typed:
btmgmt info:
Code: Select all
$ btmgmt info
Index list with 1 item
hci0: Primary controller
addr C8:5E:A9:67:12:8A version 11 manufacturer 2 class 0x000000
supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration wide-band-speech
current settings: br/edr
name
short name
hci0: Configuration options
supported options: public-address
missing options:
After I typed
bluetoothctl:
[t]it shows something like
waiting bluetoothd[/t]
Then I manually started bluetooth service and got next:
Code: Select all
$ bluetoothctl
[NEW] Media /org/bluez/hci0
SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[NEW] Controller C8:5E:A9:67:12:8A BlueZ 5.66 [default]
[NEW] Device C8:2B:6B:0B:58:DA JBL TUNE520BT
Agent registered
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001133-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001104-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00005005-0000-1000-8000-0002ee000001
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001133-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001104-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00005005-0000-1000-8000-0002ee000001
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001133-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001104-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00005005-0000-1000-8000-0002ee000001
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001133-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001104-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00005005-0000-1000-8000-0002ee000001
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001133-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001104-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00005005-0000-1000-8000-0002ee000001
[CHG] Controller C8:5E:A9:67:12:8A Alias: BlueZ 5.66
[CHG] Controller C8:5E:A9:67:12:8A Pairable: yes
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001133-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001104-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00005005-0000-1000-8000-0002ee000001
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001133-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001104-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00005005-0000-1000-8000-0002ee000001
[CHG] Controller C8:5E:A9:67:12:8A Name: pingvi
[CHG] Controller C8:5E:A9:67:12:8A Alias: BlueZ 5.66
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001133-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001104-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00005005-0000-1000-8000-0002ee000001
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001133-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001104-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00005005-0000-1000-8000-0002ee000001
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Controller C8:5E:A9:67:12:8A Alias: pingvi
After I typed
show:
Code: Select all
[bluetooth]# show
Controller C8:5E:A9:67:12:8A (public)
Name: pingvi
Alias: pingvi
Class: 0x00000000
Powered: no
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0542
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x0c (12)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
[DEL] Device C8:2B:6B:0B:58:DA JBL TUNE520BT
[DEL] Media /org/bluez/hci0
SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[DEL] Controller C8:5E:A9:67:12:8A pingvi [default]
[bluetooth]#
And BT controller and icon disappears(
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 09, 2025 12:31 pm
by CharlesV
I am starting to get the feeling that something in either your bluetooth adapter is failing, or your bluetooth data is corrupted / missing. Lets try this: In MX Package Installer - search for bluez , then switch to the Enabled repo tab, and check the following for install:
Code: Select all
bluez
bluez-cups
bluez-firmware
bluez-obexd
bluez-tools
python3-bluez
Make sure to check "Also install recommended. packages is checked (lower right ) and then install. this should reinstall all the bluez components and you *should* already have all these installed ( green box by all of them - if not, please post those that were not.)
I would restart after this and then test.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 09, 2025 1:38 pm
by andre
CharlesV wrote: Sun Mar 09, 2025 12:31 pm
I am starting to get the feeling that something in either your bluetooth adapter is failing, or your bluetooth data is corrupted / missing. Lets try this: In MX Package Installer - search for bluez , then switch to the Enabled repo tab, and check the following for install:
Code: Select all
bluez
bluez-cups
bluez-firmware
bluez-obexd
bluez-tools
python3-bluez
Make sure to check "Also install recommended. packages is checked (lower right ) and then install. this should reinstall all the bluez components and you *should* already have all these installed ( green box by all of them - if not, please post those that were not.)
I would restart after this and then test.
Done as instructed, rebooted -> same story:
Code: Select all
$ bluetoothctl
Agent registered
[bluetooth]# show
Controller C8:5E:A9:67:12:8A (public)
Name: pingvi
Alias: pingvi
Class: 0x007c010c
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0542
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x0c (12)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[DEL] Device C8:2B:6B:0B:58:DA JBL TUNE520BT
[CHG] Controller C8:5E:A9:67:12:8A Class: 0x00000000
[CHG] Controller C8:5E:A9:67:12:8A Powered: no
[CHG] Controller C8:5E:A9:67:12:8A Discovering: no
[DEL] Media /org/bluez/hci0
SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[DEL] Controller C8:5E:A9:67:12:8A pingvi [default]
[bluetooth]#
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 09, 2025 1:56 pm
by andre
anticapitalista wrote: Sat Mar 08, 2025 2:35 pm
Try adding load=all at the live boot menu.
Seems like there might be a missing module in the live init.gz
dolphin_oracle wrote: Sun Mar 09, 2025 10:57 am
You are running a live usb. There is a live usb option for load=all. Just select that when you boot.
Found!!! It is under 'Advanced Options' -> 'Failsafe options'
But that changed nothing. When I start search BT device - it fails(
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Mon Mar 10, 2025 12:35 pm
by andre
Last info.
Was downloaded MX 23.5
KDE, tested at live usb. Result - same:
fails
j2mcgreg wrote: Sat Mar 08, 2025 3:18 pm
Since both Debian and Ubuntu use SystemD and antiX and MX (by default) do not, maybe enabling SystemD in MX is the answer?
MX 23.5 AHS was installed to
hard drive, tested in both
SysVinit and Systemd modes. Result - also
fails, but now works little better - after fail I can reboot and continue to use some time...
Now
Debian 12 installed to hard drive. Result - BT works fine..
Any idea, please?
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Mon Mar 10, 2025 12:54 pm
by CharlesV
Interesting. What BT version is now installed an working?
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Tue Mar 11, 2025 8:34 am
by andre
CharlesV wrote: Mon Mar 10, 2025 12:54 pm
Interesting. What BT version is now installed an working?
@CharlesV, sorry, I don't understand fully you question, how I can get BT version?
Last my successful test was at
Debian 12 installed at hard drive.
Some info from there:
btmgmt info:
Code: Select all
Index list with 1 item
hci0: Primary controller
addr C8:5E:A9:67:12:8A version 11 manufacturer 2 class 0x6c010c
supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration wide-band-speech
current settings: powered ssp br/edr le secure-conn
name pingvi
short name
hci0: Configuration options
supported options: public-address
missing options:
Code: Select all
hci0: Type: Primary Bus: USB
BD Address: C8:5E:A9:67:12:8A ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:1729 acl:0 sco:0 events:102 errors:0
TX bytes:5834 acl:0 sco:0 commands:102 errors:0
Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: PERIPHERAL ACCEPT
Name: 'pingvi'
Class: 0x6c010c
Service Classes: Rendering, Capturing, Audio, Telephony
Device Class: Computer, Laptop
HCI Version: 5.2 (0xb) Revision: 0x200f
LMP Version: 5.2 (0xb) Subversion: 0x200f
Manufacturer: Intel Corp. (2)
Code: Select all
$ bluetoothctl
Agent registered
[CHG] Controller C8:5E:A9:67:12:8A Pairable: yes
[bluetooth]# show
Controller C8:5E:A9:67:12:8A (public)
Name: pingvi
Alias: pingvi
Class: 0x006c010c
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0542
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x0c (12)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Tue Mar 11, 2025 8:52 am
by andre
Also I checked which packages related to bluetooth was installed @
Debian:
- libspa-0.2-bluetooth/stable,now 0.3.65-3+deb12u1 amd64 [installed]
- libspa-0.2-modules/stable,now 0.3.65-3+deb12u1 amd64 [installed,automatic]
- libspandsp2/stable,now 0.0.6+dfsg-2+b1 amd64 [installed,automatic]
- pulseaudio-module-bluetooth/stable,now 16.1+dfsg1-2+b1 amd64 [installed]
- pulseaudio-utils/stable,now 16.1+dfsg1-2+b1 amd64 [installed,automatic]
- pulseaudio/stable,now 16.1+dfsg1-2+b1 amd64 [installed,automatic]
- xfce4-pulseaudio-plugin/stable,now 0.4.5-1 amd64 [installed,automatic]
- libbluetooth3/stable,now 5.66-1+deb12u2 amd64 [installed,automatic]
And later installed same packages to
MX. (And removed extra, include 'blueman')
But..
Also after BT fails @ MX(live) I booted to Debian(hard drive) and two times I found BT not working("no default controller"), but next reboot solved that.
At my opinion MX put BT module(or USB bus?) to some inoperable condition.
But how to fix that
?
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Tue Mar 11, 2025 11:09 am
by CharlesV
Interesting, so your BT version in debian is 5.2 ... and last I checked my laptop MX was a 5.3 ( I cannot say THAT is the issue.. but it sure seems like a deep clue to me.)
The BT version is listed at the bottom of the command hciconfig -a
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Tue Mar 11, 2025 5:28 pm
by andre
CharlesV wrote: Tue Mar 11, 2025 11:09 am
Interesting, so your BT version in debian is 5.2 ... and last I checked my laptop MX was a 5.3 ( I cannot say THAT is the issue.. but it sure seems like a deep clue to me.)
The BT version is listed at the bottom of the command hciconfig -a
I can't check which BT version at MX because it fails.. But I think it is same(5.2).
My new BT module:
INTEL AX200, and manufacturer declared BT 5.2 version.
Probably you have more advanced BT module.
IMHO.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Tue Mar 11, 2025 9:21 pm
by kmathern
Since you switched over to the AX200 device, have you checked in dmesg to see if it's complaining about missing firmware?
(In the first post of this topic you did post some info grepped from dmesg, but that was when you were using the RTL8822BE device)
Code: Select all
sudo dmesg | grep -Ei 'iwl|firmware|ucode|Linux version'
Also what version of firmware-iwlwifi is currently installed?
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Wed Mar 12, 2025 12:52 pm
by andre
kmathern wrote: Tue Mar 11, 2025 9:21 pm
Since you switched over to the AX200 device, have you checked in dmesg to see if it's complaining about missing firmware?
Due to the fact that I've been doing a lot of experiments lately by removing and installing packages, I decided to restore my MX to a previously taken snapshot. I've done this many times before and noticed one thing: when the system is first started, BT works pretty well. But after the first reboot, problems begin. Therefore, I attached
2 outptus of "sudo dmesg | grep -Ei 'iwl|firmware|ucode|Linux version'" here: before the first reboot and after.
sudo dmesg | grep -Ei 'iwl|firmware|ucode|Linux version' (before first reboot)
Code: Select all
[ 0.000000] Linux version 6.1.0-21-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03)
[ 0.097151] Spectre V2 : Enabling Speculation Barrier for firmware calls
[ 0.305536] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.341228] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 0.631161] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
[ 90.153528] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[ 90.173673] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[ 90.174908] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[ 90.260734] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-72.ucode
[ 90.260757] iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver
[ 90.260780] iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[ 90.283273] iwlwifi 0000:04:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 90.283281] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[ 90.283465] iwlwifi 0000:04:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 90.283472] iwlwifi 0000:04:00.0: loaded firmware version 72.daa05125.0 cc-a0-72.ucode op_mode iwlmvm
[ 91.654899] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[ 91.789893] iwlwifi 0000:04:00.0: Detected RF HR B3, rfid=0x10a100
[ 91.856191] iwlwifi 0000:04:00.0: base HW address: c8:5e:a9:67:12:86
[ 91.906380] psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x11, buttons: 3/3
[ 92.060291] iwlwifi 0000:04:00.0: firmware didn't ACK the reset - continue anyway
[ 92.060502] iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
[ 92.060507] iwlwifi 0000:04:00.0: Transport status: 0x0000004A, valid: 6
[ 92.060513] iwlwifi 0000:04:00.0: Loaded firmware version: 72.daa05125.0 cc-a0-72.ucode
[ 92.060519] iwlwifi 0000:04:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
[ 92.060526] iwlwifi 0000:04:00.0: 0x00A0A2F0 | trm_hw_status0
[ 92.060531] iwlwifi 0000:04:00.0: 0x00000000 | trm_hw_status1
[ 92.060535] iwlwifi 0000:04:00.0: 0x004FBE16 | branchlink2
[ 92.060540] iwlwifi 0000:04:00.0: 0x004F23FE | interruptlink1
[ 92.060545] iwlwifi 0000:04:00.0: 0x004F23FE | interruptlink2
[ 92.060549] iwlwifi 0000:04:00.0: 0x00014DA6 | data1
[ 92.060554] iwlwifi 0000:04:00.0: 0x03000000 | data2
[ 92.060558] iwlwifi 0000:04:00.0: 0x00000000 | data3
[ 92.060563] iwlwifi 0000:04:00.0: 0x00000000 | beacon time
[ 92.060567] iwlwifi 0000:04:00.0: 0x00027098 | tsf low
[ 92.060572] iwlwifi 0000:04:00.0: 0x00000000 | tsf hi
[ 92.060576] iwlwifi 0000:04:00.0: 0x00000000 | time gp1
[ 92.060580] iwlwifi 0000:04:00.0: 0x0002CAF3 | time gp2
[ 92.060585] iwlwifi 0000:04:00.0: 0x00000001 | uCode revision type
[ 92.060589] iwlwifi 0000:04:00.0: 0x00000048 | uCode version major
[ 92.060594] iwlwifi 0000:04:00.0: 0xDAA05125 | uCode version minor
[ 92.060599] iwlwifi 0000:04:00.0: 0x00000340 | hw version
[ 92.060603] iwlwifi 0000:04:00.0: 0x00C89000 | board version
[ 92.060607] iwlwifi 0000:04:00.0: 0x802AFD22 | hcmd
[ 92.060612] iwlwifi 0000:04:00.0: 0x20020000 | isr0
[ 92.060616] iwlwifi 0000:04:00.0: 0x00000000 | isr1
[ 92.060621] iwlwifi 0000:04:00.0: 0x08F00002 | isr2
[ 92.060625] iwlwifi 0000:04:00.0: 0x00C0000C | isr3
[ 92.060630] iwlwifi 0000:04:00.0: 0x00000000 | isr4
[ 92.060634] iwlwifi 0000:04:00.0: 0x00000000 | last cmd Id
[ 92.060638] iwlwifi 0000:04:00.0: 0x00014DA6 | wait_event
[ 92.060643] iwlwifi 0000:04:00.0: 0x00000000 | l2p_control
[ 92.060647] iwlwifi 0000:04:00.0: 0x00000000 | l2p_duration
[ 92.060651] iwlwifi 0000:04:00.0: 0x00000000 | l2p_mhvalid
[ 92.060656] iwlwifi 0000:04:00.0: 0x00000000 | l2p_addr_match
[ 92.060660] iwlwifi 0000:04:00.0: 0x00000009 | lmpm_pmg_sel
[ 92.060664] iwlwifi 0000:04:00.0: 0x00000000 | timestamp
[ 92.060669] iwlwifi 0000:04:00.0: 0x00000024 | flow_handler
[ 92.060786] iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
[ 92.060790] iwlwifi 0000:04:00.0: Transport status: 0x0000004A, valid: 7
[ 92.060796] iwlwifi 0000:04:00.0: 0x20000074 | ADVANCED_SYSASSERT
[ 92.060801] iwlwifi 0000:04:00.0: 0x00000000 | umac branchlink1
[ 92.060805] iwlwifi 0000:04:00.0: 0x80455E3C | umac branchlink2
[ 92.060810] iwlwifi 0000:04:00.0: 0x80472146 | umac interruptlink1
[ 92.060814] iwlwifi 0000:04:00.0: 0x80472146 | umac interruptlink2
[ 92.060819] iwlwifi 0000:04:00.0: 0x03000000 | umac data1
[ 92.060823] iwlwifi 0000:04:00.0: 0x80472146 | umac data2
[ 92.060827] iwlwifi 0000:04:00.0: 0x00000000 | umac data3
[ 92.060832] iwlwifi 0000:04:00.0: 0x00000048 | umac major
[ 92.060836] iwlwifi 0000:04:00.0: 0xDAA05125 | umac minor
[ 92.060841] iwlwifi 0000:04:00.0: 0x0002CAF0 | frame pointer
[ 92.060845] iwlwifi 0000:04:00.0: 0xC0886264 | stack pointer
[ 92.060849] iwlwifi 0000:04:00.0: 0x00040F07 | last host cmd
[ 92.060854] iwlwifi 0000:04:00.0: 0x00000000 | isr status reg
[ 92.060947] iwlwifi 0000:04:00.0: IML/ROM dump:
[ 92.060951] iwlwifi 0000:04:00.0: 0x00000003 | IML/ROM error/state
[ 92.061047] iwlwifi 0000:04:00.0: 0x00005868 | IML/ROM data1
[ 92.061146] iwlwifi 0000:04:00.0: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
[ 92.061240] iwlwifi 0000:04:00.0: Fseq Registers:
[ 92.061287] iwlwifi 0000:04:00.0: 0x20000000 | FSEQ_ERROR_CODE
[ 92.061334] iwlwifi 0000:04:00.0: 0x80290021 | FSEQ_TOP_INIT_VERSION
[ 92.061381] iwlwifi 0000:04:00.0: 0x00050008 | FSEQ_CNVIO_INIT_VERSION
[ 92.061429] iwlwifi 0000:04:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[ 92.061476] iwlwifi 0000:04:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[ 92.061522] iwlwifi 0000:04:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 92.061568] iwlwifi 0000:04:00.0: 0x00100530 | FSEQ_CNVI_ID
[ 92.061615] iwlwifi 0000:04:00.0: 0x00000532 | FSEQ_CNVR_ID
[ 92.061661] iwlwifi 0000:04:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[ 92.061709] iwlwifi 0000:04:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[ 92.061758] iwlwifi 0000:04:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 92.061806] iwlwifi 0000:04:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 92.061853] iwlwifi 0000:04:00.0: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[ 94.364428] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_gpu_info.bin
[ 94.395165] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_sdma.bin
[ 94.400144] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_asd.bin
[ 94.401138] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_ta.bin
[ 94.402990] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_dmcu.bin
[ 94.403538] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_pfp.bin
[ 94.403743] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_me.bin
[ 94.404477] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_ce.bin
[ 94.404695] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_rlc.bin
[ 94.405678] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_mec.bin
[ 94.406485] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_mec2.bin
[ 94.409810] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_vcn.bin
[ 94.409820] [drm] Found VCN firmware Version ENC: 1.13 DEC: 2 VEP: 0 Revision: 4
[ 94.409840] amdgpu 0000:05:00.0: amdgpu: Will use PSP to load VCN firmware
[ 94.506692] amdgpu 0000:05:00.0: amdgpu: RAS: optional ras ta ucode is not available
[ 94.515505] amdgpu 0000:05:00.0: amdgpu: RAP: optional rap ta ucode is not available
[ 94.752133] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 94.761439] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.sfi
[ 94.761508] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 94.766485] Bluetooth: hci0: Firmware Version: 15-45.22
[ 95.548486] iwlwifi 0000:04:00.0: WRT: Failed to dump region: id=21, type=10
[ 95.548563] iwlwifi 0000:04:00.0: WRT: Failed to dump region: id=22, type=10
[ 96.293972] Bluetooth: hci0: Waiting for firmware download to complete
[ 96.294947] Bluetooth: hci0: Firmware loaded in 1497466 usecs
[ 96.314584] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.ddc
[ 96.325969] Bluetooth: hci0: Firmware revision 0.3 build 15 week 45 2022
[ 102.355755] iwlwifi 0000:04:00.0: Hardware error detected. Restarting.
[ 105.834102] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-3.fw
Code: Select all
[ 0.000000] Linux version 6.1.0-21-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03)
[ 0.098676] Spectre V2 : Enabling Speculation Barrier for firmware calls
[ 0.303196] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.341169] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 0.630920] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
[ 7.959303] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[ 7.970687] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[ 7.981517] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[ 8.059908] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-72.ucode
[ 8.059929] iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver
[ 8.059954] iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[ 8.067421] iwlwifi 0000:04:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 8.067427] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[ 8.067513] iwlwifi 0000:04:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 8.067520] iwlwifi 0000:04:00.0: loaded firmware version 72.daa05125.0 cc-a0-72.ucode op_mode iwlmvm
[ 8.310547] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[ 8.442233] iwlwifi 0000:04:00.0: Detected RF HR B3, rfid=0x10a100
[ 8.507519] iwlwifi 0000:04:00.0: base HW address: c8:5e:a9:67:12:86
[ 9.579920] psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x11, buttons: 3/3
[ 10.036234] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_gpu_info.bin
[ 10.065717] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_sdma.bin
[ 10.070903] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_asd.bin
[ 10.071149] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_ta.bin
[ 10.074547] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_dmcu.bin
[ 10.075521] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_pfp.bin
[ 10.075746] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_me.bin
[ 10.076434] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_ce.bin
[ 10.076628] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_rlc.bin
[ 10.078706] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_mec.bin
[ 10.080047] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_mec2.bin
[ 10.089199] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_vcn.bin
[ 10.089212] [drm] Found VCN firmware Version ENC: 1.13 DEC: 2 VEP: 0 Revision: 4
[ 10.089237] amdgpu 0000:05:00.0: amdgpu: Will use PSP to load VCN firmware
[ 10.184839] amdgpu 0000:05:00.0: amdgpu: RAS: optional ras ta ucode is not available
[ 10.193511] amdgpu 0000:05:00.0: amdgpu: RAP: optional rap ta ucode is not available
[ 10.290522] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.sfi
[ 10.290530] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 10.290556] Bluetooth: hci0: Firmware Version: 15-45.22
[ 10.290558] Bluetooth: hci0: Firmware already loaded
[ 14.032347] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-3.fw
Code: Select all
firmware-iwlwifi:
Installed: 20230210-5
Candidate: 20230210-5
Version table:
*** 20230210-5 500
500 http://deb.debian.org/debian bookworm/non-free-firmware amd64 Packages
500 http://deb.debian.org/debian bookworm/non-free-firmware i386 Packages
100 /var/lib/dpkg/status
Hope this info can help!
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Wed Mar 12, 2025 1:37 pm
by kmathern
Code: Select all
[ 94.752133] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 94.761439] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.sfi
[ 94.761508] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 94.766485] Bluetooth: hci0: Firmware Version: 15-45.22
[ 95.548486] iwlwifi 0000:04:00.0: WRT: Failed to dump region: id=21, type=10
[ 95.548563] iwlwifi 0000:04:00.0: WRT: Failed to dump region: id=22, type=10
[ 96.293972] Bluetooth: hci0: Waiting for firmware download to complete
[ 96.294947] Bluetooth: hci0: Firmware loaded in 1497466 usecs
[ 96.314584] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.ddc
[ 96.325969] Bluetooth: hci0: Firmware revision 0.3 build 15 week 45 2022
Code: Select all
[ 10.290522] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.sfi
[ 10.290530] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 10.290556] Bluetooth: hci0: Firmware Version: 15-45.22
[ 10.290558] Bluetooth: hci0: Firmware already loaded
It looks like it's not actually loading the firmware in the 2nd one, it says it's already loaded. I wonder if you can force it to reload the firmware each time?
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Thu Mar 13, 2025 2:47 am
by andre
kmathern wrote: Wed Mar 12, 2025 1:37 pm
It looks like it's not actually loading the firmware in the 2nd one, it says it's already loaded. I wonder if you can force it to reload the firmware each time?
I'm confused by your question. I'm just an average user and I only have a general idea of how the operating system works. About the firmware.. If I understand correctly, updating / downloading firmware is a rather rare process. And once downloaded, the firmware will not disappear anywhere.
In any case, thank you for participating in solving my problem.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 15, 2025 2:57 pm
by andre
Hi!
Some idea please about my issue.
Looks like my problem too rare, and I have very little chance of solving it (((
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 15, 2025 3:29 pm
by CharlesV
Something very odd in that firmware saying that it IS already loaded. I am going to suggest to update your linux-firmware to the very latest. There are a number of things that have been updated since your version
Code: Select all
firmware-iwlwifi:
Installed: 20230210-5
and the latest linux-firmware shows updates to that package as late as 20250311 !
You can update your linux firmware as follows:
Save a copy of your current /lib/firmware/ just in case... and personally, I would do a timeshift before proceeding.
and then update is with this:
Code: Select all
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20250311.tar.gz ; tar -xf linux-firmware-20250311.tar.gz ; cd linux-firmware-20250311 ; sudo cp -R * /lib/firmware/ ; sudo update-initramfs -uk all
verify no issues / error messages and then I would shut all the way down. ( ie power off ). Wait 30 seconds and then power back up and test.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 15, 2025 3:45 pm
by CharlesV
There also appears to be a number of posts about this model having issues with "disappearing bluetooth". Some are resolved with different drivers (windows), some with bios updates.
If the above firmware update doesnt help this situation... and a bios update also does not resolve it.. you may find the best solution is to pickup that bluetooth adapter I linked back a few posts ;-/
https://support.lenovo.com/us/en/solutions/ht506394/
https://superuser.com/questions/1709718 ... th-windows
https://www.reddit.com/r/LenovoLegion/c ... th_issues/
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 15, 2025 3:47 pm
by Tom Dooley
CharlesV wrote: Sat Mar 15, 2025 3:29 pm
Save a copy of your current /lib/firmware/ just in case... and personally, I would do a timeshift before proceeding.
You don't seem to be sure about the advice you're giving. Cause:
CharlesV wrote: Sat Mar 15, 2025 3:29 pm
Code: Select all
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20250311.tar.gz ; tar -xf linux-firmware-20250311.tar.gz ; cd linux-firmware-20250311 ; sudo cp -R * /lib/firmware/ ; sudo update-initramfs -uk all
This 1 liner looks very familiar from someone else. Even the
-uk all part at the end is as is .
P.S. Don't worry, it'll work, no need to backup. However if you do not
apt-mark hold "all" the firmware packages they'll revert back to older (than 20250311) when there are "updates".
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 15, 2025 3:57 pm
by j2mcgreg
Tom Dooley wrote: Sat Mar 15, 2025 3:47 pm
CharlesV wrote: Sat Mar 15, 2025 3:29 pm
Save a copy of your current /lib/firmware/ just in case... and personally, I would do a timeshift before proceeding.
You don't seem to be sure about the advice you're giving. Cause:
CharlesV wrote: Sat Mar 15, 2025 3:29 pm
Code: Select all
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20250311.tar.gz ; tar -xf linux-firmware-20250311.tar.gz ; cd linux-firmware-20250311 ; sudo cp -R * /lib/firmware/ ; sudo update-initramfs -uk all
This 1 liner looks very familiar from someone else. Even the
-uk all part at the end is as is .
Lose the attitude.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 15, 2025 4:01 pm
by CharlesV
@Tom Dooley I try to let everyone know that backing up your system before you do a major tweak is a no brainer. Things can (and do sometimes) go wrong.
In my opinion... NOT telling someone to backup first is an issue and VERY poor tech.
And if you have a problem with that.. .you are free to leave the forum. ( AND yes.. loose the attitude please .. there is no reason for it.)
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 15, 2025 4:05 pm
by Tom Dooley
In almost all forums they tell you either to use your own words or "quote", otherwise you'll get banned just for this reason.
So, is this all you can say? "lose blah blah" or "eave the forum" as "moderato"rs ?
I hope you also read the P.S. part.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sat Mar 15, 2025 4:50 pm
by Eadwine Rose
Banned.
@andre, please disregard TD's posts. Sorry for the distraction.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Sun Mar 16, 2025 12:34 am
by Helen-Earth
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Tue Mar 18, 2025 1:48 am
by andre
kmathern wrote: Wed Mar 12, 2025 1:37 pm
...
It looks like it's not actually loading the firmware in the 2nd one, it says it's already loaded. I wonder if you can force it to reload the firmware each time?
I also executed
sudo dmesg | grep -Ei 'iwl|firmware|ucode|Linux version' command for
Debian and there also row "
Firmware already loaded":
Code: Select all
[ 0.000000] Linux version 6.1.0-29-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.123-1 (2025-01-02)
[ 0.099426] Spectre V2 : Enabling Speculation Barrier for firmware calls
[ 0.309207] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.343996] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 1.090878] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
[ 3.340750] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_gpu_info.bin
[ 3.352372] psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x11, buttons: 3/3
[ 3.367034] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_sdma.bin
[ 3.367860] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_asd.bin
[ 3.367896] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_ta.bin
[ 3.368091] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/raven_dmcu.bin
[ 3.368125] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_pfp.bin
[ 3.368152] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_me.bin
[ 3.368176] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_ce.bin
[ 3.368210] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_rlc.bin
[ 3.368358] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_mec.bin
[ 3.368447] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_mec2.bin
[ 3.369280] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/picasso_vcn.bin
[ 3.369284] [drm] Found VCN firmware Version ENC: 1.13 DEC: 2 VEP: 0 Revision: 4
[ 3.369293] amdgpu 0000:05:00.0: amdgpu: Will use PSP to load VCN firmware
[ 3.463616] amdgpu 0000:05:00.0: amdgpu: RAS: optional ras ta ucode is not available
[ 3.472297] amdgpu 0000:05:00.0: amdgpu: RAP: optional rap ta ucode is not available
[ 5.782444] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[ 5.783097] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[ 5.831099] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[ 5.848389] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-72.ucode
[ 5.848432] iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver
[ 5.848470] iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[ 5.849728] iwlwifi 0000:04:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 5.849744] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[ 5.849776] iwlwifi 0000:04:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 5.849786] iwlwifi 0000:04:00.0: loaded firmware version 72.daa05125.0 cc-a0-72.ucode op_mode iwlmvm
[ 6.094515] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[ 6.224900] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.sfi
[ 6.224920] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 6.224960] Bluetooth: hci0: Firmware Version: 15-45.22
[ 6.224963] Bluetooth: hci0: Firmware already loaded
[ 6.245550] iwlwifi 0000:04:00.0: Detected RF HR B3, rfid=0x10a100
[ 6.311887] iwlwifi 0000:04:00.0: base HW address: c8:5e:a9:67:12:86
[ 6.400466] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0
[ 6.936448] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168g-3.fw
And I have idea why when I restored MX from snapshot, first output of above mentioned command gives output:
Code: Select all
[ 96.293972] Bluetooth: hci0: Waiting for firmware download to complete
[ 96.294947] Bluetooth: hci0: Firmware loaded in 1497466 usecs
The reason is when I created snapshot, I have only RTL8822BE, and AX200 was installed later..
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Tue Mar 18, 2025 2:04 am
by Stevo
Darn, Tom seemed grumpy, but knew what he was talking about. Don't hang down your head, Tom!
Anyway, the last two lines about loading the AX200 firmware seem to me saying that it found version 15 firmware, but 20 was already loaded. This is pretty normal when you want firmware to cover multiple kernel versions.
Also, firmware files aren't being downloaded from the net, but into the device from the files on your machine, in case anyone is confused.
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Tue Mar 18, 2025 9:45 am
by andre
CharlesV wrote: Sat Mar 15, 2025 3:29 pm
Something very odd in that firmware saying that it IS already loaded. I am going to suggest to update your linux-firmware to the very latest. There are a number of things that have been updated since your version
Code: Select all
firmware-iwlwifi:
Installed: 20230210-5
and the latest linux-firmware shows updates to that package as late as 20250311 !
You can update your linux firmware as follows:
...
Code: Select all
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20250311.tar.gz ; tar -xf linux-firmware-20250311.tar.gz ; cd linux-firmware-20250311 ; sudo cp -R * /lib/firmware/ ; sudo update-initramfs -uk all
Done at live usb. But after power off/on nothing changed.
'apt-cache policy firmware-iwlwifi' output is
same:
Code: Select all
... firmware-iwlwifi:
Installed: 20230210-5
Checked same command at Debian (hard drive). Result
same, but bluetooths works fine.
UPD: exact output from Debian:
Code: Select all
firmware-iwlwifi:
Installed: 20230210-5
Candidate: 20230210-5
Version table:
20240709-2~bpo12+1 100
100 http://deb.debian.org/debian bookworm-backports/non-free-firmware amd64 Packages
*** 20230210-5 500
500 http://deb.debian.org/debian bookworm/non-free-firmware amd64 Packages
100 /var/lib/dpkg/status
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Tue Mar 18, 2025 10:04 am
by andre
CharlesV wrote: Sat Mar 15, 2025 3:45 pm
There also appears to be a number of posts about this model having issues with "disappearing bluetooth". Some are resolved with different drivers (windows), some with bios updates.
If the above firmware update doesnt help this situation... and a bios update also does not resolve it.. you may find the best solution is to pickup that bluetooth adapter I linked back a few posts ;-/
...
The most problem with bluetooh at above links about Wndows.. My both adapters work perfectly at Windows, Debian, Ubuntu..
Also
very seldom, my adapters work at MX. Usually it happens after I restart after Windows or Debian or when I write new ISO, and first boot from it...
Later, in 5 .. 10 .. 30 minutes bluetooths fails and I can observe next:
Code: Select all
[ 939.180366] Bluetooth: hci0: Resetting usb device.
[ 939.343401] usb 3-1: reset full-speed USB device number 2 using xhci_hcd
[ 939.343416] usb 3-1: hub failed to enable device, error -108
[ 939.456352] usb 3-1: reset full-speed USB device number 2 using xhci_hcd
[ 939.456369] usb 3-1: hub failed to enable device, error -108
[ 939.569342] usb 3-1: reset full-speed USB device number 2 using xhci_hcd
[ 939.979340] usb 3-1: device not accepting address 2, error -108
[ 940.091339] usb 3-1: reset full-speed USB device number 2 using xhci_hcd
[ 940.508325] usb 3-1: device not accepting address 2, error -108
[ 940.508427] usb 3-1: USB disconnect, device number 2
[ 940.510404] usb usb3-port1: couldn't allocate usb_device
USB device disappears and even restart can't help. After that I need boot to windows or Debian..
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Tue Mar 18, 2025 11:04 am
by CharlesV
andre wrote: Tue Mar 18, 2025 9:45 am
CharlesV wrote: Sat Mar 15, 2025 3:29 pm
Something very odd in that firmware saying that it IS already loaded. I am going to suggest to update your linux-firmware to the very latest. There are a number of things that have been updated since your version
Code: Select all
firmware-iwlwifi:
Installed: 20230210-5
and the latest linux-firmware shows updates to that package as late as 20250311 !
You can update your linux firmware as follows:
...
Code: Select all
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20250311.tar.gz ; tar -xf linux-firmware-20250311.tar.gz ; cd linux-firmware-20250311 ; sudo cp -R * /lib/firmware/ ; sudo update-initramfs -uk all
Done at live usb. But after power off/on nothing changed.
'apt-cache policy firmware-iwlwifi' output is
same:
Code: Select all
... firmware-iwlwifi:
Installed: 20230210-5
Checked same command at Debian (hard drive). Result
same, but bluetooths works fine.
UPD: exact output from Debian:
Code: Select all
firmware-iwlwifi:
Installed: 20230210-5
Candidate: 20230210-5
Version table:
20240709-2~bpo12+1 100
100 http://deb.debian.org/debian bookworm-backports/non-free-firmware amd64 Packages
*** 20230210-5 500
500 http://deb.debian.org/debian bookworm/non-free-firmware amd64 Packages
100 /var/lib/dpkg/status
It would not help to do this on a live usb, you would have to do it on your regular install.
Something is being turned on or off at the windows run. And you DO have fast boot turned off right?
Is there anything in your bios that has bluetooth? any mention of it?
Re: RTL8822BE/AX200 Bluetooth trouble
Posted: Tue Mar 18, 2025 3:31 pm
by andre
CharlesV wrote: Tue Mar 18, 2025 11:04 am
Something is being turned on or off at the windows run. And you DO have fast boot turned off right?
Fast boot is disabled at Windows.
CharlesV wrote: Tue Mar 18, 2025 11:04 am
Is there anything in your bios that has bluetooth? any mention of it?
I can only enable/disable bluetooth from BIOS.