I genuinely forget what "echo somevalue > /proc/sys/something" hack is needed to force AP mode. I do remember that it never worked right and in the 3-4 years since I last tested nothing has changed in the Amlogic legacy kernel that would improve it. On that basis your options are limited to using a proper router or getting a USB external wifi stick (which is also a bit of a gamble due to the old kernel involved). If you value an easy life .. use a router.
Posts by chewitt
-
-
Kodi maintain a list of known/banned add-ons and repos that we reference in our forum rules and users have to acknowledge our forum rules when creating an account.
-
If you updated from one of the initial test versions then passwords might be overwritten (once) as the password changes were added shortly before merging and the first run of the current addon would be treated as a first-run and would create/set passwords. However once you're on the current addon that shouldn't happen again. If it does, there's a bug to be investigated.
-
Good news for Slice users .. especially those still with the original CM card: Compute Module 3+ on sale now from $25 - Raspberry Pi
I swapped email with Gordon at the Pi Foundation (one of the Slice designers) this afternoon and he confirms that CM3+ is compatible. Install an LE 9.0 image to use the correct firmware.
-
Degradation over time sounds like a resource consumption issue, e.g. free memory being exhausted and the OS being unable to service requests. If there was a general issue with 8.2.5 or even the current beta we'd know about it (due to the number of active installs). These things are normally hard to pin down but the nature of LE's packaging means everyone's base (read-only OS) install looks the same so it's more likely to be the result of other software installed, e.g. add-ons.
-
It's more about how we provide support than anything else. Overlay filesystems (as used by some of the router distros) would make it possible to have /opt and install things to our read-only image but it's guaranteed that we periodically make changes that break things. Users will then blame us and/or expect us to restore compatibility and that's a level of maintenance and testing effort that we're not resourced for - we are considerably smaller than OpenWRT and all conventional distros. NB: We already support a reasonable range of apps via Kodi add-ons (and reasonable non-piracy requests for useful apps are often fulfilled) while Docker provides a more abstracted and sustainable way to handle "anything else" requirements. We have a long-term and happy partnership with the linuxserver.io team who maintain a repo of Kodi add-on containers that are proactively tested on LE.
-
Check the SSH client is current/updated. Over time the default cipher suites used with SSH change to drop support for older untrusted ciphers and old clients might not like the newer defaults. Clear any cached keys for the same reason.
-
A heads-up on future changes (note the final paragraph on 3263):
-
-
The hotspot feature in LE is intentionally basic and connman supports SSID/passphrase configuration only - nothing else. If you want wireless router features the best thing to use is .. a wireless router.
-
It might be resolved when we bump to mainline kernels, but there's no schedule on that. If you want a router the best device to use is a router. The last Apple a1rport express that I picked up on eBay was $12 and it performs miles better than any on-box hotspot.
-
You can try other GXM device trees.
-
Just a hunch .. rename the partition labels on the SD card.
-
-
If the Aeon Nox developer (who is a Team Kodi member) keeps the add-on updated in the Kodi repo it will be available for install. If it's not kept updated then Kodi may not show it as available and compatible. It's nothing to do with LE.
-
It means we stop using the older Amlogic kernel sources (full of proprietary low-quality drivers etc.) and start using the latest (aka mainline) Linux kernel with modern and higher-quality drivers.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link