[Bluez-users] unable to open /dev/rfcomm0: No such device.

["Fahad Khowaja" <fahadkhowaja@hotmail.com>]

Hi! The issue is resolved. For anyone who may be interested in the details, 
it's as follows:

The problem was that the kernel did not recognize character device major 
version 216. It had no drivers for this type of device. I had to configure 
RFCOMM protocol support and RFCOMM TTY support under Bluetooth support in 
the kernel and recompile it. This step added a driver to the kernel and a 
cat of /proc/devices listed "216 rfcomm" as a recognized device.

Not being able to recognize this type of device was also causing ioctl() 
function calls which referred to it to fail. After the drivers were loaded, 
the ioctl() calls worked properly (which were previously giving errors).

Fahad.

_________________________________________________________________
Take advantage of powerful junk e-mail filters built on patented Microsoft® 
SmartScreen Technology. 
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines 
  Start enjoying all the benefits of MSN® Premium right now and get the 
first two months FREE*.



-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users