[Bluez-users] problems using rfcomm device

[Bluez-users] problems using rfcomm device

[Kai Haberzettl]

Trying to get bluetooth running under Debian Testing here. Connecting
to my device (Nokia 6600 cell) works fine, but whenever I try to
access the device using pppd or minicom I get something like this:

Nov 19 06:18:01 arthur pppd[1382]: Failed to open /dev/rfcomm0:
Invalid argument

Yes, I did see the FAQ, but the rfcomm connect doesn't help either.

Here's what I do have working:

arthur:/home/khaberz# rfcomm show
rfcomm0: 00:0E:6D:56:44:FA channel 0 clean


arthur:/home/khaberz# hciconfig -a 
hci0:   Type: USB
        BD Address: 00:0F:3D:5F:6C:FD ACL MTU: 192:8  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN 
        RX bytes:99 acl:0 sco:0 events:13 errors:0
        TX bytes:296 acl:0 sco:0 commands:12 errors:0
        Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT 
        Name: 'arthur-0'
        Class: 0x000100
        Service Classes: Unspecified
        Device Class: Computer, Uncategorized
        HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP
        Subver: 0x20d
        Manufacturer: Cambridge Silicon Radio (10)


Any help is greatly appreciated.

Thanks,
Kai



-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problems using rfcomm device

[Marcel Holtmann]

Hi Kai,

> Trying to get bluetooth running under Debian Testing here. Connecting
> to my device (Nokia 6600 cell) works fine, but whenever I try to
> access the device using pppd or minicom I get something like this:
> 
> Nov 19 06:18:01 arthur pppd[1382]: Failed to open /dev/rfcomm0:
> Invalid argument

run "hcidump -X" as root and see what happens.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problems using rfcomm device

[Kai Haberzettl]

Marcel Holtmann <marcel@holtmann.org> writes:

> Hi Kai,
>
>> Trying to get bluetooth running under Debian Testing here. Connecting
>> to my device (Nokia 6600 cell) works fine, but whenever I try to
>> access the device using pppd or minicom I get something like this:
>> 
>> Nov 19 06:18:01 arthur pppd[1382]: Failed to open /dev/rfcomm0:
>> Invalid argument
>
> run "hcidump -X" as root and see what happens.

arthur:/home/khaberz# hcidump -X
HCIDump - HCI packet analyzer ver 1.12
device: hci0 snap_len: 1028 filter: 0xffffffff

...and that's it, even if I try to connect with pppd.

Thanks,
Kai


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problems using rfcomm device

[Marcel Holtmann]

Hi Kai,

> >> Trying to get bluetooth running under Debian Testing here. Connecting
> >> to my device (Nokia 6600 cell) works fine, but whenever I try to
> >> access the device using pppd or minicom I get something like this:
> >> 
> >> Nov 19 06:18:01 arthur pppd[1382]: Failed to open /dev/rfcomm0:
> >> Invalid argument
> >
> > run "hcidump -X" as root and see what happens.
> 
> arthur:/home/khaberz# hcidump -X
> HCIDump - HCI packet analyzer ver 1.12
> device: hci0 snap_len: 1028 filter: 0xffffffff
> 
> ...and that's it, even if I try to connect with pppd.

I overlooked your real mistake. You set the channel to the value 0 for
the /dev/rfcomm0 and this is not a valid one. Use 1 for the channel
number.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problems using rfcomm device

[Kai Haberzettl]

Marcel Holtmann <marcel@holtmann.org> writes:

>> >> Trying to get bluetooth running under Debian Testing here. Connecting
>> >> to my device (Nokia 6600 cell) works fine, but whenever I try to
>> >> access the device using pppd or minicom I get something like this:
>> >> 
>> >> Nov 19 06:18:01 arthur pppd[1382]: Failed to open /dev/rfcomm0:
>> >> Invalid argument
>> >
>> > run "hcidump -X" as root and see what happens.
>> 
>> arthur:/home/khaberz# hcidump -X
>> HCIDump - HCI packet analyzer ver 1.12
>> device: hci0 snap_len: 1028 filter: 0xffffffff
>> 
>> ...and that's it, even if I try to connect with pppd.
>
> I overlooked your real mistake. You set the channel to the value 0 for
> the /dev/rfcomm0 and this is not a valid one. Use 1 for the channel
> number.

That was it. Thanks a lot!

Cheers,
Kai


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problems using rfcomm device

[Kai Haberzettl]

Kai Haberzettl <kai@khaberz.net> writes:

> That was it. Thanks a lot!

Well. Almost. I got further. The PIN authentication worked and the key
is saved in /etc/bluetooth. However, minicom and pppd still don't
quite work. Here's what I get from minicom:

arthur:/home/khaberz# minicom
minicom: cannot open /dev/rfcomm0: No such file or directory

It's there of course:

arthur:/home/khaberz# ls -l /dev/rfcomm0
crw-rw----  1 root dialout 216, 0 Nov 18 19:48 /dev/rfcomm0

This is in the syslog:

Nov 19 18:11:38 arthur kernel: hci_cmd_task: hci0 command tx timeout

The output of hcidump -X while starting minicom is attached.

Thanks!
Kai

===File ~/bluez.txt=========================================
HCIDump - HCI packet analyzer ver 1.12
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
  0000: fa 44 56 6d 0e 00 18 cc  02 00 00 00 01           .DVm.........
> HCI Event: Command Status (0x0f) plen 4
  0000: 00 01 05 04                                       ....
> HCI Event: Connect Complete (0x03) plen 11
  0000: 00 29 00 fa 44 56 6d 0e  00 01 00                 .)..DVm....
< ACL data: handle 0x0029 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
  0000: 29 00 0f 00                                       )...
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 29 00 01 00                                    .)...
> HCI Event: Command Complete (0x0e) plen 6
  0000: 01 0d 08 00 29 00                                 ....).
> HCI Event: Max Slots Change (0x1b) plen 3
  0000: 29 00 05                                          )..
> ACL data: handle 0x0029 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0085 scid 0x0040 result 1 status 2
> ACL data: handle 0x0029 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0085 scid 0x0040 result 0 status 0
< ACL data: handle 0x0029 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0085 flags 0x0000 clen 4
    MTU 1024 
> HCI Event: QoS Setup Complete (0x0d) plen 21
  0000: 00 29 00 00 01 00 00 00  00 00 00 00 00 88 13 00  .)..............
  0010: 00 ff ff ff ff                                    .....
> ACL data: handle 0x0029 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0
< ACL data: handle 0x0029 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0085 flags 0x0000 result 0 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 29 00 01 00                                    .)...
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 29 00 01 00                                    .)...
> ACL data: handle 0x0029 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 4
    MTU 672 
< ACL data: handle 0x0029 flags 0x02 dlen 8
    L2CAP(d): cid 0x0085 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c 
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 29 00 01 00                                    .)...
> ACL data: handle 0x0029 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 
< ACL data: handle 0x0029 flags 0x02 dlen 18
    L2CAP(d): cid 0x0085 len 14 [psm 3]
      RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
      dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0
      frame_size 667 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 29 00 01 00                                    .)...
> ACL data: handle 0x0029 flags 0x02 dlen 18
    L2CAP(d): cid 0x0040 len 14 [psm 3]
      RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
      dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0
      frame_size 667 max_retrans 0 credits 3
< ACL data: handle 0x0029 flags 0x02 dlen 8
    L2CAP(d): cid 0x0085 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59 
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 29 00 01 00                                    .)...
< ACL data: handle 0x0029 flags 0x02 dlen 8
    L2CAP(d): cid 0x0085 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 2 pf 1 ilen 0 fcs 0xb8 
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 29 00 01 00                                    .)...
> ACL data: handle 0x0029 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92 
< ACL data: handle 0x0029 flags 0x02 dlen 8
    L2CAP(d): cid 0x0085 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd 
< ACL data: handle 0x0029 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0085 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 29 00 01 00                                    .)...
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 29 00 01 00                                    .)...
> ACL data: handle 0x0029 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 
> ACL data: handle 0x0029 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0085 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
  0000: 29 00 13                                          )..
> HCI Event: Command Status (0x0f) plen 4
  0000: 00 01 06 04                                       ....
> HCI Event: Disconn Complete (0x05) plen 4
  0000: 00 29 00 16                                       .)..
============================================================


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problems using rfcomm device

[Marcel Holtmann]

Hi Kai,

> > That was it. Thanks a lot!
> 
> Well. Almost. I got further. The PIN authentication worked and the key
> is saved in /etc/bluetooth. However, minicom and pppd still don't
> quite work. Here's what I get from minicom:
> 
> arthur:/home/khaberz# minicom
> minicom: cannot open /dev/rfcomm0: No such file or directory
> 
> It's there of course:
> 
> arthur:/home/khaberz# ls -l /dev/rfcomm0
> crw-rw----  1 root dialout 216, 0 Nov 18 19:48 /dev/rfcomm0

does it work when you do a "cat /dev/rfcomm0" first?

> This is in the syslog:
> 
> Nov 19 18:11:38 arthur kernel: hci_cmd_task: hci0 command tx timeout

Actually this is bad and should not happen. What kind of USB host
controller do you use?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problems using rfcomm device

[Kai Haberzettl]

Marcel Holtmann <marcel@holtmann.org> writes:

>> arthur:/home/khaberz# minicom
>> minicom: cannot open /dev/rfcomm0: No such file or directory
>> 
>> It's there of course:
>> 
>> arthur:/home/khaberz# ls -l /dev/rfcomm0
>> crw-rw----  1 root dialout 216, 0 Nov 18 19:48 /dev/rfcomm0
>
> does it work when you do a "cat /dev/rfcomm0" first?

Nope. I'm being asked for the PIN on the phone initially, but then it
still says 'No such file or directory'

>> Nov 19 18:11:38 arthur kernel: hci_cmd_task: hci0 command tx timeout
>
> Actually this is bad and should not happen. What kind of USB host
> controller do you use?

arthur:/home/khaberz# dmesg | grep usb
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-ohci.c: USB OHCI at membase 0xc6076000, IRQ 11
usb-ohci.c: usb-00:0b.0, NEC Corporation USB
usb.c: new USB bus registered, assigned bus number 1
prism2usb_init: prism2_usb.o: 0.2.1-pre21 Loaded
prism2usb_init: dev_info is: prism2_usb
usb.c: registered new driver prism2_usb
usb.c: USB device 2 (vend/prod 0xa12/0x1) is not claimed by any active
driver.
usb.c: registered new driver hci_usb
usb.c: USB disconnect on device 00:0b.0-1 address 2

Thanks,
Kai


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] problems using rfcomm device

[Marcel Holtmann]

Hi Kai,

> >> arthur:/home/khaberz# minicom
> >> minicom: cannot open /dev/rfcomm0: No such file or directory
> >> 
> >> It's there of course:
> >> 
> >> arthur:/home/khaberz# ls -l /dev/rfcomm0
> >> crw-rw----  1 root dialout 216, 0 Nov 18 19:48 /dev/rfcomm0
> >
> > does it work when you do a "cat /dev/rfcomm0" first?
> 
> Nope. I'm being asked for the PIN on the phone initially, but then it
> still says 'No such file or directory'

unbind the RFCOMM binding and use "rfcomm connect ..." and then try
again with minicom. I have seen problems with minicom, but never really
got the reason why only minicom is failing.

> >> Nov 19 18:11:38 arthur kernel: hci_cmd_task: hci0 command tx timeout
> >
> > Actually this is bad and should not happen. What kind of USB host
> > controller do you use?
> 
> arthur:/home/khaberz# dmesg | grep usb
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> usb-ohci.c: USB OHCI at membase 0xc6076000, IRQ 11
> usb-ohci.c: usb-00:0b.0, NEC Corporation USB
> usb.c: new USB bus registered, assigned bus number 1
> prism2usb_init: prism2_usb.o: 0.2.1-pre21 Loaded
> prism2usb_init: dev_info is: prism2_usb
> usb.c: registered new driver prism2_usb
> usb.c: USB device 2 (vend/prod 0xa12/0x1) is not claimed by any active
> driver.
> usb.c: registered new driver hci_usb
> usb.c: USB disconnect on device 00:0b.0-1 address 2

Is this the latest 2.6.10-rc2-bk kernel? If not, then update it.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users