samaritan

The images are not worth running in production because at some point there's sd card corruption it is worth mentioning.

Well it seems that it doesn't work that well some kind of corruption. [ 398.788954] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #2: comm systemd-udevd: reading directory lblock 0 [ 398.799372] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #10930: comm systemd-udevd: reading directory lblock 0 [ 398.831376] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #10930: comm systemd-udevd: reading directory lblock 0 [ 398.841743] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #5352: comm systemd-udevd: reading directory lblock 0 [ 398.857158] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #2: comm systemd-udevd: reading directory lblock 0 [ 399.019189] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #10930: comm systemd-udevd: reading directory lblock 0 [ 399.069134] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #76498: comm systemd-udevd: reading directory lblock 0 [ 399.093787] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #5352: comm systemd-udevd: reading directory lblock 0 [ 399.104768] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #2: comm systemd-udevd: reading directory lblock 0 [ 399.119149] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #10930: comm systemd-udevd: reading directory lblock 0 [ 399.129577] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #76498: comm systemd-udevd: reading directory lblock 0 [ 399.140373] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1660: inode #5361: comm systemd-udevd: reading directory lblock 0

I think the basic necessary with lan+ssh should work just fine isn't it ?

It seems that they have updated the linux distro with few things on https://linux-meson.com/mainlining.html Latest update linux-mainline 5.4

Oups

Images tried : Armbian_21.02.1_Odroidc1_bullseye_current_5.10.12.img.xz Armbian_22.08.0-trunk_Odroidc1_jammy_current_5.18.19.img.xz Results: Armbian_21.02.1_Odroidc1_bullseye_current_5.10.12.img.xz Network is recognized and ssh login possible + Serial console output working. ping gmail.com is working Armbian_22.08.0-trunk_Odroidc1_jammy_current_5.18.19.img.xz Network is not recognized and ssh login possible + Serial console output working. ping gmail.com is not working

@SteeMan I am so sorry I didn't realized that the windows was the wrong one.

I am so sorry!

Could someone upload the latest working image somewhere please? I have 2 old odroid-c1 board that I would like to use only with ssh, docker and external HD. Will that be possible with the current situation?