2013-01-28, 16:17
(2013-01-28, 16:11)MilhouseVH Wrote: The problem being that the Pi may already be overclocked by the time it works out it needs to perform an update of the SD card (certainly if initial_turbo is specified) and would then have to modify config.txt in an overclocked state - thus writing to the SD card, and potentially corrupting config.txt - in order to disable overclocking for the next boot...You can disable overclock at runtime by switching governor from ondemand to conservative.
Either suggest people with sdcard corruption problems avoid initial_turbo, or include a (up to 60 second) delay before updating firmware if initial_turbo is in config.txt.
(2013-01-28, 16:11)MilhouseVH Wrote: It seems that writing to the SD card is pretty safe provided that it has been initialised correctly, and the fact that it sometimes isn't initialised correctly is the crux of the problem. Automatically rebooting the Pi when the SD card isn't initialised properly is the workaround that works for me.Have you changed the kernel, or the init script to do this? Can you post your change?
