I am migrating from Fedora 8 to CentOS 5.2
I have a usb dvd drive
I added file /etc/udev/rules.d/00-my-custom.rules
BUS=="scsi", SYSFS{vendor}=="TSSTcorp", SYSFS{model}=="CDDVDW SH-S203N
",SYMLINK="dvd",OWNER="rray"
In Fedora 8 this has worked for some time
In CentOS 5.2 it seems to be ignored
This is what udevinfo tells me
looking at device '/block/sr0':
KERNEL=="sr0"
SUBSYSTEM=="block"
SYSFS{stat}==" 0 0 0 0 0 0
0 0 0 0 0"
SYSFS{size}=="4"
SYSFS{removable}=="1"
SYSFS{range}=="1"
SYSFS{dev}=="11:0"
looking at parent device
'/devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.0/host22/target22:0:0/22:0:0:0':
ID=="22:0:0:0"
BUS=="scsi"
DRIVER=="sr"
SYSFS{modalias}=="scsi:t-0x05"
SYSFS{ioerr_cnt}=="0x5"
SYSFS{iodone_cnt}=="0x126"
SYSFS{iorequest_cnt}=="0x126"
SYSFS{iocounterbits}=="32"
SYSFS{timeout}=="0"
SYSFS{state}=="running"
SYSFS{rev}=="LA00"
SYSFS{model}=="CDDVDW SH-S203N "
SYSFS{vendor}=="TSSTcorp"
SYSFS{scsi_level}=="3"
SYSFS{type}=="5"
SYSFS{queue_type}=="none"
SYSFS{queue_depth}=="1"
SYSFS{device_blocked}=="0"
SYSFS{max_sectors}=="240"
I have tried CentOS mailing list but no help
I tried "udevcontrol log_priority=debug" but did not work
I only get basic info in the log file
Jan 22 13:07:52 devl1 kernel: usb 1-6: new high speed USB device using
ehci_hcd and address 22
Jan 22 13:07:52 devl1 kernel: usb 1-6: configuration #1 chosen from 1
choice
Jan 22 13:07:52 devl1 kernel: scsi22 : SCSI emulation for USB Mass Storage
devices
Jan 22 13:07:59 devl1 kernel: Vendor: TSSTcorp Model: CDDVDW SH-S203N
Rev: LA00
Jan 22 13:07:59 devl1 kernel: Type: CD-ROM ANSI SCSI revision: 00
Jan 22 13:07:59 devl1 kernel: sr0: scsi3-mmc drive: 125x/125x writer
dvd-ram cd/rw xa/form2 cdda tray
Jan 22 13:07:59 devl1 kernel: sr 22:0:0:0: Attached scsi generic sg1 type
5
Does udev debug have to be configured in the kernel
Is there a way to "trace" udev to see which rules it is using
Any suggestions appreciated
Richard Ray
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
