If the device booted as far as it did, the app that was used to create the SD card is irrelevant because the bootloader on the SD card booted and found KERNEL which runs the init script that then failed to find the SYSTEM file in the same boot partition that KERNEL resides in; ergo the partitioning itself is not the issue. The problem resides in the kernel .. and it's usually something related to mmc support.
Posts by chewitt
-
-
Can anyone help ?
In the absence of a full debug log .. unlikely
-
RK3588 boards will be supported when upstream kernel support catches up with our requirements. Lots of the core bits already work (enough for a desktop OS) but "all the media stuff" that an LE image usually takes a while longer.
-
The connman/iwd changes are already merged into LE11 branch. NB: I'm not sure what advantage you're expecting with aarch64, but it's not going to noticeably improve anything and you will have to reinstall or remove binary add-ons) as they are not aarch64 compatible; and there will be no replacement binary add-ons in the repo as there are no ARM aarch64 releases for LE11 so the add-ons weren't built/don't exist.
The kernel patchset is ridiculously large but will reduce if I ever find the enthusiasm to rebase it on a newer kernel. I have no plans to do that in the near-term future though.
-
Netflix are very agressive at blocking traffic from non-domestic ASN's (blocks of IP ranges). I'd wager there's a 99%+ chance that the ASN's for any commercial VPS hosting provider will be on their block list.
-
The primary difference between Windows/Linux filesystems is that when problems arise Windows tries at all costs to keep things running and eventually just fails resulting in loss of access to data, while Linux fails at the first opportunity to avoid further problems, usually resulting in data being recoverable/moveable before you reach a complete loss. The difference often results in "but, but, it worked under Windows" type forum posts which are both correct and completely missing the point that Linux is doing the right thing.
-
run "pastekodi" over SSH and then share the URL generated
-
The best upgrade would be to a recent-ish Intel motherboard with integrated graphics, as those are going to support HEVC + 4K and most of the recent ones do HDR too (although HDR support is still work-in-progress in Kodi). I can't advise anything specific though as I didn't run an Intel CPU device for LE/OE use in the last decade (only ARM boards) and Intel breeds "lake" codenamed chips faster than I can keep tabs on the damn things.
-
-
It's in the boot partition of the AMLGX "box" image. If you download the "wetek-play2" image, that's the wrong image (can only be used with upstream u-boot, i.e. requires Android/vendor u-boot to be erased or overwritten).
-
Radeon HD 7000 series - Wikipediaen.wikipedia.org
If you correlate the "Southern Islands" features between ^ those two the 7550 card is 1080p max so it's not going to improve on the existing card that you have. I would also avoid the nVidia card (unless it's $free) because there is zero support for nvidia cards in the Generic/GBM image (our long-term technical direction) and whilst Generic-Legacy still exists and still supports them under X11 and it will do 4K, most 4K content is now HDR and X11 means no HDR support.
-
This was already answered in another thread. Please do not double post.
-
Post the full log .. not the bit you think is important (which leaves out all the other useful info)
-
SSH into the box and run "alsamixer" .. it's a console app not a GUI app.
-
I've asked that connman/iwd are bumped for LE 11.0.2. There's no guarantee that this resolves issues, but it's likely to improve the status of things for someone somewhere.
-
-
I tried editing /etc/hostname, but it reverts back to LibreELEC after a boot.
IIRC *the* place to change hostname is the LE settings add-on; this is the master location that defines what is set/propagated at runtime. If you edit /etc/hostname directly the change will not persist over a reboot. LE is not a general purpose distro - it does not always follow other distro conventions for doing things.
-
LE 11.x now uses a GBM/V4L2 video pipeline which does not support the methods previously used to grab frames, and reimplementing that is technically non-trivial and probably won't happen. The best (only?) approach available now is to use an external HDMI grabber, so there is no 'software' dependency on acquiring frames to drive the LED's.
