Both of the mentioned log files don't seem to give any extra info and simply repeat the error I quoted here. Hopefully this will shed some light on the issue.
Please post the contents of the logfiles, sometimes they contain references to other logs (eg failed dependencies) so it's worth to check them, too.
If in doubt capture the full build log and upload it somewhere (it could be huge, though). eg
ARCH=arm PROJECT=RPi DEVICE=RPi4 make image 2>&1 | tee build.logso long,
Hias
How to build an image for the rpi4 from the Github source? I've tried the build instructions and used device=rpi4 but that doesn't seem to work.
"Doesn't seem to work" isn't too specific. I use this to build RPi4 images:
ARCH=arm PROJECT=RPi DEVICE=RPi4 make imageso long,
Hias
That's probably the well known issue with interlaced video. See here for a fix LibreELEC (Leia) 9.2 ALPHA1 with Raspberry Pi 4B Support or wait for the next LE release (which should be available soon).
so long,
Hias
I don't remember a post on the Milhouse build thread either. The fix was included added in kernel 5.0.8 (and 4.19.35). I found this post though from Matt "Mr. Chromebox" Devo where he wrote that the network issue is fixed in LE 9.0.2 ChromeBox Kodi E-Z Setup Script (LibreELEC/Linux+Kodi) [2017/02/21]
I don't have any Chromeboxes myself, just remembered that the network issue came up numerous times in the Milhouse x86 thread.
so long,
Hias
I haven't tested composite out myself yet but others reported on the RPi forums that they had issues with composite, too Extremly Poor performance with tvout enabled - Raspberry Pi Forums
It's currently being looked into, could be that some firmware fix is needed.
so long,
Hias
Update to LE 9.0.2 or 9.1.001. Slow network performance on Chromeboxes is a known (kernel) issue and should be fixed in newer LE versions.
See also Chromebox - Official Kodi Wiki
so long,
Hias
9.1 are the alpha/beta versions, 9.2 will be the final stable version after finishing alpha/beta tests It follows the same scheme that we used eg for 8.2.
See also the wiki page: Releases [LibreELEC.wiki]
so long,
Hias
Where did you read about the crappy IR-receivers?
Sorry, can't remember, could have been on kodi or intel forums.
Unfortunately IR problems with NUCs seem to haunt a lot of (linux) users. An easy workaround is to use an external USB MCE receiver. The HP branded one for example works fine, it's not exactly a small or beautiful thing but it's well supported in Linux (I have one here too) and rather easy to get (package with HP MCE remote plus IR receiver costs about 15-20 USD shipped from China on ebay).
so long,
Hias
Is it possible the the missing shared library (libssl.so.1.0.0) could cause my problem?
Yes, this is quite certainly the problem. Make sure you have the current tvheadend42 addon installed. Kodi log will show that info, just use the logfile uploader in LE settings and post the link here.
BTW: very often (addon) update problems are caused by slow network initialization (kodi log will show that, too). Enable "Wait for network" in LE settings makes sure the network is up before kodi start and fixes these issues.
so long,
Hias
Try to update your NUC to the latest BIOS version (this may require Windows) - Intel has quite a history of screwing up IR. IIRC a BIOS update about half a year ago solved that on the gen7 models.
Also check with "ir-ctl -r" if your NUC receives any IR signals at all (you should get some "pulse" and "space" messages if you press a button).
Plus try placing the IR transmitter / hub very close to the NUC. IIRC there were also reports that the sensitivity of the IR receiver on some NUCs was very bad.
so long,
Hias
After upgrading to LibreELEC-Generic.x86_64-9.1.001.img.gz from 9.02 the TVHeadend-Server does not startup anymore. I had to connect an external TVHeadend-Server from another PC to the Libreelec-HTS-Client, otherwise TV would be unavailable.
Not much we can do about it unless you post some logs.
Provide Log File [LibreELEC.wiki]
so long,
Hias
This should be doable with a .kodi/userdata/keymaps/remote.xml with the following content:
<keymap>
<global>
<remote>
<zero>Number0</zero>
<one>Number1</one>
<two>Number2</two>
<three>Number3</three>
<four>Number4</four>
<five>Number5</five>
<six>Number6</six>
<seven>Number7</seven>
<eight>Number8</eight>
<nine>Number9</nine>
</remote>
</global>
</keymap>The default for 2..9 on remotes is JumpSMS2..9 to get T9/SMS style input. With Number2..9 you'll only get numbers and have to use the on-screen keyboard if you want to enter text.
so long,
Hias
I'd recommend getting a good quality "A1" rated SD card. I'm using the Sandisk Extreme 32GB A1 here on various RPis (1-4) and they perform really well.
Having just a SD card makes the setup a lot simpler.
so long,
Hias
No, there are no more 9.0.x releases planned. Please upgrade to 9.1/9.2 - RPi0-3 and x86 should work without problems, as the 9.0 releases before.
so long,
Hias
does the "Raspberry Pi VNC" addon on Rasp4 4GB work?
Thank you for your answer.
I haven't tested with the one that's currently in our addon repository but with a locally built one and that worked fine.
so long,
Hias
I don't really get it. I understand that this is an alpha build for Raspi Pi 4 but what about this build for generic devices which is available for download too? Is this also in alpha state?
See the release notes linked in the first post
LibreELEC 9.2 for Generic x86/64 and Raspberry Pi 0/1/2/3 devices is a solid beta quality release.
so long,
Hias
Can you upload a full log using the log uploader function in LE settings or by grabbing it from the Logfile samba share? Provide Log File [LibreELEC.wiki]
kernel/journal logs would also be helpful, the issue could be related to USB issues seen with some devices xhci: add quirk for host controllers that don't update endpoint DCS by P33M · Pull Request #3066 · raspberrypi/linux · GitHub
so long,
Hias
Stuttering and a/v sync problems on very high bitrate files (eg "Sony Surfing 4K Demo", 4kp60, avg 77Mb/sec, peak 118Mb/sec HEVC) are known issues and are being looked into.
Stuttering with interlaced videos is already fixed, either use the updated firmware or wait for the next LE release (which should be out soon).
so long,
Hias
