any observations on “ethtool eth0”?
Maybe run mii-diag on WRT to monitor the link status…
But I think this is needed on CE device side. Maybe MII training failed on your HW
Yes, but I had same problems before with kernel 4.9, as you.
But I tested it with 4.9? and it was working, so what changed?
not sure.
you tested on nightly CE-20
there is a difference between nightly CE-19 and CE-20?
No, it’s same kernel.
Maybe it’s better to try out Amlogic-ne:
On both s904x4 and both kernels my speed seems fine with live TV and iperf but there are dropped packets in ifconfig The iperf scores are higher than my 1000M hub.
Martin
not sure where something got wrong.
I installed again the nightly image 20221006 for CE-19
the result now are excellent
iperf3 -c 192.168.1.1
Connecting to host 192.168.1.1, port 5201
[ 5] local 192.168.1.149 port 38752 connected to 192.168.1.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 107 MBytes 902 Mbits/sec 0 403 KBytes
[ 5] 1.00-2.00 sec 108 MBytes 902 Mbits/sec 0 403 KBytes
[ 5] 2.00-3.00 sec 107 MBytes 899 Mbits/sec 0 403 KBytes
[ 5] 3.00-4.00 sec 107 MBytes 896 Mbits/sec 0 403 KBytes
[ 5] 4.00-5.00 sec 107 MBytes 900 Mbits/sec 0 403 KBytes
[ 5] 5.00-6.00 sec 107 MBytes 896 Mbits/sec 0 403 KBytes
[ 5] 6.00-7.00 sec 107 MBytes 897 Mbits/sec 0 403 KBytes
[ 5] 7.00-8.00 sec 107 MBytes 899 Mbits/sec 0 403 KBytes
[ 5] 8.00-9.00 sec 107 MBytes 899 Mbits/sec 0 403 KBytes
[ 5] 9.00-10.00 sec 107 MBytes 899 Mbits/sec 0 403 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.05 GBytes 899 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 1.04 GBytes 897 Mbits/sec receiver
iperf Done.
I will keep monitor it . what causes to speed drop
Thanks Everyone!
1 Like
When you don’t define your interface it’s not sure what iperf take for the test. So if also WLAN is connected it’s possible this is used.
You can test it by adding the device name with --bind-dev eth0 as example.
1 Like
Been on a road trip for about 3 weeks, just got back yesterday.
First thing I did was to try the new NE version of CoreELEC, it is working very well on my HK1 box.
Does this solve the issue of a different ethernet adapter that is only providing fast ethernet speeds.
I just try the CoreELEC-Amlogic-ne.arm-20.0-Nexus_nightly_20221007-Generic on my HK1 RBOX X4 4gb/32GB 1000MB Lan with one of the JLxxx chip and glad to say the LAN is now working. Great job to the CE team.
But there is a bug with the audio. I play a movie with Dolby Atmos and it works fine but when I stop the movie, the audio will stop working and it still show Dolby Atmos on my receiver. The UI clicking sound is not working and when I play Youtube video, there is no audio. Seems like CE is locked at Dolby Atmos sound. Only a reboot of CE will bring back the audio.
I also tried it with the CoreELEC-Amlogic-ng.arm-19.5-Matrix_nightly_20221006-Generic and it shows the LAN is active but there is no internet connection. I can still connect to the box via SSH but everytime I try to transfer file(even the small remote.conf files) also failed. The LAN seems to be active but the connection is very bad.
I enabled logging and played a high bitrate 4K movie for about an hour, and the box never locked up.
I then scraped more TV episodes for over an hour and still NO lock up.
Can the fact that the logging was taking place, keep the box from locking up??
I was testing on an HK1 X4 Rbox, with a small fan blowing air into the box from the bottom. The temp ranged from 66C to 72C, mostly 70C.
Here is the log, even though there was no lockups. http://ix.io/4cXM
The other problem as others mentioned, there is no MAC address, just one that starts with 2xxx. This may be the cause of this box changing IP addresses. Originally, the IP address ended with a “6”, for months. Now, it has changed to 163, and now 161. The IP address under Android is 192.168.10.177 with a dedicated MAC address.
I posted my workaround to force the HK1 box type MAC used in Android here. Report about Amlogic S905X4 HK1 RBOX X4 - #518 by emveepee Before using it confirm that you have the valid MAC
fw_printenv -n ethaddr
pasted your command into Putty, but got the
CoreELECHK1:~ # fw_printenv -n ethaddr
Error: “ethaddr” not defined
Since you use an unsupported box maybe continue in the other thread you started.
Does it matter what box I am using?? I am testing the NE version.
No, some of these HK1 boxes are shipped with like refurbished eMMc and so the data is not burned and that’s the reason it’s all zeros.
Post the result of fw_printenv | paste
http://ix.io/4cYb
Looking at this part of the log, ( dolby_vision_on=0 hdr_policy=1 hdr_priority= frac_rate_policy=1 hdmi_read_edid=1) does that mean my TV should show HDR?
It should have worked, maybe you ssh’d into another box?