Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! 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 £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[GiGaBlue QUAD+ PLUS] Boot loop

  • Thread starter Thread starter kupusar
  • Start date Start date
Thanks, i managed to get logs with USB.
 

Attachments

Crash is here
Code:
<   591.339> Traceback (most recent call last):
<   591.339>   File "/usr/lib/enigma2/python/mytest.py", line 614, in <module>
<   591.339>     Components.AVSwitch.InitAVSwitch()
<   591.340>   File "/usr/lib/enigma2/python/Components/AVSwitch.py", line 736, in InitAVSwitch
<   591.340>   File "/usr/lib/enigma2/python/Components/AVSwitch.py", line 266, in setConfiguredMode
<   591.340>   File "/usr/lib/enigma2/python/Components/AVSwitch.py", line 162, in setMode
<   591.340> IOError: [Errno 1] Operation not permitted: '/proc/stb/video/videomode_50hz'

Thanks for logs, someone will have a look soon.

I suspect that this will need editing.

Code:
        if os.path.exists('/proc/stb/video/videomode_50hz') and getBoxType() not in ('gb800solo', 'gb800se', 'gb800ue'):
            f = open("/proc/stb/video/videomode_50hz", "w")
            f.write(mode_50)
            f.close()
        if os.path.exists('/proc/stb/video/videomode_60hz') and getBoxType() not in ('gb800solo', 'gb800se', 'gb800ue'):
            f = open("/proc/stb/video/videomode_60hz", "w")
            f.write(mode_60)
            f.close()
        try:
            set_mode = modes.get(int(rate[:2]))
        except: # not support 50Hz, 60Hz for 1080p
            set_mode = mode_50
        f = open("/proc/stb/video/videomode", "w")
        f.write(set_mode)
        f.close()
        map = {"cvbs": 0, "rgb": 1, "svideo": 2, "yuv": 3}
        self.setColorFormat(map[config.av.colorformat.value])
 
Last edited:
can you try the following please?


Issue "init 4" command, this will stop enigma2.

Download the attachment,
unzip it

Transfer Avswitch.py to
/usr/lib/enigma2/python/Components

On restart it will decompile and overwrite the pyo

You can restart with following command
Code:
init 4 && sleep10 && init 3

If it boots fine, please delete the .py you transferred. I have added the two GB receivers mentioned in this thread. Please confirm if problem is fixed with attached file so that we can add amendments to the files used to make images. Thanks

EDIT:
Attachment removed owing to error. Corrected one below.
 
Last edited:
Any suggestion?

root@gbquadplus:~# cd/
root@gbquadplus:/# init 4 && sleep10 && init 3
-sh: sleep10: not found
 
Sould be sleep 10 (with a space).
 
I know, but something wasn't working as aspected in GBCC/telnet and I just type it.

Finally, fix is working.
 
Last edited by a moderator:
I didn't choose it. It is as default, only set HDMI and multi refresh rate.
 
The receiver cant handl multi. set it to 50Hz.

If that does not work, best to flash slightly older image until drivers are fixed.
 
Hi @abu, is that true for the GB HD Ultra UE as well?

Rob
Sorry about delayed response, yes it is the same.

The receivers do not support multi refresh rates, but they ave added the entries in the drivers. we previously had a workaround for some fof them, but they are now needed for more receivers.

They should really remove the invalid entries instead of expecting images to add hacks to avoid the crashes.

Until drivers are updated, someone could upload a modified file that deals with the brand instead of individual machines.
 
Can someone with a Gigablue affected by this issue try this file please?


Issue "init 4" command, this will stop enigma2.

Download the attachment,
unzip it

Transfer Avswitch.py to
/usr/lib/enigma2/python/Components

On restart it will decompile and overwrite the pyo

You can restart with following command
Code:
init 4 && sleep10 && init 3

If it boots fine, please delete the .py you transferred. Please confirm if problem is fixed with attached file so that we can add amendments to the files used to make images. Thanks
 

Attachments

Last edited:
@abu - I posted earlier in the thread that I was unaffected by this error. I use a fixed 1080i 50Hz output (or occasionally 1080p 50Hz). However, this morning I notice that my GB Quad+ has been in a boot loop since its scheduled wake-up time of 06:00. The following key information is in the debug log (it's not a crash log):

Code:
<   762.783> [VideoHardware] setting aspect: 16:9
<   762.783> [VideoHardware] setting wss: auto
<   762.784> [VideoHardware] setting policy: panscan
<   762.786> [VideoHardware] setting policy2: letterbox
<   762.945> [VideoHardware] setting scaler_sharpness to: 00000005
<   762.950> [VideoHardware] setMode - port: YPbPr, mode: 1080i, rate: 50Hz
[MAIN] executing main
<   762.951> Traceback (most recent call last):
<   762.951>   File "/usr/lib/enigma2/python/mytest.py", line 614, in <module>
<   762.952>     Components.AVSwitch.InitAVSwitch()
<   762.952>   File "/usr/lib/enigma2/python/Components/AVSwitch.py", line 736, in InitAVSwitch
<   762.952>   File "/usr/lib/enigma2/python/Components/AVSwitch.py", line 266, in setConfiguredMode
<   762.952>   File "/usr/lib/enigma2/python/Components/AVSwitch.py", line 162, in setMode
<   762.953> IOError: [Errno 1] Operation not permitted: '/proc/stb/video/videomode_50hz'
<   762.961> [eDVBDB] ---- saving lame channel db
<   763.017> [eDVBDB] saved 90 channels and 1052 services!
<   763.045> [eDVBResourceManager] release cached channel (timer timeout)
<   763.045> [Avahi] avahi_timeout_new
<   763.049> [Avahi] avahi_timeout_free

<   763.049> [Avahi] avahi_watch_free
<   763.050> [Avahi] avahi_timeout_free

<   763.050> [eDVBLocalTimeHandler] set RTC to previous valid time
<   763.050> [eDVBLocalTimerHandler] set RTC Time

I presume my issue is the same as others have experienced. However it's odd that it has taken weeks to manifest on my box. Do you know why a shut-down and re-boot clears it (maybe temporarily)?
I'm a bit confused as to the reference to "50Hz not permitted" - the GB Quad+ hardware will handle all SD and HD resolutions at all framerates usually. I have another box (MB Twin) which will not support 50p but will handle 50i, but the GB handles everything.
I can try the .py file.
 
Last edited:
@abu - you have a syntax error in that .py file. This causes a boot loop also. I can't risk changing and testing the .py just at the moment as my other half's Aussie soaps are about to start :eek:

See details:
Code:
[MAIN] executing main
<  1421.439> Traceback (most recent call last):
<  1421.439>   File "/usr/lib/enigma2/python/mytest.py", line 28, in <module>
<  1421.439>     from Screens import InfoBar
<  1421.439>   File "/usr/lib/enigma2/python/Screens/InfoBar.py", line 4, in <module>
<  1421.439>   File "/usr/lib/enigma2/python/Screens/MovieSelection.py", line 34, in <module>
<  1421.440>   File "/usr/lib/enigma2/python/RecordTimer.py", line 16, in <module>
<  1421.440>   File "/usr/lib/enigma2/python/Screens/Standby.py", line 4, in <module>
<  1421.441>   File "/usr/lib/enigma2/python/Components/AVSwitch.py", line 256
<  1421.441>     if os.path.exists('/proc/stb/video/videomode_60hz') and and getBrandOEM() != 'gigablue':
<  1421.442>                                                               ^
<  1421.442> SyntaxError: invalid syntax
<  1421.444> [eDVBDB] ---- saving lame channel db
 
@abu - I removed the superfluous "and". The box booted fine afterwards.

Any chance of an explanation as to what caused the issue? It seemed to be after the update to the new linux kernel. Is the box behaviour/capability any different? Or is it just an incompatibility between the code and the GB drivers (which also updated fairly recently)?
 

OpenViX Feeds Status

Back
Top