On Wednesday 22 October 2003 05:15 pm, Terence J. Golightly wrote:
> On Wed, 2003-10-22 at 16:54, Tom Brinkman wrote:
> <snip>
>
> >     Barefoot on a tile floor is my method  ;)  If your not
> > familiar with bios ram timing options, set the ram to auto or
> > bios defaults. Cas 3, precharge 3, banking disabled are the
> > safest (but slowest) settings.
> >
> > > Memtest gave me errors in the five figure area.  I
> > > shutdown and tested each stick individually. One stick is
> > > fine and the other gave two errors in test 5. Why would I get
> > > 5 figure errors when both sticks are installed and only two
> > > when the "bad" stick in installed. If you want the
> > > particulars of the output, I'll post them it you like.
> >
> >      OK, I've been havin hardware problems myself (due to
> > overclocking too far.
>
> I was overclocking then I reset them the heat was too much.  So I
> moved the box down a floor in my house and place it in a small
> room. Much cooler here year round.

   Well, could be your problems, like mine, are from weakening the 
cpu

> >  IOW's user error, ME). I narrowed it down to
> > either my ram or the cpu has become weak. Figuring it would be
> > better to try ram first, Crucial delivered a new stick of
> > pc3200 this afternoon to replace my existing Kingston (both 512
> > MB sticks).
>
> What setting should I use for PC2700? The manual states 100mhz
> for PC1600 and 133mhz for PC2100.  I know I can run that higher,
> is trial and error the way to go here? I can only do this after
> verifying my ram.

    Your system is 133FSB (DDR 266).  
>
> > I figured if ram wasn't the problem, then at least I'd
> > have twice as much ram ;)
>
> Same thinking here!
>
> >     But, I took some precautions. First I d/l'd a 1 GB ram
> > capable kernel (2.4.22-18mdk-i686-up-4GB) an installed it.
>
> I'll check on my Mdk cds. Would I be able to urpmi it?

     You don't mention versions. 9.2 should have it. Or install the 
enterprise kernel from your CD's (any fairly recent version). Mind 
you tho, kernels capable of addressing more than 860 MB of ram are 
slower. You could be just as well off usin   mem=860M  in lilo, and 
keeping the regular kernel.


> > You'll need to
> > do the same, or add   mem=860M    to your lilo append line for
> > the kernel you're usin.  The 'regular' kernel can't address
> > 1024MB of ram.  Next I underclocked my XP 3000+ cpu to less
> > than a 2200+ to try an mitigate it as a factor when I installed
> > the new ram and tested with memtest86. First with just the new
> > stick.
> >
> >    It took 3 tries to get the new ram properly seated and the
> > system to even boot. I also had to swap slots in order to find
> > a combo that worked.
>
> I first put them in slots and 2 and 3.  Then behold I read the
> manual! and put them in the right slots together and the errors
> appeared again in #5 but in a lower memory range; within the
> range of the "good" stick.

     The manuals one thing, trial'n error is another. I use'ta have 
a Soyo BX/Intel cpu board that ram only worked in slot 2&3. Usin 
slot 1 was a no go. Often the order you put the sticks in the slots 
makes all the difference.

    Like me Terry, you might'a weakened the cpu by overclocking too 
much. Usually it's the cache areas that'll get 'migrated'. IOW's 
the traces get over resistant due to heat, over-voltage, etc. 
There's no going back. Either underclock, while still over volting, 
or replace.  I'm fixin to replace as soon as I get over myself (and 
overclocking).  It's not like the old days, these new high Ghz 
wicked fast cpu's just don't have the headroom.  After years and 
years of overclocking, I think I'll just need to settle down ;)
-- 
    Tom Brinkman                  Corpus Christi, Texas


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to