* Remove create_desktop_package.sh for rk3318 board from
config/optional, clearing the whole directory tree
* Add an extension to implement serverflags workaround
for X.Org and Lima driver not being autodetected
* Fix rk3318-box and rk322x family to use extension in place
of 40-serverflags.conf bsp file
Original version destroyed journal on command postrotate as files in /var/log.hdd/journal are overwritten by cat. With the patch journal is not damaged anymore.
This was going to be used if building the bootloader from external
source did not work. As this did work we never needed this blob,
remove it.
Signed-off-by: Andrew Davis <afd@ti.com>
Sometimes we need to fix minor issues like changing the key or fixing other small problem on live OS. We can ship this as a part of BSP package, but its handling should be made easy.
This downloads script from CDN, verify its signature and executes after apt upgrade starts installing packages.
* Record patch output to syslog
* Enable armbian-live-patch as additional service and run patch mechanism at startup
* Additional security check
- this allows user to enter UMS mode from GRUB
- for usage with the `initramfs-usb-gadget-ums` extension
- has no effect unless `initramfs-usb-gadget-ums` extension is enabled together with `grub-with-dtb`
Improve naming confusion by changing build framework defaults. Set framework defaults VENDOR to Armbian-unofficial for self build images. Unsupported boards and unsupported distribution have framework defaults, except VENDOR and VENDORURL. We build images with predefined values.
- this should make `09_linux_with_dtb.sh` work across all RELEASE's, `sid` and `mantic` included
- extra: if `grub-mkconfig` (`update-grub`) fails, show all involved source files
The service is only enabled by default on Vim4 as that board heats
a lot and a fan is absolutely necessary. Service will be available
on vim1s as well and if someone has purchased the fan for it, they
would be able to enable it themselves.
The service is only added for legacy kernel right now as I am not
sure if the upcoming 5.15 kernel will have same sysfs interface for
fan.
ifconfig is no longer included in a default install of Armbian Bookworm, causing armbian-firstrun-config to silently fail when attempting to retrieve a list of network adapters. Using nmcli instead.
A change to ledtrig_netdev causes the boot to fail on Orangepi-r1plus-lts and possibly other boards. The board boots and LED netdev trigger works if service is modified to use After=timers.target.
Backport DTS/DTSI changes from linux-6.4.y to 6.1.y
Add meson64-reboot driver to all boards
Add board: ODROID N2L
Add uart_A uart_AO_B uart_B uart_C where appropriate
U-Boot v2023.07.02: ODROID N2/N2L/N2Plus/C4
Meson64-reboot driver: (source: tobetter)
While the current meson64-reboot driver is cleaner and doesn't
depend on modding other kernel sources, its functionality leaves
much to be desired. One example can be found in the ODROID C4.
Using the current driver, the board will not properly power off,
leaving the POWER LED still on. The new driver powers off the unit
completely.
Fan control: (ODROID N2L/N2PLus)
Added service and script for controlling the trip point.
fanctrl: arguments: 65 55 45 35 25 menu run
┌──┤ Fan Control ├──┐
│ │
│ 6) 65°C │
│ 5) 55°C │
│ 4) 45°C │
│ 3) 35°C │
│ 2) 25°C │
│ E) Exit .. │
│ │
│ │
│ <Ok> │
│ │
└───────────────────┘
NOTES: (N2L/HC4): I do not own the units so I can't run tests.
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
Removed WIP status
Added CONFIG_R8169=m to defconfig(s) (eth support)
Modified and added additional patches (linux 6.1 / 6.4)
U-Boot v2023.07.2 (dropped v2022.10)
Upstream BT FW (rtl8822cs) is now shared between CM4IO and M2s
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
- introduce hooks `grub_early_config`, `grub_pre_install` and `grub_late_config`
- what we see here is an extension that itself has hooks, that just works
- introduce extension `grub-with-dtb`, which
- enables `grub` extension
- requires `BOOT_FDT_FILE` to be set
- includes `/etc/armbian-grub-with-dtb` with `BOOT_FDT_FILE=` in the bsp-cli
- includes `/etc/kernel/postinst.d/armbian-grub-with-dtb` in the bsp-cli
- which reads the above and creates links for `/boot/armbian-dtb-<version>` when deploying deb's
- adds implementations of the hooks above to
- replace the distro's `10_linux` with our own `09_linux_with_dtb`
- which looks for `/boot/armbian-dtb-<version>`
- forcibly run `/etc/kernel/postinst.d/armbian-grub-with-dtb` during image build, since bsp-cli is installed after linux-image
- uefi-arm64: enable GRUB wallpaper by setting `UEFI_GRUB_TERMINAL=gfxterm`
- force GRUB_FONT so Ubuntu is not confused and gfxterm (incl wallpaper) finally works
* armbian-install: The log file should be named identical to the originally called install script
- the log file should be named as:
- /var/log/armbian-install.log if script armbian-install was originally called
- /var/log/nand-sata-install.log
- same for directory /usr/lib/nand-sata-install:
- rename this directory to /usr/lib/armbian-install
- create a symbolic link nand-sata-install to this folder for backward compatibility
in a subsequent commit
- abort script armbian-install with an error message:
- if file ${EX_LIST} does not exist
- if dir ${BOOTLOADER} does not exist
- remove the "beta" from the version title of armbian-install
* Add symlink /usr/lib/nand-sata-install to /usr/lib/armbian-install
In commit 0aa61abe7 (armbian-audio-config: Massively speed up script)
this script was changed to not call amixer for each control, but just
once for each card, feeding commands for many controls in one invocation
with the `--stdin` option.
In that commit, two errors were introduced:
- Controls that were intended to be muted were turned on instead. This
affects the "CD", "Mic" and "Internal Speaker" controls.
This occured because there is a helper shell function whose arguments
were renumbered, but the last argument kept the old numbering,
keeping it always at the default value of "on", even when it should
have been "mute".
- Controls with a space in their name would be ignored. In the original
script, arguments (including these names) were quoted and passed
separately to the `amixer` command. Now, they are quoted when passed
to `echo`, but that produces an unstructured line with the quoting
removed that can no longer be correctly parsed by amixer for names
with spaces.
This commit fixes both problems be correctly numbering the arguments and
adding an additional layer of quoting.
- this issue was introduced by commit 7e9ebe1
- the variable sduuid is supposed to start with "UUID="
- fixed now by prepending UUID= to $sduuid, if the "raw" $sduuid is not empty
closes AR-1611
Previously, the u-boot binary files used to chainload u-boot for the
amlogic tv boxes were the ones produced by balbes150 in his old
tv box builds. There was no source code for them.
This commit is the first to convert from those old binary files
to newly built ones along with a u-boot patch file and instructions
on how to build/rebuild them. Eventually this needs to be incorporated into
the build framework to automate it. But for now one step at a time.
Changes to be committed:
new file: packages/bsp/aml-s9xx-box/boot/build-u-boot/readme.txt
new file: packages/bsp/aml-s9xx-box/boot/build-u-boot/u-boot-s905x-s912.patch
deleted: packages/bsp/aml-s9xx-box/boot/u-boot-readme.txt
modified: packages/bsp/aml-s9xx-box/boot/u-boot-s905x-s912
Co-authored-by: Igor Pečovnik <igor@armbian.com>
This is needed to bring this board in line with the expectations of
the new main build (armbian-next), which dropped uImage from meson64
kernel packages.
Changes to be committed:
modified: packages/bsp/aml-s9xx-box/boot/extlinux/extlinux.conf
* Don't display RX today: Error: No interface matching when wrong NIC is detected
* Improve checking
* Address shellcheck problem
* Switch conditions order
* Fix variable $root_partition_device to be a device path
- variable $root_partition_device is intended to be a
device path as /dev/$root_partition_device_name
* Fix determination and usage of variable $sduuid
- a) lookup mmc devices excluding the mmc device probably providing
the current root partition
- b) if there is no sduuid determined by this lookup,
then lookup any mmc partition matching /dev/mmcblk*p1
- c) move the sduuid calculation to the script header
to enable usage for scenario selection filtering
- d) hide installation scenario #1 selection,
if $sduuid is empty, since $sduuid is essential for that scenario
* Hide current root partition device from destination selection
- add new variable $root_partition_name
- use this variable to filter current root partition
from destination selection in check_partitions()
* Fix behavior in case of no available partition
- The logic in check_partitions() in case of no available
partition is improved not to fail for a hidden reason
and UX for fresh disk devices is improved
- Fix the calculation of $FREE_SPACE for devices without or
with an empty partition table
- Ask the user to proceed AFTER the minimum free capacity
required is verified
- Improve the logic for auto-creating initial partitions
as follows:
1. Check for a minimum free space of 4GB for a partition
2. Ask user to proceed with auto-created partition(s) or not
3. Distinguish between UEFI and non UEFI device
4. Create a partition of full free size for non UEFI devices also
* Add support for MTD char driven flash
- replace $spicheck by $mtdcheck
- add probable MTD char device partitions to $mtdcheck
- update comments and dialog content:
- replace "SPI Flash" by "MTD Flash"
- replace call of "create_armbian 'spi' ..." by "create_armbian 'mtd' ..."
- update description for /dev/nand1 /dev/nand2 as "legacy SUNXI NAND"
- additional parameters passed to import function "write_uboot_platform_mtd":
$3 - Log file name
$4 - SPACE separated list of all MTD device partition(s)
- function check_partitions():
- remove file system filter on lsblk commands
for listing probable target partitions
- fix typo "Destnation" -> "Destination"
- fix indentation on if scopes
fixes#4576
There is no way to support this on s905 TV Boxes while reusing the
android u-boot as the android uboot on s905 conflicts with the partition
table location of standard mainline linux.
Changes to be committed:
modified: config/sources/families/meson-gxl.conf
deleted: packages/bsp/aml-s9xx-box/root/install-aml-s905-emmc.sh
