pmk wrote:If you could post some instructions on how to test and get the information you need I can do some testing over the next days or two as got some free time.
Are you currently suffering from corruption when overclock is enabled?
If so, start find the lowest overclock settings (from raspi-config) that causes corruption.
Find some activity that causes corruption. I believe running xbmc and scanning your media library is a good example.
Anything that causes the CPU to be busy (and so causes overclock to be enabled), and writes to sdcard should be a candidate.
The overclock consists of 4 lines in the config.txt file. E.g.
Try turning them down to default, one at a time. Default is:
I would suggest changing them in the order:
sdram_freq->400, core_freq->250, arm_freq->750, over_voltage->0 (this may need some of the previous 3 settings to be lowered to boot correctly).
As the corruption may cause the sdcard to not boot, you probably need to reimage the sdcard after each failure.
Boot up and use raspi-config to select an overclock level (the lowest that causes corruption). Don't reboot, but type in:
and edit the overclock setting you are currently testing to the lower value. Then:
See if you can cause the sdcard to be corrupted.
I'd like to know which of the overclock settings are necessary for corruption to occur.