Bug 101075 - Bluetooth operation fails because no RFCOMM devices in /dev
Summary: Bluetooth operation fails because no RFCOMM devices in /dev
Status: CLOSED DUPLICATE of bug 88802
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: MAKEDEV
Version: beta1
Hardware: athlon
OS: Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Brock Organ
Depends On:
Blocks: CambridgeTarget
TreeView+ depends on / blocked
Reported: 2003-07-28 22:11 UTC by Ryan Muldoon
Modified: 2007-04-18 16:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-21 18:57:49 UTC

Attachments (Terms of Use)

Description Ryan Muldoon 2003-07-28 22:11:47 UTC
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):

How reproducible:

Steps to Reproduce:
1./etc/rc.d/init.d/bluetooth restart


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.

Additional info:

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:

Comment 1 Bastien Nocera 2004-06-01 10:18:07 UTC

*** This bug has been marked as a duplicate of 88802 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:57:49 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.