Bugzilla – Bug 133730
No symlinks for DVD drives in /dev
Last modified: 2005-11-22 15:09:40 UTC
I´ve a system with a DVD drive and a DVD writer. hwinfo --cdrom returns: r098088:/home/michael # hwinfo --cdrom 22: IDE 00.0: 10602 CD-ROM (DVD) [Created at block.192] UDI: /org/freedesktop/Hal/devices/storage_model_TSSTcorpDVD_ROM_SH_D162C Unique ID: Fffu.NCXsS7z3eEE Parent ID: H0_h.P78gQwLLcqE SysFS ID: /block/hda SysFS BusID: 0.0 SysFS Device Link: /devices/pci0000:00/0000:00:06.0/ide0/0.0 Hardware Class: cdrom Model: "TSSTcorpDVD-ROM SH-D162C" Vendor: "TSSTcorpDVD-ROM" Device: "SH-D162C" Revision: "TS02" Serial ID: "" Driver: "AMD_IDE", "ide-cdrom", "ide-cdrom" Device File: /dev/hda Device Files: /dev/hda, /dev/disk/by-path/pci-0000:00:06.0-ide-0:0 Device Number: block 3:0 Features: DVD Size: 0 sectors a 512 bytes Drive status: no medium Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #7 (IDE interface) Drive Speed: 48 23: IDE 01.0: 10602 CD-ROM (DVD-R) [Created at block.192] UDI: /org/freedesktop/Hal/devices/storage_model_TSSTcorpCD/DVDW_TS_H552B Unique ID: iqvy.a355tLoUx33 Parent ID: H0_h.P78gQwLLcqE SysFS ID: /block/hdb SysFS BusID: 0.1 SysFS Device Link: /devices/pci0000:00/0000:00:06.0/ide0/0.1 Hardware Class: cdrom Model: "TSSTcorpCD/DVDW TS-H552B" Vendor: "TSSTcorpCD/DVDW" Device: "TS-H552B" Revision: "TS10" Serial ID: "" Driver: "AMD_IDE", "ide-cdrom", "ide-cdrom" Device File: /dev/hdb Device Files: /dev/hdb, /dev/disk/by-path/pci-0000:00:06.0-ide-0:1 Device Number: block 3:64 Features: CD-R, CD-RW, DVD, DVD-R Size: 0 sectors a 512 bytes Drive status: no medium Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #7 (IDE interface) Drive Speed: 48 The drives work within KDE but cedega complains about the missing /dev/dvd(reocrder) symlinks. In fstab I´ve two entries: /dev/dvd /media/dvd subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/dvdrecorder /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 but there are just /dev/hda and /dev/hdb, and no symlinks to them. Is there a way to create them with YaST?
This has to be done in the udev/devfs scheme
Optical device links are managed by Yast at the moment and not by udev.
Where is the actual problem here?
I already wrote where the problem is: The drives work within KDE but cedega complains about the missing /dev/dvd(reocrder) symlinks. This is a bug, the fstab entries are there but the targets are not. And the YaST cdrom module is not usable in 10.0.
So this is not a problem with the YaST2 cdrom module, where is the problem located then? Without knowing this, I have a hard time reassigning this. If the fstab was generated by YaST that way (pointing to symlinks) but the symlinks themselves were not created (assuming both drives were present at installation time), please attach the YaST logs of the installation. I wonder how it is possible for KDE to function with an invalid fstab.
I had a similar problem. With the subfs info inside the fstab my dvd and dvdrecorders were not accessible, i.e. /dev/dvd was never mounted under the subfs scheme. These entries in the subfs /dev/dvd /media/ subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/sr0 /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 were probably leftovers from previous SuSE installs. I cannot tell you exactly when they appeared since my system had all SuSE versions since 8.2. Once I removed the entries from fstab it all started to work correctly again, e.g inserting the SuSE 10.0 CD I get normal hardware detection working and the entry /dev/hdc on /media/dvd type subfs (ro,nosuid,nodev,fs=cdfss,procuid,iocharset=utf8) and links lrwxrwxrwx 1 root root 10 2005-11-20 17:53 /media/SU1000_001 -> /media/dvd although if I leave the CD in the drive it never stops spinning as if it is being continuously accessed.
I don´t know if the "YaST2 logs of the installation" are still present on my system. Where should they be?
Michael: in /var/log/YaST2, all y2logs thomas: is this a yast problem? if not, please reassign to us.
Created attachment 57931 [details] All YaST2 logs
I don't understand comment #2. YaST2 creates the file "/etc/udev/rules.d/ 55-cdrom.rules" but the links themself are created by udev. Looks more like a duplicate of bug #133651. Michael, you should be able to see bug #133651. Can you please check if loading the module "ide-cd" (run /sbin/modprobe ide-cd as root) causes the links to appear. If not, please attach the file /etc/udev/rules.d/55-cdrom.rules to this bug report.
Unfortunately loading the "ide-cd" module doesn´t create the symlinks. I attached the 55-cdrom.rules
Created attachment 57991 [details] 55-cdrom.rules
Did you change anything hardware-related on the system? In the 55-cdrom.rules file the ID_PATH of the dvd drive is "pci-0000:00:12.0-ide-0:0" but hwinfo of comment #1 shows it as "pci-0000:00:06.0-ide-0:0". The logs suggest a change between the 7th and 13th. Otherwise please provide the output of "bash -x path_id /block/hda" and "bash -x path_id /block/hdb".
Oh yes I did change my motherboard. Sorry I didn´t mention, I thought this has nothing to do with the drive assignment. Is SuSE designed to recognize a changed hardware configuration like windows does? I´ve submitted many bug reports just because of the fact that changing system components often lead to an unuseable system. IMHO there should be some logic which detects new devices and configures them automatically. Ok now what could I do to correct this?
These drivers are assigned by PCI ID. That ID has changed with the motherboard exchange. Edit the 55-cdrom.rules file and set the path to pci-0000:00:06.0-ide-0:0 and pci-0000:00:06.0-ide-0:1. Otherwise I consider the change of the complete motherboard as too drastic to make the system work afterwards. This already affect booting the system (e.g. driver for ide controller, finding boot device and root partition) so a reparation might not be feasible.
Ok thanks this fixed the problem for me. In general, is SuSE not designed to handle Hardware changes. I mean an OS which is popular like SuSE should be able to do that. After I changed the mobo I ran the "repair" from the isntaller and it worked (sort of) again. What about a "hardware change" mode be introduces in the installer which just does all the hardware (and partition etc.) checking (which the installer does when installing) again and writes the changes, so if the user changes anything on the hardware he could run this mode and the system will be fine again.