Posts by chewitt

I never used them, but ISTR Kodi repo has some add-ons for adding bonus feature support into screens/menus.

Netflix requires crypto support that is only available in Kodi v18, so you need to use an LE 9.0 development build not LE 8.2.4 (Kodi v17).

Unless you have disabled auto-update, all official LE release will (by default) auto-update from 8.2.3 to 8.24 (to 8.2.5, etc.). You can manually update using the LE settings add-on.

Quote from pepeq

is the following criteria met by OSMC on RPi3: - play 4k HDR material

Raspberry Pi is amazing for a $35 device, but 4k is way beyond it's capabilities.

Thread closed because this topic is not open for debate.

There is consensus among team and community developers to stop supporting the installtointernal script. Installation on eMMC/NAND provides a marginal performance gain on most boxes, but adds significant complexity to the installation process and the number of installs that go wrong and need significant hand-holding to correct is proportionally high (much too high).

Creating releases is fun. Finding bugs and resolving them can be rewarding. Supporting users with the same installtointernal issues over and over and over makes you hate life, Android boxes, and users. The script is gone. The script is not going to return (the risk is our sanity, not your box).

Sending the WOL packet has no dependency on hardware (only receiving it does) so it should work on all devices.

From the Kodi repo?

Enable the Samba server in LE settings.

Not possible in LE because software RAID tools that would allow you to create a virtual volume that spans multiple drives are deliberately absent from the OS (because we don't want the hassles of supporting users who don't understand them).

I'm not sure why Samba wouldn't work, but SFTP works with no issue. Make sure you enabled the SSH service as it is disabled by default.

There is no ppp dialup support in LE.

No

boot from the firmware, access the filesystem, search for dtb.img

popcornmix a provisional 8.2.5 image with the updated http://startup.elf/fixup.dat files seems to work fine (at leas it boots, which is the main thing).

Contents of the backup are relative to /storage so should not interfere with macOS.

The dtb file forces some defaults; but if absent the firmware changes currently result in the same defaults, so its missing but not essential. There will be an 8.2.5 release to bump firmware in the near future (we found some issues, they are being resolved) and it can be included then.

You're better off posting Chorus2 questions to the support thread in Kodi forums.

LE uses mainline kernel drivers, so if our drivers are lacking, so is Linux generally. Go test with a current Milhouse 9.0 release as it will have newer kernel/drivers over 8.2 images, and if still the same issue and the LED on the AVR really is critical (which it never is, but users get rabid OCD on this topic) you need to report the issue upstream to the AMD driver developers.