0a5c:2035 Broadcom BCM2035 not working in ubuntu natty or oneiric

[Bhaskar Divya]

I am not able to turn on the bluetooth from the bluetooth applet ... after clicking on "turn on bluetooth" , It just grayed out.
I have tried in both natty and oneiric.
edit: I think i made some progress.Bluez seems to be the problem.
I used sakis3g(www.sakis3g.org) and used my nokia mobile's mac address and it did connected for a while...and then stops.
In terminal, i used rfcomm connect command, it asked for pass in my mobile but no pass worked as i think there is no pairing agent bind to the bluetooth device.

pairing is a problem now.. as no pairing agent is running
Should i try installing precise's bluez package or compile from source?

lsusb

Bus 003 Device 003: ID 0a5c:2035 Broadcom Corp. BCM2035 Bluetooth

lsmod

Module Size Used by
bnep 17785 0
btusb 18160 1
bluetooth 65493 4 sco,bnep,l2cap,btusb

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-9-generic 2.6.38-9.43
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: home 2860 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'CMI8738'/'C-Media CMI8738 (model 37) at 0xe800, irq 19'
   Mixer name : 'CMedia PCI'
   Components : ''
   Controls : 43
   Simple ctrls : 23
Date: Fri Dec 30 00:50:46 2011
HibernationDevice: RESUME=UUID=d379af4c-ee84-4612-adee-d12372b85d95
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-9-generic root=UUID=d8c480c2-b40a-4a74-9946-bd5ea121862b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-9-generic N/A
 linux-backports-modules-2.6.38-9-generic N/A
 linux-firmware 1.52
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0414
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5QPL-AM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0414:bd06/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QPL-AM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc2 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc2'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[Bhaskar Divya (bhaskar-divya007)]

I installed the latest kernel 3.3rc2. It didn't fixed it.
I then tried to reinstall bluez 4.98 from source, it didn't fixed.
I did try service restart in between steps.

Then i installed Blueman, started it but it shows bluez error that bluez daemon was not running

I tried rfcomm command to connect with my mobile... it did asked the passkey on my mobile... no passkey matched.

Then, i tried to run bluez-simple-agent in terminal believing it was a pairing agent .
it threw some python traceback errors:

Traceback (most recent call last):
  File "/usr/bin/bluez-simple-agent", line 88, in <module>
    manager = dbus.Interface(bus.get_object("org.bluez", "/"),
  File "/usr/lib/pymodules/python2.7/dbus/bus.py", line 244, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/pymodules/python2.7/dbus/proxies.py", line 241, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/pymodules/python2.7/dbus/bus.py", line 183, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/pymodules/python2.7/dbus/bus.py", line 281, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/pymodules/python2.7/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files

Currently, I have uninstalled bluez(and with it i think gnome-bluetooth), then installed blueman (and it reinstalled bluez4.91).
Blueman is showing same errors as above even now.

[Bhaskar Divya (bhaskar-divya007)]

Some success at last...
I purged bluez via
sudo apt-get remove --purge bluez

then installed bluez from here

https://launchpad.net/ubuntu/+source/bluez/4.69-0ubuntu2/+build/1930179

these are maverick's version of bluez.
Now Blueman detects my mobile and i can browse files on it.
Still DUN is a problem a bit.
But that seems to be another bug.

[penalvch (penalvch)]

Bhaskar Divya, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Launchpad Janitor (janitor)]

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