OK, now I build a unstable image, see you later with my test report.
[nls@nls-pc ~]$ sudo buildarmimg -d oc2 -e kde-plasma -v 2021.06.18-01 -b unstable -n
The Odroid C2 is an EOL device though, so we probably won’t put to much work into fixing it, if it breaks again. Just so you know. 
Yes, I know, the device is End Of Life, I think it will be nice to keep it alive, until now no hardware issue.
Total Download Size: 8.06 MiB
Total Installed Size: 3867.66 MiB
Net Upgrade Size: 3808.15 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
mkinitcpio-busybox-1.33.1-1-aarch64 241.2 KiB 1063 KiB/s 00:00 [########################################] 100%
libva-2.12.0-0.1-aarch64 222.7 KiB 891 KiB/s 00:00 [########################################] 100%
editorconfig-core-c-0.12.5-1-aarch64 29.5 KiB 4.81 MiB/s 00:00 [########################################] 100%
okular-21.04.2-2-aarch64 7.6 MiB 842 KiB/s 00:09 [########################################] 100%
(714/714) checking keys in keyring [########################################] 100%
Short answer: The kernel source tree.
The linux package, gets built directly from kernel.org’s source, while linux-vim gets built from Tobetters (from hardkernel) source tree, which includes some fixes and stuff for odroids. I believe he wants to upstream most of it.
1 Like
The C2 have a linux-vim kernel, but the other Odroid devices (N2, C4…) not, why?
Because the other Odroids work fine with linux while, as you found out, the C2 seems to not be anymore.
The C2 had been running linux for years before this.
Thanks a lot for your answers, have a good day.
As you know, I’ll try to run the C2 as long as possible :-)
The device is working well, no hardware issue.
1 Like
Hi,
The Odroid C2 is working like a charm, one more time, thanks a lot !
Question about the Odroid N2.
To build a N2 image, I refresh right now with the command sudo getarmprofiles -f
the N2 have no specific, dedicated video driver ? the kernel do the job?
## Maintained by Strit ##
# Kernel and bootloader stuff
linux
uboot-odroid-n2
plymouth
plymouth-theme-manjaro
# Video driver
# Other device specific packages
btrfs-progs
fbset
on2-post-install
The C2 have some dedicated video driver xf86-video-fbturbo-git
## Maintained by Strit ##
# Kernel and bootloader stuff
linux-vim
uboot-odroid-c2-mainline
plymouth
plymouth-theme-manjaro
# Video driver
xf86-video-fbturbo-git
# Other device specific packages
btrfs-progs
fbset
amlogic
oc2-post-install
Yes. The kernel does the job for it.
That’s because I’m not certain if it works with the kernel driver.
Hi,
After the 2021.07.07 up date and the no reboot, I built a new image for the Odroid C2, the device boot and working, but issue with the Ethernet connection on boot
Could not get PHY for Ethernet
Hm. Was there an update to the kernel it uses?
Yes, now the device is running with the 5.13 kernel
[nlc2@c2 ~]$ screenfetch
nlc2@c2.21.07.07
OS: Manjaro-ARM 21.07
Kernel: aarch64 Linux 5.13.0-1-MANJARO-ARM
##### Uptime: 1h 2m
####### Packages: Unknown
##O#O## Shell: bash 5.1.8
####### Resolution: 1920x1080
########### DE: KDE 5.83.0 / Plasma 5.22.2
############# WM: KWin
############### GTK Theme: Breeze [GTK2], Breath-Dark [GTK3]
################ Icon Theme: oxygen
################# Disk:
##################### CPU: 4x Unknown
##################### RAM: 785MiB / 1952MiB
#################
[nlc2@c2 ~]$
I compared the extlinux.conf file
C2 image working since 2021.07.07
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/amlogic/meson-gxbb-odroidc2.dtb
APPEND initrd=/initramfs-linux.img console=tty1 console=ttyAML0,115200n8 root=PARTUUID=6a980000-02 rw rootwait quiet splash plymouth.ignore-serial-consoles
C2 not working since 2021.07.07, after the up date
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/amlogic/meson-gxbb-odroidc2.dtb
APPEND initrd=/initramfs-linux.img console=tty1 console=ttyAML0,115200n8 root=PARTUUID=74d80000-02 rw rootwait quiet splash plymouth.ignore-serial-consoles
the difference I found have an effect on the boot ?
C2 image working since 2021.07.07
PARTUUID=6a98
C2 not working since 2021.07.07, after the up date
PARTUUID=74d8
Double check with lsblk -o NAME,PARTUUID
Thanks for your answer
the working C2 is looking so
[nlc2@c2 ~]$ lsblk -o NAME,PARTUUID
NAME PARTUUID
sda
mmcblk1
mmcblk1p1 6a980000-01
mmcblk1p2 6a980000-02
mmcblk1boot0
mmcblk1boot1
zram0
[nlc2@
you need the answer for the no working c2 image ?
Yeah, change the extlinux.conf file to what’s in your lsblk output. 
Not sure why it won’t work on before update. As the PARTUUID is the only thing different.
OK, I’ll try, see you later with my feedback
Nice, the device boot, no Ethernet issue on screen but then nothing, it look like my post from 15 Jun, see below
esc is working for more info if needed…
[rootfs ]# _
error partuuid= 6a980000-02 not found. skipping fsck
mount : / new_root : can’t find partuuid= 6a980000-02
I don’t know. I’m clueless.