Maybe Joerg had point the right problem. I was just wondering if you
could get a 1Gb memory module to test and could so discard any possibility
of being the mobo the origin of your problems.
On Fri, 7 Mar 2003, Adrian Golumbovici wrote:
> Also I checked and mem=960M doesn't help and the enterprise kernel has same
> problem. I tried lowering the mem value even further and with 900 didn't
> work. With 800 it worked (both distro kernel and enterprise). :/
>
> > Here is an answer I got from someone trying to help. If there is a fault
> in
> > high-mem maybe someone could fix this before the release?
> >
> > On the other hand, Joerg since you seem to know more about this problem,
> > could you post it as a bug in the mandrake bugzilla?
> >
> > I would really like to see this thing fixed before the release or this
> > release will be useless to me. :(
> >
> > Thanx Joerg for the info.
> >
> > > Hi Mate,
> > >
> > > the problem is known (Well, to me at least).
> > > Give at the command line mem=960M and the problem should go away. It's
> the
> > > High-mem stuff that is faulty. I did circumvent that problem in the past
> > > this way. I had recompiled my own kernel, but don't know what patch I
> > > added by that time to fix it (Having a Netserver LH4 with 2 GByte of Ram
> > > and Raid5).
-----------------------
Alan Wilter S. da Silva
-----------------------
Laborat�rio de F�sica Biol�gica
Instituto de Biof�sica Carlos Chagas Filho
Universidade do Brasil/UFRJ
Rio de Janeiro, Brasil
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
