Nightly builds

Development Development & Testing
2930

Dear @Portisch, I have had this black screen/no signal issue for a long time and also with 20260812 as of today and like it be to solved if possible, Claude has helped me with the logs.

Full dmesg capture during the failure shows the driver explicitly failing the mode enable, not silently skipping it:

[292.654575] HDMITX_ERROR hdmitx_common_pre_enable_mode current hpd_state/suspend (1,1), exit
[292.654579] HDMITX_ERROR Record HDMI error: KMS_SKIP
[292.657053] HDMITX_ERROR mode enable fail
[292.657055] HDMITX_ERROR Record HDMI error: KMS_ERROR
[292.657107] [drm] meson_vout_update_mode_name: hdmitx update vout 1 name 1080p60hz.
[294.856285] [hdmitx:] Late Resume

The mode enable is attempted while the driver’s suspend flag is still set, so it exits early — and Late Resume only arrives 2.2 s afterwards. The enable is never retried, so the output stays dark while vout reports 1080p60hz and hpd_state reads 1.

kodi-send --action="RestartApp" recovers it by forcing a fresh atomic enable:

[459.240905] am_meson_crtc_atomic_enable-[0]: enable mode 1080p60hz final vmode 0
[459.241372] configure hdmitx21
[459.243048] enable phy to dig
[459.243054] hdmitx_set_dispmode
[459.283672] Sink is HDMI device

I would appreciate it if you would take a look at it, thanks.

Full logs:
Failure: https://paste.coreelec.org/WoundedAudrey
Recovered: https://paste.coreelec.org/DisarrayReeve

2931

Since the update on August 10, 2026, I can no longer play videos on my Ugoos AM8pro. A spinning red circle appears, and after a while, the device crashes.

2932

With nighties they change a lot sometimes daily.

I would suggest always trying the latest to see if the Devs have covered the issues in the background.

If not go back to one that works. I keeps 2 sd cards for that reason.

2933

Situation is unchanged. Today’s update (13.8.26) also has the same problem: 2160p files are no longer playing on AM8pro.

Back to CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20260807.tar and it’s working perfectly again.

2934

Are you using NFS mounts by chance? I’ve seen some people having issues with the latest libnfs bump that came through causing issues with playback of certain files.

2935

Yes, im using NFS sharing on a NAS

2936

This is the current workaround I’ve seen work for others: https://kodi.wiki/view/Path_substitution

You can use path substitution to map to local mounts and avoid the issue.

2937

that doesn’t sidestep the libnfs issue

use the systemd auto mount to mount it to the file system so the kernel handles it natively then Kodi is out of the loop

(already confirmed to fix 1 instance)

2938

I am using NFS with a mariadb library and latest nightly have rendered both my SK4 and AM9 Pro useless.

With latest nightly my S6 boxes are unable to play any media. Getting this error before crashing when trying to play media: CBitstreamConverter::Convert: error converting

They also crash when idle and doing nothing after a fixed duration.

Had to go back to nightly from 9th of August which I know works. Do you know if developer of libnfs is aware of these issues, of if they are being fixed?

2939

Before posting an error:

if you want to track back to upstream
immediate - Issues · xbmc/xbmc · GitHub
parent - Issues · sahlberg/libnfs · GitHub

where this issue may only present in downstream (core/libre elec) it poses a problem trying to find an upstream issue when upstream issue trackers won’t handle downstream tickets

2940

Yes my homatics also crashed as well.
The issue ist the NFS sharing.
I added my shared folders again, seems listed the movies, but than nothing played

The CE has in idle, growing memory usage up to 90%, then crash.

I made several clean install, but just helped when I set smb share to my nas.

2941

CoreELEC NFS workaround without rebuilding the Kodi library

Tested successfully on Homatics Box R 4K Plus (CoreELEC).

This workaround mounts the Synology NFS share at the Linux/CoreELEC level instead of using Kodi’s direct nfs:// access.

NAS share:

192.168.2.2:/volume2/KODI

Local mount point:

/storage/mnt/KODI

1. Create the permanent NFS mount over SSH

Run this single SSH command. Remember to adjust the NAS IP address and share path to match your own configuration.

mkdir -p /storage/.config/system.d /storage/mnt/KODI; printf '[Unit]\nDescription=Synology KODI NFS\nRequires=network-online.service\nAfter=network-online.service\nBefore=kodi.service\n\n[Mount]\nWhat=192.168.2.2:/volume2/KODI\nWhere=/storage/mnt/KODI\nType=nfs\nOptions=vers=3,rsize=131072,wsize=131072\n\n[Install]\nWantedBy=multi-user.target\n' > /storage/.config/system.d/storage-mnt-KODI.mount; systemctl daemon-reload; systemctl enable --now storage-mnt-KODI.mount

Check that it is mounted:

systemctl status storage-mnt-KODI.mount --no-pager

It should show:

Active: active (mounted)

The share is now available as:

/storage/mnt/KODI

2. Keep the existing Kodi library without rescanning

If the existing Kodi library already uses paths such as:

nfs://192.168.2.2/volume2/KODI/Filmy/...

do not delete or rescan the library.

Edit:

/storage/.kodi/userdata/advancedsettings.xml

Example complete configuration:

<advancedsettings>

<seeksteps>10, 20, 30, 45, 50, 60, 120, 240</seeksteps>

<pathsubstitution>
    <substitute>
        <from>nfs://192.168.2.2/volume2/KODI/</from>
        <to>/storage/mnt/KODI/</to>
    </substitute>
</pathsubstitution>

</advancedsettings>

Restart Kodi:

systemctl restart kodi

Kodi will keep the existing library and database, but when it opens a file stored under the old nfs://192.168.2.2/volume2/KODI/ path, it will use the local system mount /storage/mnt/KODI/ instead.

No library rescan is required.

For a completely fresh CoreELEC installation

Create the system mount first, then add Kodi sources using local paths such as:

/storage/mnt/KODI/Filmy

/storage/mnt/KODI/TV_Serialy

/storage/mnt/KODI/Dokumenty

In that case, pathsubstitution is not needed because the Kodi library is created with the correct local mount paths from the beginning.

2942

Confirmed, switching to systemd mount fixed the issue on my Homatics box.
Thank you!

2943

I guess it was either this commit to LE that did it?

or this one:

2944

I don’t know.
Currently, I needed drop all the NFS connection, like I said. Now I have just smb to my synology,
under CE 22 ..

2945

Yeah, it’s not really an option for me as I have a central mariadb database to all my devices and which is based on NFS shares from my servers. I don’t really want to change to SMB, not only because of the work involved, but mainly because I feel SMB is so slow - which is why I use NFS in the first place.

I might try majsoft’s path substitution workaround but I hope it gets fixed soon as surely this must affect a lot of people.

2946

Luckily all my main CE and kodi installation is Kodi21 and CE 21.
There is no problem with my MariadB and NFS sharing.

Testing pendives for CE 22 not use MariadB, just NFS share with local db.

2947

I think the NFS issue is only with NFSv4 server. V3 works at least here.

Update: With NFSv3 I meant client in Kodi under Settings/Services or something like that.

2948

No.
It’s broken with the v3 as well.

2949

I just try setup CE nfs server, selected v3 version, add source to kodi using browse fuction, and I could play a file over nfs.
Didn’t use library because it was long time I used this function and don’t remember how to setup.