@mlehto

Quote:

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

...and here's my "contribution" to this thread... After about 12 hours and 22 loops, everything is still OK. I guess that the stick Eyetech recommended is good...

(A1XE-G4@1066MHz, Kingston KVR133X72RC3/512)


Regards,
Pekka

@all

I have a question. I'm going to test my ram, i have 1GB on my A1.

What do i need to type? memtest and how many MBs?

I tried with 32 and got errors but i was using some programs, so i reset my A1 and start with only 4 MB... so far no errors. Do i need to test for example 700MBs? How long does it takes?

_________________
ikir

@ikir

I used trial and error to see how much memory I
could specify and have the test start immediately.
With my 512MB module the max I could enter was 315
but I ran the posted test using 300. With the 256MB
module the max I could enter was about 144 but I ran
the test with 140. I think entering half the actual
size of the actual installed memory will work. Above
that you just have to try and see. If you enter a
number and the program stalls for a few minutes then
you might want to try a lower number.

The test took about a half hour for one run with 512MB.

_________________
X1000 with 2GB memory & OS4.1FE

@ktadd & sundown

Thanks for posting your results. At least it looks like the 256MB
that comes with the µA1 is good for everybody. Apparently, Software
Hut has several batches of memory because mine is not marked anywhere
as Kingston. The only name I can find on it appears to be "WINTEC".
I suppose any name with "Win" in it is a bad sign

I just sent the bad memory back to Joe and I'm sure he'll get me a
good one. Apparently, the effects of the bad memory are not always
apparent if you're just using OS4. I don't think it comes into
play until you use programs that grab most available memory. My
system does seem more stable now that I've switched back to the
original 256MB module.

I can say that the bad memory completely prevented me from installing
Debian Linux. Hopefully the "MemTester" program will save some people
the anguish I experienced trying to install Linux. If the memory fails
the memory test you're probably not going to have very good luck
installing Linux.

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic

Yup, Debian doesn't like dodgy memory. That caused a lot of bad language on the A1g3se dev list, when we realised just how much poor quality RAM is out there.

Anyway, I've got a question: has anyone with a µA1 tried out RAM compatible with G3 iBooks?

You see, I was just upgrading a dual-USB model, and I noticed that the chips on the 256Mb SODIMM were exactly the same as on the Apacer sticks that come with the µA1-C.


EDIT
The Apacer stick seems to work quite happily with the iBook (just running memtester to be sure).
Next step, get a 512 Mb stick for iBooks from Crucial and see if it's compatible with the µA1.
Although the G3 iBooks only have a 100 MHz bus (yes, Macs have always had slow buses compared to the rest of the work), the stick itself is PC133.
And if by pure bad luck it doesn't work (bet it will, though), I'm going to have one happy iBook

Last edited by anarchic_teapot on 14-Apr-2005 at 08:17 PM.

@ikir

I think...

If you test compability, it is more or less same, if you test only 4 MB (memtester 4 1 ).

If you want test your memory stick physical condition, test as much as you can allocate. If you try to get more than is avail, it just jams in very start.

700 MB, how long it takes ? Don't know, I test 300 MB and it took maybe 10-15 minutes.

@Pecosbil

Nice to see you around here !

Results were exepted, but it hurts nothing

@thread

Don't know if this is of interest to anyone but I tested my AOne XE G4 clocked to 1066 mHz with one stick 512mb Twinmos unregistered pc 133 memory:

2.System:Tools/memtester-4.0.5> memtester 256 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 256MB (268435456 bytes)
got 256MB (268435456 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.

It took a while but I guess it's because of mlock failure (for unknown reason)!

In general I have had no problems with my memory that I have noticed (which doesn't say much).

_________________
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

@Thread

Sometimes bad quality PSU causes phantom probs specially with memory.

@mlehto

So at this time we have these 512MB modules comfirmed to work.

µA1:
Kingston KTM-TP133/512 (ktadd)

XE/SE:
Twinmos 512MB unregistered pc 133 memory (No modelname by Steff)
Kingston KVR133X72RC3/512 (Pecosbil & mlehto)


Also GGS-Data and AmigaKit are selling other unknown models which are
claimed to work.


/Harry

_________________
/Harry

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

Avatar by HNL_DK!

Btw have anyone tested this cheaper variant of PC133 SODIMM
that Kingston sells? It has the same specs CL3, PC133 and so on..

KVR133X64SC3/512

The KTM series are 50% more expensive than the KVR (Kingston Value RAM).
This model could actually work as the KVR model works ok on the XE it seems.


/Harry

_________________
/Harry

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

Avatar by HNL_DK!

@all

IMPOSSIBLE! I got several failure allocating 700MB. Teorically my memory modules aren't A1 cmpatible but i have a rock stable OS4. I have pratically 0 problems.
The thing is not working is Debian that freeze.

I'm shocked. Maybe i have one working module and the other not?

I have 2 512MB.

_________________
ikir

@ikir

What's the largest free block when typed 'avail'?

@ikir

You should test memory sticks one by one, ie. remove other and test remaining, swap them etc.

If you want get as much free memory as possible, boot without startup-sequence and run test for all free memory. I will check today evening/night, how it works.

Yes, it is possible, that other stick is broken.

edited:typos

Last edited by mlehto on 15-Apr-2005 at 10:13 AM.

@mlehto

Yes, i'm testing stick one by one. Maybe both works, but they are from different manufacter and A1 is very picky with memory.....
I'll write my result later.

PS: OS4 is rock solid also with bad memory lol


@Mr_Capehill
Now i can't i'm trying only one stick.

Last edited by ikir on 15-Apr-2005 at 10:37 AM.

_________________
ikir

@ikir

And you ARE of course limiting the amount of memory seen by Debian to not be more than around 700MB?

_________________
This weeks pet peeve:
Using "voltage" instead of "potential", which leads to inventing new words like "amperage" instead of "current" (I, measured in A) or possible "charge" (amperehours, Ah or Coulomb, C). Sometimes I don't even know what people mean.

@ikir

Maybe because you dont access faulty one ?? Ie. first 512 MB is ok... ?


Off topic, close your eyes or skip this part ... I got Abit KG7-RAID board with Athlon 1800+ XP and two 512 MB DDR sticks. I'm not problem free with them either. Bulk read and write fails ... memory speed is 520 MB/s, wich is really low for 266 MHz bus ...

Back to topic ... do you have two unreg unbuff sticks ?

@olegil

Is that 768 MB limit only in debian or is it general limitation of gnu/linux ??

@Samwel

OK you forced me to take action, I guess the system can't be up forever!

So it says PC133 512mb SDR/Cl3 no simple modell # or name but a whole slue of numbers that would take too much of my and your time to bother.

_________________
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

@ikir

I tested it and I cannot allocate anything over free virtual memory. I can save some 20 MB booting without startup-sequence. With single 512 MB stick I have 325 MB free virtual.