*** This bug is a duplicate of bug 460743 ***
https://bugs.launchpad.net/bugs/460743
** This bug has been marked a duplicate of bug 460743
[LucidKarmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
** Summary changed:
- bluetooth device not working with any 2.6.31 kernel in
I just tested my bluetooth with the new Ubutun Beta2 Released Apr 8th, 2010 and
had no problem connecting to my phone.
So Id assume that this issue got fixed.
Thanks!
--
bluetooth device not working with any 2.6.31 kernel in karmic
https://bugs.launchpad.net/bugs/411362
You received this bug
Hi SpmP,
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
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
bluetooth device not working with any 2.6.31 kernel in karmic
https://bugs.launchpad.net/bugs/411362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Hi,
I have a similar problem though im running: 2.6.31-13
I also can confirm that rfkill unblock blutooth and then a hciconfig hci0 up
brings the decive up withouth an error.
I now can scan for devices and find my cell-phone though i cannot connect to it.
j...@kiki:~$ sudo hcitool cc
Thanks for keeping onto this one.
I can confirm that
rfkill unblock blutooth
allows the device to be 'brought up'
2.6.31-1-rt and 2.6.31-5 both seem to work without needing this.
Strangely tho, the device is down by default and must be 'turned on' by
gnome-bluetooth (or hciconfig hci0 up)
So
Can you test and confirm with the newer 2.6.31-5 kernel? The reason I
ask is I thought some rfkill related work went into 2.6.31-5. Thanks.
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
bluetooth device not working with any 2.6.31 kernel in karmic
Then lets get the kernel guys in here on this to start looking for where
the regression developed. Considering the last thing happening during
that run of bluetoothd where it failed was rfkill stuff, can you check
the status of the rfkill interface too?
$ rfkill
You'll see if hci0 is ending up
ok boot with kernel ver. 2.6.31-4-generic
bluetoothd is running
ps aux|grep -i blue
root 254 0.0 0.0 0 0 ?S 19:32 0:00 [bluetooth]
root 2552 0.0 0.1 28472 1860 ?Ss 19:34 0:00
/opt/bluetooth/sbin/bluetoothd --udev
user 3407 0.3 1.2 189584
and just to prove it works on 2.6.28...
11/08/09 19:51:27 foundation bluetoothd[1859]Bluetooth
daemon 4.47
11/08/09 19:51:27 foundation bluetoothd[1860]Starting SDP
server
11/08/09 19:51:27 foundation bluetoothd[1860]bridge pan0
created
Is the btusb module getting loaded? Automatically?
--
bluetooth device not working with any 2.6.31 kernel in karmic
https://bugs.launchpad.net/bugs/411362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: bluez (Ubuntu)
Status: New = Incomplete
--
bluetooth device not working with any 2.6.31 kernel in karmic
https://bugs.launchpad.net/bugs/411362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
yes
...
usbcore: registered new interface driver btusb
...
--
bluetooth device not working with any 2.6.31 kernel in karmic
https://bugs.launchpad.net/bugs/411362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Ok, so is bluetoothd running automatically like it should then? There
is a udev rule that should be spawning it.
If it is, running, check the output of hciconfig. Is it showing an
hci0 device?
--
bluetooth device not working with any 2.6.31 kernel in karmic
14 matches
Mail list logo
