On 10/13/26 11:03, Thorsten Leemhuis wrote:
> On 10/12/26 19:28, Salvatore Bonaccorso wrote:
>> On Mon, Oct 12, 2026 at 02:00:18PM +0200, Thorsten Leemhuis wrote:
>>> On 10/4/26 18:29, Sasha Levin wrote:
>>>>> In Debian Erik Brangs reported that after the update from 6.12.107 to
>>>>> 6.12.111, specifically with the backport of 980084de4d9b ("Bluetooth:
>>>>> btusb: Add ASUS USB-BT540 for Realtek 8761CU") Bluetooth is not
>>>>> anymore working, the full report is found at
>>>>> https://bugs.debian.org/1149377 .
>>>>> | [ 38.138881] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761cu_fw
>>>>> not found
This is still unresolved. Salvatore, Erik, and/or Christoph, could you
confirm my analyses below -- and if it is ask the stable team for the
reverts?
>>>> The stable code matches mainline. The failure is a missing firmware file:
>>>> rtl_bt/rtl8761cu_fw.bin has been in linux-firmware only since 20251111,
>>>> and Debian trixie's firmware-realtek 20250410-2 does not have it.
>>>>
>>>> Marcel, Luiz: could you, or Christoph Zwerschke as the author of the ID
>>>> commit, send an upstream revert, or a fallback to ROM firmware when
>>>> rtl8761cu_fw.bin is missing? Stable will take it for 7.2, 6.18 and 6.12
>>>> through the normal Cc: stable route once it is in mainline.
>>>
>>> Hmmm, that was a week (granted: with the LPC) ago and nothing happened.
>>> Anyone working on this?
>>>
>>> If not: Should we revert 980084de4d9b and its backports? Or only the
>>> backports to older stable series?
>>>
>>> Strictly speaking it should be the former due to our policies wrt to
>>> firmware -- but I guess most users of a more recent kernels also have a
>>> newer firmware, so I wonder if reverting the change might do more harm
>>> then good now.
>>
>> If my understanding is correct from a earlier fixed regression in the
>> ariea, aka
>> https://lore.kernel.org/regressions/[email protected]/
There Christoph asked "please revert them from every tree below 6.19" --
but they afaics were only reverted for 6.6 and earlier.
"Them" meant the backports of these:
* 980084de4d9b25 ("Bluetooth: btusb: Add ASUS USB-BT540 for Realtek
8761CU") [v7.3-rc1]
* 6f0624b4427e38 ("Bluetooth: btusb: Add ASUS USB-BT600 for Realtek
8761CU") [v7.3-rc1]
Maybe because 4a23ce935f74d1 ("Bluetooth: btrtl: Add the support for
RTL8761CUV") was included in v6.18.53, v6.12.111. Which lead to the
current situation with "firmware file rtl_bt/rtl8761cu_fw not found" in
Debian.
>> should then not only 980084de4d9b ("Bluetooth: btusb: Add ASUS
>> USB-BT540 for Realtek 8761CU") be reverted, but as well along
>> 6f0624b4427e ("Bluetooth: btusb: Add ASUS USB-BT600 for Realtek
>> 8761CU") and as well 4a23ce935f74 ("Bluetooth: btrtl: Add the support
>> for RTL8761CUV")?
>
> Maybe, I didn't look closer,
I did meanwhile and agree, the backports of these should be reverted
from 6.18.y and 6.12.y:
* 980084de4d9b25 ("Bluetooth: btusb: Add ASUS USB-BT540 for Realtek
8761CU") [v7.3-rc1]
* 6f0624b4427e38 ("Bluetooth: btusb: Add ASUS USB-BT600 for Realtek
8761CU") [v7.3-rc1]
* 4a23ce935f74d1 ("Bluetooth: btrtl: Add the support for RTL8761CUV")
[v6.19-rc1]
At least if the problem wasn't resolved meanwhile, but that wasn't the
case afaics -- or did I miss it? Salvatore, Erik, or Christoph? Or was
it meanwhile agree on to fix this differently, for example by including
that file in a linux-firmware update maybe?
Ciao, Thorsten
but that's why reverting in mainline likely
> really is a bad idea: it might cause a regression for users that depend
> on those changes (one of which is from 6.19).
>
> So I guess reverting some or all of those backports in "older stable
> series", as Sasha suggested, might be the best -- but I guess it would
> be good if someone with more knowledge in this area could provide an
> opinion.
