NB: For the handful of people who are advance testing CM3 boards, the FiveNinjas folk requested the Slice2 image to be renamed to Slice3 to avoid user confusion. This means you will need to run "touch /storage/.update/.nocompat" before manually downloading the 7.95.1 beta else the compatibility check run during the update process will fail. It's technically possible for us to add an extra script to negate this, but with literally 5-6 people affected I've decided to finish something else and learn that trick another day 
Posts by chewitt
-
-
Our 7.0 branch is now closed to all development apart from add-on updates so anything testing/poking you do should be on Krypton builds.
-
They are different devices for different budgets and user styles (fully spec'd retail boxed product or bare board with accessory options). Both devices are in widespread use among the team, and ultimately our technical direction cares more about the chipset/internals than the manufacturer logo on the box so I'd say both have the same lifespan.
-
There is no official "team" and thus there is no official "leader" of the team although if you look at GitHub records some of us seem to press the merge button more than others. We operate more like a 60's hippy commune than a hierarchical army of developers
Why do you ask?
-
Nexbox has the board UPSIDE Down within the casing.
That to me is a bad design due to the fact that Heat Rises.
The casing is also smaller than other boxes.Users often misinterpret the function of cooling to be making their box/device run cool, or as cool as possible, which is never the [sic] case. In reality the main objective is ensuring a safe operating temperature range. As long as cooling holes do this, the objective is reached. Holes on the bottom generally result in lower levels of dust ingression to the device and avoid the opportunity for liquid spill damage so in most consumer products would be preferred to holes/vents on the sides or top.
-
-
There are some but the build server uploads to a private location as normally we don't want to distract attention from milhouse builds. He's moved on towards v18 so there's a gap at the moment. Be a little patient and the 7.95.1 beta will be along soon.
-
openssh: UsePrivilegeSeparation/StrictModes not needed by MilhouseVH · Pull Request #844 · LibreELEC/LibreELEC.tv · GitHub <= this has been resolved properly in LE 8.0 builds (no hacking of user/group with scripts)
-
Anything that uses autostart.sh is a dirty hack. Their instructions should be updated for 7.0 builds too, and for the same reasons.
-
17:44:26 19.334791 T:1963106304 NOTICE: ADDONS: Using repository
no support to users of piracy add-ons and repo's, particularly as the crapware in them frequently causes instability issues. Thanks. -
The problem is probably timing. The instructions on the MSL website should be adjusted so the function script is triggered/managed by systemd to fit into the OS startup and shutdown sequence. Adding dependencies on network being up etc. then become simple.
-
I can't script python either, but I can open the file in a text editor and look for /file/system/paths under /opt and experimentally change them to something under /storage. It's probably not a hard change.
-
(
sleep 10
amixer -c1 set PCM 100%
)&autostart.sh runs early in the boot sequence but
will background and sleep the command for 10 secs which is normally more than enough time for things to come up. -
I looked at Dataplicity Developer Hub probably briefly and if their install python script is similar they are trying to write things to locations under /opt that don't exist on LE so yes, it will fail. Modify the python script to use somewhere on /storage and it should work okay.
-
p.s. If you are installing a Chromium add-on from the Kodinerds repo, please ask Kodinerds for support.
-
I removed the build after jcdammers confirmed the fix. The 7.95.1 beta will ship with the fix (soon-ish)
-
It might be worthwhile looking at the unRAID forums as they have a tweaked LE image used with QEMU in their distro.
-
Virtual is a developer tool used for basic functional and GUI testing. It supports vmware (we dropped vbox as it breaks with every kernel bump and nobody used it). Virtual has no AMD/Intel/nVidia drivers so you will not be able to do GPU passthrough in ESXi. If you wanted to do that you'd need create something custom that has both vmware things (else the OS won't boot) and the video drivers required.
In a Generic/QEMU combo there should be a console on CTRL+ALT+F3 ..but it's not really a 'supported' configuration in the sense you won't find staff that know anything about running it, although we're aware it can be made to work.