Posts by chewitt

Yes "works fine for me" .. but I'm using a wireless device with a well written drivers (ath9k_htc). If you're using something with a garbage Realtek USB wireless driver .. YMMV.

Make sure you're using the HDMI connector nearest the power port.

LibreELEC.tv/openssl-config at master · LibreELEC/LibreELEC.tv · GitHub

^ put the certs that you need in /storage/.config/cacert.pem and they will be appended to the embedded certs at boot time.

I think we reached the point where we need to start mirroring add-ons for download instead of self-host

No Linux devices truly support HDR at this time and Kodi has only partial siupport (still work in progress). RPi4 and Intel NUCs (Gemini Lake and newer) are most likely to be best/first supported due to the higher overall levels of development in their ecosystem.

Team Kodi made the decision to bring forward the release for Kodi Matrix (v19) to forcibly kick-start the migration to Python3; because most of the add-on developers are sitting on their arses not-migrating their code. I'd previously expect things to play out over the next ~6 months and that would align with the original v19 not-an-agreed-schedule, but now that v19 comes early it will push HDR to v20. That said, v20 is probably a shorter development sprint than normal to compensate. Not that the word "sprint" should ever be closely associated with Kodi schedules

crazycat is/was planning to bump things once 5.4 is released, not before. I'm also waiting on LE master branch to stabilise after the Py3 changes before spending time on 5.4 things (not much spare time at the moment).

Fix NTP in your network and the RPi will have the correct time. The 11/4/2019 date is the release date of the current glibc version, which acts as the fall-back when NTP fails.

connman provides an intentionally simple tethered hotspot as you'd find on a mobile phone (which is what it was written for). If you want the hotspot to do more, you will need to code it to do more. Sources are freely available and the connman mailing list is the place to send your feature enhancement or bugfix patches.

connman/connman.git - Connection Manager

We have no plans to add support for any more Realtek chips that require badly written vendor drivers that break with every kernel update. Once their chips become supported in the upstream kernel (and thus becomes simple to maintain) we'll be happy to configure them in out kernels.

Not the answer you're looking for I know .. but that's the answer.

Devices with Atheros chips are generally well supported in the kernel, but few vendors give details on the chips inside the packaging so you've got quite a mission to find devices. As a general rule - if it's cheap it's Realtek (sadly). eBay UK might give more options for WiFi bridge devices.

Share "journalctl | paste" a minute after booting the 9.1.502 image.

Original S905 devices like the Odroid C2 do not support HDR.

Bump to 9.1.502 and retest. It has newer kernel/drivers/firmware which may resolve the issue, and even if you found the issue on 9.0.2 we're not going to put the fix in that release (there is no plan for 9.0.3 release).

Realtek breed new wireless chips faster than anyone can figure out how to support them, and 80% of their drivers are "out of tree" with low-quality driver code. Over a period of years we got bored of adding ever more shitty realtek drivers that break with every kernel bump, so we stopped adding them. In the future we'll probably move to IWD which will making it technically impossible to use half their junk too. Get a used Apple A1rport Express and run it as a WiFI bridge. It will present Ethernet to the Pi, has better range/throughput than any USB dongle, and there's no drivers required so they're future proof. You can use any WiFi bridge device, but I find the A1rport ones to be cheap ($15-20) now since Apple stopped selling them.

If your network functions correctly there is never any need to fiddle with cache settings, and the solution to a network that doesn't function correctly is to fix the network, not fiddle with cache settings. RPi 3B+ has weak wifi performance so it's best to use Ethernet or an external wifi bridge that presents Ethernet. I use some Apple A1rport Express WiFi routers in bridge mode for this .. they are fairly cheap (second hand on eBay), easy to set-up, they out-perform all USB wireless dongles for range/throughput, and no drivers are needed.

Quote from ilchenko

Almost all addons don't work

That's expected. Team Kodi announced the move to Python 3 two years ago but everyone sits on their arses and does nothing until a hard change is forced. Once the first public alpha for Kodi Matrix ships developers will wake up and start to fix their add-ons.

Apr 11 17:28:58 LibreELEC connmand[478]: eth0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
Apr 11 17:28:58 LibreELEC connmand[478]: eth0 {del} route ff00:: gw :: scope 0 <UNIVERSE>
Apr 11 17:28:58 LibreELEC connmand[478]: eth0 {add} address 192.168.0.16/24 label eth0 family 2
Apr 11 17:28:58 LibreELEC connmand[478]: eth0 {add} route 192.168.0.0 gw 0.0.0.0 scope 253 <LINK>
Apr 11 17:28:58 LibreELEC connmand[478]: eth0 {add} route 192.168.0.1 gw 0.0.0.0 scope 253 <LINK>
Apr 11 17:28:58 LibreELEC connmand[478]: eth0 {add} route 0.0.0.0 gw 192.168.0.1 scope 0 <UNIVERSE>
Apr 11 17:28:58 LibreELEC connmand[478]: ntp: adjust (jump): +18133880.539957 sec
Nov 07 13:40:19 LibreELEC connmand[478]: eth0 {add} route 212.227.81.55 gw 192.168.0.1 scope 0 <UNIVERSE>
Nov 07 13:40:19 LibreELEC connmand[478]: eth0 {del} route 212.227.81.55 gw 192.168.0.1 scope 0 <UNIVERSE>
Nov 07 13:40:20 LibreELEC crond[281]: time disparity of 302231 minutes detected

Pi devices have no RTC chip so on boot before NTP has updated the clock the time will start from the release date of the current version of glibc which probably dates from a release in April. Once the network is up NTP updates the clock and dateTime changes.

How are you running MariaDB? .. it doesn't look like the DB is up/running before Kodi attempts to access it.