Can't find any bluetooth devices after kernel-update (2.6.38-9-generic #43-Ubuntu)

Bug #775648 reported by Stefan Nagy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Since the upgrade to Natty I was affected by bug 700292, tried out the patch linked there (comment #10), but that didn't help. Today I installed the kernel update (natty-proposed) & now my adapter can't even find the keyboard anymore.

I tried it with gnome-bluetooth and with 'hcitool scan', I already restarted several times, I tried 'sudo killall bluetooth' and 'sudo bluetoothd' to restart the bluetooth daemon… nothing helped.

Please tell me if you need more information.

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: stefan 1340 F.... pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 10'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 33
   Simple ctrls : 22
Date: Mon May 2 17:00:48 2011
HibernationDevice: RESUME=UUID=7cc1bb13-9a0f-48da-a4ec-e8b17f230f67
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: Hewlett-Packard Compaq nx7010 (PG588ET#UUZ)
PccardctlIdent:
 Socket 0:
   product info: "OMNIKEY", "CardMan 4040", "", ""
   manfid: 0x0223, 0x0200
PccardctlStatus:
 Socket 0:
   5.0V 16-bit PC Card
   Subdevice 0 (function 0) bound to driver "cm4040_cs"
ProcEnviron:
 LANGUAGE=de_AT:en
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-9-generic root=/dev/mapper/ubuntu-root 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
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/14/2005
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68BAL Ver. F.55
dmi.board.name: 0860
dmi.board.vendor: COMPAL
dmi.board.version: 8051 Version 24.56
dmi.chassis.type: 10
dmi.chassis.vendor: COMPAL
dmi.chassis.version: NULL
dmi.modalias: dmi:bvnHewlett-Packard:bvr68BALVer.F.55:bd07/14/2005:svnHewlett-Packard:pnCompaqnx7010(PG588ET#UUZ):pvrF.55:rvnCOMPAL:rn0860:rvr8051Version24.56:cvnCOMPAL:ct10:cvrNULL:
dmi.product.name: Compaq nx7010 (PG588ET#UUZ)
dmi.product.version: F.55
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Stefan Nagy (stefan-nagy) wrote :
Revision history for this message
Stefan Nagy (stefan-nagy) wrote :

I'll attach the output of 'sudo bluetoothd -d -n', maybe this helps…

Martin Pitt (pitti)
tags: added: regression-proposed
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
summary: - Bluetooth adapter can't find bluetooth keyboard after kernel-update
+ Can't find/connect any bluetooth devices after kernel-update
(2.6.38-9-generic #43-Ubuntu)
Revision history for this message
Stefan Nagy (stefan-nagy) wrote : Re: Can't find/connect any bluetooth devices after kernel-update (2.6.38-9-generic #43-Ubuntu)

I tried the same thing with my Samsung Galaxy 3 (i5800) today & had no luck. I have no other bluetooth devices, but I think I can count the keyboard out as error source now.

BTW, the output of 'hcitool dev' shows that my bluetooth adapter seems to be detected…

Revision history for this message
Stefan Nagy (stefan-nagy) wrote :

OK, I tried kernel 2.6.38-9 again and bluetooth didn't work either. Then I tried different live-cds and bluetooth worked. And then I decided to reinstall the whole system to see where the problem came in. Result: Now I can't reproduce this bug anymore. Sorry, I don't know what happend there…

Since Brad Figg confirmed this bug I won't close it for now. However, it seems that for me this problem is definitely solved.

Revision history for this message
Stefan Nagy (stefan-nagy) wrote :

Ouch, there's a typo in the first sentence… I tried it with the current kernel from the 'main'-repository, that's 2.6.38-8.

Sorry for the spam :-/

Revision history for this message
Brad Figg (brad-figg) wrote :

Original submitter can no longer reproduce the issue.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Changed in linux (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Stefan Nagy (stefan-nagy) wrote :

Sorry – I have to reopen this one… After trying out Debian Squeeze for some days I decided to install Natty again & now (immediately after I installed Natty) I can absolutely reproduce this problem.

I had no problems with bluetooth on Squeeze at all, on Natty I can't connect (or even "find") any of my bluetooth devices. Now kernel 2.6.38-11-generic is affected, I just installed the "normal" updates (no backports, no proposed updates).

Revision history for this message
Stefan Nagy (stefan-nagy) wrote :

I should add that I'm able to connect devices when I start the connection from the other side – my smartphone for example. When I do so, I don't have any problems with the connection. So the problem could be limited to the ability of my adapter to find other devices.

Regarding my bluetooth keyboard this is definitely a problem, since it's not possible to start the connection "from the other side"…

Revision history for this message
Stefan Nagy (stefan-nagy) wrote :

I found a workaround for my keyboard:

I wrote down the bluetooth device address of my keyboard while using another pc running Ubuntu 10.10 & paired the keyboard and my notebook with the command 'bluez-simple-agent hci0 XX:XX:XX:XX:XX:XX'. After that my keyboard was listed in the Gnome bluetooth applet and all I had to do was to klick on 'Connect' – now everything seems to work fine.

As I said before the problem only seems to affect the scanning-process.

summary: - Can't find/connect any bluetooth devices after kernel-update
- (2.6.38-9-generic #43-Ubuntu)
+ Can't find any bluetooth devices after kernel-update (2.6.38-9-generic
+ #43-Ubuntu)
Revision history for this message
penalvch (penalvch) wrote :

Stefan Nagy, thank you for reporting this and helping make Ubuntu better. 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? Can you try 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 run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

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

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please 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. Please let us know your results.

Thanks in advance.

tags: added: needs-upstream-testing regression-update
removed: regression-proposed
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Stefan Nagy (stefan-nagy) wrote :

Hi Christopher M. Penalver, sorry – I can't try with the latest development release of Ubuntu. I'm using Debian and it's impossible for me to start Precise Pangolin (Beta 2) from a live media since my CPU doesn't support Physical Address Extension (PAE) which means I'm affected by Bug #897786

Revision history for this message
Stefan Nagy (stefan-nagy) wrote :

To test this I installed Ubuntu 12.04 with the non-pae network installation image (http://archive.ubuntu.com/ubuntu/dists/precise/main/installer-i386/current/images/netboot/non-pae/mini.iso).

I can't reproduce this bug anymore. Since I have no idea in which package, when or how this was fixed I'm going to close this report as 'invalid'. I hope that's correct.

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