Description of Problem: If I install the newest kernel for RH 8.0 using up2date and reboot the OS, it is not possible to use the cdrom in my ThinkPad T20. If I boot with the original kernel of version 8.0 there is no problem. Adding a line for cdrom to /etc/fstab does not help Version-Release number of selected component (if applicable): How Reproducible: 100% Steps to Reproduce: 1. update the RH8.0 to the latest kernel using up2date 2. reboot using the new kernel Actual Results: cdrom is not a valid device Expected Results: cdrom should be available for use Additional Information: Dual boot on ThinkPad T20 The cdrom is in the dock's Ultrabay
Hi, I reported this problem more than two weeks ago. Do you have any advice for me yet? Many thanks, Radu
does it help if you type depmod -ae as root first?
No :( I booted with the new kernel issued the command you reccomend and try to mount: no success. Then I rebooted and tried to mount -> no success again :( Do you have any other advice, please?
can you attach the output of the dmesg command in the failing kernel ?
Created attachment 87804 [details] reuired dump of dmesg command
hmmmm your cdrom really appears to not be there for some reason
Yes: I know. But what to do? If I boot with the 'old' kernel everything is fine : I can use the cdrom and I have the corresponding line in /etc/fstab If I reboot with the new kernel the line in/etc/fstab is gone and I cannot use the cdrom. Adding a line to /etc/fstab now does not help. Is the support for cdrom compiled in the newest kernel? Any suggestions? Thank you, radu
Hi, Other two weeks passed without any reply :o I updated to the newest kernel but with the same negative results :( Could you please check the cdrom support in the newest kernel? Thank you, Radu
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/