The Slice DAC requires a device-tree overlay, but this is pre-configured in the LE 9.2.8 'Slice3' image, so what image are you trying to use?
Posts by chewitt
-
-
The AMLMX image is more POC than usable. Most of the boot workflow is still rough/broken or being discovered (more u-boot archaeology needed) but if you know enough about LE boot processes and have UART cables attached then it's not too hard to bodge something and get something booted. S802/S805 should get Kodi up. S812 will boot but 8/10 boots will result in CPU stalls (disabling CPU cores to make it a single core device solves that so but there's been no Eureka moment yet). There's also no vdec at the current time. Otherwise Linux 5.17-rc4 boots and generally things sort of work. You're welcome to play around with the image, but don't expect too much.
-
Put me on the list for wanting tftp support.
Mainline u-boot already supports it (all the Amlogic boards in kernel-ci boot that way) so you should be able to write u-boot to SPI and boot the device (replacing petitboot). I have no personal experience with it so can't guide you, but it should be do-able.
-
-
emveepee I did some test boots from an SD card yesterday using the image in my web-share (5.17-rc4 and u-boot 2022.01) and it worked fine from a boot perspective. I'd recommend getting an emmc module; they're faster and more reliable than SD cards.
-
Τα ελληνικά σου είναι καλύτερα από τα δικά μου ελληνικά
-
If there were changes, great work.
No changes in nightlies
-
Okay.. I dropped that from the USB-C addition patch. That patch is a placeholder at the moment as (according to Neil) there's a polarity issue not handled in the fusb302 code that prevents the driver from probing. It's greek to me, might mean more to you?
-
If media is scraped into a local library (sqlite) database you can query the database. If you Google sqlite3 and Kodi you will find queries on various forums and reddit that can give you the basics for exporting data. NB: It's easier to look in the GUI of course.
-
I'm assuming Janitor is an add-on? (never heard of it before). If yes, there is probably a user-support thread in the Kodi forums.
-
do i need to do a clean install of my box due to the above issue ?
You can update using the .tar file or clean install. Clean install is probably quickest.
-
I'm looking for ICC profile support and HDR to SDR mapping features.
I think Kodi and kernel have plumbing for ICC but the driver for tonemapping hasn't been written yet so that's not supported. Otherwise the image should work with the "box" image all S912 boxes are pretty similar.
-
I pushed an unclean set of images to the webserver by mistake where Kodi is built against python 3.8 but the OS has python 3.9 so Kodi fails to start. Those images have now been replaced with some corrected ones. The Python 3.9 change is fresh so I won't guarantee all add-ons have been published to the LE repo yet (the bump was in the last 24h). I have no interest in maintaining Matrix images as I have limited time for testing and Nexus better supports the Amlogic codebase.
I've test installed on a C2 and Ethernet works fine for me, see http://ix.io/3PBJ. The u-boot patch you found is still being included pstream, see https://github.com/chewitt/u-boot…ot.dtsi#L32-L36 - and the unknown boot command line is harmless, I'm not aware of any hardware issues with C2 other than the USB ports needing a hack to prevent the driver from autosuspending (which is in my kernel image).
-
I did a quick diff compare of the two Armbian patches and the first one you've linked is an early draft of Zero support based on a mix of the SEI510 and U200 device-trees. The second one looks like the final merged version which contains some differences to regulator naming and ensuring HDMI has power from boot.
G12A and G12B silicon has an mmc bug that requires a workaround/quirk, but that's in the g12-common dtsi so all devices will inherit it. The issue hits SDIO wifi in some older kernels but has been resolved upstream for a while now. See the history for drivers/mmc/host/meson-gx-mmc.c and note that I have some patches in my tree 5.16.y tree that are not upstream (the 270º patch is allegedly not needed but seems to benefit non-BCM modules like QCA9377).
NB: I have the impression that Armbian support for Amlogic isn't the best due to everyone on staff deliberately trying to look the other way and avoid the noise from unsupported "TV Box" users and board vendors not funding support. The net result seems to be a mixed bag of patches from various places and a generic defconfig. I respond to Q's when asked but I don't follow their development.
-
None of the Amlogic configs have it set by default but it shouldn't be an issue for LE images due to https://github.com/LibreELEC/Libr…otloader/config which is applied at build time.
-
Chewitt: Can u confirm that "Sync Playback to Display" works too with a PI 4?
I use it to playback 24p content @ 25p to match the 50hz Display Refresh Rate.
I don't use it so cannot comment. You'll have to experiment.
-
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?
-
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.
