Posts by chewitt

    According to https://cateee.net/lkddb/web-lkddb/ASUS_WMI.html CONFIG_ASUS_WMI=m depends on CONFIG_HOTPLUG_PCI=y which you are not defining so the option is removed (unset) when the defconfig is saved.

    The patch below resulted in it being built:

    You probably don't need these:

    Code
    CONFIG_SENSORS_ASUS_EC=m
    CONFIG_ASUS_LAPTOP=m
    CONFIG_ASUS_WIRELESS=m

    Wondering if there'll be any support for this going forward.

    The C5 requires downstream vendor u-boot/kernel and amcodec support being hacked back into Kodi, so it will be possible to create an image if that's your thing. CE will probably offer support, but not LE, as we long moved away from that kind of horrid.

    Do you have Kodi settings in basic mode? - the option to configure audio to a different HDMI connection from the video connection is hidden in basic mode, but visible in advanced/expert mode.

    To boot LE you need:

    a) Bootloader installed to the disk. Can be syslinux or Grub2 or whatever you are using for the multi-boot; with a configuration file somewhere (as defined by the needs of that bootloader) that creates an LE item and tells it where the KERNEL and SYSTEM files are to be found.

    b) Boot files partition containing KERNEL and SYSTEM. Can be VFAT or EXT4 and 512MB or 1GB sized.

    c) Storage partition. Must be EXT4 and whatever size you like for your needs. No files required as the OS will populate anything it needs on /storage on first boot.

    The complicated bit is A and we don't support multi-boot setups because it's a pain in the rear to figure out what's needed and then support the resulting mess and inevitable deletion of Windows + Music Collection + Photo's of kids that happens when things aren't done right. When we say not supported we mean "we are not even remotely interested in touching that problem" so you really do need to go figure out that bit for yourself.

    The GBM/V4L2 video pipeline is completely different to the previous method used with RPi boards so the approach also needs to be different and zero-copy rendering brings inherent problems for the ambilight use-case. The same issue also exists with Allwinner, Amlogic, and Rockchip devices that use the same DRM framework in the same way.

    lrusak did some initial work on screenshot support a couple of years ago: https://github.com/xbmc/xbmc/pull/18741 but IIRC this had a problem level of impact on rendering and the effort stalled. It might be acceptable to resurrenct that for the kind of ad-hoc screenshot usage but IIRC it's the wrong approach for 60fps video.

    Our advice is (and has been since LE10) that people wanting to use Ambilight should use an HDMI grabber device. It's not as cheap as past methods, but it's simple and works everywhere.

    The error message itself is misleading and wireless being wireless there's a large number of potential variables including poor signal which RPi boards are inherently prone to. Over time things seem to have generally improved though, and you're the first person flagging an issue in this forumn for some time.

    LE13 nightlies are running newer kernels and lots of other bits. Perhaps make a test install on a spare SD card and see if that helps.

    Needs https://github.com/LibreELEC/LibreELEC.tv/pull/7864 to be merged as a basic step. Also needs upstream kernel developers to finish writing all the drivers because AFAIK that SoC type is still missing a ton of things. If you've been using it for a while already I assume you are either using some kind of vendor kernel (which we won't use on principe) or it's a desktop distro release missing a bunch of media functionality.

    ideally by extracting the ISO file to its own partition (as recommended for Google TV)

    Good luck with that. We don't ship an ISO image; never have and never will.

    I would find it better if I create 2 empty partitions and copiedthe required files from the ISO into them

    Assuming you mean the .img file (not .iso) then you are thinking in the right direction. No need to clone anything. Just copy KERNEL and SYSTEM to a dedicated LE boot partition and create whatever bootloader entries are required for whatever bootloader you are using; crib the general content from syslinux.cfg. Note that the boot partition can be VFAT or EXT4 but the /storage partition MUST be EXT4 to support Linux permissions. Also note that we do not provide support for multi-boot configurations.