34 replies to this topic

[ian1095]

I was running enigma from the 4th Dec and today Software update reported there were 303 updates ,so i tried to update.Firstly the shutdown problem is back again,which I overcame by issuing

 

chmod -x /usr/bin/turnoff_power in telnet.

 

After doing this the update did indeed continue and complete,but upon reboot enigma2 doesnt start and the image just remains on the initial boot screen.

 

This is on a VU+ Solo

 

Ian.

Edited by ian1095, 6 December 2014 - 10:58.

[Erik Slagter]

Telnet to the receiver, type init 4 and then enigma2. Copy and paste the last few lines here.

[ian1095]

PYTHONPATH: /usr/lib/enigma2/python
+ (1) Background File Eraser
+ (5) Tuxtxt
+ (8) graphics acceleration manager
+ (9) GFBDC
10800k video mem
 - double buffering available!
5040kB available for acceleration surfaces.
resolution: 720 x 576 x 32 (stride: 5120)
+ (9) gLCDDC
found OLED display!
lcd buffer 0x82c8a8 8448 bytes, stride 132
LCD resolution: 132 x 64 x 8 (stride: 132)
+ (9) Font Render Class
[FONT] initializing lib...
[FONT] loading fonts...
[FONT] Intializing font cache, using max. 4MB...
+ (10) gRC
RC thread created successfully
+ (15) eWindowStyleManager
+ (20) DVB-CI UI
+ (20) UHF Modulator
couldnt open /dev/rfmod0!!!!
+ (20) RC Input layer
+ (20) misc options
+ (20) AVSwitch Driver
couldnt open /dev/dbox/fp0 to monitor vcr scart slow blanking changed!
+ (21) input device driver
Input device "dreambox advanced remote control (native)" is a mouse
Found 1 input devices.
+ (22) Hdmi CEC driver
eHdmiCEC: detected physical address change: 1000 --> FFFF
eHdmiCEC: send message 84 FF FF 03
+ (30) eActionMap
+ (35) CI Slots
scanning for common interfaces..
CI Slot 0 setSource(0)
CI Slot 1 setSource(0)
eDVBCIInterfaces->setInputSource(0, 0)
eDVBCIInterfaces->setInputSource(1, 1)
cannot open /proc/stb/tsmux/input2
cannot open /proc/stb/tsmux/input3
done, found 2 common interface slots
+ (35) CA handler
+ (40) eServiceCenter
settings instance.
+ (41) eServiceFactoryDVD
+ (41) eServiceFactoryHDMI
+ (41) eServiceFactoryM2TS
+ (41) eServiceFactoryMP3
+ (41) eServiceFactoryFS
+ (41) eServiceFactoryDVB
+ (41) Encoders
+ (41) Stream server
reached rl 70
---- opening lame channel db
reading services (version 4)
main thread is non-idle! display spinner!
no spinner DC!
main thread is non-idle! display spinner!
no spinner DC!
main thread is non-idle! display spinner!
no spinner DC!
loaded 2820 channels/transponders and 35912 services
scanning for frontends..
opening frontend 0
close frontend 0
found 1 adapter, 1 frontends(1 sim) and 5 demux, boxtype 2
RTC not ready... wait for transponder time
[EPGC] Initialized EPGCache (wait for setCacheFile call now)
Loading spinners...
[ePNG] couldn't open /usr/share/enigma2/skin_default/spinner/wait8.png
found 7 spinner!

executing main
setIoPrio best-effort level 3 ok
Failed to open /dev/dbox/fp0
couldn't open /proc/stb/misc/12V_output
Scanning hardware info
Detected: vusolo (1400E8)
[Harddisk] enumerating block devices...
new Harddisk sda -> /dev/sda -> /dev/sda
[ePopen] command: ('sdparm', 'sdparm', '--set=SCT=0', '/dev/sda')
main thread is non-idle! display spinner!
Reading satellites.xml
sec config cleared
setSlotInfo for dvb frontend 0 to slotid 0, descr BCM7325 DVB-S2 NIM (internal),
 need rotorworkaround No, enabled Yes, DVB-S2 Yes
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/mytest.py", line 18, in <module>
    from Screens import InfoBar
  File "/usr/lib/enigma2/python/Screens/InfoBar.py", line 6, in <module>
  File "/usr/lib/enigma2/python/Screens/MovieSelection.py", line 17, in <module>
  File "/usr/lib/enigma2/python/Components/UsageConfig.py", line 5, in <module>
  File "/usr/lib/enigma2/python/Components/NimManager.py", line 1635, in <module
>
  File "/usr/lib/enigma2/python/Components/NimManager.py", line 845, in __init__
  File "/usr/lib/enigma2/python/Components/NimManager.py", line 1569, in InitNim
Manager
  File "/usr/lib/enigma2/python/Components/NimManager.py", line 511, in __init__
  File "/usr/lib/enigma2/python/Components/NimManager.py", line 163, in update
ValueError: list.remove(x): x not in list
---- saving lame channel db
main thread is non-idle! display spinner!
saved 2820 channels and 35912 services!
release cached channel (timer timeout)
- (41) eServiceFactoryDVD
- (41) eServiceFactoryHDMI
- (41) eServiceFactoryM2TS
- (41) eServiceFactoryMP3
- (41) eServiceFactoryFS
- (41) eServiceFactoryDVB
- (41) Encoders
- (41) Stream server
- (40) eServiceCenter
clear instance
- (35) CI Slots
- (35) CA handler
- (30) eActionMap
- (22) Hdmi CEC driver
- (21) input device driver
- (20) DVB-CI UI
- (20) UHF Modulator
- (20) RC Input layer
- (20) misc options
- (20) AVSwitch Driver
- (15) eWindowStyleManager
- (10) gRC
waiting for gRC thread shutdown
gRC thread has finished
- (9) GFBDC
- (9) gLCDDC
- (9) Font Render Class
- (8) graphics acceleration manager
- (5) Tuxtxt
- (1) Background File Eraser
reached rl -1
root@vusolo:~#

[delavega]

303 packages update and its shutdown

 

i was running a fresh image. why is it happening again? I thought the big update was behind us

[dog-man]

Oh dear!

[greatred]

ValueError: list.remove(x): x not in list again.....

So reports from Ultimo, Uno and now Solo.

I think it would be wise to mark the last two builds as defective.

[hemertje]

303 packages update and its shutdown

 

i was running a fresh image. why is it happening again? I thought the big update was behind us

 

no, still work in progress

[dog-man]

My VUDUO is showing has having 200 updates available.

 

Is it safe for me to update my VU or should I wait a few days?

[hemertje]

Just wait if you have no needs

[mackguil]

on ET9000 238 update and crash after downloading the upgrade for bot logo, the screen stay fix and nothing move.

 

I have try rhe update the 29 november and exactly the same.

 

Just the solution to reflash from usb with an old backup to restart the set top box.

 

[mimisiku]

Like I mentioned in the Dutch section.. Although I have massive respect for all the OpenPli developers and have been using their images on my Dreamboxes for years I must come to the coclusion that things have gone out of control. They have opted for wide OpenPli support for numerous boxes leading to a very complex build environment. Small errors are acceptable, but complete crashing and/or even non-booting of boxes is (in my opinion) is totally unacceptable.. My statement is to reduce the number of boxes or even to suspend OpenPli 4.0 completely!! There are better images that don't crash your box with support...

I know this makes "tough" reading, but I think it is very realistic. I realise that OpenPli is a free service and one can't claim any warranties as such. But enough is enough.. If they can't get it working, simply stop.

It is fully beyond me why a working build is corrupted by "some" C-library update. Why SSL's are being destroyed while update to SSL's is completely not necessary (no change whatsoever). And didn't happen before...

[ian1095]

I see there is a new build from today at 15:00,the previous broken build was from 3am this morning.

 

Is this issue now fixed with this build and is it now ok to perform an online update ?

 

Although I wasnt happy about having to flash one of my backups,its not exactly hard is it ?

I feel the previous poster was far to harsh in his comments,shit happens,just deal with it.

 

Ian.

Edited by ian1095, 6 December 2014 - 16:38.

[christophecvr]

Like I mentioned in the Dutch section.. Although I have massive respect for all the OpenPli developers and have been using their images on my Dreamboxes for years I must come to the coclusion that things have gone out of control. They have opted for wide OpenPli support for numerous boxes leading to a very complex build environment. Small errors are acceptable, but complete crashing and/or even non-booting of boxes is (in my opinion) is totally unacceptable.. My statement is to reduce the number of boxes or even to suspend OpenPli 4.0 completely!! There are better images that don't crash your box with support...

I know this makes "tough" reading, but I think it is very realistic. I realise that OpenPli is a free service and one can't claim any warranties as such. But enough is enough.. If they can't get it working, simply stop.

It is fully beyond me why a working build is corrupted by "some" C-library update. Why SSL's are being destroyed while update to SSL's is completely not necessary (no change whatsoever). And didn't happen before...

Unless You have constructive comments Go ahead.

 

But what You are writing is complete bullshit. Just use another image then You're happy.

 

It's not the first ridiculous comment You are giving.

[mimisiku]

Like I care!

[dog-man]

Pli images are great, been using them for many years now.

I can accept the occasional blip.

[littlesat]

We never can guarantee the nightly builds are good...
We can do two thinks... Release once or max twice a year... Or you are free to get all our beta's....
I suggest during the upgrade process you see enough disclaimers....

[ian1095]

This thread has sidetracked.

 

I repeat my question,is it now ok to perform an online update now there is a new build on the server ?

 

Ian.

[hemertje]

Wait à few days

[alantreet]

Help! I've just downloaded and used today's update (I went straight to the download page) and my DM800HDSE is just looking at me saying "R01: NO CA FOUND"

 

I last used an OpenPLI image with the update in Feb, but don't update that often and just tried this one and now not even rebooting my box gets me anywhere. HELP!

[delavega]

will wait then, thanks.