Bluetooth Issue No Aadaptors Plugged In

[zaileion]

Ive had this problem with just about the length I've had my PC 2.5yrs. I'm dual booted with LMDE and Windows 7.

Ive decided to make the jump from Ubuntu to Debian. In a nutshell I'm no longer happy with Ubuntu.

Anyway I've never been able to get my Bluetooth adapter to work. Actually that's not entirely true. On some occasions in the past few years and the dozens and dozens of different Linux versions I've tried Bluetooth did work here and there but I've never been successful in getting it to work long-term.

Ive used Mint on and off over the years. But now that I've switched to Debian i have to say its much better then Ubuntu especially LMDE Mate. I've used Mate since the release of Unity. Unity has its place and will make for a great tablet and phone but i prefer Mate, maybe I'm just used to menus. I've been completely successful in getting all the software and hardware to function perfectly (short of Bluetooth) which i wasn't ever able to do with Ubuntu or any flavor there of, nor with pure Debian. I also read an article stating that Linux Mint 17 could be the best OS ever built! I know Mint 17 isn't the same as LMDE but i have to say so far LMDE-Mate is absolutely AWESOME!

it seems as though the OS detects the device as shown in the screenshot of the

Code: Select all

lsusb

command. you may notice after

Code: Select all

dmesg |grep -i bluetooth

there is a line that states "can't change to loading configuration err" i have no idea if that's normal nor do i understand anything following that command.

In Windows Bluetooth works perfect, so i know the hardware is functional.


Fixing this issue would be great. Its been a while i've been dealing with it. Thanks very much!


here is the result of the 2 above commands. It's a Copy/Paste from attached screenshot.

username@lmde-vak-pc1:~$ lsusb
Bus 006 Device 002: ID 046d:09a1 Logitech, Inc. QuickCam Communicate MP/S5500
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 012 Device 003: ID 2516:0011
Bus 012 Device 002: ID 046d:c531 Logitech, Inc.
Bus 012 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 002: ID 13d3:3304 IMC Networks Asus Integrated Bluetooth module [AR3011]
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 002: ID 15c2:0045 SoundGraph Inc.
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 1b1c:1c00 Corsair
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 152d:0539 JMicron Technology Corp. / JMicron USA Technology Corp. JMS539 SuperSpeed SATA II 3.0G Bridge
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

username@lmde-vak-pc1:~$ dmesg |grep -i bluetooth
[ 7.570910] Bluetooth: Core ver 2.16
[ 7.570920] Bluetooth: HCI device and connection manager initialized
[ 7.570925] Bluetooth: HCI socket layer initialized
[ 7.570926] Bluetooth: L2CAP socket layer initialized
[ 7.570931] Bluetooth: SCO socket layer initialized
[ 12.580759] Bluetooth: Can't change to loading configuration err
[ 17.841553] Bluetooth: RFCOMM TTY layer initialized
[ 17.841565] Bluetooth: RFCOMM socket layer initialized
[ 17.841567] Bluetooth: RFCOMM ver 1.11
[ 17.867645] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 17.867648] Bluetooth: BNEP filters: protocol multicast
[ 17.867658] Bluetooth: BNEP socket layer initialized
username@lmde-vak-pc1:~$

[JeremyB]

One thing to try

Code: Select all

echo "blacklist ath3k" | sudo tee /etc/modprobe.d/ath3k.conf

Reboot and open terminal

Code: Select all

sudo modprobe ath3k

Your AR3011 bluetooth might have the same issue with xhci that the AR3012 does and this is the only way I found to fix

[zaileion]

I tried those commands. but unfortunately it did not fix the issue. I tried them a 2nd time just to make sure.

Should i be concerned about reversing the 2 commands since they had no effect on the Bluetooth?

If you have the time, would you give some level of an explanation as to what the commands mean and/or what they do. The more technical and detailed the better. I'm focused learning this OS.

Thank You!

[JeremyB]

I tried those commands. but unfortunately it did not fix the issue. I tried them a 2nd time just to make sure.

Should i be concerned about reversing the 2 commands since they had no effect on the Bluetooth?

If you have the time, would you give some level of an explanation as to what the commands mean and/or what they do. The more technical and detailed the better. I'm focused learning this OS.

Thank You!

The first command prevents the ath3k module that should load the firmware for the bluetooth device from being loaded normally. The second command forces ath3k to be loaded and it should allow firmware to be loaded. I imagine the dmesg error is the same and by the code should be an error with the firmware

Code: Select all

if ((err = usb_control_msg(udev, pipe,
				USB_REQ_DFU_DNLOAD,
				USB_TYPE_VENDOR, 0, 0,
				send_buf, 20, USB_CTRL_SET_TIMEOUT)) < 0) {
		BT_ERR("Can't change to loading configuration err");
		goto error;

Any results from

Code: Select all

dmesg | grep -i dfu

[zaileion]

The first command prevents the ath3k module that should load the firmware for the bluetooth device from being loaded normally. The second command forces ath3k to be loaded and it should allow firmware to be loaded. I imagine the dmesg error is the same and by the code should be an error with the firmware

Code: Select all
if ((err = usb_control_msg(udev, pipe,
USB_REQ_DFU_DNLOAD,
USB_TYPE_VENDOR, 0, 0,
send_buf, 20, USB_CTRL_SET_TIMEOUT)) < 0) {
BT_ERR("Can't change to loading configuration err");
goto error;

Im not sure what your messages says. you say "I imagine dmesg error..." followed by some code. I just don't know what to do with that information, sorry. Now i feel like a real Noob... I tried to run dmesg error as a command and i got a huge list of information.

Here is what was listed regarding "Bluetooth" i listed the line above and line below Bluetooth just in case it was relevant.

[ 12.304364] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input24
[ 13.670109] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 13.670113] Bluetooth: BNEP filters: protocol multicast
[ 13.670123] Bluetooth: BNEP socket layer initialized
[ 13.676569] Bluetooth: RFCOMM TTY layer initialized
[ 13.676578] Bluetooth: RFCOMM socket layer initialized
[ 13.676580] Bluetooth: RFCOMM ver 1.11
[ 13.717195] lp: driver loaded but no devices found

but i didn't get anything like the code you typed.

With regard to this code dmesg | grep -i dfu i just get the prompt again. i also tried sudo dmesg | grep -i dfu same result. just re displays the terminal prompt

[JeremyB]

See what this returns

Code: Select all

dmesg | grep -e btusb -e ath3k

[zaileion]

Here is the response from the command you suggested.

$ dmesg | grep -e btusb -e ath3k
[ 7.769512] usbcore: registered new interface driver btusb


Thanks for the help. I am extremely grateful, I've not been able to find a fix anywhere on the internet and really need to use Bluetooth on Linux. I should mention a while back i was trying to solve this and i read somewhere that it has something to do with the Windows dual boot. i followed the instructions i could find but none of them worked... Plus most if not all of them were for Ubuntu.

Edit: i ran the command. posted the above. rebooted, and ran the command again as root. I don't know if this is relevant but the numbers changed. Still no Bluetooth adapters.

$ sudo dmesg | grep -e btusb -e ath3k
[sudo] password for vak:
[ 5.687456] usbcore: registered new interface driver btusb
$

[JeremyB]

Here is the response from the command you suggested.

$ dmesg | grep -e btusb -e ath3k
[ 7.769512] usbcore: registered new interface driver btusb


Thanks for the help. I am extremely grateful, I've not been able to find a fix anywhere on the internet and really need to use Bluetooth on Linux. I should mention a while back i was trying to solve this and i read somewhere that it has something to do with the Windows dual boot. i followed the instructions i could find but none of them worked... Plus most if not all of them were for Ubuntu.

Edit: i ran the command. posted the above. rebooted, and ran the command again as root. I don't know if this is relevant but the numbers changed. Still no Bluetooth adapters.

$ sudo dmesg | grep -e btusb -e ath3k
[sudo] password for vak:
[ 5.687456] usbcore: registered new interface driver btusb
$

Shutdown the computer and boot in LM, then do a

Code: Select all

dmesg > dmesg.txt

Copy the contents of dmesg.txt and paste it at paste.ubuntu.com and post the URL. Having Windows on dual boot usually only makes a difference if you choose reboot from within Windows and go into Linux as the firmware loaded from Windows will still be loaded

Don't worry about this

Code: Select all

if ((err = usb_control_msg(udev, pipe,
USB_REQ_DFU_DNLOAD,
USB_TYPE_VENDOR, 0, 0,
send_buf, 20, USB_CTRL_SET_TIMEOUT)) < 0) {
BT_ERR("Can't change to loading configuration err");
goto error;

It is actually part of the drivers program. Something else to try before your reboot

Code: Select all

sudo apt-get install linux-firmware

[zaileion]

demesg.txt link:
http://paste.ubuntu.com/9926718/

Code: Select all

# apt-get install linux-firmware
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package linux-firmware
#

[JeremyB]

Code: Select all

modprobe -c | grep 3304

Do you have the Synaptic Package Manager program in LMDE? The package might be firmware-atheros in debian

[zaileion]

firmware-atheros was already installed, i re-installed it just to be safe. (Screenshot)

$ modprobe -c | grep 3304
Command 'modprobe' is available in '/sbin/modprobe'
The command could not be located because '/sbin' is not included in the PATH environment variable.
This is most likely caused by the lack of administrative priviledges associated with your user account.
modprobe: command not found
$ sudo modprobe -c | grep 3304
[sudo] password for vak:
alias usb:v13D3p3304d*dc*dsc*dp*ic*isc*ip*in* ath3k
$

Edit:
I removed the firmware-atheros, rebooted and re-installed. Still no Bluetooth.

Appreciate the continued help man, very much!

[JeremyB]

We still have ath3k in the blacklist so

Code: Select all

sudo modprobe ath3k

then wait a couple minutes and

Code: Select all

dmesg | tail -20

[zaileion]

$ dmesg | tail -20
[ 15.598409] <6>[fglrx] Reserved FB block: Unshared offset:f7fc000, size:504000
[ 15.598411] <6>[fglrx] Reserved FB block: Unshared offset:fff8000, size:8000
[ 15.598411] <6>[fglrx] Reserved FB block: Unshared offset:bfff4000, size:c000
[ 15.625534] <6>[fglrx] IRQ 108 Disabled
[ 15.972956] fglrx_pci 0000:06:00.0: irq 108 for MSI/MSI-X
[ 15.973232] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 15.973338] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 15.973368] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 15.973505] <6>[fglrx] Firegl kernel thread PID: 3644
[ 15.973626] <6>[fglrx] Firegl kernel thread PID: 3645
[ 15.973788] <6>[fglrx] Firegl kernel thread PID: 3646
[ 15.973911] <6>[fglrx] IRQ 108 Enabled
[ 15.986382] sda3: WRITE SAME failed. Manually zeroing.
[ 20.172393] systemd-logind[3779]: New seat seat0.
[ 20.173174] systemd-logind[3779]: New session c1 of user vak.
[ 20.173227] systemd-logind[3779]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
[ 94.647533] usb 7-1: firmware: agent loaded ath3k-1.fw into memory
[ 99.644458] Bluetooth: Can't change to loading configuration err
[ 99.644496] ath3k: probe of 7-1:1.0 failed with error -110
[ 99.644541] usbcore: registered new interface driver ath3k
$

i had high hopes this time, but still no luck.

[JeremyB]

Does the debian edition offer any newer kernels? In LM 17, I can go to the Update Manager, click view then Linux kernels and select a newer kernel and this issue could be solved in the 3.13 or 3.14 series of kernels

[zaileion]

that option isn't available in my package-manager, software-manager or update manager. under the "view" option in the menu bar there is noting about kernels anywhere.

Do you think its the kernel?

[JeremyB]

that option isn't available in my package-manager, software-manager or update manager. under the "view" option in the menu bar there is noting about kernels anywhere.

Do you think its the kernel?

It is likely the kernel or you have one of the odd machines that won't let the bluetooth work is USB 3.0 is enabled. Could you try the LM 17 Mate ISO?

[zaileion]

How do i confirm usb 3.0 is functioning properly?

Usb3.0 amd bkuetooth function flawless in Windows.

My system specs are:
Mobo: Asus Rampage 3 Black Edition (integrated Bluetooth and wifi)
Graphics: ATI Radeon 7990
Audio: Sound Blaster Platinum
Raid controller LSI MegaRaid 4i (I forgrt the model #)
Hard drives: 2 Samsung 840 Pro 256GB in Raid 0 striping
CPU: Intel x990 extreem
PSU: Corsair 1200xi

Ive had this problem with every distro ive tried. Ubuntu from 11.04 thru 14.10, Debian, LMDE, and i install linux on my box like i change flavors of gum. Ive used dozens of different releases and distros. Ive got a stack of disks 6 inches high b4 i started using usb flash memory.

I dont think its going to work with mint 17 bevause its built on ubuntu and ive tried several different ubuntu releases including ubuntu testing release and ubuntu server amd the latest release 14.10

I will try to install mint 17 just to make sure. But im all but certain it wont fix the issue. There has to be some kind of detection issue..

Is there a way i can upgrade to the latest kernel on lmde? Im no longer fond of ubuntu. Im sure it has to be compiled which i would need some guidence on.

[JeremyB]

Lets try one other thing first

Code: Select all

md5sum /lib/firmware/ath3k-1.fw

[zaileion]

$ sudo md5sum /lib/firmware/ath3k-1.fw
1211fa34c09e10ba48381586b7c3883d /lib/firmware/ath3k-1.fw
$ md5sum /lib/firmware/ath3k-1.fw
1211fa34c09e10ba48381586b7c3883d /lib/firmware/ath3k-1.fw
$

[JeremyB]

https://www.dropbox.com/s/jk2nk05t8712j ... -1.fw?dl=0

Download to your home folder then

Code: Select all

sudo cp ath3k-1.fw /lib/firmware/ath3k-1.fw

reboot then

Code: Select all

sudo modprobe ath3k

and see if it will work
And check the md5sum, it should be

Code: Select all

24cfee59a24f336dfae838a0de6445a0