Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#65560 - [linux-firmware] Bluetooth controller not detected as of 20200204.b791e15-1

Attached to Project: Arch Linux
Opened by Adam S Levy (alaskanarcher) - Wednesday, 19 February 2020, 19:50 GMT
Last edited by freswa (frederik) - Thursday, 20 February 2020, 09:00 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Laurent Carlier (lordheavy)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
After upgrading linux-firmware to 20200204, my bluetooth controller disappeared. Downgrading linux-firmware to 20200122.1eb2408-1 restored functionality.

I originally posted in the forums with some additional information here: https://bbs.archlinux.org/viewtopic.php?pid=1888422#p1888422

My laptop is a Clevo N130WU. I believe the bluetooth is integrated with the wireless card. With bluetooth working, the output of `# lspci -vt` for this card is

[code]
3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
Subsystem: Intel Corporation Dual Band Wireless-AC 8265
Flags: bus master, fast devsel, latency 0, IRQ 144
Memory at dc100000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number f8-34-41-ff-ff-d2-40-b0
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] L1 PM Substates
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
[/code]
This task depends upon

Closed by  freswa (frederik)
Thursday, 20 February 2020, 09:00 GMT
Reason for closing:  Not a bug
Additional comments about closing:  not reproducible
Comment by Adam S Levy (alaskanarcher) - Thursday, 20 February 2020, 01:24 GMT
This resolved itself when I downgraded firmware. But I can't reproduce it when I upgrade this package back to the latest version. Very odd but possible I missed something.

Requesting closure for now.

Loading...