Results 1 to 6 of 6

Thread: No bluetooth with openSUSE TW and intel 8260

  1. #1

    Default No bluetooth with openSUSE TW and intel 8260

    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
    Code:
    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.

  2. #2
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    6,725

    Default AW: No bluetooth with openSUSE TW and intel 8260

    Do you shutdown Windows without any fastboot Options?

    Please post:
    Code:
    /usr/sbin/rfkill list all

  3. #3

    Default Re: No bluetooth with openSUSE TW and intel 8260

    That's output before doing anything with the bluetooth:
    Code:
    /usr/sbin/rfkill list all
    0: phy0: Wireless LAN
            Soft blocked: no
            Hard blocked: no
    1: hci0: Bluetooth
            Soft blocked: no
            Hard blocked: no
    
    
    Code:
    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)
    
    Code:
    dmesg | grep Blue    
    [   14.703362] Bluetooth: Core ver 2.22
    [   14.703373] Bluetooth: HCI device and connection manager initialized
    [   14.703375] Bluetooth: HCI socket layer initialized
    [   14.703377] Bluetooth: L2CAP socket layer initialized
    [   14.703381] Bluetooth: SCO socket layer initialized
    [   14.789603] Bluetooth: HCI UART driver ver 2.3
    [   14.789605] Bluetooth: HCI UART protocol H4 registered
    [   14.789606] Bluetooth: HCI UART protocol BCSP registered
    [   14.789621] Bluetooth: HCI UART protocol LL registered
    [   14.789622] Bluetooth: HCI UART protocol ATH3K registered
    [   14.789623] Bluetooth: HCI UART protocol Three-wire (H5) registered
    [   14.789654] Bluetooth: HCI UART protocol Intel registered
    [   14.789676] Bluetooth: HCI UART protocol Broadcom registered
    [   14.789676] Bluetooth: HCI UART protocol QCA registered
    [   14.789677] Bluetooth: HCI UART protocol AG6XX registered
    [   14.789678] Bluetooth: HCI UART protocol Marvell registered
    [   16.077907] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
    [   16.084870] Bluetooth: hci0: Device revision is 5
    [   16.084873] Bluetooth: hci0: Secure boot is enabled
    [   16.084874] Bluetooth: hci0: OTP lock is enabled
    [   16.084876] Bluetooth: hci0: API lock is enabled
    [   16.084878] Bluetooth: hci0: Debug lock is disabled
    [   16.084880] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
    [   16.087702] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
    [   16.555333] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [   16.555335] Bluetooth: BNEP filters: protocol multicast
    [   16.555339] Bluetooth: BNEP socket layer initialized
    [   17.536850] Bluetooth: hci0: Waiting for firmware download to complete
    [   17.536852] Bluetooth: hci0: Firmware loaded in 1425846 usecs
    [   17.536903] Bluetooth: hci0: Waiting for device to boot
    [   17.547823] Bluetooth: hci0: Device booted in 10679 usecs
    [   17.547896] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
    [   17.551810] Bluetooth: hci0: Applying Intel DDC parameters completed
    [   36.840871] Bluetooth: RFCOMM TTY layer initialized
    [   36.840911] Bluetooth: RFCOMM socket layer initialized
    [   36.840925] Bluetooth: 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

    Code:
    /usr/sbin/rfkill list all
    0: phy0: Wireless LAN
            Soft blocked: no
            Hard blocked: no
    
    
    Code:
    sudo hciconfig -a hci0    
    [sudo] password for root:  
    Can't get device info: No such device
    
    
    Code:
    dmesg | grep Blue         
    [   19.451806] Bluetooth: Core ver 2.22
    [   19.451824] Bluetooth: HCI device and connection manager initialized
    [   19.451827] Bluetooth: HCI socket layer initialized
    [   19.451829] Bluetooth: L2CAP socket layer initialized
    [   19.451833] Bluetooth: SCO socket layer initialized
    [   19.471000] Bluetooth: HCI UART driver ver 2.3
    [   19.471002] Bluetooth: HCI UART protocol H4 registered
    [   19.471003] Bluetooth: HCI UART protocol BCSP registered
    [   19.471019] Bluetooth: HCI UART protocol LL registered
    [   19.471020] Bluetooth: HCI UART protocol ATH3K registered
    [   19.471020] Bluetooth: HCI UART protocol Three-wire (H5) registered
    [   19.471051] Bluetooth: HCI UART protocol Intel registered
    [   19.471075] Bluetooth: HCI UART protocol Broadcom registered
    [   19.471076] Bluetooth: HCI UART protocol QCA registered
    [   19.471077] Bluetooth: HCI UART protocol AG6XX registered
    [   19.471077] Bluetooth: HCI UART protocol Marvell registered
    [   20.565904] Bluetooth: hci0: Firmware revision 0.0 build 118 week 50 2016
    [   21.567738] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [   21.567740] Bluetooth: BNEP filters: protocol multicast
    [   21.567743] Bluetooth: BNEP socket layer initialized
    [   53.435705] Bluetooth: RFCOMM TTY layer initialized
    [   53.435716] Bluetooth: RFCOMM socket layer initialized
    [   53.435725] Bluetooth: RFCOMM ver 1.11
    [   84.027510] Bluetooth: hci0 command 0x2005 tx timeout
    
    

  4. #4

    Default Re: No bluetooth with openSUSE TW and intel 8260

    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.

  5. #5

    Default Re: No bluetooth with openSUSE TW and intel 8260

    Hello!
    I had the same problem and I've found a weird solution here https://forums.opensuse.org/showthre...72#post2849272 But it worked for me.

  6. #6

    Default Re: No bluetooth with openSUSE TW and intel 8260

    Quote Originally Posted by r0mp3t3ch0s View Post
    Hello!
    I had the same problem and I've found a weird solution here https://forums.opensuse.org/showthre...72#post2849272 But it worked for me.
    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.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •