Armbian build framework

Greetings, I'm currently modifying the Armbian build system, making it easier to add new desktop environments and application groups. This architecture is subject to heavy modifications until it is merged with the current Armbian build system. A repository with the modified build system is available here : https://github.com/Miouyouyou/armbian-desktop Currently, I only tested adding Ubuntu Focal + XFCE and application groups, since I had to make sure that the postinst and create_desktop_package.sh were actually aggregated correctly, now that they're split into multiple files, and, for comparison, we only have such …

Release Candidate Code Freeze Date: TBD Release Planning Meeting Date: 2021-10-16 1400GMT Release Date: TDB Release Candidate Branch Link: TBD Release Changelog: TBD Release Coordinator: @igor We are in doubts to make this release at all due to overall project strengthening and focus on securing maintainers and cut HW which doesn't have it. Alternative idea is to produce a release as is with minimal changes and focus on bug fixing straight from today. Meeting is this Saturday, to get on common grounds. @Igor@Werner @TonyMac32 @martinayotte@piter75 @ning@Myy@balbes150 @sfx2000 @ebin-dev@chwe@gprovost@aprayoga@5kft@JMCC@go…

In the past few weeks I have been working to improve processes of deploying our work. Scripts that runs in the background are combination of tools that are build into the main tool and additional scripts that run on the server. They are (will be) summed in a (private) scripts repository, but the functioning - which could be interested for any maintainer - are summed in this document: https://docs.armbian.com/Process_CI/ Welcome to add your ideas, especially for the merge request part, which remain unchanged. Otherwise its planned to extend this automation to execute tests, similar or the one from @William Bonnet on virtual image (image already boots insit…

https://armbian.atlassian.net/browse/AR-702 (Don't worry I only tagged it for the 21.08 Release -- so we have plenty of time to think this through) Armbian provides a lot of extra device tree improvements for support. Currently they’re added to the build system via patches, which is very difficult to follow. We need a new approach that makes our device tree files and overlays more visible within the Armbian-build framework.. as well as make it easier for us to upstream our faces to SoC maintainer kernel trees. Obviously lots to figure out here. Tagging a few.. please tag more @martinayotte @TonyMac32@Igor@Rich Ne…

note: This is from a previous thread about testing, I accidentally moved it, and this was the only way to resume the conversation --- Just kicking off a thread here to talk about different ideas around testing. It would be great if the community could help test more.,,, but what would it look like.... maybe end users can burn a test image and run a test script. the script could do cool things like: * spi loopback test * check for healthy kernel modules * look for dmesg errors * test wifi * test ethernet * test audio? * even run a phoronix test of somesort to validate a particular feature. Are there any simple circuit diagrams people could desi…

When performing a build using this key (last commit, MASTER branch) I get an error. Is this a local error in my build environment, or are others observing similar behavior ? Pre-build without CLEAN_LEVEL="" passes without errors. The error occurs during a subsequent build with saving (using) already buils packages.

Can we add .editorconfig to https://github.com/armbian/build ?!

1. What is the purpose when compilation errors are sent to a common output and then branched to a file? It turns out a million lines. It is reasonable to have only compiler error messages. 2. What is the purpose when the kernel-source package is built with include the folder /.git/? It is not traditional 3. Why folder with sources not cleared fully before compilation? git commands: git reset --hard HEAD; git clean -df guarantee a clean sheet before starting work

Hi, I'm trying to compile a kernel using the procedure described here: https://github.com/igorpecovnik/lib I've set the KERNEL_ONLY="yes" in the compile.sh script, but I get the following error after a while I wonder what i've missed or if there's some other issues. I've tried both the master branch and v2016.08 tag, same result. My system lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial Linux apu 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Any pointers would be much appreciated, Thanks …

Would it be possible to add an option build parameter, something along the lines of BUILD_MINIMAL_DISTRO to the compile system? Allowing it as a command line option to compile.sh would be great as well. The purpose of the new option would be to use an alternative PAKETKI variable with only the packages absolutely required for running the system and configuring networking (ideally Ethernet and WiFI) without the bloat of bluez, stress etc. It would also be great if there was a call after install_external_applications to a user provided script that allows the user to install any additional packages that they require. There may be reasons not to do this and / or …

Hello, with an old image "Armbian_5.10_Bananapim2_Debian_jessie_4.5.2_nfsboot.raw" I could stop the boot process and use the u-boot dhcp command and the Pi gets propper values from my DHCP Server. U-Boot SPL 2016.01-armbian (Apr 28 2016 - 10:35:52) DRAM: 1024 MiB Trying to boot from MMC U-Boot 2016.01-armbian (Apr 28 2016 - 10:35:52 +0000) Allwinner Technology CPU: Allwinner A31s (SUN6I) DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0) In: serial Out: vga Err: vga Net: eth0: ethernet@01c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0…

Hello, I understand plainly zador.blood.stain for keeping the one-liner version of compile.sh I am dumb guy with low memory in brain and I prefer a config file per board (I am using one file for XU4, one for OPi+2E, one for Lamobo-R1, one generic file for playing) instead of a file with plenty of one liners for compile.sh But I have *just* used the plain original (updated) version of Armbian lib and I felt coming back to the Age of ICE (everything is root and sudo, no possible proper CTRL-C of compile.sh to restore all files with user id&group $HOME/.ccache is root, impossible to use RSA keys for forked version of lib (to push/pull) -- unless using the RSA…

it is WIP odroid xu3 & xu4 have 4 Cortex-A7 cores max=1400MHz 4 Cortex-A15 cores max=2000MHz in HMP mode (patched kernel 3.10), 4 cores can run @1.4GHz and 4 cores @2GHz Cf. Heterogeneous Multi-Processing (HMP) solution The ODROID-XU4, equipped with four big cores (ARM® Cortex® -A15™ up to 2.0GHz) and four small cores (ARM® Cortex® -A7™ up to 1.4 GHz), provides improved processing capabilities while maintaining the most efficient power consumption available. With the big.LITTLE™ HMP solution, the Exynos-5422 can utilize a maximum of all eight cores to manage computationally intensive tasks.

I am trying to configure "next" with linux-vanilla (4.6.2) and built an Armbian image then booted from SDcard (removing my eMMC) So far, Samsung OSG provided examples of vanilla kernel @jobenvil tested 4.6 kernel but compiled on board WITH partition using UUID instead of /dev/mmc I got 4 cores in the "basic" model (4 little => 4 BIG), network, HDD issue: mixing uboot 2012.07 and vanilla kernel it seems /dev/mmcblk0 doesn't exist for uboot 2012 only boot.ini works with root=/dev/mmcblk1p2 to quick fix the problem I put /dev/mmcblk1p2 for root partition in boot.ini * I know how to manipulate UUID and partition => is it possible to put spec…

I have pushed some changes for XU4 with the help of so many internet sources (thanks!) - uboot 2016.05 - vanilla kernel (4.7.6 as of now) - single partition (using the LABEL=rootfs for booting) - SD & eMMC for eMMC, burn the image on both a SD card & eMMC first, boot with SD card to write files on mmcblk0boot0 partition, then cd /usr/lib/linux-u-boot-next-odroidxu4_5.21-GRO_armhf (probably remove -GRO) -rw-r--r-- 1 root root 15616 oct. 1 01:58 bl1.bin.hardkernel -rw-r--r-- 1 root root 14592 oct. 1 01:58 bl2.bin.hardkernel.1mb_uboot -rw-r--r-- 1 root root 1807 oct. 1 01:58 sd_fusing.sh -rw-r--r-- 1 root root 262144 oct. 1 01:58 tzsw.bin.hard…

please, is it useful if I would test MBR/PARTUUID for XU4 (as Zador is thinking of)? (instead of the former LABEL testing I did for SD/eMMC for next) in case I am on the proper path as of http://forum.armbian.com/index.php/topic/2454-fel-mass-storage-or-writing-images-directly-to-emmc/?p=18115

Hey Guys, following this very closely for a couple of days now, and I want to starting putting my two cents in the bucket. I work with the (Olimex) A13-SOM and got some working images. All quiet hacky so I would love to add the configuration to the installer script to get some clean build images. Where to start? What info do I need? I want to do both legacy kernel(I use LCD output) and vanilla kernel. Booli

Yes, sure. Go ahead ... BTW: can you try to compile U-boot for Armada ... it's failing for me on two different machines and it's suppose to work.

when build armbian via docker "proces will create and run a named Docker container armbian with 2 named volumes armbian-cache and armbian-ccache" and store it in /var. My root amount is not over 40Gb and it will be good thing to store armbian-cache and armbian-ccache in different place

Hello, I am new to armbian and it building environment. I had to start from ground and stumbled across some unclear / wrong point in the documentation. [EDIT: I already managed to build an running image. This Thread is about the documentation] So i just want to point them out, not to harm anybody, just to tell what happened to me. Perhaps all of it is just because i didn't followed the documentation correctly. If that's the case i like to apologize for disturbing. 1. https://docs.armbian.com/Developer-Guide_Using-Vagrant/#virtualbox-version suggestst to do: > vagrant plugin install vagrant-disksize …

Rebuilding kernel several times in a row, made some changes, that would be nice to have in build script by default, and also some thoughts on custom kernel patches. 1.Option to not overwrite kernel config before compilation. Example: setting KERNEL_KEEP_CONFIG="yes" in build.sh Changes (common.sh): # use proven config if [ "$KERNEL_KEEP_CONFIG" != "yes" ]; then cp $SRC/lib/config/$LINUXCONFIG.config $SOURCES/$LINUXSOURCE/.config; fi 2. Option to use ccache for kernel compilation (at least). ccache can be set by creating symlinks for cross-compiling tools, but having an option in build script is more useful and easier IMHO. Example: setting USE_CCACHE="yes" in bu…

Hello, I have seen a patch for emmc/nand with UUID, it looks interesting. Is anything planned sooner or later to use UUID in /etc/fstab in image building process, please? Or is it something to dig in? (I am looking for a solution for Odroid XU4 next to bypass the ANTIC uboot 2012.07) Thanks!

Hello, I try to use the Armbian build framework to generate a debian package with modified kernel, generated packages.deb works fine, but the compiled kernel is everytime the default and not mine. I use: ./compile.sh KERNEL_CONFIGURE=yes KERNEL_KEEP_CONFIG=no and then load my kernel_config but the result is everytime the default kernel, the .config become change then my .config I also try to bypass the problem by adding immutable attribute to my personalized .config (chattr +i ./.config) but the script crash: │ /home/maxi/sources/linux-sun8i/sun8i/scripts/kconfig/Makefile:33: recipe for target 'silentoldconfig' failed …

hello, I would suggest a quick fix of "compile.sh" to do the "git pull" of "lib" before sudo why? because .git/FETCH_HEAD file turns owned by root.root & zador.blood.stain has tried to limit being "root" all the time in the VM

Hi, I want a clean Armbian image for BPi without systemd. I pulled the actual Armbian 5.02, elected jessie and vanilla/next kernel (4.4.2) and checked SYSTEMD settings: gerd@development ~/projekte/armbian/lib (git)-[master] % find ./ -type f -exec grep -H SYSTEMD {} \; ./configuration.sh: SYSTEMD="no" # Enable or disable systemd on Jessie in debootstrap process but systemd is still active in the created image. Is there a way to get rid off it ? I saw in the blog that systemd is now default for jessie Regards Gerd

There's a typo in nfs-boot.cmd.template, line 9. s/nfsroot={nfs_root}/nfsroot=${nfs_root}/ Nevertheless thanks for the template. Regards, Steve

I created a new image for my Odroid C2 with the most current version of Armbian 5.26. Configuration was pretty much standard, except BOOTSIZE=0 and ROOTFS_TYPE=ext4. The image works fine, if dumped to a sdcard. When dumping it to an emmc card, the system boots up, but 'find / > /dev/null' leads to a filesystem error: [ 52.799920] EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:913: inode #41001: block 12032: comm find: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=8213, rec_len=4097, name_len=0 [ 52.812862] EXT4-fs (mmcblk0p1): Remounting filesystem read-only Behavior is deterministic - I tried with two different boards and two diff…

Hello I recently updated the kernel of Jessie on the Od-C2: # uname -a Linux odroidc2 3.14.65-odroidc2 #33 SMP PREEMPT Sat Mar 26 14:50:37 CET 2016 aarch64 GNU/Linux Consequently, with this new environment, the wifi connection fails: # iw wlan0 scan nl80211 not found. when started mannually, the wpa_supplicant starts +/-: # wpa_supplicant -B -i wlan0 -O /var/run/wpa_supplicant -c /etc/wpa_supplicant.conf Successfully initialized wpa_supplicant But: # ifup wlan0 wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 Failed to bring up wlan0. # iwconfig returns: eth0 no wireless exte…

Hi there, my odroidc1 somehow died last month after updating to 5.3 test kernel so I decided to build new images from scratch starting from master. I did not touch any configuration and I choose to build the classical server image. Debian Buster boot but I cannot get any network Ubuntu 18.04 does not even boot with a u-boot error (see below) Ubuntu 19.10 does not even boot with a u-boot error (see below) Here it is the u-boot log of Ubuntu images: Does anyone have an idea on what is the problem and how to fix it? Thanks in advance *Ciao Piero

I tried to compile any distro for the first time, so I'm a total n00b here (used Oracle VirtualBox on a Win x64 machine, Ubuntu 10.04.02 x64)... They seem to be compiled fine. Moved the result images, written to new SD Cards with Etcher... Legacy Ubuntu server did boot. Legacy Ubuntu Desktop did not boot (even red/green lights did not light up). Can you give me some starting points or links about how to deal with this issue? Thank you in advance... BTW: I'm giving a shot to this to get rid of unnecessary SW installed in the desktop version, such as LibreOffice etc... I also don't know if this is possible...

I'm doing a build inside a Docker container (Ubuntu Xenial 16.04; started with --privileged) and I've tried several builds but all of them fail. The .img file gets created but after copying to the SD card they always fail (unrecognized file system). Here's the output of compile.sh: [ o.k. ] Creating board support package [ orangepizero default ] [ .... ] Fingerprinting [ o.k. ] Building package [ linux-xenial-root-orangepizero ] [ o.k. ] Starting rootfs and image building process for [ orangepizero xenial ] [ o.k. ] Extracting xenial-ng-armhf.50a...4c9.tgz [ 0 days old ] xenial-ng-armhf.50a...4c9.tgz: 75.6MiB [ 204MiB/s] [=======================================…

Hi Board, I have submitted a PR a few minutes ago to Build repo (https://github.com/armbian/build/pull/927) removing some drivers that WILL NOT load in RK3288, because they are specific to other SoCs / Architectures. I also took the opportunity to convert a batch of drivers / machines to modules, in order to alleviate the kernel size and squeeze some performance (because some of the loaded stuffs does effectively consumes CPU). Well, that's what modules are meant for, right? The patch was crafted to DEV version. Need more extensive Tinkerboard tests (did not test the GUI) and MiQi (not tested at all, I lack the hardware). Ha…

Hi, I noticed that "install.log" was missing the beginning of the process, it starts at building the .deb for u-boot. There is one ">" missing in common.sh: diff --git a/common.sh b/common.sh index 503a3ab..920ba38 100644 --- a/common.sh +++ b/common.sh @@ -90,7 +90,7 @@ compile_uboot (){ cd $DEST/debs display_alert "Target directory" "$DEST/debs/" "info" display_alert "Building deb" "$uboot_name.deb" "info" - dpkg -b $uboot_name > $DEST/debug/install.log 2>&1 + dpkg -b $uboot_name >> $DEST/debug/install.log 2>&1 rm -rf $uboot_name FILESIZE=$(wc -c $DEST/debs/$uboot_name.deb | cut -f 1 …

Dear contributors, the Armbian build framework sub-forum is dedicated to collaborate on the tool founded by Igor. The framework itself is opensource/GPL. Please add in the title, if possible: [WiP] = Work in Progress [RFC] = Request for Comment [TEST], [TEST/CPU/Board] = Feed back on tests [Device specific] [Board specific] etc. The framework doc is here [WIP] The tool aims at building {legacy, vanilla} linux kernels as well as (user-)patching/creating complete working images with {trusty,wheezy,jessie} to write on your flash {sdcard/NAND} Long story short... feel free to: Report bugs related to build script itself or patches supplied with it; Suggest new f…

Today I did compile for some SBCs the kernel 5.9.1 dev but had something strange - for me - When I did compile for sunxi I also did get a .deb for sunxi64 and a new sunxi when I did compile for a sunxi64 board. AND as last I did compile for the Odroid C2 (meson64) and I also did get the sunxi and sunxi64 .deb-packages. Is this normal or a new bug? Because in the past I did only get a new .deb-package for the platform which I did actually compile for.

I got a little problem I interrupted the first lines of the compile.sh and now I do get the error: root@core2duo(192.168.6.19):/home/guido/build# ./compile.sh EXPERT=yes bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell I did found out that when entering the command "exit" this shell will close and the normal menu driven compile gui does start, but maybe anyone could give me a hint to resolve this issue? Many Thanks in advance

For a reason I didn't figure out, the build is broken : MKIMAGE CC [M] fs/ecryptfs/read_write.o CC [M] fs/ecryptfs/crypto.o CC lib/kasprintf.o CC [M] net/bluetooth/mgmt.o CC kernel/compat.o CC [M] sound/soc/soc-dapm.o CC [M] fs/ecryptfs/keystore.o Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k, sandbox Usage: mkimage -l image -l ==> list image header information mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d data_file[:data_file...] image -A ==> set architecture to …

We all know there are several shortcomings which causes mess in the config files and prevent simple implementing of more complex scripting. In order to make build system future proof and to cleanup the exception mess, which is virtually everywhere, I decided to start working on a part of the build system. Now the concept works and it is not that far to be mad if idea is bad packages/extras was moved into this, then board support package and (for now) Cubietruck and Tinkerboard hacks from config/sources/ All others have to be implement into packages and their scripts. It's one time job and it will be much easier in the future, with new boards or functions. …

Hi hi @Igor I have written in my tree a markdown file in build rootdir (wondering about a /doc directory?) guiding how to build a kernel using RHEL / CentOS containers. URL: https://github.com/rfrht/build/blob/testdoc1/build-docker-rhel.md Wondering if would you be interested to merge it into your tree. Let me know! - RF.

Hi devs, I would like to discuss our default settings for the small NanoPi H3 boards that lack HDMI output capabilities (so the use cases are pretty clear: we're talking about headless servers or IoT nodes). Based on some research done the last few weeks I would like to start with these settings: HDMI/Mali400 disabled (for obvious reasons, also this is responsible for some severe energy savings -- can't tell numbers but this is the most efficient measure together with drastically reducing DRAM clockspeed) maximum CPU clockspeed by default 1200 MHz in fex file but 912 MHz in cpufrequtils' settings so that the boards remain at 1.1V by default and also maximum consumpti…

S500 devices (LeMaker Guitar and RoseApple Pi) are the only devices without initrd/UUID support, both are EOS and have only 3.10.y EOL kernel source. I propose creating a tag in the build script and deleting their configuration files along with the code that deals with non-UUID root cases to simplify our code base for upcoming LUKS rootfs encryption support. Any thoughts/objections?

Mainline kernel 4.7 brought separate Device Tree configuration for Lime2-eMMC board. What should we do with this board? Don't provide separate images, write some basic instructions about changing Lime2 images to use eMMC Provide separate images with mainline kernel Provide separate images with mainline and legacy kernels I remember about default DRAM frequency issues, but we always can lower default value in u-boot configuration patches. Also I reworked Pine64 configuration and, now build process for legacy u-boot should be more reliable, and mainline (dev) target is also available for building. I think we should start providing preliminary images (Jessie CLI…

Hi folks, I started to think about that a while ago and want to share my thoughts with you. In my opinion RPi-Monitor is a great tool to get a clue what's going on on a SBC (especially when testing stuff but also in 24/7 use). It's also lightweight enough to run all the time in the background collecting data and to be used by a few clients also (rendering/display happens in the user's browser and not on the SBC). Currently users have to install RPi-Monitor manually and sometimes seem to be confused (for example they switch between legacy and vanilla/mainline kernel and temperature/consumption graphs disappear). If we would integrate RPi-Monitor into Armbia…

Just a thought. Over half of the boards we support feature a 26 or 40 RPi compatible GPIO header and all the other boards expose various protocols and GPIO on various pins and headers. Users coming from Raspbian and trying out any of our boards expect that basics work the same. While it's both impossible and not desirable to be 100% compatible with Raspbian a few things would make transition from Raspbian to Armbian for IoT folks more easy. Simple example: Default user pi in Raspbian has access to GPIO pins -- on Armbian it's currently root only. How's that done? A group called gpio exists in Raspbian, pi is added to it and /etc/udev/rules.d/99-com…

See conversation in this commit for background The current default, Next, Dev naming convention for the kernel source trees is confusing, and a bit inconsistent. I think it's time to rename them and provide clear definitions of what they are supposed to provide. I'll start with some ideas here: Vendor This Kernel is currently called Default . The Vendor kernel would be the BSP-derived kernel or vendor maintained kernel. Typically there for basic functionality early in a boards life. Armbian can supply patches for these kernels LTS This kernel is currently called Next. The LTS kernel would follow a LTS version of …

There's been discussion in the past of switching to a YY.MM naming convention for releases (similar to Ubuntu) [citation needed -- I think it may be buried deep inside a github discussion] How does that impact us as a rolling release? What do we want to convey with our versions/releases? Should we do monthly releases? quarterly? I do think time-based releases would help us with priority.

Hi, since a Geekbox (Rockchip RK3368) and two Pine64+ (Allwinner A64) are collecting dust and at least for the latter longsleep already prepared a nice image build process that makes including a 'foreign' rootfs quite easy I thought about supporting arm64 also and not just only armhf. But I still lack oversights over our own build process or don't know in which direction other devs will move (I saw zador rearranging stuff the last days) so I thought I better ask first instead of hacking around I thought about adding a global variable defaulting to "armhf" and setting it to "arm64" for the new boards in configuration.sh since we later have to call make ARCH=…

Based on discussions the last days/weeks it seems obvious to me that we should document default Armbian security so that people know what they get and where to tweak if they have specific concerns. I took a few minutes to start with a list of issues that should IMO be addressed (no specific order): Explain where password strength policies originate Restore distro default sshd settings if concerned: sed -i 's/PermitRootLogin yes/PermitRootLogin without-password/' /etc/ssh/sshd_config Use and purpose of haveged: https://github.com/igorpecovnik/lib/issues/503 'Secure delete' on SD card, eMMC or SSD (overwriting contents on the FS layer requires a sync call if followed …

In case anyone else needs help with this. These steps create an oven-baked .img complete with all custom goodies on board from the get-go. 1. rysnc custom code and any other local dependencies into userpatches/overlay 2. Ensure any library dependencies (libv4l-dev in this case) are met by adding 'PACKAGE_LIST="$PACKAGE_LIST libv4l-dev"' to userpatches/lib.config 3. Step 1 ensures that the target image will have content in /tmp/overlay. In userpatches/customize-image.sh one needs to move said content from the read-only directory to somewhere suitable (/test in my case) 4. Finally have customize-image.sh run the relevant build system and optionall…

Hello At first, I would like to tell how I think your work you do on the arm boards is great. Looking actively for an alternative to the official Odroid Ubuntu image, I downloaded and installed the Armbian image on a SD card with dd and booted on the Odroid-C2 board. I made a first boot and a update/upgrade cycle on the SD card before to transfer the ext4 (root) partition with rsync (with the basic : -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found", options) to an empty, new made ext4-partition on a 16 Gb-USB 3.0-drive. The OS boots well on the USB device (changed the boot.ini and fstab files as below) and I conn…

Documentation is a little thin here. Does anyone have a working example of how to get a file (or files) properly copied into the destination image? Specifically I'm trying to get a binary copied into /sbin on the target. TAIA

I have several files I want to embed into the compiled image, such as logos, desktop backgrounds, some public keys, scripts etc. I can put them in correct place (e.g. /usr/local/bin) or put it in a directory at root (e.g. /MyAppSetup) and run a script to handle/move them. In the past I was using a private git repo on my server to clone these, but if I'm compiling, I'd like to get rid of this extra layer. I could not find a way to do that. Could someone please advise?

Hello. Maybe this is discussed already, but i can't find anything with the search. I have some modifications in kernel and other things and i have my own build image of Debian Jessie and deb-s with this modifications. Version 4.84 of legacy 3.4.110 kernel. The most important for me is contiguous memory allocator - CMA, which solved my problem mentioned here - http://forum.armbian.com/index.php/topic/559-lamobo-r1-hardware-accelerated-driver/ , other things i can do under working system later, but i add them in image for ease. The problem is, after latest upgrade every modification is gone, of course. I made a new deb-s, version 5.0 with CMA enabled and apply them, but wh…

FYI, I need a DKMS module to be reloaded after I upgrade the Armbian kernel files with "dpkg -i *.deb" so the following snippet: - remove /tmp/.reboot_required - compile any header files for scripts - add my favorite frandom-dkms module gr@bpi:/armbian_kernel$ cat mod_noreboot.sh #!/bin/bash #sudo rm /tmp/.reboot_required #pushd . #for f in $(ls -d /usr/src/linux-headers-*-sunxi) #do # cd $f # sudo make scripts #done #popd sudo dpkg -i frandom-dkms_1.1-0centrych4_armhf.deb

Hello, first I want to thank for the Armbian distribution and the developer tools. "sudo ./compile.sh" complains about a syntax error in configuration.sh. Already up-to-date. Already on 'master' Your branch is up-to-date with 'origin/master'. [ o.k. ] Preparing [ host ] /home/toor/armbian/lib/configuration.sh: line 236: syntax error near unexpected token `)' /home/toor/armbian/lib/configuration.sh: line 236: ` orangepipc)#enabled' [ o.k. ] Starting Armbian build script [ @host ] [ o.k. ] Building [ Armbian 5.00 Bananapim2 Debian jessie next ] [ o.k. ] Syncing clock [ host ] [ o.k. ] source downloading [ @host ] [ o.k. ] ... creating a shallow clone fatal: repo…

thinking of http://forum.armbian.com/index.php/topic/2043-lamobo-r1-520-swconfig-problem-with-last-520-armbian-update/?p=15773 We may ask the forum users and create a list of testers for each board (or family of boards) => we could create a sub forum Armbian/Tech/Dev/Armbian build framework/Testing/ - to call for testers when needed (testers would register a pined thread managed by Igor/Mikhail/Thomas/others) - to report testing on the forum using a title like [5.20/Lamobo-R1] "Status" (OK/KO/minor issues) - create bug reports in appropriate forum each registered testers creates its minimum set of test (like testing the switch config of Lamobo-R1) and cr…

some simple thoughts to help (assuming limited time consumption) - adding a short "Roadmap" (main & side quests) section (in docs.armbian.com/Process_Contribute/ ?) displaying "main" goals for current & possible next iterations because currently the single tasks is the forum are useful but not "readable" - a (google group?) mailing list (read only) for contributors (to push roadmap changes & call for tasks) - a separate mailing list (read only) to call testers when needed - a page to report testing per board (wiki? google web document?)

FYI quick update kernel 4.4.24 gr@bpi:~$ cat /proc/version Linux version 4.4.4-sunxi (root@server1404) (gcc version 5.1.1 20150608 (Linaro GCC 5.1-2015.08) ) #1 SMP Mon Mar 7 13:55:59 CET 2016 download deb here I have moved to 4.4.4 Xcompiled with linaro 4.9.2 5.1.1 => Armbian tool on Ubuntu 14.04.34 guest with gcc 5.3 full-crypto + A20 hardware (P)RNG + CPU @1GHz NOTE: [standard sunxi-next] nice, the linux-trusty*.deb package is built with kernel only compile (thanks) config http://pastebin.com/V4p7B9bK NOTE : [standard sunxi-next] nice to have NEON as module I prefer CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y testing…

Hi, I thought about the situation with the yet announced Orange Pi One (H3 based, $10, Fast Ethernet) that should start shipping on Jan 25th. The PCB is smaller, it features less USB ports than the Orange Pi PC and has a different voltage regulator switching between 1.1V and 1.3V (adjusted through GPIO): http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=895&page=4#lastpost Igor already prepared a test image for Orange Pi Plus based on kernel 4.4.0-rc5 last year (which I used to setup a NAS with an Orange Pi PC in the meantime ) and I would believe mainline kernel support for these H3 devices will improve pretty fast in 2016. It seems …

AXP202/209 sysfs interface patch for axp20x MFD drvier in mainline kernel I'll try to maintain this patch as long as axp20x power driver is not present in mainline kernel. Adding partial sysfs interface to MFD driver is not a proper way to implement things in mainline kernel; if you want, you can use this code and RFC power driver patch to write a proper driver and send it upstream. âžœ ~ % ls /sys/power/axp_pmu/{ac,vbus,battery,charger,pmu,control,ocv_curve} /sys/power/axp_pmu/ocv_curve /sys/power/axp_pmu/ac: amperage connected used voltage /sys/power/axp_pmu/battery: amperage capacity charge charging connected power ts_voltage voltage …

Hi there, while the customize-image.sh got some attention lately because of OMV integration, I've started a try to enhance the customization process. At the moment any changes to the script are valid for the whole buildenv. That might be good when building just one image but all over I think thats not a good situation, especially for automated building or with more then one customization. I startet to define a $CUSTOM Buildvar and redefined the script locations, starting with the following changes: - delete customize-image.sh an overlay dir - placed it under config/customizations with following layout *-chroot.sh, *-host.sh, …

Greetings. Can I make sure I've understood this correctly. I want to ensure kernel sources always come from a local development directory. In my /userpatches I've got a lib.config which has: KERNELDIR="/home/user/sources/linux-sun8i" with both KERNELSOURCE and KERNELBRANCH commented out. Is this the right thing to do? And just so I can get all my idiot points at once: Specifying KERNELSOURCE and/or KERNELBRANCH will anchor the source repo and branch to whatever I wish? TAIA Jerry. P.S. Armbian *awesome* for super quick experiments/deployments.

I found "lib/patch/kernel/sun8i-default/30-real-time143-full-plus-rt-fixes.patch.disabled." So, just renamed it to .patch. and build default (Vendor provided / legacy) of version 3.4.113. But, showed ERROR. So, I cleaned scripts and newly git clone armbian lib. but the result is the same. Here is output log. Spoiler Displaying message: Preparing host info Displaying message: Build host OS release trusty info ## BUILD SCRIPT ENVIRONMENT Version: 8e605aaaf48a06d74a8e55b1636e51f6893f7b5f ## BUILD CONFIGURATION Build target: Board: nanopineo Branch: default Kernel configuration: Repository: https://github.com/igorpecovnik/linux Branch:…

rc2 breaks the builddeb patch, at least on Rockchip, investigating. [Edit] Fixed Tinker Board and Meson64 Dev

I came across this blog post which had a fantastic breakdown of the workflow for building a kernel with the armbian build tools. Just wanted to share.

If I have understood correctly, usb-redirector is an example of adding a custom application to an Armbian build? Is there a slightly simpler 'hello world' example? I typically use Buildroot to assemble an OS and RFS - is there anything similar to the BR package system in Armbian if I have misunderstood the above? TAIA.

Trying to add the hdmi hotplug udev rule to the build environment, adding it in the same manner as the C2 hdmi config script doesn't work, it tells me the file/folder doesn't exist, I'm guessing then that bsp family tweaks isn't the place to add it?

Release Candidate Code Freeze Date: 2020-01-25 Release Date: 2020-02-?? (will update thread) Current Release Candidate Branch Link: v20.02-rc1 Release Changelog: (will update) Release Coordinator: @lanefu Testing Tracking Sheet: https://bit.ly/2TGaeZN (google sheets) The goal of this thread is to discuss testing, bugfixes, and the overall quality of the release. Once the release is complete, this thread should be locked and unpinned. Our Hotfix process for completed releases is TBD. First of all I'm sorry I'm kicking this off so late. I should have started a few weeks ago. I'll continue to update this post with more info…

Release Candidate Code Freeze Date: 2021-07-18. (Fixes only afterwards) Release Planning Meeting Date: 2021-07-10 1400GMT Release Date: 2021-08-08 Release Candidate Branch Link: TBD Release Changelog: TBD Release Coordinator: @lanefu Testing Tracking Sheet: TBD (google sheets) The purpose of this thread is to discuss testing, bugfixes, and the overall quality of the release. Once the release is complete, this thread should be locked and unpinned. Please subscribe to this thread! I want this release to focus on upgrade stability. That means we need to strongly focus on: * kernel packages * rootfs package…

Hi, I've been building nanopineoplus2 stretch images with armbian build on commit c3f02be362aa216f2d3ee011916f9a18baf58291 (August 4, 2018) and it worked fine until earlier this week. My last successful build was on 10/28/2018. Could this be failing because armbian-firmware 5.55 or some older packages were taken off the apt repo? Here is the log output: [[0;32m o.k. [0m] Installing packages for [[0;33m Armbian [0m] Reading package lists... Building dependency tree... Reading state information... [[0;31m error [0m] ERROR in function create_rootfs_cache [[0;33m debootstrap-ng.sh:213 [0m] [[0;31m error [0m] Installation of Armbian packages failed [[0;32m o.…

@Igor Could we imagine another mechanism than to use git as an "upload front-end" ? Using git as some kind of spool folder is really not ideal. For instance if I clone today the armbian upload git project the size of the objects is already reaching 1.2 GB for a project that is essentially just a structure of empty folders. I even see the following error during cloning Cloning into 'upload'... remote: Enumerating objects: 75, done. remote: Counting objects: 100% (75/75), done. remote: Compressing objects: 100% (61/61), done. kex protocol error: type 7 seq 49316022.52 MiB | 6.67 MiB/s remote: Total 844 (delta 33), reused 40 (delta 14), pack-reuse…

Probably the easiest and fastest way to set up an Ubuntu Xenial build environment (needed by the armbian build scripts) is using a chroot jail. This thread should be a quick copy paste "tutorial" to create your own chroot jail and on an Debian based linux installation. 1.) Install debootstrap $ sudo apt install debootstrap 2.) Chreate chroot jail using debootstrap $ sudo debootstrap --variant=buildd --arch=amd64 xenial ./system/ http://archive.ubuntu.com/ubuntu/ 3.) Mount your local system into the chroot $ for f in dev dev/pts proc sys ; do sudo mount -o bind /$f ./system/$f ; done 4.) Mount resolv.conf from host system into…

Hi, I used armbian build many times to create my custom orangepipcplus images without any problem until now. It was working perfect. But, it started to fail today and couldn't build the image. To prevent any mistake, I created a new Oracle VirtualBox VM by using Bionic minimal iso and follow the steps on https://github.com/armbian/build but still no luck. It still gives same error and fails. I try to build by options "Full OS image for flashing", "Do not change the kernel configuration", "next Mainline (@kernel.org), "xenial Ubuntu Xenial 16.04 LTS", "Image with consol interface (server)", "Standard image with console interface" for orangepipcplus and withou…

This might be close to be off-topic, but I think this is the closest forum for this thread. Since I read that Igor asked if we know any build-farm services (clouds like Amazon's EC3 or the like), I've been thinking about private build farms. I imagine that Igor does not have a large build farm (perhaps some boards are contributing with distcc). Thomas, what is your setup for building Armbian ? (I imagine that you may have a stronger setup). Other developers, please chip in too. What's been in my mind for a while, is to make a low-cost farm, which would perform well and make things easier and quicker for the Armbian team. There…

Dear maintainers, can you answer a simple question: which board should be selected in build menu for BananaPi M1+ ? I can see 2 options for A20 Soc : "bananapi" and "bananapipro" ? Which one is the preferred option ? Thanks

I'm running an armbian build under docker (Host = Linux Mint or Ubuntu Bionic). I ran git clone --depth 1 https://github.com/armbian/build The problem is, in my customize-image.sh script I'm trying to build something that needs to have a package installed before. My lib.config looks like this: #DEBIAN_MIRROR='ftp.at.debian.org/debian/' #DEBOOTSTRAP_LIST="$DEBOOTSTRAP_LIST,apt-transport-https,ca-certificates" display_alert "Adding additional packages" "PHP 7, Redis, udisk2, dnsmasq, python3, ..." "info" PACKAGE_LIST_ADDITIONAL="$PACKAGE_LIST_ADDITIONAL php7.0 php7.0-cli php7.0-fpm php7.0-curl php7.0-intl php7.0-redis php7.0-mbstring" PACKAGE_…

Using customize-image.sh work nice with debian but not executed when build Ubuntu. Log report [O.K.] Calling image customization script [customize-image.sh] but after that no output from my script and no change on image

I just try 5.7rc1 build of linux kernel for odroid c2 And armbian can't create linux kernel package It looks like some problem in https://github.com/armbian/build/blob/master/patch/misc/general-packaging-5.6.y.patch

Armbian CI is building v5.10.43 while my local build is making v5.10.45. How can I switch? I've tried all sorts of iterations of KERNELRELEASE= BRANCH= and LIB_TAG= in userpatches/config-example.conf but can't find the right combination to build a v5.10.43 kernel with RELEASE=focal What's the correct build env var and value needed to match Armbian's CI?

Hi, my name is Tom and i am an embedded developer. I am aiming to dig into the CSI0 camera interface for the bananapi. Admittedly, i am new to the linux way of coding and compilation. Thus far for armbian, i realized,... ....compilation by script "compile.sh"...which checks all needed tools, code, updates...downloads everything...runs a config screen to select target, platform, ...and yeah..it works. When i run the script two times ...it keeps compiling again. hmm+ My experience is, that i do have the sourcecode, a compiler script/makefile....and it will just update the changes i did on the source. (old scool:-) so if i have the source in a direc…

Armbian firmware is a repo holding all firmwares used by Armbian releases. files/firmwares in this repo are directly copied to /lib/firmware in release images. I don't know which firmware is used by which device, but some of them are put in wrong place. eg: for Broadcom Bluetooth firmwares, firmwares should be in brcm/ folder, but some of them are not in this folder. is there any plan to add firmware build support in build script or simplely put firmwares in right place.

I have a test set of configuration files to build for armbian TV box platform Amlogic S905. Is anyone interested ? Should I create the pull merge GIT lib ?

Tried to have a new build today and got this [ error ] ERROR in function compile_kernel [ common.sh:200 ] [ error ] Kernel was not built [ @host ] [ o.k. ] Process terminated I was trying to build with options OPi PCPlus, RT patch, jessie, desktop and got this stopping error message Is there any log with details that I can review in order to pinpoint the exact problem?

I noticed that once in a while I receive Jenkins notification from some build machine under lollipopcloud.solutions domain. I guess I receive notification whenever my email is in some commits covered by the build. Is this build machine some armbian official build machine ? In any case I cannot access the linked jenkins portal. http://jenkins.build.lollipopcloud.solutions:8080/job/Armbian/38/

Hello, not sure if I'm at the right place here, so please let me know if I'm wrong and where I need to be. Thanks in advance and my apologies... My problem is that for some time now does Apt keep deleting custom kernels in /boot and the package appears to delete kernels not only with a rough pattern, but with "-f" as well, ignoring any file permissions. I've been watching this for a while now and it has left me at first with unbootable devices until I've noticed the cause. I would very much appreciate it of the Armbian kernel package wouldn't just delete anything that looks remotely like a kernel from /boot with a "rm -f *", but only removes the fi…

Hello guys, I built OS with legacy kernel for Orange Pi One using github framework https://github.com/armbian/build . Everything went fine and I got a resulting img file. I copied it to 16GB SD card (7Samsung EVO class 10) and powered up my device but it couldn't start. Below is the log I got from UART console. You can see from it that my device was retrying boot sequence over and over unsuccessfully. Can you help with the problem, please ? P.S. I also built Armbian with mainline kernel and it loaded fine, i.e. problem exists only with legacy kernel -------------------------------------------------------------------…

What do these explicitly do? Which ones can be disabled? Which ones can interfere with other system mods? sudo systemctl list-unit-files | grep armb* armbian-firstrun-config.service enabled armbian-firstrun.service disabled armbian-hardware-monitor.service enabled armbian-hardware-optimize.service enabled armbian-ramlog.service enabled armbian-resize-filesystem.service disabled armbian-zram-config.service enabled I've notices that ramlog can be disabled two ways - in the config, or disable …

This is to discuss and prioritize enhancements and bugfixes we want to target for v20.05 (Kagu). We will lock this thread 2020-03-15 to manage scope creep. Many items are currently in Jira here https://armbian.atlassian.net/projects/AR/issues/?filter=allopenissues If you're a frequent contributor and would like to join our Jira, please PM me. It's not mandatory, but it would make things easier. To track. Remember the Armbian Mission Statement: Armbian is a base operating system platform for single board computers that other projects can trust to build upon. Let's try to prioritize things that help us deliver on that mission

Release Candidate Code Freeze Date: 2020-07-18 Release Date: 2020-08-XX Release Candidate Branch Link: TBD Release Changelog: TBD Release Coordinator: @lanefu Testing Tracking Sheet: TBD (google sheets) The goal of this thread is to discuss testing, bugfixes, and the overall quality of the release. Once the release is complete, this thread should be locked and unpinned. --- Our next release date is coming and perhaps its time to discuss what to push into 20.08, what not, resolve open questions and distract from most used keyword for past few weeks. @Myy @TonyMac32 @balbes150 @piter75 @sfx2000 @ebin-dev @c…

Release Candidate Code Freeze Date: 2020-10-18 Release Date: 2020-11-XX Release Candidate Branch Link: TBD Release Changelog: TBD Release Coordinator: TBD Testing Tracking Sheet: TBD (google sheets) The goal of this thread is to discuss testing, bugfixes, and the overall quality of the release. Once the release is complete, this thread should be locked and unpinned. --- Our next release date is coming and perhaps its time to discuss what to push into 20.11, what not, resolve open questions and distract from most used keyword for past few weeks. @Myy @TonyMac32 @balbes150 @piter75 @sfx2000@ebin-dev …

Bugfix v1 was already pushed out: [AR-551] - Update fan configuration, enable network LED and enable UPS timer Updated Helios64, Rockpi 4* images and rockchip64 kernels Bugfix v2 Let's try to patch other critical things before Christmas. I already addressed ZFS problem on Focal by adding most recent DKMS package, but to solve it also for Buster it requires all kernel recompilation - in case you want to push some late changes, now it's the time. The Beast can handle that in no time We hopefully fixed Odroid HC4 (don't have HW to test), added KVIM2, DVFS on mvebu will be disabled from now on to secure stability (moving to 5.9.y ?)…

Release planning: January 2nd. Meeting location is IRC channel #armbian on freenode. Meeting starts at 2pm GMT. Open topics / development directions: - desktop branch merge into the master - enabling 3D support on desktop(s) - update u-boot (where possible) to 2020.10 and K5.10.y Spoiler My test farm is updated to 2020.10 / 5.10.y Cubieboard Cubietruck Cubox i2eX/i4 (old u-boot) Le potato Lime 2 NanoPi K2 (NIC not working) NanoPi M4 NanoPi M4V2 NanoPi Neo 3 Nanopi R2S Odroid C1 Odroid C2 Odroid C4 Orange Pi Lite Orange Pi Lite 2 Orange Pi One+ Orange Pi R1 Orange Pi Win Orange Pi Zero Orange Pi Zero2 (private u-boot / WIP tar…

Release Planning: April 3rd. Meeting in IRC channel #armbian on freenode. Meeting starts at 2pm GMT. (let me know if this is a bad date, because it is around easter holiday in Germany for example) Code Freeze: 2021-04-19 (Monday April 19th) Release Date: 2021-05-09 (Sunday May 9th) Release Candidate: https://github.com/armbian/build/tree/v21.05.0-rc Changelog: https://docs.armbian.com/Release_Changelog/#v2105-2021-05-09 Coordinator: @Heisath The goal of this thread is to discuss testing, bugfixes, and the overall quality of the release. Open topics: - complete desktop branch merge into master (this seems g…

The new vagrant method looks like it is broken.. In order to login with ssh it asks for password and we do not know it, it does not work as vagrant/vagrant, ubuntu/vagrant, ubuntu/reverse and everything else tried. Can the vagrant armbian instructions be more specific to this? ( although it looks like a serious vagrant bug -> https://bugs.launchpad.net/cloud-images/+bug/1569237 ) /edit followed this guide to setup, executing exactly what is referenced -> https://github.com/igorpecovnik/lib/blob/master/README-Vagrant.md and managed to have a vagrant box up and running, but no means to login to it /edit2 Host system: Win7/64, VirtualBox 5…

Hello guys, I tried to build v3.* starting from here https://github.com/armbian/build, my build environment is Hiper-V & Ubuntu 16.04 x64. I have chosen OrangePi One board to build u-boot & kernel of v3.* but got issue with compiling kernel. Looking into log & scripts I found the compiler version assigned for kernel is > 6.x but looks like the code base (or whatever) is not ready for this high version. Logs attached. Can you help, please ? Thank you logs-26_05_2017-14_26_00.tgz

Today I noticed something strange about packages : armbian-config and armbian-firmware (bionic all) Repository version becomes 19.11.3 (via apt update) but self built packages created via kernel build script are version 5.98 Other kernel packages are ok, version 4.19.85 What about this?

My Cubox i4pro is running Armbian. I'm using Apticron to notify me of package updates that are available for my system. Apticron usually tells me a short summary of what has changed with a certain newer version. Somehow, the armbian-firmware never shows this information. Is it available somewhere online? I would like to be able to verify what I'm updating so I can assess if there's a risk that something breaks...

Hi everyone, I use Orangepipc and want to make full encryption of the root file system, I applied the following topics, but each time it says "starting kernel ..." and freezes on the booting What is the problem? I tried OS; Armbian_5.59_Orangepipc_Debian_stretch_next_4.14.65 Armbian_19.11.3_Orangepipc_buster_current_5.3.9 Armbian_20.02.1_Orangepipc_buster_current_5.4.20 Armbian_20.02.1_Orangepipc_bionic_current_5.4.20 and https://ch1p.io/armbian-fde/

Hello guys, I need my device to load armbian , autologin and run my application fullscreen. Can you give me a hint, please, what I should add into customization scripts ? Thanks

Hello guys I need instructions on how to skip mandatory steps during first load when Armbian requires to login as root and use password 1234. What I need is to have pi account created automatically during sd-image build (with a custom password) and assigned a predefined set of groups. I want Armbian start and auto-login with pi account and run my linuxfb-based full-screen application. It seems like customize-image.sh is the right place to create a new account on target image. But how can I disable that startup poll to create a new user, change password, etc? Thanks