From: Stephen Shirley (diamond at domain csn.ul.ie)
Date: Wed 04 Aug 1999 - 12:02:40 IST
I'm guessing that you're running Suse 5.2 or older, with one of the 2.0.x
series of kernels, right? If so, you have to inform Linux of any memory above
the 64mb line with
append = "mem=128"
in your lilo file. Eg:
***********************************
boot = /dev/hda
timeout = 50
prompt
default = linux
vga = normal
root = /dev/hdb1
read-only
map=/boot/map
install=/boot/boot.b
image = /boot/vmlinuz
label = linux
append = "mem=128"
*************************************
If that gives you grief, try mem=127 etc until the damn thing boots properly.
Note of caution, make sure you make a backup boot option so that if the machine
screws up with 128mb ram, you can still get in and fix it:
*************************************
image = /boot/vmlinuz
label = backup
*************************************
If you are running one of the 2.2.X kernels, then it's possible that you have
faulty ram.
G'luck
Steve
On Wed, 04 Aug 1999, you wrote:
> I have a machine at home with 1*128m DIMM. The BIOS reports it
> correctly, but when SuSE starts up it only reports 64m. It has never
> run under any other OS, so I can't check to see what NT or 95 reports.
>
> Does anybody have any ideas what might be causing this ? One
> possibility is that the display (SiS6326) shares 8m of the main
> memory and maybe this causes Linux some grief.
>
> Any ideas ?
>
> Cheers,
>
> David
>
> --
> Irish Linux Users' Group: ilug at domain linux.ie
> http://www.linux.ie/mailman/listinfo/ilug for (un)subscription information.
> List maintainer: listmaster at domain linux.ie
-- <The .sig got shot cause someone didn't like it>
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:04:25 GMT