Posts by chewitt

Quote from ludelafo

Would you be interested?

You have mail

#################################################################
# Installing syslinux to /tmp/installer/part1
#################################################################

/dev/nvme0n1p1: unsupported sectors size

(as before) the installer fails to install syslinux to the NVME drive and no bootloader = no boot.

If you have a standard non-fancy drive around you can see if that works (to isolate the issue to NVME vs SATA) but it's likely due to some oddity with NVME drive firmware. I'm unsure what the solution/workaround is with syslinux so install grub to the (otherwise fine) nvme drive instead of syslinux and see what happens.

Google reports there are 387,000 results for "install grub bootloader" so plenty of things to read.

The add-on base version is bumped occasionally during development; meaning over time there are multiple versions of the add-on repo and a specific LE nightly will pull add-ons only from it's hard-coded version-matched repo. We aim to keep current and one-previous nightly repo version around (although only the current one will receive updates) and we delete older repos to save disk space over time which means old nightlies will often have no add-ons available. It's not clear from your explanation whether this is an LE11 or LE12 nightly, but I'd guess LE12 and that's likely the problem. Unless you want to build your own add-ons, the sole solution is to update to a current release (with current repo).

NB: while it will boot, Zero 2W is no longer supported due to being 512MB RAM size. I'm also not aware of any issues with Samsung SD cards over 32GB, and anything with major boot impact like that would normally be a high priority firmware or kernel issue for the Pi developers to resolve.

Create an Ubuntu Live USB and see if that boots. If it does, grub works (where syslinux does not) and you can do a manual LE install to the NVME drive using grub as the bootloader. Create a GPT partition scheme on the drive with two partitions: BOOT (512MB/VFAT) and STORAGE (100% remaining space/EXT4) and setup the grub boot entry using the data in syslinux.cfg as a general guide for boot params.

Nope

jernej any ideas on the root cause here?

It's not possible to fully answer the Q without a Kodi debug log to look at, but I'd guess this is an interlaced resolution and since Kodi only outputs progressive, it (and other interlaced modes) is/are automatically excluded from the output options.

I've never seen/owned/booted a Chromebox so can't really advise. There's fairly extensive instructions on the mrchromebox site.

Share the install log from the installer USB?

I need a UART log to see what is (or isn't) happening when the board boots.

I think you're over-thinking what's involved. Just configure a different HDMI output to the one being used for video.

Capturing and setting persistent EDID data will prevent LE from seeing disconnect/connect events on the HDMI connection. This might help the AVR not loose sync, or it might not (my gut feel is it won't).

There's nothing to prevent you from using one HDMI port for video and one for audio. Just configure it.

Disable CEC in Kodi drivers if not needed, then the toaster message doesn't show. Read the wiki section on calibration. No need to touch buffering settings. And Kodi Omega has a splash image that's designed to look glitchy. Not the greatest design idea. If AMLGX works for you, that's nice. If it doesn't,

I'd guess the SD card is a newer/faster one and doesn't get reset properly after the initial boot and thus can't be read-from. If you find an old/slow SD card without fancy fast modes it will probably work. Using the USB adaptor sidesteps such issues.

NB: AMLGX is not perfect. If you want to nit-pick on what works/doesn't, you can save fingers from typing forum reports about this/that test file because a) I know there are bugs, b) I know nobody is working to fix them. I'd like to see improvements of course, but until there are some, the reports aren't interesting. Best results come with using the mode whitelist and adjust-refresh. Using "sync playback to display" will probably cause more issues that it might solve. If it works for you, that's nice. If it doesn't,

I mostly use our USB/SD Creator app; albeit a currently-unreleased macOS version. And most of the time I'm using self-built images that are a little ahead of our master branch. Etcher/Rufus/Win32DiskImager should all work though, there is nothing special about our app or the .img file we build.

See if the image here works? https://chewitt.libreelec.tv/testing/

If you want to run things like teleconferencing apps on-screen side-by-side with Kodi you need a desktop or app environment where such apps exist, e.g. Ubuntu/Fedora or (don't laugh) Android or Windows. LE is not what you're looking for; unless it's being run in a virtual environment (with GPU mapped to the VM) to handle media-client activities under one of the dedicated NAS distros that allow such things.

As a general rule Linux already "does the right thing" by down-clocking CPU/GPU etc. when not active. There isn't really anything specific that you can configure or do to achieve more.