Initial release of the satip-axe firmware is available (Minisatip for Digibit R1,DSI 400, IDL400s)

    Hi,


    I do not believe so as all work was specific to dvb-s up to now, and nobody knows what firmware they deliver with the new box.


    CU
    9000h

    Es ist eagl in wlehcer Reiehnfogle die Bchustebaen in Woeretrn vokrmomen. Huapstache der estre und leztte Bchustbae sitmmen.

    Hi perexg,


    I have a problem compiling the kernel. I have compiled the kernel without errors and injected it my own initrd, which is basically the original Image with my changes. The uImage.gz resulting boots well until it wants to use the DVB-devices, then there is a kernel oops. Same Image with original Kernel boots and works well. I have no idea where the problem could be, since you compile and use your own kernel, too. Maybe you have an idea by looking into the dmesg:



    Thanks


    Tim


    Check the uboot parameters. https://github.com/perexg/sati…ster/patches/uboot.script


    The parameter 'bigphysarea=20000' is required for the kernel - it seems that the original firmware has this parameter somewhat build-in.

    Hi,


    Zitat von perex

    The parameter 'bigphysarea=20000' is required for the kernel - it seems that the original firmware has this parameter somewhat build-in.


    btw: You could set in ".config":


    Code
    CONFIG_CMDLINE_EXTEND=y
CONFIG_CMDLINE="console=ttyAS0,115200 bigphysarea=20000"


    Maybe this is easier, than passing the parameters via modification of uboot parameters? That's at least how the original kernel was configured.


    Best & Thanks again

    Zitat von tehlers

    Maybe this is easier, than passing the parameters via modification of uboot parameters? That's at least how the original kernel was configured.


    Yes, sure. I was lazy to look for this option. Added to my repo - commit 26f0dff40a7e9567994d4c06bc46aee4e072cbd0 .

    Hi,


    I'm runing your Firmware since 3 Days and its very stable compared to the Stock Firmware, many thanks for that.
    One Question, is it possible to get the State of the Tuner LEDs from the shell ?

    1. Server Zotac D2700-ITS Cine-S2 Dual yaVDR 0.5
    2. Client Zotac D2550-ITS yaVDR 0.5
    Sonstige VDRs
    2. Zotac-HD-ID11 TT-S2-3600 yaVDR 0.5
    3. Zotac D2700-ITS TT-S2-3600 yaVDR 0.5
    4. Zotac ITX-F-E TT-S2-3600 yaVDR 0.5

    Zitat von hummel99

    Hi,


    I'm runing your Firmware since 3 Days and its very stable compared to the Stock Firmware, many thanks for that.
    One Question, is it possible to get the State of the Tuner LEDs from the shell ?


    No, it's not possible. The LEDs are controlled using a special char device /dev/axe/fp-0 . I don't think that this information can be read back.


    But it's easy to write the "tuner busy" information from minisatip to a file or maybe, the http protocol can be used to serve this information.

    Ok, thanks, can you give me a hint how to get the Information which tuners are busy from minisatip ? I found nothing in the readme

    1. Server Zotac D2700-ITS Cine-S2 Dual yaVDR 0.5
    2. Client Zotac D2550-ITS yaVDR 0.5
    Sonstige VDRs
    2. Zotac-HD-ID11 TT-S2-3600 yaVDR 0.5
    3. Zotac D2700-ITS TT-S2-3600 yaVDR 0.5
    4. Zotac ITX-F-E TT-S2-3600 yaVDR 0.5

    hummel99:
    In fact I was thinking about the same problem - over time it is pretty annoying to run every five minutes to the server cabinet just to find out about the currrent device status.
    In normal daily use this is probably no issue but in case of intense testing it is an advantage to know the state of the satip-server.


    I use now this little shell command to create a simple html-file below /media:

    Code
    more /proc/driver/axedmx-ts |grep datainCnt | sed 's/%/%p/g;s/@/%a/g' | tr '\n' @ | sed 's/@/<br>/g;s/%a/@/g;s/%p/%/g'  >/media/status.htm


    You can access that via your webbrowser with

    Code
    http://minisatip/status.htm


    and it delivers this:

    Code
    + DEMUX_0> datainCnt:16725876 rdbytes:536254468
     + DEMUX_1> datainCnt:18906553 rdbytes:3406155684
     + DEMUX_2> datainCnt:0 rdbytes:0
     + DEMUX_3> datainCnt:0 rdbytes:0


    In my example two tuners are used.


    Regards
    Mister.Spliss

    Hi,


    is the reboot command problem solved?


    Zitat

    - reboot command cannot be used (uboot usb init fails, hw init fails)

    About the tuner status:


    we could use cgi :)


    create a cgi-bin directory:


    Code
    mkdir /media/cgi-bin


    create the status script:


    Code
    vi /media/cgi-bin/status


    give it right at least 700:


    Code
    chmod 700 /media/cgi.bin/status


    contents of the status file under cgi-bin:


    Bash
    #!/bin/bash


echo "Content-type: text/html"
echo ""
echo "<meta http-equiv="refresh" content="5" />"
echo "<html><head><title> SatIP Tuner Status</title></head><body>"
echo "$(more /proc/driver/axedmx-ts | grep datainCnt | sed 's/%/%p/g;s/@/%a/g' | tr '\n' @ | sed 's/@/<br>/g;s/%a/@/g;s/%p/%/g' | sed s/"+ DEMUX_"//g | sed s/"> datainCnt"//g | sed s/" rdbytes"//g)"
echo "</body></html>"


    This will show the usage of the tuners and will refresh the page every 5 seconds, you can edit this value



    with the index.html under /media i did the following:


    Code
    <meta http-equiv="refresh" content="0; URL=http://BOXIP/cgi-bin/status">


    that will redirect directly to the status script.


    now everytime you open the website the status will be generated on demand and automatically by refresh


    [Blockierte Grafik: http://i.imgur.com/Ppzfuw6.png]



    [Blockierte Grafik: http://i.imgur.com/oWycPG2.png]



    Regards X23

    Hi,


    perex can you compile (integrate) vdr or tvh into you image?


    Also as you can see at my tuner status screenshot above (new one) it seems that a tuner can be lost.
    tuner 1 is missing there:


    [Blockierte Grafik: http://i.imgur.com/Dwv2I1I.png]


    Is there a way to activate it again, and why is it maybe lost?


    Edit:


    it appeared again:
    [Blockierte Grafik: http://i.imgur.com/Ppzfuw6.png]


    Edit:


    Still working on a status page :):


    [Blockierte Grafik: http://i.imgur.com/T4vkt2A.png]




    Regards X23

    Zitat von arel

    Hat jemand hier auch schon mal die axe Firmware auf den unterstützten satip-servern (gssbox usw.) getestet ?

    Ich habe auch eine gssbox leider bekomme ich die box mit der axe Fw nicht zum laufen
    die box bootet immer mit der originalen Fw
    ich habe schon mehrer sticks ausprobiert

    Zitat von x23piracy

    perex can you compile (integrate) vdr or tvh into you image?


    Hi X23,
    I think the CPU has by far not enough resources to run vdr or anythink like that. And for what? As recording server you need a fast hard disk interface (the box has only USB) and any other services (streamdev etc) need a client vdr anyway. So why not use satip-plugin or vtuner/satip? I am happy with the box as it is now, even with the original firmware. I will give the satip-axe alternative firmware a try and see if some of my issues goes away. Although I expect them to be on the client side, but who knows...


    Darkstar.

    Hardware: Seagate Dockstar@1500MHz, GSS Box DSI 400 SAT>IP Server, VDR 2.1.6 mit Streamdev-Server
    Videoausgabe: RaspberryPi mit MLD-4.0.1-RPi an LG 42LM660

    Zitat von reepi

    Ich habe auch eine gssbox leider bekomme ich die box mit der axe Fw nicht zum laufen
    die box bootet immer mit der originalen Fw
    ich habe schon mehrer sticks ausprobiert


    Hast du den USB Stick in den oberen USB Steckplatz gesteckt? Nur da bootet er die Firmware vom Stick.... ;)

    Zitat von Uwe


    Hast du den USB Stick in den oberen USB Steckplatz gesteckt? Nur da bootet er die Firmware vom Stick.... ;)

    ja ich habe immer den oberen Steckplatz genommen geht leider nicht
    jetzt habe ich mal die originale Fw genommen geht auch nicht

    Hi reepi,


    Welche Firmware Version hat hat deine Box?


    Bei mir startete der USB-Stick auch erst als die Box die Orginal Firmware 1.17.0.120 hatte.


    https://github.com/perexg/sati…ware/idl4k.bin-1.17.0.120



    Gruß vdrdream

    OctupusNet SATIP Server => VDR-SERVER : i3-4150, 4GB, NVidia GT640 passiv, yaVDR 0.6.1, X10 FB

    Clients : Windows-PC's mit VDR-Zapper, Android-Handys und FireTV mit VDR-Manager (MX-Player) am Smarttvweb Plugin, iPad per Goodplayer am Streamdev-Server Plugin
    in Rente:
    Server/lokaler VDR : AT5IONT-I, 4GB, 2.5" 500GB HD, yavdr 0.5.0a, Mystique SaTiX-S2 V2 CI Dual,TT USB-3600,August DVB-T210 V2.0, Pollin Cyberlink IR Empf.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden