bluetooth support broken?

Rui Miguel Seabra rms at 1407.org
Fri Feb 11 22:38:30 UTC 2005


Hi, I used to swap files and vcards with my cell phone through
bluetooth.

My usb bt dongle is a Sitecom CN-502, which AFAIK works.

When I plug-it, I see in /var/log/messages
Feb 11 22:25:19 roque kernel: Bluetooth: Core ver 2.7
Feb 11 22:25:19 roque kernel: NET: Registered protocol family 31
Feb 11 22:25:19 roque kernel: Bluetooth: HCI device and connection
manager initialized
Feb 11 22:25:19 roque kernel: Bluetooth: HCI socket layer initialized
Feb 11 22:25:19 roque kernel: Bluetooth: HCI USB driver ver 2.8
Feb 11 22:25:19 roque kernel: usbcore: registered new driver hci_usb
Feb 11 22:25:19 roque kernel: usb 3-2: reset full speed USB device using
uhci_hcd and address 3
Feb 11 22:25:19 roque kernel: usb 3-2: device firmware changed
Feb 11 22:25:19 roque kernel: usb 3-2: USB disconnect, address 3

Then I start the bluetooth service:
# service bluetooth start

and see:
Feb 11 22:28:09 roque hcid[3963]: Bluetooth HCI daemon
Feb 11 22:28:10 roque kernel: Bluetooth: L2CAP ver 2.7
Feb 11 22:28:10 roque kernel: Bluetooth: L2CAP socket layer initialized
Feb 11 22:28:10 roque hcid[3963]: HCI dev 0 up
Feb 11 22:28:10 roque hcid[3963]: Starting security manager 0
Feb 11 22:28:10 roque sdpd[3966]: Bluetooth SDP daemon
Feb 11 22:28:10 roque kernel: Bluetooth: RFCOMM ver 1.5
Feb 11 22:28:10 roque kernel: Bluetooth: RFCOMM socket layer initialized
Feb 11 22:28:10 roque kernel: Bluetooth: RFCOMM TTY layer initialized

I try sending something to my bluetooth phone with:

gnome-obex-send -d XX:YY.... a_friend.vcf
Browsing XX:YY.... ...
Service Name: OBEX Object Push
Service RecHandle: 0x10004
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 9
  "OBEX" (0x0008)
Service Class ID List:
  "OBEX Object Push" (0x1105)
** Message: device XX:YY.... (OBEX Object Push) port 9

And a dialog shows up saying:
  <<Remote device doesn't support receiving objects.>>

In /var/log/messages...
Feb 11 22:28:43 roque hcid[3963]: link_key_request (sba=AA:BB....,
dba=XX:YY....)

Sending _from_ the cell phone to the laptop works.

Feb 11 22:36:27 roque hcid[3963]: link_key_request (sba=AA:BB....,
dba=XX:YY....)

But shouldn't 's' and 'd' change order now?

If I define an rfcomm I can dial by typing
   atd someNumber

Rui

-- 
+ No matter how much you do, you never do enough -- unknown
+ Whatever you do will be insignificant,
| but it is very important that you do it -- Gandhi
+ So let's do it...?

Please AVOID sending me WORD, EXCEL or POWERPOINT attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20050211/3619aa3c/attachment.sig>


More information about the fedora-devel-list mailing list