public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217805] Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area)
Date: Fri, 08 Dec 2023 08:23:22 +0000	[thread overview]
Message-ID: <bug-217805-62941-skn5Ofei0G@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217805-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217805

--- Comment #3 from François Armand (fanf42@gmail.com) ---
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

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2023-12-08  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  8:21 [Bug 217805] New: Qualcomm NFA725A on T14s AMD Gen3: Bluetooth: hci0: Failed to send headers (or body or access otp area) bugzilla-daemon
2023-08-28  7:17 ` [Bug 217805] " bugzilla-daemon
2023-08-31 13:26 ` bugzilla-daemon
2023-12-08  8:23 ` bugzilla-daemon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-217805-62941-skn5Ofei0G@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox