Boot loop

[kupusar]

Hi, now I get error when I start wathcing a free channel.

[abu baniaz]

What did you set your resolution as?

[kupusar]

I didn't choose it. It is as default, only set HDMI and multi refresh rate.

[abu baniaz]

The receiver cant handl multi. set it to 50Hz.

If that does not work, best to flash slightly older image until drivers are fixed.

[robiom]

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

[abu baniaz]

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.

[abu baniaz]

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

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

[Joe_90]

@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):

<   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.

[Joe_90]

@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

See details:

[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

[Joe_90]

@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)?

[abu baniaz]

I have updated the file in post 37.

Andy said that there was an issue where they do not support some modes. Looks like the issue which affected some models, now affects more of their models. As you know Andy is not happy about adding workarounds, he'd rather that the problems were addressed where they lie, at driver level. No point adding a mode to drivers if you don't support it.

The file in post 37 deals with all Gigablues instead of the individually listed ones. The irony is that adding the "workaround" means that the manufacturer may not have to adjust the drivers. There was a subsequent crash reported by the previous poster, that needs checking too.

[Joe_90]

@abu - that's the bit I don't understand - "do not support some modes" The GB Quad+ supports 480i/p, 576i/p, 720p, 1080i/p at the "usual" TV frame rates of 50Hz and 60Hz. I don't recall ever trying to playback 24fps material with it, but wouldn't really expect it to.

As regards the .py "fix", how will I know if it is working? I've had 4.2.030 installed for almost two weeks now and have not had a problem manifest itself until today. I hadn't changed anything in my AV settings either, so I don't know what triggered the problem today.

[abu baniaz]

Sorry, I don't know the specifics.

Are you using your own build or official build?

[Joe_90]

I'm using Release 4.2.030 official.

[jawz]

is anyone else experiencing problems with the WiFi with this 4.2.030 official release too? Not having any loop problems but my Gigablue Quad+ can't connect to WiFi and most of the times struggles to even find the list of wireless networks. Updated it with a fresh usb flash.

Then when i downgraded to older release it works fine but can't use the plugins download section. I guess this is a problem since the kernels were updated?

Thanks
jawz