I recently started looking at using EnOS on my ODROID N2+ again, now the ARM editions are back. However, I noticed that there is a typo in /boot/boot.ini in the section about detecting the board variant and subsequently loading the correct *.dtb file.
In the line starting with 'If test “&{variant}” ', that should be “n2_plus” with an underscore instead of a hyphen. The SBC is then properly detected as the “plus” variant and the right DTB loads.
So I am fine now I edited boot.ini, but I suppose it would be nice if the newer images get this addressed.
Line 1 has an arrow pointing to “n2_plus” change that to “n2-plus”
Line 2 specfies the Odroid N2+ meson driver for mesa.
“meson64_odroidn2_plus.dtb” change to " meson-g12b-odroid-n2-plus.dtb"
Line 4 specifies the Odroid N2 meson driver for mesa
“meson64_odroidn2.dtb” change to “meson-g12b-odroid-n2.dtb”
" Any new installations on a Odroid N2 or Odroid N2 Plus will utilize the linux-eos-arm kernel."
This is what fastfetch tells me with the underscore in place:
Host: Hardkernel ODROID-N2Plus
Kernel: Linux 6.9.7-1-eos-arm
lscpu tells this about the max clock speeds of the CPU cores. I think they are correct for the “plus” but I could be wrong.
Model name: Cortex-A53
CPU max MHz: 1800.0000
Model name: Cortex-A73
CPU max MHz: 2208.0000
With the hyphen instead:
(fastfetch)
Host: Hardkernel ODROID-N2
Kernel: Linux 6.9.7-1-eos-arm
(lscpu)
Model name: Cortex-A53
CPU max MHz: 1992.0000
Model name: Cortex-A73
CPU max MHz: 1908.0000
So I do not get entirely what is going on, given that the hyphen thus seems deliberate (based on that post by Pudge).
@Peter1986C
Welcome to the EndeavourOS forum. I hope you enjoy your time here.
Thank you very much for the feedback. I remember this snafu, but don’t remember which is correct now. The - or the _
I will check into this tomorrow. Right now I am doing testing on the new image for a headless server on the Odroid N2 / N2+ platform. I hope to have this tested and on github before I go to bed.
Thanks again for your interest in EnOS ARM.
Pudge
Just out of curiosity, which Desktop Environment or i3wm did you choose?
enosServer is my RPi 4b server that contains all my important files.
enosServer2 is the test Odroid N2 server.
enosServer and enosServer2 can be Auto launched during login, see the How-to Homeserver 3. That way all your files are immediately available when logging in.
Here I simply did a ssh from my client computer into enosServer2 which is how one would do maintenance. Such as pacman -Syu updates, backups, etc. Or even a neofetch
EDIT2:
After looking at this some more, I am convinced that the “n2_plus” is correct.
Just looking at the if statement,
if test "${variant}" = "n2_plus"; then
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson-g12b-odroid-n2-plus.dtb
else
load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson-g12b-odroid-n2.dtb
fi
the if condition
if test “${variant}” = “n2-plus”
doesn’t ever come up as true thus it goes to the else statement and always uses the n2 dtb no matter what.
the if condition of
if test “${variant}” = “n2_plus”
does come up as true and does set the n2-plus dtb
I have changed this in the boot.ini here
and I will issue a new server-odroid-n2-image and odroid-n2-image as soon as possible.
Somewhere in a closet, on a shelf, I have an Odroid N2 (not plus)
Tomorrow after I issue the new odroid-n2-image, I will burn a new uSD and try it on both the N2 and the N2+ and see if it recognizes the difference in a fastfetch & neofetch.
