Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 28

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

  1. #11

    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??
    Later, I realized the Kernel:stable OBS repo also has a kernel-default package, so I installed it. I also made a clean up here, so now I have just 2 kernels installed (both kernel-default and their respective kernel-default-devel, kernel-devel, kernel-source, kernel-syms):


    1. 4.4.57 from the openSUSE Leap 42.2 Update repo; and
    2. 4.10.12 from the Kernel:stable repo.


    Now I booted with the second one:

    Code:
    # uname -a
    Linux viny-notebook 4.10.12-1.g3043bd9-default #1 SMP PREEMPT Fri Apr 21 11:50:25 UTC 2017 (3043bd9) x86_64 x86_64 x86_64 GNU/Linux
    I managed to install the driver for TP-Link Archer T4U and the kernel modules for VMware Workstation Player.

    Quote Originally Posted by vinyanalista View Post
    I repeated the procedure described on Bluetooth can't find any devices, nothing new. Then I rebooted, nothing new again.
    The same happened this time with the 4.10.12-default kernel.

  2. #12

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

    Now I'm just with the kernel 4.4.62 from the Leap 42.2 OSS repo:

    Code:
    # uname -a
    Linux viny-notebook 4.4.62-18.6-default #1 SMP Fri Apr 21 16:14:48 UTC 2017 (84f9824) x86_64 x86_64 x86_64 GNU/Linux
    I removed all the other kernels. Also, I downgraded everything (including kernel-firmware) to the Leap 42.2 OSS/Update repo.

    I noticed a package named bluez-firmware, but installing it didn't help recognizing my Bluetooth card.

    I remembered I have an old and cheap Bluetooth 2.0 USB 2.0 dongle by Noteship. Just as a test, I decided to plug it on my laptop, not sure that test can help. The Bluetooth dongle was recognized and I was able to transfer a file using it. I was not able to stream to a Bluetooth speaker, but I think it's a limitation of that dongle, as I was not able to stream audio on Windows as well.

    Running those commands again, I got:

    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)
    (nothing new)

    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 008: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
    Bus 001 Device 007: ID 1bcf:2c81 Sunplus Innovation Technology Inc. 
    Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    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
    This is the Bluetooth dongle:

    Code:
    Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    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.04
    S:  Manufacturer=Linux 4.4.62-18.6-default 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=03 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
    D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=0a12 ProdID=0001 Rev=01.00
    S:  Manufacturer=Bluetooth v2.0
    S:  Product=Bluetooth V2.0 Dongle
    C:  #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA
    I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
    I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
    
    
    T:  Bus=01 Lev=01 Prnt=01 Port=06 Cnt=03 Dev#=  7 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=04 Dev#=  8 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.04
    S:  Manufacturer=Linux 4.4.62-18.6-default 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.04
    S:  Manufacturer=Linux 4.4.62-18.6-default 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


    Here is the dongle:

    Code:
    T:  Bus=01 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
    D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=0a12 ProdID=0001 Rev=01.00
    S:  Manufacturer=Bluetooth v2.0
    S:  Product=Bluetooth V2.0 Dongle
    C:  #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA
    I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
    I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
    Code:
    # dmesg | egrep 'ath|wifi|hal'
    [    1.786018] device-mapper: multipath: version 1.11.0 loaded
    [   16.014438] ath: phy0: WB335 2-ANT card detected
    [   16.014441] ath: phy0: Set BT/WLAN RX diversity capability
    [   16.021100] ath: phy0: Enable LNA combining
    [   16.022201] ath: phy0: ASPM enabled: 0x42
    [   16.022203] ath: EEPROM regdomain: 0x6c
    [   16.022204] ath: EEPROM indicates we should expect a direct regpair map
    [   16.022205] ath: Country alpha2 being used: 00
    [   16.022205] ath: Regpair used: 0x6c
    [   17.379941] usbcore: registered new interface driver ath3k
    This line is new:

    Code:
    [    1.786018] device-mapper: multipath: version 1.11.0 loaded
    Code:
    # dmesg | egrep -i 'bluetooth|firm'
    [    0.222697] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    [    2.770532] usb 1-4: Product: Bluetooth V2.0 Dongle
    [    2.770533] usb 1-4: Manufacturer: Bluetooth v2.0
    [   16.695348] Bluetooth: Core ver 2.21
    [   16.695366] Bluetooth: HCI device and connection manager initialized
    [   16.695370] Bluetooth: HCI socket layer initialized
    [   16.695372] Bluetooth: L2CAP socket layer initialized
    [   16.695378] Bluetooth: SCO socket layer initialized
    [   26.944642] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [   26.944645] Bluetooth: BNEP filters: protocol multicast
    [   26.944649] Bluetooth: BNEP socket layer initialized
    [   75.699703] Bluetooth: RFCOMM TTY layer initialized
    [   75.699710] Bluetooth: RFCOMM socket layer initialized
    [   75.699715] Bluetooth: RFCOMM ver 1.11
    These lines are new:

    Code:
    [    2.770532] usb 1-4: Product: Bluetooth V2.0 Dongle
    [    2.770533] usb 1-4: Manufacturer: Bluetooth v2.0
    
    
    
    [   75.699703] Bluetooth: RFCOMM TTY layer initialized
    [   75.699710] Bluetooth: RFCOMM socket layer initialized
    [   75.699715] Bluetooth: RFCOMM ver 1.11
    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
    3: hci0: Bluetooth
    	Soft blocked: yes
    	Hard blocked: no
    Those last three lines are new.


    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
    (nothing new)

    Any ideas?

  3. #13

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

    Not sure that may help, but see this AIDA64 Extreme report:



    Compare to the outputs of lsusb and usb-devices. My Bluetooth adapter should be here:

    Code:
    # lsusb
    Bus 001 Device 002: ID 8087:8001 Intel Corp. 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 002: ID 0424:5537 Standard Microsystems Corp. 
    Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 002 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
    Bus 002 Device 005: ID 1bcf:2c81 Sunplus Innovation Technology Inc. 
    Bus 002 Device 006: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
    Bus 002 Device 004: ID 2357:010d 
    Bus 002 Device ___: ID 04ca:3014 Lite-On Technology Corp. Qualcoom Atheros Bluetooth
    Bus 002 Device 002: ID 0424:2137 Standard Microsystems Corp. 
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    (the same way it appears on an Acer Aspire E11 laptop)

    and here:

    Code:
    # usb-devices
    
    
    T:  Bus=01 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.04
    S:  Manufacturer=Linux 4.4.62-18.6-default 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=01 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
    
    
    T:  Bus=02 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.04
    S:  Manufacturer=Linux 4.4.62-18.6-default 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=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=02 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=02 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=02 Lev=01 Prnt=01 Port=04 Cnt=03 Dev#= 5 Spd=12 MxCh= 0
    D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
    P: Vendor=04ca ProdID=3014 Rev=00.02
    C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
    I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    
    
    T:  Bus=02 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=02 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=03 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.04
    S:  Manufacturer=Linux 4.4.62-18.6-default 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=03 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
    (as here)

    Now I noticed: what happened to Bus 002 Device 003 on lsusb? It seems it was "skipped". Maybe that's the Bluetooth adapter we are looking for?

  4. #14

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

    Also, I downloaded the Windows driver for the Bluetooth adapter from the laptop manufacturer's website: https://www.acer.com/drivers

    I noticed it has the files AthrBT_0x31010100.dfu and ramps_0x31010100_40.dfu and the first differ in size from the one at /lib/firmware/ar3k/. So I replaced it and rebooted my laptop. Nothing happened.

    Do you have any other idea that may help? I'm thinking about reporting a bug for the Linux kernel. By what I read on the Internet, that Bluetooth adapter should be at least recognized.

  5. #15
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,897

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

    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
    3: hci0: Bluetooth
    	Soft blocked: yes
    	Hard blocked: no
    You have seen this?
    softblocked: yes

    Code:
    rfkill unblock all

  6. #16

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

    Quote Originally Posted by Sauerland View Post
    You have seen this?
    softblocked: yes

    Code:
    rfkill unblock all
    Yes, but in my case, my Bluetooth adapter is not even shown:

    Code:
    # rfkill unblock all
    viny-notebook:/home/viny # 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
    Now, I realized this:

    Code:
    # dmesg | grep 04ca
    [    6.135872] usb 1-5: New USB device found, idVendor=04ca, idProduct=3014
    The system somehow recognizes my Bluetooth adapter. Why it is not set up?

  7. #17

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

    Googling around, I found this: bluetooth controller not showing up in lsusb but showing up in dmesg

    Then, I tried:

    Code:
    # dmesg | grep -i usb
    [    5.350180] ACPI: bus type USB registered
    [    5.350209] usbcore: registered new interface driver usbfs
    [    5.350222] usbcore: registered new interface driver hub
    [    5.350247] usbcore: registered new device driver usb
    [    5.354655] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
    [    5.355119] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [    5.357118] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    [    5.357120] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    5.357121] usb usb1: Product: xHCI Host Controller
    [    5.357122] usb usb1: Manufacturer: Linux 4.4.62-18.6-default xhci-hcd
    [    5.357122] usb usb1: SerialNumber: 0000:00:14.0
    [    5.357277] hub 1-0:1.0: USB hub found
    [    5.359183] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
    [    5.359233] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
    [    5.359234] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    5.359235] usb usb2: Product: xHCI Host Controller
    [    5.359236] usb usb2: Manufacturer: Linux 4.4.62-18.6-default xhci-hcd
    [    5.359237] usb usb2: SerialNumber: 0000:00:14.0
    [    5.359372] hub 2-0:1.0: USB hub found
    [    5.359962] usb: port power management may be unreliable
    [    5.360182] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 3
    [    5.374624] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
    [    5.374676] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
    [    5.374678] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    5.374679] usb usb3: Product: EHCI Host Controller
    [    5.374680] usb usb3: Manufacturer: Linux 4.4.62-18.6-default ehci_hcd
    [    5.374680] usb usb3: SerialNumber: 0000:00:1d.0
    [    5.374860] hub 3-0:1.0: USB hub found
    [    5.574661] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
    [    5.591054] usb 2-2: New USB device found, idVendor=0424, idProduct=5537
    [    5.591056] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=0
    [    5.591056] usb 2-2: Product: USB5537B
    [    5.591057] usb 2-2: Manufacturer: SMSC
    [    5.591609] hub 2-2:1.0: USB hub found
    [    5.686633] usb 3-1: new high-speed USB device number 2 using ehci-pci
    [    5.706629] usb 1-2: new high-speed USB device number 2 using xhci_hcd
    [    5.819053] usb 3-1: New USB device found, idVendor=8087, idProduct=8001
    [    5.819056] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [    5.819337] hub 3-1:1.0: USB hub found
    [    5.838988] usb 1-2: New USB device found, idVendor=0424, idProduct=2137
    [    5.838990] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    5.838992] usb 1-2: Product: USB2137B
    [    5.838993] usb 1-2: Manufacturer: SMSC
    [    5.839317] hub 1-2:1.0: USB hub found
    [    6.006708] usb 1-5: new full-speed USB device number 3 using xhci_hcd
    [    6.135872] usb 1-5: New USB device found, idVendor=04ca, idProduct=3014
    [    6.135875] usb 1-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [    6.206710] usb 1-2.1: new high-speed USB device number 4 using xhci_hcd
    [    6.295317] usb 1-2.1: New USB device found, idVendor=2357, idProduct=010d
    [    6.295320] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [    6.295321] usb 1-2.1: Product: 802.11n NIC
    [    6.295322] usb 1-2.1: Manufacturer: Realtek
    [    6.295323] usb 1-2.1: SerialNumber: 123456
    [    6.406713] usb 1-7: new high-speed USB device number 5 using xhci_hcd
    [    6.543952] usb 1-7: New USB device found, idVendor=1bcf, idProduct=2c81
    [    6.543956] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    6.543957] usb 1-7: Product: HD WebCam
    [    6.543957] usb 1-7: Manufacturer: NC2141103M50708908LM05
    [    6.610716] usb 1-2.2: new full-speed USB device number 6 using xhci_hcd
    [    6.704291] usb 1-2.2: New USB device found, idVendor=045e, idProduct=0745
    [    6.704295] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    6.704296] usb 1-2.2: Product: Microsoft® 2.4GHz Transceiver v8.0
    [    6.704297] usb 1-2.2: Manufacturer: Microsoft
    [    6.720756] usbcore: registered new interface driver usbhid
    [    6.720758] usbhid: USB HID core driver
    [    6.725488] input: Microsoft Microsoft® 2.4GHz Transceiver v8.0 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.0/0003:045E:0745.0001/input/input6
    [    6.778833] hid-generic 0003:045E:0745.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® 2.4GHz Transceiver v8.0] on usb-0000:00:14.0-2.2/input0
    [    6.779204] input: Microsoft Microsoft® 2.4GHz Transceiver v8.0 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.1/0003:045E:0745.0002/input/input7
    [    6.810665] usb 1-8: new high-speed USB device number 7 using xhci_hcd
    [    6.834775] hid-generic 0003:045E:0745.0002: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® 2.4GHz Transceiver v8.0] on usb-0000:00:14.0-2.2/input1
    [    6.844958] input: Microsoft Microsoft® 2.4GHz Transceiver v8.0 as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.2/0003:045E:0745.0003/input/input8
    [    6.898994] hid-generic 0003:045E:0745.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Microsoft Microsoft® 2.4GHz Transceiver v8.0] on usb-0000:00:14.0-2.2/input2
    [    6.939239] usb 1-8: New USB device found, idVendor=0bda, idProduct=0129
    [    6.939242] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [    6.939245] usb 1-8: Product: USB2.0-CRW
    [    6.939247] usb 1-8: Manufacturer: Generic
    [    6.939248] usb 1-8: SerialNumber: 20100201396000000
    [    6.945781] usbcore: registered new interface driver rtsx_usb
    [   18.318545] usb 1-5: USB disconnect, device number 3
    [   22.649268] input: HD WebCam as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/input/input19
    [   22.649339] usbcore: registered new interface driver uvcvideo
    [   22.649339] USB Video Class driver (1.1.1)
    [   22.797181] usbcore: registered new interface driver btusb
    [   23.195793] usbcore: registered new interface driver ath3k
    [   23.506222] usbcore: registered new interface driver rtl8812au
    See those lines?

    Code:
    # dmesg | grep 'usb 1-5'
    [    6.006708] usb 1-5: new full-speed USB device number 3 using xhci_hcd
    [    6.135872] usb 1-5: New USB device found, idVendor=04ca, idProduct=3014
    [    6.135875] usb 1-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [   18.318545] usb 1-5: USB disconnect, device number 3
    What does dmesg mean by found and then disconnect???

  8. #18

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

    Quote Originally Posted by vinyanalista View Post
    What does dmesg mean by found and then disconnect???
    I thought: maybe the kernel finds the device, does not know how to handle it and then disconnect it. So, I decided to try to load the btusb and ath3k kernel modules earlier, right at boot time, using initramfs. I followed the instructions here:

    Booting a Linux System | Reference | openSUSE Leap 42.2

    # echo 'force_drivers+="ath3k btusb"' > /etc/dracut.conf.d/01-bluetooth.conf
    # dracut -f
    # reboot

    Indeed, something has changed, new messages appeared in dmesg:

    Code:
    # dmesg | egrep 'ath|wifi|hal'
    [    5.309618] device-mapper: multipath: version 1.11.0 loaded
    [    6.311336] ath3k: probe of 1-5:1.0 failed with error -2
    [    6.311352] usbcore: registered new interface driver ath3k
    [   19.969812] ath: phy0: WB335 2-ANT card detected
    [   19.969814] ath: phy0: Set BT/WLAN RX diversity capability
    [   19.976484] ath: phy0: Enable LNA combining
    [   19.977581] ath: phy0: ASPM enabled: 0x42
    [   19.977582] ath: EEPROM regdomain: 0x6c
    [   19.977582] ath: EEPROM indicates we should expect a direct regpair map
    [   19.977583] ath: Country alpha2 being used: 00
    [   19.977584] ath: Regpair used: 0x6c
    Code:
    # dmesg | egrep -i 'bluetooth|firm'
    [    0.206528] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    [    6.309932] Bluetooth: Core ver 2.21
    [    6.309947] Bluetooth: HCI device and connection manager initialized
    [    6.309950] Bluetooth: HCI socket layer initialized
    [    6.309952] Bluetooth: L2CAP socket layer initialized
    [    6.309959] Bluetooth: SCO socket layer initialized
    [    6.311331] usb 1-5: Direct firmware load for ar3k/AthrBT_0x31010100.dfu failed with error -2
    [    6.311332] Bluetooth: Patch file not found ar3k/AthrBT_0x31010100.dfu
    [    6.311333] Bluetooth: Loading patch file failed
    [   84.128995] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [   84.128997] Bluetooth: BNEP filters: protocol multicast
    [   84.129002] Bluetooth: BNEP socket layer initialized
    Code:
    # uname -a
    Linux viny-notebook 4.4.70-18.9-default #1 SMP Wed May 31 09:09:25 UTC 2017 (c1231a7) x86_64 x86_64 x86_64 GNU/Linux
    That is kernel 4.4.70 from the openSUSE Leap 42.2 Update repo, I'm going to try kernel 4.11.4 from the Kernel:stable OBS repo.

  9. #19

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

    Quote Originally Posted by Sauerland View Post
    You have seen this?
    softblocked: yes

    Code:
    rfkill unblock all
    Sorry, I misunderstood you! But I think that hci0 was an external USB dongle I had plugged in just as a test:

    Quote Originally Posted by vinyanalista View Post
    I remembered I have an old and cheap Bluetooth 2.0 USB 2.0 dongle by Noteship. Just as a test, I decided to plug it on my laptop, not sure that test can help. The Bluetooth dongle was recognized and I was able to transfer a file using it. I was not able to stream to a Bluetooth speaker, but I think it's a limitation of that dongle, as I was not able to stream audio on Windows as well.

    Running those commands again, I got:

    ...

    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
    3: hci0: Bluetooth
        Soft blocked: yes
        Hard blocked: no
    Those last three lines are new.
    I already removed that dongle. Now I'm just with my Bluetooth card, which I'm trying to get recognized by the kernel.

  10. #20

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

    Quote Originally Posted by vinyanalista View Post
    I'm going to try kernel 4.11.4 from the Kernel:stable OBS repo.
    Same messages appear:

    Code:
    # dmesg | egrep 'ath|Bluetooth|firm|hal|usb|wifi'
    [    2.755254] usbcore: registered new interface driver usbfs
    [    2.755296] usbcore: registered new interface driver hub
    [    2.755345] usbcore: registered new device driver usb
    [    2.775181] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    [    2.775229] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    2.775271] usb usb1: Product: EHCI Host Controller
    [    2.775302] usb usb1: Manufacturer: Linux 4.11.4-1.gcba98ee-default ehci_hcd
    [    2.775345] usb usb1: SerialNumber: 0000:00:1d.0
    [    2.779171] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
    [    2.779208] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    2.779242] usb usb2: Product: xHCI Host Controller
    [    2.779265] usb usb2: Manufacturer: Linux 4.11.4-1.gcba98ee-default xhci-hcd
    [    2.779298] usb usb2: SerialNumber: 0000:00:14.0
    [    2.783577] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
    [    2.783621] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [    2.783668] usb usb3: Product: xHCI Host Controller
    [    2.783699] usb usb3: Manufacturer: Linux 4.11.4-1.gcba98ee-default xhci-hcd
    [    2.783744] usb usb3: SerialNumber: 0000:00:14.0
    [    2.784927] usb: port power management may be unreliable
    [    3.101456] usb 1-1: new high-speed USB device number 2 using ehci-pci
    [    3.109503] usb 3-2: new SuperSpeed USB device number 2 using xhci_hcd
    [    3.129831] usb 3-2: New USB device found, idVendor=0424, idProduct=5537
    [    3.129832] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=0
    [    3.129833] usb 3-2: Product: USB5537B
    [    3.129834] usb 3-2: Manufacturer: SMSC
    [    3.249457] usb 2-2: new high-speed USB device number 2 using xhci_hcd
    [    3.249753] usb 1-1: New USB device found, idVendor=8087, idProduct=8001
    [    3.249754] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [    3.389797] usb 2-2: New USB device found, idVendor=0424, idProduct=2137
    [    3.389798] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    3.389799] usb 2-2: Product: USB2137B
    [    3.389800] usb 2-2: Manufacturer: SMSC
    [    3.509467] usb 2-5: new full-speed USB device number 3 using xhci_hcd
    [    3.650736] usb 2-5: New USB device found, idVendor=04ca, idProduct=3014
    [    3.650739] usb 2-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [    3.659096] Bluetooth: Core ver 2.22
    [    3.659128] Bluetooth: HCI device and connection manager initialized
    [    3.659132] Bluetooth: HCI socket layer initialized
    [    3.659135] Bluetooth: L2CAP socket layer initialized
    [    3.659142] Bluetooth: SCO socket layer initialized
    [    3.661355] usbcore: registered new interface driver btusb
    [    3.662287] usb 2-5: Direct firmware load for ar3k/AthrBT_0x31010100.dfu failed with error -2
    [    3.662290] Bluetooth: Patch file not found ar3k/AthrBT_0x31010100.dfu
    [    3.662291] Bluetooth: Loading patch file failed
    [    3.662298] ath3k: probe of 2-5:1.0 failed with error -2
    [    3.662333] usbcore: registered new interface driver ath3k
    [    3.729501] usb 2-2.1: new high-speed USB device number 4 using xhci_hcd
    [    3.829913] usb 2-2.1: New USB device found, idVendor=2357, idProduct=010d
    [    3.829914] usb 2-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [    3.829915] usb 2-2.1: Product: 802.11n NIC
    [    3.829916] usb 2-2.1: Manufacturer: Realtek
    [    3.829917] usb 2-2.1: SerialNumber: 123456
    [    3.949528] usb 2-7: new high-speed USB device number 5 using xhci_hcd
    [    4.098723] usb 2-7: New USB device found, idVendor=1bcf, idProduct=2c81
    [    4.099460] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    4.100171] usb 2-7: Product: HD WebCam
    [    4.100879] usb 2-7: Manufacturer: NC2141103M50708908LM05
    [    4.169480] usb 2-2.2: new full-speed USB device number 6 using xhci_hcd
    [    4.274514] usb 2-2.2: New USB device found, idVendor=045e, idProduct=0745
    [    4.275253] usb 2-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    4.276007] usb 2-2.2: Product: Microsoft® 2.4GHz Transceiver v8.0
    [    4.276753] usb 2-2.2: Manufacturer: Microsoft
    [    4.292377] usbcore: registered new interface driver usbhid
    [    4.293709] usbhid: USB HID core driver
    [    4.295730] input: Microsoft Microsoft® 2.4GHz Transceiver v8.0 as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.2/2-2.2:1.0/0003:045E:0745.0001/input/input6
    [    4.353643] hid-generic 0003:045E:0745.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® 2.4GHz Transceiver v8.0] on usb-0000:00:14.0-2.2/input0
    [    4.355494] input: Microsoft Microsoft® 2.4GHz Transceiver v8.0 as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.2/2-2.2:1.1/0003:045E:0745.0002/input/input7
    [    4.389483] usb 2-8: new high-speed USB device number 7 using xhci_hcd
    [    4.413586] hid-generic 0003:045E:0745.0002: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® 2.4GHz Transceiver v8.0] on usb-0000:00:14.0-2.2/input1
    [    4.425359] input: Microsoft Microsoft® 2.4GHz Transceiver v8.0 as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.2/2-2.2:1.2/0003:045E:0745.0003/input/input8
    [    4.485606] hid-generic 0003:045E:0745.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Microsoft Microsoft® 2.4GHz Transceiver v8.0] on usb-0000:00:14.0-2.2/input2
    [    4.529861] usb 2-8: New USB device found, idVendor=0bda, idProduct=0129
    [    4.530932] usb 2-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [    4.532004] usb 2-8: Product: USB2.0-CRW
    [    4.533069] usb 2-8: Manufacturer: Generic
    [    4.534134] usb 2-8: SerialNumber: 20100201396000000
    [    4.537925] usbcore: registered new interface driver rtsx_usb
    [   16.900234] usb 2-5: USB disconnect, device number 3
    [   17.808497] ath: phy0: WB335 2-ANT card detected
    [   17.809910] ath: phy0: Set BT/WLAN RX diversity capability
    [   17.818436] ath: phy0: Enable LNA combining
    [   17.821011] ath: phy0: ASPM enabled: 0x42
    [   17.821673] ath: EEPROM regdomain: 0x6c
    [   17.821673] ath: EEPROM indicates we should expect a direct regpair map
    [   17.821674] ath: Country alpha2 being used: 00
    [   17.821675] ath: Regpair used: 0x6c
    [   19.512034] input: HD WebCam as /devices/pci0000:00/0000:00:14.0/usb2/2-7/2-7:1.0/input/input25
    [   19.513387] usbcore: registered new interface driver uvcvideo
    [   95.875432] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [   95.875436] Bluetooth: BNEP filters: protocol multicast
    [   95.875441] Bluetooth: BNEP socket layer initialized
    [  330.333981] usbcore: registered new interface driver rtl8812au
    Code:
    # uname -a
    Linux viny-notebook 4.11.4-1.gcba98ee-default #1 SMP PREEMPT Wed Jun 7 15:14:28 UTC 2017 (cba98ee) x86_64 x86_64 x86_64 GNU/Linux

Page 2 of 3 FirstFirst 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
  •