2013-09-18, 19:27
(2013-09-18, 11:56)RichG Wrote: Seems the update doesn't work corectly in some cases, I presume due to an issue with the updater script or similar. You may have to manually update the Kernel and possibly System files on your install.
I can't confirm this yet, but will try later on and report back...
If you have configured the boot parameter in config.txt to use something other than /dev/mmcblk0p1 - for example, when "booting" from USB, NFS, SMB etc. - then the standard update process (manual or automatic) will NOT work 100%. At best the Pi will not receive the new kernel and experience glitches such as non-functional lirc, at worst the Pi may not boot at all.
There are two problems with OpenELEC:
- The initramfs init script blindly copies new kernel firmware to /flash even when /flash isn't the boot partition - an issue for this was opened long ago and a subsequent patch was rejected and rotted almost as long ago
- The update.sh script doesn't preserve the timestamps of the new firmware files (they're always 1 Jan 1980) so the user never knows when they have old firmware. This is trivial to fix, however the original patch was rejected. I've resubmitted patch 2614, we'll see how that goes. It's a small step, but progress.
(2013-09-18, 19:19)pplucky Wrote: Unless you're running XBMC from USB drive or NFS, as this update has stopped working, it always corrupts the SD card. I need to copy the files manually to boot SD card partition.
Yes, this "wrinkle" in the update process is very unfortunate, particularly as it was flagged up as an issue so long ago and will now likely catch out a lot more users than it would have done 9 months ago. Though actual SD card corruption could be something else, a check for that was also part of the rejected (and now rotten) patch - the problem with the update process is that it simply writes the Pi's most important firmware file to the wrong location.