Have hit a big problem

There are 29 replies in this Thread which was already clicked 3,561 times. The last Post () by s1m0nw.

    Hi all,


    Got my new Gigable 800 se hd this morning and i think i've wrecked it already,


    i tried to follow the guide to flash new image but failed miserably, now stuck with gigablue loading on the tv screen for 20mins and no progress... box has a number 25 on the screen,


    It started off with openvix on it but i couldn't find much info on how to install cccam or oscam and set my card up, all the reading i did lead up to flashing with teamred f/w, so i gave it a go, I loaded the 1st set of files onto the formated fat32 usb and plugged it into the box, started it up and it looked like it was loading but the box didn't reboot, after 20 mins of it being stuck on the same page i unplugged the box and ran the 2nd set of files, again it looked like it was starting up then it got to a page saying gigablue with teamred underneath, the lcd panel counts up to 25 then stops, and nothing more happens..


    i have tried to reinstall the bootloader for vix newmorous times but every thing leads to the same place, the box does not reboot as it should when flashing, i have to unplug the box after it gets stuck for 10mins,


    Also when i plug the usb back into my comp it has around 10 files saying enigma2_crash_84 and other numbers


    Does anyone have any idea where i'm going wrong at all?


    thank you

    try openmips mate nice clean image..but if you want to use vix we'll go with that


    Step by step do this


    Get latest bootloader http://linuxsat-support.com/gi…-gigablue-solo-se-ue.html


    format pen drive then put the folder into the pen drive


    switch box off plug pen drive in and switch back on (this process should take a min at most)


    switch box off and remove pen drive


    delete files - get vix image put the gigablue folder onto pen drive


    plug pen drive into box and switch on this process should take no more than ten mins. it should end up with openvix loading screen


    After that ftp a channel list to box and configure tuner settings


    Follow the above and tell us when you cant get any further

    This is one of the crash things that end up back on the usb when i remove it from the box


    <?xml version="1.0" encoding="utf-8"?>
    <opendreambox>
    <enigma2>
    <crashdate>Thu Jan 1 00:07:01 1970</crashdate>
    <compiledate>Feb 17 2012</compiledate>
    <contactemail>crashlog@giga-red-team.eu</contactemail>
    <!-- Please don't email this crashlog to above address -->
    <skin>Default Skin</skin>
    <sourcedate>Feb 17 2012</sourcedate>
    <branch>by RedTeam</branch>
    <rev></rev>
    <version></version>
    </enigma2>
    <image>
    <gigaboxmodel>Gigablue</gigaboxmodel>
    <kernelcmdline> root=/dev/mtdblock0 rootfstype=jffs2 rw bmem=106M@150M</kernelcmdline>
    <nimsockets>NIM Socket 0:</nimsockets>
    </image>
    <crashlogs>
    <enigma2crashlog>
    <![CDATA[
    + (1) Background File Eraser
    + (8) graphics acceleration manager
    + (9) GFBDC
    10800k video mem
    - double buffering available!
    7560kB available for acceleration surfaces.
    resolution: 720 x 576 x 32 (stride: 2880)
    + (9) gLCDDC
    lcd buffer 0x6ba908 8448 bytes, stride 132
    + (9) Font Render Class
    [FONT] initializing lib...
    [FONT] loading fonts...
    [FONT] Intializing font cache, using max. 4MB...
    + (10) gRC
    RC thread created successfully
    + (15) eWindowStyleManager
    + (20) DVB-CI UI
    + (20) UHF Modulator
    couldnt open /dev/rfmod0!!!!
    + (20) RC Input layer
    + (20) misc options
    + (20) AVSwitch Driver
    couldnt open /dev/dbox/fp0 to monitor vcr scart slow blanking changed!
    + (21) input device driver
    Input device "bcm7325 remote control" is not a keyboard.
    Input device "bcm7325 key control" is not a keyboard.
    Found 2 input devices!
    + (21) Console RC Driver
    failed to open /dev/tty0
    + (22) Hdmi CEC driver
    + (30) eActionMap
    + (35) CI Slots
    scanning for common interfaces..
    CI Slot 0 setSource(0)
    eDVBCIInterfaces->setInputSource(0, 0)
    eDVBCIInterfaces->setInputSource(1, 1)
    done, found 1 common interface slots
    + (40) eServiceCenter
    settings instance.
    + (41) eServiceFactoryM2TS
    + (41) eServiceFactoryMP3
    + (41) eServiceFactoryFS
    + (41) eServiceFactoryDVB
    reached rl 70
    resolve: resolve ${sysconfdir}/enigma2/lamedb
    resolve: -> /etc/enigma2/lamedb
    ---- opening lame channel db
    resolve: resolve ${sysconfdir}/enigma2/lamedb
    resolve: -> /etc/enigma2/lamedb
    scanning for frontends..
    opening frontend 0
    detected satellite frontend
    close frontend 0
    opening frontend 1
    failed! (/dev/dvb/adapter0/frontend1) No such device
    failed! (/dev/dvb/adapter0/frontend1) No such device
    opening frontend 2
    failed! (/dev/dvb/adapter0/frontend2) No such device
    failed! (/dev/dvb/adapter0/frontend2) No such device
    opening frontend 3
    failed! (/dev/dvb/adapter0/frontend3) No such device
    failed! (/dev/dvb/adapter0/frontend3) No such device
    boxtype detection via /proc/stb/info not possible... use fallback via demux count!


    found 1 adapter, 1 frontends(1 sim) and 8 demux, boxtype 4
    RTC not ready... wait for transponder time
    [EPGC] Initialized EPGCache (wait for setCacheFile call now)
    resolve: resolve ${datadir}/enigma2/skin_default/pal.png
    resolve: -> /usr/share/enigma2/skin_default/pal.png
    FATAL: pal.png not found!
    resolve: resolve ${sysconfdir}/enigma2/settings
    resolve: -> /etc/enigma2/settings
    ]]>
    </enigma2crashlog>
    </crashlogs>
    </opendreambox>

    Still no joy mate, what ever i try it goes to the same page, on lcd it say boot done at start up then says giga blue, the screen says openvix in black and white, then the screen goes off and lcd starts to count from 1 to 24 then the screan comes back on saying gigablue and teamred underneath, then lcd goes to 25 and screan changes to gigablue with loading underneath, have left it at that for 15mins and it hasn't done anything else

    looks like its not programming right.


    When u said removed it... After programming the image, did you switch box off and removed pen drive then switch it back on?


    Also does your pen have any other files other than he vix team image?

    Ive never had any probelms flashing gigablue. Just trying to suss out where youve maybe gone wrong.


    you used the latest bootloader, loaded onto box switched box back off


    deleted bootloader from pen drive


    put gigablue folder from image onto pen drive and put it into box switch box on let it program then switch box off and removed pen drive then switch box back on


    Can you confirm this is what u did?

    Hi i have 2 pen drives that i have tried


    I now have it working, i had to go back to the team red image i tried to load onto it this afternoon, this time it has loaded and now works.. What a relief!!! thank you for all your help mate, i don't think i'll try that flashing malarky again lol


    It must of got stuck somehow half way through loading teamred and when it didnt work 1st time i tried to revert it back to vix, which wouldnt work


    thanks again

    I would reccomend you get a different image as theres no updates for team red image. But you can do this when you get a bit more comfortable with the box.


    Glad you got it sorted mate and have fun with it now

    searching for info I came across this :



    so this is probably worth a try.... go back to older drivers... before anything else..

    Hi mate, how would i go about installing those drivers, not having much luck with this box, tried ftp the extraurl thing following the instuction and even that says it's failed lol


    Sorry just seen to ftp it, thanks will give it a go

    Is there something missing out of the openvix image file? i managed to flash it with teamred 1st atemp, tried openvix about 30 times but failed miserably everytime, now tried openmips and it has flashed 1st time..


    i have noticed that both teamred and openmips have a burn.bat file in the image files, openvix does not, could this be my problem?


    regards

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login