On Fri, May 12, 2006 at 12:11:43AM +0200, Stefan Reinauer wrote:
- Ward Vandewege ward@gnu.org [060506 15:11]:
On Sat, May 06, 2006 at 02:39:13PM +0200, Stefan Reinauer wrote:
- Ward Vandewege ward@gnu.org [060505 23:38]:
I've tried this; the boot log is attached (minicom-20060505.cap) with DEBUG_PCI, DEBUG_IDE and DEBUG_LINUXBIOS enabled. Didn't help.
- if that doesnt help: try whether the disk is detected as hda instead of hde. This might happen with the current code.
I've tried that too, the bootlog is also attached (minicom-20060505-2.cap). Still no luck; though here it does seem to find the IDE controller. But not the drive...
Aha! It shows a floating IDE bus... Does anyone have an idea what's wrong exactly if this shows up? It might just be an issue of waiting just a little bit longer..
Hm. can you set the timeout from 20ms to 200ms?
Do you mean this line
timeout = currticks() + 20 * TICKS_PER_SEC / 1000;
in ide_bus_floating() in drivers/ide.c?
Does it work with the etherboot filo btw?
Yes; that's what I've been using. But it _only_ works if I guarantee at least 3 to 4 seconds of bootup delay; that's why I have the AUTOBOOT_DELAY set to 5. But that doesn't work for Filo 0.5 - maybe it tries to find the disks before doing the AUTOBOOT_DELAY?
Ward.