You are not logged in.
I have been having trouble getting the bluetooth with the AR9285 combo card to work. The btusb module loads, but then has a timed out error. I found a similar problem both on the Gentoo forum and the Ubuntu forum.
I have tried adding the ath3k module to rc.conf, but it did not change anything.
lspci:
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
rfkill list:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
dmesg:
[ 351.590002] Bluetooth: Core ver 2.16
[ 351.590044] NET: Registered protocol family 31
[ 351.590048] Bluetooth: HCI device and connection manager initialized
[ 351.590054] Bluetooth: HCI socket layer initialized
[ 351.590058] Bluetooth: L2CAP socket layer initialized
[ 351.590278] Bluetooth: SCO socket layer initialized
[ 351.598017] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 351.598729] usbcore: registered new interface driver btusb
[ 351.788539] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 352.601287] hci_cmd_timer: hci0 command tx timeout
[ 353.604337] hci_cmd_timer: hci0 command tx timeout
[ 354.607307] hci_cmd_timer: hci0 command tx timeout
[ 355.610316] hci_cmd_timer: hci0 command tx timeout
[ 356.613349] hci_cmd_timer: hci0 command tx timeout
[ 357.616341] hci_cmd_timer: hci0 command tx timeout
[ 358.619364] hci_cmd_timer: hci0 command tx timeout
[ 359.622376] hci_cmd_timer: hci0 command tx timeout
[ 360.625388] hci_cmd_timer: hci0 command tx timeout
[ 362.598164] hci_cmd_timer: hci0 command tx timeout
[ 363.601177] hci_cmd_timer: hci0 command tx timeout
[ 364.604138] hci_cmd_timer: hci0 command tx timeout
[ 365.607145] hci_cmd_timer: hci0 command tx timeout
[ 366.610228] hci_cmd_timer: hci0 command tx timeout
[ 367.613239] hci_cmd_timer: hci0 command tx timeout
[ 368.616259] hci_cmd_timer: hci0 command tx timeout
[ 369.619209] hci_cmd_timer: hci0 command tx timeout
[ 370.622286] hci_cmd_timer: hci0 command tx timeout
[ 371.625263] hci_cmd_timer: hci0 command tx timeout
/var/log/messages.log
Sep 14 06:21:46 localhost kernel: [ 351.590002] Bluetooth: Core ver 2.16
Sep 14 06:21:46 localhost kernel: [ 351.590044] NET: Registered protocol family 31
Sep 14 06:21:46 localhost kernel: [ 351.590048] Bluetooth: HCI device and connection manager initialized
Sep 14 06:21:46 localhost kernel: [ 351.590054] Bluetooth: HCI socket layer initialized
Sep 14 06:21:46 localhost kernel: [ 351.590058] Bluetooth: L2CAP socket layer initialized
Sep 14 06:21:46 localhost kernel: [ 351.590278] Bluetooth: SCO socket layer initialized
Sep 14 06:21:46 localhost kernel: [ 351.598017] Bluetooth: Generic Bluetooth USB driver ver 0.6
Sep 14 06:21:46 localhost kernel: [ 351.598729] usbcore: registered new interface driver btusb
Sep 14 06:21:47 localhost bluetoothd[2359]: Bluetooth daemon 4.96
Sep 14 06:21:47 localhost bluetoothd[2359]: Starting SDP server
Sep 14 06:21:47 localhost kernel: [ 351.788539] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 14 06:21:47 localhost bluetoothd[2359]: Listening for HCI events on hci0
Sep 14 06:22:11 localhost bluetoothd[2394]: Bluetooth daemon 4.96
hciconfig:
[isaac@laptop ~]$ hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:66 acl:0 sco:0 commands:20 errors:0
[isaac@laptop ~]$ sudo hciconfig hci0 up
Password:
Can't init device hci0: Connection timed out (110)
[isaac@laptop ~]$ hcitool dev
Devices:
lsmod:
Module Size Used by
bnep 9245 2
btusb 11577 1
bluetooth 139297 10 bnep,btusb
cryptd 8213 0
aes_x86_64 7476 3
aes_generic 26106 1 aes_x86_64
ipv6 290791 44
coretemp 5947 0
ext2 64314 1
snd_hda_codec_hdmi 22092 1
snd_hda_codec_conexant 46356 1
arc4 1410 2
i915 707339 2
ath9k 86536 0
mac80211 216021 1 ath9k
uvcvideo 64963 0
drm_kms_helper 25409 1 i915
snd_hda_intel 22122 0
snd_hda_codec 77927 3 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel
drm 183380 3 i915,drm_kms_helper
snd_hwdep 6325 1 snd_hda_codec
snd_pcm 73888 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
ath9k_common 1770 1 ath9k
ath9k_hw 275564 2 ath9k,ath9k_common
snd_timer 19416 1 snd_pcm
snd 57818 7 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
ath 14667 2 ath9k,ath9k_hw
cfg80211 160740 3 ath9k,mac80211,ath
rfkill 15402 3 bluetooth,cfg80211
videodev 78006 1 uvcvideo
soundcore 6146 1 snd
iTCO_wdt 12717 0
sg 25557 0
media 10437 2 uvcvideo,videodev
v4l2_compat_ioctl32 8292 1 videodev
mei 31313 0
snd_page_alloc 7121 2 snd_hda_intel,snd_pcm
i2c_algo_bit 5199 1 i915
i2c_i801 8187 0
pcspkr 1819 0
intel_agp 10904 1 i915
i2c_core 20133 6 i915,drm_kms_helper,drm,videodev,i2c_algo_bit,i2c_i801
intel_gtt 14423 3 i915,intel_agp
serio_raw 4294 0
psmouse 55192 0
evdev 9530 6
iTCO_vendor_support 1929 1 iTCO_wdt
wmi 8347 0
thermal 7863 0
video 11228 1 i915
battery 10905 0
ac 3265 0
button 4470 1 i915
atl1c 32528 0
cpufreq_ondemand 6132 8
acpi_cpufreq 5877 1
freq_table 2451 2 cpufreq_ondemand,acpi_cpufreq
processor 24256 1 acpi_cpufreq
mperf 1275 1 acpi_cpufreq
ext4 370398 2
mbcache 5817 2 ext2,ext4
jbd2 71074 1 ext4
crc16 1297 2 bluetooth,ext4
sr_mod 14951 0
sd_mod 28307 5
cdrom 36329 1 sr_mod
ahci 20865 4
libahci 18885 1 ahci
libata 173297 2 ahci,libahci
scsi_mod 131546 4 sg,sr_mod,sd_mod,libata
xhci_hcd 70396 0
ehci_hcd 39511 0
usbcore 142576 5 btusb,uvcvideo,xhci_hcd,ehci_hcd
Last edited by the sad clown (2013-01-24 03:13:45)
I laugh, yet the joke is on me
Offline
Wow... looking at this led me down a wild path... if I followed it correctly.
It appears that this long thread sort of explains how your chip works on Linux:
http://forum.soft32.com/linux/RFC-btusb … 22254.html
They're talking about having the chip provide a VID:PID when there's no firmware loaded, and then morph into a different VID:PID after the firmware is loaded. Bizarre.
OBTW: Marcel Holtmann is the Bluez developer when you read that thread.
So it looks like the ath3k module needs to be involved here... as it's the module that loads the firmware.
Here's it's code for Linux 3.0.4:
http://lxr.linux.no/#linux+v3.0.4/drive … th/ath3k.c
So that's saying that the following should show a hit in your /var/log/everything.log file when it probed your chip:
grep "intf.*id" /var/log/everything.log
Also check the logs for any errors.
So... what's the output of the lsusb with the ath3k module in play?... and out of play?
Last edited by pigiron (2011-09-15 07:36:20)
Offline
Here is the everything.log with btusb and bluetoothd started up:
Sep 15 07:57:15 localhost kernel: [ 213.701612] Bluetooth: Core ver 2.16
Sep 15 07:57:15 localhost kernel: [ 213.701663] NET: Registered protocol family 31
Sep 15 07:57:15 localhost kernel: [ 213.701670] Bluetooth: HCI device and connection manager initialized
Sep 15 07:57:15 localhost kernel: [ 213.701678] Bluetooth: HCI socket layer initialized
Sep 15 07:57:15 localhost kernel: [ 213.701684] Bluetooth: L2CAP socket layer initialized
Sep 15 07:57:15 localhost kernel: [ 213.701870] Bluetooth: SCO socket layer initialized
Sep 15 07:57:15 localhost kernel: [ 213.708510] Bluetooth: Generic Bluetooth USB driver ver 0.6
Sep 15 07:57:15 localhost kernel: [ 213.708997] usbcore: registered new interface driver btusb
Sep 15 07:57:16 localhost kernel: [ 214.710780] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:17 localhost kernel: [ 215.712970] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:18 localhost kernel: [ 216.715449] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:19 localhost kernel: [ 217.718054] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:20 localhost kernel: [ 218.721062] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:21 localhost kernel: [ 219.723525] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:22 localhost kernel: [ 220.725669] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:23 localhost kernel: [ 221.728563] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:24 localhost kernel: [ 222.730846] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:24 localhost bluetoothd[2092]: Bluetooth daemon 4.96
Sep 15 07:57:25 localhost bluetoothd[2092]: Starting SDP server
Sep 15 07:57:25 localhost kernel: [ 223.314208] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 15 07:57:25 localhost bluetoothd[2092]: Listening for HCI events on hci0
Sep 15 07:57:26 localhost kernel: [ 224.703041] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:27 localhost kernel: [ 225.705263] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:28 localhost kernel: [ 226.707732] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:29 localhost kernel: [ 227.710728] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:30 localhost kernel: [ 228.713307] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:31 localhost kernel: [ 229.715650] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:32 localhost kernel: [ 230.718321] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:33 localhost kernel: [ 231.720569] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:34 localhost kernel: [ 232.723144] hci_cmd_timer: hci0 command tx timeout
Sep 15 07:57:35 localhost bluetoothd[2096]: Can't init device hci0: Connection timed out (110)
Sep 15 07:57:35 localhost kernel: [ 233.725765] hci_cmd_timer: hci0 command tx timeout
And now after modprobe ath3k:
Sep 15 08:02:07 localhost kernel: [ 505.200081] Bluetooth: Atheros AR30xx firmware driver ver 1.0
Sep 15 08:02:07 localhost kernel: [ 505.200144] usbcore: registered new interface driver ath3k
Sep 15 08:02:17 localhost kernel: [ 515.164286] Bluetooth: RFCOMM TTY layer initialized
Sep 15 08:02:17 localhost kernel: [ 515.164299] Bluetooth: RFCOMM socket layer initialized
Sep 15 08:02:17 localhost kernel: [ 515.164304] Bluetooth: RFCOMM ver 1.11
Sep 15 08:02:17 localhost bluetoothd[2092]: Stopping hci0 event socket
Sep 15 08:02:17 localhost bluetoothd[2092]: Stopping SDP server
Sep 15 08:02:17 localhost bluetoothd[2092]: Exit
Sep 15 08:02:18 localhost bluetoothd[2267]: Bluetooth daemon 4.96
Sep 15 08:02:18 localhost bluetoothd[2267]: Starting SDP server
Sep 15 08:02:18 localhost bluetoothd[2267]: Listening for HCI events on hci0
Sep 15 08:02:19 localhost kernel: [ 517.243180] hci_cmd_timer: hci0 command tx timeout
Sep 15 08:02:20 localhost kernel: [ 518.246056] hci_cmd_timer: hci0 command tx timeout
Sep 15 08:02:21 localhost kernel: [ 519.248887] hci_cmd_timer: hci0 command tx timeout
Sep 15 08:02:22 localhost kernel: [ 520.251723] hci_cmd_timer: hci0 command tx timeout
Sep 15 08:02:23 localhost kernel: [ 521.254512] hci_cmd_timer: hci0 command tx timeout
Sep 15 08:02:24 localhost kernel: [ 522.257394] hci_cmd_timer: hci0 command tx timeout
Sep 15 08:02:25 localhost kernel: [ 523.260232] hci_cmd_timer: hci0 command tx timeout
Sep 15 08:02:26 localhost kernel: [ 524.263066] hci_cmd_timer: hci0 command tx timeout
Sep 15 08:02:27 localhost kernel: [ 525.265868] hci_cmd_timer: hci0 command tx timeout
Sep 15 08:02:28 localhost bluetoothd[2269]: Can't init device hci0: Connection timed out (110)
Sep 15 08:02:28 localhost kernel: [ 526.268607] hci_cmd_timer: hci0 command tx timeout
lsusb before btusb + bluetoothd are started:
Bus 001 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 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
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 001 Device 003: ID 05c8:030d Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 004: ID 04f2:aff1 Chicony Electronics Co., Ltd
lsusb after btusb + bluetoothd but before ath3k:
Bus 001 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 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
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 001 Device 003: ID 05c8:030d Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 004: ID 04f2:aff1 Chicony Electronics Co., Ltd
lsusb after ath3k:
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 05c8:030d Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 004: ID 04f2:aff1 Chicony Electronics Co., Ltd
grep "intf.*id" /var/log/everything.log showed nothing both before and after ath3k.
I'll have a look at the forums later on today when I have more time and get back to you on it. Thanks for the effort.
I laugh, yet the joke is on me
Offline
After reading the forums, I've got some more ideas. Let me get back with you tomorrow after I have time to try them out on my machine. And thanks again for taking the time to look those links up and go through them.
Last edited by the sad clown (2011-09-16 04:21:34)
I laugh, yet the joke is on me
Offline
Well, nothing panned out. After a thorough check, I do indeed have a bluetooth device. It is the AR3011 and is part of the AR9002WB-1NGCD. I have even opened up the laptop and confirmed a BT ADDR right on the chip.
I started to think that perhaps there was a switch I needed to physically activate to turn it on, but the only switch I can find is the keyboard one (Fn-F2) and my tests came back negative (before and after switch):
[isaac@laptop ~]$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
[isaac@laptop ~]$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
I have never seen the device on lsusb, and so I am forced to believe that it not being detected on some level. However, on a different level, surely it is being seen by the software, for why else would btusb keep trying to use it and time out? My previous laptop, which didn't have bluetooth, never triggered btusb.
I laugh, yet the joke is on me
Offline
Well, an important discovery has been made. My bluetooth device is listed under lsusb, I just didn't know it:
Bus 001 Device 004: ID 04f2:aff1 Chicony Electronics Co., Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x04f2 Chicony Electronics Co., Ltd
idProduct 0xaff1
bcdDevice 0.01
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 177
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
I discovered this by watching powertop. I noticed that it would briefly pop up as a device using power whenever I modprobed btusb. Of course, it would then drop off as it timed out, but at least I know it is being seen by my system and recognized. My question is now why my bluetooth device, which I was sure was an Atheros device, is registering as a Chicony device. Is Chicony supplying Atheros? And what driver driver should I use for this device?
Edit: Further searching seems to indicate that ath3k is what should be used. How can I tell my system to associate it with my device?
Edit2: I just found a very recent bug report on this: https://bugs.launchpad.net/ubuntu/+sour … bug/841673
Is there any solution to this besides simply waiting?
Last edited by the sad clown (2011-09-20 06:33:51)
I laugh, yet the joke is on me
Offline
Hello,
have you filed a bug report on this? This seems to be happening with me too (sony vaio VPCCA series...).
I am using gnome 3 I cannot switch it off there in the application, meanwhile if I click on the 'B' icon at the top it is marked as 'on'.
What can we do now?
I have tried a couple of things, like you, with no success:
before turning the wifi/bluetooth switch on
rfkill list
0: sony-wifi: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: sony-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: yes
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
after turning the switch on
rfkill list
0: sony-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: sony-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
starting bluetooth daemon
Oct 25 23:15:52 localhost bluetoothd[8904]: Bluetooth daemon 4.96
Oct 25 23:15:52 localhost bluetoothd[8904]: Starting SDP server
Oct 25 23:15:52 localhost bluetoothd[8904]: Listening for HCI events on hci0
Oct 25 23:15:52 localhost NetworkManager[1639]: <warn> bluez error getting default adapter: No such adapter
Oct 25 23:15:52 localhost kernel: [24410.911233] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 25 23:15:53 localhost kernel: [24411.912254] hci_cmd_timer: hci0 command tx timeout
Oct 25 23:15:54 localhost kernel: [24412.914104] hci_cmd_timer: hci0 command tx timeout
Oct 25 23:15:54 localhost kernel: [24412.984695] wlan0: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
Oct 25 23:15:55 localhost kernel: [24413.915933] hci_cmd_timer: hci0 command tx timeout
Oct 25 23:15:56 localhost kernel: [24414.917773] hci_cmd_timer: hci0 command tx timeout
Oct 25 23:15:57 localhost kernel: [24415.919626] hci_cmd_timer: hci0 command tx timeout
Oct 25 23:15:58 localhost kernel: [24416.921470] hci_cmd_timer: hci0 command tx timeout
Oct 25 23:15:59 localhost kernel: [24417.923308] hci_cmd_timer: hci0 command tx timeout
Oct 25 23:16:00 localhost kernel: [24418.925143] hci_cmd_timer: hci0 command tx timeout
Oct 25 23:16:01 localhost kernel: [24419.926982] hci_cmd_timer: hci0 command tx timeout
Oct 25 23:16:02 localhost bluetoothd[8909]: Can't init device hci0: Connection timed out (110)
Oct 25 23:16:02 localhost kernel: [24420.928872] hci_cmd_timer: hci0 command tx timeout
Oct 25 23:16:26 localhost kernel: [24444.495926] wlan0: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
Oct 25 23:16:57 localhost kernel: [24475.765327] wlan0: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:66 acl:0 sco:0 commands:20 errors:0
lsusb
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 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 03f0:3d17 Hewlett-Packard LaserJet P1005
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0489:e027 Foxconn / Hon Hai
Bus 001 Device 004: ID 05ca:18c0 Ricoh Co., Ltd
Bus 003 Device 003: ID 0458:0084 KYE Systems Corp. (Mouse Systems)
hcitool dev
Devices:
lsmod
Module Size Used by
bnep 9245 2
ipt_MASQUERADE 1706 1
xt_state 1295 1
ipt_REJECT 2313 2
xt_tcpudp 2535 4
iptable_filter 1488 1
nf_nat_h323 6015 0
nf_conntrack_h323 42274 1 nf_nat_h323
nf_nat_pptp 2282 0
nf_conntrack_pptp 4689 1 nf_nat_pptp
nf_conntrack_proto_gre 3989 1 nf_conntrack_pptp
nf_nat_proto_gre 1413 1 nf_nat_pptp
nf_nat_tftp 926 0
nf_conntrack_tftp 3505 1 nf_nat_tftp
nf_nat_sip 6579 0
nf_conntrack_sip 19579 1 nf_nat_sip
nf_nat_irc 1406 0
nf_conntrack_irc 3459 1 nf_nat_irc
nf_nat_ftp 1636 0
nf_conntrack_ftp 6260 1 nf_nat_ftp
iptable_nat 4056 1
nf_nat 15629 9 ipt_MASQUERADE,nf_nat_h323,nf_nat_pptp,nf_nat_proto_gre,nf_nat_tftp,nf_nat_sip,nf_nat_irc,nf_nat_ftp,iptable_nat
nf_conntrack_ipv4 11665 4 iptable_nat,nf_nat
nf_conntrack 59639 18 ipt_MASQUERADE,xt_state,nf_nat_h323,nf_conntrack_h323,nf_nat_pptp,nf_conntrack_pptp,nf_conntrack_proto_gre,nf_nat_tftp,nf_conntrack_tftp,nf_nat_sip,nf_conntrack_sip,nf_nat_irc,nf_conntrack_irc,nf_nat_ftp,nf_conntrack_ftp,iptable_nat,nf_nat,nf_conntrack_ipv4
nf_defrag_ipv4 1371 1 nf_conntrack_ipv4
ip_tables 16775 2 iptable_filter,iptable_nat
x_tables 17467 7 ipt_MASQUERADE,xt_state,ipt_REJECT,xt_tcpudp,iptable_filter,iptable_nat,ip_tables
nls_utf8 1320 0
isofs 33177 0
tun 16022 2
ipv6 290855 42
uvcvideo 64963 0
usblp 11083 0
videodev 78006 1 uvcvideo
media 10437 2 uvcvideo,videodev
btusb 11577 1
v4l2_compat_ioctl32 8292 1 videodev
bluetooth 139297 10 bnep,btusb
snd_hda_codec_hdmi 22092 1
joydev 9895 0
snd_hda_codec_realtek 294320 1
snd_hda_intel 22122 2
arc4 1410 2
snd_hda_codec 77927 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
ath9k 86568 0
sg 25557 0
iTCO_wdt 12717 0
mac80211 215908 1 ath9k
ath9k_common 1770 1 ath9k
ath9k_hw 275596 2 ath9k,ath9k_common
snd_hwdep 6325 1 snd_hda_codec
snd_pcm 73952 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer 19416 1 snd_pcm
snd 57818 11 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6146 1 snd
iTCO_vendor_support 1929 1 iTCO_wdt
sony_laptop 29444 0
atl1c 32528 0
mei 31313 0
ath 14667 2 ath9k,ath9k_hw
intel_agp 10904 0
snd_page_alloc 7121 2 snd_hda_intel,snd_pcm
cfg80211 160772 3 ath9k,mac80211,ath
evdev 9530 10
sdhci_pci 8530 0
sdhci 22194 1 sdhci_pci
mmc_core 73682 1 sdhci
i2c_i801 8187 0
psmouse 55192 0
intel_gtt 14423 1 intel_agp
serio_raw 4294 0
pcspkr 1819 0
thermal 7863 0
rfkill 15402 5 bluetooth,sony_laptop,cfg80211
video 11228 0
processor 24256 0
button 4470 0
battery 6317 0
ac 2376 0
fuse 67290 5
ext4 370462 4
mbcache 5817 1 ext4
jbd2 71074 1 ext4
crc16 1297 2 bluetooth,ext4
usbhid 35256 0
hid 81635 1 usbhid
sr_mod 14951 0
cdrom 36329 1 sr_mod
sd_mod 28307 7
ahci 20897 6
libahci 18885 1 ahci
libata 173297 2 ahci,libahci
xhci_hcd 70783 0
scsi_mod 131546 4 sg,sr_mod,sd_mod,libata
ehci_hcd 39543 0
usbcore 142576 7 uvcvideo,usblp,btusb,usbhid,xhci_hcd,ehci_hcd
radeon 993027 3
ttm 54360 1 radeon
drm_kms_helper 25409 1 radeon
drm 183380 5 radeon,ttm,drm_kms_helper
i2c_algo_bit 5199 1 radeon
i2c_core 20133 6 videodev,i2c_i801,radeon,drm_kms_helper,drm,i2c_algo_bit
Last edited by szebenyib (2011-10-25 21:38:44)
Offline
I didn't file a bug report because one had already been filed with the same kernel (at the time) and same hardware on the ubuntu site: https://bugs.launchpad.net/ubuntu/+sour … bug/841673
I am waiting to see if kernel 3.1 fixes the issue since I have read that there have been some changes made to the bluetooth module that should come with the new kernel.
Your issue might be different than mine, since you aren't using the same hardware, so it might be a good idea for you to file a bug.
Last edited by the sad clown (2011-10-25 21:50:47)
I laugh, yet the joke is on me
Offline
I have fixed this problem, but it requires building my own kernel via abs, running makepkg -o, then patching ath3k.c and btusb.c, adding support for my VID/PID in the former and blacklisting it in the latter, then compiling with makepkg -e and installing the compiled kernel.
You can read more about it here: https://bbs.archlinux.org/viewtopic.php?pid=1221279
If anyone is interested, here is the patch:
diff -uprN a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
--- a/drivers/bluetooth/ath3k.c 2013-01-23 20:45:24.946984407 -0600
+++ b/drivers/bluetooth/ath3k.c 2013-01-23 20:45:51.443693307 -0600
@@ -68,6 +68,7 @@ static struct usb_device_id ath3k_table[
{ USB_DEVICE(0x0930, 0x0215) },
{ USB_DEVICE(0x0489, 0xE03D) },
{ USB_DEVICE(0x0489, 0xE027) },
+ { USB_DEVICE(0x04f2, 0xaff1) },
/* Atheros AR9285 Malbec with sflash firmware */
{ USB_DEVICE(0x03F0, 0x311D) },
diff -uprN a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
--- a/drivers/bluetooth/btusb.c 2013-01-23 20:45:24.946984407 -0600
+++ b/drivers/bluetooth/btusb.c 2013-01-23 20:45:51.443693307 -0600
@@ -125,6 +125,7 @@ static struct usb_device_id blacklist_ta
{ USB_DEVICE(0x0930, 0x0215), .driver_info = BTUSB_IGNORE },
{ USB_DEVICE(0x0489, 0xe03d), .driver_info = BTUSB_IGNORE },
{ USB_DEVICE(0x0489, 0xe027), .driver_info = BTUSB_IGNORE },
+ { USB_DEVICE(0x04f2, 0xaff1), .driver_info = BTUSB_IGNORE },
/* Atheros AR9285 Malbec with sflash firmware */
{ USB_DEVICE(0x03f0, 0x311d), .driver_info = BTUSB_IGNORE },
Last edited by the sad clown (2013-01-24 04:05:50)
I laugh, yet the joke is on me
Offline