[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: What is the state of bulez4?





On Wed, Feb 4, 2009 at 12:48 PM, Bastien Nocera <bnocera redhat com> wrote:
On Wed, 2009-02-04 at 15:35 +0100, Kevin Kofler wrote:
> Paulo Cavalcanti wrote:
> > since I started using F10 in my main computer, I have
> > not been able to pair a single bluetooth device,
> > either using bluez-gnome or hidd.
>
> I cannot speak for the GNOME tools (but I thought they're already supposed
> to be working? Can any maintainer of GNOME or bluez-gnome comment?),

They're already supposed to be working indeed, since Fedora 10 was
released. There's certainly bugs, but I gather this is more likely to be
a kernel regression.

Check your /var/log/messages for Bluetooth-related kernel and bluetoothd
errors. Some devices have been known to be problematic with recent
kernel changes.


Using hcidump and hidd:

[cascavel:~] sudo hidd --search
Searching ...
    Connecting to device 00:12:5A:69:05:87
Can't get device information: Connection reset by peer


[cascavel:~] sudo /usr/sbin/hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
< HCI Command: Inquiry (0x01|0x0001) plen 5
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
> HCI Event: Inquiry Complete (0x01) plen 1
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Remote Name Req Complete (0x07) plen 255
> HCI Event: Disconn Complete (0x05) plen 4
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Remote Name Req Complete (0x07) plen 255
> HCI Event: Disconn Complete (0x05) plen 4
^C

 

My guess is a duplicate of:
https://bugzilla.redhat.com/show_bug.cgi?id=481221

I do not see anything unusual in /var/log/messages:


Feb  4 08:22:24 cascavel pulseaudio[5490]: pid.c: Daemon already running.
Feb  4 08:24:22 cascavel bluetoothd[6007]: Bluetooth daemon
Feb  4 08:24:22 cascavel bluetoothd[6007]: Starting SDP server
Feb  4 08:24:22 cascavel kernel: Bluetooth: L2CAP ver 2.11
Feb  4 08:24:22 cascavel kernel: Bluetooth: L2CAP socket layer initialized
Feb  4 08:24:22 cascavel bluetoothd[6007]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Feb  4 08:24:22 cascavel bluetoothd[6007]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Feb  4 08:24:22 cascavel kernel: Bluetooth: SCO (Voice Link) ver 0.6
Feb  4 08:24:22 cascavel kernel: Bluetooth: SCO socket layer initialized
Feb  4 08:24:22 cascavel bluetoothd[6007]: Parsing /etc/bluetooth/network.conf failed: No such file or directory
Feb  4 08:24:22 cascavel kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb  4 08:24:22 cascavel kernel: Bluetooth: BNEP filters: protocol multicast
Feb  4 08:24:22 cascavel kernel: Bridge firewalling registered
Feb  4 08:24:22 cascavel bluetoothd[6007]: bridge pan0 created
Feb  4 08:24:22 cascavel bluetoothd[6007]: Registered interface org.bluez.Service on path /org/bluez/6007/any
Feb  4 08:24:22 cascavel bluetoothd[6007]: HCI dev 0 registered
Feb  4 08:24:22 cascavel bluetoothd[6007]: HCI dev 0 up
Feb  4 08:24:22 cascavel bluetoothd[6007]: Starting security manager 0
Feb  4 08:24:22 cascavel bluetoothd[6007]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/6007/hci0
Feb  4 08:24:22 cascavel kernel: Bluetooth: RFCOMM socket layer initialized
Feb  4 08:24:22 cascavel kernel: Bluetooth: RFCOMM TTY layer initialized
Feb  4 08:24:22 cascavel kernel: Bluetooth: RFCOMM ver 1.10
Feb  4 08:24:22 cascavel bluetoothd[6007]: Registered interface org.bluez.NetworkPeer on path /org/bluez/6007/hci0
Feb  4 08:24:22 cascavel bluetoothd[6007]: Registered interface org.bluez.NetworkHub on path /org/bluez/6007/hci0
Feb  4 08:24:22 cascavel bluetoothd[6007]: Registered interface org.bluez.NetworkRouter on path /org/bluez/6007/hci0
Feb  4 08:24:22 cascavel bluetoothd[6007]: Registered interface org.bluez.Service on path /org/bluez/6007/hci0
Feb  4 08:24:22 cascavel bluetoothd[6007]: Adapter /org/bluez/6007/hci0 has been enabled



--
Paulo Roma Cavalcanti
LCG - UFRJ

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]