Re: [Sheflug] Memory Problems

[Sammy Redshaw <nospam [at] cableinet.co.uk>]

Go to www.linuxnewbie.org they have a helpful how-to to sort out the ram problem

or go etc/lilo conf
open

find : append="(may have other comment do not delete)"
add:append"mem=160m" or slightly lower number depending on how much memory you
have !

then

go to console

and  type (in root)

[root@localhost / root]# /sbin/lilo -v

then reboot

then check memory

at console
[root@localhost / root]#cat /proc/meminfo

this work see my attached lilo.conf

to make sure it is correct!



[root@localhost / root]#cat /proc/meminfo



Damion Yates wrote:

> On Wed, 3 May 2000, Foz wrote:
>
> > During my easter vacation I decided it was time to bump up the
> > 32Mb of ram with a 128Mb, giving a total of 160Mb
> > Unfortunantly Linux, does not seem to acknoledge that it is there:
> >
> > foz [at] linux:/proc > free /t
> >              total       used       free     shared    buffers    cached
> > Mem:         63616      48656      14960      49860       2948     23056
> > -/+ buffers/cache:      22652      40964
> > Swap:        66492          0      66492
> > Total:      130108      48656      81452
> >
> >
> > foz [at] linux:/proc > cat meminfo
> >         total:    used:    free:  shared: buffers:  cached:
> > Mem:  65142784 56696832  8445952 54460416  3620864
> > 27090944
> > Swap: 68087808       0 68087808
> > MemTotal:     63616 kB
> > MemFree:       8248 kB
> > MemShared:    53184 kB
> > Buffers:       3536 kB
> > Cached:       26456 kB
> > BigTotal:         0 kB
> > BigFree:          0 kB
> > SwapTotal:    66492 kB
> > SwapFree:     66492 kB
> >
> >
> > Am I just reading the information incorrectly or is there a problem
> > here?
>
> Try booting with mem=160M as a kernel param (DO NOT MISS THE M :)
> if this works add it to your loadlin/grub/nuni/lilo config for booting, or
> rdev -r your kernel.
>
> Linux doesn't always successfully find all memory, I think this is a problem
> with PC hardware as it stands (as are loads of other problems) but as NT/win
> can work it out I still consider this a bug.  I think it's a problem of doing
> the check once you've already entered prot. mode which can be fixed.
>
> Damion
>
> --
> Damion Yates - Senior Internet Operations Engineer - Internet Services
> email: Damion.Yates [at] bbc.co.uk - phone: +44 1737 839510
>
> ---------------------------------------------------------------------
> Sheffield Linux User's Group - http://www.sheflug.co.uk
> To unsubscribe from this list send mail to
> - <sheflug-request [at] vuw.ac.nz> - with the word
>  "unsubscribe" in the body of the message.
>
>   GNU the choice of a complete generation.
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/hda1
	label=windows
	table=/dev/hda
image=/boot/vmlinuz
	label=linux
	root=/dev/hda6
	append="/dev/hdd=ide-scsi   mem=128m"
	read-only
other=/dev/fd0
	label=floppy
	unsafe