Posts by chewitt

  • LibreELEC & Windows 11 Dual Boot?

    The issue with BIOS selection is both drives are permanently connected so you have to enter the BIOS boot menu to switch, whereas with a removable SD card device it can be preferred over the HDD only when connected. The SSD will give a decent I/O performance advantage unless it's a rubbish one. So really you need to configure a bootloader capable of working with both OS.

  • LibreELEC & Windows 11 Dual Boot?

    The project does not support dual-boot configurations; it's always a complete pain in the rear to setup and future Windows updates are likely to break whatever fragile arrangement you come up with. There are some threads in the forum which describe the seqence of fiddling that worked for some other users if you search for them, but I wouldn't expect too much sympathy or help from staff, as we're all volunteers giving up free time and we prefer fun stuff on Linux not purgatory on Windows :)

  • X264: 1080p videos with 16 Reference Frames will not play in DRM PRIME

    Code
    2024-02-27 08:12:23.466 T:553      INFO <general>: Starting Kodi (19.5 (19.5.0) Git:19.5-Matrix). Platform: Linux ARM 32-bit
2024-02-27 08:12:23.466 T:553      INFO <general>: Using Release Kodi x32
2024-02-27 08:12:23.466 T:553      INFO <general>: Kodi compiled 2023-01-07 by GCC 10.2.0 for Linux ARM 32-bit version 5.10.110 (330350)
2024-02-27 08:12:23.466 T:553      INFO <general>: Running on BCM2835 with LibreELEC (official): 10.0.4, kernel: Linux ARM 32-bit version 5.10.110
2024-02-27 08:12:23.466 T:553      INFO <general>: FFmpeg version/source: 4.3.2-Kodi

    The non-working file plays fine here, but RPi5 doesn't support H264 H/W decode and ffmpeg is software decoding the file. Please retest with a current LE12 nightly and run "pastekodi" and share the URL.

  • /dev/sda: unrecognised disk label

    Was the drive formatted (anything would be good) before trying to install?

    Perhaps try booting from an Ubuntu USB and use 'dd' to directly write the LE image to the 1TB drive, then interrupt boot and type "run" to run from USB (or in your case HDD) instead of starting the installer.

  • Docker Swarms, vxlan kernel module

    It looks like Amlogic (and RPi 0/1) are the only kernels we ship that don't have VXLAN support enabled. That can be changed.

  • Using a RTL8812AUUSB WiFi dongle instead of built-in WiFi adaptor on RPI4

    Code
    mount -o remount,rw /flash
echo "# disable wifi" >> /flash/config.txt
echo "dtoverlay=disable-wifi" >> /flash/config.txt
mount -o remount,ro /flash
reboot

    There are several options, but that ^ will disable the onboard WiFi in device-tree allowing the USB external dongle to appear as wlan0 instead of wlan1. The RTL8812AU should work out of box, but like all downstream Realtek drivers, there's no guarantee.

  • Wetek Play 2 can boot LE9 from SDcard without eMMC?

    The UART output at least confirms the box finds nothing to boot, which is a much better starting point for recovery activities than when u-boot is broken/half-working. And the upstream u-boot binaries in my testing share have no knowledge of boot files like kernel.img and dtb.img so it won't find and use them. However I'm wondering what happens if you simply rename stuff to files that it does know about?

    For kicks, create an SD card from the LE12 image for WP2 in my testing share and delete everything except the extlinux/extlinux.conf folder/file. Then copy kernel.img file from the 9.2.8 image (rename to KERNEL) and the SYSTEM file (leave as-is) and then dtb.img (rename to meson-gxbb-wetek-play2.dtb) and see what happens when it tries to boot (share the UART output and/or dmesg should it make it that far). I'll be surprised if it works, but you have nothing to loose.

  • Wetek Play 2 can boot LE9 from SDcard without eMMC?

    Random guessing: image this to an SD card: https://github.com/LibreELEC/Libr…/bootloader.img

    Then write the LE 9.2.8 image to a USB stick, connect both SD and USB devices, boot and see what happens. If you're lucky it will find u-boot on the SD card, boot it, and then u-boot will find the LE 9.2 image on USB and boot the LE kernel.

    If that doesn't work, try the process again with https://github.com/LibreELEC/Libr…es/recovery.img written to the SD card instead.

    If you can connect the serial UART cable to the board to literally 'see' the boot process it will help you (else you are blind to what actually happens). WeTek did ship one with the box.

    The primary challenge you have is that S905 boards look for a signed boot header in different locations on SD/USB and eMMC boot media, hence an image of the factory Android image on eMMC (which we have) will not boot from SD as the SoC cannot find the signature. The LE 9.2.8 image does not include u-boot at all as LE relies on the factory u-boot being installed to eMMC. The LE12 image boots as this does include u-boot and the .img is specially built to have the signed boot header in both eMMC and SD/USB locations; but I doubt modern u-boot can boot the legacy images (have never tried). In theory it's possible to create your own Amlogic u-boot binary then sign it using the FIP sources in https://github.com/LibreELEC/amlo…ter/wetek-play2 .. but there's no guides for that kind of thing.