Quote:
Originally posted by KraM
Yes, but the bootloader loaded the image. |
Exactly where did the image come from???? It came from the CDROM disc called 'distro install disc one'. Flawless performance on that first try when accessing the CDROM drive. After that point, the loaded data contained something that eventually modified how the current process would access the CDROM. Buggy BIOS or no, the same BIOS worked correctly before the software loaded in order to get the bootloader (did not need ATAPI resets at that point... I'd have heard it, very distinct pattern of head positioning attempts), then everything still worked correctly while loading the first booted code and even worked while loading of a few subsequent screens. After this, the system then began working incorrectly. And the same BIOS works fine on a different CDROM.
Quote:
|
It just sounds like linux is having trouble with your particular combination of hardware. Or, there is something wrong with you hardware.
|
Granted. I use a different CDROM
now because I have already decided the first CDROM drive might be bad... I'm now using a diffferent drive on the same system and things now act correctly. We'll see how the different drive functions over the next few weeks, but no ATAPI resets thus far means I like it more than the first drive.
Quote:
I'm taking an educated guess here: I think the bootloader uses the BIOS to access the IDE devices. But, Linux, being the advanced piece of software that it is  , accessing these devices directly, thus bypassing potentially buggy BIOSes.
|
Might the device be designed exactly the other way around - assuming the BIOS will be the only method? Might the Linux assumption that 'all CDROM drives are standardized' be a bit less than realistic?
Quote:
|
You can force Linux to access the PCI bus through the BIOS, and the IDE controllers are on the PCI bus (??). Anyway, to do this, while configuring a kernel:
|
Not while booting from CD for the first install....
Thanks for trying, but I remain uninformed.