>64MB mem read fail

>64MB mem read fail

Post by klum.. » Thu, 31 Aug 2000 04:00:00



I'm running Redhat 6.2 with kernel 2.2.14-5.0, and my system doesn't
detect memory above 64mb (I have 256).

My config:
Abit BE6-II, 660Mhz P-III (6 X 110Mhz bus)
256 mb RAM (in 2 PC133 128mb chips)
2 HDs, 4 and 7GB
nVidia TNT2 ultra (Diamond Viper 770)

my Output from free is still only 64mb total physical memory, and the
total 263mb swap (2 partitions)

I've tried compiling 2.2.14 again, and tried running 2.2.16 also. On the
other hand if I run 2.4.0 test7 the kernel detects the right amount of
RAM.

Any Ideas?

Regards
Klumhru

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

>64MB mem read fail

Post by Sven Bovi » Thu, 31 Aug 2000 04:00:00



> I'm running Redhat 6.2 with kernel 2.2.14-5.0, and my system doesn't
> detect memory above 64mb (I have 256).

> My config:
> Abit BE6-II, 660Mhz P-III (6 X 110Mhz bus)
> 256 mb RAM (in 2 PC133 128mb chips)
> 2 HDs, 4 and 7GB
> nVidia TNT2 ultra (Diamond Viper 770)

> my Output from free is still only 64mb total physical memory, and the
> total 263mb swap (2 partitions)

> I've tried compiling 2.2.14 again, and tried running 2.2.16 also. On
> the
> other hand if I run 2.4.0 test7 the kernel detects the right amount of
> RAM.

> Any Ideas?

> Regards
> Klumhru

Add
  append="mem=256M"
to your lilo.conf and rerun lilo.
This is, BTW, a vFAQ (very Frequently Asked Question).

--
-----------------------------------------------------------
     sven dot bovin at chem dot kuleuven dot ac dot be
-----------------------------------------------------------

 
 
 

>64MB mem read fail

Post by klum.. » Thu, 31 Aug 2000 04:00:00





> > I'm running Redhat 6.2 with kernel 2.2.14-5.0, and my system doesn't
> > detect memory above 64mb (I have 256).

> > My config:
> > Abit BE6-II, 660Mhz P-III (6 X 110Mhz bus)
> > 256 mb RAM (in 2 PC133 128mb chips)
> > 2 HDs, 4 and 7GB
> > nVidia TNT2 ultra (Diamond Viper 770)

> > my Output from free is still only 64mb total physical memory, and
the
> > total 263mb swap (2 partitions)

> > I've tried compiling 2.2.14 again, and tried running 2.2.16 also. On
> > the
> > other hand if I run 2.4.0 test7 the kernel detects the right amount
of
> > RAM.

> > Any Ideas?

> > Regards
> > Klumhru

> Add
>   append="mem=256M"
> to your lilo.conf and rerun lilo.
> This is, BTW, a vFAQ (very Frequently Asked Question).

> --
> -----------------------------------------------------------
>      sven dot bovin at chem dot kuleuven dot ac dot be
> -----------------------------------------------------------



append="MEM=256M"
What I should have written:
append="mem=256M"

My mistake.

Regards
Klumhru

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

>64MB mem read fail

Post by Chuc » Thu, 31 Aug 2000 04:00:00



> This is, BTW, a vFAQ (very Frequently Asked Question).

2nd time in 2 days, 3rd time in a week :)
 
 
 

1. >64MB mem problem - why not fix it?

I'm very curious about why Linux only recognises 64MB RAM?
I know that there's a limitation in the method Linux uses to
get the RAM-size, but then USE ANOTHER METHOD!

My BIOS counts up to 96megs when I boot, NT finds 96 megs whithout
any help, so why could Linux not accomplish this too?

//Marcus
--
-------------------------------+------------------------------------
        Marcus Sundberg        | WWW: http://www.e.kth.se/~e94_msu/
 Royal Institute of Technology |       This space for rent...

2. mod_rewrite + VirtualHost

3. Newbie Questions (ICEWM Background, ppp question, mem > 64mb)

4. Upgrading and re-make world guranteed to work ?

5. request help w/lilo.conf and mem > 64mb

6. Retrieving Ports from behind a proxy/fw

7. HW slowdown w/mem>64Mb

8. Inittab?

9. Q: 128 MB, 64MB cachable -> 64MB RAM disk, swap space?

10. VM fails when real mem >32 M.

11. A <= ping => B => OK A <= TCP => B => FAILS

12. rpc.mountd: getfh failed: Operation not permitted ( WinNT -> samba -> Linux -> NFS -> Solaris)

13. tadpole 64mb mem simms