March 15, 20233 yr 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
March 15, 20233 yr @samaritan You do understand that the Odroid C1 board is listed as EOS (End of support). No one is working to maintain that board anymore and thus over time more and more will cease to work on that board.
March 15, 20233 yr Author 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
March 15, 20233 yr Author 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
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.