Would be option, yes.
[ 0.000000@0] Kernel command line: init=/init console=ttyS0,921600 no_console_suspend earlycon=aml-uart,0xfe07a000 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 loop.max_part=4 loglevel=7 otg_device=0 logo=osd0,loaded,0x00300000 vout=1080p60hz,enable panel_type=lcd_1 hdmitx=,422,12bit
hdmimode=1080p60hz hdmichecksum=0xbc710000 dolby_vision_on=0 hdr_policy=1 hdr_priority= frac_rate_policy=1 hdmi_read_edid=1 cvbsmode=576cvbs osd_reverse=0 video_reverse=0 irq_check_en=0 androidboot.selinux=permissive androidboot.firstboot=0 jtag=disable androidboot.bootloader=01.01.220620.224252 androidboot.hardware=amlogic androidboot.serialno=ah21280566015c1a11b0e androidboot.wificountrycode=US androidboot.rpmb_state=1x1 androidboot.slot_suffix=_b BOOT_IMAGE=kernel.img boot=LABEL=COREELEC disk=LABEL=STORAGE console=tty0 no_console_suspend keymap=us vout=1080p60hz,dis logo=osd0,loaded,0x00300000 frac_rate_policy=0 hdmitx=, hdr_policy=1 quiet androidboot.vbmeta.device=/dev/block/vbmeta androidboot.vbmeta.avb_version=1.1 androidboot.vbmeta.device_state=locked androidboot.vbmeta.hash_alg=sha256 androidboot.vbmeta.size=6912 androidboot.vbmeta.digest=918696b10612ff2e5d2b99ef9840a63d4e1e003204c0fb61cb800d28722086fb androidboot.vbmeta.invalidate_on_error=yes androidboot.veritymode=enforcing androidboot.verifiedbootstate=green
There is no mac or ethaddr in boot parameters defined. The box I have SSH access do read this mac from memory. But in CE kernel it’s not possible anymore since SC2 because of security.
It just read 0x00. But I checked the other HK1 box and might got just an idea. Let me check if it’s somehow possible.
@emveepee please make me a log of your complete bootloader environment with:
fw_printenv | paste
Sure here you go http://ix.io/4cb2
this is your problem:
if keyman read mac ${loadaddr} str; then setenv bootargs ${bootargs} mac=${mac}
Your vendor did not burn the mac unify key.
Please run in CE console:
cat /sys/class/efuse/mac
cat /proc/cpuinfo
# cat /sys/class/efuse/mac
0x00: 00 00 00 00 00 00
# cat /proc/cpuinfo
processor : 0
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0
processor : 1
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0
processor : 2
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0
processor : 3
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0
Serial : 320b0201000000000e1ba1c115605680
Hardware : Amlogic
It’s also empty and you need to use your workaround script.
efuse return 0x00
320b0201000000000e1ba1c115605680 what represent the mac is also empty.
You can “fix” your bootloader configuration by:
fw_setenv cmdline_keys 'setenv region_code US; setenv bootargs ${bootargs} mac=${ethaddr}'
The whole keyman stuff is not needed as it is empty. But on next update this change is lost again and you will need to run fw_setenv again.
This image should have now the “workaround” implemented for your cheap sh$%& box:
CoreELEC-Amlogic-ne.arm-20.0-Nexus_devel_20221003163621-Generic.img.gz
Maybe the data is not burned as it’s a used and refurbished eMMC what is assembled in your hardware. I would not trust this peace of hardware, I guess it will fail soon…
EDIT:
Image removed
For devices like yours please use the option config.ini:
Add on bottom coreelec='mac=<your mac>' and it should be permanent available.
So in your case coreelec='mac=02:ad:32:01:70:2a'
EDIT:
Maybe this is working as well:
coreelec='mac=${ethaddr}'
1 Like
OK thanks I can work with my autostart.sh script and rewrite it when it is zeroes to avoid the down/up delay.
Edit: config.ini with my mac worked. The variable doesn’t works because it is not in the environment, I was getting ethaddr with fw_printenv in my script. I might stick with autostart since I can use the same card in multiple devices.
Martin
Hi, can you post again this image, I have the same problems as @emveepee and I want to test this image. Thank you sir for the great job BTW.
Did you try using the earlier ne image File on MEGA with working VFD?
No, the link its not working, but that one I like to try it.
Sorry I didn’t check, I downloaded directly so don’t have a copy.
@Portisch, hi, can you repost the image [CoreELEC-Amlogic-ne.arm-20.0-Nexus_devel_20221003093146-Generic.img.gz], I wish to try it. Thank you.
The JL2xx1 chip will be supported soon in next CE-19 and CE-20 nightlies.
Many thanks to the CE user @tomergam who gave us the possibility to have remote access to such piece of hardware. Because of this remote sessions it was possible to add support for Amlogic-ng and upcoming Amlogic-ne project.
6 Likes
This was also the case on my X96 X4, HW rev 1.3.
efuse return 0x00
But did not need to edit config.ini, because in cmdline MAC was set already and it worked.
I did post logfiles already here some time ago.
Yes, this is the normal way. The bootloader read it from eMMc and set it in boot console. But these others one looks like refurbished eMMc or something else cheap cheating and the data is not on eMMc.
So it’s set only manual by the vendor in source.
So when you buy such device you will never be sure what you receive. There are now about 4 different hardware configurations and 4 images as well.
Remind, this all for one device sold under same name…
I build the new version (don’t know if it is in the nightly yet) and the jl2xxx device is started on my two devices, I guess they get ah212 from the dtb. Logs http://ix.io/4cl2 or http://ix.io/4cl4.
With the nightly the old 02:00… no is not consistent so people might not get a fixed IP from the router here is my autostart.sh that works on both my jl21xxx devices
if [ -z "$(fw_printenv -n mac)" ]; then
my_mac="$(fw_printenv -n ethaddr)"
fw_setenv cmdline_keys 'setenv region_code US; setenv bootargs ${bootargs} mac='$my_mac''
fw_setenv mac $my_mac
ip link set eth0 down
ip link set dev eth0 address $my_mac
ip link set eth0 up
fi
The CE20 on the VFD is a nice touch, I never noticed that before
Which file and where can I download the latest CE to try on my HK1 box to see if the 1000gb LAN works?
Try the latest nightly build.
try the nightly 20221006 CE19
now I got eth0
but getting very slow results
iperf3 -c 192.168.1.1
Connecting to host 192.168.1.1, port 5201
[ 5] local 192.168.1.149 port 44400 connected to 192.168.1.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 424 KBytes 3.47 Mbits/sec 23 1.41 KBytes
[ 5] 1.00-2.00 sec 127 KBytes 1.04 Mbits/sec 11 2.83 KBytes
[ 5] 2.00-3.00 sec 63.6 KBytes 521 Kbits/sec 5 1.41 KBytes
[ 5] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec 4 1.41 KBytes
[ 5] 4.00-5.00 sec 191 KBytes 1.56 Mbits/sec 16 2.83 KBytes
[ 5] 5.00-6.00 sec 255 KBytes 2.08 Mbits/sec 16 2.83 KBytes
[ 5] 6.00-7.00 sec 0.00 Bytes 0.00 bits/sec 7 2.83 KBytes
[ 5] 7.00-8.00 sec 63.6 KBytes 522 Kbits/sec 6 2.83 KBytes
[ 5] 8.00-9.00 sec 127 KBytes 1.04 Mbits/sec 13 2.83 KBytes
[ 5] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec 4 1.41 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.22 MBytes 1.03 Mbits/sec 105 sender
[ 5] 0.00-10.00 sec 1.07 MBytes 900 Kbits/sec receiver
Sorry, but must be. Buy cheap, buy twice…