Malbonulo

I just created a pull request for this. Apologies if I got the request wrong, it's been a long time since I created a PR on anything.

Although they're in my file (I have used armbian for a long time so it might be legacy code) they do not run because they are in a test that returns false. I think you have the important part which is # this is for mainline only if test "${board_name}" = "xu4"; then setenv fdtfile "exynos5422-odroidxu4.dtb"; fi if test "${board_name}" = "xu3"; then setenv fdtfile "exynos5422-odroidxu3.dtb"; fi if test "${board_name}" = "xu3l"; then setenv fdtfile "exynos5422-odroidxu3-lite.dtb"; fi if test "${board_name}" = "hc1"; then setenv fdtfile "exynos5422-odroidhc1.dtb"; fi # legacy shares a single DT for all boards if ext4load mmc 0:1 0x00000000 "/boot/.next" || fatload mmc 0:1 0x00000000 ".next" || ext4load mmc 0:1 0x00000000 ".next"; then echo "Found mainline kernel configuration"; else setenv fdtfile "exynos5422-odroidxu3.dtb"; fi ext4load mmc 0:1 0x44000000 /boot/dtb/${fdtfile} || fatload mmc 0:1 0x44000000 dtb/${fdtfile} || ext4load mmc 0:1 0x44000000 dtb/${fdtfile} Although I'm no expert.

It's been a while since I coded in bash but I'll take a look. I see the necessary line in the motd is taken from /etc/armbian-image-release and then these values are over-written from /etc/armbian-release The variable in question is BOARD_NAME. I guess it would be a simple matter to rewrite BOARD_NAME=..., I just wouldn't know if this had a knock-on effect down the line somewhere. Having said all this, this is all just cosmetic, the important change will be to /boot/armbianEnv.txt where the line board_name= needs to change, this is what sets the correct dtb in boot.ini. But it strikes me that even if I send a pull request, that will take someone's time, and if you can't support an hour, maybe the pull request is not worth it?

Thank-you. > Aha, you mean you miss this: Yes! Why was it removed? > You need to edit /boot/boot.ini and add / replace it in this line: > setenv overlays "i2c0 i2c1 hktft-cs-ogst That line was already in the file > Also there is a problem here: > ext4load mmc 0:1 0x60000000 /boot/dtb/overlays/${overlay}.dtbo Ok, but to change the filepath to /boot/dtb/${overlay}.dtbo, I would need to put the .dtbo files back into /boot/dtb/, right?

Thanks. I followed your instructions, and selected every overlay in the list, then rebooted. The motd is still saying it's an XU4 board. /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v24.11.1 for Odroid XU4 running Armbian Linux 6.6.60-current-odroidxu4 I also have /boot/armbianEnv.txt: line 2: hktft35: command not found when saving these options in armbian-config. # cat /boot/armbianEnv.txt board_name=hc1 fdt_overlays=ads7846 hktft32 hktft35 hktft-cs-ogst i2c0 i2c1 onewire spi0 sx865x-i2c1 uart0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u # ls /boot/dtb/overlay/ ads7846.dtbo hktft35.dtbo i2c0.dtbo onewire.dtbo sx865x-i2c1.dtbo hktft32.dtbo hktft-cs-ogst.dtbo i2c1.dtbo spi0.dtbo uart0.dtbo

I've been running Armbian on an Odroid HC1 board for some time now. We've just had a kernel upgrade and it now boots as an XU4 according to the motd. This used to be changeable with armbian-config (I did this regularly on kernel updates). But, with the new armbian-config I can't find a way to do this any more. *edit A bit more info Running SY017 in armbian-config gives an empty list, and I get this error: ls: cannot access '/boot/dtb/overlay/*.dtbo': No such file or directory In fact /boot/dtb/overlay/ does not exist

Apologies. It's an old build updated to bullseye. ___ _ _ _ _ _ ____ _ / _ \ __| |_ __ ___ (_) __| | | | | |/ ___/ | | | | |/ _` | '__/ _ \| |/ _` | | |_| | | | | | |_| | (_| | | | (_) | | (_| | | _ | |___| | \___/ \__,_|_| \___/|_|\__,_| |_| |_|\____|_| Welcome to Armbian 22.11.1 Bullseye with Linux 5.4.225-odroidxu4 System load: 1% Up time: 2 days 3:00 Memory usage: 10% of 1.94G Zram usage: 5% of 0.97G IP: 81.187.18.18 CPU temp: 28°C Usage of /: 6% of 29G storage/: 57% of 916G RX today: Error: Interface "--oneline" not found in database. [ General system configuration (beta): armbian-config ] Last login: Mon Dec 5 15:46:03 2022 from 2001:8b0:1312:0:f7c9:e052:f864:973d admin@henry:~$ sudo armbianmonitor -u [sudo] password for admin: System diagnosis information will now be uploaded to https://paste.armbian.com/mulukovagu Please post the URL in the forum where you've been asked for.

$ systemctl status ● henry State: degraded Jobs: 0 queued Failed: 1 units Since: Sat 2022-12-03 10:19:04 GMT; 24h ago $ systemctl list-units --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● logrotate.service loaded failed failed Rotate log files $ journalctl -u logrotate.service Journal file /var/log/journal/c87d7c4913d949949100f089ec48b092/system.journal is truncated, ignoring file. -- Journal begins at Sun 2022-12-04 00:00:06 GMT, ends at Sun 2022-12-04 10:33:57 GMT. -- Dec 04 00:00:06 henry armbian-ramlog[2714]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2715]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2716]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2717]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2718]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2719]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2720]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2721]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2722]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry systemd[1]: logrotate.service: Control process exited, code=exited, status=1/FAILURE Dec 04 00:00:06 henry systemd[1]: logrotate.service: Failed with result 'exit-code'. Dec 04 00:00:06 henry systemd[1]: Failed to start Rotate log files. Dec 04 00:00:06 henry systemd[1]: logrotate.service: Consumed 5.879s CPU time.