834 replies to this topic

[Tech]

Even did a reboot, deinstall and install of openwebif but problem persists. Maybe mipsel related?

No not at all, the owi is broken after this commit.

 

Today I flashed a Xsarius Galaxy4k and the owi didn't start, I edited the config.py and the owi runs.

[Tech]

 

That it doesn't fit anymore...

Ok. So why there is possibiltty to download 6.0 RC for Duo?

What can I do to bring alive the box?

 

Flash it back with an OpenPLi4 image.

The bootloader is not a part of the image, so it can´t be corrupted by flashing an OpenPLi6 image.

[Satuser1972]

 

 

That it doesn't fit anymore...

Ok. So why there is possibiltty to download 6.0 RC for Duo?

What can I do to bring alive the box?

 

Flash it back with an OpenPLi4 image.

The bootloader is not a part of the image, so it can´t be corrupted by flashing an OpenPLi6 image.

 

I have no "Starting..." message and of course "Reading USB...". one. Blank display.

Just red light.

 

FYI, I've bought the box in the 2010.

Edited by Satuser1972, 24 September 2017 - 14:57.

[betacentauri]

Maybe not genuine box? As far as I heard there are a couple of VU clones available...

[Satuser1972]

Maybe not genuine box? As far as I heard there are a couple of VU clones available...

In the April of 2010 no any clones were known. DUO was almost just released.

[Tech]

 

Even did a reboot, deinstall and install of openwebif but problem persists. Maybe mipsel related?

No not at all, the owi is broken after this commit.

 

Today I flashed a Xsarius Galaxy4k and the owi didn't start, I edited the config.py and the owi runs.

 

The owi will be fixed after next build.

[Tech]

 

 

 

That it doesn't fit anymore...

Ok. So why there is possibiltty to download 6.0 RC for Duo?

What can I do to bring alive the box?

 

Flash it back with an OpenPLi4 image.

The bootloader is not a part of the image, so it can´t be corrupted by flashing an OpenPLi6 image.

 

I have no "Starting..." message and of course "Reading USB...". one. Blank display.

Just red light.

 

FYI, I've bought the box in the 2010.

 

Just a 'red light' sounds like the well known 'capacitor 807' issue.....

[Satuser1972]

 

 

 

 

That it doesn't fit anymore...

Ok. So why there is possibiltty to download 6.0 RC for Duo?

What can I do to bring alive the box?

 

Flash it back with an OpenPLi4 image.

The bootloader is not a part of the image, so it can´t be corrupted by flashing an OpenPLi6 image.

 

I have no "Starting..." message and of course "Reading USB...". one. Blank display.

Just red light.

 

FYI, I've bought the box in the 2010.

 

Just a 'red light' sounds like the well known 'capacitor 807' issue.....

 

Already replaced twice

[Tech]

I've seen boxes overhere which were 'repaired' more than two times, and even then I had to replace capacitor for a new one.

[Satuser1972]

I've seen boxes overhere which were 'repaired' more than two times, and even then I had to replace capacitor for a new one.

The C807 capacitor was replaced 6 hours ago. Made in Japan.

[foxbob]

Openwebif work.

[Taapat]

I have read complaints about the openpli-6.0 problems on VU+ solo and duo.
Image installation breaks the boot partition.
This problem is not on all receivers, but on individual ones.

 

I can make a mistake, but I have read that solo and duo are two versions.
The first version memory size is smaller. I remember that there was already a problem with one of the plugins.
Openpli-6.0 image is biger than openpli-4.0, and maybe its size exceeds the available memory size on the first version recievers.

 

Maybe it's time to stop solo and duo support or post a warning about it?

Edited by Taapat, 25 September 2017 - 07:09.

[Satuser1972]

I have read complaints about the openpli-6.0 problems on VU+ solo and duo.
Image installation breaks the boot partition.
This problem is not on all receivers, but on individual ones.

 

I can make a mistake, but I have read that solo and duo are two versions.
The first version memory size is smaller. I remember that there was already a problem with one of the plugins.
Openpli-6.0 image is biger than openpli-4.0, and maybe its size exceeds the available memory size on the first version recievers.

 

Maybe it's time to stop solo and duo support or post a warning about it?

I am agree. I have first version of Duo.

Fow now the only possible solution to bring back the box alive is some kind of JTAG via BBS.

Also warning should be posted.

[betacentauri]

But then bootloader is crap. It should check rootfs and kernel size and if that don't fit, it should abort.
Or like on old Xtrends where the bootloader could only flash images < 110 MB. If the image was bigger the flashing "worked", but box didn't boot. But it didn't brick the box. After flashing a smaller image the box worked again.

[betacentauri]

Again me. What I don't understand is why this never happened with PLi 4. Users could install several plugins/picons/... and then make an backup. Flashing such a big image backup should also brick the box if that is really the problem. But I never heard of it and I can't really believe nobody tried that.

[littlesat]

Did you try to re-install openPLi 4?

[Satuser1972]

Did you try to re-install openPLi 4?

No any messages on the display "Starting...", "Reading USB..." Just red light.COM port is also dead.

[betacentauri]

How much flash memory does the first version of the DUO have?

ATV 6.1 image 71,3 MB big. PLi 6.0 75,9 MB. Not really much difference. And with ATV there is no problem?

[Bag58]

@betacentauri

 

VU+Duo original version: Flash 128 MB, RAM 384 MB

[betacentauri]

ubifs uses compression. So flashed image size should be smaller than 128MB... I still don't understand why this image should brick the box.

Edit: Maybe kernel size?
Can somebody with an original Duo post the output of

cat /proc/mtd

Edited by betacentauri, 25 September 2017 - 15:29.