LE installation simply creates two partitions; 512MB and 100% of remaining space. We install the syslinux bootloader with a conf file but we don't actually care which bootloader is used, so if you prefer grub (or grub is the only one that works on your box) go use it. Ubuntu uses grub so that might be a good idea. You simply need to set boot= and disk= in boot params to indicate which partition contains the KERNEL and SYSTEM files, and which one should be used as /storage.
Posts by chewitt
-
-
It's also /storage/.config/system.d not /storage/.configfiles/system.d
-
There is no reason to create a .mount file in /storage/.config/sysctl.d
-
LibreELEC 6.0.3 is not supported anymore, so you are very much on your own.
LibreELEC 6.0 doesn't exist, we forked and started our releases at 7.0. Anything before then is someone else's problem
-
I want to use my old unused htpc as nas/media server for my s905 & s912 boxes overn LAN.
Unfortunately my mobo is old and doesnt seem to support WOL. It does however resume from USB (mouse, keyboard or ir receiver).
With this in mind, if I purchased a USB lan adapter for htpc, will I be able to use resume then (ie wake up PC as WOL)?
No. The USB network adapter is not a keyboard.
-
You need to ask that question to Kodi developers in their forum.
-
I would advise against nvidia purchases. Long-term LE/Kodi support for nVidia GPU's is questionable due to nVidia (again) choosing to set their own 'standard' instead of following the one used by literally everyone else. I'll be writing a blog post about them soon.
-
It's not possible. Kodi currently builds the 'playlist' of images at start and the list is not refreshed or added-to unless you stop and restart the slideshow. The whole 'photos' side of Kodi is a little under-developed, so code submissions to improve it are welcome.
-
lorenzo53 in 2014 when OpenELEC discontinued i386 images there were only ~1500 users. That number will be much smaller today, and there is no plan for LibreELEC to reverse the decision.
-
UsePrivilegeSeparation=yes makes sense in a conventional distro where you have multiple users and it is desirable to limit the code that runs with root privileges. In LE everything already runs as root, so setting it achieves nothing.
If you want to experiment you set additional boot time args in /storage/.cache/services/sshd.conf, e.g. include an option to use an alternate config file /etc/sshd_config .. from fuzzy memory it's "-F /path/to/file" ??
-
If you want to mount to /storage/timecapsule the systemd mount file MUST be named storage-timecapsule.mount, the hyphen/dash in the filename is important. You said you created "storage.timecapsule.mount" .. which won't work.
-
It depends on what you define as "standard add-ons" ??
-
You need to tell us the USB ID's of the device (run 'lsusb' to see them) else we can only guess at the problem.
-
Some users expect to replace their box(es) every two years. Others expect their investment to last longer. Since we know today that those boxes are currently (sadly) a technical dead-end, we should be clear about it so users can make an informed choice. For the record, I am still petitioning Amlogic to license the Linux libs that would guarantee S912 a better future.
-
-
LE does not provide the BIOS for your unknown hardware box. You need to ask the manufacturer.
-
There's a tool called l2ping that's part of bluez-tools, but we don't compile it into standard LE images. If you did a custom build with that you can ping the device. I'm not sure that will keep the device alive though. I would expect the keyboard to sleep and then the pings will just time out. You probably need to do something that queries information from the device. I'm not sure what that would be though
-
It's probably an S805 and you might find a working image among the sticky threads in this subforum. There are few people creating images for S805 boxes now .. mostly because there are newer/shinier cheap boxes available.
