aegressy
asked on
IDE/ATAPI CD-ROM fail under 2.2.0 and higher
I have an IDE/ATAPI cdrom (ACER 8x) which doesn't work on kernels 2.2.0 and higher.
On kernel 2.0.35 it runs well:
hda: QUANTUM FIREBALL ...
hdc: no response, resetting
hdc: CD-ROM ...
BUT on kernel 2.2.0+ the following happens:
hda: QUANTUM FIREBALL ...
-- 5 seconds the computer is waiting ---
AND countinues booting without any CD-ROM detected.
I know, that there must exist a compilation of kernel 2.2.x that works, because the installation of Su.S.E 6 is also built on kernel 2.2.0.
BUT no publicated version worked.
Please give me an advise, what to do.
Thanks
aegressy
Note: Maybe there will be something on 'no response, resetting' - but I don't know what.
On kernel 2.0.35 it runs well:
hda: QUANTUM FIREBALL ...
hdc: no response, resetting
hdc: CD-ROM ...
BUT on kernel 2.2.0+ the following happens:
hda: QUANTUM FIREBALL ...
-- 5 seconds the computer is waiting ---
AND countinues booting without any CD-ROM detected.
I know, that there must exist a compilation of kernel 2.2.x that works, because the installation of Su.S.E 6 is also built on kernel 2.2.0.
BUT no publicated version worked.
Please give me an advise, what to do.
Thanks
aegressy
Note: Maybe there will be something on 'no response, resetting' - but I don't know what.
ASKER
I have the Quantum disk on Primaty-Master and the CD-ROM on Secondary-Master. And I have no other devices on the controller.
I will check it again, but it must be jumpered well - by my opinion - cause otherwise it wouldn't work in Windowzes or on an older kernel.
I will check it again, but it must be jumpered well - by my opinion - cause otherwise it wouldn't work in Windowzes or on an older kernel.
Not neccessarily; the "no response" message under 2.0.35 says that SOMETHING is still wrong there.
When you first boot, what does your BIOS say it recognizes?
When you first boot, what does your BIOS say it recognizes?
Clay is right. Windoze is much more passive about bad hardware. I have a cdrom doing just the opposite right now works under linux but not win. You can alos try tapping the eject button during the scan to wake up a "sleepy " drive.
ASKER
So first the BIOS at first boot-up:
Found ATAPI CDROM 685A-(SM)
(SM) - means on Secondary Master.
And one more note: It happened two times, that the CD-ROM worked under the mentioned kernel. Once I was openning the CD's door right at the time, when Linux was initializing the IDE-controller, but I tried it at least 20 times, and it did not help. At the second time, it was after using Windoze. But I also tried this - with Win drivers, with DOS drivers, restarting, resetting, restarting from DOS mode ... And the result: still nothing.
Found ATAPI CDROM 685A-(SM)
(SM) - means on Secondary Master.
And one more note: It happened two times, that the CD-ROM worked under the mentioned kernel. Once I was openning the CD's door right at the time, when Linux was initializing the IDE-controller, but I tried it at least 20 times, and it did not help. At the second time, it was after using Windoze. But I also tried this - with Win drivers, with DOS drivers, restarting, resetting, restarting from DOS mode ... And the result: still nothing.
I still think you need to check the device itself (I know it's a pain to pull it out; I've been through exactly this problem). On my CD (it's a "generic" brand I got at a discount store), there were TWO jumpers - for MASTER, one of them was not connected, and the other was jumpered across 1-2 (of 6). For SLAVE, 3-4 and 5-6 were BOTH jumpered. It's possible that you've got that sort of a problem. Also, the "hdc - no response, resetting" message indicates that there REALLY IS a problem; but for some reason the earlier kernel recovers. I would expect that if you get rid of that problem, the problem with 2.2 will go away as well.
Have you tried jumpering the CD as a SLAVE and running it off the PRIMARY interface?
Clay
Have you tried jumpering the CD as a SLAVE and running it off the PRIMARY interface?
Clay
ASKER
Something very special happened:
When I put the CD-ROM to the same cable, as the HDD, it WORKED.
But if I have the CD and the HDD on the same cable, the HDD is SLOW (and it is not a good thing).
AND I tried all the possibly situations with the jumpers (on the CD), and I also tried to exchangle the IDE cables.
The result is the same: with the HDD it works, whithout it doesn't work.
Very, very unusual.
Where is the problem? Not known.
When I put the CD-ROM to the same cable, as the HDD, it WORKED.
But if I have the CD and the HDD on the same cable, the HDD is SLOW (and it is not a good thing).
AND I tried all the possibly situations with the jumpers (on the CD), and I also tried to exchangle the IDE cables.
The result is the same: with the HDD it works, whithout it doesn't work.
Very, very unusual.
Where is the problem? Not known.
I have seen similiar problems with hardrives that have had there controller go bad on them. This means two things, one you have a really good hdd and second is that your cdrom likly bad or rapidlly failing.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I've seen this happen when a drive was jumpered as a SLAVE and there was no MASTER drive present on that controller.
If that's the case, then you'll want to either put the CDROM on the 2nd port of the PRIMARY controller; or re-jumper the CDROM to be a MASTER on the SECONDARY controller.