Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

David A

Members
  • Joined

  • Last visited

Everything posted by David A

  1. Same issue with Armbian 25 / kernel 6.6 😞
  2. @Igor It did. Thank you. The final PR will be here: https://github.com/armbian/build/pull/7216
  3. Hi, Context systemd's cloud-init.target and armbian-firstrun.service will be started concurrently (both are wanted by multi-user.target). Both will try to create SSH host keys by default: - armbian-firstrun will always delete SSH host keys and then generate new ones - cloud-init.target (by default) will always delete SSH host keys and then generate new ones. Problem When one must run armbian-firstrun and cloud-init, there is no deterministic ordering between the 2 files execution and therefore no one can guarantee which will be last to setup host keys. In my current scenario, host keys are explicitly setup in cloud-init and I would expect armbian-firstrun to not delete keys + no ssh host key generation. Proposed Solution armbian-firstrun support user defined config to control SSH host keys deletion + generation: - on: ssh host key deleted + generated (compatibility: current armbian behaviour) - off: no ssh key deleted + no ssh host key generated. Allow cloud-init to take over this behaviour deterministically. Question I am seeking guidance on where the user config setting should be added. Then I can write the if/else condition in the armbian-firstrun script.
  4. Preferred to ask as sometimes (but not an Armbian) maintainers are reluctant to increase the project's scope. Here it is: https://github.com/armbian/build/pull/6307
  5. Hi community, Context I build my own custom Arabian image on arm 32bit (prod), and experimenting running the following armbian image configuration on Qemu with console/serial only support for uefi-x86 and uefi-arm64 boards to speed up development/test. Problem I stumble upon something odd: both "uefi-*" boards are configured to only run GRUB in gfxterm mode ONLY. BOARD: uefi-86 -> BOARDFAMILY="uefi-x86". -> UEFI_GRUB_TERMINAL="gfxterm" [0] BOARD: uefi-arm64 -> BOARDFAMILY="uefi-arm64". -> UEFI_GRUB_TERMINAL="gfxterm" [1] [0] https://github.com/armbian/build/blob/2afd8fe9bb8aca33a2a3913e931fc43c43c8e309/config/sources/families/uefi-x86.conf#L11 [1] https://github.com/armbian/build/blob/2afd8fe9bb8aca33a2a3913e931fc43c43c8e309/config/sources/families/uefi-arm64.conf#L10 Image built from these boards should be runnable as CLI image (no gui) or Desktop image (gui). However, when running with qemu -nographic ... these image can't boot up to a working shell and produce an error: "GRUB: gfxterm is not supported" Proposed change I would like to submit a patch to change UEFI_GRUB_TERMINAL to "gfxterm vga_text console serial" to cover a large set of virtualised hardware configurations. 1. Is this something you guys are interested in ? 2. Does this fix need more than the proposed change to achieve the desired objective ? Thanks

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.