48 replies to this topic

[mymon]

seems like the last build and upgrade bricks the box

firs I did opkg upgrade and my box froze on Vu logo

didn't seem dangerous

 

root@vusolo4k:~# opkg list-upgradable

Not selecting python-requests 1.2.3 as installing it would break existing dependencies.

Not selecting python-requests 1.2.3 as installing it would break existing dependencies.

enigma2-plugin-extensions-mediascanner - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

busybox - 1.22.1-r32.5 - 1.22.1-r32.6

enigma2-plugin-extensions-pictureplayer - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-fastscan - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-hotplug - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-cablescan - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-wirelesslan - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

busybox-mdev - 1.22.1-r32.5 - 1.22.1-r32.6

enigma2-plugin-extensions-openwebif - 1+git2388+821de77-r0.0 - 1+git2390+1b697fc-r0.0

enigma2-plugin-systemplugins-osd3dsetup - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-extensions-cutlisteditor - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-positionersetup - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-videomode - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-softwaremanager - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-osdpositionsetup - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

busybox-cron - 1.22.1-r32.5 - 1.22.1-r32.6

enigma2 - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-extensions-mediaplayer - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-hdmicec - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-skinselector - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-extensions-graphmultiepg - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-satfinder - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

enigma2-plugin-systemplugins-videotune - 2.7+git14987+c22847b-r0.0 - 2.7+git14991+1fa6c1c-r0.0

root@vusolo4k:~# 

 

 

than I re-flashed with the last build from 29 Jan and same thing

I re-flashed again with build from 28th Jan all all seems OK - just don't do the upgrade!

[WanWizard]

Just did an upgrade of a few boxes (no VU+), haven't seen a prorblem. So it doesn't seem to be a generic issue.

[Samba!]

Beste allemaal, zojuist lid geworden van het forum :-)
Ik heb precies hetzelfde probleem gehad vandaag op de VU+ Solo 4K: update gedraaid, bleef zeer lange tijd hangen. Herstart (stroom eraf): bleef hangen op VU+ logo.
Daarna image van gisteren (28-01-2017) geflashed: geen probleem. Daarna opnieuw update => hangt.
Dit enkele keren herhaald als test, exact dezelfde uitkomst.
Probleem is dus (althans bij mij) repliceerbaar!
Groet uit Den Haag van Bart!


Verzonden vanaf mijn iPhone met Tapatalk

[WanWizard]

Welcome here: first tip: this is an English language forum, so replies in English please so others can read it too.

[Samba!]

Sorry, should have been in English ;-)
I have had exactly the same problem on my VU+ Solo 4K: today's (29-01-2017) update freezes the box on update, restarting makes it 'hang' at the VU+ logo.
Yesterday's (28-01-2017) image no problem whatsoever.
Tested this 4 times to see if it could be replicated: same results every time...
So there IS some problem here...
Best regards from The Hague, Bart.


Verzonden vanaf mijn iPhone met Tapatalk

[mymon]

WanWizard its probably just affecting solo4k but like I've said.. even when I tried to re-flash the box with a build from the 29th it froze on the vu+ logo

however I still don't get whats causing it as you can see from the list-upgradable that there is nothing that could break it.. anyway I'll hold with upgrades until someone else confirms its OK again

[S_Hopper]

Same here with my Solo 4k
Update of this monding has the same issue. Can't even flash the fresh image of 30.01.

Verstuurd van mijn Galaxy Note 4

[ricki]

same problem here.

[pinnoes]

hi,

 

same problem here not booting

must reinstall another one

but i need openpli

hel¨p

pinnoes

[mymon]

just install the build from the 28th Jan and don't do the upgrade

[Samba!]

From the openpli.org-website, just download a zip from a couple of days ago (28th worked for me on solo 4k), unzip to a usb drive, put it in the receiver, turn power on and follow on-screen instructions. Stay tuned, because after finish & boot it asks if you want to restore all your backed-up settings. Oh yeah, extra plugins such as oscam are (unless you have a FULL backup) not part of the backup and have to be re-installed. The SETTINGS of those same plugins ARE, however, part of the backup.
Does this help?


Verzonden vanaf mijn iPhone met Tapatalk

[WanWizard]

It is being looked at. The 28th is ok, later ones are missing something, probably due to an issue on our buildserver.

[nor50]

Why does this happen so often...? :-(

[WanWizard]

The build enviroment is one single compiler environment, but is has to cross-compile for lots of different kernel versions and architectures. It is a very complex set of recipes, with all sorts of inheritance, and recipes overruling other recipes. It becomes even more complex because a lot of those come from third parties.

 

Most of these parties only have a single environment to cater for. Developers only building for a single box, manufacturers only building for a single brand, etc. So sometimes issues only surface when you bring it all together.

 

From what I understand the problem this time is the requirement of the build process for a specific version of an Ubuntu library, which doesn't want to install due to a dependency problem in Ubuntu (not an Ubuntu user, so I don't know the details).

 

In itself it is not a problem for users. However, it now is, because we don't have a separation between test images (we use in development) and stable images (you as an enduser can use). We are going to change that soon, we are currently making the preparations for duplicating our environment to facilitate that.

[nor50]

I have used about 15 hours today because of this. Watch the thread about errors. Nothing there. Reset the tuner 3-4 times, same problem. Searching for errors on my equipment, tried other images, and so on...

[WanWizard]

We are aware of that, and working very hard to address it.

 

That being said, our current images are automatically generated, nighty, beta images, from whatever the current state of the code. So if you expect a stable end-user image. don't update one that works, because we currently don't produce any. And if you want to update, make sure you read up on it's current development state. You are not the first one reporting this issue.

 

I can only say that we want to have separate production images, known to be stable (doesn't mean bug-free), as soon as possible.

[nor50]

Now my LNB set-up is faulty. I can only use 1 out of 4 tuners. I have a SatCR-LNB on input 2. After the Jess-update (?) where my LNB was included in the image, I had no problems, but now I have problems, and don't remember what setting should be. See enclosed pictures, and please tell me what is wrong in the LNB-setting. I have tried a lot, but now it's a mess..  (I have this SatCR LNB on input 2).

 

Attached Files

•  IMG_20170130_214336.jpg   63.34KB   8 downloads
•  IMG_20170130_214321.jpg   73.02KB   9 downloads
•  IMG_20170130_214309.jpg   70.57KB   10 downloads
•  IMG_20170130_214253.jpg   79.27KB   10 downloads

[Pedro_Newbie]

I have used about 15 hours today because of this. Watch the thread about errors. Nothing there. Reset the tuner 3-4 times, same problem. Searching for errors on my equipment, tried other images, and so on...

 

One word of advice, don't discard the disclaimer you got presented when you updated the first time. It contains some imported advise to create at least an Autobackup or even a full backup. In case of any mishap you don't have to spend 15 hours to recreate your image but at most 15 minutes or even in case of a full backup a minute or 2

 

[mymon]

Pedro_Newbie fair enough about the potential risk during upgrade (from menu) but you can't see that if you do it via the command line.. beside that if you re-flash the image with build from the 29th it freezes on the vu logo which may point you on the wrong direction (because there is no work about the faulty image on the main/download page)

BTW the 29th JAN image for solo4k is still available for download

[Samba!]

Careful suggestion:
Build status traffic light should perhaps be red?
Remove builds after 28th of jan. (last known good image) or place a warning on the download page?


Verzonden vanaf mijn iPhone met Tapatalk