@amigakit

Wow! There is memtester OS4 port in os4depot from Stephan Rupprecht now.

@mlehto

Thanks I will test with this port and check the memory out. Watch this space...

_________________
Amiga Kit Amiga Store
Links: www.amigakit.com | New Products | A600GS

@thread

Don't want to step on anyones toes here but if someone wants to take a chance Komplett.se (I'm pretty sure they would take back anything that didn't work as long as you pay for shipping costs of course) is selling Crucial SO-DIMM PC133 512MB CL3 144pin. Non-parity, 3.3V, 64Meg x 64, 7.5ns for 995:- skr. They claim 36 in stock. Shipping costs would be extra though.

Of course the extra 400:- skr could be worth it knowing that it works!

Last edited by Steff on 12-Apr-2005 at 01:49 AM.

_________________
Fixed A1G4XE 7455 RX933PC with fried CPU
Sapphire Radeon 9100 128mb
ESI Juli@ 24bit 192kHz Envy24HT
Sil 680 Ultra Ata 133 E-ide
SeaGate Barracuda 120gb 8mb cache

@amigakit

I just ram "Memtester" for a while on my µA1. I'm getting errors
reported for my 512MB upgraded µA1. I'm not going into panic mode
until I see someone reporting a 100% error free memory test on
a 512MB µA1. Please keep us posted.

By the way, MemTester doesn't seem to be able to access all 512MB
for testing. I got it to work with 300MB and will see just how much
it will grab for testing above that when I get home tonight.

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic

Obviously it won't be able to test all 512Mb, it depends how the OS has divided it up and how much of it is used.

_________________
Playstation Network ID: xeron6

@Steff

I will test a Crucial 512mb sodimm soon and will report here...

_________________
-------------------------------
AmigaOS, the last hope...

@Xenic

Quote:
By the way, MemTester doesn't seem to be able to access all 512MB

It is not very important, if you test memory compatibilty rather than memory stick health (AFAIK).

Anyway if it gives errors with some setup, it tells that memtester will catch faulty/incompatible memory in some cases...


My Kingston KVR133X72RC3/512 seems to be ok. At least memtester won't report any errors after 8 hours of testing. I continue later next night ...

My setup is G3-SE 666/133

Last edited by mlehto on 12-Apr-2005 at 10:06 PM.
Last edited by mlehto on 12-Apr-2005 at 09:42 PM.

@mlehto

To ppl who report here.

It should be usefull to know, what setup ppl have, MoBo/CPU/Memorystick.

@mlehto

I'm running Memtester on a µA1 with 512MB memory from Software Hut.
I don't know how to tell if my processor is GX or FX.
If anyone else reports good results on a µA1 I'm going to replace the
memory with the original 256MB memory. Since I got errors from a single
run, I don't see any point in an extended run.

Here are my results:

memtester 315 1
memtester version 4.0.5 (32-bit)
Copyright (C) 2005 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesizemask is 0xfffff000
want 315MB (330301440 bytes)
got 315MB (330301440 bytes), trying mlock ...failed for unknown reason.
Continuing with unlocked memory; testing will be slower and less reliable.
Loop 1/1:
Stuck Address : ok
Random Value : ok
FAILURE: 0x818a0087 != 0x81aa0087 at offset 0x0029a8f0.
FAILURE: 0x80259a38 != 0x80059a38 at offset 0x00421da2.
FAILURE: 0x052c18bf != 0x050c18bf at offset 0x009403a2.
FAILURE: 0xa1ae1a86 != 0xa18e1a86 at offset 0x016f92f2.
FAILURE: 0x43081387 != 0x43281387 at offset 0x01e825b0.
Compare XOR : FAILURE: 0x61ab768e != 0x61cb768e at offset 0x0029a8f0.
FAILURE: 0x6047103f != 0x6027103f at offset 0x00421da2.
FAILURE: 0xe54d8ec6 != 0xe52d8ec6 at offset 0x009403a2.
FAILURE: 0x81cf908d != 0x81af908d at offset 0x016f92f2.
FAILURE: 0x2329898e != 0x2349898e at offset 0x01e825b0.
Compare SUB : FAILURE: 0x68583c96 != 0x43f83c96 at offset 0x0029a8f0.
FAILURE: 0xa7588863 != 0xcbb88863 at offset 0x00421da2.
FAILURE: 0xc016b4ee != 0xe476b4ee at offset 0x009403a2.
FAILURE: 0xbf6eafb9 != 0xe3ceafb9 at offset 0x016f92f2.
FAILURE: 0x1608a396 != 0xf1a8a396 at offset 0x01e825b0.
Compare MUL : FAILURE: 0x00000001 != 0x00000000 at offset 0x0029a8f0.
FAILURE: 0x00000001 != 0x00000002 at offset 0x00421da2.
FAILURE: 0x00000000 != 0x00000002 at offset 0x01e825b0.
Compare DIV : FAILURE: 0xfd67cc51 != 0xfd67cc53 at offset 0x00421da2.
FAILURE: 0xfd67cc51 != 0xfd67cc53 at offset 0x01e825b0.
Compare OR : Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

Done.

MemTester brings up a Reaper if I quit with Ctrl-C and when it's
done with the test.

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic

Do you memory stick have name/manufacturer/ID number ??

Quote:
I don't know how to tell if my processor is GX or FX.

uboot menu -> system information ??


Quote:
Since I got errors from a single run, I don't see any point in an extended run.

That's right. I don't know, how much it counts to make long period tests after all, because this tests compability. If you test old memory sticks, one particular memory address can work or fail randomly. Better safe than sorry anyway.


Quote:
MemTester brings up a Reaper if I quit with Ctrl-C and when it's done with the test.

Same here, I think that it is "normal"

Last edited by mlehto on 13-Apr-2005 at 01:35 AM.

@mlehto

OK. I checked the processor and its a "GX".

Why am I the only one posting results? This is getting to be a big
problem for me. I get very litle response when I request confirmation
with µA1 problems. Where are all the µA1 users hiding?? I got the
same lack of response when I asked people for diskspeed results
for FFS filesystem.

After the results I posted earlier, I removed my 512MB memory and
replaced it with the original 256MB SODIMM. Naturally I had to
request a smaller chunk of memory for testing. Here are the results
for the original 256MB memory:

memtester 140 1
memtester version 4.0.5 (32-bit)
Copyright (C) 2005 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesizemask is 0xfffff000
want 140MB (146800640 bytes)
got 140MB (146800640 bytes), trying mlock ...failed for unknown reason.
Continuing with unlocked memory; testing will be slower and less reliable.
Loop 1/1:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

Done.

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic

Quote:
Why am I the only one posting results?

Good question ...

I asked couple of friends to test and send results. So they will make it, when they have time

Will you please send model number of memory sticks ?

Last edited by mlehto on 13-Apr-2005 at 07:05 PM.

@mlehto

I have only 256MB of memory on mA1...so far my tests have been succesful (memtester 100 1), but pressing Control-C causes recoverable alert and after I finished last test (1 loop) I got DSI exception.

@Mr_Capehill

Good.

I get Grim also, so there is bug somewhere. I think, that it won't affect to results.

With ctrl-c I get Elf Library requester, unknown/unsupported Reloc.

@Xenic
Quote:

Why am I the only one posting results?

I have a uA1 with a Kingston 512M ram module. I've downloaded memtest and
I'll run it and post results after I get home from work.

_________________
Kevin - X1000 First Contact / uA1

@ktadd

Thanks. I'd just like to add that the results turn out to be meaningful
in real-world use. i just spent the last 2 weeks trying to get Linux
installed on my MicroA1-C with no success. After spending hours redoing
the installation, writing messages to various mailing lists and trying
the suggestions I discovered that the problem was the 512MB memory.

Someone on one of the lists stated that the installation would not work
on an A1XE if the memory wasn't 100% good, so when I saw someone mention
MemTester on this forum I decided to try it. As you can see from the
results, my memory showed up as bad. When I replaced the 512MB memory
with my original 256MB memory, the Debian Linux installation works!!

I purchased my memory from an Amiga dealer to be sure I got good memory.
Apparently, some dealers aren't testing the memory enough. Needless to
say, I'm really pissed that I had to waste so much time on this crap
memory.

I think this thread was started by someone offering µA1 memory for sale.
I hope that person is going to be honest with us and let us know how
his memory does when tested with "MemTester".

_________________
X1000 with 2GB memory & OS4.1FE

I have a GX µA1 with the standard Apacer 256MB module.
I thought I'd do a test anyway. This module does not seem
to give any complaints


/Harry

_________________
/Harry

[SOLD] µA1-C - 750GX 800MHz - 512MB - Antec Aria case

Avatar by HNL_DK!

@Samwel

Could people that do tests with their modules PLEASE add the results
to Intuitionbase compatibility list?


/Harry

_________________
/Harry

[SOLD] µA1-C - 750GX 800MHz - 512MB - Antec Aria case

Avatar by HNL_DK!

Here's my test on a µA1 with 750GX & 256Mb.

pagesizemask is 0xfffff000
want 133MB (139460608 bytes)
got 133MB (139460608 bytes), trying mlock ...failed for unknown reason.
Continuing with unlocked memory; testing will be slower and less reliable.
Loop 1/1:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

Done.

_________________
Hate tends to make you look stupid...

Here are my results. I only ran 1 loop as that's all I have time for right now.
I have a uA1 with GX processor. The RAM is a 512M Kingston Technology KTM-TP133/512
module purchased from Software Hut.

pagesizemask is 0xfffff000
want 300MB (314572800 bytes)
got 300MB (314572800 bytes), trying mlock ...failed for unknown reason.
Continuing with unlocked memory; testing will be slower and less reliable.
Loop 1/1:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

Done.

_________________
Kevin - X1000 First Contact / uA1