Posts by chewitt

Disable sync playback to display. This forces Kodi to use the media for clocking. It's normally more stable.

for i in $(git rev-list --ancestry-path 353213e..968e285); do git show $i; done

That ^ diffed the commits between the good/bad change and I don't see anything major in the list, but there are a load of u-boot and boot config changes. I know the bulk of them are good and really the single difference between N2 and other boards is the use of FDTDIR instead of normal FDT in extlinux.conf. So on a hunch, if you remove the trailing / from the FDTDIR line so it reads "FDTDIR /amlogic" not "FDTDIR /amlogic/" does it boot properly now?

Not seen anything like it. Have you followed the general setup recommendations in https://wiki.libreelec.tv/configuration/4k-hdr ?

Probably best to ask in the add-on support thread in the Kodi forums (where the add-on developer usually hangs-out).

Feb 28 03:26:06.168165 LibreELEC kernel: dvb-usb: found a 'Sony PlayTV' in cold state, will try to load a firmware
Feb 28 03:26:06.221403 LibreELEC kernel: dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
Feb 28 03:26:06.854691 LibreELEC kernel: dvb-usb: found a 'Sony PlayTV' in warm state.
Feb 28 03:26:06.854918 LibreELEC kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Feb 28 03:26:06.858193 LibreELEC kernel: dvbdev: DVB: registering new adapter (Sony PlayTV)
Feb 28 03:26:06.859088 LibreELEC kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
Feb 28 03:26:07.192154 LibreELEC kernel: dvbdev: dvb_create_media_entity: media entity 'DiBcom 7000PC' registered.
Feb 28 03:26:07.240171 LibreELEC tvheadend[436]: linuxdvb: adapter added /dev/dvb/adapter0
Feb 28 03:26:07.477923 LibreELEC kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Feb 28 03:26:07.481703 LibreELEC kernel: dvbdev: DVB: registering new adapter (Sony PlayTV)
Feb 28 03:26:07.484807 LibreELEC kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
Feb 28 03:26:07.648585 LibreELEC kernel: dvbdev: dvb_create_media_entity: media entity 'DiBcom 7000PC' registered.
Feb 28 03:26:07.696182 LibreELEC tvheadend[436]: linuxdvb: adapter added /dev/dvb/adapter1
Feb 28 03:26:07.925450 LibreELEC kernel: dvb-usb: schedule remote query interval to 50 msecs.
Feb 28 03:26:07.925475 LibreELEC kernel: dvb-usb: Sony PlayTV successfully initialized and connected.
Feb 28 03:26:07.925502 LibreELEC kernel: usbcore: registered new interface driver dvb_usb_dib0700

It seems to be working ^

Feb 27 17:26:09.585022 LibreELEC udevil[447]: mount: /var/media/MadMax: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
Feb 27 17:26:09.585022 LibreELEC udevil[447]:        dmesg(1) may have more information after failed mount system call.
Feb 27 17:26:09.585809 LibreELEC kernel: ntfs3: sda1: failed to replay log file. Can't mount rw!

The NTFS filesystem on the drive has issues so the kernel refuses to mount the drive. You'll need to fix the issue with chkdsk.exe from a Windows PC as there are no Linux utilities for doing that.

Have you tested a current LE13 nightly?

If you want more precise scheduling (after something, but before Kodi starts) you can use a systemd service to run commands. Have a look at the wireguard sample service in /storage/.config/system.d for a rough template.

Read: https://wiki.libreelec.tv/development/build-basics and https://wiki.libreelec.tv/development/git-tutorial

Once you create the image with the required changes you just copy the image file to /storage/.update and update, no need to wipe everything and start over.

You need to rebuild (or build) an image with that module enabled in config then.

Quote from lucian

just needs dtparam=audio=on in /flash/config.txt as prior Rpi experience taught me, but that solved nothing,

It's not an RPi, so copying the RPi config.txt file (an RPi only thing) does indeed acheive nothing.

The fix patch is merged to LE13 and L12 branches so will show up in official nightlies from tomorrow (allegedly).

What happens if you install LE 11.0.6 and then manually update to the LE12 nightly?

https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10199 <= no updates other my nagging, but we'll keep doing that

Have you enabled the firewall in LE settings?

mount -o remount,rw /flash
cp /flash/cmdline.txt /flash/cmdline.original
nano /flash/cmdline.txt

Make /flash writeable then edit cmdline.txt ^ to use "boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2" and it will read boot instructions from the NVME drive but will then boot the KERNEL and userspace SYSTEM from SD card; which means the partitions on the NVME drive are not actively in use and can be unmounted to run commands against. Remember to copy cmdline.orginal to cmdline.txt before shutting down to remove the SD card else it will attempt to boot from the SD device which is no longer connected.

If you're using a Windows PC it may have been converted to Windows line endings. If it happens again the file(s) can be fixed with the "dos2unix" command.