Posts by fogonero

  • Barry Allen Latest

    Barry Allen 7.0.6


  • How to Enigma2 to OpenRSI

    credits


    h**p://www.openrsi.org


    Installation procedure from E2 to OpenRSi.


    Be sure you have downloaded the right firmware and/or kernel from our downloadpage.
    Also, be sure that your AZBox HD receiver is connected tot the netwerk, using a LAN cable. We do not recommend Wireless connections.


    NOTE:
    In this tutorial, we will install OpenRSi, including the kernel, which you will find on our downloadpage.
    In case you have installed our kernel in an earlier stage, you do not have to install the kernel again and you can skip the "Installing the kernel" procedure.


    If you want to install OpenRSi from within the original OpenSat firmware, please take a look at the video at the top of the page.


    First step
    If you don't have Azup installed on your PC, please follow the next steps:
    Download and install Azup 2.0.4 (latest installer version).
    Download and unpack Azup 2.1.6
    Download the latest firmware and kernel for your AZBox HD, from our download page.




    Installing the kernel

    • Flip the powerswitch at the back of you AZBox HD receiver.
    • While booting, press and hold the Volume + key on your remote control, until an IP address is shown in the display.
    • Start Azup 2.1.6 on your PC.


    • Please, enter the IP number that was shown to you on the display of the AZBox HD receiver.
    • In Advanced Options, select the "Only kernel" option ( all other options will turn grey).
    • Press the GO button in the Install E2/Kernel section.
    • A window will pop-up. Select the kernel file, which you have downloaded from our downloadpage and double-click on it or click on the Open button.
    • Azup will now install the kernel files. When it is done, the AZBox HD will reboot.




    Installing OpenRSi firmware

    • While booting, press and hold the Volume + key on your remote control, until an IP address is shown in the display.
    • Start Azup 2.1.6.
    • Please, enter the IP number that was shown to you in the display of the AZBox HD receiver.
    • De-select the options "Only Kernel" and "Copy kernel" in Advanced Options.


    • Press the GO button in the Install E2/Kernel section.
    • A pop-up window will show. Select the OpenRSi firmware file, which you have downloaded from our downloadpage and double-click on it or click on the Open button.
    • Azup will now install the OpenRSi firmware. When it is done, the AZBox HD will reboot.
    • After rebooting, your AZBox HD receiver will show the Enigma2 Setup Wizard.




    Pd.I have done tests on this firmware and I was impressed, zapping the fastest I've ever seen in a azbox. OpenPLi based, great job, I recommend.

  • how to Flashing OpenSAT Oficcial to OpenRSI E2

    Flashing your AZBox HD Elite/Premium(+)/Ultra


    If you want to install OpenRSi firmware from you original OpenSat firmware, please follow the steps in this video


    From original firmware


    There is a video we would like to provide on how to install the OpenRSi firmware, using a first generation AZBox HD with the original OpenSat firmware.


  • How to setup OSCAM's CACHE-EX Feature with a friends

    Please note that this tutorial is now out of date for the upto date version please go http://linuxsat-support.com/showthread.php?t=84347


    Thx By CapNCooK



    OSCAM Cache-EX Tutorial
    I was asked to write a little tutorial on howto setup Oscam's CACHE-EX Feature...


    What is Cache-EX ?
    The Cache-EX feature makes it possible to exchange Oscam's caches from server to server.



    Why is Cache useful in general ?
    Quite simple. Even without Cache-EX enabled, Oscam builds a cache by default. Every requested ECM by a client is forwarded to an available card or proxy reader. This ECM will stay in Oscam's memory (cache), until its validity expire. On a busy server, you can imagine that there are quite a lot of valid ECM's in memory.


    When a second client requests an ECM for the same channel, it will automatically forward the available ECM from local cache, without requesting a reader or proxy, resulting on less load on your cards. Obviously, when its not available from local cache, the request is forwarded to a proxy or card.


    You can see answers from Oscam's local cache in your logs.
    The reader-name mentioned, is the reader where the ECM originally came from.



    2012/03/12 1412EAF0 c USER_A (0100&00006A/5212/64:4A32): cache1 (4 ms) by READER1 (13 of 26) - RTL7 HD
    2012/03/12 1412EAF0 c USER_B (0100&00006A/51BD/64:0C7D): cache2 (22 ms) by READER2 (14 of 26) - Sport1 Tennis
    2012/03/12 140E5170 c USER_C (0100&00006A/17CC/64:6172): cache2 (133 ms) by READER3 (14 of 26) - EredivisieLive1 HD
    2012/03/12 141226A0 c USER_D (0100&00006A/17CC/64:6172): cache2 (190 ms) by READER3 (14 of 26) - EredivisieLive1 HD



    OK, so why use Cache-EX on top of the normal cache ?
    Cache-EX can be enabled by adding a special user to the server, and a special reader to the client with corresponding Cache-EX parameters. This reader and user is only capable of transporting cached-ecm's. When no valid cached-ecm is found on the server, the request is 'rejected'.


    The benefit of this method, is that every ECM request on your server will be tried against the cache of your Cache-EX-enabled readers first. The answer on such requests is given very fast, since a server is able to check this in no-time. When no Cache-EX-enabled reader is able to answer the ECM request, the request is forwarded to- and answered by a 'normal' reader.



    How-To setup CACHE-EX
    Like stated above, Cache-EX can be configured with the 'cacheex' parameter on your user or reader.
    To use it, Oscam has to be compiled with CACHE-EX support set to ON.


    The Cache-EX-user must have always the same mode configured as the connecting Cache-EX-reader.


    --


    There are 4 modes you can setup:


    cacheex = 1 - cachepull


    OSCam A reader1 has cacheex = 1
    OSCam B account1 has cacheex = 1


    OSCam A gets a ECM request, reader1 send this request to OSCam B,
    OSCam B checks his cache:


    Not found in cache: return NOK (shows as 'rejected' in logs)
    Found in cache: return OK+CW
    Not found in cache, but found pending request: wait cacheexwaittime in oscam.conf [global] and check again.


    OSCam B never requests new ECMs.
    CW-flow = B ---> A



    cacheex = 2 - cachepush


    OSCam A reader1 has cacheex = 2
    OSCam B account1 hastcacheex = 2


    If OSCam B gets a CW, its pushed to OSCam A, reader has normal functionality and can request ECMs.


    Problem: OSCAM can only push CW's if OSCam A is connected
    Problem or feature?: OSCam A reader can request ECMs from OSCam B
    CW-flow = B ---> A



    cacheex = 3 - reversecachepush


    OSCam A reader 1 has cacheex = 3


    If OSCam A gets a CW, its pushed to OSCam B. OSCam A never requests new ECMs.
    CW-flow = A ---> B


    To make a long story short, i tested all modes extensively, and found out that mode 1 is working best.



    Example of Mode1 Cache-EX(change) in two directions.
    This example creates a bi-directional transport of cache between two servers, with mode 1.


    oscam.reader on OSCAM-A:



    oscam.user on OSCAM-B:


    Code
    [account]
user = OSCAM-A-CACHE
pwd = password
group = 1
cacheex = 1
cccmaxhops = 10
cccreshare = 1


    oscam.reader on OSCAM-B:



    oscam.user on OSCAM-A:


    Code
    [account]
user = OSCAM-B-CACHE
pwd = password
group = 1
cacheex = 1
cccmaxhops = 10
cccreshare = 1



    Logging and monitoring
    You can see traffic flowing from Oscam's log.


    For example:


    When a cache-ex-request is NOT found in cache, or an invalid SID is requested:
    2012/03/12 13:51:13 1412EAF0 c OSCAM-A-CACHE (0100&00006A/51E0/64:C1C8): rejected peer (55 ms) (13 of 25) - Sport1 HD



    When a cache-ex-request IS found in cache:
    2012/03/12 13:51:07 144716B0 c OSCAM-A-CACHE (0100&00006A/17CC/64:B81C): found (32 ms) by OSCAM-B-CACHE (7 of 16) - EredivisieLive1 HD


    Also, you can check an overview of the cache thru the WEB GUI -> http://<oscamserverURL>/cacheex.html


    The efficiency of your cache can be measured with the totals displayed on the bottom of Oscam's Users page in the GUI.


    My server currently reports:


    Total Disabled Expired Active Connected Online OK NOK IGN TOUT CACHE TUN Action
    50 1 0 46 36 11 29513 0 186905 3741 24140 0


    Meaning.. almost almost 50% of all my request are flowing from cache.


    If you have any questions, don't hesitate to ask. Also, i am always searching low-latency cache friends.

  • AzBox MiniMe RTi Core v1.7.0 - 08.02

    AzBox MiniMe RTi Core v1.7.0 - 08.02



    - New Kernel from 04.02.2012 [ Added support for ppp ]


    - New smp865x.ko from 04.02.2012


    - Added Blindscan support for AZBox MiniMe


    - Fixed mp4 playback with .srt files


    - Fixed segmentation fault problem on .avi files


    - Added support for 3G USB Modems (Currently added configs for Marroco Telecom Operators) [ HDM EC122, Huawei E153, Huawei E156G, Huawei E1750 ] - Menu -> Setup -> System -> [3G Set]



    DOWNLOAD

  • AzBox Me RTi Core v1.6.0 - 29.01.2012

    AzBox Me RTi Core v1.6.0 - 29.01.2012


    - New Kernel


    - New Drivers of 25.01.2012


    What's new:


    - Added support for Blindscan for models Me and MiniMe (Menu -> Setup -> Service Searching -> Manual Scan -> Type of Scan (Blindscan) )


    - Fixed problem with IR mixing from some TV brands which are using same NEC protocol as in AZBox Me/MiniMe


    - New application example_outports & activate_outports for more stability in work with Outputs like HDMI, Component and Composite.


    - When receiver is in standby just clock will be shown without date, to prevent scrolling. (Me)


    - Better support for timeshift and recording.



    Currently we are doing transition to new kernel 3.2.1 which will have support for vTuner (DVB-T/C and DVB-S2 USB tuners), and better support for all other things and parts which was missing in old kernel 2.6.22.


    DOWNLOAD

  • BarryAllen 6.09 by GM

    6:09 BarryAllen by GM


    6:09 BarryAllen by GM


    Correct as lacking a P :-) For purists, overwrite / media / ba / locale / en / LC_MESSAGES / 2 files present. Mo /. With the archive bit (decompresso!!)
    That couple of warnings in Italiano, GM will have to add in the PY to be able to be translated, I think they are from elsewhere :-)


    LG blu8


    Ps / ON: who does not like bootlogo (me for example), replace it with that contained in 'archive barryallen.rar, overwriting the file in the folder bootlogo. MVI
    Ps / OFF: both are my two


    Grazzi blu8


    The new boot-logo


  • Edit k*y - Openbox / ***box S10

    Code
    1, open constan.cw as text file(.txt) in computer
2, edit the keycode in the file Constant.cw
3, save the file in USB
4, insert the USB into the receiver
5, go to menu "NETWORK SETUP"----CCCAM CLIENT SETUP"
6, go to the first list "update files by USB'
7, go to the third list "constant.cw(cccam plug) , then press ok
8, press the yellow key on the remote controller, the receiver will save the files

  • multics ( CSP + CCcam connector )

    Check MultiCS Execution


    Code
    sometimes multics stops running due to some unexpected incoming data or unknown bugs.
    the next tool checks multics every 60s and execute it if isnt running.
    use this tool when running only one instance of multics, it doesnt work with multiple instances.
    the source code is included to add other programs to be checked.