Posts by chewitt

  • Official LE11 Test Images for Amlogic (Kodi-20)

    I'm effectively on hiatus; currently focussed on a new job and preparing for an Ironman triathlon later in the year. There is allegedly someone working on the hardware decoders (funded work from an LE friendly board manufacturer) so if/when that ever results in some interesting code to test in a public repo I'll think about resuming. Until then nightlies should have K21 alpha code and aarch64 kernels.

  • How to undo rm

    If LE was a normal Linux distro you could install testdisk or ddrescue (data recovery tools) but we're not and the amount of "Jumping through hoops" required to work around our packaging limitations will be more effort than re-ripping the movie from original media.

  • Wetek Play, what to do with it?

    1. Forget it, there is zero modern Linux support for Meson 6 hardware and no modern distro's support booting 3.10 vendor kernels from 2013 (that were already dated in 2015 when it launched and killed OpenELEC).

    2. It's detected during boot and thus prevents other box vendors shipping product that used the WeTek OS. You can remove it, but then the box won't boot and there's no modern u-boot alternative.

    3. You can run LE 9.2.8 via dtech images, but that's the end of the line for the box, and K18 is on the traliing edge of add-on compatibility these days (not that most authors switched their focus to Python3 based add-ons used from K19 onwards).

    4. Only crazy debugging..

    4. Put LE 9.2.8 on it with TVHeadend server and then use a newer client device to watch TV from it .. or use it with LE 9.2.8 to watch stuff on the same box .. or bin it, there's really isn't anything else it's good for (too slow for retro gaming).

  • USB won't boot

    Quote from account001

    I would be grateful if you tell me what I'm doing wrong.

    Two things:

    a) You hijacked someone else's thread to make a post about a different issue.

    b) Your post is about a distro that I've never booted (and is not LibreELEC).

    In summary: You're seeking help from the wrong person in the wrong forum.

    Удачи /shrug

  • Cheap X96A tv Box

    Use the AMLGX "box" image with meson-gxl-s905w-p281.dtb or meson-gxl-s905w-tx3-mini.dtb defined in uEnv.ini .. P281 is an S905W, which is a cost-engineered S905X. It will be limited to 1080p in LE.

  • Wetek play 2 build

    WP2 will boot from Android/WeOS using the "box" image or if you overwrite WeOS, using the WP2 board image. All has been written in the wiki docs. Kodi will output the GUI at 1080p max (hard silicon limit) but video can be ouput at 4K with caveats: upstream code for S905 only supports 4K with 8-bit HEVC; because S905 doesn't support 10-bit, 4K H264 was never implemented in upstream drivers, and there is currently no HDR>SDR conversion. I would position any S905 device as 1080p max; you might find some content works at 4K, but most 4K media these days is HEVC/10-bit/HDR so it won't output or look right.

  • Beelink GT1 Ultimate w/o eMMC

    You'll probably need to make a custom LE "board" image that uses https://github.com/LibreELEC/amlo…ter/beelink-gt1 so the board is using the correct FIP sources for upstream u-boot support. Those are extracted (by me) from the original Beelink u-boot sources. This will also allow you to boot u-boot with the correct board dts. Use the GT1 (non-ultimate) dts in extlinux.conf as this supports the QCA9337 wifi chip; the ultimate dts expects a Broadcom device.

  • Cloned partition doesn't boot

    Create a backup of the old system. Make a new clean install and then restore the backup or simply mount the old drive and copy/sync the data over as needed. It's usually a faster and more reliable approach since by-design you start out with a working new install.

  • Minix U9-H freeze on kodi loading page / black screen

    The 1GB size of the card is not important. What does matter is that it's an older and slower card. Modern high speed cards use different voltages and if that part of setup isn't handled correctly within u-boot the SD card won't be detected when the kernel loads. The older card does not support the higher-speed modes and thus sidesteps the issue. Depending on your perspective this is either vendor u-boot failing to setup the card correctly, or the kernel mmc drivers failing to handle the state u-boot put the card in. I'm in the blame u-boot camp since the Amlogic code quality isn't brilliant. It's all been hacked to work togther.. and we're not using one half of the hackfest.

    I have zero interest in trying to investigate or improve compat with some random Android ROM that people have loaded. Reverting back to the factory image seems to be the pre-requisite.

  • HDMI on MEELO UNO2

    Code
    ------------ /sys/devices/virtual/amhdmitx/amhdmitx0/rawedid ------------
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

    ^ That from the CE dump confirms that there is bad (zero) EDID data on the HDMI connection. The difference between the vendor kernel and mainline is that the vendor kernel includes a bunch of forced defaults which allow things to work. The upstream kernel doesn't, so there is no active video or audio connection. If you've tried other cables and TVs then I'd guess something got damaged in the HDMI socket.

    The one thing you can try is configuring the box to use an edid.bin file, and substitute the edid.bin captured from another device.

  • HDMI on MEELO UNO2

    Code
    edid-decode /sys/devices/platform/soc/d0100000.vpu/drm/card0/card0-HDMI-A-1/edid | paste

    Remove the override from uEnv.ini and reboot, then run ^ that and share the URL please. If the output from the main command is null, you need to check the HDMI cables and connection (unplug and change cable, use a different port on the TV etc.) .. as that's the single most likely cause of not seeing EDID data.