Posts by milhouse

Your 4K HEVC video, was it 10-bit?

You've butchered the log in your efforts to keep your data anonymous, which makes it hard to interpret (and trust) what remains. You should enable debug logging, restart, reproduce the problem and then upload a complete and unmolested log.

Don't post logs directly to the forum, use a pastebin site and then paste the link.

Those with driver issues, post a kodi log, preferably with debug enabled. If kodi is crashing, post your crash log too.

Ah OK, thanks, that might need to be addressed in 8.0.1.

Unfortunately I don't know when ADSP will be back, but it's unlikely to be in the lifetime of LE8/Kodi 17. Hopefully the remaining issues can be resolved during the development of Kodi 18 (the release of which is another 9-12 months from now).

Quote from sakos

So the removal of the ADSP support is done on a very odd way. It much more looks like a fault than and intended removal.

ADSP removal in the Final 8.0.0 release is completely intentional as the ADSP system remains unstable and crashes systems. Its removal in Final only looks odd because you're coming to it from an alpha/beta build where you could enable ADSP.

The fact some alpha/beta testers still have these unsupported alpha/beta ADSP add-ons installed is something we can't "undo", and is why those users still see these add-ons in their 8.0.0 system. Users coming to 8.0.0 from LE7 won't know anything about ADSP, and won't be able to enable it or install any ADSP add-ons.

tl;dr: there's not much we can do about add-ons installed by users during the alpha/beta cycle and which didn't make it into the official Final release.

Quote from djhifi

Another question, once we enforce the legacy driver, all it needs to revert to the actual one is to update the LibreELEC again?

No, just revert the changes you made to force the legacy driver. Once you force the legacy driver the change will continue across upgrades.

Please don't post logs directly to the forum - use pastebin.com (or the pastebinit command in LibreELEC) and paste the link.

Lol. Don't worry, as you're not the first to have made this mistake (hence the question, are you sure it was a Pi2). As you were so certain I think we took you at face value but maybe we should be less trusting in future - I'm starting to think we'll need to get users to post a photograph of their board next time!

Glad you got it sorted. Yes, if you want to mount /storage over NFS then you're going to have to have the files within the exported share owned by root:root (as they would be if the storage were local) otherwise file permissions will break and cause you problems. The obvious consequence of this is that you then need no_root_squash on the export.

Ok, yep, that looks like the RPi2 image. Now, assuming the SD card is fine and not corrupt, then that only leaves the other two options...bad PSU, or device (RPi2) failure.

Can't see that image - can you use imgur.com instead?

This is rather unusual as the RPi image writing and boot procedure is pretty straight forward, and fairly well proven.

Provided you've chosen the correct image for the target device, the only reason for failure is hardware related - power supply, SD card, or the device itself. Since you've tried multiple SD card and multiple RPi2 can you try a different power supply (and/or USB power cable - too thin a cable causes significant voltage drop) as that's about the only component you haven't tried replacing.

There is no root= option, LibreELEC uses boot=. Other than that, simply adding ip=dhcp worked for me last time I tried this (PR621).

Remove "quiet" if you want to see what's going on. Add "debugging" otherwise it won't break on anything (yeah, I know...).

Are you using SQLite or MySQL (you see, your log would have given us all the technical details we now need to ask you).

Does it always get to the same point in the scan before running out of memory, or are new songs/albums added with each scan before again running out of memory?

How big is your music media library (number of songs)? Do you have embedded artwork or are the posters/fanart separate, and if so how big are these images (width/height)?

If you're already in contact with Dave (Blake?) then he's probably the best person to investigate this assuming it's a core Kodi issue - presumably you've hit upon a very memory inefficient code path, or some aspect of the scan - maybe tag processing - has gone bonkers.

And crashlogs won't be created when the Kodi process is killed by the out of memory (OOM) process killer.

HiassofT are you able to test my latest #0211 RPi build (based on 4.9.9 with CONFIG_REGULATOR options for Cirrus Logic) with a Zero and the Just Boom?

Right, but you've not provided any details of how it failed so we're none the wiser what the actual problem is.

How is it broken? "md5sum -t" tells md5sum to read the file in text mode, are you saying "-t" isn't supported by Arch, or that the "-t" option isn't working in Arch? Either way this sounds like an Arch issue... unless it's something else...