Posts by chewitt

The later doesn't exist in our numbering scheme and the former is someone else's codebase, so not our problem.

Odroid C2 and RPi are using completely different kernels (3.14 and 4.11/4.14 depending on whether it's an 8.2 or 9.0 LE image) so that's where the difference will be.

I had a hunch there was an issue with the eMMC device as some mainline testing with the sdio/emmc drivers showed errors with modules from a specific manufacturer (which translates to different colours that have been shipped). Good to hear it's resolved though

ISTR there is something unusual about Kangaroo devices, but right now the details escape me. If you can install Ubuntu, perhaps try using an Ubuntu Live USB to manually install. Basically you need to create two partitions; one 512MB and the second for the remaining space, both ext4 and install grub as the bootloader (same as Ubuntu). Now copy the contents of the first partition of the LE installer USB to the 512MB partition and translate the contents of the extlinux.conf file to grub's format. I'm a little light on details here, but creating two partitions, copy the files, configure the bootloader is all our own installer script does.

Have a look at root's crontab to see if anything has been set. Another possibility on pi hardware is some heavy load function is done (some kind of housekeeping routine) and the CPU load causes the PSU to reset. Both are random guesses not hunches.

I'm bored of repeating myself so this thread is locked.

That location contains whatever Jenkins built the previous day (sometimes a few days, sometimes longer). If nothing built, for whatever reasons things sometimes fail to build, nothing (or nothing new) will be there.

I don't recall anyone posting about OTG support before so I'd assume (at best) it's untested.

Correct. No moonlight on LE 9.0 unless someone who uses and cares about the code takes over maintenance to navigate a sensible path through the frequent breakage we've seen with the newer OS codebase. It's not that we haven't tried.

ISTR the Amlogic version also had challenges. It really needs to be maintained by someone who uses the addon actively and is prepared to commit some time and effort (and code changes) to keeping on-top of things. Hacking things to work for personal use and making clean submissions to our repo can be a little different, but if that's an issue staff will be more than happy to walk people through the PR process.

Yes (and No). Each time we fix the moonlight addon some kind of breaking API change is pushed into the next versions of the nVidia code and other libs and it's broken again. None of the staff have the hardware to test it, so we can only go by user reports which are usually as detailed as "it worked" or (more often) "it didn't work" so in the end we've given up and marked the addon as broken. If someone with the hardware and basic dev skills would care to submit curated changes to us on a regular basis to keep it working we'd be happy to receive them. So far nobody cared enough to volunteer though.

Quote from mbonet

Most probably I'll go for a FLIRC for this setup, though.

For reliable simplicity.. nothing beats FLIRC

MusicBrainz Picard <= Logs should help you identify problem Albums, then use Picard to ensure files are correctly tagged. It took me a few months of ad-hoc sessions to back-fill proper tagging of a large audio library, but once done I can re-scrape at any time. The lesson learned is that not taking shortcuts and spending time on preparation prior to scraping delivers a consistent and repeatable result.

Pioneer AVR's have a reputation for quirks (there's a reason I guessed Pioneer or Denon). Have a go with forced EDID.

Kodi debug log would be a good starting point.

If it works when connected to the TV and doesn't work when the AVR is between them the issue points towards the AVR. It may be the case that firmware/drivers didn't understand something quirky about the AVR in the past and now attempt to handle things and do it badly. You can see that as a problem with the drivers but usually the root problem is with the AVR. Denon or Pioneer?

First suggestion is to change the HDMI cable. Second suggestion is to read of Custom EDID [LibreELEC.wiki] and see if capturing the TV edid and forcing this solves the problem.

Moderators are not always developers. Don't be rude.

Go look at the kernel config in his GItHub repo.