Open BlackHole Online Update

OBH has got an incredibly comfortable feature, without the need of any additional plugins (like AutomaticFullBackup): you can schedule a backup at the desired frequency: for instance, I set it to be done everyday.
And you'll get files easy to be interpreted, because it will contain the release as well as the date and time.
For instance:
OBH-Solo4K-release-4.3.026-20200424_182723.zip

I strongly recommend that.
So, if anything goes wrong you have two options: if the image starts and give you access to the FullBackup from the GUI, you can get back to a previous day (and a previous version) by the GUI itself.
If the image cannot complete the boot, you can get the .zip file of the backup from the device you chose and proceed like for a clean image install.
That's why I suggest to use as a device one that's easily accessible, like an external USB disk, a NAS or also an internal HDD easily detachable like in Solo4K and other models.

If the daily F.B. habit became common, a lot of troubles will vanish.
 
@Ev0
I found this:
root@vuuno:~# init 5
root@vuuno:~# enigma2.sh > /media/hdd/debug.log 2>&1
root@vuuno:~# cat /media/hdd/debug.log
enigma2 is the main pvr application... adjust oom score!
/usr/bin/enigma2.sh: line 71: 27620 Killed LD_PRELOAD=$LIBS /usr/bin/enigma2 &> /dev/null
root@vuuno:~#

$LIBS=/usr/lib/libopen.so.0.0.0

Code:
if grep -q 'config\.crash\.enabledebug=True' /etc/enigma2/settings; then

    debug_dir=$(sed -n 's/config.crash.debug_path=//p' /etc/enigma2/settings)
    [ -n "${debug_dir}" -a -d "${debug_dir}" ] || debug_dir=/home/root/logs/
    LD_PRELOAD=$LIBS /usr/bin/enigma2 &> "${debug_dir}Enigma2_debug_$(date +%Y-%m-%d_%H-%M-%S).log"
else

    if grep -q 'config\.misc\.firstrun=False' /etc/enigma2/settings; then

        LD_PRELOAD=$LIBS /usr/bin/enigma2 &> /dev/null
    else

        LD_PRELOAD=$LIBS /usr/bin/enigma2
    fi
fi
 
Should be fixed now, so if you telnet into your box, then use command:

Code:
opkg update && opkg upgrade

You box should update then once complete you can reboot the box.
 
  • Like
Reactions: KFL
@Ev0 Thank you! UNO is working now.
(OBH4.3.019 -> init 4 && opkg update && opkg upgrade && init 6 -> OBH4.3.026 working)
 
Uno/Uno4kSE upgrade to 4.3.027 is OK (I did it manually)
Code:
init 4 && opkg update && opkg upgrade && init 6
alsa-state error 99 solution (appeared few versions ago)
Code:
init 4 && opkg remove alsa-state --force-depends && opkg install alsa-state && init 6
 
My VU+ SE cannot update and install ny update over the internet .
when i click install I wait for download and restart, after restart I look info still old OpneBH .
tried several times to no effect, still an old OpenBH 4.3.025.
 
@kralj upgrade manually via telnet/ssh
Code:
init 4 && opkg update && opkg upgrade && init 6
alsa-state error 99 solution (appeared few versions ago)
Code:
init 4 && opkg remove alsa-state --force-depends && opkg update && opkg install alsa-state && init 6
 
@kralj upgrade manually via telnet/ssh
Code:
init 4 && opkg update && opkg upgrade && init 6
alsa-state error 99 solution (appeared few versions ago)
Code:
init 4 && opkg remove alsa-state --force-depends && opkg update && opkg install alsa-state && init 6

Thanks. This solved it. I had the "alsa-state error" 99.
 
Good morning

From update openbh 4.3.028 (2020-04-30)
I performed software update, the system found 65 new packages,
as usual update and restart but this appeared:

upload_2020-5-13_8-15-15.png

Hall
 
Hi, who helps me understand what could have happened.
In practice, on my Solo2 already with version 4.3.027 installed, I proceeded to update the image from the "Settings -> Update OBH menu, at the end of the procedure I still display version 4.3.27 and with the CrossEPG menu in Cyrillic!!! :eek:(see photo)
What may have happened?
1_0_1_D49_1450_13E_820000_0_0_0_20200514042110.jpg
 
OBH tells us an update ... I did it but I can't tell if it solved the issue or not, as I had already changed the .mo ...

And try...

oT638Hi.png
 
Back
Top