LibreELEC for Khadas EDGE (RK3399)

microdude · June 22, 2019, 4:03am

Sure @Frank - I’ve written a bit about it above, but I will try to summarize. I’m using the Edge-V platform.

When I run the Edge_Ubuntu-server-bionic_Linux-4.4_arm64_SD-USB_V20181115.img image which I found on the Khadas website, everything works just fine. I have no issues with this image that I’ve found.

However, when I try to run any LibreELEC image or the newer Armbian images provided by @balbes150, I have such terrible network performance (both WiFi and Ethernet) that it is effectively unusable. I get ~50% packet loss and erratic ping times; if I run a command over SSH with a lot of output it ends up hanging SSH and eventually disconnecting before outputting everything. Specifically I’ve had trouble with these images:

Armbian_5.88_Rk3399-tv_Ubuntu_bionic_default_4.4.154_20190612.img
Armbian_5.88_Rk3399-tv_Ubuntu_bionic_next_5.2.0-rc4-next-20190613.img
LibreELEC-RK3399.arm-9.1-devel-20190607091142-a41fdf1-khadas-edge.img
LibreELEC-KVIM.arm-9.0.2.img
LibreELEC-RK3399.aarch64-9.1-devel-20190606140016-a41fdf1-khadas-edge.img
LibreELEC-RK3399.arm-9.0-devel-20181219114346-cc816a4-khadas-edge.img
LibreELEC-RK3399.arm-9.1-devel-20190607091142-a41fdf1-khadas-edge.img
LibreELEC-RK3399.arm-9.1-nightly-20190613-77b811b-khadas-edge.img

I’ve also tried stealing the .dtb file from the working Edge image and putting it on the others, which did help get NVMe to be recognized, but it did not fix the WiFi or Ethernet.

Edit: If you’re able to get it working, could you please let me know which image you used? Also, were you able to get any LibreELEC images working specifically? That is my end purpose, so ideally that would be the most helpful. Thank you for all the time and effort, it is very much appreciated!

Frank · June 22, 2019, 6:10am

Hi @microdude, LibreELEC-RK3399.aarch64-9.1-devel-20190606140016-a41fdf1-khadas-edge.img is the firmware which I used.
These are my test steps:
1.ping command

/ # ping www.baidu.com
PING www.baidu.com (14.215.177.38): 56 data bytes
64 bytes from 14.215.177.38: seq=0 ttl=54 time=8.278 ms
64 bytes from 14.215.177.38: seq=1 ttl=54 time=8.453 ms
64 bytes from 14.215.177.38: seq=2 ttl=54 time=8.674 ms
64 bytes from 14.215.177.38: seq=3 ttl=54 time=8.223 ms

cd /media and wget http://cn.wordpress.org/wordpress-3.1-zh_CN.zip

wget http://cn.wordpress.org/wordpress-3.1-zh_CN.zip 
Connecting to cn.wordpress.org (198.143.164.252:80)
Connecting to cn.wordpress.org (198.143.164.252:443)
wordpress-3.1-zh_CN.  18% |*****                           |  607k  0:02:39 ETA

can you try my way ? Thanks.

balbes150 · June 22, 2019, 10:33am

Have you tried these images ? Show the contents of the file “/extlinux/extlinux.conf” with which you try the launch and test LE.

microdude · June 22, 2019, 5:13pm

@Frank I loaded the image LibreELEC-RK3399.aarch64-9.1-devel-20190606140016-a41fdf1-khadas-edge.img which only has rk3399-khadas-edge.dtb available on my Edge-V, which is set in extlinux.conf. I cannot access the console using CTRL+ALT+F3, and SSH is very difficult to use. In fact, this particularly time, I couldn’t even successfully launch a shell with SSH and half the time it wouldn’t prompt for a password. I tried at least 15 times. However, pinging from another system on my network I see lots of packet loss:

$ ping 192.168.0.234
PING 192.168.0.234 (192.168.0.234): 56 data bytes
64 bytes from 192.168.0.234: icmp_seq=0 ttl=64 time=1.265 ms
64 bytes from 192.168.0.234: icmp_seq=1 ttl=64 time=0.767 ms
64 bytes from 192.168.0.234: icmp_seq=2 ttl=64 time=0.768 ms
Request timeout for icmp_seq 3
64 bytes from 192.168.0.234: icmp_seq=4 ttl=64 time=0.444 ms
64 bytes from 192.168.0.234: icmp_seq=5 ttl=64 time=0.501 ms
64 bytes from 192.168.0.234: icmp_seq=6 ttl=64 time=0.810 ms
Request timeout for icmp_seq 7
64 bytes from 192.168.0.234: icmp_seq=8 ttl=64 time=0.568 ms
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
^C
--- 192.168.0.234 ping statistics ---
14 packets transmitted, 7 packets received, 50.0% packet loss
round-trip min/avg/max/stddev = 0.444/0.732/1.265/0.255 ms

Additionally, it took 3 times to boot successfully using this image. The first two times it had some weird stack trace message scrolling by too rapidly to read.

Moving on to @balbes150’s questions. Here is the extlinux.conf I was using:

LABEL LibreELEC
  LINUX /KERNEL
#  FDT /dtb/rk3399-rock-pi-4.dtb
  FDT /dtb/rk3399-khadas-edgev-linux.dtb
  APPEND boot=LABEL=LIBREELEC disk=LABEL=STORAGE quiet console=uart8250,mmio32,0xff1a0000 console=tty0 coherent_pool=2M

I have not previously tried the images you listed, so I’m trying them now.

Using image LibreELEC-RK3399.arm-9.1-devel-20190517110312-a41fdf1-khadas-edge.img and its default extlinux.conf I have the same problems with the network. It also does not have an Edge-V specific DTB file to use.

Using image LibreELEC-RK3399.aarch64-9.1-devel-20190517102030-a41fdf1-khadas-edge.img, which also does not have an Edge-V specific DTB, I have the same network problems (50% packet loss, unusable SSH). However, by random chance, I was able to launch a shell via SSH and executed @Frank’s commands:

LibreELEC (community): devel-20190517102030-a41fdf1 (RK3399.aarch64)
LibreELEC:~ # ping www.baidu.com
PING www.baidu.com (104.193.88.123): 56 data bytes
64 bytes from 104.193.88.123: seq=1 ttl=52 time=45.488 ms
64 bytes from 104.193.88.123: seq=5 ttl=52 time=45.467 ms
64 bytes from 104.193.88.123: seq=8 ttl=52 time=45.141 ms
64 bytes from 104.193.88.123: seq=9 ttl=52 time=45.450 ms
64 bytes from 104.193.88.123: seq=13 ttl=52 time=45.323 ms
64 bytes from 104.193.88.123: seq=15 ttl=52 time=45.383 ms
64 bytes from 104.193.88.123: seq=17 ttl=52 time=45.271 ms
64 bytes from 104.193.88.123: seq=18 ttl=52 time=45.319 ms
64 bytes from 104.193.88.123: seq=19 ttl=52 time=45.308 ms
64 bytes from 104.193.88.123: seq=21 ttl=52 time=45.403 ms
64 bytes from 104.193.88.123: seq=23 ttl=52 time=45.429 ms
64 bytes from 104.193.88.123: seq=28 ttl=52 time=45.174 ms
64 bytes from 104.193.88.123: seq=29 ttl=52 time=45.586 ms
64 bytes from 104.193.88.123: seq=31 ttl=52 time=45.080 ms
64 bytes from 104.193.88.123: seq=32 ttl=52 time=45.273 ms
64 bytes from 104.193.88.123: seq=34 ttl=52 time=45.544 ms
^C
--- www.baidu.com ping statistics ---
35 packets transmitted, 16 packets received, 54% packet loss
round-trip min/avg/max = 45.080/45.352/45.586 ms

and:

LibreELEC:~ # cd /media
LibreELEC:/var/media # time wget http://cn.wordpress.org/wordpress-3.1-zh_CN.zip
Connecting to cn.wordpress.org (198.143.164.252:80)
Connecting to cn.wordpress.org (198.143.164.252:443)
wget: error getting response: Connection reset by peer
Command exited with non-zero status 1
real    1m 40.01s
user    0m 0.00s
sys     0m 0.00s

Note: All of my tests were performed using Ethernet. As mentioned previously, I’ve tried different cables, switches, WiFi, etc. and have the same issues reported. Furthermore, the same Ethernet cable, switches, ports, etc. work just fine using the Edge_Ubuntu-server-bionic_Linux-4.4_arm64_SD-USB_V20181115.img image.

balbes150 · June 22, 2019, 7:20pm

In the composition of the images LE no DTB files and there are no such settings file “extlinux.conf” default. What image are you trying to use ?

microdude · June 22, 2019, 8:56pm

The ones you linked have a “default”. When I burn the image there is a fat32 paritition labeled LIBREELEC with the dtb/ and extlinux/ directories. The extlinux/ directory has a file extlinux.conf and the contents are as follows:

$ cat extlinux/extlinux.conf
LABEL LibreELEC
  LINUX /KERNEL
#  FDT /dtb/rk3399-rock-pi-4.dtb
  FDT /dtb/rk3399-khadas-edge.dtb
  APPEND boot=LABEL=LIBREELEC disk=LABEL=STORAGE quiet console=uart8250,mmio32,0xff1a0000 console=tty0 coherent_pool=2M

This is from the image you posted, LibreELEC-RK3399.aarch64-9.1-devel-20190517102030-a41fdf1-khadas-edge.img

balbes150 · June 23, 2019, 7:26am

Can you test this image on EDGE-V (with the DTB that is the default in the image ) ? Immediately after the initial setup, enable SSH and check how the connection via SSH to EDGE-V. Also check the wired network (via SSH).

microdude · June 23, 2019, 2:58pm

Same problem

$ ping 192.168.0.234
PING 192.168.0.234 (192.168.0.234): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
64 bytes from 192.168.0.234: icmp_seq=3 ttl=64 time=0.577 ms
64 bytes from 192.168.0.234: icmp_seq=4 ttl=64 time=0.678 ms
64 bytes from 192.168.0.234: icmp_seq=5 ttl=64 time=0.624 ms
64 bytes from 192.168.0.234: icmp_seq=6 ttl=64 time=0.691 ms
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
64 bytes from 192.168.0.234: icmp_seq=11 ttl=64 time=0.761 ms
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
64 bytes from 192.168.0.234: icmp_seq=14 ttl=64 time=0.493 ms
64 bytes from 192.168.0.234: icmp_seq=15 ttl=64 time=0.597 ms
64 bytes from 192.168.0.234: icmp_seq=16 ttl=64 time=0.746 ms
64 bytes from 192.168.0.234: icmp_seq=17 ttl=64 time=0.804 ms
Request timeout for icmp_seq 18
64 bytes from 192.168.0.234: icmp_seq=19 ttl=64 time=0.707 ms
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
64 bytes from 192.168.0.234: icmp_seq=24 ttl=64 time=0.787 ms
^C
--- 192.168.0.234 ping statistics ---
25 packets transmitted, 11 packets received, 56.0% packet loss
round-trip min/avg/max/stddev = 0.493/0.679/0.804/0.093 ms

Also after the initial boot and filesystem re-size, when it tried rebooting I got two stack trace crashes. I had to remove power twice to get it to successfully boot. I was able to take a couple pictures, not sure if that helps:

Do I just have a bad Edge-V?

Gouwa · June 23, 2019, 3:53pm

Shouldn’t be

Can you have a try to upgrade the Android ROM

Thanks!

microdude · June 23, 2019, 4:13pm

I haven’t tried upgrading the Android ROM, but I did boot into the Android that came pre-loaded on the eMMC and the networking seemed fine.

balbes150 · June 23, 2019, 5:44pm

My previous post related to @Frank . Something he would have checked the network on instance of EDGE-V.

@microdude
The new version Armbian 5.89 DEV kernel compiled from source Khadas. Try networking with these images.

microdude · June 23, 2019, 11:39pm

I tried image Armbian_5.89_Rk3399-tv_Ubuntu_bionic_dev_4.4.167_desktop_20190623.img with extlinux.conf using:

  FDT /dtb/rockchip/rk3399-khadas-edgev-linux.dtb

Unfortunately Ethernet is still 52% packet loss and unusable. I also have the same problem reported in the Armbian thread where iwlist wlan0 scan reports wlan0 Interface doesn't support scanning.

Frank · June 24, 2019, 12:58am

Hi @balbes150, I will check it today.

Frank · June 24, 2019, 1:52am

Hi @balbes150, unable to connect via SSH with you image which you told me to check.which username you used with SSH.

Frank · June 24, 2019, 1:53am

Hi @microdude, I’ve also seen this problem. Just unplug your SD card and restart it.

microdude · June 24, 2019, 2:13am

Is that to fix the crashes on boot or the network problems? Do you have to install it to eMMC for that to work? I haven’t tried to install to eMMC yet because it’s been so problematic.

Also, the username on @balbes150’s image is root and password 1234.

Frank · June 24, 2019, 2:22am

Hi @microdude ,The password looks wrong, I am failed to connect.I check the network just now,it work fine.

balbes150 · June 24, 2019, 5:39am

What system are you checking ? Armbian SSH is enabled by default. In LE, you must first enable SSH in the settings, by default, SSH access is disabled.

Frank · June 24, 2019, 5:41am

Hi @balbes150 , I check in LE, I enable SSH Already. Can you tell me which user and password is right?

balbes150 · June 24, 2019, 5:49am

login root
passwd libreelec