26 replies to this topic

[ana_simo_sat]

Hello,
I have VU+DUO2 with theVTI6.0.6 image mounted on the flash and I like go to the OPENPLI4. but after installing OPENPLI4, I find that it is very slow especially the passage between the channel and the menu!
I tried several times but the same problem still persists.
I do not understand where this problem come from? knowing that I have seen on other duo2 OPENPLI4 that works perfectly.

 

Your Help please

[Frenske]

Message removed. I didn't read your posting properly.

Edited by Frenske, 28 March 2014 - 09:57.

[Erik Slagter]

If your VU+ Duo2 is slow, check the time, it's probably years off. It's a known problem with the Duo2, once the time has been set correctly (mostly because it has been tuned to a valid transponder for some time), the problem will vanish.

Edited by Erik Slagter, 28 March 2014 - 09:05.

[christophecvr]

There are some small issues when flashing the vuduo2 (or solo2) with pli4

Some tips :

 

1) Do not remove the power before You flash.

    best way : Whit box running ! , remove all eventual usb devices plugged in in any usb port.

                       Use an usb stick off max 2 Gb formated fat32 (with a stick off 4GB it works only now and then however i've seen a change into vuplus.code.com which is just for this mather I guess)

                       insert the stick containing the expanded vuplus map with the image you wan't to flash.

                       shutdown the box trough menu (do not unpower the box )

                       restart box via the power knob. And push this knob again when update starts flashing.

                       It will nicely flash and all will be fine.

2) If power was removed before You flash

     You will encounter this slow menu change with regularly time keeper and so on.

     To recover normal working, When after flashing this problem arise, first telnet to you're box . issue command:

     root@vuduo2:~# date -s "2014-03-28 09:26"  (the current date and hour ) You're problem with slow menu will be solved

Edited by christophecvr, 28 March 2014 - 09:30.

[christophecvr]

small note one

Use an usb stick off max 2 Gb formated fat32

 

It's max physical 2 GB using a bigger stick with smaller partition does not work unfortunately I tried it.

[ana_simo_sat]

Christophecvr: it works fine after follow your instructions

[ana_simo_sat]

thanks

[kota]

I've no idea why you're having these issues with your Duo2 when flashing openPli 4.0.

I myself have probably flashed my Solo2 more times than I care to remember in the last month or so using a fat32 formatted 8gb usb stick with most of the images available out there, including openPli obviously.

The procedure is always the same and there's no need for any workarounds whatsoever in order to flash the box effortlessly. Simply power off the box at the back and remove any extra usb stick you might have. Place your usb stick with the image of your choice in the front, power the box back on at the rear and press the power button at the front when asked. That's it.

One thing I do when a new image is installed is always leave the tuner configuration as "not configured". Set up everything else first and when finished load your own channel settings with dremboxEdit or dreamset. Reboot and finally configure your tuner's accordingly.

[christophecvr]

@kota

 

Nice for You but that does not work out. And the max partion size for fat32 is 4GB.

 

But yes many ways leads to a solution and You are ass well using a work around

[ana_simo_sat]

Only Christophecvr method has resolved this problem. we must dont power off the box at the back button. thankx

[ana_simo_sat]

christophercvr: any new about the PLIBMC project for vu+ box?

[blzr]

I've no idea why you're having these issues with your Duo2 when flashing openPli 4.0.

I myself have probably flashed my Solo2 more times than I care to remember in the last month or so

the difference is that unlike solo2, vu+duo2 is (thanks to vu devs) probably the first known casualty of the Y2038 problem

[Erik Slagter]

the difference is that unlike solo2, vu+duo2 is (thanks to vu devs) probably the first known casualty of the Y2038 problem

ROFL!!!

 

Actually the problem has more something to do with the time being < 1970, which, according to Unix, is the Begin Of Time. IIRC we had some sort of workaround for it.

[christophecvr]

the difference is that unlike solo2, vu+duo2 is (thanks to vu devs) probably the first known casualty of the Y2038 problem

ROFL!!!

 

Actually the problem has more something to do with the time being < 1970, which, according to Unix, is the Begin Of Time. IIRC we had some sort of workaround for it.

Ok yess it's only the vuduo2 not the solo2 then sorry.

 

And I was scarred 14 years ago about the Y2000 possible bug . Agree vu dev's brings some fun

[blzr]

the difference is that unlike solo2, vu+duo2 is (thanks to vu devs) probably the first known casualty of the Y2038 problem

ROFL!!!
 
Actually the problem has more something to do with the time being < 1970, which, according to Unix, is the Begin Of Time. IIRC we had some sort of workaround for it.

IMHO it's exactly Y2038 bug example (triggered prematurely by by vu devs with this 'big number' instead of 0)...

BusyBox v1.21.1 (2013-09-05 05:11:38 CEST) multi-call binary.
root@et9x00:~#  date -D "%s" -d 3945083648
Sun Nov 30 11:05:52 CET 1958

an here my 64 bit machine:

BusyBox v1.20.2 (Ubuntu 1:1.20.0-8.1ubuntu1) multi-call binary.
bart@bart:~$ busybox date -D "%s" -d 3945083648
Wed Jan  5 17:34:08 CET 2095

I suspect 2095 wouldn't be a problem, but pre-epoch 1958 is...

[Erik Slagter]

The problem is lame programmers using an "int" to store time, while they should be using a "time_t" as is stated in the manual page. Time_t should be an unsigned int so this problems shouldn't occur. Unix doesn't know of dates < 1970, a time should always be positive 32 bits. Or even better 64 bits.

[ana_simo_sat]

Erik Slagter: any news about the PLIBMC project for vu+ box?

[Erik Slagter]

I believe there will be some public announcement in a few days, probably tuesday.

[ana_simo_sat]

Erick Slagter: this nex software will be available for mips cpu like vu+duo2 or new boxes?

[Erik Slagter]

I believe there will be some public announcement in a few days, probably tuesday.