=/dev/hda2
There are other LOADLIN options if your parms won't fit into 1 line - see
/usr/doc/loadlin.
--
From: Rick Macdonald
To: Vincent Murphy
Subject: Re: The case of the missing 64 meg...
Date: Thursday, April 22, 1999 6:04AM
On Thu, 22 Apr 1999, Vincent Murphy wrote:
> On Thu,
On Thu, 22 Apr 1999, Vincent Murphy wrote:
> On Thu, Apr 22, 1999 at 12:31:39AM -0400, Will Lowe wrote:
> > .. Simplest thing to do is put:
> >
> > append="mem=128m"
> >
> > in your lilo.conf file. For my 96 meg machine, I've got a stanza that
> > reads:
>
> what if i don't use lilo and i w
We also shouldn't forget, after adding to lilo.conf append='mem=128M'
to run lilo.
Sebastian Canagaratna,
Department of Chemistry
Ohio Northern University
Ada, OH 45810
> *- On 22 Apr, Arcady Genkin wrote about "Re: The case of the missing 64
> meg..."
> > D
> >> Linux won't recognize memory above 64 megs by itself. You need to add
> >> 'mem=128m' in your lilo.conf file. (or rather append = 'mem=128m'). Check
> >> out the lilo.conf man page for better details, I can't remember the exact
> >> syntax at the moment.
> >
> > Just want to add that anoth
*- On 22 Apr, Arcady Genkin wrote about "Re: The case of the missing 64 meg..."
> Dan Willard <[EMAIL PROTECTED]> writes:
>
>> Linux won't recognize memory above 64 megs by itself. You need to add
>> 'mem=128m' in your lilo.conf file. (or rather
Kernel 2.0.36 will do > 64MB. For previous kernels you can download a
patch from David Parsons, for which I don't have the URL handy at the
moment. E-mail me privately if you'd like me to look.
On Thu, 22 Apr 1999, Vincent Murphy wrote:
> On Thu, Apr 22, 1999 at 12:31:39AM -0400, Will Lowe wrot
On Thu, Apr 22, 1999 at 12:31:39AM -0400, Will Lowe wrote:
> .. Simplest thing to do is put:
>
> append="mem=128m"
>
> in your lilo.conf file. For my 96 meg machine, I've got a stanza that
> reads:
what if i don't use lilo and i want to boot from a floppy? any way of
makeing 2.0.x recognise
> I have a system with 128 meg. of memory but I believe Linux only
> sees half of it and the rest is wasted.
The kernel will only autodetect 64 megs (apparently there was a bug in
some older PCs which caused problems if you probed beyond 64 megs).
You need to pass an argument to the kernel at boo
Dan Willard <[EMAIL PROTECTED]> writes:
> Linux won't recognize memory above 64 megs by itself. You need to add
> 'mem=128m' in your lilo.conf file. (or rather append = 'mem=128m'). Check
> out the lilo.conf man page for better details, I can't remember the exact
> syntax at the moment.
Just w
iginal Message-
> From: Ernie Pasveer [SMTP:[EMAIL PROTECTED]
> Sent: Thursday, April 22, 1999 12:01 AM
> To: debian-user@lists.debian.org
> Subject: The case of the missing 64 meg...
>
> I was hoping someone could help me.
>
> I have a system with 128 meg. of memor
On Wed, 21 Apr 1999, Ernie Pasveer wrote:
>I was hoping someone could help me.
> ...
I should follow up my own message by saying the available memory "64236K av"
Mem: 64236K av, 40180K used, 24056K free, 10932K shrd, 2548K
buff
never changes no matter what my system load is.
--e
I was hoping someone could help me.
I have a system with 128 meg. of memory but I believe Linux only
sees half of it and the rest is wasted.
Here's an output from 'top'
53 processes: 51 sleeping, 1 running, 0 zombie, 1 stopped
CPU states: 33.2% user, 11.8% system, 0.0% nice, 55.0% idle
Mem:
12 matches
Mail list logo
