RTL8822BE/AX200 Bluetooth trouble

Message
Author
andre
Posts: 29
Joined: Thu Feb 13, 2025 4:49 am

Re: RTL8822BE/AX200 Bluetooth trouble

#31 Post 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]# 
:rolleyes:

andre
Posts: 29
Joined: Thu Feb 13, 2025 4:49 am

Re: RTL8822BE/AX200 Bluetooth trouble

#32 Post 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(
:rolleyes:

andre
Posts: 29
Joined: Thu Feb 13, 2025 4:49 am

Re: RTL8822BE/AX200 Bluetooth trouble

#33 Post by andre »

Last info.
Was downloaded MX 23.5 KDE, tested at live usb. Result - same: fails :rolleyes:
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.. 9_9

Any idea, please?

User avatar
CharlesV
Global Moderator
Posts: 7089
Joined: Sun Jul 07, 2019 5:11 pm

Re: RTL8822BE/AX200 Bluetooth trouble

#34 Post by CharlesV »

Interesting. What BT version is now installed an working?
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

andre
Posts: 29
Joined: Thu Feb 13, 2025 4:49 am

Re: RTL8822BE/AX200 Bluetooth trouble

#35 Post 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: 
hciconfig -a:

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)
buetoothctl -> show:

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

andre
Posts: 29
Joined: Thu Feb 13, 2025 4:49 am

Re: RTL8822BE/AX200 Bluetooth trouble

#36 Post 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.. :rolleyes:
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 :confused: ?

User avatar
CharlesV
Global Moderator
Posts: 7089
Joined: Sun Jul 07, 2019 5:11 pm

Re: RTL8822BE/AX200 Bluetooth trouble

#37 Post 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

Image
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

andre
Posts: 29
Joined: Thu Feb 13, 2025 4:49 am

Re: RTL8822BE/AX200 Bluetooth trouble

#38 Post 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

Image
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.

User avatar
kmathern
Developer
Posts: 2509
Joined: Wed Jul 12, 2006 2:26 pm

Re: RTL8822BE/AX200 Bluetooth trouble

#39 Post 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?

Code: Select all

apt-cache policy firmware-iwlwifi

andre
Posts: 29
Joined: Thu Feb 13, 2025 4:49 am

Re: RTL8822BE/AX200 Bluetooth trouble

#40 Post 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
sudo dmesg | grep -Ei 'iwl|firmware|ucode|Linux version' (after 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.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
apt-cache policy firmware-iwlwifi:

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!

Post Reply

Return to “Hardware /Configuration”