Posts by chewitt

  • [x86-64] HDMI-CEC not working on Intel N100

    Update with https://chewitt.libreelec.tv/testing/LibreE…_64-12.80.2.tar and check/test again. I've enabled some more kernel modules; I'm intentionally doing them in bits to see which ones make a difference (or not). Also share the URL generated by "pastekodi" (run from the SSH console) after updating so I can see the system log.

    Information on IR remotes is here: https://wiki.libreelec.tv/configuration/ir-remotes but an RC6/MCE remote should basically work out of box. Worst case you might need to swap some buttons around via XML maps. If you have some other kind of remote you'll need to create a toml keymap (not hard to do).

    I'd advise against Amlogic purchases due to no LE support on anything recent. RPi5 is nice. Mine just has some standoffs fitted to the board with plastic bits top/bottom to give some basic protection. It sits in a cupboard out of sight though so appearance and protection aren't important, and I use a BT remote so line-of-sight with an IR remote isn't required (CEC is disabled in the AVR as I have too many CEC capable devices connected and this only causes problems).

  • [RPi3] WiFi Broken (Invalid Key)

    LE and RPiOS use the same kernels but RPiOS uses wpa_supplicant whereas LE uses iwd and the issue is proven to not occur when using wpa_supplicant. Reverting LE images to wpa_supplicant can be done but aren't going to entertain that idea as wpa_supplicant has its own set of very-legacy-code problems and the Linux community is keen to iwd mature and replace it. Signal strength is the most important factor as poor signal introduces all kinds of errors and iwd is probably not handling all of them as gracefully as it needs to; although a specific issue with WPA3 on Broadcom cards (which RPi boards use) was resolved and things have generally improved to the point where invalid-key is rarely reported now.

    Cables are always best. External dongles or anything with a proper antenna beats the RPi on-board one.

  • enable asus wmi and asus nb wmi in kernel

    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

  • [Odroid-C5] LibreELEC Support?

    Quote from iyah

    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.

  • Nightly update issue on Generic/Legacy – only one update visible after switching to test channel?

    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.

  • Feature Request: Enable Writeback or Scanout Access on Raspberry Pi 5 (VC6)

    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.

  • [RPi3] WiFi Broken (Invalid Key)

    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.