The archive is hosted on a team members server. For some reason it's offline and he's not contactable at the moment (could be related). I'm not aware of any other archives. The other way to get a 9.0.1 image is to self-build it.
Posts by chewitt
-
-
Nobody on staff is interested in supported emmc installs on box devices; primarily because it's a pain in the arse to guide users through the install process, and then because history has proven that subset of boxes and users to be a time consuming pain in the arse to support.
You have a working SD card install. That sounds like a good direction.
-
SMB browse still works fine .. but as designed, and it's designed (by Microsoft) around SMB1 networks and these days everyone is running SMB2+ which doesn't support browsing.
-
LE images are not "ROM" images for flashing the internal storage of boxes. Create an SD card and boot the card. No guarantees it will work on all devices .. it's all about the device-tree file.
-
Enable AirPlay in Kodi?
-
-
Bad PSU, Bad SD Card, User not waiting until things actually shut down?
There is no general "reboot issue" with the RPi4 image so it's something local.
-
We already have a USB/SD Creator app for Windows on our website and we distribute a simple .img file that can be restored to a USB/SD card using a dozen or so different tools that require no integration or effort. We have no plan to ship an .iso image which is what that tool appears to want.
-
Reboot and things should be present now, someone forgot to create some aliases on the webserver (RK3399 uses the Tinkerboard addons).
-
What OS are you using to build with (distro and version) ?
-
Master has bumped to Python3 .. possibly a little prematurely, but at least it highlights where all the issues are.
So I think this patch series will be required (it's the fix for the problem, not the cause): U-Boot - Patchwork
Can you test?
-
Download "handbrake" and transcode it to H264/H265 on the desktop machine. Time to transcode will be shorter than time looking for a Pi based solution that doesn't exist.
-
chmod +x /path/to/autoexec.py ??
-
It's technically possible if you run Chrome in a docker container .. which means you cheat by running a full general purpose distro like Ubuntu in the background to gain the X11 environment needed for Chrome. TL/DR; It will run, but the performance should be pretty sucky at the same time.
-
Can i ask which is the more advanced build
Milhouse images are based on Kodi Matrix (v19-pre-pre-pre-alpha) and the LE 9.2 codebase is based on Kodi Leia (v18.4). Milhouse normally curates his images to be fairly stable despite the bleeding edge code, but right now the Python 3 bump in the Matrix codebase makes that a serious challenge and you should expect some breakage.
-
Mainline Linux kernels have zero support for Amlogic's proprietary 'Android' partitioning scheme (and there's no plan to change that). If you use a decent SD card or USB the speed difference against internal eMMC storage is negligible. If you use some cheap old device, for sure it will be less snappy.
-
Win10 needs authenticated access to an SMB2 or SMB3 share. In LE this means you will need to enable the Samba password in LE settings before trying to connect to the Samba server.
-
S905X2 needs a newer kernel than the S905X and "internal" install is not supported (old kernel scripts will not work on a mainline kernel). There is no plan to support this in the future either. Use an SD card or USB.