New image 20200821 kernel 5.7.16
Posts by balbes150
-
-
I've downloaded this version, do I still need to do the uboot replacement thing or is this supposed to be a standalone version? (If it's meant to be standalone it doesn't boot, it worked similarly to the previous version when I did the u-boot replacement with the armbian bullseye u-boot (as in it works but there are issues with the sound).
Also, just to note, I have the M4v2 not just the M4 (not sure if this makes much difference?)
Try the latest version at this link. You need to check the startup without adding U-boot (I need to understand whether the u-boot from the LE build works or not). Write down which DTB you are using and describe the sound problem in more detail (what settings are specified in KODI for sound).
-
I hadn't realised this, I was using the Armbian .DTB will have a play with the other ones (I didn't see a specific M4V2 version?)
I added images for NanoPI M4 and ROC-PC (Renegade Elite) to the 20200815-aarch64 on my site. Can you check the overall image launch for M4 ? I am interested in the work of u-boot (so that the system would start) and the General work of DTB from the image.
-
put the .dtb in the folder
I don't know which videos you run, but on all the rk3399 I have, almost all the videos work. You should only use DTB from the LE image. Only u-boot is used from Armbian.
-
I've managed to get things sort of working on NanoPi M4v2 using Armbian Bullseye as the base and the LibreELEC
Write more about what you launched and how.
I think the BBC thing is something to do with Python (I grabbed the zip from git and it gave an error about python version)?
With questions about Addons, you need to contact their developers, I don't know how they work and what the problem is.
to all
New image 20200813 kernel 5.7.15
-
Ver 20200813 kernel 5.7.15
-
I am wondering why does latest version of armbian have so many problems. Like wifi not working
What problems do you write about ? I have everything working in Armbian on T4, including WiFi And analog audio via 3.5.
Then I can successfully launch Kodi with docker.
Why do we need these perversions with Docer, if there is a LE in which KODI works in full mode ?
The first is the resolution seems to be limited to 1920x1080 but the RockPro64 should be able to display 4k.
I don't have RockPro64, but on NanoPC T4 and RockPI 4, 4K works.
-
Update version 20200810 with kernel 5.7.14.
for 3288 added the ability to install in eMMC (via GUI).
-
Frist-I changed the image to Telos, same issue,with Wifi not connected..
If I understand correctly, you are trying to use DTB from the Telos model for Meta. It won't help , they have different equipment.
'When I write the image to emmc, it appear to write successfully, when I removed the SD Card, the system will not boot to LE, the power is on the box but there is no Tronsmart start up logo the screen was just black. I reflash back to Tronsmart Android firmware, then went through the process of emmc, same issue the system will not boot from emmc.
Any suggestions to make it boot from emmc.
The S905 models have a very old u-boot. It does not support installing the system in eMMC. There is only one workaround: install Armbian with u-boot replacement and then install LE. But replacing u-boot to limit the size of RAM used, you will only use 1Gb.
-
I was able to burn "LibreELEC-ARMv8.aarch64-9.80-devel-20200720113414-38e34a4-amlgx.img" into a SD card, however, the image can connect to wire networks, but not to the wifi ,my box image is "meson-gxbb-vega-s95-meta"
Any suggestions to make the system connect at least I can get log report.
I checked the image on Telos, WiFi works. It is possible that Meta uses a different chip or needs different firmware. What is in eMMC ? What other systems have you run previously on this model ? Try running Armbian and checking the WiFi (it uses different settings and firmware).
It worth mention that I installed balbes150 SPI boot 20191003/spiboot.img. Should I use different one SPI?
When you set the switch to SD\eMMC, SPIboot is not used in any way and does not affect the launch from the SD card. If you have eMMC with u-boot, the SD card will not start.
-
Version 20200720 for rk3328\3399 and rk3288.
Kernel 5.7.9.
to quickly test the performance of audio and video , a small test video clip has been added to the images. To start, need to add the source to "Videos" (Root filesystem / usr/config/test). And a test clip will be available. This allows you to quickly check the overall performance of audio and video without having to connect external media or network devices (i.e. you can check audio\video, if there are problems with the network and access to network resources or media USB).
-
Ver 20200715 kernel 5.7.8
-
ver 20200710
kernel 5.7.8
-
New image kernel 5.7.6
-
Presently I am on Coreelec
Read carefully the first message of the topic.
-
To force SSH activation, add it to the text file (uEnv.txt) in the APPEND argument string at the end of "ssh".
APPEND=boot=LABEL=LIBREELEC disk=LABEL=STORAGE quiet console=ttyAML0,115200n8 console=tty0 systemd.debug_shell=ttyAML0 ssh
-
Where can I get this dtb? I have not been able to find a working link in this thread.
The version from this theme has full T4 support immediately without any additional settings. Including analog sound, WiFi, BT , installation in eMMC or on NVMe etc.
-
Display More
Latest version ,amlogic not work for me
LibreELEC (community) devel - xxxx
and rebboting every 1 minutes
I see that the uEnv structure (.txt no .ini) and entry have changed
version of this post Test LibreELEC images with KODI-19 for S9xxx
it worked properly now, it doesn't work anymore
(I checked the latest version and wanted to return to the previous version but none work)
Restore the regular firmware and perform a clean multi-boot activation. Right now, there is a piece of shits in your system that interferes with the normal operation of LE.
Among the listed DTB, I tried these five, in each occasion, the system write some scripts, but when it try to reboot, it get stuck at Libreelec Logo, hence it not launch to Kodi.
You need a clean installation in a clean system. This means that you need to restore the clean regular Android firmware to eMMC and activate a new multi-boot.
