I was having trouble booting new builds of both 2.2.17 and
2.4.0-test8. They both boot as far as
loop: registered device at major 7
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
before spontaneously rebooting. Specifying ide or mem parameters made
no difference. It was made stranger by the fact that the stock Debian
'potato' 2.2.17 image boots and runs fine.
I have just managed to sort out a way of getting the new built kernels
to boot. It confuses me even more, but I hope it make sense to someone
out there.
I was testing the builds by booting from a floppy (made with make
bzdisk). My normal boot is from DOS with a config.sys/autoexec.bat boot menu and
loadlin. If I copy the built vmlinuz images to DOS and boot them with
loadlin automatically from autoexec.bat they go fine. However, if I enter the
loadlin command line manually in DOS I get a reboot at the same point.
I cannot see why entering the loadlin command manually is different
from using autoexec.bat. I also can't really see why booting from a
floppy should be that different from using loadlin/lilo. Does this make any sense at
all?
TIA for any thoughts
Mark
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
