Having a problem with my WiFi / BT card - intel 8260. The hardware is fine, because it works without an issue on Windows (dual booting) but not on openSUSE. The WiFi works just fine, but bluetooth does not. However, it used to work on openSUSE as well until recently. Unfortunately, I don’t know it it was TW update or BIOS update on my XPS 9590 (now using bios v 1.6.1) that broke it.
Sometime, when I booth into TW, it shows that BT is enabled, bet if I try to scan for new device, it says that no bluetooth module is found.
Also, If i check hardware list before scanning bor BT device, it sais that
btusb
driver is loaded and if i check after scanning for a BT device there is nothing, as if hardware doesn’t even exist.
Some “googling” suggest that cmos reset is required to fix this, but I’m away for the holidays and can’t open my laptop to test it.
I guess some command output will be needed, but I don’t know what, so just ask away 
and thanks in advance.
Do you shutdown Windows without any fastboot Options?
Please post:
/usr/sbin/rfkill list all
That’s output before doing anything with the bluetooth:
/usr/sbin/rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
sudo hciconfig -a hci0
[sudo] password for root:
hci0: Type: Primary Bus: USB
BD Address: AC:ED:5C:2E:F9:D1 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN ISCAN
RX bytes:19391 acl:0 sco:0 events:2493 errors:0
TX bytes:597494 acl:0 sco:0 commands:2453 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: SLAVE ACCEPT
Name: 'Bluemoon Universal Bluetooth Host Controller'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: 4.2 (0x8) Revision: 0x100
LMP Version: 4.2 (0x8) Subversion: 0x100
Manufacturer: Intel Corp. (2)
dmesg | grep Blue
14.703362] **Blue**tooth: Core ver 2.22
14.703373] **Blue**tooth: HCI device and connection manager initialized
14.703375] **Blue**tooth: HCI socket layer initialized
14.703377] **Blue**tooth: L2CAP socket layer initialized
14.703381] **Blue**tooth: SCO socket layer initialized
14.789603] **Blue**tooth: HCI UART driver ver 2.3
14.789605] **Blue**tooth: HCI UART protocol H4 registered
14.789606] **Blue**tooth: HCI UART protocol BCSP registered
14.789621] **Blue**tooth: HCI UART protocol LL registered
14.789622] **Blue**tooth: HCI UART protocol ATH3K registered
14.789623] **Blue**tooth: HCI UART protocol Three-wire (H5) registered
14.789654] **Blue**tooth: HCI UART protocol Intel registered
14.789676] **Blue**tooth: HCI UART protocol Broadcom registered
14.789676] **Blue**tooth: HCI UART protocol QCA registered
14.789677] **Blue**tooth: HCI UART protocol AG6XX registered
14.789678] **Blue**tooth: HCI UART protocol Marvell registered
16.077907] **Blue**tooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
16.084870] **Blue**tooth: hci0: Device revision is 5
16.084873] **Blue**tooth: hci0: Secure boot is enabled
16.084874] **Blue**tooth: hci0: OTP lock is enabled
16.084876] **Blue**tooth: hci0: API lock is enabled
16.084878] **Blue**tooth: hci0: Debug lock is disabled
16.084880] **Blue**tooth: hci0: Minimum firmware build 1 week 10 2014
16.087702] **Blue**tooth: hci0: Found device firmware: intel/ibt-11-5.sfi
16.555333] **Blue**tooth: BNEP (Ethernet Emulation) ver 1.3
16.555335] **Blue**tooth: BNEP filters: protocol multicast
16.555339] **Blue**tooth: BNEP socket layer initialized
17.536850] **Blue**tooth: hci0: Waiting for firmware download to complete
17.536852] **Blue**tooth: hci0: Firmware loaded in 1425846 usecs
17.536903] **Blue**tooth: hci0: Waiting for device to boot
17.547823] **Blue**tooth: hci0: Device booted in 10679 usecs
17.547896] **Blue**tooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
17.551810] **Blue**tooth: hci0: Applying Intel DDC parameters completed
36.840871] **Blue**tooth: RFCOMM TTY layer initialized
36.840911] **Blue**tooth: RFCOMM socket layer initialized
36.840925] **Blue**tooth: RFCOMM ver 1.11
However, this morning (performed distro upgrade last night), hci0 device does not “vanish” after performing a scan, but does not detect any bluetooth devices.
And after a reboot, i have performed a device scan (via GUI) and hci0 has “vanished” again. Outpur after scan is
/usr/sbin/rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
sudo hciconfig -a hci0
[sudo] password for root:
Can't get device info: No such device
dmesg | grep Blue
19.451806] **Blue**tooth: Core ver 2.22
19.451824] **Blue**tooth: HCI device and connection manager initialized
19.451827] **Blue**tooth: HCI socket layer initialized
19.451829] **Blue**tooth: L2CAP socket layer initialized
19.451833] **Blue**tooth: SCO socket layer initialized
19.471000] **Blue**tooth: HCI UART driver ver 2.3
19.471002] **Blue**tooth: HCI UART protocol H4 registered
19.471003] **Blue**tooth: HCI UART protocol BCSP registered
19.471019] **Blue**tooth: HCI UART protocol LL registered
19.471020] **Blue**tooth: HCI UART protocol ATH3K registered
19.471020] **Blue**tooth: HCI UART protocol Three-wire (H5) registered
19.471051] **Blue**tooth: HCI UART protocol Intel registered
19.471075] **Blue**tooth: HCI UART protocol Broadcom registered
19.471076] **Blue**tooth: HCI UART protocol QCA registered
19.471077] **Blue**tooth: HCI UART protocol AG6XX registered
19.471077] **Blue**tooth: HCI UART protocol Marvell registered
20.565904] **Blue**tooth: hci0: Firmware revision 0.0 build 118 week 50 2016
21.567738] **Blue**tooth: BNEP (Ethernet Emulation) ver 1.3
21.567740] **Blue**tooth: BNEP filters: protocol multicast
21.567743] **Blue**tooth: BNEP socket layer initialized
53.435705] **Blue**tooth: RFCOMM TTY layer initialized
53.435716] **Blue**tooth: RFCOMM socket layer initialized
53.435725] **Blue**tooth: RFCOMM ver 1.11
84.027510] **Blue**tooth: hci0 command 0x2005 tx timeout
I’ve tried this thing.
removed intel 8260 module, installed the original broadcom module. Botteet into Win 10 - it works, booted into opensSUSE TW - it works. Well, it has it’s glitches, buts it’s functional for most part.
Then, installed intel 8260. booted into Win 10 - it works, booted into openSUSE TW - it works, BUT, I’be booted into openSUSE TW this morning and hci0 again “vanishes” as soon as i try to connect any BT device to a laptop.
Glad it worked for you. Unfortunately, It didn’t work for me.
Removing the component and installing it again worked once, but after a second reboot it was not working again.
Booting to another distro didn’t help either.
I can’t remove CMOS battery (well… I can, but there is quite a bit of disassembly to be done since smos battery is between MoBo and keyboard on XPS 9550).
So, my solution was to go back to using broadcom module. I do need to boot into windows one in a while to “reset it” (i.e. boot into windows and pair with some BT device, then reboot), but it works in general sense.