On Sun, Aug 31, 2008 at 9:37 PM, Mikkel L. Ellertson
<mikkel(a)infinity-ltd.com> wrote:
>>> When I try to open the DVD burner tray with the command
eject, I get
>>> the following problem:
>>>
>>> $ eject
>>> eject: unable to find or open device for: `cdrom'
>>> $
>>>
>>> Any ideas?
>>>
>> Missing the /dev/cdrom symlink. Depending on hardware changes, you
>> may only have /dev/cdrom0 and /dev/cdrom1, but no /dev/cdrom.
>
> Thanks, Mikkel, but
>
> $ eject /dev/cdrom0
> eject: unable to find or open device for: `/dev/cdrom0'
> $ eject /dev/cdrom1
> eject: unable to find or open device for: `/dev/cdrom1'
> $ eject /dev/cdrom2
> eject: unable to find or open device for: `/dev/cdrom2'
> $
>
> Any further ideas?
>
Does "ls /dev/cdrom*" produce anything?
You may also want to take a look at
/etc/udev/rules.d/70-persistent-cd.rules - this is where the
symlinks are created.
Results:
# ls /dev/cdrom*
ls: cannot access /dev/cdrom*: No such file or directory
#
and
# more /etc/udev/rules.d/70-persistent-cd.rules
# This file was automatically generated by the /lib/udev/write_cd_rules
# program, probably 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.
# DVD_RW_ND-3520A (pci-0000:04:06.0-scsi-0:0:1:0)
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:04:06.0-scsi-0:0:1:0",
SYMLINK+="cdrom", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:04:06.0-scsi-0:0:1:0",
SYMLINK+="cdrw", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:04:06.0-scsi-0:0:1:0",
SYMLINK+="dvd", ENV{GENERATED}="1"
ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:04:06.0-scsi-0:0:1:0",
SYMLINK+="dvdrw", ENV{GENERATED}="1"
#
Paul