linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: DervishD <udev@dervishd.net>
To: linux-hotplug@vger.kernel.org
Subject: Some sysfs attrs have vanished!
Date: Sun, 15 Jul 2007 20:53:43 +0000	[thread overview]
Message-ID: <20070715205343.GA18557@DervishD> (raw)

    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

             reply	other threads:[~2007-07-15 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-15 20:53 DervishD [this message]
2007-07-21  1:08 ` Some sysfs attrs have vanished! Greg KH
2007-07-23  6:42 ` DervishD

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=20070715205343.GA18557@DervishD \
    --to=udev@dervishd.net \
    --cc=linux-hotplug@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).