Red Hat Bugzilla – Bug 101075
Bluetooth operation fails because no RFCOMM devices in /dev
Last modified: 2007-04-18 12:56:16 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686) Gecko/20030530 Galeon/1.3.5
Description of problem:
I could not get the "rfcomm" utility that comes with bluez-utils with Severn
because there were no "rfcomm0" or "rfcomm1". I created these devices using:
mknod rfcomm0 c 216 0 && mknod rfcomm1 c 216 1
which allowed RFCOMM to work, so I could then use the OBEX utilities.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: This resulted in an RFCOMM failure: No file or Directory Found
(because there were no rfcomm devices in /dev)
Expected Results: RFCOMM should have worked properly so my bluetooth adapter
could send files back and forth to my phone.
In general, I followed the advice of
and was able to get my bluetooth phone to talk to Severn. It would be great if
these steps were taken to work by default. (Like the various kernel modules
being loaded on the presence of a bluetooth adapter...)
Finally, Bluetooth could be a lot easier for normal users if the GNOME-Bluetooth
programs were included by default. These can be found here:
*** This bug has been marked as a duplicate of 88802 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.