Bugzilla – Bug 120122
CDRom module lists drive as not bound
Last modified: 2006-01-23 14:41:44 UTC
My CD drive works correctly in my system, but the YaST2 module always shows it as not configured when there´s no CD in the drive. When I click on "add" and restart YaST2 the drive is again listed as not configured. Perhaps there´s something wrong with the HAL automounter. If needed I can post a YaST2 log.
yes, please add y2log and screenshot. thanks
Created attachment 51413 [details] YaST2 logs
Unfortunately the screenshot program isn´t included in 10.1A1, so I don´t know how to make a screenshot. The CD drive is present in the list, the device is correct, but there´s neither a link nor a mountpoint. The "add" button is enabled, the "remove" one disabled. Reading through the text on the left side this means the drive is not integrated, even though it works. It´s also strange why there is a coloumn for a mountpoint even if the mountpoint changes to the media name every time I insert a CD.
There were bugs in cdrom.ycp that will be fixed in SL 10.1. With all this new hal things this modules is not of too much use anyway. The problems are only in the cdrom-module within YaST2, functionality of the drives should not be affected at all.
Yes tha´s also what I thought. The cd-rom module seems to need to be updates for HAL
Will this be fixed for 10.1 (so that the cdrom module gets usable again). Or since I don´t see many things to configure with the HAL + subfs system will the module disappear. IMHO it´s a little bit strange to ship SuSE with unusable YaST modules (which already happened in 10.0)
To be honest, I have no idea what HAL,subfs,udev will do to cdrom module in SL 10.1. So I will simply see what happens. Maybe dropping the module would really be the best long term solution.
Since there will be no fstab entries for optical devices in SL 10.1 any more (starting with beta#2), the cdrom module will also be dropped.