LibreELEC for Khadas EDGE (RK3399)

[Frank]

HI @balbes150 , I check it just now.It work fine via SSH.It look like not problem.

[balbes150]

@Frank

I check it just now.It work fine via SSH.It look like not problem.

Do I understand correctly that you have checked the LE on the EDGE is V and the wired network works without problems ?

[Frank]

@balbes150 no problems.

[microdude]

So should I submit for a return or ??

[Frank]

@microdude, I can’t reproduce you problem,so I don’t know What’s the reason for that. Can you provide more information to me . Or check it again ? Maybe there’s something wrong with the cable itself ?

[microdude]

I’ve written quite extensively about my problems in this thread. I’ve tried:

• Many different images. The only one that works is Edge_Ubuntu-server-bionic_Linux-4.4_arm64_SD-USB_V20181115.img. The fact that this image works with Ethernet and the NVMe and I was able to transfer over 1TB of data successfully seems like it’s not the Edge-V.
• Different switches
• Different cables
• WiFi vs Ethernet
• Different microSD cards

They all have the same problem, but all work with that image. I can’t imagine it’s the Edge-V, but I’m at a loss if you’ve tried the LibreELEC image on an EDGE-V and it works for you.I don’t know what to do other than exchange it for a different one. If there is a diagnostic step you’d like me to take, please list the exact commands or steps and I’m happy to do so.

[Frank]

@microdude , Which version of EDGE-V do you use?

[microdude]

It is the Edge-V V13 1903 18 19

[Frank]

@microdude OK, I will check it in V13 again.

[Frank]

HIi @microdude ,I check it just now. The network does have problems when the V13 version runs LE.We are identifying the cause of the problem.It maybe need some times.

[Frank]

Hi @balbes150 . I check it with EDGE-V V13. I found some problems:

1. It failure to get the correct IP address. The right IP is 192.168.1.xxx,but it always be169.264.xxx.xxx.
2. I found it need long time to get the MAC address.
3. Sometimes If it fast access to MAC address, it will the IP address is right.And it wrok fine.

But , whether the firmware is Android or Ubuntu, It both work fine.And it just happened on EDGE-V V13.We try to use the DTB which is use for ubuntu to replace it . But the same result has emerged.Then we try to use another LE firmware , there has been no improvement.
We don’t have any idea with it .We try to solve it now .So, If you have any idea with it , you can tell us. Thanks. I am sorry that tell you no problem with it, I test in EDGE-V V12 at that time.

[balbes150]

@Frank

I check it with EDGE-V V13. I found some problems:

1. It failure to get the correct IP address. The right IP is 192.168.1.xxx ,but it always be 169.264.xxx.xxx .
2. I found it need long time to get the MAC address.
3. Sometimes If it fast access to MAC address, it will the IP address is right.And it wrok fine.

But , whether the firmware is Android or Ubuntu, It both work fine.And it just happened on EDGE-V V13.We try to use the DTB which is use for ubuntu to replace it . But the same result has emerged.Then we try to use another LE firmware , there has been no improvement.
We don’t have any idea with it .We try to solve it now .So, If you have any idea with it , you can tell us. Thanks. I am sorry that tell you no problem with it, I test in EDGE-V V12 at that time.

Hi @Frank try the version from here.

https://libreelec.tv/downloads_new/rockchip/

[Frank]

@balbes150，I will check it after download completed.

[Frank]

Hi @balbes150, I test with LibreELEC-RK3399.arm-9.1.001-khadas-edge.img.gz.The same phenomenon.

[balbes150]

@Frank There are three options for the source of the problem.

1. u-boot
2. kernel configuration
3. the source code of the kernel (driver).
   You can check u-boot. take u-boot from the old version (in which the wired network works) and write to the SD card with the new Le or Armbian image. The configuration and the source code I’ll check at home.

[Frank]

@balbes150 Ok, If there’s any new information, we’ll come back here and tell you.

[balbes150]

Try adding ‘extlinux.conf’ to the in the argument string for the fixed MAC kernel.

APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 mac=xx.xx.xx.xx

[balbes150]

@Frank
And try out the earliest versions of Armbian and LE images from MEGA file sharing (the link is in the first post of the theme about LE and Armbian).

[microdude]

Thank you for confirming @Frank, at least now I know I’m not crazy!

I also had the DHCP issue, but I think it was just a symptom of the larger packet loss problem (in other words, dropped DHCP packets causing DHCP to fail).

Glad you guys are able to reproduce.

[numbqq]

@balbes150

Try adding ‘extlinux.conf’ to the in the argument string for the fixed MAC kernel.

APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 mac=xx.xx.xx.xx

This mac address is not applied by current kernel. And I add the patch for it, I’m building a new image…

The ip address is very strange. ifconfig show the ip address is:

/ # ifconfig
eth0      Link encap:Ethernet  HWaddr 16:AB:6D:E8:52:D0  
          inet addr:169.254.128.4  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:38 errors:0 dropped:0 overruns:0 frame:0
          TX packets:178 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:6178 (6.0 KiB)  TX bytes:30108 (29.4 KiB)
          Interrupt:24 

But when I check the router, I found the ip address is:

My router gateway is 192.168.1.1, I don’t know how 169.254.128.4 come from…