ananconda do not like cd/dvd reader. [Solved]

[Asimov]

I did to 2 installation of Sabayon. And in both case, the cd/dvd reader is missing. Is it a choice or a bug ?

[Asimov]

i learned about the file: /etc/udev/rules.d/70-persistent-cd.rules

And it was empty ...

[Fitzcarraldo]

Code: Select all

# This file was automatically generated by the /lib64/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.

# DVD_RW_AD-7580S (pci-0000:00:1f.2-scsi-1:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="cdrom", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="cdrw", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="dvd", ENV{GENERATED}="1"
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:0:0", SYMLINK+="dvdrw", ENV{GENERATED}="1"

# Mass_Storage (pci-0000:00:1d.0-usb-0:1.6:1.2-scsi-0:0:0:0)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="HUAWEI_Mass_Storage-0:0", SYMLINK+="cdrom1", ENV{GENERATED}="1"

# Cruzer (pci-0000:00:1d.0-usb-0:1.5:1.0-scsi-0:0:0:1)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="SanDisk_Cruzer_07747002D5903BC6-0:1", SYMLINK+="cdrom2", ENV{GENERATED}="1"

# Cruzer (pci-0000:00:1d.0-usb-0:1.5:1.0-scsi-0:0:0:1)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="SanDisk_Cruzer_0877630290D23880-0:1", SYMLINK+="cdrom3", ENV{GENERATED}="1"

As you can see from the comment at the beginning of the file /etc/udev/rules.d/70-persistent-cd.rules on my main laptop, listed above, that file is automatically generated by the /lib64/udev/write_cd_rules program. Is that program present in your installation, and is udev in the sysinit runlevel?

Code: Select all

# rc-update show -v | grep udev
udev |                                        sysinit
udev-mount |                                        sysinit

If udev is not in the sysinit runlevel, you need to add it:

Code: Select all

rc-update add udev sysinit

[Asimov]

# rc-update show -v | grep udev
udev | sysinit
udev-mount |

That my result. Sysinit is missing ?
My icons-set is almost complete and a don't have backup. The last things that i need now is a major screw-up.

[Fitzcarraldo]

Code: Select all

rc-update add udev-mount sysinit

[Asimov]

Done!

What the next step?

[Asimov]

I did a restart and i did a check up on /etc/udev/rules.d/70-persistent-cd.rules. No change

Part of the file 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.

And i did a check-up for the existence of the script "write_cd_rules" . And it do not exist on my installation. Something else must be missing.

[Fitzcarraldo]

Actually, I've just checked and it doesn't exist on my main laptop either, so I'm at a loss. What udev packages have you got installed? Here is what is installed on my main laptop:

Code: Select all

$ eix -I udev
[U] dev-python/pyudev
     Available versions:  (~)0.11 (~)0.12 (~)0.13 0.15 (~)0.16.1 {{pygobject pyqt4 pyside test}}
     Installed versions:  0.15(02:19:58 29/03/12)(pyqt4 -pygobject -pyside)
     Homepage:            http://packages.python.org/pyudev/ http://pypi.python.org/pypi/pyudev
     Description:         Python binding to libudev

[I] sys-fs/udev
     Available versions:  (~)141-r1 146-r1^t 149 151-r4 164-r2 171-r8 (~)189^t (~)190^t (~)191^t (~)192^t (~)193^t (~)194^t (~)195^t **9999^t {{acl action_modeswitch build debug (+)devfs-compat doc edd (-)extras floppy gudev hwdb introspection keymap old-hd-rules +openrc +rule_generator selinux static-libs test}}
     Installed versions:  195^t(23:21:07 07/11/12)(acl gudev hwdb keymap openrc static-libs -doc -introspection -selinux)
     Homepage:            http://www.freedesktop.org/wiki/Software/systemd
     Description:         Linux dynamic and persistent device naming support (aka userspace devfs)

[I] sys-fs/udev-init-scripts
     Available versions:  (~)10^t (~)12 (~)14 (~)15^t (~)16^t (~)17^t (~)17-r1^t **9999^t
     Installed versions:  17-r1^t(22:12:42 07/11/12)
     Homepage:            http://www.gentoo.org
     Description:         udev startup scripts for openrc

Found 3 matches.

eix is a Portage tool, but is in the Entropy repository. You can install it and then run the eix-update command to update its database:

Code: Select all

emerge --sync
layman -S
equo install eix
eix-update

[Asimov]

That all a got.

eix -I udev
[I] dev-python/pyudev
Available versions: (~)0.11 (~)0.12 (~)0.13 0.15 (~)0.16.1 {{pygobject pyqt4 pyside test}}
Installed versions: 0.16.1(08:58:40 AM 10/08/2012)(pyqt4 -pygobject -pyside)
Homepage: http://packages.python.org/pyudev/ http://pypi.python.org/pypi/pyudev
Description: Python binding to libudev

[U] sys-fs/udev
Available versions: (~)141-r1 146-r1^t 149 151-r4 164-r2 171-r8 (~)189^t (~)190^t (~)191^t (~)192^t (~)193^t (~)194^t (~)195^t **9999^t {{acl action_modeswitch build debug (+)devfs-compat doc edd (-)extras floppy gudev hwdb introspection keymap old-hd-rules +openrc +rule_generator selinux static-libs test}}
Installed versions: 189^t[?](06:43:23 PM 08/30/2012)(acl gudev hwdb keymap openrc static-libs -doc -introspection -selinux)
Homepage: http://www.freedesktop.org/wiki/Software/systemd
Description: Linux dynamic and persistent device naming support (aka userspace devfs)

[U] sys-fs/udev-init-scripts
Available versions: (~)10^t (~)12 (~)14 (~)15^t (~)16^t (~)17^t (~)17-r1^t **9999^t
Installed versions: 16^t[?](07:59:19 AM 09/24/2012)
Homepage: http://www.gentoo.org
Description: udev startup scripts for openrc

I just making a guess here: Anaconda is a Python script and 'write_cd_rules' is a runtime module of Anaconda ?

[Fitzcarraldo]

This has nothing to do with Anaconda. Anaconda is the installer that installs SL to the HDD. Udev is the device manager for the kernel, and write_cd_rules is part of udev.

What do you have in /etc/fstab? If you have added any optical drives to that you must remove them from fstab, as that will interfere with what udev is doing. For example, I have an optical drive that works fine in Linux, but notice that /etc/fstab on my machine does not have any reference to optical drives:

Code: Select all

/dev/sda6               /                       ext4    user_xattr,noatime        1 1
/dev/sda7               /home                   ext4    user_xattr,noatime        1 2
/dev/sda3               /boot                   ext4    user_xattr,noatime,noauto 1 2
/dev/shm                /dev/shm                tmpfs   defaults                  0 0
/dev/sda5               swap                    swap    defaults                  0 0
/dev/sda2               /media/Windows7         ntfs-3g defaults                  0 0

What do you have in /dev/? Here is what I have:

Code: Select all

# ls -la /dev/sr0
brw-rw----+ 1 root cdrom 11, 0 Nov 16 07:21 /dev/sr0
# ls -la /dev/dvd*
ls: cannot access /dev/dvd*: No such file or directory
# ls -la /dev/cd*
lrwxrwxrwx 1 root root 3 Nov 16 07:21 /dev/cdrom -> sr0

You should have a device /dev/sr0. Notice that I have a symlink /dev/cdrom that is linked to /dev/sr0. If you have /dev/sr0 but not the symlink, then you can create one manually:

Code: Select all

su
Password:
cd /dev
ln -s sr0 dvd
ln -s sr0 cdrom

You shouldn't need to do that, but it might at least get it working.

EDIT: Also, what you you have in the file /usr/lib64/udev/rules.d/60-cdrom_id.rules on your machine? Here is mine for comparison:

Code: Select all

# do not edit this file, it will be overwritten on update

ACTION=="remove", GOTO="cdrom_end"
SUBSYSTEM!="block", GOTO="cdrom_end"
KERNEL!="sr[0-9]*|xvd*", GOTO="cdrom_end"
ENV{DEVTYPE}!="disk", GOTO="cdrom_end"

# unconditionally tag device as CDROM
KERNEL=="sr[0-9]*", ENV{ID_CDROM}="1"

# media eject button pressed
ENV{DISK_EJECT_REQUEST}=="?*", RUN+="cdrom_id --eject-media $devnode", GOTO="cdrom_end"

# import device and media properties and lock tray to
# enable the receiving of media eject button events
IMPORT{program}="cdrom_id --lock-media $devnode"

KERNEL=="sr0", SYMLINK+="cdrom", OPTIONS+="link_priority=-100"

LABEL="cdrom_end"

or, if you have more than one optical drive, the udev rules file given in the Gentoo Forums post: http://forums.gentoo.org/viewtopic-p-71 ... ml#7184082