Just received my memory from usa, finally got here. Its 2 x 1gb sticks on infineon. My A1 is a G4 800mhz using on board IDE, 512mb ram

Just plugged in the new ram and uboot shows both sticks, thus 2gb :D but once it gets to the boot menu, it finds a device but then lists loads of 'bad checksum at block **" is there an issue when changing mem.

I havnt yet tried boot off a cd.

_________________
Cross-developer on Windows, OS3, OS4, Linux; Current Projects:-
Nephele Cloud App OS4
UserProfile System OS4
AmigaOneXE OS4.1.6

TaoSoftwareBlog Youtube

@TheAMIgaOne

Do the usual test and only use one at a time first.

_________________
A1/G4 1GHZ

OS4.1 latest update.
1ghz Radeon Club3d 9250
Usb/Dma fixed.

@TheAMIgaOne

Yes the AmigaONE-XE is picky about ram, and I also think it's easier to get it to work whit one large one then with two.

There is a RAM test in UBOOT, and also there is a RAM test tool on OS4Depot.net.

Last edited by NutsAboutAmiga on 02-Mar-2013 at 02:33 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Well I can now say Im writing this using the 2GB :D

I got four sticks on 1gb, so I went the long way round of installing my sil card(not yet managed to get it working properly) to see if that helped, well I got further than before, it booted to OS4 splash screen, then went to hyperion disk insert screen. So went back to onboard IDE and changed both mem sticks to the other two sticks and worked first time lol

PS im starting to beleive my HDD is failing, had block errors show in the past and again now, so this could of been the problem all along.

Il do some more in-depth checks on there other two sticks, then i'll hopefully have two more 'testing working' sticks to sell if any A1 users need them.

Last edited by TheAMIgaOne on 02-Mar-2013 at 02:45 PM.

_________________
Cross-developer on Windows, OS3, OS4, Linux; Current Projects:-
Nephele Cloud App OS4
UserProfile System OS4
AmigaOneXE OS4.1.6

TaoSoftwareBlog Youtube

@TheAMIgaOne

Good luck with your tests! And if it comes that all the sticks work I would be interested to get one or two if sou sell them, have that in mind and PM me :)

_________________
Peg1, Peg2, Efika,
Amiga 500, Amiga 1230,
Amiga 4000PPC,
Sam 440EP, AmigaOne XE,
MacMini PPC, PowerMac G4, G5

@TheAMIgaOne

Well its strange that your HD is failing just when installed some new memory sticks, but good luck, whit project, I hope you get it working.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

Quote:

There is a RAM test in UBOOT

Is this located in the u-boot menu or is it done through command line?

_________________
Peg1, Peg2, Efika,
Amiga 500, Amiga 1230,
Amiga 4000PPC,
Sam 440EP, AmigaOne XE,
MacMini PPC, PowerMac G4, G5

@Morphix

The command in uboot is “mtest”, type “help mtest” for more information.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

yep did the mtest and that was fine.

My hdd was throwing occasional block errors since ive been using it more in the last 2months. But the last couple of days Ive been chucking a load of 650mb isos on my workbench partition so this may have brought out the other errors.

Extra note, during a block error just now it came up with a SFS Partion warning saying its unavailable, then rebooted to find my Workbench uninitilized. So im atm running on an OS4.0 partition before I install os4.1 again

I think somewhere the mem has sped-up the os, which could be why the hdd errors are more pronouced.

_________________
Cross-developer on Windows, OS3, OS4, Linux; Current Projects:-
Nephele Cloud App OS4
UserProfile System OS4
AmigaOneXE OS4.1.6

TaoSoftwareBlog Youtube

@TheAMIgaOne

The memory test should take long time to finish, so that was quick.
Good time to take backup, I think.

Last edited by NutsAboutAmiga on 02-Mar-2013 at 05:40 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@TheAMIgaOne

I have been facing similar random block errors on my Hard Disk, plus my boot System partition was not initialized completely on boot, I mean OS 4.1 would start to boot but then the gray screen and this error window would pop up -can not remember the message right now it was sure a block error or an initialization fail error-.

I used the Partition check and fix utility found on the 4.0 & 4.1 CD. This solved the problem quite well I believe. It has been a long time since I face such errors.

_________________
Peg1, Peg2, Efika,
Amiga 500, Amiga 1230,
Amiga 4000PPC,
Sam 440EP, AmigaOne XE,
MacMini PPC, PowerMac G4, G5

Grab memtester off Depot, http://os4depot.net/share/utility/hardware/memtester.lzx

The test will do a full test & start over again, takes a long time to test the memory, but if it completes 1 pass without errors, I consider the stick good.

_________________
Hate tends to make you look stupid...

@sundown

I used memtester recently and it did not take that much time. I executed it booting with no startup sequence.

_________________
Peg1, Peg2, Efika,
Amiga 500, Amiga 1230,
Amiga 4000PPC,
Sam 440EP, AmigaOne XE,
MacMini PPC, PowerMac G4, G5

@Morphix

Seems like i didnt finish mtest, (may of typed in the wrong command)

I been working back on my 512mb(working stick) and seems the only error that was showing up using the new sticks now shows up on my old stick.

A window showing

'Smart FileSystem Request'

The was an error while accessing this volume:

Volume 'AmigaOS416' (os416: a1ide.device. unit 0)

General device failure
The disk is in an unreadable format

errorcode = 20
io_command = 4
io_Offset = 1525871616
io_length = 0
io_actual = 11

Which is weird because the actual partition I was accessing which showed a block read error just before was my Recovery: partition, which is still FFS2

So although there was an error on one partition(recovery:), its destroyed a SFS workbench partition.

I think we need that MCP feature that stops the RDB being overwritten (unless we allow it)

_________________
Cross-developer on Windows, OS3, OS4, Linux; Current Projects:-
Nephele Cloud App OS4
UserProfile System OS4
AmigaOneXE OS4.1.6

TaoSoftwareBlog Youtube

@TheAMIgaOne



Update:

When I run memtester booting with no startup-sequence straight form shell it take a little time to finish, running it form Workbench -under shell window- from inside OS4 it really takes a lot of time, still is running under my A1.


A window showing

'Smart FileSystem Request'

The was an error while accessing this volume:

Volume 'AmigaOS416' (os416: a1ide.device. unit 0)

General device failure
The disk is in an unreadable format

errorcode = 20
io_command = 4
io_Offset = 1525871616
io_length = 0
io_actual = 11
Quote:

TheAMIgaOne wrote: @Morphix Seems like i didnt finish mtest, (may of typed in the wrong command) I been working back on my 512mb(working stick) and seems the only error that was showing up using the new sticks now shows up on my old stick. A window showing 'Smart FileSystem Request' The was an error while accessing this volume: Volume 'AmigaOS416' (os416: a1ide.device. unit 0) General device failure The disk is in an unreadable format errorcode = 20 io_command = 4 io_Offset = 1525871616 io_length = 0 io_actual = 11 Which is weird because the actual partition I was accessing which showed a block read error just before was my Recovery: partition, which is still FFS2 So although there was an error on one partition(recovery:), its destroyed a SFS workbench partition. I think we need that MCP feature that stops the RDB being overwritten (unless we allow it)

I guess this is a hard disk error and not a memory one. Is memtester testing hard disks as well?

_________________
Peg1, Peg2, Efika,
Amiga 500, Amiga 1230,
Amiga 4000PPC,
Sam 440EP, AmigaOne XE,
MacMini PPC, PowerMac G4, G5

@Morphix

Quote:

I guess this is a hard disk error and not a memory one. Is memtester testing hard disks as well?

When you read your disk, it puts the read block into memory, this where the CRC etch is checked, so when your getting a read/write error it not only testes you HD, but your RAM as well.

And if RAM that contains a block or cylinder you have read and modified is corrupted in RAM before its being written to to disk, so now you get two problems instead of just one.

Slowly your HD might get more and more corrupted, because the RAM is corrupted.

Its more likely it just trash the content of partitions at random places (or depending on files you modify), not so likely its going to overwrite the RDB or partition table, unless you mess whit Media Toolbox.

Last edited by NutsAboutAmiga on 03-Mar-2013 at 01:48 PM.
Last edited by NutsAboutAmiga on 03-Mar-2013 at 01:41 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@TheAMIgaOne

Quote:

Volume 'AmigaOS416' (os416: a1ide.device. unit 0) General device failure The disk is in an unreadable format errorcode = 20 io_command = 4 io_Offset = 1525871616 io_length = 0 io_actual = 11 Which is weird because the actual partition I was accessing which showed a block read error just before was my Recovery: partition, which is still FFS2 So although there was an error on one partition(recovery:), its destroyed a SFS workbench partition. I think we need that MCP feature that stops the RDB being overwritten (unless we allow it)

The RDB is NOT located at io_Offset = 1525871616,

its located at the start of the disk, io_Offset = 0, Followed by the partition table at io_Offset = 512, 1024, 1536, ...

Last edited by NutsAboutAmiga on 03-Mar-2013 at 01:32 PM.
Last edited by NutsAboutAmiga on 03-Mar-2013 at 01:32 PM.
Last edited by NutsAboutAmiga on 03-Mar-2013 at 01:31 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Well as mentioned Im back on my original 512mb ram and im still getting more errors, ive even got some on my old OS4.0 partition is now showing errors.

True the RDB would be at the base and would kill all partitions if overwritten. The error points to the location on my os416: partition, I have about 4 partitions before that one.


Well, back to mtest, seems before I used the 'post memtest' which was alot shorter,

thus using Mtest on my A1 with 1gb, a write/read cycle lasts 9-10secs, at which im now on pattern 6FA = (1786 * 2 ) * 10 secs = So its been running for 8-9 hours, and so far no errors with just the 1gb stick.

Im getting out an old storage HD(pc storage) so once I clear it out Il try a reinstall on that one.

I worked out that my current HD could be around 7-8 years old, so its done well lol

Last edited by TheAMIgaOne on 03-Mar-2013 at 03:55 PM.

_________________
Cross-developer on Windows, OS3, OS4, Linux; Current Projects:-
Nephele Cloud App OS4
UserProfile System OS4
AmigaOneXE OS4.1.6

TaoSoftwareBlog Youtube