13d3:3304 IMC Networks bluetooth doesn't work

Bug #736788 reported by Petr Dlouhý
50
This bug affects 10 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: bluez

The "13d3:3304 IMC Networks" internal bluetooth module found in Asus U36JC notebook is not working in Ubuntu Maverick nor Natty.

The systems certainly knows about presence of the bluetooth module - the icon in status bar is visible and allows to switch it on/off, but nothing else works.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
Architecture: amd64
CheckboxSubmission: 4c3a0145220348e366d02efaed27e66e
CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
Date: Thu Mar 17 12:03:47 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
InterestingModules: sco bnep l2cap btusb bluetooth
MachineType: ASUSTeK Computer Inc. U36JC
ProcEnviron:
 LANGUAGE=cs_CZ:en
 PATH=(custom, user)
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic root=UUID=2d566c56-67c7-4af1-a443-a8c80061120c ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U36JC.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U36JC
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.:bvrU36JC.205:bd01/26/2011:svnASUSTeKComputerInc.:pnU36JC:pvr1.0:rvnASUSTeKComputerInc.:rnU36JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: U36JC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
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:3 acl:0 sco:0 commands:1 errors:0

Revision history for this message
Petr Dlouhý (petr-dlouhy) wrote :
Revision history for this message
Petr Dlouhý (petr-dlouhy) wrote :

Full lsusb of bluetooth device

Revision history for this message
Petr Dlouhý (petr-dlouhy) wrote :
Revision history for this message
Petr Dlouhý (petr-dlouhy) wrote :

Now, I was able to make the bluetooth working. It started working after I followed manual at http://www.phlerion.com/blog/exopc/exopc-ubuntu/ (section Bluetooth).

Revision history for this message
Petr Dlouhý (petr-dlouhy) wrote :

The strange think is, that identification of that device changes after applying that instructions.

Changed in bluez (Ubuntu):
status: New → Confirmed
papukaija (papukaija)
tags: added: maverick
Revision history for this message
bsides (rafaelwebb) wrote :

Please, what is the fix? The site pointed out is offline! =/

Revision history for this message
James Wroblewski (wroblewski-james) wrote :

This bug is present for Asus X401A using the same IMC Networks bluetooth adapter

Revision history for this message
Michel-Ekimia (michel.ekimia) wrote :

We really need to get this fixed.
This is integrated in RTL8723BE

source code is here : https://github.com/lwfinger/rtl8723au_bt/tree/new

Revision history for this message
Ákos Maróy (akos-maroy) wrote :

I'm encountering this not working after a suspend / resume cycle. on a clean boot, it seems to work. this is on an Asus UX32LN

Revision history for this message
Ákos Maróy (akos-maroy) wrote :

I wonder if there is a workaround to at least unload the module / re-load after resuming from suspend

Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :

Providing linux-firmware-nonfree is installed, this work in Ubuntu 15.10.

Changed in bluez (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Artiom Neganov (aneganov) wrote :

Has it been fixed or not? It doesn't work on Ubuntu 18.04!!!

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug has been closed for over 3 years. If you have any problems at all then please open a new bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.