Armbian build framework

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…

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…

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 …

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…

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…

I added a while back 'free' output to 'armbianmonitor' and 'armhwinfo' to get some monitoring data from real-world installations about swap usage. Armbian uses an emergency swap file of 128MB by default (vm.swappiness=0) which means swapping should be avoided unless really needed. Let's have a look and extract data from +50 support URLs collected within the last months. I piped the output of https://pastebin.com/raw/DjxAX6Rn through while read ; do curl -q "${REPLY}" | grep '^Swap: '; done | sort | uniq -c and this is what we end with: 175 Swap: 127M 0B 127M 1 Swap: 127M 22M 105M 1 Swap: …

For the past 10 years, I have been moving evenly and rectilinearly in an inertial frame of reference called OpenSUSE. I had to first read about creating Debian packages and look here: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/ Both Ubuntu and OpenSUSE distributions start with the kernel source package, which contains a set of scripts and rules for further build. This has a sacred meaning. To get started, I took two scripts from the v5.7-rcX core as a basis and put them in packages/armbian/builddeb packages/armbian/mkdebian checked the build process for bionic current core v5.4.y This initial state can ser…

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 …

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 …

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

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. …

In my project I would like to create Armbian ISO that has only the packages that are really needed for system itself and literally few I need for my application. Just to use smallest possible SD card and not update packages I will never use. Regardless how I configure build at the end I got 1GB image. While I know it is possible to go down to 100MB using Ubuntu bionic and latest kernel. Shall debootstrap use configurable —variant option? For me “minbase” would be perfect. But it does not change anything. Shall I put into lib.config my version of PACKAGE_LIST? Still a rootfs is forced to download. No success. So how to strip do…

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…

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…

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.

Hello everyone, since i couldn't find a section for the NanoPi Neo/M1 (or maybe i just overlooked it), and the OrangePi One is rather close to it anyways, i'll post it here. Would there be interrest in a 3.4.112 kernel tree with the preempt_rt patches (rt143) added? I got myself said NanoPi's some days ago, and started to patch my way up from the original sunxi kernel 3.4.39 to the 3.4.112 version, then added the preempt_rt patches, and finally added (most?) patches from the Armbian build. Obviously manually adding the rejects. I'm also having a U-Boot 2016.09-rc1 that i have slightly patched to have it use uEnv.txt instead of boot.scr, because i got too annoyed t…

It might be time for some release line. Let's put together what was done in past few month, need to be done, was forgotten and it's worth mentioning. I sure missed stuff out ... so just add it. IMAGES / KERNEL: - all 3.10+ kernels are Docker ready - added Odroid C2 CLI and desktop, kernel upgraded to 3.14.65 - Udoo Neo wireless works - legacy kernel for Allwinner boards was upgraded to 3.4.111 - legacy kernel for iMx6 boards was upgraded to 3.14.65 - vanilla images comes with kernel 4.4.6 - Clearfog comes with 3.10.101 and 4.4.6 - added Armbianmonitor which knows .... - fixes for SPDIF / I2S audio driver in legacy kernel - added USB camera section - added f…

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…

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 …

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…

To continue from here. Actually it works the way repository is build together: host Debian Jessie, and then I changed release, update. Now we only have jessie desktop packages, so it looks ok. # armbian.list deb http://apt.armbian.com jessie main utils desktop ... Ign http://apt.armbian.com jessie/desktop Translation-en_US Ign http://apt.armbian.com jessie/desktop Translation-en Ign http://apt.armbian.com jessie/desktop Translation-en_US.UTF-8 Ign http://apt.armbian.com jessie/main Translation-en_US Ign http://apt.armbian.com jessie/main Translation-en Ign http://apt.armbian.com jessie/main Translation-en_US.UTF-8 Ign http://apt.armbian.com jessie/utils Translation-en…

Are there any chance to build testing image for Ubuntu 18.04 ?

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…

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…

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…

I have compiled to test new armbian 5.04 in a banana pro (Output: Armbian_5.04_Bananapipro_Debian_jessie_4.4.3.zip). At the first boot it is asking for the new user: login as: root root@192.168.178.30's password: Thank you for choosing Armbian! Support: www.armbian.com Creating new account. Please provide a username (eg. your forename): I introduce whatever username and after that the system is booting. There is a loop continuously because after the boot, if I try to login with root, aks again for user but if I login with a created new user doesn't work because the password not was asked before and therefore is not accepting a password. I'm doing something wron…

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

hi, i have latest Armbian environment pulled from github running on Ubuntu Bionic 18.04. There are 2 issues that are bugging me. Not sure It does produce in most cases images but i think they are incomplete. Tried even secondary copy (another clone) that i would run in docker containers just to see if that was the issue but outcome seems to be the same. 1. Every time i start ./compile it pulls Linaro toolchain and fails to verify its signature. Looking at the files https://dl.armbian.com/_toolchains/ it seems that linaro toolchain has GPG signature in ASC file where as others have checksum. Am not sure ... zh@acus:~/armbian$ ./comp…

Hello, guys, when can we expect mainline Kernel 4.14 for sun8i h3 ? Now we have only 2 options : 4.11 or 4.13. Thank you

What about solving ramlog this way: - added cronjob on every 15 minutes - if space is 75% full do: logrotate --force /etc/logrotate.d/ write to SD card truncate and remove files It is better than now. Good enough for defaults? Spoiler diff --git a/packages/bsp/common/etc/cron.d/armbian-truncate-logs b/packages/bsp/common/etc/cron.d/armbian-truncate-logs new file mode 100644 index 0000000..dbc024c --- /dev/null +++ b/packages/bsp/common/etc/cron.d/armbian-truncate-logs @@ -0,0 +1 @@ +*/15 * * * * root /usr/lib/armbian/truncate-logs \ No newline at end of file diff --git a/packages/bsp/common/usr/lib/armbian/truncate-logs b/p…

Is there a way to increase/change CMA (contiguous memory alocator) reserved memory in kernel configuration for H3 devices? The value stays at default of 16Mb, but after kernel/image creation magically increase to some higher value like 160Mb for OpiOne (512Mb RAM), or 256Mb for OpiPC (1Gb RAM). Even if i try to change the value in kernel configuration, like i used to in A20, with: KERNEL_CONFIGURE="yes" FORCE_CHECKOUT="no" in compile.sh , this have no effect for H3 and the above values of 160Mb/256Mb stays the same. So i guess it's defined somewhere else, patch maybe? Is there a way to change this? I want to see if increasing the CMA value will help to get rid of "out…

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…

I have a really slow internet connection and I'm doing alot of re-building Armbian and target systems etc. I have a copy of apt-cacher running on a local machine, I know how to configure it on target machines but I'm not sure how I would point the Armbian build system at it? At a guess I'm thinking that I probably need to modify debootstrap to create /etc/apt/apt.conf.d/90-apt-proxy.conf but wondered if anyone had any better ideas?

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…

Hi, I was just setting up a new armbian build environment following the usual github instructions on a bionic 18.04.3 system. Running ./compile.sh (alone or with any configuration) generates the following error: [ o.k. ] Checking for external GCC compilers [ .... ] downloading using torrent network [ gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar.xz ] [ error ] ERROR in function download_and_verify [ general.sh:1026 ] [ error ] verification failed From the output/debug/output.log Displaying message: Checking for external GCC compilers info Displaying message: …

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…

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.

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…

Hello, While trying to build full Devian Jessy image for NanoPi Neo at stock x86_64 Ubuntu 16.04 using latest https://github.com/igorpecovnik/libgit , got this: ... [ o.k. ] Compiling default kernel [ 3.4.113 ] [ o.k. ] Compiler version [ arm-linux-gnueabihf-gcc 5.4.0 ] [ o.k. ] Using kernel config file [ lib/config/kernel/linux-sun8i-default.config ] HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.hash.c SHIPPED scripts/kconfig/zconf.lex.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig drivers/net/wireless/b…

Just a quick list: It's named completely wrong since it doesn't install anything but transfers an already running installation from one media to another. Main focus on 'without breaking stuff' since transfering a booted/running system is challenging! It's named completely wrong since it's not about NAND and SATA any more (hello Cubieboards and Bananas back in 2014) but eMMC and USB these days (and yeah, SATA too) It's a blind alley: moving the installation from SD card to $somewhere will work. But nand-sata-install is still there, people might want to use it and will fail (though I think that will most probably never happen since once people are h…

Hi, I recently set up an ubuntu 16.04 parallels machine for armbian building. I use ./compile.sh BRANCH=dev to build orange pi lite2 dev images. But it failed, here is the log: [ o.k. ] Downloading sources [ o.k. ] Checking git sources [ u-boot h6-hdmi-rebased-1 ] [ .... ] Up to date [ o.k. ] Checking git sources [ linux-mainline h6-integrate-2-ugly ] [ .... ] Up to date [ o.k. ] Checking git sources [ arm-trusted-firmware-sunxi-mainline sun50i_h6_pmic ] [ .... ] Up to date [ o.k. ] Checking git sources [ sunxi-tools master ] [ .... ] Up to date [ o.k. ] Checking git sources [ rkbin-t…

Is there any simple way that we automatically produce a patch of changes made to the (kernel / uboot) source? Of course also if files are added.

Short changelog: Removed autodetection for H3 boards, changed DVFS and thermal settings Repackaged tools, hostapd and firmware (may require manual installation of packages) Odroid C2: Fixed headers packaging script, updated kernel configuration, updated boot script Added back watchdog to sun7i-default kernel Purging and reinstalling "unattended-upgrades" package should be recommended in changelog Script "40-updates" update logic was changed; script was switched to python3 since Xenial doesn't use python2 by default. Installing "python3-apt" should be recommended in changelog. Reworked initrd images handling on kernel upgrade ... (to be added) Other fixes and enhancements…

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…

I made some changes in the build scripts and wanted to ask if some of you may find them useful... ability to use custom skel folder in /userpatches directory support for xdm display manager (with graphical keyboard) selectable display manager in expert mode (lightdm, xdm or nodm) Especially the custom skel folder gives much more flexability for modders to generate images for wip or scs boards. I am currently testing different configurations, all seems good so far. What do you think about these changes? Would a pull request make sense?

I an new in building ARMBIAN. I have native: ' Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial with a nfs-mounted share on my NAS as working directory. [ o.k. ] Building deb [ linux-u-boot-dev-bananapim2ultra_5.27_armhf.deb ] dpkg-deb: Fehler: Control-Verzeichnis hat falsche Zugriffsrechte 770 (muss >=0755 und <=0775 sein) -> Sorry, I have German settings in my linux: I translate it corresponding: Error: Control-Directory has wrong access rights 770 (must be >=755 and <= 775) [ error ] ERROR in function compile_uboot [ common.sh:156 ]…

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 don't know if this is related to Linux kernel 5.0 but I didn't have this problem with 4.20 I used linux-headers-dev-.._arm64.deb kernel header files to compile mali kernel drivers on board I don't know if armbian changed something or it is kernel 5.0 related now I can't as linux-headers-dev debian/postinst script don't generate scripts/mod/modpost and only scripts/basic/fixdep any idea? this is output from make -d -s scripts http://paste.ubuntu.com/p/fbhr37q8GF/

Hi guys, Is this syntax still valid? Config file is placed in userpatches/config-<conf_name>.conf ./compile.sh docker <conf_name> It still displays the configuration menu for me. Thanks in advance.

Does anyone else have to run testdisk regularly after writing Armbian images to SD cards? It may simply be that I've cycles through the 3 or 4 cards that I have here so many times now that they are all on their way out, but it certainly happens on more than 1 card. I've just tried the latest Git version and it's happens with both debootstrap and debootstrap-ng. I used dd in an ubuntu VM to write the SD cards using a USB SD card reader. Workflow: Build Armbian use dd to write image file to SD card Try SD card in *pi board, it fails with unsupported file system error EDIT: the actual error is "Failed to mount Ext2 filesystem" Insert SD card into USB reader a…

Officially, how do I convince my build environment that I still want to use 4.14? When I just ./compile.sh BOARD=nanopiair BRANCH=next it defaults to 4.17 What I have come up with is: git checkout sunxi-4.14 && touch .ignore_changes This results in a lot of patches failing What is the correct way please?

I saw @zador.blood.stained was doing some housekeeping, so I wanted to open the discussion again about what to do about it in the future. We've obviously demonstrated what you "don't want to do". My last comments on this were as follows: We should have temporary per-kernel branches when undertaking a bigger change. This allows wider testing for those who like to build experimental things Makes the creator of the branch responsible for keeping it up to date gets flattened out and merged into "master" or a "next" waiting for a revision bump PR's should be used on anything anyone is not 100% certain of to g…

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 ?)…

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 …

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

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

A thought occurred to me while watching my machine sync a bunch of repos while running the Armbian build script, and I couldn't help wondering: Could we put the board support patches into their own repo separate from the build scripts themselves? More specifically: board support for "Boards of Interest" to the Armbian maintainers would be in whatever "official" repos we dedicate, I recommend separating per board family or SoC board support for CSC goes into, predictably, a CSC repo board support for EOL boards can be spun off into their own repo TV boxes go into a TV box repo Advantages: Supporting every pet …

Hi! I already successfully get mainline Armbian working on Pinebook (no sound - working on fix, and also suspend took much time to wake up), but, I don't like the way how I made it. Github repo: https://github.com/gamelaster/build/tree/pinebook-build I set the branch to "next", I set kernel repository to anarsoul's kernel (contains latest patches for A64 and also for Pinebook & Sopine devices) and deleted all patches from sunxi-next (all that patches has been for 4.14), I just kept and add some of patches. But this is probably terrible idea. @Igor or anyone, can you please me suggest better way to support "next" kernel (The task…

Hello, The compilation of a kernel failed with the error returned: ERROR in function compile_kernel [common.sh:254] Armbian building script, http://www.armbian.com | Author: Igor Pecovnik Compiling kernel... ... CC [M] drivers/net/wireless/rtl8189fs/core/rtw_mp_ioctl.o LD [M] drivers/net/wireless/rtl8189fs/8189fs.o LD drivers/net/wireless/built-in.o LD drivers/net/built-in.o Makefile:948 : la recette pour la cible « drivers » a échouée make: *** [drivers] Erreur 2 This error occurred after activating in the config of the kernel: ----> Device Driver -----> USB Support ------> USB Modem (CDC ACM…

I am building a full image for the OPiPC. For the most part everything works. I do get one error while running compile.sh The error I see during build is: "W: Failed to fetch http://apt.armbian.com/dists/jessie/InRelease Unable to find expected entry 'jessie-utils/binary-armhf/Packages' in Release file (Wrong sources.list entry or malformed file) E: Some index files failed to download. They have been ignored, or old ones used instead. I am building on a VMware vm running Linux armbian 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I did the clone from the git repository and ran compile.sh as root. …

I have machines available at work, but I loose quite a big amount of time fighting with proxy issues. I also have VM available with proxy almost correctly configured (some protocols/ports don't work, like for adding gpg key), but the disks aren't big enough. At home, I have network without any proxy, but it's not that good... So, I was wondering if I could try and build Armbian on the cloud... for free. I tried several websites like google cloud and other services offering Docker, but I haven't found any with enough disk space. Is anyone of you building in the cloud? Thanks.

Today i wanted to try some changes an build a new kernel for my H3 PCPlus. When I executed compile.sh i got a Message that the script was outdated. So i copied a newer Version from lib to my root directory. I made thechanges i did before: Set KERNEL_Configure to "yes" and set DEST_LANG="de_DE.UTF-8" (that was the only way to get a clean translated german Desktop before..) Now I get a warning Message: [ warn ] Can't update since you made changes to: compile.sh When I hit Enter the next thing happens: The Toolchan is downloaded every time. Is this really necessary? I have only a volume based Internet connection... Regards

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

Hello guys can you help me please understand your overlay compilation support which is working in "next" build? I transferred required patches and made a build with 4.15. Now I have my dtbos and scr in place, added "overlays=" in armbianEnv.txt but my overlays are not loaded in run-time. I noticed that you have the following condition around dtbos: ifeq ($(CONFIG_OF_CONFIGFS),y) ... endif and there is also a special patch to add configs module to build. My question: is configs module required for loading overlays ? I can't apply this patch into 4.15 as configfs.c is not compatible with new codebase. …

In my customize-image.sh I need to dowload source via git and make it like user and not like root. Example of customize-image.sh: git clone https://github.com/xxx/xxx /home/pi/xxx su -c "sudo -S /home/pi/xxx/xxx.sh" - pi This work when I build image for OrangePi4 (and all other rk3399 board) It dosen't work when build image for sun8i board like OrangePi Lite. Both git and su command return error and compilation fail. This happen with legacy and mainline kernel, with ubuntu or debian.

Hello. I have some problem, building image from source. I try to build legacy kernel, full image, CLI, for Orange Pi PC and Orange Pi One (the two i have), but it always stops at "LD kernel/built-in.o", with the following error: [ error ] ERROR in function compile_kernel [ common.sh:177 ] on both platforms. I try Ubuntu Xenial and Debian Jessie, same error at the same place, so i don't think it's OS related. I delete the source and git clone again, but this not helped. I also try to build the same image (5.14_Ubuntu_xenial_3.4.112, CLI) for my A20 Lamobo R1 and it builds with no errors. So there must be something with H3 only. As far as i see, line 176 and 177 of…

Hello guys I have a question regarding H3 overlays. I see that during build "overlay" folder is created in arch/arm/boot/dts and H3 overlays are copied there. Can you point, please, where build framework takes those file from and how to customize this ? The goal here is to add an extra overlay. I see that the structure is very similar to https://github.com/armbian/sunxi-DT-overlays but I can't find in build scripts if you copy files from there or any other repository. Thanks.

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=…

Hello, everyone, I found a very serious issue with Armbian build framework: build may corrupt your host's rootfs! This has happened to my system 3 times: my rootfs has been totally destroyed without being able to recover it (I used a number tools, like testdisk, etc. All of the tools detected some deleted files but all of those files appeared to be 0-sized). I have delayed reporting this to be 100% sure that it is Armbian build that caused those issues. Now I am, absolutely, because such a problem NEVER happened to me before (I have been using Ubuntu 16.04 for a long time). After 2nd crash I changed my HDD to a brand new one and installed all again …

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…

Dear All, I´m trying to boot my nanoPi NEO from an external SPI Flash. Actually, I attached a small AT25DF321A and I´m able to see it´s is working: when in FEL mode, using a slightly modified sunxi-tools, there´s the message: osboxes@osboxes:/tmp/marcellus-sunxi-tools/sunxi-tools$ sudo ./sunxi-fel spiflash-info Manufacturer: Adesto AT25DF321A (1Fh), model: 47h, size: 4096k bytes. I can write to and read from it, too. Now, I need to compile U-BOOT with the command "sf" (I know I will need to write another spi driver, but baby steps...). The problem is: when I change the U-BOOT´s .config file and call the "compile.sh" script using the o…

Hi guys setting variables like MAINLINE_KERNEL_SOURCE in userpatches/lib.config does not change anything in the build. Is this fine ? What is the correct place to update this variable ? Thanks

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 …

First. Thanks for so great work in the ARMBIAN community. Any word of gratitude will not be enough. I have been installing Linux on different SBC. Some of them are supported by ARMBIAN, others not. There are some that never will be supported (as the Parallella 16). And the ARMBIAN process it is very clean for the already refined machines. However, when trying to bring up some other machine, it is complicated to understand what to do, how and where, as the process have been evolving for a long period of time. Recently I began to work with @chwe on the BPI-R2, and my first job is to make the nand-sata-install to work. So, I prepared an image to check this, to s…

Hi, From the supported boards list armbian/config/boards$ ls orangepi* orangepi2.conf orangepi.eos orangepimini.eos orangepipc2.conf orangepipcplus.conf orangepiplus.conf orangepi-r1.conf orangepizero.conf orangepizeroplus2-h5.conf orangepi2g-iot.csc orangepilite.conf orangepione.conf orangepipc.conf orangepiplus2e.conf orangepiprime.conf orangepiwin.conf orangepizeroplus2-h3.conf orangepizeroplus.conf we can see that Orange Pi Plus 2e and Orange Pi Plus are supported, however Orange Pi Plus 2 is NOT. These 3 boards are of trivial differences. I wonder if I can use the configuration of Orange Pi Plus 2e …

Today I did build the image for stretch (for M2 Ultra) - but it was a bit strange - because it ended up in a 1.1GB .image file, but the compressed size was only 1.5MB OK, before building the image I got only 6GB free on my virtual HDD - by the last images this did work.... Now I will reinstall my build-system with the double size (60GB against 30GB before) and then I will firstly try to create a xenial image (not stretch which give me the compressed 1.50MB image whcih doesnt boot )

Hi Igor, hi team, we are using Armbian since the the first version. We only using it with Banana Pi and Banana Pi Pro. Yesterday I wanted to build a new image for our BananaPro projects, but unfortunately there is no support for Banana Pi Pro anymore. Why? Is it possible to continue supporting this board? What is the difference to the Banana Pi? You still support Banana Pi. Thanks. Steffen

This might be more targeted towards security, but building Armbian should not be as a root/privileged user... https://docs.armbian.com/Developer-Guide_Build-Preparation/#how-to-start OpenWRT builds fine as a normal user account, does not need elevated access. Also - FWIW - the local build directory should be armbian, not build - too many other things use /build. @Igor-- thoughts here?

Hello guys, I am trying to build another kernel within your framework. Here is what I did: 1) copied sun8i.conf to userpaches/sources and modified kernel source url and branch 2) copied patches to userpatches/kernel/sun8i-dev and removed those that made compilation fail I was able to compile u-boot and kernel, but in the end I am getting the following issue: dpkg-deb: error: failed to read archive '/home/sergey/Projects/orangepi/armbian/output/debs/linux-image-dev-sun8i_5.32_armhf.deb': No such file or directory [ o.k. ] Kernel build done [ @host ] [ o.k. ] Target directory [ /home/sergey/Projects/orangepi/armbian/output/de…

For some days now I get the following error trying to build C4 images. I attempted the --fix-missing, apt update apt upgrade etc, still this after some time in compilation. Running in a Virtualbox direct session, no Vagrant or the like. Had been working fine for quite some time, went a few weeks and decided to rebuild and got this error. Is it trying to download from my own machine? What to do?

Hello guys, is it possible to build custom source code in customize-image.sh ? Seems like /tmp/overlay is read-only, can I use another location to git clone my source code, make and install in target file system ? My idea is to build & deploy sources using native gcc compiler. Thanks

Hello, I am not very experienced on the Armbian development and want to add a kernel driver to the legacy kernel using the compile.sh development tool, but did not grasp the best practice to add the kernel source reading some forum posts and docs. As a start lets add the sunxi-can driver for the Olimex CAN-A20 interface for legacy kernel for Olimex lime2 A20 board like described in the Wiki at Olimex: https://www.olimex.com/wiki/A20-CAN I did: a) http://docs.armbian.com/Developer-Guide_Build-Preparationon an virtual box on my machine and can successfully build kernel packages and apply user-patches enable some patches like the copy /patch…

4.17.y is, even not LTS, but probably better than heavily patched 4.14.y in any way. Shall we do this switch now and start preparing 4.18.y on a DEV?

@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…

I am doing test builds and I notice some strange behaviour. First boot is very short and it resets, than we got this: (Orangepi PC+ / legacy / jessie CLI) What was changed / break here? Is this related to my build host?

Hello. Now, build environment is only Ubuntu 18.04 (bionic). But some time ago, the build environment was Ubuntu 16.04 (xenial). How can I build armbian on Xenial? Maybe, I have to change branch to another, or checkout to certain commit? Help me please...

Hello, all images for OrangePI PC (next) produced since yesterday give the following output: ----------------------------------- U-Boot SPL 2017.11-armbian (Dec 03 2017 - 17:13:28) DRAM: 1024 MiB Trying to boot from MMC1 Uncompressing Linux... done, booting the kernel. Loading, please wait... starting version 232 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block…

Is there any appetite for a smaller, lighter release without systemd ? Unfortunately it breaks some of armbian-config. I use Devuan at times on my desktop and wanted Armbian for a light Arm64 server. I found a Devuan based method to change over, but it is really simple in just Armbian Replace systemd with SysV Init as the init system on Armbian Buster arm64 (nanopc-t4) $ su - # apt update # apt upgrade # apt purge policykit-1 (suggested by Devuan) # apt autoremove # apt install sysvinit-core edit /etc/network/interfaces to include eth0 auto lo eth0 iface lo inet loopback iface eth0 inet dhcp …

Hi, When I start armbian script, there is no Banana Pi M1 model anymore. Was Banana Pi M1 merged with Banana Pi Pro model? I could not find any note or info about this change anywhere. Thank you!

There was recently a discussion on an issue over on github dealing with an issue that popped up when building Armbian within a Docker container. Following on from there, it was decided that it would be a good idea to document the build process using Docker, and adding a howto, best practices, and FAQ to the main Armbian documentation. (I've put my hand up to coordinate this.) Using Docker is a good alternative to a VM, and particularly for anyone on macOS or Windows. So to kick off the thread, it'll be good just to discuss what should go into the docs. Also to see if anyone is interested in building with Docker and hasn't done so yet.

Hi members and developers, I've tried to compile buster with using the latest armbian build environment for an Banana R1 SCB but it failed whith this errors: ... [ o.k. ] Installing base system [ Stage 1/2 ] /home/wolli/build/lib/debootstrap.sh: line 185: debootstrap: command not found [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:190 ] [ error ] Debootstrap base system for current lamobo-r1 buster yes first stage failed [ o.k. ] Process terminated I know that this SBC is EOS thats why I need to compile it by my self. Even when I try to compile a supported SBC linke the Bananapi I got this same debootstrab …

new to the ARMbian build process.. seems very well put together. this is my second attempt at a fresh ARMbian Kernal build in a clean VBox Mini_Ubuntu 16.04 VM. this Kernel build (successful) was invoked by: git clone --depth 1 https://github.com/armbian/build cd build ./compile.sh EXPERT=yes BRANCH=dev RELEASE=xenial BOARD=nanopineo2 KERNEL_ONLY=yes I am still easing into the build process, at the interactive prompt, I opted not to change the kernel's configuration. During the build, I noticed that many modules unrelated to my target NanoPiNeo2 board's hardware.. .. ( yes I know it's still a WIP, then for…

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

Hi there, i try to compile a kernel via: apt-get -y install git git clone https://github.com/igorpecovnik/lib--depth 1 cp lib/compile.sh . chmod +x compile.sh ./compile.sh In compile.sh, i changed: KERNEL_ONLY="yes" and added KERNELTAG="v4.3.5" I get an error which can be seen in the attached file. I was able to compile 4.3.4 on the same machine, so i do not expect enironment issues. Any hint? Thx, A.

How can I debug kernel source code in armbian build system very simply? Each build will need to download source code from the git hub , if add a line of source code，also need patch again, but the process need very super time, what is the simple method?

Hello, I am trying to build a custom Armbian image and I would like to remove some deb packages in order to not to be installed. ¿What would be the right place to do that? Thank you!!

Implement them to board configuration like: DEFAULT_OVERLAY="usbhost2" or hardcode into device tree?