Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[VU+ Duo4K SE] Box cycling endlessly after failed update to 6.7.0019

point17

Forum Supporter
Donated Member
Joined
Apr 11, 2015
Messages
67
Reaction score
0
Points
6
Age
61
What type of support thread are you creating?
Support question
What OpenViX Image build number are you using?
6.7.0019
Have you tried re-flashing WITHOUT settings restore?
NO
Have you tried re-flashing WITH a settings restore?
NO
Hi,

I tried to use Software Update to take my Vu from 6.7.009 (I think) to 6.7.0019. The update hung on the OpenVIX blue screen with the hexagons. I left it for an hour and then tried to follow the advice in another thread to use putty to enter commands "init 4" and then "opkg update && opkg upgrade". These produced what looked like sensible output ending with a request to reboot, which I did from putty.

However, the box is not booting - it tries to boot and briefly displays some error messages before rebooting, in a seemingly endless cycle. The last message is: "ImportError: cannot import name 'startVideoJudderDriverFixTask' from 'Components.AVSwitch' (/usr/lib/enigma2/python/Components/AVSwitch.py)". Then "[MAIN] (exit code 5). I can, however, access the Vu's root filesystem from a Windows box and have retrieved the attached log. It's generating a new one 5 or 6 times a minute.

Does anyone have any advice on how I can restore the box to a usable condition? I'm guessing that the best thing to do is to reflash the latest image downloaded onto a USB drive - is that correct or might that make the situation worse?

Thanks,
Dan
 

Attachments

Hi,

I tried to use Software Update to take my Vu from 6.7.009 (I think) to 6.7.0019. The update hung on the OpenVIX blue screen with the hexagons. I left it for an hour and then tried to follow the advice in another thread to use putty to enter commands "init 4" and then "opkg update && opkg upgrade". These produced what looked like sensible output ending with a request to reboot, which I did from putty.

However, the box is not booting - it tries to boot and briefly displays some error messages before rebooting, in a seemingly endless cycle. The last message is: "ImportError: cannot import name 'startVideoJudderDriverFixTask' from 'Components.AVSwitch' (/usr/lib/enigma2/python/Components/AVSwitch.py)". Then "[MAIN] (exit code 5). I can, however, access the Vu's root filesystem from a Windows box and have retrieved the attached log. It's generating a new one 5 or 6 times a minute.

Does anyone have any advice on how I can restore the box to a usable condition? I'm guessing that the best thing to do is to reflash the latest image downloaded onto a USB drive - is that correct or might that make the situation worse?

Thanks,
Dan
so 1st try this and if that doesn,t work, we can look at other alternatives.
Use putty or equivalent to telnet to the box using login root and your passsword ... if password is not set then enter passwd and set one and repeat.
In telnet type init 4 (space between)
In filezilla or another similar program copy attachment to /usr/lib/enigma2/python/Components
In putty/telnet type init 3 (space between) and see if it boots.
If it boots then immediately use ImageManager to flash latest image

Post back results
 
so 1st try this and if that doesn,t work, we can look at other alternatives.
Use putty or equivalent to telnet to the box using login root and your passsword ... if password is not set then enter passwd and set one and repeat.
In telnet type init 4 (space between)
In filezilla or another similar program copy attachment to /usr/lib/enigma2/python/Components
In putty/telnet type init 3 (space between) and see if it boots.
If it boots then immediately use ImageManager to flash latest image

Post back results

Thanks. I'll try that but I don't see any attachment in your message. Maybe the new forum user interface is confusing me - where should I be looking?

Cheers,
Dan
 
Thanks. I'll try that but I don't see any attachment in your message. Maybe the new forum user interface is confusing me - where should I be looking?

Cheers,
Dan
sorry trying to do too many things at same time!
 

Attachments

Thanks. I'll try that but I don't see any attachment in your message. Maybe the new forum user interface is confusing me - where should I be looking?

Cheers,
Dan
you also need this in
same library
 

Attachments

you also need this in
same library

OK. So transferring those two files across has stopped the cycling behaviour but an "init 3" only gets me as far as the blue screen. I've tried rebooting (using putty) a couple of times but get the same result.

Log attached. The relevant bit looks like it might be this section:
< 45.772554> 12:46:26.8264 Traceback (most recent call last):
< 45.772664> 12:46:26.8265 File "/usr/lib/enigma2/python/StartEnigma.py", line 471, in <module>
< 45.773892> 12:46:26.8277 from Components.SystemInfo import SystemInfo # noqa: E402 don't move this import
< 45.774322> 12:46:26.8281 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
< 45.774388> 12:46:26.8282 File "/usr/lib/enigma2/python/Components/SystemInfo.py", line 178, in <module>
< 45.774933> 12:46:26.8288 from Tools.Multiboot import getMultibootslots, isFat32 # noqa: E402 This import needs to be here to avoid a SystemInfo load loop!
< 45.775418> 12:46:26.8292 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
< 45.775550> 12:46:26.8294 ImportError: cannot import name 'isFat32' from 'Tools.Multiboot' (/usr/lib/enigma2/python/Tools/Multiboot.py)

Anny thoughts on what to try next?

Thanks,
Dan
 

Attachments

OK. So transferring those two files across has stopped the cycling behaviour but an "init 3" only gets me as far as the blue screen. I've tried rebooting (using putty) a couple of times but get the same result.

Log attached. The relevant bit looks like it might be this section:
< 45.772554> 12:46:26.8264 Traceback (most recent call last):
< 45.772664> 12:46:26.8265 File "/usr/lib/enigma2/python/StartEnigma.py", line 471, in <module>
< 45.773892> 12:46:26.8277 from Components.SystemInfo import SystemInfo # noqa: E402 don't move this import
< 45.774322> 12:46:26.8281 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
< 45.774388> 12:46:26.8282 File "/usr/lib/enigma2/python/Components/SystemInfo.py", line 178, in <module>
< 45.774933> 12:46:26.8288 from Tools.Multiboot import getMultibootslots, isFat32 # noqa: E402 This import needs to be here to avoid a SystemInfo load loop!
< 45.775418> 12:46:26.8292 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
< 45.775550> 12:46:26.8294 ImportError: cannot import name 'isFat32' from 'Tools.Multiboot' (/usr/lib/enigma2/python/Tools/Multiboot.py)

Anny thoughts on what to try next?

Thanks,
Dan
forgot to ask - which receiver??
so one last try before usb flash.
Multiboot.py goes in /usr/lib/enigma2/python/Tools
MultiBootSelector goes in /usr/lib/enigma2/python/Screens
 

Attachments

forgot to ask - which receiver??
so one last try before usb flash.
Multiboot.py goes in /usr/lib/enigma2/python/Tools
MultiBootSelector goes in /usr/lib/enigma2/python/Screens

Ah, sorry, I didn't see this as I had already decided to go ahead and re-flash off USB. It took me a couple of attempts but it seems to be working now. Receiver is a VU+ Duo4K SE.

Many thanks for your help.
Dan
 
Ah, sorry, I didn't see this as I had already decided to go ahead and re-flash off USB. It took me a couple of attempts but it seems to be working now. Receiver is a VU+ Duo4K SE.

Many thanks for your help.
Dan
No problem - glad its working
 

OpenViX Feeds Status

Back
Top