Page 1 of 3 123 LastLast
Results 1 to 10 of 28

Thread: Qualcomm Atheros Bluetooth 4.0 (04CA 3014) is not detected

  1. #1

    Default Qualcomm Atheros Bluetooth 4.0 (04CA 3014) is not detected

    I have an Acer Aspire E15 laptop (model number E5-573-54ZV) that came with Windows 10 and a built-in Bluetooth 4.0 adapter. While using Windows, I'm able to use the Bluetooth adapter.


    I've installed openSUSE Leap 42.2 in dual boot. While using openSUSE, the Bluetooth adapter is the only piece of hardware that does not work. It seems like it is not even detected.


    A report made using AIDA64 for Windows shows:


    Code:
    04CA 3014    Qualcomm Atheros Bluetooth 4.0
    It appears in the USB devices section, so it is attached to the USB bus.

    Someone made it work on Linux Mint: https://forums.linuxmint.com/viewtopic.php?t=217091


    How can I make that Bluetooth adapter work on openSUSE?


    Thank you in advance!

    Some commands and their outputs:

    Code:
    # lspci
    00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
    00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
    00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
    00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
    00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
    00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
    00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
    00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
    00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
    00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
    00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
    00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
    00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
    02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
    03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)
    I have two built-in network adapters:


    1. Realtek RTL8111/8168/8411 PCI-E Gigabit Ethernet Adapter [10ec:8168], if I run ifconfig it shows as eth0
    2. Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036], if I run ifconfig it shows as wlan0



    Code:
    # lsusb
    Bus 003 Device 002: ID 8087:8001 Intel Corp. 
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 002: ID 0424:5537 Standard Microsystems Corp. 
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
    Bus 001 Device 005: ID 1bcf:2c81 Sunplus Innovation Technology Inc. 
    Bus 001 Device 006: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
    Bus 001 Device 004: ID 2357:010d  
    Bus 001 Device 002: ID 0424:2137 Standard Microsystems Corp. 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Code:
    # usb-devices
    
    
    T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh=11
    D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=1d6b ProdID=0002 Rev=04.10
    S:  Manufacturer=Linux 4.10.11-1.gbd70196-vanilla xhci-hcd
    S:  Product=xHCI Host Controller
    S:  SerialNumber=0000:00:14.0
    C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
    
    
    T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=480 MxCh= 7
    D:  Ver= 2.10 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
    P:  Vendor=0424 ProdID=2137 Rev=60.80
    S:  Manufacturer=SMSC
    S:  Product=USB2137B
    C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
    I:  If#= 0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub
    
    
    T:  Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  4 Spd=480 MxCh= 0
    D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
    P:  Vendor=2357 ProdID=010d Rev=00.00
    S:  Manufacturer=Realtek
    S:  Product=802.11n NIC
    S:  SerialNumber=123456
    C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
    I:  If#= 0 Alt= 0 #EPs= 5 Cls=ff(vend.) Sub=ff Prot=ff Driver=rtl8812au
    
    
    T:  Bus=01 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#=  6 Spd=12  MxCh= 0
    D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
    P:  Vendor=045e ProdID=0745 Rev=06.56
    S:  Manufacturer=Microsoft
    S:  Product=Microsoft® 2.4GHz Transceiver v8.0
    C:  #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=100mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
    I:  If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
    I:  If#= 2 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
    
    
    T:  Bus=01 Lev=01 Prnt=01 Port=06 Cnt=02 Dev#=  5 Spd=480 MxCh= 0
    D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=1bcf ProdID=2c81 Rev=00.05
    S:  Manufacturer=NC2141103M50708908LM05
    S:  Product=HD WebCam
    C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
    I:  If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
    
    
    T:  Bus=01 Lev=01 Prnt=01 Port=07 Cnt=03 Dev#=  7 Spd=480 MxCh= 0
    D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs=  1
    P:  Vendor=0bda ProdID=0129 Rev=39.60
    S:  Manufacturer=Generic
    S:  Product=USB2.0-CRW
    S:  SerialNumber=20100201396000000
    C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
    I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=06 Prot=50 Driver=rtsx_usb
    
    
    T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 4
    D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
    P:  Vendor=1d6b ProdID=0003 Rev=04.10
    S:  Manufacturer=Linux 4.10.11-1.gbd70196-vanilla xhci-hcd
    S:  Product=xHCI Host Controller
    S:  SerialNumber=0000:00:14.0
    C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
    
    
    T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=5000 MxCh= 7
    D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
    P:  Vendor=0424 ProdID=5537 Rev=60.80
    S:  Manufacturer=SMSC
    S:  Product=USB5537B
    C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
    
    
    T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
    D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
    P:  Vendor=1d6b ProdID=0002 Rev=04.10
    S:  Manufacturer=Linux 4.10.11-1.gbd70196-vanilla ehci_hcd
    S:  Product=EHCI Host Controller
    S:  SerialNumber=0000:00:1d.0
    C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
    
    
    T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 8
    D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=8087 ProdID=8001 Rev=00.03
    C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

    Some notes about my USB devices:


    1. Microsoft Corp. Nano Transceiver v1.0 for Bluetooth (045e:0745) is the transceiver for my Microsoft Wireless Desktop 800 (wireless keyboard + mouse combo). I use it at home.
    2. I also have a third network adapter, TP-Link Archer T4U, which is a wireless dual band (802.11n/ac 2.4GHz/5GHz) USB adapter, I didn't find it in the above outputs, I have installed it following the instructions here and here, if I run ifconfig it shows as wlan1


    Code:
    # dmesg | egrep 'ath|wifi|hal'
    [   13.950073] ath: phy0: WB335 2-ANT card detected
    [   13.952609] ath: phy0: Set BT/WLAN RX diversity capability
    [   13.961812] ath: phy0: Enable LNA combining
    [   13.963776] ath: phy0: ASPM enabled: 0x42
    [   13.964565] ath: EEPROM regdomain: 0x6c
    [   13.964566] ath: EEPROM indicates we should expect a direct regpair map
    [   13.964567] ath: Country alpha2 being used: 00
    [   13.964567] ath: Regpair used: 0x6c
    [   16.927559] usbcore: registered new interface driver ath3k
    Code:
    # dmesg | egrep -i 'bluetooth|firm'
    [    0.565244] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
    [   14.921957] Bluetooth: Core ver 2.22
    [   14.926457] Bluetooth: HCI device and connection manager initialized
    [   14.929069] Bluetooth: HCI socket layer initialized
    [   14.929976] Bluetooth: L2CAP socket layer initialized
    [   14.930876] Bluetooth: SCO socket layer initialized
    [   81.227149] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [   81.227154] Bluetooth: BNEP filters: protocol multicast
    [   81.227159] Bluetooth: BNEP socket layer initialized
    Code:
    # uname -a
    Linux viny-notebook 4.10.11-1.gbd70196-vanilla #1 SMP PREEMPT Tue Apr 18 05:55:31 UTC 2017 (bd70196) x86_64 x86_64 x86_64 GNU/Linux
    What I have tried so far...


    Googling, I have found this kernel patch: https://patchwork.kernel.org/patch/8789671/

    If I have understood that page correctly, it has been applied upstream to the kernel 4.5 release.

    As openSUSE Leap 42.2 uses kernel 4.4.x, I installed the latest kernel release available from:

    http://download.opensuse.org/reposit...table/standard

    Today, 4.10.11, as you can see in the uname output. Doing that didn't make the Bluetooth adapter work.

  2. #2
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,981

    Default AW: Qualcomm Atheros Bluetooth 4.0 (04CA 3014) is not detected

    Is Bluetooth blocked:
    Code:
    /usr/sbin/rfkill list all
    That is the TP-Link:
    Code:
    Bus 001 Device 004: ID 2357:010d

  3. #3

    Default Re: AW: Qualcomm Atheros Bluetooth 4.0 (04CA 3014) is not detected

    Quote Originally Posted by Sauerland View Post
    Is Bluetooth blocked:
    Code:
    /usr/sbin/rfkill list all
    I think it is not:

    Code:
    # /usr/sbin/rfkill list all
    0: acer-wireless: Wireless LAN
        Soft blocked: no
        Hard blocked: no
    1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
    2: phy1: Wireless LAN
        Soft blocked: no
        Hard blocked: no
    Are phy0 and phy1 equivalent to wlan0 and wlan1? What is this acer-wireless?

    That is the TP-Link:
    Code:
    Bus 001 Device 004: ID 2357:010d
    Hmm now I see:

    Quote Originally Posted by vinyanalista View Post
    Code:
    # usb-devices
    
    ...
    
    T:  Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  4 Spd=480 MxCh= 0
    D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
    P:  Vendor=2357 ProdID=010d Rev=00.00
    S:  Manufacturer=Realtek
    S:  Product=802.11n NIC
    S:  SerialNumber=123456
    C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
    I:  If#= 0 Alt= 0 #EPs= 5 Cls=ff(vend.) Sub=ff Prot=ff Driver=rtl8812au
    You are right, because rtl8812au is the name of the driver. Thank you!

  4. #4
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,981

    Default AW: Qualcomm Atheros Bluetooth 4.0 (04CA 3014) is not detected

    Please post:
    Code:
    /sbin/lspci -nnk | grep -iA3 net
    to see the ID and the Driver.

  5. #5

    Default Re: AW: Qualcomm Atheros Bluetooth 4.0 (04CA 3014) is not detected

    Quote Originally Posted by Sauerland View Post
    Please post:
    Code:
    /sbin/lspci -nnk | grep -iA3 net
    to see the ID and the Driver.
    Code:
    # /sbin/lspci -nnk | grep -iA3 net
    02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
    	Subsystem: Acer Incorporated [ALI] Device [1025:098a]
    	Kernel driver in use: r8169
    	Kernel modules: r8169
    03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01)
    	Subsystem: Lite-On Communications Inc Device [11ad:0803]
    	Kernel driver in use: ath9k
    	Kernel modules: ath9k

  6. #6
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,981

    Default AW: Qualcomm Atheros Bluetooth 4.0 (04CA 3014) is not detected

    Did you also install kernel-firmware from the kernel:stable Repo?

    https://wiki.archlinux.org/index.php...ire_E11_Series

  7. #7

    Default Re: AW: Qualcomm Atheros Bluetooth 4.0 (04CA 3014) is not detected

    Quote Originally Posted by Sauerland View Post
    Did you also install kernel-firmware from the kernel:stable Repo?
    Yes, I did:

    Code:
    # zypper info kernel-firmware
    Loading repository data...
    Reading installed packages...
    
    
    Information for package kernel-firmware:
    ----------------------------------------
    Repository     : Kernel:stable                    
    Name           : kernel-firmware                  
    Version        : 20170404-35.1                    
    Arch           : noarch                           
    Vendor         : obs://build.opensuse.org/Kernel  
    Installed Size : 187.8 MiB                        
    Installed      : Yes                              
    Status         : up-to-date                       
    Source package : kernel-firmware-20170404-35.1.src
    Summary        : Linux kernel firmware files      
    Description    :                                  
        This package contains the firmware for in-kernel drivers that was
        previously included in the kernel. It is shared by all kernels >=
        2.6.27-rc1.
    Thank you for the directions. I've read the section Bluetooth can't find any devices and followed its instructions. Let me quote them here.

    Some laptops have an Atheros AR9565 Wifi/Bluetooth controller built in:


    Code:
    # lsusb
    ...
    Bus 001 Device 005: ID 04ca:3014 Lite-On Technology Corp. Qualcoom Atheros Bluetooth
    ...
    Wifi works fine, the bluetooth controller is recognized but no bluetooth devices are found. The problem is that as of Linux 4.3.3 this devices is not listed in ath9k.ko which loads the firmware files and patches into the Atheros bluetooth controllers.
    Indeed, my laptop has that controller. But it's important to note that, in my case, that controller is not even recognized, as lsusb does not show it. Going on...

    Quick and dirty fix, patching this USB ID into the modules (from: https://bbs.archlinux.org/viewtopic.php?pid=1433352):
    Here is what I did (from https://bbs.archlinux.org/viewtopic....33352#p1433352):

    Code:
    # cd /lib/modules/`uname -r`/kernel/drivers/bluetooth/
    # cp ath3k.ko ath3k.ko.backup
    # cp btusb.ko btusb.ko.backup
    # sed -e 's/\xf3\x0c\x05\x30/\xf3\x0c\x05\xe0/g' ath3k.ko > at.ko
    # sed -e 's/\xf3\x0c\x05\x30/\xf3\x0c\x05\xe0/g' btusb.ko > bt.ko
    # mv at.ko ath3k.ko
    # mv bt.ko btusb.ko
    # rmmod ath3k
    # rmmod btusb
    # modprobe btusb
    # modprobe ath3k

    You will still need to copy two firmware files (AthrBT_0x31010100.dfu and ramps_0x31010100_40.dfu) under /lib/firmware/ar3k.
    Curiously, they seem to be already there:

    Code:
    # cd /lib/firmware/ar3k/
    # ls -lah
    total 380K
    drwxr-xr-x 1 root root  884 Abr 20 21:11 .
    drwxr-xr-x 1 root root 9,9K Abr 21 10:02 ..
    drwxr-xr-x 1 root root   74 Abr 20 21:11 1020200
    drwxr-xr-x 1 root root   46 Abr 20 21:11 1020201
    drwxr-xr-x 1 root root   72 Abr 20 21:11 1020201coex
    drwxr-xr-x 1 root root   74 Abr 20 21:11 30000
    drwxr-xr-x 1 root root   74 Abr 20 21:11 30101
    drwxr-xr-x 1 root root  160 Abr 20 21:11 30101coex
    -rw-r--r-- 1 root root  54K Abr  4 18:30 AthrBT_0x01020001.dfu
    -rw-r--r-- 1 root root  40K Abr  4 18:30 AthrBT_0x01020200.dfu
    -rw-r--r-- 1 root root  48K Abr  4 18:30 AthrBT_0x01020201.dfu
    -rw-r--r-- 1 root root  36K Abr  4 18:30 AthrBT_0x11020000.dfu
    -rw-r--r-- 1 root root  46K Abr  4 18:30 AthrBT_0x11020100.dfu
    -rw-r--r-- 1 root root  40K Abr  4 18:30 AthrBT_0x31010000.dfu
    -rw-r--r-- 1 root root  37K Abr  4 18:30 AthrBT_0x31010100.dfu
    -rw-r--r-- 1 root root  31K Abr  4 18:30 AthrBT_0x41020000.dfu
    -rw-r--r-- 1 root root 1,2K Abr  4 18:30 ramps_0x01020001_26.dfu
    -rw-r--r-- 1 root root 1,3K Abr  4 18:30 ramps_0x01020200_26.dfu
    -rw-r--r-- 1 root root 1,2K Abr  4 18:30 ramps_0x01020200_40.dfu
    -rw-r--r-- 2 root root  264 Abr  4 18:30 ramps_0x01020201_26.dfu
    -rw-r--r-- 2 root root  264 Abr  4 18:30 ramps_0x01020201_40.dfu
    -rw-r--r-- 1 root root 1,8K Abr  4 18:30 ramps_0x11020000_40.dfu
    -rw-r--r-- 1 root root 1,8K Abr  4 18:30 ramps_0x11020100_40.dfu
    -rw-r--r-- 1 root root 1,9K Abr  4 18:30 ramps_0x31010000_40.dfu
    -rw-r--r-- 1 root root 1,9K Abr  4 18:30 ramps_0x31010100_40.dfu
    -rw-r--r-- 1 root root 1,8K Abr  4 18:30 ramps_0x41020000_40.dfu
    Fortunately, Ubuntu Forums user Ephialta links to a Windows driver update archive (.cab) containing the missing firmware files: http://ubuntuforums.org/showthread.p...9#post13207809
    Okay, here we go:

    Code:
    # wget http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2014/01/20623393_919a4673931aa789f0b1c3eeafb360b36097894a.cab
    # cabextract 20623393_919a4673931aa789f0b1c3eeafb360b36097894a.cab
    # ls -lah
    total 2,3M
    drwxr-xr-x 1 root root 1,8K Abr 22 10:08 .
    drwxr-xr-x 1 root root 9,9K Abr 21 10:02 ..
    drwxr-xr-x 1 root root   74 Abr 20 21:11 1020200
    drwxr-xr-x 1 root root   46 Abr 20 21:11 1020201
    drwxr-xr-x 1 root root   72 Abr 20 21:11 1020201coex
    -rw-r--r-- 1 root root 656K Jan 29  2014 20623393_919a4673931aa789f0b1c3eeafb360b36097894a.cab
    drwxr-xr-x 1 root root   74 Abr 20 21:11 30000
    drwxr-xr-x 1 root root   74 Abr 20 21:11 30101
    drwxr-xr-x 1 root root  160 Abr 20 21:11 30101coex
    -rw-r--r-- 1 root root 242K Jan 28  2014 AtherosBT.bin
    -rw-r--r-- 1 root root  54K Abr  4 18:30 AthrBT_0x01020001.dfu
    -rw-r--r-- 1 root root  48K Jan 28  2014 AthrBT_0x01020200.dfu
    -rw-r--r-- 1 root root  48K Jan 28  2014 AthrBT_0x01020201.dfu
    -rw-r--r-- 1 root root  46K Jan 28  2014 AthrBT_0x11020000_ac01.dfu
    -rw-r--r-- 1 root root  46K Jan 28  2014 AthrBT_0x11020000.dfu
    -rw-r--r-- 1 root root  46K Jan 28  2014 AthrBT_0x11020100.dfu
    -rw-r--r-- 1 root root  46K Jan 28  2014 AthrBT_0x31010000.dfu
    -rw-r--r-- 1 root root  37K Jan 28  2014 AthrBT_0x31010100.dfu
    -rw-r--r-- 1 root root  31K Abr  4 18:30 AthrBT_0x41020000.dfu
    -rw-r--r-- 1 root root 150K Jan 28  2014 btcoinst.dll
    -rw-r--r-- 1 root root 156K Jan 28  2014 BtContextMenu.dll
    -rw-r--r-- 1 root root  11K Jan 28  2014 BtContextMenu.dll.muien-US
    -rw-r--r-- 1 root root 493K Jan 28  2014 btfilter.sys
    -rw-r--r-- 1 root root  30K Jan 28  2014 qca_btusb.cat
    -rw-r--r-- 1 root root  17K Jan 28  2014 qca_btusb.inf
    -rw-r--r-- 1 root root 1,2K Abr  4 18:30 ramps_0x01020001_26.dfu
    -rw-r--r-- 1 root root 1,2K Jan 28  2014 ramps_0x01020200_26_0x01.dfu
    -rw-r--r-- 1 root root 1,2K Jan 28  2014 ramps_0x01020200_26.dfu
    -rw-r--r-- 1 root root 1,3K Jan 28  2014 ramps_0x01020200_40_0x01.dfu
    -rw-r--r-- 1 root root 1,2K Jan 28  2014 ramps_0x01020200_40_0x02.dfu
    -rw-r--r-- 1 root root 1,2K Jan 28  2014 ramps_0x01020200_40_0x03.dfu
    -rw-r--r-- 1 root root 1,2K Jan 28  2014 ramps_0x01020200_40_0x04.dfu
    -rw-r--r-- 1 root root 1,2K Jan 28  2014 ramps_0x01020200_40.dfu
    -rw-r--r-- 1 root root  264 Jan 28  2014 ramps_0x01020201_26_0x01.dfu
    -rw-r--r-- 2 root root  264 Jan 28  2014 ramps_0x01020201_26.dfu
    -rw-r--r-- 1 root root  296 Jan 28  2014 ramps_0x01020201_40_0x01.dfu
    -rw-r--r-- 1 root root  264 Jan 28  2014 ramps_0x01020201_40_0x02.dfu
    -rw-r--r-- 1 root root  264 Jan 28  2014 ramps_0x01020201_40_0x03.dfu
    -rw-r--r-- 1 root root  278 Jan 28  2014 ramps_0x01020201_40_0x04.dfu
    -rw-r--r-- 2 root root  264 Jan 28  2014 ramps_0x01020201_40.dfu
    -rw-r--r-- 1 root root 1,8K Jan 28  2014 ramps_0x11020000_40.dfu
    -rw-r--r-- 1 root root 1,8K Jan 28  2014 ramps_0x11020100_40.dfu
    -rw-r--r-- 1 root root 1,9K Jan 28  2014 ramps_0x31010000_40.dfu
    -rw-r--r-- 1 root root 1,9K Jan 28  2014 ramps_0x31010100_40.dfu
    -rw-r--r-- 1 root root 1,8K Abr  4 18:30 ramps_0x41020000_40.dfu
    After following all the procedure until the end, lsusb still does not show my Bluetooth adapter. I'm going to reboot my laptop to see if anything changes.

  8. #8

    Default Re: AW: Qualcomm Atheros Bluetooth 4.0 (04CA 3014) is not detected

    Quote Originally Posted by vinyanalista View Post
    After following all the procedure until the end, lsusb still does not show my Bluetooth adapter. I'm going to reboot my laptop to see if anything changes.
    Nothing changed...

    I see the Kernel:stable OBS repo released a new kernel, version 4.10.12. I'm not going to install it because that would require me to repeat everything (install the driver for TP-Link Archer T4U, install the kernel modules for VMware Workstation Player and follow the procedure described on Bluetooth can't find any devices).

    I'm going to stay with the kernel 4.10.11-vanilla for a while:

    Code:
    # uname -a
    Linux viny-notebook 4.10.11-1.gbd70196-vanilla #1 SMP PREEMPT Tue Apr 18 05:55:31 UTC 2017 (bd70196) x86_64 x86_64 x86_64 GNU/Linux
    What should I try next?

  9. #9
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,981

    Default AW: Qualcomm Atheros Bluetooth 4.0 (04CA 3014) is not detected

    Linux viny-notebook 4.10.11-1.gbd70196-vanilla
    Vanilla Kernel is without any Suse Patches, maybe the kernel-default do work??

  10. #10

    Default Re: AW: Qualcomm Atheros Bluetooth 4.0 (04CA 3014) is not detected

    Quote Originally Posted by Sauerland View Post
    Vanilla Kernel is without any Suse Patches, maybe the kernel-default do work??
    Linux kernel 4.4.57 from openSUSE Leap 42.2 was still installed, so I rebooted with it:

    Code:
    # uname -a
    Linux viny-notebook 4.4.57-18.3-default #1 SMP Thu Mar 30 06:39:47 UTC 2017 (39c8557) x86_64 x86_64 x86_64 GNU/Linux
    TP-Link and VMware worked at first, I had to do nothing about them, but Bluetooth didn't show up. I repeated the procedure described on Bluetooth can't find any devices, nothing new. Then I rebooted, nothing new again.

    I realized that there are modules for each kernel version (/lib/modules/`uname -r`/), but only one firmware for the whole system (/lib/firmware/). Right now, I'm using the package kernel-firmware from the Kernel:stable OBS repo. Should I downgrade it to the one provided by the openSUSE Leap 42.2 Update repo?

Page 1 of 3 123 LastLast

Posting Permissions

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