[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Multia Boot failure for RH5.2
- From: Jason Ball <jasonb wyvern apana org au>
- To: axp-list redhat com
- Subject: Multia Boot failure for RH5.2
- Date: Tue, 12 Jan 1999 01:54:59 +1100 (EST)
How do,
I am having some problems getting my Multia to boot Redhat/Alpha 5.2. Up
until a recent hard disk crash this machine was running RH4.2 happily so I
know the machine works.
I successfully load the noname milo image, however when trying to load the
kernel with a
boot floppy
or a
boot fd0:vmlinux.gz root=/dev/fd0 load_ramdisk=1
The system then tries to access the boot floppy, immediately fails
with a 'fatal error: not enough memory', and locks up the milo
console.
However this should not be the case, even with only 24Mb of RAM on board.
I am using the noname boot image, ramdisk and milo image. I have
also built and tried custom boot kernels (both 2.0.36 and 2.1.131) without
any success.
In testing the machine I have successfully installed and run NT, which
reports the correct amount of RAM and runs as well as expected.
I am loath to go to the expense of more memory for a machine that does
little more than drive a couple of modems and runs as a firewall as the
additional memory is not required for normal operation. Additionally the
kernel should at least be able to boot regardless of what the redhat
install wants to do.
Has anybody else experienced similar problems with the Mutlia
installation/bootup under redhat 5.2 ?
Anybody have any ideas on how to fix it ?
Anybody know if there were recent kernel changes that increased the
required memory base ? (It used to work with only 8Meg. I'll spend the
money if there is a real chance that it will fix the problem.)
Thanks
Jason.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[]