i have Minix Neo X7
how install in usb ?
It will not work with USB, only with an SD card (but there is no guarantee that your model is supported).
Posts by balbes150
-
-
Good news.
Working version of Libreelec for rk3188 (thanks to knaerzche for providing the source code). I tested it on my UT2 (rk3188). I wrote the image to the SD card, connected it to UT2, and the system automatically started. Works with HDMI audio and HW acceleration for video (not all formats are supported yet). My LAN hasn't worked yet. Important - now there is a working version of the kernel and u-boot for rk3188, I hope to build a version of Armbian with these sources in the near future.
Thank you to knaerzche for the work done to add support for rk3188 with a modern kernel and u-boot.
-
should it work on the wetek core also?
What's the chip on wetek core ?
-
-
Test version of LE-10 (KODI-19) with the 5.10 kernel from Martin.
Versions for s8xx are located in directories with the s8xx extension
KODI works well, the interface is fast even when starting the system from USB media. I didn't get the sound through either HDMI or analog 3.5, but I have a USB sound card for$ 2, with it the sound works fine (no video brakes). HW video does not work yet (this is understandable), but even in SW mode, the system works smoothly with 720p video and USB sound.
Great job Martin.
-
ver 20201216 kernel 5.10.1
-
After thinking a while, I believe I was in wrong way bridging LE and armbian with docker. When running container in docker, even in priviledged mode, there are limitations in container. My goal is not to containerize LE, but just to use kodi well prepared in armbian. So, I decide to simply chroot to LE fs, so that kodi can run with full compability as in host. If we want to put some restriction to it by using 'unshare' and 'runuser' commands.
I recommend that you try the latest versions of Buster-legacy-desktop Armbian + media script for Firefly Station P1 (rk3399) \ M1 (rk3328). In it, KODI and Rockchip Gst Player works with HW without any containers (including 4k). Details can be seen at the end of these topics.
rk3399
rk3328
-
After this commit N2 and N2+ use the same boot fips. I have separate odroid-n2 and odroiod-n2-plus folders only to stop people asking me "do the N2 files work on N2 plus?" .. the files in both folders are identical.
I don't have such equipment, I don't know if it works or not. That's why I don't release such images.
To all - ver 20201203
-
-
did you get a chance to look at the boot log in post #1,624 posted by cdu13a? I originally installed a chewitt build by mistake from a link in this topic, but subsequently tried one of your builds on my N2+ (not ordinary N2) which won't boot for me. I think your builds theoretically should be more likely to boot properly on the N2+ as they contain the boot.ini expected by the initial bootloader on the system.
Yes, I looked at the log. U-boot in my image is not suitable for direct launch in SD\eMMC mode for N2+. Need to build a different version of u-boot for your model. But I don't have an N2+ sample, so I'm sorry, I can't help you. The standard u-boot, which is in SPI, uses a clueless PITEBOOT that interferes with the direct execution of u-boot commands, so I doubt that you will be able to use my image in SPI mode (using boot.ini). For the N2 model (not plus), I created a special version of UbootSPI that allows you to run any system with USB \ SD\eMMC\LAN, but I think it will not work on N2+, need to create a special version for N2+.
-
chewitt is the official maintainer of AML, so its test images should be considered as "official" and discussed in the appropriate topic (which is specially created for such discussion). This topic only discusses images that I create. Please note that the official versions and my versions have a significant difference in the launch methods, settings, and functionality, so information about them should be placed in different topics (so as not to confuse users who try to use different images with incorrect configuration and management steps). We kindly ask everyone to correctly place your information in the appropriate topics, do not create unnecessary problems for others.
-
Have I any chances to use LE on RK3318 (TV box Magicsee M5 Nova)?
Sorry, I don't have that kind of support equipment.
-
The most recent images with extension eba do not boot, without boot.
I just can't get balbes150 N2 build (from Yandex folder) to boot on my N2+
I don't have such hardware, so without a detailed startup log from the UART console, I can't help you in any way.
-
Ver 20201121 kernel 5.10.0-rc4 mesa 20.3.0-rc2
-
Ver 20201122 kernel 5.10.0-rc4 mesa 20.3.0-rc2
-
Ver 20201120 kernel 5.9.9
-
Please note that the composition of images changes from the current date. Odroid N2 now uses its own separate image.
no aml_autoscript.zip
fix
add support for cvbs on the odroid n2
I don't have the testing equipment.
-
Ver 20201113 kernel 5.9.8 mesa 20.3.0-rc1
