Posts by AGLyons

    I'm currently running an x64 v11 nightly but I've come across this since, forever.

    If my LE system crashes or needs a reboot and the home theatre receiver is not turned on, the LE system does not know what resolution to set the output. Since it does not know what resolution to set, it sets no resolution. Many times have I come to fire everything up and I am presented with a blue screen as there is no signal coming into the Onkyo receiver. It forces me to SSH in and re-boot the system when the receiver is turned on so that the display comes back up again.

    I'm hoping there might be a way that I can force the system to output a specific resolution within the LE config somewhere. I've already whitelisted resolutions in Kodi but I suspect the problem starts before Kodi gets started up.

    Hmmmmm Problems

    I managed to get the script in and I can run it. But it keeps saying there are now new nightly builds

    LEv11:~ # ./
    Connecting to (
    saving to 'releases.json'
    releases.json        100% |*********************************************************************************|     2  0:00:00 ETA
    'releases.json' saved
     No new nightly
    LEv11:~ #

    It's clear I am running an older nightly 05-02-2022.

    Using username "root".
    # LibreELEC #
    # #
    LibreELEC (community): nightly-20220502-907d2d6 (Generic.x86_64)

    The latest I can see in the list is LibreELEC-Generic.x86_64-11.0-nightly-20220723.

    Any ideas?

    EDIT - releases.json is blank. That's why there are no new releases.

    chewitt - Do you know of any reason why the releases.json is not getting updated? Has that file been abandoned or could there be a bug somewhere?

    Hey Joeaverage!

    So I made the script (thanks!). Saved it to the storage folder and chmod the file.

    I tried calling it and putty just returned "can't find the file". I tried moving that to the user folder (one level up) and couldn't do that as the file system is read-only.

    I moved the sh file to the downloads folder and tried to run it there. Again, can't find file.

    I'm not sure how to execute this.

    Also, is it normal that stopping Kodi also kills all samba shares?

    Once it's stopped I can't get to any files with my Win10 laptop.

    ok, round 3. This time it's the MB and nvme drive by itself. No AMD GPU.

    Installed todays nightly. First thing I came across is selecting option 1 at the install screen returns "Failed, no such file or directory"

    Install did complete and this time instead of adding my advancedsettings.xml, I manually added source folders. I'll have to wait till general release of v11 to use the external DB.

    All the files scraped properly and playback is working, both audio and video.

    Now, I wish there was a simple way to copy the skin settings so I don't have to rebuild the UI each time I install a new box. I use Aeon Nox:Silvo. Is there a simple approach you use?


    How far off do you think v11 is?

    I just tried today's nightly and I still can't things up and running right.

    None of the default shares are present, at least Win can't access any of them for some reason. I even went down to SMBv1.

    I managed to get a copy of my advancedsettings, mediasources, sources and passwords XML's over and it took them. I then defined the media folder contents and that's when things blew up. Reboots would freeze the Kodi splash screen for about 2 minutes before the UI would come up. None of my content showed up after that.

    I then got smart and thought I would put my GPU back in and stuff the SATA SSD with my existing 10.02 in the case. But that wouldn't boot as I totally missed that 10.02 wouldn't support the 11th gen chipset. I get the suslinux line and that's it.

    I don't think I'll be able to put this box in production till v11 is out or if someone has compiled Kodiv19 with a 5.18 Kernel.

    I'd do this myself but I haven't the first idea of how to start.

    hey @heitbaum,

    Thanks for jumping in!

    So I'm not a dev really but I do know enough to cause serious system problems lol

    If I wanted to give your build a go how would I build the USB key? I tried a nightly build a while back, LE11 X86 04-02-2022 and while it did recognize the GPU, it did not see the HDMI audio out. Perhaps that's been resolved. I haven't checked a new build yet

    So I have a couple of x86 boxes pulling data from the same Maria dB.

    I built a small replacement 1u box as my main system but discovered LE10 doesn't support the Intel chipset/GPU.

    I tried a v11 nightly and it did support the GPU but did not support HDMI audio out. I figured I would pull the Radeon GPU from the x86 box it is replacing and just run v10 for now.

    The only way I could get the GPU in the 1u case is to put the OS on an nvme drive built into the MB. But v10 can't see that drive because v10 doesn't support that chipset yet (ASRock H510M-ITX/AC LGA 1200 Intel H510).

    I'd really like to follow along with v11 dev and see how builds are coming along, get filled in on the roadmap.

    I currently have two installs running v10.02 x86 sharing the same MariaDB. I have to go with a nightly v11 to support some newer hardware. Would running one system on v11(nightly) change the DB and end up breaking the v10 system?

    How can we know if/when a new build is going to make changes to the DB that might affect other installs?

    I have come across a couple of old posts talking about Intel GPU support.

    Since I could not get v10.02 to install, I was able to install v9.26. After installing v9.26, the boot process gets stuck stating "Failed to start xorg. is your GPU supported"

    MB -ASRock H510M-ITX/AC

    CPU - Intel i3-10105

    RAM - 8GB

    I can't figure out what's going on here.

    Forgive my ignorance but how come we can install Raspi OS (Buster) on a Pi4b and install VNC server on it?

    Headless Raspberry Pi 4 Remote Desktop VNC Setup (Mac + Windows, 13 Steps) –

    Also, a step by step installing TightVNC on 64bit RASPI-OS

    How to Install VNC on Raspberry Pi OS (64 bit)
    VNC doesn't come preloaded on the 64-bit OS, but you can install an alternative.

    How are these different than how it used to be done on Libreelec?

    Interestingly, I was able to install tubed. But only from the add-ons section in settings. If I tried to install tubed from the prompt when trying to view a trailer, it always failed with a dependency error.

    Installing from the settings > add-ons menu worked fine.

    Every since libreelec 10 I am getting prompted to use tubed for trailers. I haven't been able to install it, keep getting an error.

    The dependency on version 1.0.14 could not be satisfied.

    Oddly enough not all items (movie or TV show) try to use tubed. Some use YT, some want to use Tubed. I wish I could figure a way to stop tubed from being triggered altogether.

    Anyone have any ideas?

    Sorry, I asked this in another thread.

    Does LE10 make any changes to the DB?

    I have a Maria DB feeding two installs. If I update one install and DB changes are made it'll affect the other install.