Re: [Bluez-users] problems using rfcomm device

Marcel Holtmann
2004-11-19T21:51:03Z

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