Sorry, i have renamed this DTB file:
Ayayay .... 
Try this dtb on T4. You can rename it for yourself as convenient . I am interested to start LE and Armbian.
Posts by balbes150
-
-
I downloaded the image Recalbox on your link. It has only a single DTB file with name (rk3399-rockpro64.dtb). Where did you the file with name (rk3399-nanopc-t4.dtb) ?
-
The desktop works up to 1920x1024x60Hz.
Good
I just can't get WiFi to work right away. I have to look at the logs again and get back to you.
Perhaps for WiFi need add firmware, by default there minimal set of firmware.
it will be useful to check the installation of a media script that includes HW on Armbian and allows you to watch any video in full screen.
[Development] RK3399 media script - Rockchip 3399 - Armbian forum
-
Hi
What is exactly the file you are using (copying) from the image Recalbox ? I need the full name of the DTB file used. If running Armbian happens, you can try to perform the initial configuration. If you took a desktop image, you need to log in to the console as "root" with the password 1234, change the password, create a new user, set the password and see if the graphical desktop shell will start.
-
Thank you balbes, I took that spi and flashed it on sd card, but it doesn't happen
Write more about what and how you do it.
On my N2 all good starts and runs.
-
1. You can specify the name of the DTB file are you using from the image Recalbox ?
2. You can perform a simple test of image is running Armbian
https://yadi.sk/d/tpeis4lvlmgtvq
(I'm interested in two things, will it work booting u-boot on a T4 and what DTB from the image Armbian will have better hardware support T4) ?
-
LibreELEC-AMLG12.arm-9.80-devel-20190913121812-60568a1-odroid-n2.img on Odroid n2 has an green overlay, after reboot over splasscreen and the menu.
For the LE to work properly on the N2, I recommend using the SPI startup mode (in this case, all colors work correctly and you can use USB media to start the system quickly). I've put together a new version of SPIboot that properly supports starting from all media (SD USB eMMC PXE, the startup order can be easily changed to your liking or add new options like NFS). For quick tests, a USB drive is best (you can use any USB stick >=2 GB USB 2.0 or USB 3.0). For example, you can post in the eMMC system Armbian and quickly run the LE from the USB stick (or Vice versa , in LE eMMC, Armbian on USB 3.0). The speed of the system from a fast USB 3.0 medium is significantly higher than eMMC. Step updates on new SPIboot can be seen here.
https://forum.armbian.com/topic/9789-bring-up-for-odroid-n2-meson-g12b/?do=findcomment&comment=86377
-
Did a quick test with the 20190916 image. Still doesn't boot - had to manually dd u-boot for it to work.
You can check these two files, what will the startup work with (if possible, show the output of the UART console with both options) ?
-
Hello Balbes150,
Both Images for Nanopi-K2 won't boot on freshly burned SD: 20191010 and 20190911.
I've looked at your Github and it appears that the extra steps required to get u-boot working on the NanoPi K2 is missing in the latest builds. Copied from the u-boot readme for this boot, these steps are:
Check the last option (20190916) to run from Sd card on nanopi-k2.
While you're at it, could you please test if playing DRM content works on your builds (any device and not just the NanoPi K2)? As mentioned in my earlier post, so far I've had no success and I'm not sure if it's your images that's not working, or it's the InputStream Adaptive add-on / libwidevine that's not compatible.. You can test with the Video Test Streams Add-on by Matt Huisman (choose "Input Stream Adaptive - Dash with Widevine").
Alas, I have no opportunity and time for such checks.
-
New look with KODI-19. Please note, this is the first trial version and many things may not work.
Both Images for Nanopi-K2 won't boot on freshly burned SD: 20191010 and 20190911.
To check the reasons I don't post the image for nanopi-k2. Can you specify the exact version of the image (full name) that runs from the SD card ?
hi my beelink gt1 mini a no boot in all virsions
I checked on the Beelink GT1 mini. Everything works, including WiFi. Follow the instructions exactly.
-
New image 20190910 .
KODI 18.4,
kernel 5.3.0-rc8 (with all DVB modules available in this kernel enabled).
-
I got Fran 's message by mail before it was deleted. I understand it can be annoying to read messages that appear to be repetitive and inflammatory.
I think it's more due to a non native speaker having problems expressing himself, but in any case it's not spam and removing it as such only reinforces the view expressed in said message.
1. I'm not interested in" opinions " about which system is better or worse. Want to discuss it - create your own theme.
2. I'm not interested in advertising other systems. Want to discuss it - create your own theme.
3. I'm not going to persuade anyone to use any system. Everyone decides what to use.
I tried different DTBs but the wired still wouldn't work.....F2 S905X2 box...
Write in detail how you configured DTB. What systems have you previously run on your device ?
However, Windows Security reported that there is a Trojan "Spursint.F!cl" in the tar file.
Wow, did Windows learn to read the Linux tar format and understand its contents ????
-
Version update 20190902.
KODI 18.4.
Add graphic (via LE menu settings - eMMC) control power on\off mode cyclic run LE and Android from eMMC when running from external media (no need to pull media when you reboot into Android).
-
s905x2 box, wired doesn't work, wireless works sporadically then totally drops off the network...
On s905x2 there are two wired network options, for proper operation you need to use the correct DTB.
-
So actually in order to launch LE from the Amlogic boxes, I need to update the internal Uboot first?
Yes. Even if you have the LE starting, it does not guarantee proper operation.
-
I normally run CE but while ago I made some tests regarding the ethernet support in mainline LE release and I am planning to continue on this as soon as I have some spare time. At that time if coming from CE on SD, it was enough to reboot in android and redo one of the "boot from SD" methods (Reboot update, toothpick or whatever) to boot LE from the SD card (and again the same to eventually reboot in CE).
Now you write that it is required to restore the standard firmware. Are you talking about CE installed to internal, or it really affect any device that are currently booting CE from SD (and or USB)?
Coreelec are using an outdated and not compatible with other new systems technology run from external media. No matter what you have in eMMC. If you are running coreelec from external media, then your eMMC has an old version of multi-boot that is not compatible with the new systems. No new system can run properly on your device anymore.
-
The new version 20190821
just wanted to test new Image on nanopi-k2. As for older Images (since June) Nanopi won't boot. Unfortunately my Computer crashed, so I am not able to do an update from May Image (not longer on my Computer or yandex). Is it possible to upload an May Image (before 16.05) on yandex, so that I can make further Tests with update Images? Thanks for your kindness.
Try the new version, there should be a fixed startup
If we will have a version with DTV, when will it be available?
I have no equipment with DTV, I am not engaged in development of this direction. As far as I know afl1 has sent a patch to the main kernel, I don't know when its patch will be in the main kernel.
Can you elaborate more on this? Some times ago it was just enough to restart in Android and do again the "reboot update" (or other methods)
I don't understand your question. Write in detail what you want to know.
For those who want to run a regular Android without disabling external media with LE. I put together a test script to run s905_autoscript, which , if there is an empty boot_android file on the external media in the FAT section , will run both systems (LE and Android) in turn on reboot. Please note that this version of the launch is only the primary layout and may not work correctly. For use. Download the script and replace it with the existing file in the image. To create to patition FAT (/boot) the empty file boot_android. The first time you run the new script, Android will be launched. When rebooting, one of the systems will be started in turn.
https://github.com/150balbes/amlogic_s905/tree/master/script/s9xxx_mainline/le_v01
-
For all.
1. Everyone chooses for himself what systems to use it. No one is forcing you to use LE.
2. The launch system in Coreelec is not compatible with LibreELECE and Armbian. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems.
