Asysob
-
Posts
5 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Community Map
Posts posted by Asysob
-
-
Thank you for all your efforts. I will wait for your results.
-
It is really strange. I've done this now multiple times, always with the same result. The upgrade yields the warnings and errors above. Rebooting after the upgrade - and that is really curious - works once. I can log in and do whatever i want, but when i reboot a second time (counting from the last upgrade), the system hangs with the blue alive LED being continuously on (which looks like no kernel is booting at all - at least there is no output on the screen). /var/log/messages also says that no system has been started. dd'ing the image Armbian_5.14_Odroidc2_Debian_jessie_3.14.72 again and everything is fine, so it doesn't look like a hardware error?
-
After this upgrade, these systems don't reboot correctly. The blue heartbeat LED is constantly on and the ssh login is not available anymore (/etc/network/interfaces and /etc/ssh/sshd_config appear to be okay). This behavior happens consistently on both Odroid C2 after the upgrade and it happens even with a fresh installation and subsequent upgrade. These systems are used headless and it is quiet complicated to see the boot sequence, but i guess i can check that from the logs in some kind of post-portem analysis by inserting the eMMC into another Linux computer. Sometimes, it takes a little longer until i remember all the tools available to recover from some error .
-
I do have problems on my two Odroid C2 after "apt-get update" and "apt-get upgrade". It happens on a freshly installed Armbian_5.14_Odroidc2_Debian_jessie_3.14.72 (on a 64GB eMMC) immediately after the first login (so at least in principle, i can't be the culprit, but who knows ):
The following packages will be upgraded:linux-dtb-odroidc2 linux-headers-odroidc2 linux-image-odroidc2 linux-jessie-root-odroidc2 linux-libc-devlinux-u-boot-odroidc2-default tzdataPreparing to unpack .../linux-dtb-odroidc2_5.16_arm64.deb ...Unpacking linux-dtb-odroidc2 (5.16) over (5.14) ...Preparing to unpack .../linux-headers-odroidc2_5.16_arm64.deb ...Unpacking linux-headers-odroidc2 (5.16) over (5.14) ...dpkg: warning: unable to delete old directory '/usr/src/linux-headers-3.14.72-odroidc2/scripts/selinux/mdp': Directory not emptydpkg: warning: unable to delete old directory '/usr/src/linux-headers-3.14.72-odroidc2/scripts/selinux/genheaders': Directory not emptydpkg: warning: unable to delete old directory '/usr/src/linux-headers-3.14.72-odroidc2/scripts/selinux': Directory not emptydpkg: warning: unable to delete old directory '/usr/src/linux-headers-3.14.72-odroidc2/scripts/basic': Directory not emptydpkg: warning: unable to delete old directory '/usr/src/linux-headers-3.14.72-odroidc2/scripts/kconfig': Directory not emptydpkg: warning: unable to delete old directory '/usr/src/linux-headers-3.14.72-odroidc2/scripts/dtc': Directory not emptydpkg: warning: unable to delete old directory '/usr/src/linux-headers-3.14.72-odroidc2/scripts/mod': Directory not emptydpkg: warning: unable to delete old directory '/usr/src/linux-headers-3.14.72-odroidc2/scripts': Directory not emptydpkg: warning: unable to delete old directory '/usr/src/linux-headers-3.14.72-odroidc2': Directory not emptyPreparing to unpack .../linux-image-odroidc2_5.16_arm64.deb ...Unpacking linux-image-odroidc2 (5.16) over (5.14) ...Preparing to unpack .../linux-jessie-root-odroidc2_5.16_arm64.deb ...Unpacking linux-jessie-root-odroidc2 (5.16) over (5.14) ...Preparing to unpack .../linux-libc-dev_3.16.7-ckt25-2+deb8u3_arm64.deb ...Unpacking linux-libc-dev:arm64 (3.16.7-ckt25-2+deb8u3) over (3.16.7-ckt25-2) ...Preparing to unpack .../linux-u-boot-odroidc2-default_5.16_arm64.deb ...Unpacking linux-u-boot-odroidc2-default (5.16) over (5.14) ...Processing triggers for initramfs-tools (0.120+deb8u2) ...ln: failed to create hard link ‘/boot/initrd.img-3.14.72-odroidc2.dpkg-bak’ => ‘/boot/initrd.img-3.14.72-odroidc2’: Operation not permittedupdate-initramfs: Generating /boot/initrd.img-3.14.72-odroidc2WARNING: missing /lib/modules/3.14.72-odroidc2Ensure all necessary drivers are built into the linux image!depmod: ERROR: could not open directory /lib/modules/3.14.72-odroidc2: No such file or directorydepmod: FATAL: could not search modules: No such file or directorydepmod: WARNING: could not open /var/tmp/mkinitramfs_z0d3vz/lib/modules/3.14.72-odroidc2/modules.order: No such file or directorydepmod: WARNING: could not open /var/tmp/mkinitramfs_z0d3vz/lib/modules/3.14.72-odroidc2/modules.builtin: No such file or directoryProcessing triggers for systemd (215-17+deb8u4) ...Setting up linux-dtb-odroidc2 (5.16) ...Setting up linux-headers-odroidc2 (5.16) ...Compiling headers - please wait ...Setting up linux-image-odroidc2 (5.16) ...update-initramfs: Generating /boot/initrd.img-3.14.73-odroidc2
[Odroid C2] Upgrading fresh 5.14 to 5.16 fails
in Amlogic meson
Posted
Okay, good to hear! So in order to have a running system again, I should upgrade to version 5.16 and before i reboot, i should compile kernel and u-boot from the sources?