Some sysfs attrs have vanished!

Some sysfs attrs have vanished!

[DervishD]

    Hi all :)

    I don't know if I screwed anything while compiling my 2.6.20.14
kernel, and I'm not sure how much time has this been happening because I
removed one of the units and so I removed some bits from my rules file,
so please tell me if I'm doing wrong anything obvious.

    Well, here is the story: I have two DVD recorders, and until I
removed one of them (long story) I had my udev.rules configured to
assign names to them based on $ATTRS{model}. And it worked, I swear. One
of them reports something like "HL-DT-ST" and the other said
"DUW1616/ARR", or something very similar.

    Today I've put again the second recorder and I did run "udevinfo" to
get the model strings (I didn't remember them exactly) and to my
surprise, there's no ATTRS{model}!

    This is what I get:

    $ udevinfo -a -n /dev/hdc

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/block/hdc':
    KERNEL="hdc"
    SUBSYSTEM="block"
    DRIVER=""
    ATTR{stat}="       0        0        0        0        0        0        0        0        0        0        0"
    ATTR{size}="8388604"
    ATTR{removable}="1"
    ATTR{range}="1"
    ATTR{dev}="22:0"

  looking at parent device '/devices/pci0000:00/0000:00:0f.1/ide1/1.0':
    KERNELS="1.0"
    SUBSYSTEMS="ide"
    DRIVERS="ide-cdrom"
    ATTRS{modalias}="ide:m-cdrom"
    ATTRS{drivename}="hdc"
    ATTRS{media}="cdrom"

  looking at parent device '/devices/pci0000:00/0000:00:0f.1/ide1':
    KERNELS="ide1"
    SUBSYSTEMS=""
    DRIVERS=""

  looking at parent device '/devices/pci0000:00/0000:00:0f.1':
    KERNELS="0000:00:0f.1"
    SUBSYSTEMS="pci"
    DRIVERS="VIA_IDE"
    ATTRS{msi_bus}=""
    ATTRS{broken_parity_status}="0"
    ATTRS{modalias}="pci:v00001106d00000571sv0000147Bsd00001416bc01sc01i8a"
    ATTRS{local_cpus}="1"
    ATTRS{irq}="0"
    ATTRS{class}="0x01018a"
    ATTRS{subsystem_device}="0x1416"
    ATTRS{subsystem_vendor}="0x147b"
    ATTRS{device}="0x0571"
    ATTRS{vendor}="0x1106"

  looking at parent device '/devices/pci0000:00':
    KERNELS="pci0000:00"
    SUBSYSTEMS=""
    DRIVERS=""

----------------------------------------------------------

    Exactly the same happens to the other IDE devices, they have stopped
telling $ATTRS{model}, and they did!. Is there anything in the kernel
that I've turned off to suffer this problem? As far as I know, I haven't
removed anything from my configuration in the last three kernel updates,
if I recall correctly. I suspect I'm doing something very obvious and
stupid here but I'm missing the point.

    Sorry for the stupid question, but I'm a bit lost O:) Thanks a lot
in advance.

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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: Some sysfs attrs have vanished!

[Greg KH]

On Sun, Jul 15, 2007 at 10:53:43PM +0200, DervishD wrote:
>     Hi all :)
> 
>     I don't know if I screwed anything while compiling my 2.6.20.14
> kernel, and I'm not sure how much time has this been happening because I
> removed one of the units and so I removed some bits from my rules file,
> so please tell me if I'm doing wrong anything obvious.
> 
>     Well, here is the story: I have two DVD recorders, and until I
> removed one of them (long story) I had my udev.rules configured to
> assign names to them based on $ATTRS{model}. And it worked, I swear. One
> of them reports something like "HL-DT-ST" and the other said
> "DUW1616/ARR", or something very similar.
> 
>     Today I've put again the second recorder and I did run "udevinfo" to
> get the model strings (I didn't remember them exactly) and to my
> surprise, there's no ATTRS{model}!

I would ask on the dvb mailing list, perhaps the driver code changed
somehow to not export this attribute anymore?

thanks,

greg k-h

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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: Some sysfs attrs have vanished!

[DervishD]

    Hi Greg :)

 * Greg KH <greg@kroah.com> dixit:
> On Sun, Jul 15, 2007 at 10:53:43PM +0200, DervishD wrote:
> >     Hi all :)
> > 
> >     I don't know if I screwed anything while compiling my 2.6.20.14
> > kernel, and I'm not sure how much time has this been happening because I
> > removed one of the units and so I removed some bits from my rules file,
> > so please tell me if I'm doing wrong anything obvious.
> > 
> >     Well, here is the story: I have two DVD recorders, and until I
> > removed one of them (long story) I had my udev.rules configured to
> > assign names to them based on $ATTRS{model}. And it worked, I swear. One
> > of them reports something like "HL-DT-ST" and the other said
> > "DUW1616/ARR", or something very similar.
> > 
> >     Today I've put again the second recorder and I did run "udevinfo" to
> > get the model strings (I didn't remember them exactly) and to my
> > surprise, there's no ATTRS{model}!
> 
> I would ask on the dvb mailing list, perhaps the driver code changed
> somehow to not export this attribute anymore?

    Looks like this may be the case, or simply the attribute was never
exported and I just imagined it was. I've tested with Ubuntu kernels
(just to see if it was MY kernel the culprit) and the same happens, so
probably I was entirely wrong about the attribute.

    Thanks a lot for your answer :) imagined it was. I've tested with
Ubuntu kernels (just to see if it was MY kernel the culprit) and the
same happens, so probably I was entirely wrong about the attribute.

    Thanks a lot for your answer :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
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