Bug 217805
| Summary: | Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area) | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | François Armand (fanf42) |
| Component: | Bluetooth | Assignee: | linux-bluetooth (linux-bluetooth) |
| Status: | NEW --- | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | Subsystem: | ||
| Regression: | No | Bisected commit-id: | |
| Attachments: | lsmod | ||
|
Description
François Armand
2023-08-18 08:21:51 UTC
Created attachment 304965 [details]
lsmod
I failed to attach lsmod, so here we go.
For info, I find that subject: https://superuser.com/a/1451102 So I tried to disable bluetooth in bios, boot, re-enable bluetooth in bios. With that, I was able to "unblock" the bluetooth adaptater in rfkill. But I still didn't have any controler listed in `bluethoothctl list`. I then tried to disable laptot battery ("power > servicing" option in bios) to see if a full cold restart does something. It does: I've came back to the initial state, where the controler can't be enabled at all. I tried the disable-then-enable-bluetooth-in-bios trick, but that time it doesn't do anything. I also notice than early in boot, I have that message: --- kernel: usb usb1-port3: connect-debounce failed --- Which seems to be link to the bluetooth controler (I don't have the message when bluetooth is disabled in bios). So it looks like an hardware problem right? More information on that subject: - the bluetooth antenna was physically disconnect from the chipset, I reconnected it. - now, I'm able to have bluetooth from an old ubuntu 22.04 live usb key, - I still don't have it from a modern linux 6.6.4 arch kernel The main difference I noticed happened when the firmware is loaded: - on ubuntu, where it works: Dec 08 07:00:36 ubuntu kernel: usb 1-3: new high-speed USB device number 2 using xhci_hcd ... Decrep 08 07:00:36 ubuntu kernel: usb 1-3.1: new full-speed USB device number 3 using xhci_hcd Dec 08 07:00:36 ubuntu kernel: usb 1-3.1: New USB device found, idVendor=10ab, idProduct=9309, bcdDevice= 0.01 Dec 08 07:00:36 ubuntu kernel: usb 1-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ... Dec 08 07:00:37 ubuntu kernel: thinkpad_acpi: radio switch found; radios are enabled ... Dec 08 07:00:37 ubuntu kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked .... - on the newer kernel: Dec 08 08:54:42 lalande21185 kernel: thinkpad_acpi: radio switch found; radios are enabled ... Dec 08 08:54:42 lalande21185 kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked Dec 08 07:00:3Dec 08 08:56:14 lalande21185 kernel: usb 1-3.1: new full-speed USB device number 5 using xhci_hcd Dec 08 08:56:14 lalande21185 kernel: usb 1-3.1: New USB device found, idVendor=10ab, idProduct=9309, bcdDevice= 0.01 Dec 08 08:56:14 lalande21185 kernel: usb 1-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Dec 08 08:56:15 lalande21185 kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00130201.bin Dec 08 08:56:15 lalande21185 kernel: Bluetooth: hci0: QCA: patch rome 0x130201 build 0x65e2, firmware rome 0x130201 build 0x38e6 Dec 08 08:56:15 lalande21185 kernel: Bluetooth: hci0: Failed to send headers (-71) Dec 08 08:56:15 lalande21185 kernel: usb 1-3.1: USB disconnect, device number 5 8 ubuntu kernel: Bluetooth: hci0: using NVM file: qca/nvm_usb_00130201_gf.bin Could it have something to do with the `thinkpad_acpi` module? The exact rome build is not the same too, which is expected I think for a newer kernel |