Bug 42932

Summary: bluetooth device is found but cannot use
Product: Drivers Reporter: Paolo (paolos)
Component: BluetoothAssignee: drivers_bluetooth (drivers_bluetooth)
Status: RESOLVED PATCH_ALREADY_AVAILABLE    
Severity: high CC: fuzzy_sys, gustavo, info, justincase, lupylucke, szebenyib, zanetu
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: every kernel (2.X and also 3.X) Subsystem:
Regression: No Bisected commit-id:
Attachments: Info about my Sony laptop
modprobe btusb on 3.7-rc8
hciconfig hci0 up on 3.7-rc8
fix for ID 1310:0001 Roper Class 1 Bluetooth Dongle
fix applied modprobe btusb on 3.7-rc8

Description Paolo 2012-03-14 20:00:35 UTC
I've a Sony Vaio VPCEH-1S0E with this bluetooth adapter (lsusb):
Bus 001 Device 004: ID 0489:e027 Foxconn / Hon Hai
For every bluetooth software i've used (gnome or kde) it stops working into "finding devices" step.
And also the command:
hcitool dev
show *no* devices.
I've this problem with: Ubuntu both arch, Archlinux both arch, Fedora both arch and OpenSuse both arch.
I've tested also various kernel from 2.6.29 to 3.3.0-rc7 and still have this problem :(
If you need some other thing just let me know :)
Comment 1 fuzzy_sys 2012-09-09 11:15:04 UTC
I have the same problem on a Sony Vaio VPCF22S8E

hciconfig shows me a device with a BD Address of 00:00:00:00:00:00

Everything works fine, when I start windows first and reboot to Linux afterwards.

Windows tells me another name for this device: Atheros AR3011
Comment 2 szebenyib 2012-11-03 13:49:05 UTC
I am also affected by this bug on a Sony VAIO VPCCA2S1E.

No matter if I use Arch or Ubuntu, the problem remains. I have also noticed, that it has worked for me once or twice, after windows. Due to unreliability I have not really checked it, just once when I have installed Ubuntu 12.10.

Please take a look into this if you can as it renders the usb on many Sony devices useless.
Comment 3 szebenyib 2012-11-03 13:52:06 UTC
Created attachment 85431 [details]
Info about my Sony laptop

Also contains the info about other computers which still have the issue.
Comment 4 Gustavo Padovan 2012-11-19 22:34:50 UTC
This is fixed on mainline now!
Comment 5 szebenyib 2012-11-26 21:27:22 UTC
I have installed the newest kernel (3.7.0-1-mainline) = -rc7 on my arch laptop from the AUR. Has this patch been included in the latest release? I have checked Linus' message about the release, but I have not seen your name in the commits.
hcitools still shows nothing, lsusb: Bus 001 Device 005: ID 0489:e027 Foxconn / Hon Hai.
Can you tell me please if I am doing it the wrong way or the patch is not available yet?
Comment 6 Simon 2012-12-01 22:12:44 UTC
Exact same symptoms here, but different hardware: my device is ID 04ca:3002 Lite-On Technology Corp.
'hciconfig' shows the device, but BD Address is listed as 00:00:00:00:00:00.
'hciconfig up' times out with error 110
The device works when rebooting from Windows 7.

I tried both 3.7-rc6 and a build from git (20121122) - The problem is _not_ fixed for me
Comment 7 mastervolkov 2012-12-09 16:09:35 UTC
Exact same symptoms here, but different hardware: my device is ID 1310:0001 Roper Class 1 Bluetooth Dongle

The device works in Windows 7

I tried both 3.7-rc6 and 3.7-rc7 and 3.7-rc8 - The problem is _not_
fixed for me

But when i remark, in 

net/bluetooth/hci_core.c:106


if (test_bit(HCI_INIT, &hdev->flags) && hdev->init_last_cmd != cmd)
return;

by 

//if (test_bit(HCI_INIT, &hdev->flags) && hdev->init_last_cmd != cmd)
//return;


All work good - I test it on:
2.6.39
3.2.12
Comment 8 mastervolkov 2012-12-10 09:14:01 UTC
Created attachment 88691 [details]
modprobe btusb on 3.7-rc8


for bluetooth
EXTRA_CFLAGS += -DDEBUG

Bus 005 Device 002: ID 1310:0001 Roper Class 1 Bluetooth Dongle

modprobe btusb
Comment 9 mastervolkov 2012-12-10 09:15:19 UTC
Created attachment 88701 [details]
hciconfig hci0 up on 3.7-rc8

for bluetooth
EXTRA_CFLAGS += -DDEBUG

Bus 005 Device 002: ID 1310:0001 Roper Class 1 Bluetooth Dongle

hciconfig hci0 up
Comment 10 mastervolkov 2012-12-10 10:03:30 UTC
Created attachment 88711 [details]
fix for ID 1310:0001 Roper Class 1 Bluetooth Dongle

After this patch my ID 1310:0001 Roper Class 1 Bluetooth Dongle initing and work properly.

no "timeout 110" more and i can use my bluetooth dongle.

If someone will be able to adapt these patch for proper use in mainline kernel - we can use our dongles in future without problem.
Comment 11 mastervolkov 2012-12-10 10:13:39 UTC
Created attachment 88721 [details]
fix applied modprobe btusb on 3.7-rc8

after previous patch https://bugzilla.kernel.org/attachment.cgi?id=88711

modprobe btusb on 3.7-rc8


for bluetooth
EXTRA_CFLAGS += -DDEBUG

Bus 005 Device 002: ID 1310:0001 Roper Class 1 Bluetooth Dongle

modprobe btusb


all initing ok without problem (bnep disabled/not builded in my case)
Comment 12 mastervolkov 2012-12-10 10:35:28 UTC
P.S. my bluetooth dongle (ID 1310:0001 Roper Class 1 Bluetooth Dongle) stopped work in kernel-2.6.39 (kernel-2.6.38 all work fine)
Comment 13 mastervolkov 2012-12-19 15:43:55 UTC
https://bugzilla.kernel.org/show_bug.cgi?id=51831
Comment 14 Yill Din 2013-02-22 13:03:18 UTC
Works for me with https://bugzilla.kernel.org/attachment.cgi?id=88711

[343115.685695] usb 1-1.2.3: New USB device found, idVendor=1310, idProduct=0001
[343115.685698] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[343115.685701] usb 1-1.2.3: Product: SiW
[343115.685703] usb 1-1.2.3: Manufacturer: SiW
[343115.685705] usb 1-1.2.3: SerialNumber: CB3A0A0D0B00
Comment 15 mastervolkov 2015-07-07 13:58:03 UTC
Complete solved and work from kernel 4.2-rc1 https://bugzilla.kernel.org/show_bug.cgi?id=60901

By adding HCI_QUIRK_BROKEN_LOCAL_COMMANDS for that dongles.