| View previous topic :: View next topic |
| Author |
Message |
310354
n00b
Joined: 01 Aug 2013
Posts: 59
|
 Posted: Wed Dec 04, 2013 9:40 pm Post subject: Bluetooth card drivers (ath3k / Alaska 2006 / AR3012) (?) |
 |
|
Hi,
I am trying to setup my bluetooth card (laptop) following https://wiki.gentoo.org/wiki/Bluetooth. Checking dmesg, I found that there was a 'USB Bluetooth host controller' on 'usb 4-5':
| Code: | [ 3.737104] usb 4-5: new full-speed USB device number 2 using ohci_hcd
[ 3.883341] usb 4-5: default language 0x0409
[ 3.889344] usb 4-5: udev 2, busnum 4, minor = 385
[ 3.889350] usb 4-5: New USB device found, idVendor=13d3, idProduct=3362
[ 3.890282] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.891168] usb 4-5: Product: Bluetooth USB Host Controller
[ 3.892074] usb 4-5: Manufacturer: Atheros Communications
[ 3.892928] usb 4-5: SerialNumber: Alaska Day 2006
[ 3.894167] usb 4-5: usb_probe_device
[ 3.894171] usb 4-5: configuration #1 chosen from 1 choice
[ 3.897231] usb 4-5: adding 4-5:1.0 (config #1, interface 0)
[ 3.897476] btusb 4-5:1.0: usb_probe_interface
[ 3.897480] btusb 4-5:1.0: usb_probe_interface - got id
[ 3.897513] usb 4-5: adding 4-5:1.1 (config #1, interface 1)
[ 3.897610] btusb 4-5:1.1: usb_probe_interface
[ 3.897612] btusb 4-5:1.1: usb_probe_interface - got id
[ 13.196090] usb 4-5: USB disconnect, device number 2
[ 13.196093] usb 4-5: unregistering device
[ 13.196096] usb 4-5: unregistering interface 4-5:1.0
[ 13.196173] usb 4-5: unregistering interface 4-5:1.1
[ 13.196221] usb 4-5: usb_disable_device nuking all URBs |
I searched on Google for "Alaska Day 2006" and I found a bug page in which was mentioned that card as 'ath3k' (I have an ath9k as wireless card, fully working). So I searched for 'ath3' and found this: http://wireless.kernel.org/en/users/Drivers/ath3k. Since I couldn't know the model of the 'presumed' ath3k card, I used 'lsusb -v | grep -i iProduct': since all the iProducts were 2, my card could have only been the 'AR3012'. I set up the kernel and the two files ath3k.c and btusb.c as explained in the guide (blacklisting btusb, adding support for ath3k and loading related firmwares).
Doing all this, things have got worse: dmesg no more notifies about the bluetooth controller, even if I restore the two config files I modified (ath3k.c and btusb.c) and recompile the kernel.
Probably kernel .config is useful to locate the problem:
| Code: | cat /usr/src/linux/.config | grep -i bt
CONFIG_BT=y
CONFIG_BT_RFCOMM=y
# CONFIG_BT_RFCOMM_TTY is not set
# CONFIG_BT_BNEP is not set
CONFIG_BT_HIDP=y
CONFIG_BT_HCIBTUSB=y
# CONFIG_BT_HCIBTSDIO is not set
# CONFIG_BT_HCIUART is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBPA10X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIDTL1 is not set
# CONFIG_BT_HCIBT3C is not set
# CONFIG_BT_HCIBLUECARD is not set
# CONFIG_BT_HCIBTUART is not set
# CONFIG_BT_HCIVHCI is not set
# CONFIG_BT_MRVL is not set
CONFIG_BT_ATH3K=y
CONFIG_EXTRA_FIRMWARE="radeon/ARUBA_me.bin radeon/ARUBA_pfp.bin radeon/ARUBA_rlc.bin radeon/TAHITI_uvd.bin radeon/SUMO_uvd.bin radeon/CAICOS_pfp.bin radeon/CAICOS_me.bin radeon/BTC_rlc.bin radeon/CAICOS_mc.bin ar3k/AthrBT_0x01020200.dfu ar3k/ramps_0x01020200_26.dfu"
CONFIG_MAC_EMUMOUSEBTN=y
CONFIG_ATH9K_BTCOEX_SUPPORT=y
# CONFIG_TABLET_USB_KBTAB is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_SND_BT87X is not set
# CONFIG_TOSHIBA_BT_RFKILL is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_RBTREE_TEST is not set |
Also...
| Code: | hcitool dev
Devices: |
and
| Code: | lsusb
Bus 002 Device 002: ID 1bcf:2883 Sunplus Innovation Technology Inc.
Bus 003 Device 004: ID 046d:c05f Logitech, Inc. M115 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:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub |
and
| Code: | rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no |
and
lspci: http://pastebin.com/tin5dWzq
lshw: http://pastebin.com/QWJyijFM
Notice that bluetooth works on Windows 7 (dual boot).
Thanks for the patience :) |
|
| Back to top |
|
 |
Logicien
Veteran
Joined: 16 Sep 2005
Posts: 1555
Location: Montréal
|
| Posted: Wed Dec 04, 2013 10:16 pm Post subject: |
|
|
Did you try without modifying any source code, with all needed kernel Bluetooth support and the firmware file for it, /lib/firmware/ath3k-1.fw from linux-firmware package?
Is your Bluetooth device supported by another Linux distribution, mainly a live-cd who take in charge Bluetooth?
_________________
Paul |
|
| Back to top |
|
|
310354
n00b
Joined: 01 Aug 2013
Posts: 59
|
| Posted: Fri Dec 06, 2013 9:45 pm Post subject: |
|
|
| Logicien wrote: | Did you try without modifying any source code, with all needed kernel Bluetooth support and the firmware file for it, /lib/firmware/ath3k-1.fw from linux-firmware package?
Is your Bluetooth device supported by another Linux distribution, mainly a live-cd who take in charge Bluetooth? |
I tried restoring ath3k.c and btusb.c and also compiling ALL available bluetooth drivers in-kernel, but dmesg still doesn't detect bluetooth host controller. Now I boot Mint from usb and check loaded modules. |
|
| Back to top |
|
|
310354
n00b
Joined: 01 Aug 2013
Posts: 59
|
| Posted: Sat Dec 07, 2013 3:21 pm Post subject: |
|
|
| Tried with mint, no bluetooth modules/drivers loaded, what can I do? |
|
| Back to top |
|
|
szatox
Advocate
Joined: 27 Aug 2013
Posts: 3150
|
| Posted: Sat Dec 07, 2013 7:17 pm Post subject: |
|
|
Make sure your BT adapter is not damaged.
I have 2 of those, one based on ath3k and the other using broadcom chip. I've made them work simply compiling BT drivers as modules. Also, /etc/init.d/bluetooth must be started. I'm using blueman for easy gui. It even supports hot-plugging usb dongle (gui vanishes when I pull it out and reappears automagicaly when I put it in again)
The only thing that should really be mentioned is ath3 coexistance support module, you need it if you also have atheros wifi device. (I do have)
Long story short, it actualy "just works" for me so I expect hardware failure rather than wrong configs. Especialy if it doesn't work with mint either |
|
| Back to top |
|
|
310354
n00b
Joined: 01 Aug 2013
Posts: 59
|
| Posted: Sun Dec 08, 2013 5:33 pm Post subject: |
|
|
| szatox wrote: | Make sure your BT adapter is not damaged.
I have 2 of those, one based on ath3k and the other using broadcom chip. I've made them work simply compiling BT drivers as modules. Also, /etc/init.d/bluetooth must be started. I'm using blueman for easy gui. It even supports hot-plugging usb dongle (gui vanishes when I pull it out and reappears automagicaly when I put it in again)
The only thing that should really be mentioned is ath3 coexistance support module, you need it if you also have atheros wifi device. (I do have)
Long story short, it actualy "just works" for me so I expect hardware failure rather than wrong configs. Especialy if it doesn't work with mint either |
I already added bluetooth daemon with rc-update. After few recompilations dmesg shows bluetooth card again. I noticed another problem: xfce does not have bluetooth settings (I already have bluetooth in use flags), I remember I had it some time ago.. wtf
edit: I have net-wireless/bluez-4.101-r7 and net-wireless/gnome-bluetooth-3.8.2.1 installed
edit #2: here is dmesg: http://pastebin.com/wtmSqyb8
edit #3: I verified that bluetooth usb controller is not detected when I edit btusb.c as explained in this example: http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=e9036e336a8e5640871e0006ea4a89982b25046f. In my case:
| Code: | + /* Atheros AR3012 with sflash firmware */
+ { USB_DEVICE(0x13d3, 0x3362), .driver_info = BTUSB_IGNORE }, |
:x |
|
| Back to top |
|
|
310354
n00b
Joined: 01 Aug 2013
Posts: 59
|
| Posted: Thu Dec 12, 2013 8:39 pm Post subject: |
|
|
I installed blueman.. of course it is useless at the moment, since I still haven't had my card working :| Can anyone help?
P.S. I noticed that both ath3k and btusb probe the bluetooth device, check dmesg.. Is this a good thing?
!!! I noticed a strange thing: the bluetooth usb controller is detected by the kernel ONLY when the computer 'comes' from a shutdown; this means that *rebooting* Gentoo implies unrecognized bluetooth device (with recognize I mean dmesg, because in any case bluetooth devices do not appear in both hcitool and rfkill) |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Installing Gentoo
