You can play around with profile to limit options.
Posts by chewitt
-
-
Add the DNS record to Win10's hosts file, then it will always resolve.
-
I'd ask that the LE repo is removed and forked properly before the branch is then re-added. This allows cross-fork comparison so changes made can be easily seen and understood. The way it's currently been done, comparison is awkward.
-
How is this relevant to LibreELEC ?
-
No discussion or recommendation of Acestream in these forums. It's sole purpose is piracy.
-
-
Change Kodi to use MMAL not OMXplayer?
-
I think that Libreelec is mostly used by people who reuse old hardware. If delelopers think otherwise - then this project is already DEAD (or in active process of decaying)... IMHO...
I base my knowledge of our userbase on facts (we track this kind of thing) not humble opinions. The facts are (and have been since our inception) that we focus on dedicated HTPC devices; we do not intentionally support old hardware and laptops. If old junk works, that's great. If it doesn't, our standard response to any user is "head on over to Ubuntu, they support old stuff better than we do" and there are no plans to change that.
-
Or use LE 8.2.2 and set the "legacy security" option in the GUI (added in the 8.2.2 release). No need to visit the console.
-
Do I have to answer the question again? At what point do you get off the fence and believe the answer?
-
-
LE runs fine (slowly, but fine) on RPi1 devices with 512MB RAM.
-
Set a static DHCP reservation in the router or DHCP server, then DNS resolution doesn't break and interfaces don't need to be restarted.
-
Kodi debug log and "dmesg" log
-
Old laptops are not target hardware so there is no PCMCIA support in the OS, which narrows your choices. On the USB Ethernet front, it's always a bit of a gamble as it's never possible to tell which chipset is used from the box/packaging, but in practice there are only 2-3 usb ethernet chipsets in use and the drivers for those are included.
-
1.5GB should be fine
-
If you can understand and isolate where the issue is:
a) OS things should be resolvable through a software update. Eminent (or their maintainer) can choose to fix anything they like as this is under their direct control and they can release their software as required. That said, in recent times they have been loosely tracking our releases, and 8.2.2 is the last release we intend to make for Krypton so I wouldn't expect miracles.
b) Kodi issues will not be resolvable in the current (Krypton) codebase. All fixes in the last ~6 months have gone into the Leia codebase and this will require Eminent to create/ship an image based on Leia in the future.
Make sense?
-
GDPR-1 I asked spiff and he has no plan to submit vfs.sacd to Kodi until there's been some decent field testing .. so there's a chicken vs. egg situation there
