Jump to content

Search the Community

Showing results for tags 'documentation'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Volunteering opportunities
  • Part time jobs

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

Found 9 results

  1. Here will be published all the tweaks for the Youyeetoo YY3568 board to enter the mainline with armbian. Images Kernel Vendor 6.1: https://github.com/armbian/linux-rockchip/commit/27a98750790114235c72e8420d45f44eff210461 Overlays: https://github.com/armbian/linux-rockchip/commit/18f066190842fc6bd509662a2d19588eb9f04612 Kernel Vendor 5.1: https://github.com/armbian/linux-rockchip/commit/b5964f997e2267802db0a965e66ec299b8a1f437
  2. Hello, My spare R4S is currently running the Rolling releases with Armbian Linux v6.12 Trixie image It seems /etc/resolved.conf got filled by at least /etc/systemd/resolved.conf [ global ] /etc/netplan/armbian.yaml [ per link/ ethernets: ] However I miss from which script the IPv6 nameservers are gathered and added as currently /etc/resolv.conf shows something like this and Iike to have just the ones from [ global ]: ( Please note I removed nameservers from the yaml file already ) # operation for /etc/resolv.conf. nameserver 127.0.0.1 nameserver ::1 nameserver fda8:5894:4e78:0:xxxx:xxxx:xxxx:xxxx # Too many DNS servers configured, the following entries may be ignored. nameserver 2001:1c00:2a02:ba00:xxxx:xxxx:xxxx:xxxx nameserver fda8:5894:4e78:0:xxxx:xxxx:xxxx:xxxx nameserver 2001:1c00:2a02:ba00:xxxx:xxxx:xxxx:xxxx search . Aiming for just the localhost nameservers in resolv.conf as unbound and pihole ( +wireguard ) will be running on the SBC only ... Hoping one can guide me as I could not find it from the Networking - Armbian Documentation TiA!
  3. The page at https://docs.armbian.com/Process_Release-Model/ has a link entitled "Release Testing", but the link doesn't seem to go anywhere. Is there a document on the release testing process?
  4. I would like to change the image types at https://www.armbian.com/mks-klipad50/ so that Debian Server images ("full-cli-stable-debian") for current and edge kernels are built for this board. Optimal would be, if the "Desktop" and "Minimal/IOT" were omitted, so that only the Server images appear. Something similar is done for "aml-s9xx-box" here: https://github.com/armbian/os/blob/main/userpatches/targets-release-community-maintained.template#L57 So my approach for enabling Server images would be https://github.com/armbian/os/compare/main...torte71:armbian-os:main as PR. But I am not sure a) if adding boards directly to the "items:" property is intended at all (or if it is e.g. just an unwanted workaround) b) if my changes work at all: I don't see a way to test it first c) how to disable generation of Desktop and Minimal/IOT images (but that point is optional, esp. if the changes would become too big) Could someone please give me some tipps for that?
  5. The "Edit Device" wordpress template ("https://www.armbian.com/wp-admin/...") has some input fields that I would like to understand. I am trying to complete it for the MKS-Klipad50 (https://www.armbian.com/mks-klipad50). (It's a CSC board, not standard support - if that matters.) Following fields are unclear to me: "Compatible" What is the meaning and expected syntax? Is that something like devices using the same kernel, but different setup/devicetree files? "Expose kernels" / "How many kernels to expose?" Is this related to the "Kernels" table (see below), like how many rows to use? "Kernels" Is it required adding rows to have images automatically generated and appear as download links on the device page? Or are these options just required for additional non-standard images? Is it better to leave it empty? Could someone please shed some light on the meaning of these fields?
  6. I downloaded and installed the Ubuntu noble image. Was this the correct one for my Raspberry Pi400 if I wanted the rolling release version? Thanks
  7. until
    Didier J. will be leading this meeting and sharing progress on the documentation tasks. Anyone interested in the documentation process and content can join this meeting!
  8. How to I generate `.img` files? When I run `.compile` I end up with `.deb` files. I've been looking through the scripts but there are so many of them and I want to get to how to do this without having to use commands like: find . -name '*.sh' -print0 | xargs -0 grep compile_uboot | less for a long time. Thank you
  9. hi I've been using the flag compile.sh PREFER_DOCKER=no while building in a systemd-nspawn container: Building Armbian using Ubuntu (jammy) in a systemd-nspawn container This time I managed to make a complete successful build with my work arounds for loop devices in systemd nspawn. However, the flag PREFER_DOCKER=no Didn't seem to be documented in the build options https://docs.armbian.com/Developer-Guide_Build-Options/ can the documentation be updated to add PREFER_DOCKER=no flag (at least under 'advanced users') ? note that it isn't possible to run docker normally within systemd-nspawn or that it'd require all those workarounds such as patching and using the host docker server which defeats the purpose of using docker. rather systemd-nspawn is the container to at least decouple the build environment from the host os environment (which can be a different linux distribution, I'm doing so from OpenSuse https://www.opensuse.org/), with the unfortunate caveat that loop devices still requires a workaround.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines