[Asus 1215p] - Bluetooth - No Devices Found

Bug #954348 reported by Greg Vallande
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
High
Unassigned

Bug Description

Output of checkbox's "bluetooth_scan" -

g@g-EeePC:/usr/share/checkbox/scripts$ ./bluetooth_scan
Can't get device info: No such device

also the output of hcitool dev:

g@g-EeePC:~$ hcitool dev
Devices:

Looks to be an unsupported bluetooth interface.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: bluez 4.96-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
CheckboxCommand: hcitool dev | tail -n+2 | awk '{print $2}' |grep -E "^([0-9a-fA-F]{2}\:){5}[0-9a-fA-F]{2}$"
CheckboxDescription: Output address of detected Bluetooth device, if any, or exits with error if none is found.
CheckboxTest: bluetooth/detect
Date: Tue Mar 13 13:56:24 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
InterestingModules: rfcomm bnep bluetooth
MachineType: ASUSTeK Computer INC. 1215P
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=8def2d8b-52fc-445c-994a-22409b909fe0 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1215P
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd12/30/2010:svnASUSTeKComputerINC.:pn1215P:pvrx.x:rvnASUSTeKComputerINC.:rn1215P:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1215P
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
hciconfig:

Revision history for this message
Greg Vallande (gvallande) wrote :
affects: bluez (Ubuntu) → linux (Ubuntu)
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? 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 in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc7-precise/

tags: added: needs-upstream-testing
Revision history for this message
Peter Snow (peter-x8o) wrote :

Also affects the Acer Aspire 4752G running:

Kubuntu 12.04LTS
3.2.0-24-generic-pae #39-Ubuntu SMP Mon May 21 18:54:21 UTC 2012 i686 i686 i386 GNU/Linux

Output of:

sudo dmesg | grep -i blue
[ 20.322767] Bluetooth: Core ver 2.16
[ 20.322943] Bluetooth: HCI device and connection manager initialized
[ 20.322946] Bluetooth: HCI socket layer initialized
[ 20.322949] Bluetooth: L2CAP socket layer initialized
[ 20.322955] Bluetooth: SCO socket layer initialized
[ 20.325735] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 20.325740] Bluetooth: BNEP filters: protocol multicast
[ 20.327085] Bluetooth: RFCOMM TTY layer initialized
[ 20.327090] Bluetooth: RFCOMM socket layer initialized
[ 20.327093] Bluetooth: RFCOMM ver 1.11

The laptop has no hardware switch for disabling the bluetooth, neither does it have a hardware LED dedicated to it. Their is also no explicit FN+ keyboard combination for this, unless it is included in the Wireless FN+ combination. However, I'm using the Wifi LAN adaptor now, so if it is linked to that, it is certainly enabled.

Thanks.

Revision history for this message
penalvch (penalvch) wrote :

Greg Vallande, 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 comment as to if your bluetooth device is USB? If so, could you please plug it in, unplug all other USB devices, execute the following via a terminal, and post the results to this report:
lsusb

If not, could you please clarify?

As well, 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

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.