[Bluez-users] bluez udev rules for Slackware 10.2

[Bluez-users] bluez udev rules for Slackware 10.2

[Aaron Miller]

[-- Attachment #1.1: Type: text/plain, Size: 1567 bytes --]

Hello,

First off I have to say I am somewhat of a Linux newbie so I apologize if
this question may seem obvious.

I am trying to get bluetooth working on my Slackware 10.2 and udev does not
seem to be creating any devices for my usb dongle. When I searched google,
all I found in regards to the topic was a recent patch which added some new
files to the source for udev rules.

So I downloaded bluez from the cvs (05/31/2006) and also dbus-0.61 since the
./configure was complaining about missing the headers. After installing
bluez-libs I built bluez-utils as so:

./configure --prefix=/usr/local --sysconfdir=/etc --localstatedir=/var
--enable-all
make
make install DESTDIR=<temporary build directory>

>>From there I went to my build directory and changed the init script to the
Slackware standard (<BuildDIr>/etc/rc.d/rc.bluetooth) and modified the file
a bit to reflect these changes. I then proceeded to build into a
slack-package and installed it to my system.

Now I can run 'sh /etc/rc.d/rc.bluetooth start' just fine and get the
following output:
Starting Bluetooth subsystem: hcid sdpd hidd hid2hci rfcomm.

But still no device from udev.

I didn't see any of the files in the source directory this
patch<http://lists.pld-linux.org/mailman/pipermail/pld-cvs-commit/Week-of-Mon-20060515/105676.html>refers
to, nor did I see any udev rules in my build directory. Did I miss a
step somewhere?

Sorry this is so long, I wans't sure what information was needed so I tried
to be as descriptive as possible.

Thank you for taking the time to read this.
...aaron

[-- Attachment #1.2: Type: text/html, Size: 1682 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] bluez udev rules for Slackware 10.2

[Marcel Holtmann]

Hi Aaron,

> First off I have to say I am somewhat of a Linux newbie so I apologize
> if this question may seem obvious.
> 
> I am trying to get bluetooth working on my Slackware 10.2 and udev
> does not seem to be creating any devices for my usb dongle. When I
> searched google, all I found in regards to the topic was a recent
> patch which added some new files to the source for udev rules. 
> 
> So I downloaded bluez from the cvs (05/31/2006) and also dbus-0.61
> since the ./configure was complaining about missing the headers. After
> installing bluez-libs I built bluez-utils as so:
> 
> ./configure --prefix=/usr/local --sysconfdir=/etc --localstatedir=/var
> --enable-all 
> make
> make install DESTDIR=<temporary build directory>
> 
> From there I went to my build directory and changed the init script to
> the Slackware standard (<BuildDIr>/etc/rc.d/rc.bluetooth) and modified
> the file a bit to reflect these changes. I then proceeded to build
> into a slack-package and installed it to my system. 
> 
> Now I can run 'sh /etc/rc.d/rc.bluetooth start' just fine and get the
> following output:
> Starting Bluetooth subsystem: hcid sdpd hidd hid2hci rfcomm.
> 
> But still no device from udev. 

the Bluetooth subsystem doesn't need any device nodes (except for the
RFCOMM TTY emulation). It will simply work and "hciconfig -a" should
show your Bluetooth device.

Regards

Marcel




_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] bluez udev rules for Slackware 10.2

[Aaron Miller]

[-- Attachment #1.1: Type: text/plain, Size: 2432 bytes --]

Thanks for the reply Marcel.

 I'm sorry I wasn't more specific, I didn't realize that there were other
devices then the rfcomm tty device node. This is actually the on I am after
sense it is needed for my device to work with p3nfs.

I have RFCOMM protocol support enabled in the kernel as a modules, and
RFCOMM TTY support hard coded. I had to 'modprobe rfcomm' but the bluetooth
module loaded automatically, both of which are listed in my 'lsmod'. How do
I get udev to create the rfcomm device node? I searched for files containing
"rfcomm" in the bluez build directory but didn't see anything relating to
udev rules. Am I supposed to build this node myself or should udev be
creating it automatically?

Thanks for the help!
...aaron

On 6/3/06, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Aaron,
>
> > First off I have to say I am somewhat of a Linux newbie so I apologize
> > if this question may seem obvious.
> >
> > I am trying to get bluetooth working on my Slackware 10.2 and udev
> > does not seem to be creating any devices for my usb dongle. When I
> > searched google, all I found in regards to the topic was a recent
> > patch which added some new files to the source for udev rules.
> >
> > So I downloaded bluez from the cvs (05/31/2006) and also dbus-0.61
> > since the ./configure was complaining about missing the headers. After
> > installing bluez-libs I built bluez-utils as so:
> >
> > ./configure --prefix=/usr/local --sysconfdir=/etc --localstatedir=/var
> > --enable-all
> > make
> > make install DESTDIR=<temporary build directory>
> >
> > From there I went to my build directory and changed the init script to
> > the Slackware standard (<BuildDIr>/etc/rc.d/rc.bluetooth) and modified
> > the file a bit to reflect these changes. I then proceeded to build
> > into a slack-package and installed it to my system.
> >
> > Now I can run 'sh /etc/rc.d/rc.bluetooth start' just fine and get the
> > following output:
> > Starting Bluetooth subsystem: hcid sdpd hidd hid2hci rfcomm.
> >
> > But still no device from udev.
>
> the Bluetooth subsystem doesn't need any device nodes (except for the
> RFCOMM TTY emulation). It will simply work and "hciconfig -a" should
> show your Bluetooth device.
>
> Regards
>
> Marcel
>
>
>
>
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>

[-- Attachment #1.2: Type: text/html, Size: 3032 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] bluez udev rules for Slackware 10.2

[Marcel Holtmann]

Hi Aaron,

>  I'm sorry I wasn't more specific, I didn't realize that there were
> other devices then the rfcomm tty device node. This is actually the on
> I am after sense it is needed for my device to work with p3nfs. 
> 
> I have RFCOMM protocol support enabled in the kernel as a modules, and
> RFCOMM TTY support hard coded. I had to 'modprobe rfcomm' but the
> bluetooth module loaded automatically, both of which are listed in my
> 'lsmod'. How do I get udev to create the rfcomm device node? I
> searched for files containing "rfcomm" in the bluez build directory
> but didn't see anything relating to udev rules. Am I supposed to build
> this node myself or should udev be creating it automatically? 

you will see these device nodes if you bind or connect a RFCOMM TTY to a
remote device. See the rfcomm command for more details.

Regards

Marcel




_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] bluez udev rules for Slackware 10.2

[Aaron Miller]

[-- Attachment #1.1: Type: text/plain, Size: 1544 bytes --]

<smacks myself on head>
Reading the rfcomm man page was actually what sent me on this long quest to
create an rfcomm device. I misunderstood 'rfcomm bind <dev>' to mean that I
had to supply it with the device that already existed. After your comments,
and rereading the man page, I see that <dev> is the device I want to create,
not the one that is already there. All is good now.

Thanks for your help!
...aaron

On 6/3/06, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Aaron,
>
> >  I'm sorry I wasn't more specific, I didn't realize that there were
> > other devices then the rfcomm tty device node. This is actually the on
> > I am after sense it is needed for my device to work with p3nfs.
> >
> > I have RFCOMM protocol support enabled in the kernel as a modules, and
> > RFCOMM TTY support hard coded. I had to 'modprobe rfcomm' but the
> > bluetooth module loaded automatically, both of which are listed in my
> > 'lsmod'. How do I get udev to create the rfcomm device node? I
> > searched for files containing "rfcomm" in the bluez build directory
> > but didn't see anything relating to udev rules. Am I supposed to build
> > this node myself or should udev be creating it automatically?
>
> you will see these device nodes if you bind or connect a RFCOMM TTY to a
> remote device. See the rfcomm command for more details.
>
> Regards
>
> Marcel
>
>
>
>
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>

[-- Attachment #1.2: Type: text/html, Size: 2109 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users