Posts by chewitt

All I did was enable SMB (as normally I have it disabled) and either clicking on the now-visible device in Finder>Network or doing the command+k to give an explicit address using <name> (not <name>.local) worked fine.

NB: The default SMB password is libreelec/libreelec not root/libreelec

Just do "command + k" in Finder and provide the smb://NAME/SHARE you want to access, or at least smb://NAME and it will then prompt for credentials and list the available shares.

Changes are merged and should appear in nightlies in the next 24h. You will need to manually update to a fixed nightly before the update process will start working again.

This change should fix the update process in nightlies https://github.com/LibreELEC/serv…ttings/pull/330

There is no need to chainload u-boot as Armbian does. Just use the AMGLX "box" image which includes s905_autoscript and boot.scr on the SD card and vendor u-boot will read one of them and reconfigure the boot environment to look for LE boot files first (and if not found, fall back to default boot into OSMC). It will be the same for Vero 4K and 4K+ boxes (and pretty much anything else with vendor u-boot on internal storage).

I'd suggest you submit the idea to the Raspberry Pi kernel developers via their GitHub repo as this is not something that will be developed by LE staff.

Please provide the URL's from:

lspci -vnn | paste

lsmod | sort | paste

Enabling deep colour changes HDMI properties advertised by the TV on the HDMI port to include 12-bit 4:2:2 and I'd guess that the display chain cannot handle the additional bandwidth required for 4K60 and thus sync is lost. Disabling deep colour forces 8/10-bit 4:2:0 output and allows things to work. The most common issue with 4K60 video is the HDMI cable not being able to sustain higher bandwidths required (esp. when combined with HD audio). Do you have 4K60 certified cables?

There is very little real-world media in 4K60 format (most is under 4K30) and almost nothing in 12-bit (only 10-bit) so if the cable is not the issue, disabling deep colour on the TV or leaving the video= change in syslinux.cfg and never using 4k50/59.94/60 modes (where the issue will probably reappear) are both options. The video= change only forces the initial connector state to 1080@60, it does not prevent Kodi from detecting and using 4K modes with the whitelist later.

Quote from ziggy815

Even did a last try with Manjaro and latest Kernel, also no chance to get any audio over hdmi at the desktop

That proves it's not an LE specific issue.

Quote from ziggy815

alsamixer sees 4 spdif outputs and nothing more on the hdmi "card".

See if adding /storage/.config/modprobe.d/blacklist.conf with the following content does anything?

blacklist snd_hda_codec_realtek
blacklist snd_hda_codec_sigmatel
blacklist snd_hda_codec_cirrus

There is/was a Kodi Backup add-on in the Kodi repo. I've never used it, but it might be worth looking into. It probably backs-up only to a "local" filesystem path, so to save off-box you'll need to configure a persistent SMB mount (there are instructions in the wiki) so there's a local filesystem path under /var/media/ to the remote NAS share.

The backup function in the LE settings add-on also captures /storage/.kodi, /storage/.cache, /storage/.config to a tarball which is saved to /storage/backups. Unless you are locally storing media on the SD card which needs to be preserved those are probably the only folders which need to be backed-up. It doesn't handle movement of the file off-box though.

The BT device list shows device-type icons so game controllers normally stand out from the noise of phones/laptops/etc. and there's probably only a single game controller in the list.

It's arguably a workaround/hack for the underlying issue of most ARM SoC hardware lacking the capability to tonemap (or if the hardware can do it, the kernel drivers don't exist) .. but you can submit a feature request to Kodi devs via the forums (or find the thread that's probably already there). It's not something that LE can solve; the issue is upstream from us.

video=HDMI-A-1:1920x1080M@60

If the box is connected to the HDMI-A-1 connector append this ^ to boot params in syslinux.cfg and see if forcing the initial DRM output to 1080@60 helps. Adjust as needed for whichever connector is connected. You want to run the GUI at 1080p anyway (see: https://wiki.libreelec.tv/configuration/4k-hdr).

The moral of the story is: if you really need AV1 support, get something that really supports AV1.

Start with tracking down BIOS and LSPCON firmware updates for the board and installing them (most will require Windows to run them from). If that doesn't fix anything I'm out of ideas as modern consumer Intel hardware is a mystery to me. It might need some kernel driver quirk applying; there are many to choose from in kernel drivers but I have no clue how you divine things.

I've replied in your other thread. Don't cross post the same thing please.

LE is an "embedded" style distro so it's not possible to change the Kodi version in an image as kodi.bin lives inside the read-only SYSTEM file which is uncompressed into a virtual filesystem (in RAM) on boot. Even if you could replace it, the file you're looking to download and use is a) an old version of Kodi, b) compiled for Debian so almost certainly wouldn't run on LE anyway.

https://wiki.libreelec.tv/development/build-basics (and adjacent wiki pages) contains instructions on how to self-build your own LE image. Start with building a default image. Then add the diff patch with Kodi changes to packages/mediacentre/kodi/patches and then rebuild the image; it will detect the patch and rebuild only the Kodi package. You can also add udev rules files to packages/mediacentre/kodi/udev.d and they will be included in the SYSTEM file or you can add them manually to /storage/.config/udev.rules.d sometime later.

NB: The "how to build an LE image" instructions that leecher1337 provides in the last post to that thread are not correct in a couple of places. I'd guess written by ChatGPT and not from actual experience.

Quote from imhotep

The Nightly works perfectly!

I disagree with that

but at least the audio and BT bugs are resolved, and the enthusiasm is appreciated..