[Milhouse]

Hi Milhouse,

I want to test the latest testbuild with my environment. This is complete network booting without an SD card. a few month agou you updated the testbuild with the driver for pi 3b+ for this.
Yesterday I got the POE hat for my Pi and I want to test the lastest build because there is an (fan) driver for the hat available.
8.2.5 with network boot works well.
the latest two testbuild crashes after the kodi intro video / boots the kernel and i got one crash log then the display stays blank and I'm able to access the linux console via ssh.
i tested your build with a clean storage so there shoud be no impact from addons! Only my advancedsettings.xml for database connection and some dirmapping are available.

there is nothing available in the log:
http://ix.io/1mkM

and here is the crashlog:
http://ix.io/1mkN

since 0822 there is also rpi-poe.dtbo missing... (new kernel version in this update)

if you need more information or if i can do something at the console pls. give feedback.

Thanks
Frank

Yes, thanks for reporting this - it looks like RPi POE support is missing from the 4.18.y kernel - I've pinged popcornmix about that.

I don't think the Kodi crash is netboot (or POE) related - Kodi seems to be in an infinite/recursive loop authenticating URLs for some reason, presumably path substitution related.

The line in the log that should be appearing (but doesn't) is:

text:


00:19:45.400 T:1938610848  NOTICE: CMediaSourceSettings: loading media sources from special://masterprofile/sources.xml

Just out of interest, is Kodi starting successfully with #0821?

Can you try starting Kodi 18 (ie. #0907) without your path substitutions? If Kodi starts, can you add the path substitutions back one at a time to determine which one is the problem?

If LibreELEC 8.2.5 is starting Kodi *with* your path substitutions but these test builds are not, then this would suggest there is a change in Kodi 18 that is causing the problem - I fixed LE9 netbooting in #0323 so hopefully the problem exists somewhere between #0323 and #0907, can you identify the first build with the problem?