AMD 5x86/133 then parity errors

AMD 5x86/133 then parity errors

Post by Dr.Ulrich Fause » Fri, 31 Jan 1997 04:00:00



Hi,

After upgrading my 486DX2/66 to an AMD 5x86/133 and voltage regulator I
experience parity errors whenever I put something in memory bank 2.
I have 32 MB as 8 times 4 MB, five are 80ns 3 are 70 ns.
They work fine with the 486DX2/66.
Now with the AMD whenever I put only 16 MB in the lower memory bank in
whatever mixture of chips, this works fine.
But as soon as I put whatever mixture in the second bank I get parity
errors.
Sometimes immediately when booting , sometimes minutes to hours later.

Has anybody a clue what could cause this.
I think defective chips should also cause an error when they are in the
lower 16 MB.
Or are the first and second memorybanks treated differently.

BTW this happens with LINUX and WIN95

Otherwise the AMD 5x86/133 works allright.

Uli

 
 
 

AMD 5x86/133 then parity errors

Post by Jay Thorn » Fri, 31 Jan 1997 04:00:00



> Hi,

> After upgrading my 486DX2/66 to an AMD 5x86/133 and voltage regulator I
> experience parity errors whenever I put something in memory bank 2.
> I have 32 MB as 8 times 4 MB, five are 80ns 3 are 70 ns.
> They work fine with the 486DX2/66.
> Now with the AMD whenever I put only 16 MB in the lower memory bank in
> whatever mixture of chips, this works fine.
> But as soon as I put whatever mixture in the second bank I get parity
> errors.
> Sometimes immediately when booting , sometimes minutes to hours later.

> Has anybody a clue what could cause this.
> I think defective chips should also cause an error when they are in the
> lower 16 MB.
> Or are the first and second memorybanks treated differently.

> BTW this happens with LINUX and WIN95

> Otherwise the AMD 5x86/133 works allright.

> Uli

The main issue you have is speed of the chips.  The first ram bank is
probably closer electrically to the bus transcievers, so is less timing
sensitive, but the second is fairly obviously more sensitive.  At higher
speeds (and AMD's can fully saturate your memory bus, unlike 486's) you
have more problems.

My advice: Ram is cheap, buy 4 x 8 MB 60ns New Ram, and use it ONLY.
Sell your old ram to someone with a 386.
Don't mix speeds.  If you insist on using your old ram, go into your
bios and add a wait state, or two.

--

--

the Net Result System Services

 
 
 

AMD 5x86/133 then parity errors

Post by Rich McDonal » Sat, 01 Feb 1997 04:00:00



> Hi,

> After upgrading my 486DX2/66 to an AMD 5x86/133 and voltage regulator I
> experience parity errors whenever I put something in memory bank 2.
> I have 32 MB as 8 times 4 MB, five are 80ns 3 are 70 ns.

One other thing to check:  make sure your new voltage regulator is
getting the proper voltage to the CPU, preferably within tolerance on
the high side.  I.e. 3.6V for a 3.45V AMD 5x86/133ADW.  I have had a bad
experience in that the CPU runs fine on the low side, but the connected
periperal chips were not getting what they perceived as a proper logic 1
voltage.

Cheers,
Rich

 
 
 

AMD 5x86/133 then parity errors

Post by Erik Ratclif » Sun, 02 Feb 1997 04:00:00


: After upgrading my 486DX2/66 to an AMD 5x86/133 and voltage regulator I
: experience parity errors whenever I put something in memory bank 2.

You may want to pop into your CMOS setup and change your write cache wait state to 1.  That may help.

 
 
 

AMD 5x86/133 then parity errors

Post by Dr.Ulrich Fause » Tue, 04 Feb 1997 04:00:00



> Hi,

> After upgrading my 486DX2/66 to an AMD 5x86/133 and voltage regulator I
> experience parity errors whenever I put something in memory bank 2.

Well thanks to everybody who answered.

Changing my waitstate from 0 to 1 really helped and it's now working
without crashing.

Thanks
ULI

 
 
 

1. AMD 5x86-P75 S (133 MHz) and seg faults

Greetings -
  I have been trying for several weeks to install linux on a shiny
new machine running on an AMD 5x86-133 processor, unfortunately,
the machine dies, often during boot, sometimes on exiting fdisk, and
if not then, then after rebooting when I try to run mke2fs... I have
been using a modified version of the Slackware distribution, with
a 2.0.0 kernel.  I have even tried to change motherboards (someone
indicated to me that this might be the problem...), but to no avail.
Currently, the motherboard is a Soyo SY-4SAW2 with an SiS 85C496
chipset.  Common errors have are:
 Segmentation fault, unable to handle kernel paging request at
virtual addres (x), idle task may not sleep (about five times),
and several others.  Any ideas would be greatly appreciated...

   Thanks in advance,

      Bryan Jurish

        -(using my girlfriends account at the moment - mail to

2. Pan-0.13.91 Released....

3. AMD 5x86/133 doesn't boot Linux 2.0.29

4. USB flash reader

5. AMD 5x86-133: Will it run Linux???

6. Changing Netscape Enterprise Server 4.1 Banner String

7. AMD 5x86 133 problems

8. Qt lib tutorial needed

9. set6x86 and AMD 5x86-133

10. AMD 5X86-133 CPU and Linux ?

11. SOLVED: Booting AMD 5x86/133 on linux

12. AMD 5x86/133 & Locking problems

13. Spooging over BogoMips / AMD 5x86-133