Re: Memory above 64M and slink

[Lee Bradshaw <lee@sectionIV.com>]

I think 2.0.36 was the first stable kernel to recognize more than 64M
automatically. Try it without the append= line. My systems recognizes
256M without the append= line in lilo.conf. Here are the first few lines
from dmesg:

>>Memory: sized by int13 0e801h
  Console: 16 point font, 400 scans
  Console: colour VGA+ 80x25, 1 virtual console (max 63)
  pcibios_init : BIOS32 Service Directory structure at 0x000fdb60
  pcibios_init : BIOS32 Service Directory entry at 0xfdb70
  pcibios_init : PCI BIOS revision 2.10 entry at 0xfdb91
  Probing PCI hardware.
  Calibrating delay loop.. ok - 400.59 BogoMIPS
>>Memory: 256984k/262144k available (816k kernel code, 384k reserved, 3960k data)

If it doesn't work I can't offer any other suggestions.

On Mon, Mar 22, 1999 at 06:56:37AM -0500, Sebastian Canagaratna wrote:
> Hi: , I was under the impression that going from Hamm to
>       slink would enable me to use all my 80M of memory.
> 
>       I am using kernel 2.0.36, with, in the /etc/lilo.conf
>       the first line append="mem=80M" but only about 63 odd M
>       are recognized? Is it possible to overcome this?

-- 
Lee Bradshaw                 lee@sectionIV.com (preferred)
Alantro Communications       lee@alantro.com