On Thu, 14 Sep 2000, Mirek Kwasniak wrote:
> On Tue, Sep 12, 2000 at 09:33:11PM +0200, Floods wrote:
> > append="mem=192m"
>
> Grub has own memory detection metod
Then it doesn't work...My system sees only 64M if I don't specify
'mem=192m'
> but lilo doesn't has any.
> Your append-mem e
On Tue, Sep 12, 2000 at 09:33:11PM +0200, Floods wrote:
> I have an Athlon-based system too and grub sees all my 192M.
> This is my linux section in menu.lst file:
>
> title linux
> kernel (hd0,4)/boot/vmlinuz root=/dev/hda5 vga=2 mem=192m
> initrd (hd0,4)/boot/initrd.img
On Wed, Aug 30, 2000 at 05:56:52PM -0600, Art Edwards wrote:
> I just purchased two Athalon-based systems, each with 768M of ram.
> However, under debian (potato runnin kernel 2.2.17) the OS sees only 65
> M of memory. I have tried to use the append command
>
> mem=768M
>
> but it still
On Tue, 12 Sep 2000, Julio Merino wrote:
> On Mon, Sep 11, 2000 at 11:44:41PM -0700, Krzys Majewski wrote:
>
> > Debian install docs do say something about disabling all
> > "memory holes" in the bios. -chris
>
> I have these options disabled... but why are they useful?
>
> Thanks
>
>
No i
On Mon, Sep 11, 2000 at 11:44:41PM -0700, Krzys Majewski wrote:
> Debian install docs do say something about disabling all
> "memory holes" in the bios. -chris
I have these options disabled... but why are they useful?
Thanks
>
> On Mon, 11 Sep 2000, Julio Merino wrote:
>
> > On Mon, Sep 11, 2
Lucky I didn't shut my server down then ;-)
--On Monday, September 11, 2000 22:19 +0200 Julio Merino <[EMAIL PROTECTED]>
wrote:
On Mon, Sep 11, 2000 at 07:09:08PM +0200, Jason Quigley wrote:
Does your bios have the setting memory hole at 64M activated? I'm not sure
if that's the exact opti
Debian install docs do say something about disabling all
"memory holes" in the bios. -chris
On Mon, 11 Sep 2000, Julio Merino wrote:
> On Mon, Sep 11, 2000 at 07:09:08PM +0200, Jason Quigley wrote:
>
> > Does your bios have the setting memory hole at 64M activated? I'm not sure
> > if
> > tha
On Mon, Sep 11, 2000 at 07:09:08PM +0200, Jason Quigley wrote:
> Does your bios have the setting memory hole at 64M activated? I'm not sure
> if
> that's the exact option. I only vaguely remember something like that as I
> haven't rebooted for such a long time - and sorry - I refuse to for
>
Does your bios have the setting memory hole at 64M activated? I'm not sure if
that's the exact option. I only vaguely remember something like that as I
haven't rebooted for such a long time - and sorry - I refuse to for this! ;-)
Cheers,
Jason.
--On Monday, September 11, 2000 9:20 -0700 Eri
On Wed, Aug 30, 2000 at 05:56:52PM -0600, Art Edwards wrote:
> I just purchased two Athalon-based systems, each with 768M of ram.
> However, under debian (potato runnin kernel 2.2.17) the OS sees only 65
> M of memory. I have tried to use the append command
>
> mem=768M
>
> but it still sees only
Thanks for all of the responses. It turns out that I had forgotten to
invoke /sbin/lilo after altering my lilo.conf file. the utility free
sees all of my memory now.
Sheepishly yours,
--
Arthur H. Edwards
712 Valencia Dr. NE
Abq. NM 87108
(505) 256-0834
just type exactly
append mem=768M
on a line in lilo.conf
then on / run lilo
reboot, what free command shows to you?
>
> > mem=768M
> >
> > but it still sees only 65 M?
> >
> > Does anyone have any ideas?
>
> Where are you applying the append command -- at the LILO boot prompt or
> in /etc/lilo
On Wed, Aug 30, 2000 at 05:56:52PM -0600, Art Edwards ([EMAIL PROTECTED]) wrote:
> I just purchased two Athalon-based systems, each with 768M of ram.
> However, under debian (potato runnin kernel 2.2.17) the OS sees only 65
> M of memory. I have tried to use the append command
>
> mem=768M
>
> bu
13 matches
Mail list logo
