Bluetooth does not work in Ubuntu 12.04.2, AMD AMD® Trinity APU A10-4655M 2.0 GHz

[Riyugi, Murakami]

In the bluetooth indicator/global menu, options are available to turn
it on/off. However, in the bluetooth settings window, it is indicated
that bluetooth is disabled and it cannot be turned on. Furthermore,
trying to setup a new device returns "No Adapters Found".

Here is the output of lsusb :
Bus 001 Device 002: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 001 Device 003: ID 04f2:b364 Chicony Electronics Co., Ltd
Bus 004 Device 010: ID 13d3:3392 IMC Networks
Bus 004 Device 003: ID 0eef:7907 D-WAV Scientific Co., Ltd
Bus 005 Device 002: ID 046d:c052 Logitech, Inc.
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
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub.

Here is the output of rfkill list :
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

1: brcmwl-0: Wireless LAN
Soft blocked: no Hard blocked: no
2: asus-wlan: Wireless LAN
Soft blocked: no Hard blocked: no
3: asus-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no.

Here is the output of sudo hcitool dev :
Devices : .

In windows 8, the bluetooth works flowlessly. If I login Windows 8,
keep the bluetooth on before restarting to Ubuntu, the bluetooth
is still disabled.

In the BIOS/UEFI settings, the bluetooth is enabled.

Furthermore, the wifi and bluetooth share the same set of keys :
Fn + F2. In Windows 8, If i turn on the bluetooth a small dot in the
F2 key is lit. In ubuntu pressing, Fn + F2 enables/disables wifi and
the bluetooth indicator menu swaps between on/off but the bluetooth
is still really off.

Side Note : This is a new machine (2013) and I couldn't try the settings
for Ubuntu 13.04 and 13.10. Installation of Ubuntu 13.04 and 13.10
resulted to corrupted display. [This will be a different bug.]

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-2ubuntu7
ProcVersionSignature: Ubuntu 3.5.0-34.55~precise1-generic 3.5.7.13
Uname: Linux 3.5.0-34-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
Date: Tue Jul 2 12:37:36 2013
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
InterestingModules: rfcomm bnep bluetooth
MachineType: ASUSTeK COMPUTER INC. U38N
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-34-generic root=UUID=d3189321-36df-497c-a331-8e942669bf3e ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/22/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U38N.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U38N
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU38N.204:bd11/22/2012:svnASUSTeKCOMPUTERINC.:pnU38N:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnU38N:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: U38N
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:

syslog:

[Riyugi, Murakami (murakamiriyugi)]

Correction to

Side Note : This is a new machine (2013) and I couldn't try the settings
for Ubuntu 13.04 and 13.10. Installation of Ubuntu 13.04 and 13.10
resulted to corrupted display. [This will be a different bug.]

13.10 should be 12.10

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[bjv (bjamesv)]

Unintentionally disabled bluetooth via indicator icon,

unable to re-enabled through settings, toggling 'on' flashes my configured devices in the list below for a split second, then goes back to 'off'/'Bluetooth is disabled'

[bjv (bjamesv)]

freshly installed 13.10 (daily 20130817)

[Yusuke Iwaki (q7w8e9w8q7w8e9)]

Doesn't the commands below fix the problem?
--
 echo "13d3 3392" > /sys/bus/usb/drivers/btusb/new_id
 modprobe btusb

[Riyugi, Murakami (murakamiriyugi)]

Dear Yusuke Iwaki-san

Thank you for looking into the matter.
I am now using Ubuntu 12.04.3 kernel 3.8.

Inputting in the terminal returns:
bash: /sys/bus/usb/drivers/btusb/new_id: No such file or directory

I think I do not have this btusb module.
Or maybe I misunderstood your what you wanted
to say. Could you be more specific please?

Thank you very much.

Sincerely,
Allan L. Alinea

On Thu, Sep 26, 2013 at 11:12 PM, Yusuke Iwaki
<email address hidden>wrote:

> Doesn't the commands below fix the problem?
> --
> echo "13d3 3392" > /sys/bus/usb/drivers/btusb/new_id
> modprobe btusb
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1196788
>
> Title:
> Bluetooth does not work in Ubuntu 12.04.2, AMD AMD® Trinity APU
> A10-4655M 2.0 GHz
>
> Status in “bluez” package in Ubuntu:
> Confirmed
>
> Bug description:
> In the bluetooth indicator/global menu, options are available to turn
> it on/off. However, in the bluetooth settings window, it is indicated
> that bluetooth is disabled and it cannot be turned on. Furthermore,
> trying to setup a new device returns "No Adapters Found".
>
> Here is the output of lsusb :
> Bus 001 Device 002: ID 0bda:0139 Realtek Semiconductor Corp.
> Bus 001 Device 003: ID 04f2:b364 Chicony Electronics Co., Ltd
> Bus 004 Device 010: ID 13d3:3392 IMC Networks
> Bus 004 Device 003: ID 0eef:7907 D-WAV Scientific Co., Ltd
> Bus 005 Device 002: ID 046d:c052 Logitech, Inc.
> 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
> Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub.
>
> Here is the output of rfkill list :
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>
> 1: brcmwl-0: Wireless LAN
> Soft blocked: no Hard blocked: no
> 2: asus-wlan: Wireless LAN
> Soft blocked: no Hard blocked: no
> 3: asus-bluetooth: Bluetooth
> Soft blocked: no
> Hard blocked: no.
>
> Here is the output of sudo hcitool dev :
> Devices : .
>
> In windows 8, the bluetooth works flowlessly. If I login Windows 8,
> keep the bluetooth on before restarting to Ubuntu, the bluetooth
> is still disabled.
>
> In the BIOS/UEFI settings, the bluetooth is enabled.
>
> Furthermore, the wifi and bluetooth share the same set of keys :
> Fn + F2. In Windows 8, If i turn on the bluetooth a small dot in the
> F2 key is lit. In ubuntu pressing, Fn + F2 enables/disables wifi and
> the bluetooth indicator menu swaps between on/off but the bluetooth
> is still really off.
>
> Side Note : This is a new machine (2013) and I couldn't try the settings
> for Ubuntu 13.04 and 13.10. Installation of Ubuntu 13.04 and 13.10
> resulted to corrupted display. [This will be a d...

[Benjamin (benmoran56)]

Hi Iwaki-san,

Thanks for your advice. This worked for me on Arch linux. However, I had to modprobe btusb first. Then, the btusb folder appeared under drivers and I could echo the id.

 modprobe btusb
 echo "13d3 3392" > /sys/bus/usb/drivers/btusb/new_id

[Riyugi, Murakami (murakamiriyugi)]

Iwaki-san and Mr. Benjamin,

I got mine also working
[Ubuntu 12.04.3 kernel 3.8
AMD AMD® Trinity APU A10-4655M]

I inputted the following commands:

sudo modprobe btusb
sudo sh -c 'echo 13d3 3392 > /sys/bus/usb/drivers/btusb/new_id'

[Riyugi, Murakami (murakamiriyugi)]

Bluetooth does work by using the above-mentioned
method. But after reboot, bluetooth is in off state again
and the commands mentioned above have to be executed
again.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please upgrade to the latest version and re-test.

[Launchpad Janitor (janitor)]

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]