You are not logged in.
I have a USB Bluetooth dongle, which has been running ok for a long time. Recently however, the KDE Bluetooth daemon reports 'no device found'. This the dmesg output when i plug in the dongle:
--------------------------------------------
ohci_hcd 0000:00:02.0: wakeup
usb 3-1: new full speed USB device using ohci_hcd and address 5
--------------------------------------------
When I start the bluetooth script:
sudo ./bluetooth start
Starting Bluetooth subsystem: hcid sdpd hidd hid2hci rfcomm.
--------------------------------------------
hciconfig gives me a blank output
--------------------------------------------
#kbluetoothd
kbluetoothd: HciListener::HciListener()
kbluetoothd: WARNING: No usable bluetooth device found.
kbluetoothd: Using hci0 as default bluetooth device.
kbluetoothd: HciSocket::open()
kbluetoothd: Bind failed: No such device
kbluetoothd: TrayIcon::slotMruMenuUpdate
kbluetoothd: HciSocket::open()
kbluetoothd: Bind failed: No such device
kbluetoothd: Kbluetoothd: Error opening HCI socket
kbluetoothd: TrayIcon::slotMruMenuUpdate
kbluetoothd: HciSocket::open()
kbluetoothd: Bind failed: No such device
-----------------------------------------------
i thought this maybe a hardware issue, but the dongle is still detected in Windows.
I'm running custom 2.6.15 with the latest udev from testing and the uevent patch applied.
Appreciate all help.
Offline
Would this patch in bluez.org be the one i need? I tried applying it to the kernel source and it failed.
Bluetooth kernel patch 2.6.15-mh2 available
This patch fixes the crash in the HID report mode protocol support and makes it work again.
Offline
i'll look into chucking those bluetooth patches into the next archck release. not sure when that will be yet.
iphitus
Offline
I'm using testing repo and the latest ArchCK and Bluetooth works fine. Perhaps it is a KDE issue. Try running these commands and let me know what they say:
hcitool dev
hciconfig
Offline
$ hcitool dev
Devices:
$ hciconfig
(this doesnt give any output)
Offline
Ahh I just saw in the first post you said hciconfig doesn't output anything, oops. I'm not sure if MH's patches will provide the magic fix but that's probably the next thing I'd try.
Offline
Yeah I managed to patch the kernel but no luck.. everything is just the way it was. :-(
Offline
I wish I could test this out with an older udev like 0.78 or 0.79..I unfortunately did pacman -Syc and lost the old packages..is there any place I can get them?
Offline
Here you go:
One very basic question for you - did the bluetooth services actually start i.e. can you see messages like this
Feb 16 11:13:18 tk-i5ka hcid[9424]: Bluetooth HCI daemon
Feb 16 11:13:18 tk-i5ka sdpd[9426]: Bluetooth SDP daemon
Feb 16 11:13:18 tk-i5ka hcid[9424]: HCI dev 0 up
Feb 16 11:13:18 tk-i5ka hcid[9424]: Starting security manager 0
in /var/log/everything.log? Specifically, is hcid running? Check this:
$ ps ax | grep hci
9424 ? Ss 0:00 hcid: processing events
My dongle is working fine with the latest udev and a custom archck kernel, btw.
Offline
Thanks tomk, it works perfectly with the 079 package.
Offline
I have bluetooth working fine in 2.6.15 and the latest udev. It had nothing to do with those patches, but was an error on my part. Somewhere along the way I borked up my initscripts and forgot to add the bluetooth modules. Still doesn't explain why udev-079 worked though :?:
Anyway, all issues sorted out. Thanks for the help people.
Offline