Works for me, both via the Diagnostics page and via the command line. Set safe mode and then reboot, access to WebIF gets this:
View attachment 4461
It shows what the webif should be showing after rebooting into Safe modein which way does that help me?
Yes, because 3.13 doesn't have the iplayer anymoreIt shows what the webif should be showing after rebooting into Safe mode
Are you still on a downlevel CF level?
Whether or not iplayer still works doesn't depend on the custom firmware version; it depend on the standard firmware version. Last time I tried with 1.03.12_mod_3.13 iplayer worked.Yes, because 3.13 doesn't have the iplayer anymore
What are you talking about? Standard firmware lower than 1.03.xx no longer supports iPlayer, so you won't want CF 3.13 for 1.02.20 (for example), but there's no reason you can't install CF 3.13 for 1.03.12.Yes, because 3.13 doesn't have the iplayer anymore
It shows what the webif should be showing after rebooting into Safe mode
Are you still on a downlevel CF level?
So that probably explains why you are having problems following our instructions. Stop wasting our time and get your installation up to date.
To reduce the logged ouput, you could tweak it like this:...
Based on a link I posted earlier in this thread is created a small routine that logs the top 10 cpu consuming processes every 10 secs and can be run in both normal and safe mode to help identify what is actually causing any spikes.
create and make executable /mod/bin/cpulog
...
#!/bin/sh
# ignore below total CPU threshold in %
CPU_THRESH=65
# polling interval in second
INTERVAL=5
LOGFILE=/mod/tmp/cpulog.log
# number of busy processes
TOP_NUM=5
# extra ps columns
PS_COLS="pmem,pid,ppid,args"
# sort order - busy first, + busy last
UPDN="-"
total() { # sum integers from stdin to stdout
local sum=0
local ii
while read ii; do
sum=$(($sum + ${ii%.*}))
done
printf "%d" "${sum:-0}"
}
echo "log top $TOP_NUM processes to $LOGFILE when CPU usage > $CPU_THRESH"
PS_COLS="pcpu,$PS_COLS"
hdr="$(ps -o $PS_COLS | head -n 1)"
case $UPDN in
'+') crop="tail";;
*) crop="head";;
esac
while true; do
# "ps | total()" is much more efficient than using the system idle percentage from "top -b -n 1"
[ "$(ps -e -o pcpu --no-headers | total )" -ge $CPU_THRESH ] &&
{ echo "${hdr} ----- $(date '+%F %T %Z')" &&
ps -e -o $PS_COLS --sort=${UPDN}pcpu --no-headers |
"$crop" -n ${TOP_NUM}; } >> "$LOGFILE"
sleep $INTERVAL
done
UPDN
parameterisation to switch head
/tail
.cpulog &
or using an abduco session abduco -n cpulog cpulog
.Yes SirWhat are you talking about? Standard firmware lower than 1.03.xx no longer supports iPlayer, so you won't want CF 3.13 for 1.02.20 (for example), but there's no reason you can't install CF 3.13 for 1.03.12.
So that probably explains why you are having problems following our instructions. Stop wasting our time and get your installation up to date.
I am out of safe mode for now. will go into it later this afternoon.Tunefix wont run while in Safe mode but should work as normal when you exit Safe mode
Among other possibilities: run a manual backup and compare that file with the automatic backup.is there a way to see whether I set a recording via the remote control since the last backup of my schedule at 1 am this morning?
that is the same box but totally different circumstances. that thread was about cropping during recording.It could be helpful to compare this thread with a previous related thread from the same OP.
Is this the same box?
What is reported for the disk (SMART status), eg from Webif>Diagnostics>Disk Diagnostics?
there, it was a process I could control: cropping.In both cases, you're reporting pixellation apparently related to background processing.
As this doesn't seem to affect all, or perhaps even most, users, the question arises whether there's some root cause associated with your, or some subset of, HDR boxes. With consumer electronics it's not likely that you just have a "Friday afternoon" model (like the boiler PCB I had with a connector soldered in backwards). One possible source is a problem with the disk, which is why I asked about the SMART data.
I can confirm from experience that a failing disk does cause picture break-up, though I never went to the length of trying safe mode to overcome it.
No, you've just eliminated some of the potential culprits. Saying that the CF (as a whole) is the culprit is tarring everything with the same brush.think i found the culprit
hmmm,No, you've just eliminated some of the potential culprits. Saying that the CF (as a whole) is the culprit is tarring everything with the same brush.