|
Bugzilla – Full Text Bug Listing |
| Summary: | eject doesn't work - /dev/{cdrecorder,cdrom} missing | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Andreas Kleen <ak> |
| Component: | YaST2 | Assignee: | Kay Sievers <kasievers> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | logs | ||
Please attach the yast logs, a seperate `hwinfo --cdrom' would also be nice. Thanks. It has nothing to do with yast. Wrong, the rule to create /dev/cdrom is maintained by Yast. If /dev/sr0 is there but /dev/cdrom is not, Yast needs to setup the rule to create the symlink. Yes, and this did not work, so the logfiles should be of use here - maby YaST was just confused about the SATA device. Created attachment 69340 [details]
logs
Reassigning to Thomas. I checked some other beta3 systems and only the one with the SATA CD/RW has this problem *** Bug 153691 has been marked as a duplicate of this bug. *** Here is another machine where udev does not seem to create the symlinks in /etc/udev/rules.d/65-cdrom.rules What does: udevtest /block/sr0 print? # udevtest /block/sr0 main: looking at device '/block/sr0' from subsystem 'block' run_program: '/sbin/usb_id -x' run_program: '/sbin/usb_id' returned with status 1 run_program: '/sbin/scsi_id -g -x -s /block/sr0 -d /dev/.tmp-11-0' run_program: '/sbin/scsi_id' returned with status 1 run_program: '/sbin/scsi_id -g -x -a -s /block/sr0 -d /dev/.tmp-11-0' run_program: '/sbin/scsi_id' (stdout) 'ID_VENDOR=PLEXTOR' run_program: '/sbin/scsi_id' (stdout) 'ID_MODEL=DVDR_PX-712A' run_program: '/sbin/scsi_id' (stdout) 'ID_REVISION=1.05' run_program: '/sbin/scsi_id' (stdout) 'ID_SERIAL=' run_program: '/sbin/scsi_id' (stdout) 'ID_TYPE=cd' run_program: '/sbin/scsi_id' (stdout) 'ID_BUS=scsi' run_program: '/sbin/scsi_id' returned with status 0 run_program: '/sbin/path_id /block/sr0' run_program: '/sbin/path_id' (stdout) 'ID_PATH=pci-0000:00:1f.2-scsi-1:0:1:0' run_program: '/sbin/path_id' returned with status 0 udev_rules_get_name: add symlink 'disk/by-path/pci-0000:00:1f.2-scsi-1:0:1:0' udev_rules_get_name: add symlink 'cdrom' udev_rules_get_name: no node name set, will use kernel name 'sr0' create_node: creating device node '/dev/sr0', major = '11', minor = '0', mode = '0640', uid = '0', gid = '6' create_node: creating symlink '/dev/disk/by-path/pci-0000:00:1f.2-scsi-1:0:1:0' to '../../sr0' create_node: creating symlink '/dev/cdrom' to 'sr0' main: run: 'socket:/org/freedesktop/hal/udev_event' main: run: 'socket:/org/kernel/udev/monitor' What's the content of /etc/udev/rules.d/65-cdrom.rules? # cdrom links generated by YaST2
#
SUBSYSTEM=="block", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:1:0", SYSFS{removable}=="1", SYMLINK+="cdrom"
Looks all fine: create_node: creating symlink '/dev/cdrom' to 'sr0' Are you sure that the link is not there after reboot? It's not # ls -l /dev/cdrom /bin/ls: /dev/cdrom: No such file or directory Ok after another reboot it's there now. |
> eject eject: unable to find or open device for: `/dev/cdrom' It should work out of the box The system has a sata cdrecorder which is /dev/sr0. I guess something should create the proper /dev/cdrom symlinks (both /dev/cdrom and /dev/cdrecorder)