Posts by petediscrete

    Unusual for burning .img to SD cards or unusual among RPI distros? There are certainly many potential failure points, but the commonalities seem to infer there is *something* about the structure of RPI Kodi distros that can wreak this sort of havoc when imaging an SD card from a linux machine. I trust your word that it isn't unique to LibreELEC, although I'm no closer to actually knowing what is happening.

    If you need further convincing, something I mentioned before if you really want to get “deep down” into your SD cards. Might shed some further insight on your problem. Personally I’ve used LE images and formatted cards for other uses no problem. You might be looking in the wrong place. Card reader and card quality might be the place to check next https://medium.com/@drawn_stories…al-f0109bef63ea

    Back to work!

    the rpi2 mostly just does not boot with HDMI connected.

    powerup without HDMI connected does boot, connecting HDMI a second later boots normal operation with screen working. Maybe the power puply is to small.

    i will find out later.

    Thanks to PE!

    I’m having a similar problem on a RockPro64 (RK3399). I now have to power up the board WITHOUT hdmi connected, wait for about 6 seconds, connect the hdmi cable and the Kodi screen appears with the correct resolution. Not ideal but it’s the only way I get Nexus 11 to boot correctly. Doesn’t happen on Matrix 10.04.

    I'm trying to run the TVHeadend script so i can access the setup from my browser because I typed in the correct IP and Port after installing TVH, but it didn't load the page. (I am on the right network)

    Code
    Unable to connect
    
    Firefox can’t establish a connection to the server at 192.168.1.108:9981.
    
        The site could be temporarily unavailable or too busy. Try again in a few moments.
        If you are unable to load any pages, check your computer’s network connection.
        If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.

    When you installed the TVH server from the addons Services section in TVH did you enable it. Once enabled then go to a remote PC, open a browser and type in the Ip address of the LE machine as I mentioned above and the TVH configuration GUI will open. There is no script to run. Just a configuration Wizard that needs to be completed. Btw this is nothing to do with SSH and audio fix. Start a fresh post if you want to discuss TVH.

    PuTTY worked for me, but trying to run tvheadend fails.

    I typed tvheadend and it didn't work.

    What do you mean “run TVHeadend”. If you’ve installed both the TVH server and client on the same board and enabled both, TVH will run as a service assuming you have configured TVH from a remote terminal. You access TVHEADEND from a remote browser using the LE IP address. As an example

    192.168.0.150:9981 and configure TVH from there.

    For Windows users PuTTY is best for an SSH session into LibreELEC. Ensure you have SSH enabled in LE and use the default username root and password libreelec unless you changed the password on first time configuration.

    disconecting HDMI the rpi boots and i can conect with ssh,

    but also after boot there is no HDMI signal: the monitor is black, says "NO SIGNAL" and goes to sleep.

    How can i turn HDMI on?

    Other than trying a different HDMI cable or a different TV to see if that solves your problem you can’t. You can either revert to your previous install. Assuming you took a backup before making any changes do a fresh install of Nexus 11, remove the IR remote from the equation, restore your backup and see will your RPI boot again.

    Looks like getedid create is not an option with LE on the RockPro64 board. Amazingly both a cold start and a warm start using the Rock64Pro onboard switches and the LE Power Off followed by a switch on return a perfect boot with correct display. The only non functioning item now is the LE Reboot. That option returns a black screen.

    I’ll stick with the onboard reset until myself or someone figures this one out. Maybe someone from the Rock Chip community might have some thoughts on this if they happening to be passing through.

    Just tried a fresh install of Nexus on a RockPro64 and got a black screen. Decided to try the upgrade route instead from 10.04 to 11.0 and had much better results. Upgrade went fine BUT the black screen returns when doing system restart. If I power down the unit and start from cold LE is booting fine. I have to say this is a new one on me. I’ve ruled out the possibility of cable issues too.

    A quick mention. The Outer limits files did not work on The Core (OSMC) video box either. It's not just the Pi!!!

    I have not tested The Shipwreck files on the core.

    Also, this complaint does NOT appear for my movies, just TV files, for what that is worth.

    I have a busy schedule today. I'll do as suggested above re: the logs and check back later.

    Not as busy a schedule as the guys here have answering your query. You were asked to supply logs and possibly a snippet of the offending video. Still no sign of either. Maybe when you get around to it

    Did you try SD Formatter as I suggested above before proceeding any further. Outside of that you may have a flaky card reader. Try an alternative one if you can. https://www.sdcard.org/downloads/formatter/

    Another item worth checking is your card reader. I had a USB card reader which displayed similar symptoms. Changed the card reader and it solved the problem. The electronics in those USB card readers do fail. I wouldn’t go to any expense though. Just try an alternative reader and see if it makes any difference.

    I will say the quality of SD cards these days is a little dubious. Even supposed branded ones and particularly high capacity ones. For anyone interested there’s a neat little utility for Linux called f3. You’ll be surprised at the results it returns for so called branded high capacity cards https://medium.com/@drawn_stories…al-f0109bef63ea

    It’s amazing how many installations fail to perform as expected with either poorly unpacked image files and/or poorly written images to SD card. The frustrating part is you just don’t know and spend hours making changes to the application. The finger usually points to SD cards as a last resort. Thankfully not in this case.