Where can I find info on nightlies or LE v11 dev roadmap?

AGLyons - LE11 pretty much tracks the kernel releases, usually a kernel update ~ once a month. Kernel 5.18 will be next.

The package updates are in GitHub - https://github.com/LibreELEC/LibreELEC.tv/pulls.

My development tree is https://github.com/heitbaum/LibreELEC.tv/tree/dev for which commits may/may not be planned/scheduled to go in. I update all packages, but my x86 focus is GBM - and Intel specifically. Some of the other developers run other graphics chips (and X11/vulkan)

I run a tiger lake i7 with both hdmi audio and passthru.

To get a “functioning” Gen11 cpu. At least kernel 5.12 - but realistically you will want nightly, which includes updates to the graphics subsystems - wiki here - https://wiki.libreelec.tv/hardware/intel-x86-64-generic

All the parts that you are wanting will be in the current nightly. There have been lots of updates since February. My dev tree is probably not a good place to learn building you own LE image. If you are going to build your own - start with your own fork of the main tree and then add your changes to it.

There is a known samba issue. See the GitHub, that we are working through. You can go to the shares directly. The browse is the issue.

LE11 is a ways off.

from a hardware support perspective - it sounds like nightly was working fine? <please confirm> Happy to help work through this - but this needs to be step 1, and ensure stability. We have had good success with Intel Gen11 CPUs with nightly, so will want to check this is ok in your hardware first, with your motherboard hardware.

As you indicated - something blew up, was that adding some of files back manually? (🙂 my crystal ball is broken without seeing logs….)

If you are assembling a Frankenstein software then you will need to be able to stop kodi, move the .kodi directory out of the way, start kodi, and try, try again.

Check the journalctl and kodi.log, etc ….

Glad that it is working. In the /storage all the configuration is stored. If you are trialling (trying to get to the why the addon isn’t working…) you will want to keep a “working copy of” this as you experiment. You can stop and start Kodi from the prompt using systemctl stop kodi - and systemctl start kodi. The update process to the next nightly will keep your settings in place, etc. you can always revert back to a working in your situation nightly, as long as you keep a copy of the img.gz file around.

Quote from heitbaum

as long as you keep a copy of the img.gz file around.

AGLyons I use a small script to manage that.

the script fetches a new nightly (the *.tar) and keeps a copy in ~/backup.

cleaning of ~/backup is up to your own ...

#!/bin/bash

NIGHTLY="LibreELEC-Generic.x86_64-11.0-nightly-";
SERVER_URL="https://test.libreelec.tv";

# clean in any case ~/.update/
cd ~/.update/ && rm -rf *;

# operate in /tmp and clean up before
cd /tmp/ && rm -rf releases.json*;

wget ${SERVER_URL}/releases.json;

[ -e releases.json ] && NEW_NIGHTLY=$(grep -i ${NIGHTLY} releases.json | grep tar | cut -d: -f2| sed -e 's/"//g' -e 's/ //g' -e 's/,//g');

if [ ! -z "${NEW_NIGHTLY}" ]; then

# get currently running nightly version
CURRENT_NIGHTLY=$(cat /etc/issue |grep nightly|cut -d: -f2|cut -d "(" -f1|sed -e 's/ //g');

# and compare with the one on the server
RC=$(echo ${NEW_NIGHTLY} | grep ${CURRENT_NIGHTLY});

[ ! -z "${RC}" ] && echo -e "\n lastest nightly already running \n" && exit 13;


rm -rf ${NEW_NIGHTLY};   # clean maybe old downloaded stuff before downloading the new nightly

echo -e "\n fetching ${NEW_NIGHTLY} \n\t wait ...\n";

# download new nightly to ~/.update/ and save a copy to ~/backup/
cd ~/.update/ && rm -rf *;

wget -nc ${SERVER_URL}/${NEW_NIGHTLY};

cp *.tar ~/backup/;

echo -e "\n\n reboot to install the new nightly, e.g. \n\n\t sync && sync && systemctl reboot \n";

else
echo -e "\n No new nightly \n";
fi;

exit 0;

copy the content of the "code box" into a file, and name it, let's say "get_nightly.sh".

chmod u+x get_nightly.sh to make it executable

and run it - after ssh'ed into the box with:

./get_nightly.sh

shortcomming's:

- script doesn't distinguish between new nightlies with same git tag and different date. what leads to a 2^cd download...

- my thinko's I did in the script

- warranty does not exit !

1. I ssh into my LE, ( I had a typo in comment #9, wrongly wrote ssd'ed - me old idiot -)

2. cd to the folder where the script is

3. and run the script from there with

./get_nightly.sh

note the point in front of the slash ("/") !

the script just downloads the last nightly into ~/.update (script line 32+34) and additional copies it to ~/backup (line 36) and then offers you to run the commands "sync && sync && systemctl reboot" (line 38).

it offers only !

if you don't run the offered commands nothing will happen until you reboot the box.

only during reboot the last nightly in ./update will get installed and the folder ./update will emptied from the update-installer

the scripts doesn't stop any service, e.g. smb.

hint:

on linux you could just mark/highlight the command "sync && ..." with your mouse and now do a middle-click to copy it for subseq. execution with the Enter-Key

AGLyons we are in the midst of moving to the final (updated servers)

test3 is now test as of last night.

The new server has the additional storage to hold previous nightlies.

For the moment - wget the img file into .update.

... and please read the first page of this thread:

Thread

shell script to get the lastest nightly

as a command line user I wrote a shell script to download nightlies for updates/downgrades

script supports the newer directory structure on the nightly download server and LE 11 nightlies.

What is does

- reads out /etc/os-release to get the nightly variant from your currently running LE box

- checks the download server for last (for updates) and previous (for downgrades) nightlies

where "updates" means: to the newest on the download server (in one step ! I don't know if that always work out)


where…

GDPR-7

July 19, 2022 at 6:50 PM

esp.: => requirements

and of course get the last script before

heitbaum

sorry to revive an old thread but you mentioned in your 1st post that you have HDMI audio working for 11th Gen iGPU UHD 750 in your development tree.

I have spent the last few days trying to get this up and running via an UNRAID VM see here: RE: No HDMI Audio option available for Intel UHD 750 iGPU in UNRAID VM

How do I go about acquiring an .img of your development tree for testing or have I missed something entirely? Thanks in advance!

I see you were able to get it ok on the native hardware from your response to chewitt. My dev tree is pretty much always up to date at GitHub if you are looking.

Thanks for the reply mate, much appreciated! yes everything worked fine when LE (LibreELEC-Generic.x86_64-10.95.0) was booted outside of UNRAID, I had multiple HDMI sound options in Kodi.

This suggests the problem is indeed Unraid and how the hardware is passed through to the VM.

Out of curiosity how would I implement your DEV tree into a .img like "LibreELEC-Generic.x86_64-10.95.0.img" so I could test on my end.

Also what your professional opinion as to where the root issue may be LE or Unraid? As I'm desperately running out of options with my limited knowledge on the matter.

heitbaum So I've had some good help from a Dev on Unraid forums to try to get the HDMI audio passed through, sadly though we could not get the HDMI audio option to show up within KODI.

see here: https://forums.unraid.net/topic/134700-l…for-intel-igpu/

His last comment pointed towards Libreelec's implementation of the audio device, he believes that everything is being passed through correctly and the Linux kernel is loading the audio device correctly.

As a last ditch effort i was hoping to load your dev tree, can you please point me in the right direct on how to achieve this?