Actually, sometimes when trying to shutdown, the screen doesn't even blank and I only know that XBMC isn't still running because the debug OSD stops updating.
I initiated the shutdown at 14:27:43 (13:27:43 according to the log) and it's ten minutes later and it's still like that, although the log stopped after 10s when XBMC presumably was terminated).
http://pastebin.com/
Fudge, my previous post seems to have disappeared!
Right let's see if I can remember what I posted.
It seems to be pretty stable now, even with the hub and remote connected, albeit sometimes lagging/ignoring keypresses and occasionally going into a phantom keypress loop (although that seems much less likely to happen now). I don't understand why the remote would lock up sending phantom keypresses whenever I try it in the Pi directly, as I'd think that should be less complicated but hey.
I actually swapped the hub out as I wanted to try one (same model) I'd disconnected the LEDs from, in the hope that it would generate less heat and thus make my box less warm. It turned out that it doesn't help and the heat is being generated by the current draw by the remote receiver (without that, or anything else, connected it doesn't get warm) but maybe the other hub was just dodgy. I'll try swapping it back in to test.
I've got iPlayer, ITV Player, Youtube, Radio, ListenLiveEu, ShoutCast2 working reasonably. Sometimes the radio plugins lockup the GUI for as much as a minute when trying to start a station with a non-working link and Shoutcast2 seems to be a lot slower than Radio, taking about 30s to switch stations but other than that they're OK.
When booting I see some messages but they're probably not critical.
sbin/init: source: line 49: can't open '/var/config/settings.conf.
rpcbind: cannot get local address for udp. Servname not supported for ai_socktype
same message for tcp then udp6 and tcp6 several times.
garbage after 'name' token in line 378 ignored
invalid code found for Xbox: KEY_PAUSE
I don't seem to be getting the rainbow splash most of the time but just linux boot text, or sometimes I get both.
Also, sometimes I can't seem to shutdown properly now and although the screen goes blank, all the lights stay on, with Link flickering. I don't know if this could be caused by running from SD and using iotimeout maybe, or by using autostart.sh to make an OS-level NFS mount at boot, like this (comes in handy to pause at boot to note any error messages, as I can just disconnect the network and then as it can't find it, it pause the boot).
Code:
#!/bin/sh
# Wait for the network to come up...
while [ -z "$(connmanctl state | grep State | grep -E "ready|online")" ]; do sleep 0.25; done; logger -t "$(basename $0)" "** Network is up **"
[ ! -d /storage/NFS-Media ] && mkdir /storage/NFS-Media
mount -t nfs 192.168.1.64:/Media -o nfsvers=3,rw,intr,noatime,rsize=32768,wsize=32678,nolock,async,proto=udp /storage/NFS-Media
Other than the power-off problem though it seems stable enough, so I should try moving Storage back to the USB stick next and then try overclocking again, although I guess we should try and fix the power-off problem first (unless it is caused by running from SD and using iotimeout, in which case it might not be a problem when using the USB stick for Storage, I certainly never experienced it when I was using the USB stick before resetting .xbmc)
