- we might want to have different welcome colors for stable and nightly images
- this adds another branding option alongside with VENDOR, VENDORURL, VENDORSUPPORT, ...
fix: /usr/lib/armbian/armbian-firstlogin: line 406:
break: only meaningful in a `for', `while', or `until' loop
Signed-off-by: Martin Schmiedel <Martin.Schmiedel@tq-group.com>
While it is unusual to run both NetworkManager and systemd-networkd
simultaneiously and doing so can cause startup problems, there is
nothing inherently wrong with doing so: the services are not
incompatible and some people run both, each managing different
interfaces.
The Armbian build framework enables one or the other but not both.
Therefore, if both are enabled at first login, it is probably because
the user has manually modified the image. In this case, trust that the
user knows what they are doing and don't disable one of them.
NetworkManager and systemd-networkd should never both be enabled
at the same time. In this case, disable systemd-networkd, with
message to the user that this is being done.
Avoid waiting for the NetworkManager-wait-online or
systemd-networkd-wait-online service to complete in the midst of
prompting for root account password.
- switch MOTD download to new central location https://github.armbian.com/
- move cronjob for MOTD download from weekly to daily
- change mord defaults, remove clear from defaults
Scanning accesspoints requires an activated wifi device.
Networkd does not activate it (only NetworkManager does so).
As a result, firstlogin is not able to configure and use wifi on minimal
images, as only Server and Desktop images have NetworkManeger installed.
Activating the wifi device using "ip link set ${WIFI_DEVICE} up" before
scanning fixes this.
(And can safely be done - there is no problem activating it multiple
times, as it is the case with NetworkManager installed.)
Option "--connect-timeout" used to determine external IP covers only
connection phase. Curl may "hans" in a different phase and this makes
login to the system impossible if MOTD "header" module enabled.
Using "--max-time" is more reliable and prevents hanging for hours.
Fixes issue https://github.com/armbian/build/issues/7753
Signed-off-by: Uladzimir Bely <wiselord1983@gmail.com>
NCM has advantages over RNDIS and postmarketOS has toggled
to it 2 years ago. And I have tested it can work with common
linux and window10.
I also made some changes to let this script run inside intramfs.
And the systemd service can run well after rootfs is loaded.
* rockchip64: add `BOOT_SCENARIO=binman` for mainline u-boot
- drop special handling for 3308's `legacy` branch
- rpardini: note how SPI/mtd is not yet supported for this scenario
Co-authored-by: Ricardo Pardini <ricardo@pardini.net> (squash/splits, shellfmt)
* `rock-s0`/`rockpi-s`: use `BOOT_SCENARIO=binman`; move blobs to armbian/rkbin
- Move rk3308 boot blobs to armbian/rkbin
- delete obsolete ones
- Alter rock-s0 and rockpi-s to use the new "binman" BOOT_SCENARIO
Co-authored-by: Ricardo Pardini <ricardo@pardini.net> (shellfmt; small fixes; squashes)
* Add a list of BASH shell aliases and merge them with ohmyZSH aliases
* Add command armbian-upgrade to the BSP which executes update + upgrade
* Display armbian-upgrade only if there are upgrades
* Generate empty folder where will store data. This doesn't exists at early start
* Move armbian-install to /usr/bin and autoexecute sudo
- remove patches (already mainlined)
- while at it, rename BOARD_MAINTAINER to the actual GitHub profile
Signed-off-by: Martin Schmiedel <Martin.Schmiedel@tq-group.com>
