device not part of a subsystem?

device not part of a subsystem?

[Marco d'Itri]

[-- Attachment #1: Type: text/plain, Size: 393 bytes --]

Is this a bug? The rfcomm driver reports just this:

$ udevinfo -a -p /class/tty/rfcomm0

[...]

device '/sys/class/tty/rfcomm0' has major:minor 216:0
  looking at class device '/sys/class/tty/rfcomm0':
    SYSFS{dev}="216:0"

Should I change my rules files to not depend on the driver being part of
the tty subsystem or ask for the rfcomm driver to be fixed?

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: device not part of a subsystem?

[Kay Sievers]

On Sat, 2005-04-09 at 02:01 +0200, Marco d'Itri wrote:
> Is this a bug? The rfcomm driver reports just this:
> 
> $ udevinfo -a -p /class/tty/rfcomm0
> 
> [...]
> 
> device '/sys/class/tty/rfcomm0' has major:minor 216:0
>   looking at class device '/sys/class/tty/rfcomm0':
>     SYSFS{dev}="216:0"

That looks bad. The subsystem is read from the device path. Don't know
why this isn't working. What udev version is it? Do you use klibc?

How does a "ls -l" in that directory look like?

Is it a bluetooth device?

> Should I change my rules files to not depend on the driver being part of
> the tty subsystem or ask for the rfcomm driver to be fixed?

Hmm, that device should probably have a "device" link? But let's find
the SUBSYSTEM bug first.

Kay



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: device not part of a subsystem?

[Marco d'Itri]

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

On Apr 09, Kay Sievers <kay.sievers@vrfy.org> wrote:

> That looks bad. The subsystem is read from the device path. Don't know
> why this isn't working. What udev version is it? Do you use klibc?
The user reported 056, and the Debian package does not use klibc.

> How does a "ls -l" in that directory look like?
Just the dev file.

> Is it a bluetooth device?
Yes.

Another user just reported that gentoo udev 045 does not report the
subsystem, but my 056 udevinfo binary running on his system does.

A third user reported the same thing happening with fb devices and
the graphics subsystem, an upgrade to 056 fixed the problem.

So I will ask again the first user to double check which version of udev
he is running (I do not use any of these devices).

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: device not part of a subsystem?

[Kay Sievers]

On Sat, 2005-04-09 at 02:29 +0200, Marco d'Itri wrote:
> On Apr 09, Kay Sievers <kay.sievers@vrfy.org> wrote:
> 
> > That looks bad. The subsystem is read from the device path. Don't know
> > why this isn't working. What udev version is it? Do you use klibc?
> The user reported 056, and the Debian package does not use klibc.

I've got my bilt-in bluetooth running for the first time now. I can't
reproduce it here with the latest udev-devel version and kernel 2.6.11.

  [kay@pim ~]$ udevinfo -a -p /sys/class/tty/rfcomm0/
  ...
  device '/sys/class/tty/rfcomm0' has major:minor 216:0
    looking at class device '/sys/class/tty/rfcomm0':
      SUBSYSTEM="tty"
      SYSFS{dev}="216:0"

Kay



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: device not part of a subsystem?

[Marco d'Itri]

[-- Attachment #1: Type: text/plain, Size: 409 bytes --]

On Apr 09, Kay Sievers <kay.sievers@vrfy.org> wrote:

> I've got my bilt-in bluetooth running for the first time now. I can't
> reproduce it here with the latest udev-devel version and kernel 2.6.11.
Indeed, the user cannot either. So now I need to understand why this did
not work for him (I still suspect he was using an older release):

SUBSYSTEM="tty",        GROUP="dialout"

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: device not part of a subsystem?

[Marco d'Itri]

[-- Attachment #1: Type: text/plain, Size: 234 bytes --]

On Apr 09, Marco d'Itri <md@Linux.IT> wrote:

> Indeed, the user cannot either. So now I need to understand why this did
> not work for him (I still suspect he was using an older release):
He confirmed this.

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]