[Debburn-devel] udev link vanishes if burn programs load the drive tray on Debian 6.0.2 amd64

[Thomas Schmitt]

Hi,

Nicolas George wrote:
> Can you show the udev rules that are leading to this situation? I had a
> similar problem some time ago, and the cause was that the udev rules were
> reacting to the "add" events but not the "change" events.

-----------------------------------------------------------------------------
/etc/udev/rules.d/70-persistent-cd.rules
-----------------------------------------------------------------------------
# This file was automatically generated by the /lib/udev/write_cd_rules
# program, run by the cd-aliases-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and set the $GENERATED variable.

# CDDVDW_SH-S223B (pci-0000:00:11.0-scsi-2:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-2:0:0:0", SYMLINK+="cdrom", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-2:0:0:0", SYMLINK+="cdrw", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-2:0:0:0", SYMLINK+="dvd", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-2:0:0:0", SYMLINK+="dvdrw", ENV{GENERATED}="1"

# DVD-ROM_SH-D162C (pci-0000:00:14.1-scsi-0:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:14.1-scsi-0:0:0:0", SYMLINK+="cdrom1", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:14.1-scsi-0:0:0:0", SYMLINK+="dvd1", ENV{GENERATED}="1"

# BDDVDRW_GGC-H20L (pci-0000:00:12.2-usb-0:1:1.0-scsi-0:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:12.2-usb-0:1:1.0-scsi-0:0:0:0", SYMLINK+="cdrom2", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:12.2-usb-0:1:1.0-scsi-0:0:0:0", SYMLINK+="cdrw2", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:12.2-usb-0:1:1.0-scsi-0:0:0:0", SYMLINK+="dvd2", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:12.2-usb-0:1:1.0-scsi-0:0:0:0", SYMLINK+="dvdrw2", ENV{GENERATED}="1"

# BDDVDRW_GGC-H20L (pci-0000:00:12.2-usb-0:1:1.0-scsi-0:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="HL-DT-ST_BDDVDRW_GGC-H20L_55C886416162-0:0", SYMLINK+="cdrom3", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="HL-DT-ST_BDDVDRW_GGC-H20L_55C886416162-0:0", SYMLINK+="cdrw3", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="HL-DT-ST_BDDVDRW_GGC-H20L_55C886416162-0:0", SYMLINK+="dvd3", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="HL-DT-ST_BDDVDRW_GGC-H20L_55C886416162-0:0", SYMLINK+="dvdrw3", ENV{GENERATED}="1"

# Cruzer (pci-0000:00:12.2-usb-0:3.2:1.0-scsi-0:0:0:1)
# SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="SanDisk_Cruzer_0164620760128686-0:1", NAME="sr9", SYMLINK+="cd_cruzer", ENV{GENERATED}="0"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="SanDisk_Cruzer_0164620760128686-0:1", SYMLINK+="cd_cruzer", ENV{GENERATED}="0"

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

Currently only "CDDVDW_SH-S223B" and "DVD-ROM_SH-D162C" are attached.


The effect is somewhat volatile. Yesterday it was difficult to reproduce,
today it is present since booting. It needs a DVD+RW in the tray.
Empty tray or a CD-RW heal it until i reboot or until i use xorriso
to burn a session after loading the tray by itself.


Have a nice day :)

Thomas