Posts by chewitt

LE11 nightlies are the only images that will run on RPi02W hardware (without a lot of jumping through unsupported hoops) .. but you'll likely run into a bug that will stop Kodi from running in the latest nightlies. The issue is known, but needs some dev attention to fix, and the devs in question (from RPi Foundation) are on PTO at the moment. So be patient and wait a week and it should be resolved. NB: RPi02W only has 512MB RAM so while it can/will boot LE11 nightlies we have no plans to formally support it (or any other 512MB devices) as Kodi Matrix/Nexus really need 1GB.

ConnMan has no method for chosing which WLAN card the tether should run on, so you may need to blacklist driver modules to disable the internal card. Once that's done, it should work, as long as the driver for the USB card supports AP modes; most do, but not all <insert usual statement about garbage realtek drivers>.

If you spend $$ on faster SD cards you may be able to empirically measure a minor speed bump and it might boot marginally quicker, but in practical terms you will not notice any real-world difference in performance. Save goes for USB3 SSD drives; they are quicker in certain tests but you're unlikely to notice much difference (and you need to hang the drive out the back of the board, which is ugly).

SSH in and "journalctl | paste" after a clean boot, and share the URL so we can see what's not right. No logs = No problem

Your AVR may support S/PDIF input at 96KHz, but I'm not sure the box will support S/PDIF output over 44.1KHz.

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.