Build-in recognized bluetooth doesn't find devices

[linuxfluesterer]

Hallo guys.
For a new notebook, an Acer V3-571G with Core i5, 8GB Ram, NVidia GT-630M, I have a problem with build-in bluetooth 4.0.
I run SL X and KDE 4.9.4 (64bit) with Kernel 3.7.

It seems, bt hardware is recognized (see dmesg-messages).

Code: Select all

Sabayon-KDE-SSD .. # dmesg|grep lue
[    5.327470] Bluetooth: Core ver 2.16
[    5.327485] Bluetooth: HCI device and connection manager initialized
[    5.327491] Bluetooth: HCI socket layer initialized
[    5.327494] Bluetooth: L2CAP socket layer initialized
[    5.327499] Bluetooth: SCO socket layer initialized
[   12.247272] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   12.247275] Bluetooth: BNEP filters: protocol multicast
[   12.247281] Bluetooth: BNEP socket layer initialized
[   12.250214] Bluetooth: RFCOMM TTY layer initialized
[   12.250224] Bluetooth: RFCOMM socket layer initialized
[   12.250225] Bluetooth: RFCOMM ver 1.11


An lspci gives the following, where I can only assume, what is my bluetooth.

Code: Select all

Sabayon-KDE-SSD .. # lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 630M] (rev a1)
02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785 Gigabit Ethernet PCIe (rev 10)
02:00.1 SD Host controller: Broadcom Corporation NetXtreme BCM57765 Memory Card Reader (rev 10)
02:00.2 System peripheral: Broadcom Corporation Device 16be (rev 10)
02:00.3 System peripheral: Broadcom Corporation Device 16bf (rev 10)
03:00.0 Network controller: Atheros Communications Inc. AR9462 Wireless Network Adapter (rev 01)


An lsusb gives the following, where I googled, that the '0489:e04e Foxconn / Hon Hai' is my bluetooth, so also recognized.

Code: Select all

Sabayon-KDE-SSD .. # lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 003: ID 046d:c045 Logitech, Inc. Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0489:e04e Foxconn / Hon Hai
Bus 001 Device 004: ID 04f2:b374 Chicony Electronics Co., Ltd


An lsmod shows, that btusb and bluetooth are loaded modules.

Code: Select all

Sabayon-KDE-SSD .. # lsmod|grep bt
btusb                  11913  0
bluetooth             213518  22 bnep,btusb,rfcomm


Finally, I have rfkill messages:

Code: Select all

Sabayon-KDE-SSD .. # rfkill list bluetooth
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
3: acer-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no


Code: Select all

/etc/init.d/bluetooth

is running. I have a bt-symbol in Taskline.

When I configure it, I get (Sorry for German language, but I hope, that doesn't matter):

You can see a device ip (68.94...), a name 'Sabayon-KDE-SSD-0 and 'Always visible'.

And now, when I search for new bt devices, then no other bt device can be found (after minutes).
Also, this bt can't be found by my phones.
When I used my bt-usb-stick (in another laptop), there are visible bt devices within seconds.


My problem, my question is: why (it seems to be a bt adapter present)?
So, the next question is, what can I do to make it work (find and be found by other bt-devices)? Ok, in the end, I want to connect with other bt devices like phones like I could before with old notebook and bt-usb-stick.

I know, this is a long text here, I say sorry in advance. But I hope, someone has experience in this problem to solve.
Thank you in advance.

--Linuxfluesterer (I love KDE ...)

[linuxfluesterer]

Hallo again.
In between, I found out, that Wlan and Bluetooth is activated with one Key (Fn+F3), depending on one or two pushes.
Bluetooth device disappears and appears again in 'Bluetooth settings' window.
I have been searching for more information, my status is still the same: No bt devices are shown while searching.
So I installed 'hwinfo' with Rigo and startet:

Code: Select all

Sabayon-KDE-SSD .. # /usr/sbin/hwinfo --bluetooth

Result is:

Code: Select all

01: USB 00.0: 11500 Bluetooth Device                           
  [Created at usb.122]
  Unique ID: lfzD.+XjOheJX3H7
  Parent ID: ADDn.4Nx_qoDfSd7
  SysFS ID: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0
  SysFS BusID: 1-1.1:1.0
  Hardware Class: bluetooth
  Model: "Foxconn / Hon Hai Bluetooth Device"
  Hotplug: USB
  Vendor: usb 0x0489 "Foxconn / Hon Hai"
  Device: usb 0xe04e
  Revision: "0.01"
  Driver: "btusb"
  Driver Modules: "btusb"
  Speed: 12 Mbps
  Module Alias: "usb:v0489pE04Ed0001dcE0dsc01dp01icE0isc01ip01in00"
  Driver Info #0:
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #11 (Hub)


I don't have any idea, what is wrong with my bluetooth. Any suggestions?

-Linuxfluesterer (I love KDE ...)

[Fitzcarraldo]

An lspci gives the following, where I can only assume, what is my bluetooth.

Your assumption is incorrect: looking at your lsusb output, your Bluetooth device is a USB device, albeit internal. (I'm in the same situation, BTW.)

I don't have your hardware, so cannot be more help, but one idea that springs to mind is that there may be another kernel module that need to be loaded specifically for your model of Bluetooth adapter. Have you checked the kernel configuration for the version of kernel you are using? For example, the configuration file for kernel sabayon-3.7-r3 lists several Bluetooth modules (search for "Bluetooth" to find the beginning of the section in the config file). You could try loading them and unloading them manually to see if one of them is the driver for your specific model of Bluetooth adapter.

[linuxfluesterer]

Hallo Fitzcarraldo.
Glad to hear from you.
I have unloaded btusb module and loaded ath3k (suggested in another post in Google). But ath3k module didin't activate my bluetooth symbol.
Finally, only btusb module activated the bluetooth symbol in status line.
So... I have been going on searching and found:
http://www.spinics.net/lists/linux-bluetooth/msg32871.html

I think that could help me. But honestly, I don't have any idea (or I forgot) how to deal with it.
Could you tell me, pls, can I use the patch, and what must I do to make it?
Do I need to compile a module or all the kernel sources?
I found this also:
https://lkml.org/lkml/2013/1/10/41
Does it mean (maybe) in Kernel 3.8, my bt hardware (foxconn 0489:e04e) will be supported?
If so, I could wait for Kernel 3.8 then, though I'm interested in patching a kernel (module).

Sorry for bothering you, really.

Thanks a lot,

-Linuxfluesterer (I love KDE ...)