So, I guess I will wait till after the weekend. Thank you for your help.
Once https://github.com/LibreELEC/actions/actions/runs/2477868749 completes. The image should be available at https://test.libreelec.tv/11.0/
So, I guess I will wait till after the weekend. Thank you for your help.
Once https://github.com/LibreELEC/actions/actions/runs/2477868749 completes. The image should be available at https://test.libreelec.tv/11.0/
Sure, I am willing to try any suggestions. I also searched for a way to make it somehow return the board type, i.e. rpi2 in my case, but sadly I found none. The file /etc/issue seems to be the only one containing it in text.
---edit
I did not notice the quoted text (rough day today, sorry). So, if the script does check for 0 byte files, please ignore my last suggestion.
The 0 byte thing is now cleaned up. (But only after a workflow is completed. https://github.com/LibreELEC/acti…uite_focus=true
The pr that fixed this is: https://github.com/LibreELEC/actions/pull/3
You can see the cause of the issue in the build-image logs.
We are working to have a larger server for the .img.gz files. But until then - max 2 copies of each img.gz file and the cleanup is done after the workflow (not the job) completes.
Do you mean trouble accessing the shares on the Pi from a computer, or accessing SMB shares on a computer from the Pi.
I can ssh into the Pi from the PC, so I know there is no fundamental network problem. If I need to I can probably reboot the PC with Ubuntu and copy the update across from there.
\\server\updates will work (and similar). It is the “browse” share list that is not working.
This should work for you.
kodi:~ # smbclient -U libreelec \\\\localhost\\update
Password for [WORKGROUP\libreelec]:
Try "help" to get a list of possible commands.
smb: \> ls
. D 0 Sun Jun 5 09:12:40 2022
.. D 0 Sat Jun 4 13:51:18 2022
.DS_Store H 6148 Sun Nov 3 12:09:13 2019
._.DS_Store H 4096 Sun Nov 3 12:08:56 2019
51290592 blocks of size 1024. 10397088 blocks available
You will still have to use the share name directly. Browse not yet fixed.
Happy to loop in with the P2 and M1 on my desk too.
jim_p the old test webserver has disk space issues. Whilst the builds are pretty much now all 100% reliable. (Have an issue with automake in the GitHub issues) when the job to copy them up fails - that results in the 0 file. Once the new webserver is going well - we should be better. The full image build happens daily and takes ~11 hours. I usually kick off a “fix build” for the failed upload images. And you will notice that a new file usually appears.
But as chewitt says - (allegedly fun in spare time)
Only error is with libretto builds is game.libretto.fsuae on x86.
The addon builds are probably a few days behind on the server.
But would expect them to be updated more frequently in the coming weeks with improvement to the build server.
Hi walidbha - syncthing will be available again in nightlies. Build issue that was resolved this week. https://github.com/LibreELEC/LibreELEC.tv/pull/6455
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.
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 ….
The crash is occurring in python (guessing the add on) and there are a couple of warnings in the log about XML invalid from the skin.
Can you please try with the default skin. If the default skin is ok. Then you may want to check https://forum.kodi.tv/showthread.php?tid=210069 and see if there is a fix/known issue/…
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.
Hi niek - Kodi 19 uses Python3 - https://kodi.tv/article/kodi-19-python-3-goes-live/
We do recommend a clean install because of the breaking Addons between Python 2 and 3. https://libreelec.tv/2021/08/26/libreelec-matrix-10-0/
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
thanks for answering...
unfortunately i can't build it by my self (https://wiki.libreelec.tv/development-1/build-basics),
i switched to the new ubuntu 22.04 LTS and it seems there are some build dependency i can't resolve.
Try using the docker build. It covers off the dependencies.