The crash came at re-boot time (after adjusting /etc/lilo.conf
and running Lilo).
The BIOS reports a full 32M.
Having removed the "append" line in lilo.conf I'm back where I
was with 23M of RAM reported at the log-in screen.
The diagnosis that the on-board video card is grabbing 8MB sounds
right.
I append my lilo.conf file - any one see anything sinister about
it?
Many thanks for all the help.
Glyn M.
-------------------------------------------------
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
vga=normal
default=linux
keytable=/boot/uk.klt
prompt
timeout=50
message=/boot/message
other=/dev/fd0
label=floppy
unsafe
image=/boot/vmlinuz
label=linux
root=/dev/hda1
append=""
read-only
On Thu, Apr 06, 2000 at 08:16:29AM -0800, thus spake Civileme:
> Glyn Millington wrote:
> >
> > Wow! I tried this and it threw
>
>
> The kernel footprint is about 500K.� This is not windows where it runs
> about 4Mb (at least for NT)
>
> A kernel panic when?� When you ran LILO?� When you rebooted as well or
> just when you rebooted?
>
> What does your BIOS say when it tests memory at the opening screen?�
> This sounds suspiciously like a memory problem. �� The kernel normally
> accepts the amount of memory reported by the BIOS, and the append is to
> workaround BIOSes that fail to report all of it, but almost always this
> is upwards of 64M or 15 or 14M depending on whether the "hole" from
> 15-16M is activated in the BIOS.
>
> Civileme
>
>
--
******************************************************
* "The soul is greater than the hum of it's parts. " *
* Douglas Hoftstatder *
******************************************************
