Posts by chewitt

twilightened thread hijacking? .. and it's known, and will be solved once devs resume work in Jan, prob.

Quote from marg

I'm user of ODROID C2 - but it don't start my USBs Disk . The ports are quite 'dead' . The hdds dont event power ON.

It's a long-time known issue with the upstream kernel, see this thread: https://www.spinics.net/lists/linux-usb/msg214709.html - there is more follow-up since, but I can't seem to find the latest/follow-on thread at the moment.

EDIT: here it is: http://lists.infradead.org/pipermail/linu…ber/011098.html

If the current (hopefully temporary) issue with hardware decode is resolved I would like to resume releases for LE11 - there are still some bits missing but particularly with older GXBB/GXL/GXM hardware (which has less features to miss) it's more than usable.

I haven't seen much progress with internal DVB driver support. Availink are still tinkering with their demod driver, but most tuner drivers are out-of-tree and horrific code which will be a drag on attempts to upstream anything, and I'm not aware of anyone thinking about the missing V4L2 demux driver.

CE + TVH can work, and the IR situation is easily solved with some tape over the problem IR sensor once setup has been done. If not that, I'd go with the USB Hauppage route; their cards have well maintained upstream drivers so are low-drama.

If the module is already built and part of the LE image then the mostly likely issue is the device-tree file not containing any references to WiFi hardware; thus the chip is not probed-for and the driver not loaded. Running insmod won't do anything.

Kodi calls the kernel DRM APIs to perform modeset, so Kodi itself doesn't change the mode, the kenel does; it's an abstracted process.

You cannot switch resolutions like you can with xrandr (which doesn't work as we don't use X11) but you can force the intitial resolution used for boot by adding "video=HDMI-A-1:1920x1080M@60" to kernel boot params. On a Raspberry Pi this is in cmdline.txt in the root folder of the SD card. From SSH this is /flash/cmdline.txt but you will need to remount /flash in rw mode first to edit the file.

It helps. You'll find that our documentation on the build-system is rather light, which is a little deliberate. Our observation over the years is that the people who succeed at custom images and things built on our codebase generally look at the huge pile of prior-art the build-system represents and just get on with it. You'll find "git grep" is helpful for tracing variables and packages.

An older example of minimal config https://github.com/chewitt/LibreE…93ae1a9d2ff85e8

NB: Current record for a minimal image is 35MB for a functional Kodi + TVHeadend + screensaver image for WeTek Play 2 (also S905 like C2) but that required junking the entirety of systemd for a more minimal LinuxFromScratch and init based approach.

Add "video=HDMI-A-1:1920x1080M@60" to kernel boot params and reboot, it should force the defaults to 1080p@60.

Can I ask, what exactly are you going to try and build?

You guess incorrectly. LE uses libudfread, which is linked with libbluray.

We don't need to break the secure OS, only avoid it, since it's running long before LE/Linux gets started. LE should work with the vendor u-boot and the normal Amlogic recovery boot process. NB: If your goal is to run Armbian you're in the wrong forum. I don't run it often and am not that familiar with it (someone else's problem, so to speak).

You can write the AMLGX "box" image to an SD card (no flashing to internal storage, we don't support that) and experiment with different dtb names in uEnv.ini (edit the dtb to use, don't rename the dtb files). I can't really recommend a specific dtb to try; perhaps VIM1 since this has a complete dtb with features like Broadcom WiFi/BT enabled. The boot log shows the box has BL2 secure firmware, but that just means we need to exclude some additional memory areas (and we do, else we use them and crash the secure world OS). It's 1GB device so I would have low expectations for overall performance. LE images should support the keyboard without any issues. If you meant the remote, you will need to put it on the network and SSH in then follow https://wiki.libreelec.tv/configuration/…figuration-hard

Just use 'dd' to write the image.

LE is based on a cross-compile workflow where the buildsystem will download package sources, cache them, unpack them, apply local patches to the sources, and then build them. The package is then included into an image or update tar file by adding the package to the distro/project/device options config. It's possible to use local sources in the package folder but that's a bad habit, and some binaries you might be able to copy accross as-is from another distro, but it depends on how they were compiled (static or dynamic) and it's never guaranteed to work. There is intentionally no package install system in LE (other than the tools add-ons in the Kodi GUI) so to build on-device you'll have to delve into the world of Docker to have a build environment. As a rule its a lot easier to work in a VM on a desktop/laptop which has more grunt.

See documentation in https://github.com/LibreELEC/Libr…master/packages and go read the wiki sections on self-building..

htop already exists in the build-system, so you can either install the system-tools add-on package via the Kodi GUI (which contains htop) or you can add "htop" to extra packages in one of distribution/project/device 'options' files and it should be added to the default image.

sagittarius the Android boot log shows the box has RTL8822CS WiFi which is partially supported in the upstream rtw88 kernel driver (PCIe works, but not SDIO). I'm expecting to see some patches from MartinB and jernej on the linux-wireless mailing list in the new year though, as they have been collaborating on adding SDIO supprot. BT drivers are already upstream for a while but some device-tree fu is needed to get it working.

Use the "box" image (for anything booting from vendor u-boot) not the WP2 image (experimental mainline u-boot and wiped emmc).