Bugzilla – Bug 118673
CD-ROM drives detected incorrect
Last modified: 2005-09-30 09:27:28 UTC
Attached is a screenshot which is shown by the YaST2 module "cdrom" The first entry is correct, the drive is installed in my system. The second entry is correct too, the drive is present, but when I "add" the drive (goes successfully on /media/dvd) and exit and reenter the module, its state is still as seen on the screenshot (not integrated). The third drive isn´t present and the forth is a duplicate. It seems that YaST detects 3 drives instead of one.
Created attachment 50772 [details] Screenshot displaying the detected configuration
I just noticed another strange thing. Sometimes the whole system hangs for some seconds while the LED of the drive which is misdetected flashges, regardless whether there´s a CD in it or not
please provide /var/log/YaST2/y2log and hwinfo --cdrom
Attached id the y2log. I removed all the cd drives from my system, but YaST still reports 2 cd drives. hwinfo --cdrom returns nothing.
why you removed the drives? there is no y2log attached.
Oops sorry I´ll attach the log. I removed the drives because the system often locks up with the light of the first drive lit. I tried various configurations with the drives and YaST always showed drives that didn´t exist. So I thought the best for helping to fix this bug is attaching a log where no drives are attached to the system but YaST reports 2 drives in the system.
Created attachment 50826 [details] YaST2 Logs
unfortunately are also cdrom drives visible that have been removed from the system since these removed drives still have entries in the hwinfo database. This will be fixed in SL 10.1.
How can I fix this for my system? These entries cause one drive to fail to be integrated and also cause lockups sometimes as described above.
I doubt that presence of these entries cause lockups maybe the lockups are caused by the udev subsystem itself but I have no knowledge about udev. YaST2 only creates lines in /etc/udev/rules.d/55-cdrom.rules and /etc/fstab. It might help to remove all entries concerning cdroms from these files but of course then udev will not create links /dev/{cdrom,dvd,cdrecorder} automatically for you.
Isn´t it possible to configure the system like its "supposed" to be. I mean like if I´d do a clean install of RC1. If there are some old entries which aren´t removed can I just remove them and make the non-existing entries in YaST disappear?
As already said, simply edit the entries from /etc/udev/rules.d/55-cdrom.rules according to your needs. These lines look like the following (all in one line): SUBSYSTEM=="block", ENV{ID_PATH}=="pci-0000:00:1f.1-ide-1:0", SYSFS{removable}=="1", SYMLINK+="cdrom" The entry for "ENV{ID_PATH}" can be found with "hwinfo --cdrom" just look at the line with "/dev/disk/by-path/" and use the last entry of this path after ENV{ID_PATH}==. The entry "SYMLINK+=" contains symlinks in /dev created for this device if there should be more than one separate them by spaces.
I don´t have a /etc/udev/rules.d/55-cdrom.rules file There exists a 20-cdrom.rules which contains the following: # cdrom links generated by YaST2 # BUS="ide", ID="1.0", SYSFS{removable}="1", SYMLINK="dvdrecorder cdrom dvd cdrecorder" BUS="ide", ID="0.0", SYSFS{removable}="1", SYMLINK="dvd cdrom" BUS="none", ID="0.0", SYSFS{removable}="1", SYMLINK="dvd"
This was present in SL 9.3 and will not work any more in SL 10.0 Just create lines in a file /etc/udev/rules.d/55-cdrom.rules as described in comment #12.
Sorry if I misunderstand you here, but I´ve another system with RC1 installed (no upgrade) and there´s also no "55-cdrom.rules" present as you said its created by YaST but also a "20-cdrom.rules". Before I try to get the cdroms to work I´d like to remove the old entries from the hardware database. YaST2 still reports the 2 non-existing cdroms even if I delete the rules file.
You have to create 55-cdrom.rules manually, I explained in comment #12 how this can be done. The problem with the duplicated lines in cdrom dialog is unrelated to the file 55-cdrom.rules as are the hangs of you cdrom devices.
*** Bug 119103 has been marked as a duplicate of this bug. ***