Bug 80752
Summary: | (IDE)cdrom drive non properly recognized during boot up if empty | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | giacomo caio <tanyako02> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | alan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:40:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
giacomo caio
2002-12-30 21:55:49 UTC
Is anyone out there? Nobody out there at all 8) From the trace it appears that with no disk in the drive the drive refuses to allow speed set/query (strange but I guess not completely insane) unfortunately from the traces it then goes bananas. I've not seen any similar reports before at all. Booted with a disk in both drives continue to function happily ? Yes, with a disk inside everything goes happily and shiningly. As a matter of fact, I'm always leaving a disk in the drive but I don't think that this is the best way to face the problem. After all I'm not solving anything... I was having a problem with a machine with an MSI motherboard which has onboard VIA vt8235 controller with a seagate ide drive (st340016a) and an empty (though, this doesn't seem to matter) sony cdrom (cdu5211). I was able to happily kickstart the machine (rh7.3 with 2.4.18-18.7.x kernel off of a local patched install server), but on reboot, it would hang after "Enabling swap". So after much fiddling, i booted the machine by appending init=/bin/bash in grub. I then started walking through /etc/rc.d/rc.sysinit. i hit the place where rh disables dma on the cdrom devices, so i did /sbin/hdparm -q -d0 /dev/hdc all heck broke loose with lots of lost interrupts and all manner of pain (eve if i do this by hand with a data cdrom in there i get lots of lost interrupts and drive not being ready). i shutdown and yanked the cdrom from controller, and i was able to boot the os just fine. if i comment out the section in there, i can boot fine and have a cdrom. it seems that this portion of the rc.sysinit may need to be protected from the vp_ide devices. Sean - different bug so can you open another bug for it, rather than get two confused - thanks. (File it against 'initscripts' as that is what owns those boot scripts) alan- i have opened up bug 81324 covering initscripts. thanks! C'mon guys, I've waited more than a month down here! How is it possible that nobody knows how to fix this?? Please You have apparently the only machine in the world with a bug which may be dependant on precise combinations of controller and firmware. That makes it non trivial to fix and fairly low priority. Quite a bit of IDE work has been done since that release, but I cannot say whether it will fix your problem or not I'm afraid. 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/ |