125 replies to this topic

[athoik]

Sources are here as I was informed: https://github.com/PURE2-Team

Based on OE-A.

[littlesat]

Last source changes may 2018 ??? Only 8 commits ???

Edited by littlesat, 22 December 2018 - 08:48.

[athoik]

I guess they just pushed some sources without keeping "git history".

Anyway sources are public, so they didn't violate the GPLv2 license.

Obviously there is some issue with scan, and when there is an issue "deus ex machina" a semi open/close image has the solution.

Nice way to promote pure2...

[littlesat]

Latest sources seems not to be public when they have more recent images.... but maybe the solution is just change the region from australia to Europe -or- make smaller frequency steps...

Edited by littlesat, 22 December 2018 - 14:31.

[gorski]

Jesus Marx.... constantly cutting my text, adding some silly text...

Edited by gorski, 22 December 2018 - 14:55.

[gorski]

Arrrgghhh!!!

Edited by gorski, 22 December 2018 - 14:55.

[gorski]

Just to make it clear: I merely tested OpenPLi 7, as advised by WTE. One must keep comparing, obviously, so as it was good advice, I tested in good faith. I only mentioned what I compared with, to make it clear where I found flaws, which others have confirmed. I did not go into this with the idea of PurE2 'promotion'. That is a wild accusation and stretching it badly... Please... I even stopped mentioning it (until now, for obvious reasons) because "some members of OpenPLi" did not like me stating my opinion on the matter and kept deleting my messages about it...

 

And I tried giving solutions to some of the problems, pointing to PurE2 contributions to the hobby. Even if it is not under PurE2 coder's names, these still go back to the community, usually via Captain. Graugans, Delfi, Franc, Terra, Mario are OK guys!

 

Easy for you to 'bitch' about GIT not being up to date but how big a team is your team (or OpenATV for that matter, who frequently level this kind of accusation on PurE2)?

 

Believe me, you wouldn't want all kinds of problems that some of them have to deal with, from sheer survival onwards. But they still contribute to the hobby...

 

(Had to post a third message from Opera... sorry...)

Edited by gorski, 22 December 2018 - 14:57.

[WanWizard]

Easy for you to 'bitch' about GIT not being up to date but how big a team is your team

 

Not as big as we'd like to, and certainly not as big as the perception of some people.

 

PLi is a very old team, a lot of people are not active anymore (but still a team member), or are only testers or moderators, and not developers. If you look at the commits, you have about 3 that regularly commit to our OE, and maybe 2 that commit regularly to our Enigma2?

[gorski]

Yes but as an established Team/GIT you have people adding to it regardless of membership, non?

 

Which is the case with OE-A, too...

 

PurE2 is tiny...

 

P.S. I did not intend to talk about PurE2, as I had enough of "misunderstandings" around it - I only mentioned it as a comparison point, which is necessary. It kept cropping up afterwards but not by my design, I just reacted to some statements, perhaps done in haste, that's all...

[WanWizard]

That is why I wrote "regularly".

 

The plus of being open source is that everyone has access to the source and can propose and submit changes.

 

Given the fact that all OSS images out there are either OpenPLi or OE-A based, you can expect these contributions to happen at the source, and not and the edge (i.e. an image derived from either OpenPLi or OE-A).

 

But an occasional contributor is not an image developer. And that is where the problem lies, you need developers (as in a team of) to tackle larger projects (for example, replace EPG, xml's, bouquets, lamedb by a database), contributors only supply simple one-time additions or fixes.

[gorski]

Here is a PurE2 team's second generation solution for the small flash, guys, for OpenATV image, as a member of LinuxSat Support forum Hisakatano figured it out. Hopefully, it will help OpenPLi image as well, perhaps with a minimal effort? Have a look....

 

SECOND GENERATION SCRIPT FOR EXPANDING ZGEMMA'S H9X/H9.2X FLASH TO MICRO SD CARD/USB STICK

 

ZGEMMA H9X/H9.2X STB (Sat TV receiver) series mostly has a 256 MB Flash, which today is not much to play with...

 

So, serious hobbyists need to expand its Flash to play with Kodi and so on... There are 3 ways:

 

1) old Flash Expander E2 plugin, to a fast USB 3.0 stick (I wrote in detail about it on various forums - but better not do this);

 

2) this script, moving everything (= root) from the flash to a fast Micro SD memory card (much better!);

 

3) using the same script one can now use a fast USB memory stick (especially in H9X series, which has a fast USB 3.0 port)!

 

Various Micro SD cards have been tested: class4, class 10 and class A1.

In principle, they are all working but not every single Micro SD card will work.

 

HOW TO CHECK IF A MICRO SD CARD IS OK FOR FLASH EXPANSION WITH ZGEMMA H9X/H9.2X STB

 

Insert the Micro SD card into Zgemma H9X/H9.2X and reboot the box.

Check the /var/logs/message file, using the PuTTy app. Log in by writing:

 

root

password, if any - for example "pure2" for PurE2 image [without "" signs].

 

Now, copy and paste this telnet command into PuTTy:

cat /var/log/messages | grep mmcblk0:

If you see something like these messages:

Apr 6 19:28:13 zgemmah9t user.info kernel: mmcblk0: mmc0:59b4 USDU1 7.31 GiB
Apr 6 19:28:13 zgemmah9t user.info kernel: mmcblk0: p1

or

May 20 13:25:49 zgemmah9s user.info kernel: mmcblk0: mmc0:aaaa SC64G 59.5 GiB
May 20 13:25:49 zgemmah9s user.info kernel: mmcblk0: p1

...then you can proceed...

 

LET'S DO IT

 

First, please note:

 

Scripts etc. were taken from PurE2 image, where the solution was found for the "second generation problem" of this sort.

 

Thanx to Hisakatano, who published this on LinuxSat Support forum, where I published the first generation solution

to the problem (credit for the first one, I think, goes to the Captain@OpenATV).

 

It seems to me that Hisakatano then came up with this, second solution, having seen it working in PurE2, as described by me.

 

He then informed us how this can be done not only in PurE2, where it is integrated in the image - but also in OpenATV 6.2.

 

So, this manual is for the second generation Script of this sort but in OpenATV v. 6.2 Enigma2 image!

It differs from the first one in several steps, as described below...

 

"How to move '/' (root, i.e. all the folders and files) to mmc (MicroSD) card in OpenATV 6.2 image"

 

One can prepare an mSD card by formatting it in EXT4 (a single active partition).

 

Use freeware "Minitool Partition Wizard" Windows app for the task.

 

Note: it is not necessary, as the script will also do it, inside the box itself.

 

1. Insert micro SD Card into the back mSD slot of Zgemma H9X/H9.2X series.

 

2. Download script.zip and extract it. (See Hisakatano's post earlier!)

 

3. Use FTP Client (FileZilla) App to send the "script" folder to Zgemma H9x/H9.2X > /usr folder.

 

4. Right click on the script folder > "File attributes" > 755 > check the "Recurse in the subdirectories" > OK.

 

5. In OpenATV image go to Info Panel > Plugins > Job Manager > Select H9_boot_mSD.sh > Run.

6. "Are you ready to run the script?" > Yes > Run once > wait for it to finish ("Execution Finished").

 

7. Restart H9X/H9.2X

 

8. After reboot go to Menu > Information > Memory and see if you have loadsa flash suddenly...

 

===============================================================

 

How to go back to a previous state of things (rollback to rootfs, to NAND)?

 

Simply take the mSD out and flash a new image.

 

===============================================================

 

Credits:

 

As far as I know, credit for the first generation script goes to Captain@OpenATV.

 

For this one ("second generation") to work in OpenATV, I do not know whom to credit for sure...

 

BUT I presume Hisakatano figured it out...

 

What I do know is that the problem was solved by Delfi/trom/tromoto of PurE2 team (with a little help from yours truly...).

 

As I said, from what I can see, all the scripts were taken from PurE2 and a solution was found for them to work in OpenATV.

 

In PurE2 everything is done via remote control, the scipt is included in the image: MENU > pManager > Script...

 

As above, i.e. the last part of > step 5, as above > Run once...

 

Additional info and editing by gorski

 

===============================================================

 

P.S. Do not mount Micro SD card using pManager (in PurE2 or any kind of Device Manager in any other Enigma2).

Then, the script can't umount it. Once I unmounted it, using pManager - it worked!

Attached Files

•  script.zip   10.16KB   15 downloads

Edited by gorski, 3 January 2019 - 13:53.

[littlesat]

!/bin/sh

opkg update

opkg install rsync

umount /dev/mmcblk0p1

dd if=/dev/zero of=/dev/mmcblk0p1 bs=1M count=150

mkfs.ext4 -L "H9-ROOTFS" /dev/mmcblk0p1

mkdir /tmp/mmc

mount /dev/mmcblk0p1 /tmp/mmc

mkdir /tmp/root

mount --bind / /tmp/root

rsync -aAXv /tmp/root/ /tmp/mmc/

umount /tmp/root

umount /tmp/mmc

rmdir /tmp/root

rmdir /tmp/mmc

 

sync

sync

sync

 

dd if=/usr/script/bootargs-mmc.bin of=/dev/mtdblock1

 

sync

sync

sync

echo "****************************************"

echo "*  Transfer to mSD done, please reboot *"

echo "****************************************"

sleep 5

[littlesat]

I would say it could better considered to adapt ofgwrite... when there is an usable SD card in the box.. than it flashes on that SD card, and prepare the boot sequence for it... then no script and work-a-rounds required.... Only ''disadvantage' SD required... and the first time you need to flash the flash... Maybe than also bigger SD cards could be devided in 4 partitions ....

Edited by littlesat, 3 January 2019 - 16:15.

[gorski]

Well, if you check the Zgemma devs GIT, they are planning a bootloader to choose a booting menu via RC...

But for now, this works swell!

[littlesat]

That sounds we can better wait....

[gorski]

Still, this is well worth implementing in the meanwhile...

[littlesat]

why work a round it when the manufacturer comes with a solution from themselves...!

Edited by littlesat, 3 January 2019 - 19:29.

[gorski]

...who knows when...

 

In the meantime, your images for H9X/H9.2X are not properly supported, even though this is available...

It will take you, what... 5 minutes to make it run in OpenPLi via RC?

[littlesat]

Everyone can run that script.... (not the whole package is required)... the script that can be simplified either

Edited by littlesat, 3 January 2019 - 21:59.

[gorski]

No need to add/edit anything, check your GUI to see if it can be run via RC etc?

 

So, why not included it, if it is that simple?