Your message dated Sat, 18 Nov 2006 15:31:41 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#398696: udevinfo don't show ID_TYPE field of pcmcia cdrom
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: udev
Version: 0.100-2.2
Hi,
As informed in #398305, D-I had some trouble recognizing my pcmcia
cd-rom during installation.
Digging a little bit more, I found that the symlink was correct in
/dev/cdroms/, but the "list-devices" script was not able to find it.
The problem is that "udevinfo -q env -p /block/hde" (from the
list-devices script) don't return an ID_TYPE field as expected.
So, with the system already installed, I tried out the following commands:
# udevinfo -q all -p /block/hde
P: /block/hde
N: hde
S: cdrom
E: ID_CDROM=1
E: ID_CDROM_MRW=1
E: ID_CDROM_MRW_W=1
E: GENERATED=1
(Please note that this very same command from d-i didn't show any Env
field, only Path, Name and Symlink. This is the output from the
installed system).
# udevtest /block/hde
This program is for debugging only, it does not create any node,
or run any program specified by a RUN key. It may show incorrect results,
if rules match against subsystem specfic kernel event variables.
main: looking at device '/block/hde' from subsystem 'block'
run_program: 'cdrom_id --export /dev/.tmp-33-0'
run_program: '/lib/udev/cdrom_id' (stdout) 'ID_CDROM=1'
run_program: '/lib/udev/cdrom_id' (stdout) 'ID_CDROM_MRW=1'
run_program: '/lib/udev/cdrom_id' (stdout) 'ID_CDROM_MRW_W=1'
run_program: '/lib/udev/cdrom_id' returned with status 0
udev_rules_get_name: add symlink 'cdrom'
udev_rules_get_name: no node name set, will use kernel name 'hde'
udev_device_event: device '/block/hde' already in database, validate
currently present symlinks
udev_node_add: creating device node '/dev/hde', major = '33', minor =
'0', mode = '0660', uid = '0', gid = '24'
udev_node_add: creating symlink '/dev/cdrom' to 'hde'
main: run: 'socket:/org/kernel/udev/monitor'
main: run: '/etc/init.d/hdparm hotplug'
I also ran the "ata_id" program from the "extras" directory of the
udev sources. Interestenly, it showed the "ID_TYPE" field:
# ./ata_id --export /dev/hde
ID_TYPE=cd
ID_MODEL=TOSHIBA_CD-ROM_XM-7002Bc
ID_SERIAL=
ID_REVISION=1910
ID_BUS=ata
If there's something you want me to try in order to help, I'll be glad to.
Thanks,
Dario.-
--- End Message ---
--- Begin Message ---
On Nov 15, Dario Rapisardi <[EMAIL PROTECTED]> wrote:
> The problem is that "udevinfo -q env -p /block/hde" (from the
> list-devices script) don't return an ID_TYPE field as expected.
By design, ata_id is not run on removable devices:
KERNEL=="hd*[0-9]", ATTRS{removable}=="1", \
GOTO="no_volume_id"
This is probably not going to change any time soon since probing some
removable devices this way has ugly side effects.
I would argue that the real bug is in list-devices, which should check
for $ID_CDROM and not $ID_TYPE=cd.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
