public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] rfcomm broken in RHEL-WS-3 kernel 2.4.21
Date: Mon, 18 Sep 2006 23:42:28 +0200	[thread overview]
Message-ID: <1158615748.25125.28.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.10.10609181354210.8015-100000@froya.boat.washington.edu>

Hi Billy,

> I've installed the bluez RPMs that I saw on rpmfind for Red Hat
> Enterprise 3, which are bluez-libs-2.10-1.1.el3.rf.i386.rpm,
> bluez-utils-2.9-1.1.fc3.rf.i386.rpm and
> bluez-bluefw-1.0-1.rhel3.dag.i386.rpm.  These did not enable
> rfcomm nor install /dev/rfcomm*.  The rfcomm executable always
> reports, "Can't open RFCOMM control socket: Address family not
> supported by protocol."

this basically means that the RFCOMM kernel module is not loaded. You
might wanna check with lsmod.

> I then tried installing bluez-libs and bluez-utils from their
> tarballs.  This changed nothing; /dev/rfcomm* still isn't there
> and I still get the same error from the rfcomm executable.

For a 2.4 kernel, you need to create the /dev/rfcommX device nodes by
yourself.

> My machine is RHEL-WS-3, kernel 2.4.21-32.0.1.ELsmp.  I use
> whatever kernel rpm up2date gives and I don't compile kernels
> myself anymore.
> 
> I got pretty much identical results from a second machine which
> also runs Red Hat Enterprise Workstation 3 and kernel 2.4.15.

The 2.4.15 was never supported by RHEL3 and also doesn't include support
for the RFCOMM kernel module at all.

> There were a few clues on this list's archives and elsewhere
> that I should add these lines to /etc/modules.conf:
> 
> alias net-pf-31 bluez
> alias bt-proto-0 l2cap
> alias bt-proto-2 sco
> alias bt-proto-3 rfcomm
> 
> Adding these didn't change anything.  Also, modprobe rfcomm
> reports, "Can't locate module rfcomm".
> 
> So what should I do about the broken rfcomm?  I hope to use a
> USB bluetooth dongle to send faxes through my cellphone.

The RHEL3 kernel config shows me that a RFCOMM module should be there,
but I haven't check an actual RHEL3 installation right now. Take a look
at your /lib/modules directory.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2006-09-18 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18 21:05 [Bluez-users] rfcomm broken in RHEL-WS-3 kernel 2.4.21 William Kreuter
2006-09-18 21:42 ` Marcel Holtmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1158615748.25125.28.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox