Posts by chewitt

Swap things around then. Write the A95XMAX_boot.img to USB and boot from it, and put the restore files on the SD card.

Get a Raspberry Pi 3B+ .. or even the 2GB 4B model. For the sake of $20 difference in price you can have something reliable and not needing to be on the bleeding edge of development. Do you prefer to watch movies or forever chase down fixes?

If you're at the LE serial console "emmctool" will tell you which is the /dev/device for emmc, so connect ethernet and scp the A95X .img to /storage and then write u-boot to emmc with "dd if=A95MAX_boot.img of=/dev/mmcblkX bs=1M" .. this should make the box bootable from emmc again and you free up the SD card for booting some kind of OS image (LE, Armbian, etc.).

What OS do you want to restore to emmc? .. and if you already have some kind of files, what are they called and what format are they? (and where did you get them from).

I said "write the image to USB" e.g. same as you wrote the other image to SD card, not "copy paste the file" so that's why it's not doing anything. Note that once the image is written and the image is mounted, you need to access the USB and edit the uEnv.ini file to set the name of the dtb file to use.

put the A95MAX_boot.img on SD card, use any SD/USB writing app (even ours, you can drag/drop any .img file no the GUI and we'll use it.

put the AMLG12 on a USB stick.

If you're lucky it will boot u-boot from SD and then search/find the LE boot files on the USB.

The "G12A:BL:0253b8:61aa2d;FEAT:F0F831B0:12020;POC:F;RCY:0;EMMC:0" stuff means no bootloader on eMMC. It's actually a better position to be in than having the wrong bootloader (as then you're in pin-shorting territory). If you put A95XMAX_boot.img on an SD card it will boot from the card and start looking for something to boot. If the u-boot environment contains the usual Amlogic bsp garbage it will look for some "autoscript" files or boot.ini or boot.scr .. so I would start with putting LibreELEC-AMLG12.arm-9.80.0-box.img.gz on a USB stick, setting a dtb name in uEnv.ini - pick another G12A device like X96max or U200. If you're lucky it will find the USB and boot, and tthe UART will then give you access to an OS and console where you have more tools to play with. I suck at figuring out all the sector counts, but as a minimum you can then "dd" the A95XMAX_boot.img back to the emmc device, and then you can probably run LE or other distro's from an SD card.

Enable authentication on the LE samba server, set a credential, then use the credential on the Win10 side.

Interface naming is determined by kernel hardware probing order. As a broad rule "internal" hardware normally probes first, but it's not guaranteed, so if the USB device is probed first it will be wlan0, and the internal becomes wlan1, etc.

WiFi has nothing to do with Kodi.

Do a couple of reboots and see if the MAC address of the wlan0 (USB) interface changes with each boot?

Turn the volume up and it will un-mute. Worst case, SSH into the devices and type "kodi-remote" for a simple keyboard remote.

Use the USB/SD creator to write the image to an SD card, put the card in the box, boot from SD card - ISTR the WeTek devices use the power key on the remote to toggle between Android and LE/OE boot modes when pressed during the boot sequence.

Best solution (being serious) is to plug the Ethernet cable back in. RPi wireless isn't the best.

No idea, but it's simple enough to try, isn't it.

There are some logical milestones to complete before we can give a definite yes, but current intent is to resume Amlogic support in LE10. One thing that I can confirm though, there will be no "updates" from older releases. Users will need to clean install due to changes to boot process.

There are Milhouse RPI4 images now, but I'm not aware of any eureka moments on HBR audio. It is being worked on tho..

An official recommendation to anyone reading the ^ above procedure is: Do not upgrade from old OE installs. Back-up the essential things like sources and database files, but then do a clean install of LE instead of cross-grading, followed by a restore of the few things you copied. You will end up with a cleaner and leaner install, and will have a 512MB boot partition so you won't need to resize partitions at some future point.

Do you have 4K60 media? .. because 99% of people do not, and forcing it in config.txt results in higher power draw and other things. As nearly all 4K media is under 4K30 there is really no need to activate it.

I can't see anything wrong. The Intel driver is loaded, firmware loads, there are other signs that the card is up/running.

Build an LE image and then edit project/RPi/devices/RPi4/linux/linux.arm.conf (for RPi4, others in similar folders) and then rebuild the image, it will only rebuild the kernel with your changes. If you truly need/want to edit the defconfig it can be done by navigating to the linux build folder, which will be somewhere like build.LibreELEC-RPi4.arm-<version>/build/linux-<string>/ and then doing "ARCH=arm make menuconfig" to edit the existing .config file in the folder, then copy the .config to project/RPi/devices/RPi4/linux/linux.arm.conf and rebuild the image.