1308 replies to this topic

[ferra1]

Whit "Zgemma H9 combo" not work! (openpli 7.3 and openpli 8)

[Dimmie]

Openpli 8 (2020/12/31)

Backupsuite (git515+8834910-r0.0)

 

libmtd: error!"/dev/" is not a character device

nandump: error!: mtd_get_dev_info failed

First of all, the H9.2H SE was not recognized by backupsuite, so I added this line to the lookuptable:

Zgemma H9SE.2H    h9se.2h    Zgemma H9SE.2H    /zgemma/h9    /fullbackup_h9    /zgemma    -m 2048 -e 126976 -c 8192    -m 2048 -p 128KiB    rootfs.ubi    uImage    none

 

Now the box is recognized, but now it gives exactly the same error as the H9 Combo:

 

libmtd: error!"/dev/" is not a character device

nandump: error!: mtd_get_dev_info failed

 

Anyone know the solution ?

Edited by Dimmie, 21 May 2021 - 01:46.

[WanWizard]

I have no idea what all these parameters mean, but I assume it is a copy of an other line?

 

The H9 Combo/Twin and the H9 SE are different from the H9, more like the Mutant HD60.

[Dimmie]

These boxes are in the lookuptable:

 

Zgemma H9 Combo    h9combo    Zgemma H9 Combo    /zgemma/h9combo    /fullbackup_h9combo    /zgemma    -m 2048 -e 126976 -c 8192    -m 2048 -p 128KiB    rootfs.ubi    uImage    none
Zgemma H9 Combo SE    h9combose    Zgemma H9 Combo SE    /zgemma/h9combose    /fullbackup_h9combose    /zgemma    -m 2048 -e 126976 -c 8192    -m 2048 -p 128KiB    rootfs.ubi    uImage    none
Zgemma H9 SE    h9se    Zgemma H9 SE    /zgemma/h9se    /fullbackup_h9se    /zgemma    -m 2048 -e 126976 -c 8192    -m 2048 -p 128KiB    rootfs.ubi    uImage    none
Zgemma H9 Twin    h9twin    Zgemma H9 Twin    /zgemma/h9combo    /fullbackup_h9combo    /zgemma    -m 2048 -e 126976 -c 8192    -m 2048 -p 128KiB    rootfs.ubi    uImage    none

 

HD 60 is different listed:

HD 60    hd60    Mutant HD60    /hd60    /fullbackup_hd60                rootfs.tar.bz2    uImage    none

Edited by Dimmie, 21 May 2021 - 14:38.

[WanWizard]

Ok, wrong guess then. No further idea, I've never used it.

 

Do you have the exact  error output, or the log file?

[WanWizard]

Looking at the backupsuite script:

 

https://github.com/p...upsuite.sh#L347

https://github.com/p...upsuite.sh#L441

 

have h9se hardcoded, so I assume they also need changing to h9se.sh ?

 

edit: also the plugin code itself has hardcoded references.

Edited by WanWizard, 21 May 2021 - 15:23.

[WanWizard]

Tried to do some debugging.

 

The entire code is wrong for the H9 multiboot boxes, as they should indeed folllow the rules for the HD60.

 

Can anyone with a H9 multiboot model, please flash the current nightly build image in a slot, boot it, and report the contents of the file /proc/stb/info/boxtype please?

[WanWizard]

With the changes to the HD60 format, the backup works fine.

 

 screenshot_20210521181438.jpg   102.14KB   3 downloads

 

To fix this I need a list of all boxtype values of all H9 models that are multiboot capable ( so not the original H9 ! )

[WanWizard]

Fix pushed: https://github.com/p...9624fd0a35e4bb9

[Dimmie]

Thank you for the quick response.

 

First of all I had to add this line to the lookuptable to get the H9.2H SE recognized:

 

Zgemma H9SE.2H    h9se.2h    Zgemma H9SE.2H    /zgemma/h9se    /fullbackup_h9se    /zgemma            rootfs.tar.bz2    uImage    none

 

But after all it still does not succeed in making a backup.

 

 

 

 

 

 

 

 

Attached Files

•  20210522_193610.jpg   118.01KB   1 downloads

Edited by Dimmie, 22 May 2021 - 18:43.

[WanWizard]

There were also changes in the code.

 

edit: there seems to be a space missing before a "-o" on line 377 of backupsuite.sh.

 

Difficult if you don't have a box to test it on...

[Dimmie]

I also tried to install develop, installed backupsuite, put the two fixed files

Put extra line to get the box recognized > same problem

root.ubifs is made and then it stops.

[WanWizard]

Our comments have crossed.

[Dimmie]

We were almost there.

 

backupsuite.sh:

 

In line 377 and line 441, the following must be added:

 

-o $SEARCH = "h9se.2h"

 

 

 

In lookuptable.txt , this line must be added:

Zgemma H9.2H SE    h9se.2h    Zgemma H9.2H SE    /zgemma/h9se    /fullbackup_h9se    /zgemma            rootfs.tar.bz2    uImage    none

 

 

And then backupsuite works fine.

 

Can this be pushed in the next update ?

[WanWizard]

I thought I'd added all of them? I'll have a look.

[WanWizard]

Are they all there now?

[Dimmie]

Yes, I think so. But the problem is I cannot test H9S SE since I don't have this box here. I onlly have the H9.2H SE.

 

I have also never heard of any Zgemma H8 and Zgemma HZero that are both listed in the lookuptable ?

Edited by Dimmie, 23 May 2021 - 03:01.

[WanWizard]

They haven't been released yet as far as I know, but are defined in the BSP. Zgemma has asked us not to build them. I've never seen a H10 in the wild too...

[WanWizard]

Yes, I think so. But the problem is I cannot test H9S SE since I don't have this box here. I onlly have the H9.2H SE.

 

If you box works, I'm confident the other SE's work too.

[magicsonny]

Hello. i get this error:

cat: can't open '/sys/firmware/devicetree/base/chosen/kerneldev': No such file or directory

 

On github page is written that If you got this error

 

It means Backup Suite couldn't detect "/dev/mtd# or /dev/mmcblk0p#" of your kernel and needs to be added to the manual detection.

 

how can fix? i have openpli 8 on zgemma h9.2h se