Igor

Sure, the rest can be adjusted on PR itself. I still wait / hope we will manage to switch CURRENT to 6.12.y with this release, otherwise this will stick at edge until.

Last week I managed to complete first part of run-time desktop deployment script. It might serve as a starting point of what you want to achieve. https://github.com/armbian/configng/pull/436

# Europe/Moscow - 2000 Mbit/s - server: stpete-mirror.armbian.com/beta/ rules: - field: location.country.iso_code not_in: - UA latitude: 59.9417 longitude: 30.3096 weight: 10 # Europe/Kiev - 1000 Mbit/s - server: fastmirror.pp.ua/armbian/ rules: - field: location.country.iso_code not_in: - RU latitude: 50.458 longitude: 30.5303 weight: 10 After this change, our redirector blocks access to Russian mirrors for users in Ukraine and vice versa. Hopefully, this feature will become obsolete soon.

Test for latest stable image (Armbian_25.2.1_Odroidxu4_bookworm_current_6.6.75_minimal.img.xz) 1. https://dl.armbian.com/odroidxu4/Bookworm_current_minimal 2. Boot logs on HC1 https://paste.next.armbian.com/kupugotasi No issues whatsoever. Check PSU, cables, use different SD card, ...

This is how network is set for some time now: https://docs.armbian.com/User-Guide_Networking/

Desktop installation: (XFCE and Gnome at the moment) https://docs.armbian.com/User-Guide_Armbian-Software/Desktops/ automatic install and uninstall on code changes and daily modular packages assembly https://github.com/armbian/configng/blob/main/tools/modules/system/module_desktop_packages.sh clean and minimal (will be cleaned more, PR is welcome)

If you already upgraded to broken version before, it will break. Then re-installation of those package is needed, like I did.

Manual test on our test device: root@odroidxu4:~# apt update root@odroidxu4:~# apt install --reinstall linux-image-current-odroidxu4 linux-dtb-current-odroidxu4 root@odroidxu4:~# reboot After machine is up: https://paste.next.armbian.com/zapohihawi

We have 3a and 3c. What is the difference anyway? Doesn't work with any of those?

@c0rnelius added missing files https://github.com/armbian/firmware/pull/100/files right. I guess this is it, just merging it.

Nice! In case you will get an idea to add something to this system, this is how it goes: https://docs.armbian.com/Contribute/Armbian-config/

Yes, of course. Running apt update + apt upgrade should update armbian-config to the latest. If you want to keep installed software updated, see options in "Updates". You can enable automatic updating of container images. If you are somehow missing sources lists, manual way: https://github.com/armbian/configng/tree/main?tab=readme-ov-file#getting-started

Yes of course. But documentation or FAQ should be somewhere and up2date. Its a lot of work / impossible for our small team to cover all aspects of a Linux system. But for at least Armbian specifics - which this is - we might have somehting. Thanks!

Help in improving our recovery instructions is also warmly welcome https://docs.armbian.com/User-Guide_Recovery/ We are too small for "everything"

Old one works nice again: https://www.armbian.com/odroidc1/

This looks like DNS problem / or lack of apt update command before installation.

With point releases we are targeting (CURRENT) LTS kernels, while the rest is anyway DIY or build daily. This is just an idea / option, perhaps better way to share the load. Keep the good work!

You should always use apt.armbian.com as we are automatically removing mirrors from pool that are not synced yet. I just tested Odroid XU4 switching between nightly and stable, and it works when installing packages from stable repo. Name / version of the file is the same. If someone has time, those instructions would need some update https://docs.armbian.com/User-Guide_Recovery/ I am totally busy making a release and can't touch this in weeks to come.

No worries, I am happy that you tried. Its never too late to learn new tools, and Git is the most important tool in this world. What you did wrong is removing other files - keep old, add new, then we merge them into the code. Principle goes this way: 1. You make a clone of this Git (git clone ...) 2. You checkout to a new branch (git checkout -b adding_rpi5_firm) 3. Add files to correct location (which it looks like you did) 4. Push the code and open pull request Some generic instructions: https://docs.armbian.com/Process_Contribute/ https://github.com/armbian/build/blob/main/CONTRIBUTING.md Also some AI tool can help you driving this process easily.

@unic8 I look into the code too, but it will have to wait ... not exactly 5 minute job. I have reverted that bump, so we are back at 6.6 and working USB.

Could be. I also don't know - has to be tested. Can you jut open a PR with those files to firmware repo? I can test perhaps next week.

Its a shame for us There are so many problems (in general) and so little time / resources. Not yet fully fixed, but working on.

This can give some ideas: https://docs.armbian.com/User-Guide_Recovery/ (not exact walk trough, but the principle is the same) Note that fixed packages are not yet uploaded. In a couple of hours.

Fixed by: https://github.com/armbian/build/commit/5115cdf47a91f9cf5eb15f1b4984deebbe329002 This can help https://docs.armbian.com/User-Guide_Recovery/

XU4 / HC1 is fixed by https://github.com/armbian/build/commit/5115cdf47a91f9cf5eb15f1b4984deebbe329002 Images are in generation, update is going out when possible. (broken updates were also disabled, but takes time for repo to sync)