Posts: 487
Joined: Jul 2012
Reputation:
6
2012-10-17, 21:50
(This post was last modified: 2012-10-17, 21:50 by fernandovg.)
But is it really a XBMC error?
If its not assigned to anyone, how an updated version will have the fix for it?
thks
Posts: 487
Joined: Jul 2012
Reputation:
6
Ok, sorry. I didn't know about that. thanks for enlighten me
Posts: 137
Joined: Aug 2012
Reputation:
2
2012-10-18, 09:41
(This post was last modified: 2012-10-18, 15:49 by Wanderlei.)
With new 512mb board I keep getting corrupted files.
With r12015 and latest start.elf, boots fine but on reboots it gets stuck at the logo screen, 'error cannot mount such and such'. Re-imaged and kept trying but it continued to happen.
Tried r12089 which is the latest I could find but it didnt have a start.elf for 512mb boards, updated to new start.elf and it wont boot at all, passes splash screen but stays black, Any overclocking via config.txt results in corruption, needs to be re-imaged.
Edit
I did have a bit more success with going back to a earlier revision of OpenELEC (r12015)
R-Pi 512mb
arm_freq=800
sdram_freq=450
core_freq=300
gpu_freq=300 Works
arm_freq=850
sdram_freq=450
core_freq=325
gpu_freq=325 Works
arm_freq=900
sdram_freq=500
core_freq=350
gpu_freq=350 Corrupts Files
I went back again to r12089 but it still continues to never boot up with anything other than the start.elf it comes packaged with and any overclock corrupts.
I think its a case of my new 512mb being a bit less overclockable and revisions of OpenELEC being temperamental about using start.elf, loader.dol, bootcode.dol that dont come packaged with that revision.
Although with older start.elf on 256mb board I never experience any file corruption from overclocking. It was just a matter of changing config.txt and rebooting to recover, now I only way I know to recover is to re-image.