torz77

So, I have revisited my Odroid C1+ board, as I want to move away from Ubuntu. I'm pleased to say that the latest Armbian (Bookworm) builds just fine for the Odroid C1+, with the same caveats as before: - Probably No HDMI (Not tested) - Probably No WiFi (Not tested) However, unlike before, rebooting seems to work fine without requiring a manual power cycle. Whilst the instructions work for me, that does not mean that they will work for you. I just provide this here for any other Odroid C1+ users who may want to get a more up to date distro + kernel on their board. I have not done any extensive testing I have built a Debian Bookworm image on a Debian Bookworm host system. I include the instructions that worked for me below. At the time of image build there is no need to download any external files from elsewhere. I have built a minimal image as that is what I require. I have not tested with any other flags. I built on host system without Docker, so cannot speak for the Docker build process. With that said, current process is very simple. HEAD was at commit `fc54623c4a6dd3b1a8fb5f0a325e5461f0ae6364`, in case you need to go back to a known working build. sudo apt install git git clone --depth=1 https://github.com/armbian/build.git ./compile.sh \ BOARD=odroidc1 \ BRANCH=current \ RELEASE=bookworm \ BUILD_MINIMAL=yes \ BUILD_DESKTOP=no \ CLEAN_LEVEL= \ PREFER_DOCKER=no \ KERNEL_CONFIGURE=no \ COMPRESS_OUTPUTIMAGE=sha,gpg,img And that's it. Image is saved in: ./output/images Final image running on the Odroid C1+: /_\ _ _ _ __ | |__(_)__ _ _ _ ___ _ _ _ _ ___ / _|/ _(_)__(_)__ _| | / _ \| '_| ' \| '_ \ / _` | ' \___| || | ' \/ _ \ _| _| / _| / _` | | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \_,_|_||_\___/_| |_| |_\__|_\__,_|_| v24.11 rolling for Odroid C1 running Armbian Linux 6.6.43-current-meson Packages: Debian stable (bookworm) Support: DIY (custom image) IP addresses: (LAN) IPv4: xxx.xxx.x.xxx IPv6: xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx (WAN) xx.xx.xx.xxx Performance: Load: 13% Up time: 12 min Memory usage: 7% of 988M CPU temp: 49°C Usage of /: 3% of 29G Commands: Configuration : armbian-config Monitoring : htop

Yes, I built from source. Unfortunately I don't think I still l have the img around. I have not tried Docker, no.

I've been using this daily on a headless C1+ with no issues (outside of the reboot issue, which I can live with).

Reboot definitely doesn't work from cli. I don't have a button, so can't test. Basically SSH session closes, but the network interface still pings until a power cycle.

I will do. At the moment, I've only hit one issue, and that is the need to power-cycle the board to reboot. Unfortunately I can't connect a serial console, so can only go off SSH. (I'll check the log next time I reboot). `sudo reboot now` throws me out of SSH as expected, but the network connection stays up (I can ping the board), although cannot reconnect on SSH until after power cycling, so it looks like it is getting stuck somewhere prior to shutting down networking. This is a mild frustration, rather than the end of the world. The board is just running as an OpenLDAP server for my homelab, so shouldn't need power cycling too often. I was going to put an OpenVPN server on it too, but I may skip that if I can't reboot it remotely.

I just got home to a successfully built image from the master branch ___ _ _ _ ____ _ / _ \ __| |_ __ ___ (_) __| | / ___/ | | | | |/ _` | '__/ _ \| |/ _` | | | | | | |_| | (_| | | | (_) | | (_| | | |___| | \___/ \__,_|_| \___/|_|\__,_| \____|_| Welcome to Armbian 23.02.0-trunk Jammy with Linux 5.15.95-meson No end-user support: built from trunk System load: 47% Up time: 3 min Memory usage: 8% of 990M IP: 192.168.1.77 CPU temp: 46°C Usage of /: 21% of 7.0G RX today: 31.4 KiB Thanks again for your continued work on this.

Ok, I switched to the master branch, and it is definitely getting further along now (didn't even reach dependency download before). I have to go out now, but will leave it running and report back later tonight/tomorrow. Does this still have the restart bug (i.e. needing a power cycle?)

I have exactly the same issue as Kovács Gábor above. What I have tried: Downloading uboot: git clone --depth 1 https://github.com/armbian/build cd build mkdir ./output/debs wget -c -O ./output/debs/linux-u-boot-current-odroidc1_23.02.0-trunk_armhf.deb http://apt.armbian.com/pool/main/l/linux-u-boot-odroidc1-current/linux-u-boot-current-odroidc1_21.02.3_armhf.deb ./compile.sh CLEAN_LEVEL= BOARD=odroidc1 BRANCH=current RELEASE=jammy REPOSITORY_INSTALL= BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no KERNEL_ONLY=no COMPRESS_OUTPUTIMAGE=sha,gpg,img Using REPOSITORY_INSTALL flag: git clone --depth 1 https://github.com/armbian/build cd build ./compile.sh CLEAN_LEVEL= BOARD=odroidc1 BRANCH=current RELEASE=jammy REPOSITORY_INSTALL=u-boot BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no KERNEL_ONLY=no COMPRESS_OUTPUTIMAGE=sha,gpg,img Compile has been tried with and without sudo. Have tried cloning into a new location. Always the same issue: [🌱] Fetching SHA1 of branch odroidc-v2011.03 [ https://github.com/hardkernel/u-boot.git ] [🌱] SHA1 of branch odroidc-v2011.03 [ 'e7d4447d551ccba5d60be8b11697aa0ab49086c4 b7b8dc21b64b9494618325c9b4d2fbae728aeed6' ] [💥] error! [ Failed to fetch Makefile from 'https://raw.githubusercontent.com/hardkernel/u-boot/e7d4447d551ccba5d60be8b11697aa0ab49086c4 b7b8dc21b64b9494618325c9b4d2fbae728aeed6/Makefile' ] [💥] Exiting with error 43 [ at /mnt/Data/git/build/lib/functions/logging/traps.sh:1 exit_with_error() --> lib/functions/logging/traps.sh:1 obtain_makefile_body_from_git() --> lib/functions/general/git-ref2info.sh:84 memoized_git_ref_to_info() --> lib/functions/general/git-ref2info.sh:127 run_memoized() --> lib/functions/general/memoize-cached.sh:52 artifact_uboot_prepare_version() --> lib/functions/artifacts/artifact-uboot.sh:26 artifact_prepare_version() --> lib/functions/artifacts/artifacts-obtain.sh:24 do_with_logging() --> lib/functions/logging/section-logging.sh:72 obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:76 build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:209 main_default_build_packages() --> lib/functions/main/build-packages.sh:49 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:4 do_with_default_build() --> lib/functions/main/default-build.sh:17 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:17 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:126 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:164 main() --> compile.sh:52 ] [💥] Cleaning up [ please wait for cleanups to finish ] Any insights you may have would be appreciated, otherwise I'll just roll with focal for now. Either way, thanks for posting this. Good to know people are still trying to get life out of the C1, even if HardKernal basically decided to stop supporting it pretty much on release 😕