View Full Version : [Zgemma H7] 1st Bug ZGemma H7 [Resolved, not a bug]
Full Image backup isn't working. The log shows the nanddump is complete but the destination temp folder is empty. The OSD hangs backing up kernel 18/100
< 68.957> [ImageManager] Stage1: Free Mem 670456
< 68.957> [ImageManager] Stage1: Found Enough Ram
< 70.965> [ImageManager] Stage1: Creating tmp folders. /media/hdd/imagebackups/
< 70.965> [ImageManager] Stage1: Creating backup Folders.
< 71.072> [ImageManager] Stage1: Making Kernel Image.
< 71.072> [Console] command: nanddump /dev/mmcblk0p2 -f /media/hdd/imagebackups/ViX-ZGemmaH7-release-temp/vmlinux.gz
< 71.073> [eConsoleAppContainer] Starting /bin/sh
< 71.087> [Console] finished: nanddump /dev/mmcblk0p2 -f /media/hdd/imagebackups/ViX-ZGemmaH7-release-temp/vmlinux.gz
Haven't fully setup the image yet as feeds are still updating. I've flashed the image and added a few plugins locally so far. I have loaded the Automatic Full Backup plugin and that does generate a full image backup OK
I tested this recently and it worked fine.
Sent from my iPhone using Tapatalk
I tested this recently and it worked fine.
Sent from my iPhone using Tapatalkwill check out!
Full Image backup isn't working. The log shows the nanddump is complete but the destination temp folder is empty. The OSD hangs backing up kernel 18/100
< 68.957> [ImageManager] Stage1: Free Mem 670456
< 68.957> [ImageManager] Stage1: Found Enough Ram
< 70.965> [ImageManager] Stage1: Creating tmp folders. /media/hdd/imagebackups/
< 70.965> [ImageManager] Stage1: Creating backup Folders.
< 71.072> [ImageManager] Stage1: Making Kernel Image.
< 71.072> [Console] command: nanddump /dev/mmcblk0p2 -f /media/hdd/imagebackups/ViX-ZGemmaH7-release-temp/vmlinux.gz
< 71.073> [eConsoleAppContainer] Starting /bin/sh
< 71.087> [Console] finished: nanddump /dev/mmcblk0p2 -f /media/hdd/imagebackups/ViX-ZGemmaH7-release-temp/vmlinux.gz
Haven't fully setup the image yet as feeds are still updating. I've flashed the image and added a few plugins locally so far. I have loaded the Automatic Full Backup plugin and that does generate a full image backup OK
Its not recognising it as a Zgemma H7
Can you give me the full debug log or from when ImageManager starts!! attach here.
deleted,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Just couch flashed and usb flashed from the backup and both methods working okay.
Works for me :thumbsup:
Can you also give me a debug log?!
Want to compare logs.....
Tried it 3 times and it failed every time, so I installed the Automatic Full Backup plugin and that created an image OK. I flashed that backup back to the box, then removed the Automatic Full Backup plugin and tried ViX image manager again and it worked, although there is a huge disk.img file in the archive that isn't in the AFB backup and is 100Meg bigger than in the downloaded ViX image.
So I don't know whats happening, maybe the AFB plugin fixed something but it only puts files in plugins and not in the bin or sbin. I'm not goiong to mess around with raw images to try to replicate at this time, will just carry on customising.
This is all that was in the original log from entering the section to it hanging
< 63.171> [Skin] processing screen VIXImageManager:
< 63.216> [Skin] No skin to read...
< 63.216> [Skin] processing screen <embedded-in-'PluginBrowserSummary'>:
< 63.271> [eInputDeviceInit] 0 160 1
< 63.272> [InfoBarGenerics] KEY: 352 OK
< 65.618> [eInputDeviceInit] 1 18f 1
< 65.620> [InfoBarGenerics] KEY: 399 GREEN
< 65.823> [eInputDeviceInit] 0 18f 1
< 65.824> [InfoBarGenerics] KEY: 399 GREEN
< 65.824> [ActionMap] Keymap 'ColorActions' -> Action = 'green'
< 65.828> [Skin] processing screen MessageBox:
< 65.845> [Skin] processing screen MessageBox_summary:
< 66.964> [eInputDeviceInit] 1 160 1
< 66.966> [InfoBarGenerics] KEY: 352 OK
< 66.966> [ActionMap] Keymap 'MsgBoxActions' -> Action = 'ok'
< 66.970> [ImageManager] Device: /media/hdd/
< 66.970> [ImageManager] Directory: /media/hdd/imagebackups/
< 66.971> [ImageManager] MTD Kernel: mmcblk0p2
< 66.971> [ImageManager] MTD Root: mmcblk0p3
< 66.971> [ImageManager] Type: airdigitalemmc
< 66.991> [Skin] processing screen JobView:
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'cancelable' was not found in screen 'JobView'!. Please contact the skin's author!
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'cancelable' was not found in screen 'JobView'!. Please contact the skin's author!
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'finished' was not found in screen 'JobView'!. Please contact the skin's author!
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'finished' was not found in screen 'JobView'!. Please contact the skin's author!
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'backgroundable' was not found in screen 'JobView'!. Please contact the skin's author!
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'backgroundable' was not found in screen 'JobView'!. Please contact the skin's author!
< 67.012> [Skin] processing screen JobView_summary:
< 67.271> [eInputDeviceInit] 0 160 1
< 67.272> [InfoBarGenerics] KEY: 352 OK
< 68.953> [Task] job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
< 68.957> [ImageManager] Stage1: Free Mem 670456
< 68.957> [ImageManager] Stage1: Found Enough Ram
< 70.965> [ImageManager] Stage1: Creating tmp folders. /media/hdd/imagebackups/
< 70.965> [ImageManager] Stage1: Creating backup Folders.
< 71.072> [ImageManager] Stage1: Making Kernel Image.
< 71.072> [Console] command: nanddump /dev/mmcblk0p2 -f /media/hdd/imagebackups/ViX-ZGemmaH7-release-temp/vmlinux.gz
< 71.073> [eConsoleAppContainer] Starting /bin/sh
< 71.087> [Console] finished: nanddump /dev/mmcblk0p2 -f /media/hdd/imagebackups/ViX-ZGemmaH7-release-temp/vmlinux.gz
Tried it 3 times and it failed every time, so I installed the Automatic Full Backup plugin and that created an image OK. I flashed that backup back to the box, then removed the Automatic Full Backup plugin and tried ViX image manager again and it worked, although there is a huge disk.img file in the archive that isn't in the AFB backup and is 100Meg bigger than in the downloaded ViX image.
So I don't know whats happening, maybe the AFB plugin fixed something but it only puts files in plugins and not in the bin or sbin. I'm not goiong to mess around with raw images to try to replicate at this time, will just carry on customising.
This is all that was in the original log from entering the section to it hanging
< 63.171> [Skin] processing screen VIXImageManager:
< 63.216> [Skin] No skin to read...
< 63.216> [Skin] processing screen <embedded-in-'PluginBrowserSummary'>:
< 63.271> [eInputDeviceInit] 0 160 1
< 63.272> [InfoBarGenerics] KEY: 352 OK
< 65.618> [eInputDeviceInit] 1 18f 1
< 65.620> [InfoBarGenerics] KEY: 399 GREEN
< 65.823> [eInputDeviceInit] 0 18f 1
< 65.824> [InfoBarGenerics] KEY: 399 GREEN
< 65.824> [ActionMap] Keymap 'ColorActions' -> Action = 'green'
< 65.828> [Skin] processing screen MessageBox:
< 65.845> [Skin] processing screen MessageBox_summary:
< 66.964> [eInputDeviceInit] 1 160 1
< 66.966> [InfoBarGenerics] KEY: 352 OK
< 66.966> [ActionMap] Keymap 'MsgBoxActions' -> Action = 'ok'
< 66.970> [ImageManager] Device: /media/hdd/
< 66.970> [ImageManager] Directory: /media/hdd/imagebackups/
< 66.971> [ImageManager] MTD Kernel: mmcblk0p2
< 66.971> [ImageManager] MTD Root: mmcblk0p3
< 66.971> [ImageManager] Type: airdigitalemmc
< 66.991> [Skin] processing screen JobView:
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'cancelable' was not found in screen 'JobView'!. Please contact the skin's author!
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'cancelable' was not found in screen 'JobView'!. Please contact the skin's author!
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'finished' was not found in screen 'JobView'!. Please contact the skin's author!
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'finished' was not found in screen 'JobView'!. Please contact the skin's author!
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'backgroundable' was not found in screen 'JobView'!. Please contact the skin's author!
< 66.999> [Skin] Error in screen 'JobView' widget 'widget': [Skin] {slyk-onyx-1080/skin.xml}: [Skin] source 'backgroundable' was not found in screen 'JobView'!. Please contact the skin's author!
< 67.012> [Skin] processing screen JobView_summary:
< 67.271> [eInputDeviceInit] 0 160 1
< 67.272> [InfoBarGenerics] KEY: 352 OK
< 68.953> [Task] job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
< 68.957> [ImageManager] Stage1: Free Mem 670456
< 68.957> [ImageManager] Stage1: Found Enough Ram
< 70.965> [ImageManager] Stage1: Creating tmp folders. /media/hdd/imagebackups/
< 70.965> [ImageManager] Stage1: Creating backup Folders.
< 71.072> [ImageManager] Stage1: Making Kernel Image.
< 71.072> [Console] command: nanddump /dev/mmcblk0p2 -f /media/hdd/imagebackups/ViX-ZGemmaH7-release-temp/vmlinux.gz
< 71.073> [eConsoleAppContainer] Starting /bin/sh
< 71.087> [Console] finished: nanddump /dev/mmcblk0p2 -f /media/hdd/imagebackups/ViX-ZGemmaH7-release-temp/vmlinux.gz
So this is correct: Type: airdigitalemmc but this is wrong - finished: nanddump /dev/mmcblk0p2 -f /media/hdd/imagebackups/ViX-ZGemmaH7-release-temp/vmlinux.gz
So I need to check further....
"is a huge disk.img file in the archive that isn't in the AFB backup and is 100Meg bigger than in the downloaded ViX image."
...........thats correct as ImageManager creates BOTH usb flash file(disk.img ... which will be bigger than ViX original) and the kernel and root for multiboot flashing.
@lincsat you could try running with the following ftp'ed to /usr/lib/enigma2/python/Plugins/SystemPlugins/ViX
rename the existing .pyo first, as it has changes that are not currently in the live version! Work for me but .....
58152
@Lincsat are you running with settings backup enabled and/or imagebackups enabled to run on a scheduled basis??
Reason I ask is that the "job" started before finishing the initial code.
I have setup for regular backups+Imagebackups and set a custom prefix.
I've put the updated imagemanager.py on and it seems to be backing up OK, like I said, I've not gone back to default settings
Debug log attached.
Many thanks ... thats what I expected to happen.
Your log implies that Lincsat must have something set (automatic scheduled abckup?) that starts running the backup job before the initial settings are complete.
Just noticed something else, may be hardware but didn't notice when using ATV.
On a channel change, the LED appeared to be slightly flickering, so went into LED manager, didn't change anything but did press save, now on a channel change, the number comes up for a few seconds, then when it goes back to clock, it flickers between clock and channel number for a few seconds before the clock becomes solid.
I have setup for regular backups+Imagebackups and set a custom prefix.
I've put the updated imagemanager.py on and it seems to be backing up OK, like I said, I've not gone back to default settings
Many thanks - you must be one of the few!
However, looks like there is a bug in this scheduled imagebackup code ........
Just noticed something else, may be hardware but didn't notice when using ATV.
On a channel change, the LED appeared to be slightly flickering, so went into LED manager, didn't change anything but did press save, now on a channel change, the number comes up for a few seconds, then when it goes back to clock, it flickers between clock and channel number for a few seconds before the clock becomes solid.
Dunno what your setting, but front panel is working like any other 7 Segment LED display in OpenViX here. Shows clock all the time. If you key in a channel number then press ok, channel number briefly shows, then reverts back to clock. On reboot will briefly show clock > channel number > then clock and remains on clock. All 7 segment displays behave this way in OpenViX.
On channel change using CH UP / DOWN breifly shows channel number then reverts back to clock, this is normal.
But it's not normal for the display to flicker between channel number and clock for a few seconds
But it's not normal for the display to flicker between channel number and clock for a few seconds
If it does it on channel change it’s normal, that’s how 7segment displays have been setup.
All 7 segment displays have been set the same.
Sent from my iPhone using Tapatalk
Here's a video, never seen it on other boxes
Here's a video, never seen it on other boxes
No idea what you've setup but not doing that here.
Just noticed something else, may be hardware but didn't notice when using ATV.
LED manager
What LED Manager?
@lincsat .... just curious! But did you do a settings restore from another receiver?
There is no previous ViX image to do a restore from, I did consider restoring a backup from ATV but decided against that
LED Manager is in System, this was the default setting, I've now set to clock only
58154
There is no previous ViX image to do a restore from, I did consider restoring a backup from ATV but decided against that
LED Manager is in System, this was the default setting, I've now set to clock only
58154
That is not part of OpenViX image, looks like you installed a plugin somehow.
You have got vfdcontrol installed in system plugins, you need to remove it.
Dunno how he's installed it becuase the feeds aint even online yet!
I don't know either but vfdcontrol will add the led settings to the front panel display menu and cause all sorts of weird problems on an Arm box.
There is no previous ViX image to do a restore from, I did consider restoring a backup from ATV but decided against that
LED Manager is in System, this was the default setting, I've now set to clock only
58154
I meant settings backup ... I see more and more people transferring settings from another different receiver
I meant settings backup ... I see more and more people transferring settings from another different receiver
Never thought of that, maybe I should have tried using the settings backup from an Ultimo4K.
Anyway, I started again from scratch once the feeds were up, so I didn't need to use local files for all the plugins. This time the Image backup works and the disk.img file compresses significantly smaller making the final zip a whopping 75Meg smaller
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.