Posts by chewitt

It's been a while since I flashed one, but the rough sequence (once you installed the CM drivers to Win7) is to connect the USB cable and wait for that device to be detected, then run the exe file and it detects the device, then power the box on and the memory will mount. According to the Pi Foundation site the exe should run automagically but it never happened for me - I always had to do it manually. At this point if the original Slice image used a FAT partition for boot stuff (it's a couple of years since I saw the original noobs config and I can't remember) it will be mount and you can copy over (overwrite) the boot files from the target folder of the .tar file. If not, the only option will be to flash the eMMC with our .img file which will nuke the existing install .. but the ease the pain of loss you get some extra space on the eMMC as noobs is no longer present. Flashing the eMMC won't touch the internal HDD if you have one installed.

NB: No idea what J4 is about so definitely not required.

"run" gets you a persistent install on the USB and "live" gives you a non-persistent install

I've created webspace for balbes150 to upload an aarch64 repo into, so at some point over the weekend things should start working.

Put the alpha release on a USB stick and test-boot without touching the existing install.

Read Infrared Remotes [LibreELEC.wiki] for info on creating a custom IR config. It's not that hard and using the original remote is probably miles easier than suffering CEC (which works well on some TV's but can be awful on others).

LE has never shipped anything official with that script included.

GMA3650 is not supported. It's not impossible to find the drivers. It's only impossible to use them

If you changed the Kodi splash (and the new splash lives under /storage/.kodi somewhere) it will be included in a backup. If you changed the LE boot splash in the boot partition it will not be included.

NB: LE doesn't ship images with installtointernal scripts so anything in that direction isn't our problem.

If you're using the current alpha release CTRL+ALT+F3 should switch you to a local console. On older releases you might need to add "tty" to the boot params in either syslinux.conf or extlinux.conf (whichever is being used) in the first partition on the USB stick.

It depends on the hardware vendor, there's never been a standard for which key gets into firmware/bios

The first question for all "my wireless doesn't work" questions is .. what chipset is in the wireless device?

Old laptops have never been target hardware for the project so we'll probably skip the opportunity to add support. Self build and figure out the changes; then push them to a GitHub repo so we can see what's required. Best case if it's simple we might consider adding it. Worst case anyone else who ever needs the same driver and find this thread can go see how it's done .. or they know who to beg an image from

You need approx 2.5x the size of the update file free to perform an update. If you get stuck you can unpack the .tar file on another device and copy the KERNEL (or kernel.img) and SYSTEM file over manually. This avoids the need to store the .tar file + uncompressed tar file on the same (full) disk and you can usually get away with the update. Some spring cleaning is never a bad idea tho

"Spins up" and "has enough power to be used" are two entirely different things.

That's not a debug log (so all the python debug output is missing) and there's no evidence of you opening the settings addon and taking a backup in the log. Not much I can do with that.

I'm not sure why you created a Raspberry Pi image because you don't have a Raspberry Pi, and you posted looking for the older kszaq images (which moved server) and I've given you updated URLs.

FYI, I'm planning to add wireguard support to our kernels once it gets merged.

It might work. It may add new problems (as playback on S912 devices is on the edge of acceptable anyway). You need to go experiment instead of asking hypothetical questions.