© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
So, the <sysfs-attributes> element is simply missing :(
Not such a huge problem, but bad nevertheless: This data is used only to get the SCI vendor and model name. We can _probably_ find this data for SCSI block devices in the udevadm output, but not for SCSI scanners (and mostly likely also other non-block SCSI devices, like the "robot part" of tape libraries). The following is that part of the output of "udevadm info --export-db" (that's the content of the <udev> node in the submitted data) for an Adaptec 1480A SCSI adapter and Sharp JX250 scanner connected to the adapter:
P: /devices/
E: UDEV_LOG=3
E: DEVPATH=
E: SUBSYSTEM=scsi
E: DEVTYPE=scsi_host
P: /devices/
E: UDEV_LOG=3
E: DEVPATH=
E: SUBSYSTEM=scsi_host
P: /devices/
E: UDEV_LOG=3
E: DEVPATH=
E: SUBSYSTEM=spi_host
P: /devices/
E: UDEV_LOG=3
E: DEVPATH=
E: SUBSYSTEM=scsi
E: DEVTYPE=scsi_target
P: /devices/
E: UDEV_LOG=3
E: DEVPATH=
E: SUBSYSTEM=scsi
E: DEVTYPE=scsi_device
E: MODALIAS=
P: /devices/
N: bsg/5:0:6:0
S: char/253:2
E: UDEV_LOG=3
E: DEVPATH=
E: SUBSYSTEM=bsg
E: DEVNAME=
E: MAJOR=253
E: MINOR=2
E: DEVLINKS=
P: /devices/
E: UDEV_LOG=3
E: DEVPATH=
E: SUBSYSTEM=
P: /devices/
N: sg2
S: char/21:2
E: UDEV_LOG=3
E: DEVPATH=
E: SUBSYSTEM=
E: DEVNAME=/dev/sg2
E: MAJOR=21
E: MINOR=2
E: DEVLINKS=
No trace of the strings "SHARP" or "JX250"....