Toon firmware - update script

[FunFair]

Ah ok Eneco changed their scripts again. Just checked and it is ok. I updated the update-rooted script to allow this (version 3.86 just published).

WOW! Quick service. But a bit too quick lol.
Getting a syntax error.
But it seems to be an error in the update script from Toon?

Code: Select all

Which version do you want to upgrade to?
5.5.7
Alright, I will try to upgrade to 5.5.7
Now starting the VPN tunnel and waiting for it to be alive and configured...
Now starting the VPN tunnel and waiting for it to be alive and configured...
Tunnel is alive and configured.
Upgrade script downloaded. We need to download the upgrade files first. No upgrade is done yet. Do you want me to download the files (yes) or quit (anything else)?
yes
Starting the upgrade prepare option which downloads all necessary files. No upgrade is done yet.
/mnt/data/update/upgrade-qb2.sh: line 62: syntax error: unexpected "}"

Prepare failed. Please check the logs at /mnt/data/update/upgrade-qb2.sh.log
Quitting the upgrade. It was a nice try tho...

The log file is not updated btw. Removed the old log and no new one was created.

[yustmenl]

I am having the same problem here.

[TheHogNL]

Should work now. A line was changed in their script which my script needed to modify but now failed.

The line is about posting everything you do while updating your toon to the eneco server center. We don't want that so my script removes that line. But that failed now because they changed a small thang. So again, it is fixed now, version 3.87.

[yustmenl]

Thanks for the quick responce but unfortunaly i stil have the same problem

[FunFair]

Thanks for the quick responce but unfortunaly i stil have the same problem

Mine works. Did you re-download the script?

Thanks HogNL

[yustmenl]

It's working now, Thanks!

[MP51]

Upgrading my Toon from version 4.16.8 to 5.5.7 by update script, everything went fine.
After reboot my Toon shows only Toon logo with aan loading bar until 33% then stopped, what can i do ?

[TheHogNL]

Upgrading my Toon from version 4.16.8 to 5.5.7 by update script, everything went fine.
After reboot my Toon shows only Toon logo with aan loading bar until 33% then stopped, what can i do ?

How did you reboot after the update?
Can you check /etc/inittab and /usr/bin/startqt ? Should both be readable files. In some cases they end up empty. Probably after a power cycle reboot.

[mAiden]

Upgrading my Toon from version 4.16.8 to 5.5.7 by update script, everything went fine.
After reboot my Toon shows only Toon logo with aan loading bar until 33% then stopped, what can i do ?

Probably inittab is empty and you missing qt-gui now.

On the forum you will find a inittab, p put it in it. And start a VPN and install qt-gui with:

Opkg install qt-gui

[MP51]

i have checked /etc/inittab and /usr/bin/startqt, the are both with readable text in it inittab = 3kb and startqt = 2kb
Have done Opkg install qt-gui, that give the message already installed.

my inittab

Code: Select all

# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:5:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin

# HCBv2 static stuff
#ovpn:235:respawn:/usr/sbin/openvpn --config /etc/openvpn/vpn.conf --verb 0 >/dev/null 2>&1
qtqt:245:respawn:/usr/bin/startqt >/dev/null 2>&1
# add serial console access:
gett:235:respawn:/sbin/getty -L 115200 ttymxc0 vt102
tscs:245:respawn:/usr/bin/tsc >/var/log/tsc 2>&1

# WARNING: auto-managed by '/etc/init.d/HCBv2 inittabwrap' with '/HCBv2/etc/start.d/*'
#          lines containing 'inittabwrap' will be removed automagically.
netc:235:respawn:/etc/init.d/HCBv2 inittabwrap hcb_netcon
comm:345:respawn:/etc/init.d/HCBv2 inittabwrap hcb_comm
even:345:respawn:/etc/init.d/HCBv2 inittabwrap happ_eventmgr
kpik:345:respawn:/etc/init.d/HCBv2 inittabwrap happ_kpi
pwru:345:respawn:/etc/init.d/HCBv2 inittabwrap happ_pwrusage
scsy:345:respawn:/etc/init.d/HCBv2 inittabwrap happ_scsync
smar:345:respawn:/etc/init.d/HCBv2 inittabwrap happ_smartplug
ther:345:respawn:/etc/init.d/HCBv2 inittabwrap happ_thermstat
user:345:respawn:/etc/init.d/HCBv2 inittabwrap happ_usermsg
weat:345:respawn:/etc/init.d/HCBv2 inittabwrap happ_weather
bxtp:345:respawn:/etc/init.d/HCBv2 inittabwrap hcb_bxtproxy
conf:345:respawn:/etc/init.d/HCBv2 inittabwrap hcb_config
logl:345:respawn:/etc/init.d/HCBv2 inittabwrap hcb_log
rrdr:345:respawn:/etc/init.d/HCBv2 inittabwrap hcb_rrd
watc:345:respawn:/etc/init.d/HCBv2 inittabwrap hcb_watchdog
hueh:345:respawn:/etc/init.d/HCBv2 inittabwrap hdrv_hue
p1p1:345:respawn:/etc/init.d/HCBv2 inittabwrap hdrv_p1
zwav:345:respawn:/etc/init.d/HCBv2 inittabwrap hdrv_zwave
ligh:345:respawn:/etc/init.d/HCBv2 inittabwrap lighttpd
# end of 'inittabwrap' section.

my startqt

Code: Select all

#!/bin/sh

# load a sane environment, HCBv2 can prevent execution with 'exit'
. /etc/profile
. /etc/default/HCBv2

cd /qmf/sbin

if [ -z `pidof psplash` ]
then
        echo "Starting psplash..."
        /etc/init.d/psplash.sh
fi

# set the initial progress of the UI
/etc/init.d/psplash.sh progress 30

# do we have dim support in our binary? For qt if the system supports it the UI will as well
SYSBL="`/bin/ls /sys/class/backlight/*/ramp_brightness_sync | grep -v contrast | head -n1`"
if [ "$SYSBL" ]
then
        BL=1
        BLMAX="`dirname $SYSBL`/max_brightness"
fi

# calib screen first?
if [ ! -f /etc/pointercal ]
then
        [ "$BL" ] && cat $BLMAX > $SYSBL
        echo 0 > /sys/class/graphics/fb0/blank
        ts_calibrate
        #[ "$BL" ] && echo 0 > $SYSBL
fi

# enable screen and create the tmp file if it was still missing
echo 0 > /sys/class/graphics/fb0/blank
echo 0 > /tmp/fb0_blank

#export QT_DEBUG_PLUGINS=1
#export QML_IMPORT_TRACE=1

echo "Starting Qt"
exec /qmf/sbin/qt-gui -platform linuxfb -plugin Tslib

[mAiden]

Nothing strange there.
Start VPN with:

Code: Select all

sh update-rooted.sh -o

Open a new SSH window (Dont close the other one with the VPN!), and try this one:

Code: Select all

opkg install --force-reinstall qt-gui

[TheHogNL]

Try to log the QT start sequence and see why QT isn't booting up.

[mAiden]

Try to log the QT start sequence and see why QT isn't booting up.

Dangerous to do this, but I suspect a wrong resource file with no backup. hence my reaction above.
There are hardly any other choices.

[TheHogNL]

Try to log the QT start sequence and see why QT isn't booting up.

Dangerous to do this, but I suspect a wrong resource file with no backup. hence my reaction above.
There are hardly any other choices.

Dangerous to do a log? Nothing dangerous about that mAiden

[mAiden]

Try to log the QT start sequence and see why QT isn't booting up.

Dangerous to do this, but I suspect a wrong resource file with no backup. hence my reaction above.
There are hardly any other choices.

Dangerous to do a log? Nothing dangerous about that mAiden

You misunderstand me.
It is dangerous to make statements that I just made. That wrong resource file might have been loaded..
QT logging is always a good thing, so you can see exactly what's wrong.