I've moved this into a separate thread so it's easier to track the discussion. Can you share diff patches or clearer instructions on what you've enabled or disabled for LZO?
Posts by chewitt
-
-
I tried to run the nightly for the N2 from SD card, but nothing happpens. I don't see a uEnv.ini file to edit either. I build the image from source and tried that too but same thing. Does this image only run from emmc? If is there a command way of building it to run from SD?
The odroid-n2 image includes mainline u-boot which uses FDTDIR in extlinux.conf (not FDT and dtb name or uEnv.ini) to auto-determine the correct dtb to use from hardware data read at boot time. I haven't tested a clean install from SD card that recently but the image should boot both SD and eMMC with no config required. NB: You need the SPI boot switch on the N2 set to the right. If set to left, petitboot will be active and it does not understand exlinux boot configs and the device will not boot. The latest image in my testing share is running fine on an N2+ (see http://ix.io/3Ps4) although the emmc module it's booting from might have an older u-boot installed.
-
Now there is fully supported Hardware Deinterlacing with a Raspberry PI 4 ?
So i can use it to watch PVR MPEG 2, 1080i Channels without any problems?
Correct.
-
I'll feign suprise
-
You would need to install original LE from an USB/SD image first, and then 'update' to the other image using the .tar file. However that image is old and probably buggy. So when it doesn't work, please don't come here expecting support
-
Best to ask the Allwinner devs. I have some Allwinner boards in my collection but they are mostly gathering dust.
-
Can anyone point me to a how-to for installing the LibrEelec builds on these boxes - my box appears to be an old Edal T95Z plus (2g RAM 16g ROM) and runs ok with the "gxm_q200_2g" device tree file
Get the AMLGX "box" image from https://test.libreelec.tv/ .. write to SD card and then edit uEnv.ini to set the dtb name (do not rename the dtb to dtb.img). Insert the SD card and trigger recovery boot again so the LE bootscripts are loaded (else you have CE scripts which look for different files). If all is well it will boot. The "meson-gxm-q200.dtb" device-tree exists and should support most hardware.
-
This is probably best reported via the Kodi forus. It's not an LE specific issue.
-
FQDNs are not supported, you MUST use an IP address.
-
See https://forum.kodi.tv/showthread.php…5119#pid3085119 .. perhaps scroll back a little in the thread.
-
You will need to reflash the module from a Windows PC connected via USB cable (and some drivers, which need to be insalled). There are instructions for flashing core modules on the Raspberry Pi Foundation website (old links on the FiveNinjas GitHub site are dead now). The website instructions will not mention Slice, but they apply to any CM/CM3 device.
-
Add "textmode" to kernel boot params in cmdline.txt and attach a USB keyboard. LE will boot to a console instead of Kodi so you can see the output on-screen and save logs to a USB drive or experiment with connmanctl to connect to networks. Use 'iw' to change regulatory domain if that's important. Once you've either got it working or obtained logs so we can investigate what the issue is .. share info.
Jocke.Sve LE has never used wpa_supplicant.conf files and there are no plans to add support (we plan to drop wpa_supplicant and switch to IWD at some point in the near or mid-term future).
-
Can we run Kodi 19 on the amlogic S912 boxes with any of the LE nightly build
Nightly images use Kodi Nexus (20) not Matrix (19). The images are not perfect but quite usable on S912 hardware as long as your media needs are not too exotic.
-
(whether they are pirated or not, who cares)
You might not care, but pirates are generally not welcome in this forum.
-
Connect an Ethernet cable for setup/investigation. NB: LE does not support/use wpa_supplicant.conf files.
-
Go look at the systemd .mount file samples in /storage/.config/system.d .. these are sequenced correctly during startup to mount things after the network comes up and before Kodi (and TVH add-ons) are started.
-
All I can say is .. it's not a software problem. It's about cables and physical connectivity.
-
If the box is running Kodi Helix (15.2) I suspect you have a Slice (CM1) device not Slice (CM3) as the CM3 board was launched some time after we forked LE from OE (the original SliceOS was based on OpenELEC) and it's around the time 5Ninjas ceased trading. The simple way to check is the RAM size. If it's 512MB it's CM1, and 1GB it's CM3.
Either way, the original SliceOS was installed via NOOBS, and if you have a working install you should be able to cross-grade from SliceOS to LE after placing the .tar file in /storage/.update, but I would stop Kodi first (systemctl stop kodi) and rename /storage/.kodi to /storage/.kodi-old to move existing data out of the way as it's a large version jump and it's worth spring cleaning at the same time.
