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
-
-
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.
-
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.
-
-
-
-
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.