Boot loop

[kupusar]

Have anybody stuck in boot loop. I tried clean instal with 4.2.030 and I get boot loop. I tried deleting every plugin and skin by skin and still nothing. It seems that 4.2.028 is the last image I can flash successful (when I try updating I get message The linux kernel has changed, plugins are not compatible. Install latest image using USB stick or image Manager).

[Andy_Hazza]

So how did you update to 4.2.030?


Sent from my iPhone using Tapatalk

[bellejt]

quote : I tried clean instal with 4.2.030

[bbbuk]

Could you clarify you get bootloop on initial flashing of image, or whilst installing your plugins, etc?

[morph]

Hi
I have a similar problem was watching sat box other day all ok turned it off went to bed when i got up turned it on & nothing just had time on 00:01 it was 8am display was dim tried to turn it on & it would'nt so turned it off on the box left it for a minute turned it back on & know all it says on box is 'boot' all i see on screen is openvix logo....
Help please.....

[morph]

sorry its an Edison OS Mini twin tuner

[Joe_90]

@morph - open a new thread for your issue. This thread is about Gigablue Quad Plus.

[kupusar]

Could you clarify you get bootloop on initial flashing of image, or whilst installing your plugins, etc?

I downloaded (www.openvix.co.uk/index.php/downloads/gigablue-images/gigablue-hd-quad-plus/) image 4.2.030 for Gigablue quad plus and extract it. Then I copy/pasted folder gigablue to fat32 formatted USB stick, inserrted into front panel usb port and hit OK on the box when it asked me.

When rec is started, it just keep booting. The black front panel boots till 49% than the front panel screen logo (trees, the road and message please wait) shows up and it goes to 100% and again from 0 to 81 % without black screen and it just repeats all over again infinite like only GUI is restarting before it comes to full start.

[abu baniaz]

Are there any crashlogs in /home/root/logs?

[db2000]

Hello , same problem Gigablue HD800 UE PLUS

[Joe_90]

Just as an aside - I have a GB Quad+ and I am running 4.2.030 without incident. I did a "couch flash" (online download and restore) and restored my settings from 4.2.029. Could there be an issue with the zip downloads? Wouldn't have thought so as they should be the same files.

[abu baniaz]

We wont know without logs. Can you try flashing by USB please @fat-tony

[Joe_90]

We wont know without logs. Can you try flashing by USB please @fat-tony
@abu - my system is ok. Just pointing out that I did a "couch flash" - and I don't have any issues :D . Won't be flashing my GB in the middle of a Wales - England match ;)

[kupusar]

Are there any crashlogs in /home/root/logs?

No logs in the mentioned folder

[abu baniaz]

If you have a HDD attached, issue this command

[

init 4 && enigma2 &> /media/hdd/Enigma2_debug_$(date +%Y-%m-%d_%H-%M-%S).log


Then look at the hdd for the log file. Attach it to this thread please.

Guide to Putty in my signature if you need it.

[BubbleBalls]

Same issue on on regular Quad. Couch flashed to .29 and had bootloop. Just tried updating my second Quad to .30 and exactly the same bootloop. First time I done a Plugin restore, second time I did not, but both Quads bootloop. Interestingly, I tried to USB flash VIX and it would not work. I just tried Openmips image and it flashed OK. Then I try VIX and it is not recognised at boot. Head scratching. Now two of my three boxes are not on VIX. Ouch.

Edit. How can one restore a previously saved image via putty? Or how can one take an image backup from a HDD and make it into a flashable USB file?

[abu baniaz]

Or how can one take an image backup from a HDD and make it into a flashable USB file?

Transfer it to PC and then unzip. You will find the images in /hdd/imagebackups/

[Joe_90]

I'm struggling to understand this issue - my GB Quad+ flashed perfectly to 2.4.030 :confused: I use this as my everyday machine. Still recording daily soaps etc.

[abu baniaz]

Only distinction is you flashed by Image Manager, others flashed by USB.

[BubbleBalls]

I'm struggling to understand this issue - my GB Quad+ flashed perfectly to 2.4.030 :confused: I use this as my everyday machine. Still recording daily soaps etc.
I've used image manager to update from 26 to 29 on one Quad and from 26 to 30 on another and both machines looped. No crash log. I could ftp into them though. Both machines would not allow a fresh USB flash to either 29 or 30. OpenMIPS would flash OK and Abu method below allowed me to flash 26 but very strange things going on with GB lately. Quad, Quad + and UE models showing same issue on Vix. I'll try clean installs today with no restore.

Transfer it to PC and then unzip. You will find the images in /hdd/imagebackups/
Thanks Abu. Up and running again.


Mi Max Tapatalker

[kupusar]

[QUOTE=abu baniaz;439027]If you have a HDD attached, issue this command

Unfortunately I don't have HDD attached. Hope somenone else with the same problem could find logs on the HDD...

[abu baniaz]

If you have a USB stick attached, that will be fine.

[kupusar]

Thanks, i managed to get logs with USB.

[abu baniaz]

Crash is here


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



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])

[abu baniaz]

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


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.

[kupusar]

Any suggestion?

root@gbquadplus:~# cd/
root@gbquadplus:/# init 4 && sleep10 && init 3
-sh: sleep10: not found

[ccs]

Sould be sleep 10 (with a space).

[kupusar]

still nothing

[abu baniaz]

Sorry, I forgot a leading bracket. Please try this one.

BTW, you can paste those commands.

[kupusar]

I know, but something wasn't working as aspected in GBCC/telnet and I just type it.

Finally, fix is working.

[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 :eek:

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

[ccs]

The kernel upgrade on the et10k has rendered my rtl8192cu wifi pretty much useless, I'm stuck on 4.2.026, with, as you say, no more plugin access.

It also knocked my Sundtek usb tuner for six as well.

[BubbleBalls]

HI,

Just updated to 5.0.001 and had bootloop on regular Quad. This file/process fixed it(using space between sleep and 10(corrected in quote below)) Thanks.


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 && sleep 10 && 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

[MrKappa]

Hello' I found this thread and it seems to be useful for my problem. I was watching a channel Gigablue Quad was working fine, then suddenly it shut down and started to boot loop.
Then I downloaded last Openvix image .25 from the website and after I flashed the image I cannot even start the regular setup or restore because the decoder is still rebooting continuously.
I wonder if it some hardware issue or I may try something else. In this condition I cannot telnet to the decoder at the moment.

[twol]

If you have a PC then connect to your router and find out what address the receiver is using (its obviously at the point where it has not setup the normal internet IP)
Then telnet into the box with this IP
Init 4
Enigma2
Paste the log here

[MrKappa]

If you have a PC then connect to your router and find out what address the receiver is using (its obviously at the point where it has not setup the normal internet IP)
Then telnet into the box with this IP
Init 4
Enigma2
Paste the log here

Hello' twol, many thanks for the reply.
I tried flashing only the bootloader and it has started normally, then I could restore the settings and it's working for now.
I will monitor the situation. I hope it's not a sign of bad memory condition or some hardware starting to suffer it's age.....
I will report in case of news.

[Ojustaboo]

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


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.


Just for your info, I had to do this in the past, not sure I had to do it last time when I went to 5.0.017 or the time before.

But I also had to do it today when I went from 5.0.017 to 5.0.032 (USB Flash), was stuck in the same boot loop until I did.

GBQuad (NOT Plus version).

All working fine now.