Posts by milhouse

Try looking at an existing addon.

If your add-on is a binary add-on - ie. it contains C/C++ code - then look (for example) at pvr.demo, and if not - ie. it's 100% Python and/or XML - then look at something like the LibreELEC-settings package.

You need to add the package (ie. package.mk) to the build, with the package.mk linking to your add-on source repo, then you need the package to be included in the build by adding the package name as a "PKG_DEPENDS_TARGET" in packages/virtual/mediacenter/package.mk

Quote from eightball70

Patch for GLK HDMI bug was updated to V3: [v3] drm/i915/glk: Add Quirk for GLK NUC HDMI port issues

There's a v4 of this patch included in last night's #0703 build: LibreELEC Testbuilds for x86_64 (Kodi 18.0)

Just to say for LibreELEC there's a couple of extra steps when extracting the firmware:

1. Extract bootcode.bin, start_x.elf, fixup_x.dat from the popcornmix zip

2. Rename start_x.elf to start.elf

3. Rename fixup_x.dat to fixup.dat

4. Copy bootcode.bin, start.elf and fixup.dat to /flash

I'll include it but the first reply to the v3 patch on the bug doesn't look promising.

105887 – (ford) [GLK] no signal after switch resolution from [email protected]

I would suggest getting PVR Simple working with LE 8.2.5, then once you have it working only *then* upgrade to an LE 9 test build.

I'm not saying there are known problems with LE9 and PVR Simple, but you're starting with an unstable build and it's entirely possible you've found an issue, but it's just as likely (from our point of view) that you're simply not setting it up correctly.

So start with known good software, ie. LE 8.2.5, then upgrade to LE9.0 once you have a working system.

I'm not aware of any reported issues with interlacing or black/flickering screens in 9.0 (there's a dedicated 9.0 testing thread on the Kodi forum) and without any bug reports there isn't likely to be a fix.

Sorry, been a bit busy.

I'll ask popcornmix if he can determine what changed in the firmware between #0226 (stable) and #0305 (unstable) that might explain the instability. It's very strange that this is only affecting a very small number of users (you, maybe Mario).

Did you try the latest LE9 test build as you were instructed? It includes a more recent version of xf86-video-ati (18.0.1 vs. 7.8.0) and newer versions of a whole bunch of components, any one of which might contribute to this bug in LE8.2.x. AMD hardware now supports VAAPI by default in LE9 builds.

Testing with the current development version is your best option because as already stated there are no plans for further LE 8.2.x releases.

All versions of MySQL server are currently supported with no known issues, although only limited MySQL testing is performed so if you're testing a bleeding edge MySQL server you're likely to be on your own.

My guess is your database is/was corrupt, or because you had installed the server on Windows there was a problem with case sensitivity (Linux is case sensitive, Windows is not). Best option is to not use Windows...

MySQL :: MySQL 8.0 Reference Manual :: 9.2.2 Identifier Case Sensitivity

Quote from vamp

What do you think milhouse it is possible to create a test release that include the latest firmware, but not include this changes?

There's no need for a test release, copying the #0226 firmware is sufficient.

Please try the remaining daily builds (#0227, #0228 etc.) just to be sure, but it's quite interesting that #0620 + 0226 firmware is stable.

Can you post the contents of your /flash/config.txt ?

mkdir /storage/bind
cp -r /usr/share/kodi/addons/service.libreelec.settings/ /storage/bind

Add the following to /storage/.config/autostart.sh:

mount --bind /storage/bind/service.libreelec.settings /usr/share/kodi/addons/service.libreelec.settings

Reboot, and now you have read/write access to the addon. Most of the Python code is compiled, so you'll need to copy any source code you wish to test into the /storage/bind/service.libreelec.settings directory.

phunkyfish - write the LE8.2.5 img.gz to your flash drive, then...

1) Open the contents of the LE9 tar file (7zip on Windows will work), find the SYSTEM and KERNEL files within the tar file and copy them over the same files in the root of the flash drive - you've now updated the flash drive to LE9

or

2a) Boot the LE8.2.5 flash drive, choose "run" mode so that LE 8.2.5 boots from the flash drive and uses the available space of the flash drive for storage (don't worry if it doesn't give you any video at this stage)

2b) Connect to your machine (you'll need to find out it's IP address somehow) using Windows Explorer (or similar) and copy the new tar file into the Samba "Update" folder

2c) Reboot LE 8.2.5 from the flash drive, select "run" mode again and it will proceed to update the flash drive to LE9 - when it reboots, choose "run" mode to boot into LibreELEC LE9

Quote from vamp

So i think the problem between #0305-#0226

That's interesting, and you're sure that #0226 is stable? There's not much change in the #0305 firmware, but popcornmix will know for sure.

Can you confirm the device you have - is it RPi2 or RPi3B? I'm assuming it's not a RPi3B+ based on the versions you have been testing. Edit: You've already said it is RPi2

Just to be sure there's nothing non-firmware involved, can you also test the individual builds between #0226 and #0305 (ie. #0227, #0228, #0301, #0302, #0303 and #0304) and confirm that they are all stable - if any of them start rebooting then it's not exclusively a firmware issue.

I appreciate this is a lot of tedious, slow work but hopefully it will prove fruitful in the end!

Mario77 if you still have your RPi2 are you able to confirm that #0305 reboots, and #0226 is stable?

vamp this would suggest a firmware issue, but so far you (and Mario77) are the only people reporting it.

Unfortunately there are 6 months of firmware changes between 8.2.3 and 8.2.4: Comparing 89a2371~1...3347884 · raspberrypi/firmware · GitHub

In order to determine which change is causing your random reboot, which is extremely rare (only two of you out of hundreds of thousands), you'll need to identify which firmware introduced the problem - although it seems more likely to be a hardware issue (maybe a marginal SOC) given how rare it is.

You could try testing the LE nightly builds from early this year to late last year, which covers the period for 8.2.3 to 8.2.4:

#0313: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0309: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0307: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0305: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0226: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0209: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0207: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0202: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0131: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0125: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0117: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0111: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0108: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#1201: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#1117: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#1103: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#1024: LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

#0313 is the most recent build you should test, and includes the same firmware that is used by 8.2.4 - in theory, you should experience random reboots.

#1024 is the oldest build you should test, and includes firmware from about the time of 8.2.3 - in theory, you should not experience random reboots.

If you test #1024 (and have no reboots) and then #0313 (and have reboots), then somewhere between those two builds you should be able to determine the build when the rebooting starts. Once we know this, we can identify what changed in the firmware.

Please continue testing with your 2.5A power supply.

Quote from CvH

exactly ... meh so we have to wait a bit - next time I try to boot it ;D

An updated build should work now that Python 2.7.15 has been merged - the Kodi crash is caused by a Python 2.7.14/gcc8 incompatibility.

vamp it's very (very!) unusual for a Kodi related issue to cause the entire system to reboot. I'm not even sure what could cause the system to reboot (apart from a malicious addon) - normally if there's a problem the system might freeze, behave strangely or Kodi will crash, but almost never have I seen the system spontaneously reboot.

The Kodi crash log you posted (from https://forum.libreelec.tv/8.2.2) shows a MMAL crash (video player), but you're saying 8.2.3 is good and 8.2.5 is bad, so I'm not sure what the relevance is of the 8.2.2 crash log?

Given the unusual reboot behaviour I would suspect a hardware issue, possibly insufficient power supply. What kind of power supply are you using, what is the rating in amps?

It is possible the firmware in 8.2.4/8.2.5 causes the GPU to do more work which changes the power profile of the device, requiring slightly more powe and, if your power supply is marginal , it could turn a stable 8.2.3 device into an unstable 8.2.5 device. The solution is to use a correctly specified power supply with your Raspberry Pi.

If you are using a correctly specified power supply, and continue to have these "random restarts" then try a different RPi board, if possible.

If you continue to experience Kodi crashing (ie. not system reboot) while playing movies then please reproduce the issue with a LibreELEC 9/Kodi 18 test build as the version of Kodi in LE8.2.5 is no longer developed, so no fixes will be possible. Post a crash log in the Kodi forum thread from the LE9 build, ideally with a sample movie, and we can investigate that and hopefully provide a fix in LE9.

I've officially switched my nightly builds to 4.17.y and will now continue publishing 4.17.y based Generic builds in the Kodi forum. Thanks for all the testing, it's been very helpful, and thanks to sky42 for finding the GLK patches and getting the ball rolling on these mainline kernels.

Quote from chewitt

Attachment #1370318 for bug #1527231 is the proposed patch. What image do you need for testing?

ping milhouse

I'll push a PR to master and include it in my nightly builds, but don't merge it until we get some feedback...