Posts by abu baniaz

    He is using a Dreambox Two. It has a separate "data" partition which openATV does not see/recognise. That whole partition is unused by OpenATV. Details below from my DM900. The whole 2.5GB partition is not used by OpenATV apart for multiboot.


    So instead of suggesting/implying "picons are in a folder called /data/picon", he should really have just said, "I have created a picon folder on the data partition".


    dm900 atv devices.png


    You are suggesting that creating a folder called "data" on the internal flash memory (where the image is flashed) which then has a sub-folder for picons survives an image flash? How is it possible for the bootloader to ignore overwriting that part of the internal flash memory and flash around it?


    Otherwise, you are using a different receiver which has a separate partition. OpenATV does not see that as user space, so ignore it. If this is the case, the issue is not picon location, it's recognising the partition as usable.

    There is no function in ATV to select a picon folder. Some other plugins also search and use the location so I doubt they will change it. But you never know. Until they change it, put them in a permitted location. They are determined in this file:

    Code
    https://github.com/openatv/enigma2/blob/master/lib/python/Components/Renderer/Picon.py

    I have the picons folder in /data/picon, but I can't get them to appear in the infobar or channel list. Is there a way to choose the path for the picons, so I don't have to copy them to the default folder?

    I dont think that location is allowed/searched. A "picon" folder on the root (i.e not in a sub-folder) of a mounted device/location should be fine. You are using a sub-folder. Ask on the openatv thread to double check. It may also be worthwhile you saying which skin you are using as some have their own renderers and require a different location.


    The only way to have them in a location that is not searched is by creating symlinks to it. You will have to modify the one provided for you in post 7. However, if these are on the internal flash memory, just rename it.

    What's a BMX?

    BMX = BouquetMakerXtreme. Thread is on link below.


    The receiver only has 64MB of internal flash memory.


    Image in post 1 is 76MB, so it won't fit on the internal memory of the receiver. It has to be run on external memory. This is why the note says: "multiboot only"


    The image to install on the internal memory of the receiver (primary image) are posted in post 2. There are two images in post 2. One is for a genuine receiver, the other is for a clone.

    Sorry, I dont understand your response.


    You asked if there was a repo with a patchcd oscam.

    I pointed it out to you

    Now you say you have a finished patched version


    So, why did you ask the question if you have a patched version already?

    Is there anything wrong with the repo with the patched version that I pointed out to you?

    UK Freeview EPG:

    There are no entries in Rytec database for UK terrestrial channels. EPG importer therefore does not import EPG for UK Terrestrial channels. It is going to be difficult because from my experience, all the different regions all have the same service references. Either use EPG refresh and add a terrestrial channel for it to zap to or create your own xml file for EPG importer to use.


    I am a bit confused about what you are saying in your second issue. Are you using that the localised ABM provide file that ABM Terrestrial Finder creates is not restored? The whole of /etc/enigma2 directory and contents should be backed up then restored on ATV . The ABM customised folder is within /etc/enigma2/ I have asked one of the ATV developers to double check.


    The whole reason for using frequency finder in ABM is because the official ABM Terrestrial provider file does not have the all the details. You have to select that provider file while the details are missing in the official provider file. It will be better to add the missing data to the official provider so that all your channels are found when you select Darvel with the stock . Please upload your lamedb file and also the provider file that ABM frequency finder creates. The example file you uploaded is just a list of channels, it is of no use.


    Alternatively, do not use ABM for Terrestrial, use the Terrestrial scan plugin.

    There are 5 versions:


    OE-A version- available to receivers using any OE-A image. (ATV, VIX, OBH, HDF etc.) Code is opensource and people can contribute to it. This is installable from the plugin server.

    OpenPLi version- available to receivers using official PLI. Code is opensource and people can contribute to it. This is installable from the plugin server.


    Lullua/Belfagor's version. He can better describe what his beginning source is and what improvements he has made. See his thread.

    Dorik 1972's version. He can better describe what his beginning source is and what improvements he has made. See his thread.

    IET's version. He can better describe what his beginning source is and what improvements he has made. See his thread.


    I would recommend that you install the one from the plugin server. Report any issues you experience to your image team and they will look to fix it.

    Please do not mix up EPG Importer issues with EPG source data issues. They are two different things.

    Thanks. While in active ATV image, I transferred the file uploaded by hannibal_lecter. I then flashed it with the command you gave. It is still 103 after reboot.


    The wget command did not like the https in the address


    Code
    root@dm900:~# wget https://dreamboxupdate.com/opendreambox/2.5/stable/images/dm900/zImage-rescue-3.14-r0-dm900-20200715.bin
    Connecting to dreamboxupdate.com (178.63.252.154:443)
    wget: server returned error: HTTP/1.1 400 Bad Request


    I thought I got it done by these commands while in recovery mode. It still says it is 103


    I have tried this


    1. Copy this .bin to /tmp
    2. Open telnet and login
    3. flash-rescue /tmp/*.bin
    4. Wait 3-5 minutes. Wait for DONE info!
    5. Power OFF to 10 sec and power ON.
    6. Done. You have new rescue loader.




    I fail at stage 1, it won't allow FTP while in recovery. Do I need to be booted into an operating image instead of recovery?