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@going@jeanrhum@dolphs @jock@belfastraven@TRS-80@Bozza@Rich Neese@sgjava@Mangix@tony013

I will confess that I don't even really understand the build system myself.  In fact I think only a few people really do.  So as a side effect I hope to increase my own understanding.  And eventually improve documentation.

For example I am not even sure any of these initiatives are really conflicting with one another?  But I still feel like we should probably discuss them all together, from a high level point of view.

I hope through this process we can come up with some better and more comprehensible architecture which will (ideally) become more accessible to newcomers, ultimately easing the long term maintenance burden (among other benefits).

Some of major initiatives I am aware of currently are:

rpardini fragment / hooks idea

Hooks are used a lot in Emacs for instance, so this idea was immediately comprehensible to me.  It's clear @rpardini has put a lot of thought / effort into that, and there is some very good discussion there, which I encourage everyone to have a good look at.

Architecture for adding additional desktop enviromnents, and application groups

@Myy has done some nice work here.  I am almost embarrassed to state that I am not even sure if this is what @Rich Neese has been implementing with all the desktop stuff, or not?  Desktop / graphical stuff is not my area and I know @JMCC @jock @balbes150 also have additional multimedia stuff which lie outside Armbian itself, but maybe we have an opportunity to make things a little easier on them here?

creating packages in the armbian build system

@going has what seem to me like some great ideas, even if I must confess to only partially comprehending them (Debian packaging being a hairy beast I aspire one day to learn more about).

I feel like I am probably missing some more, in which case please add links to other discussions you may be thinking about which are related.

I encourage everyone to really take the time and try and understand what these people are working on if you have not done so already.  This is probably the most difficult part of this, taking the time and try and really try and understand the other person's point of view (and/or, areas outside our own expertise).

In addition to big initiatives above, I recall several offhand comments I read from @Igor and @balbes150 about long logic chains, maintainability, & etc. which I think we need to also discuss in a broad architectural sense.  I don't know the build scripts deeply enough to comment helpfully, but my hope is that the few people who do can have some sort of productive discussion.

Besides people I already mentioned, I can see from GitHub that @martinayotte @TonyMac32 @piter75 @Werner @lanefu @Heisath @aprayoga and @gprovost are current members of the project who seem to commit to the build scripts a lot.  Please help me by tagging anyone else you think of who may be interested in this discussion, and apologies to anyone I missed.

We need to produce a repository per release for our debs just like Debian ubuntu etc

aka

lane@blipsqueak:~/GIT/lj-tools$ cat /etc/apt/sources.list.d/armbian.list
deb http://apt.armbian.com focal main focal-utils focal-desktop

becomes

lane@blipsqueak:~/GIT/lj-tools$ cat /etc/apt/sources.list.d/armbian.list
deb http://apt.armbian.com/chiru focal main focal-utils focal-desktop

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 packages

* u-boot updates

* -current kernel remains on 5.10LTS!

* testing

* testing

* TESTING

Please share you priorities, thoughts, etc in this thread...  Any format is fine.. post, GitHub link, jira issue.

help me menton peeps plz.

@Igor@Werner @TonyMac32 @martinayotte@piter75 @ning@Myy@balbes150 @sfx2000 @ebin-dev@chwe@gprovost@aprayoga@5kft@JMCC@going@jeanrhum@dolphs @jock@belfastraven@TRS-80@Bozza@Rich Neese@sgjava@Mangix@tony013
 

(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 generally done, but might need fine tuning)

- enable 3D support (also done? Bugfixing)

- discuss support for desktops (IIRC it was planned to have a longer supported LTS desktop version, we need a maintainer for that, if it happens)

- check if remaining boards can / have been updated to LK5.10 (some were left out last release)

- check possible u-boot updates

- complete remaining Jira issues

- cycle and check board support status (espressobin for example needs a new maintainer (otherwise EOS) @Pali maybe?)

- late topics: 

- business meeting schedule

- kernel config changes on arm64

Release Planning Meeting Agenda:

Please add developers and more topics below, I will then also add them here.

@Myy @TonyMac32 @balbes150 @piter75 @sfx2000 @ebin-dev @chwe @ning @lanefu @gprovost @aprayoga @5kft @JMCC @martinayotte @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @Pali

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 scripts for XFCE.

Also :

• the current list of packages for XFCE include unrelated packages (like neverball), added to test the packages files aggregation;
• there's a lot of debug messages added here and there, in order to have an overview of the current build state.

The actual packages list for other desktop environments and distributions, along with the scripts, still have to be added. (They're currently empty)

That said, I'd like to have a few maintainers test (quickly) the new architecture, in order to check if there isn't any obvious feature missing.

So, here's how to add a desktop environment with the new architecture :

Adding a desktop environment

Currently, only official repositories are supported.

Let's say that you want to add that new desktop environment "superduperde", that is now available on official on Debian/Ubuntu repositories.

First, focus on one specific distribution like focal (Ubuntu) or buster (Debian). In our example, will take focal.

We'll create our first configuration 'full', which should provide the DE along with all its specific apps, widgets and the kitchen sink.

• Create the directory config/desktop/focal/environments/superduperde/config_full
• Create the file config/desktop/focal/environments/superduperde/config_full/packages
• Open the packages file, add the list of packages for apt.

Then select it in the configuration menu, or pass the following variables to ./compile.sh :

BUILD_DESKTOP="yes" RELEASE="focal" DESKTOP_ENVIRONMENT="superduperde" DESKTOP_ENVIRONMENT_CONFIG_NAME="config_full"

Then test the resulting image !

Adding an appgroup

Appgroups are roughly the same. Let's say that you want to add remotecontrol to the appgroups for Ubuntu focal :

• Create the directory config/desktop/focal/appgroups/remotecontrol
• Create the file config/desktop/focal/appgroups/remotecontrol/packages
• Open the packages file, add the list of packages for apt.

Tale a look at https://github.com/Miouyouyou/armbian-desktop#the-architecture-added-to-the-build-system, for a more detailed documentation of the new architecture, and how to add special packages files for specific boards, and desktop configurations, along with specific debian/postinst and armbian/create_desktop_packages.sh files.

What needs to be quickly tested :

• Modifying an existing desktop environment (gnome, kde, ...).
• Adding a new desktop environment or window manager (mate-desktop, i3, fluxbox, ...)
• Adding a new appgroup
• Bonus points for adding a desktop environment with Wayland support (but remember that default installations come with terrible OpenGL support on most boards !)

...

[ 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 problems:

...
[ 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 bananapi buster   yes first stage failed
[ o.k. ] Process terminated

Please can somone help me how I can come around this problem and explain what the debiitstrap is trying to do ?

Here are the lines 184 to 191 from my debootstrap.sh in .../buld/lib

184                 eval 'debootstrap --variant=minbase --include=${DEBOOTSTRAP_LIST// /,} ${PACKAGE_LIST_EXCLUDE:+ --exclude=${PACKAG_LIST_EXCLUDE///,}} \
185                         --arch=$ARCH --components=${DEBOOTSTRAP_COMPONENTS} $DEBOOTSTRAP_OPTION --foreign $RELEASE $SDCARD/ $apt_mirror' \
186                          ${PROGRESS_LOG_TO_FILE:+' | tee -a $DEST/debug/debootstrap.log'} \ ${PROGRESS_LOG_TO_FILE:+' | tee -a $DEST/debug/debo$  
187                         ${OUTPUT_DIALOG:+' | dialog --backtitle "$backtitle" 188 --progressbox "Debootstrap (stage 1/2)..." $TTY_Y $TTY_X'} \

188                         ${OUTPUT_VERYSILENT:+' >/dev/null 2>/dev/null'}
189
190                 [[ ${PIPESTATUS[0]} -ne 0 || ! -f $SDCARD/debootstrap/deboo$
191

Thanks
wollik

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?

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 insite Github actions) and real hardware (need implementation).

Examples:
 

- updating images and kernel update for families that those boards belong to: rockpro64, station-p1, station-m1, odroidc2, odroidn2, odroidc4, odroidhc4, odroidxu4, nanopir4s, udoo, cubox-i, rockpi-s, rockpi-e, rockpi-n10. nanopct4, espressobin, tinkerboard

- building under Docker and booting qemu image inside Github action (WIP, not enabled yet)

- upstream kernel changes for a few families caused rebuild and updating of both repositories

I'm trying to build a full bootable image for the Rock pi 4B using a VM with the recommended build system I followed the build instructions in https://docs.armbian.com/Developer-Guide_Build-Preparation/.

I got the image built without errors. At this point I haven't tried the image because I still want to change a source file and recompile.

I changed the file in question: build/cache/sources/linux-mainline/linux-5.10.y/drivers/pci/controller/pcie-rockchip-host.c

and rerun compile.sh in the build directory.

The system builds again without issues, but the file I edited get replaced by the original content along the way. 

Obviously, this is not the way to change the file in the source tree. Is there a workaround? Or what should be the way to accomplish what I'm trying to accomplish, which is simply tweak a specific file of the kernel source code?

Thanks in advance,

Jorge

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 serve as a starting point.

How it works?

In armbian/build

git remote add armbian-build https://github.com/The-going/armbian-build.git
git fetch armbian-build packaging
git checkout -b packaging armbian-build/packaging

./compile.sh NEWPKG="true"

NEWPKG="true" - no longer used

This repository branch changes its commit history by following the flight of thought and eliminating garbage.

Update it with the   -f, --force key

git pull -f armbian-build packaging

Please test and write your wishes and thoughts here.
At this stage, we can opt out of general-packaging-5.X.X.patch

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

# reboot
# apt purge systemd
# rm -rf /etc/systemd /lib/systemd
# reboot

now apt purge unwanted services

Parts of armbian-config are reliant on systemd

but there aren't any apt dependencies ???

nand-sata-install still works to both emmc and nvme

If you want to make the change stick, add systemd to your Apt preferences in /etc/apt/preferences.d/...

Package: systemd
Pin: release *
Pin-Priority: -1

more to test ...

and debian provides a tool: u-boot-menu to update extlinux.conf.

in order to use u-boot-menu in armbian, need to update kernel build scripts, need to follow debian's build rules. or make change to u-boot-menu to fit armbian's kernel.

Since long time ago, build system is stuck at mainline kernel version 5.10.21 (for OrangePi H2+ H3 and H5 boards).

Am I doing something wrong or what?

Best regards.

I'd like build the module for my usb dongle with rtl8821cu. Im using the 4.4.154 version on rk3328 tvboxes. I need the kernel sources. Is the a repo on github for this build? Thanks and excuse me for my English

(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 Neese@Werner 

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

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 target)
Orange Pi Zero Plus
Orange Pi Zero Plus 2
Pine H64
Rockpi 4B
RockPro 64
Tinkerboard (u-boot stays behind)
ZeroPi

- ZSH setting to default or optimise 1st run choosing

- moving blob section (except build packages) to newly created structure inside "desktop" branch (need to discuss best way / adjust framework if needed and set rules!)

- and Jira bugs / features we chose to deal with by then

There are reports about some broken images on Rockchip legacy, K5.9.y is EOL so there is an option to squeeze another bugfix update with focus on u-boot / kernel update + image refreshing. Anything that is outside of my test rig - I have no idea about the statue - except well known NIC troubles with Orangepi 3.

@Myy @TonyMac32 @balbes150 @piter75 @sfx2000 @ebin-dev @Heisath @chwe @ning @lanefu @gprovost @aprayoga @5kft @JMCC @martinayotte @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava

On 3/24/2019 at 10:46 PM, lanefu said:

It would be great if the community could help test more.

well, in a way they do via complaint.  ;-)

A lot of parts need some sort of script, amlogic BSP kernels (not Armbian) are tested in such a way (perform 1000 reboots, etc).

On 3/24/2019 at 10:46 PM, lanefu said:

Are there any simple circuit diagrams people could design to make testing easier...

That I can aid in, but the typical user probably won't have the sorts of things needed.

On 3/24/2019 at 10:46 PM, lanefu said:

run a test script.

https://github.com/armbian/testings

On 3/25/2019 at 12:24 AM, TonyMac32 said:

That I can aid in, but the typical user probably won't have the sorts of things needed

That'd be awesome!

I'm coming from the perspective of creating more opportunities and interest for the undiscovered non-typical users.  

On 3/25/2019 at 7:05 AM, Tido said:

https://github.com/armbian/testings

 

was a nice starter, unfortunately nobody contributes to it and the testings there are really outdated..

I did some tests back then to automate testing (actually it was one of the use-cases I thought about for my BPi-R2 (using its serial from the pinheader to connect them to the serials of the tested boards) doing automated upgrades and check if network comes up, in case not it would try to log-in via serial.. automation has some issues.. e.g. properly filter dmesg issues is hard cause different drivers tend to float dmesg with different errors so it's hard to filter them properly..

You also need some way to powercycle the board (e.g. reboot and powercycle are different things in case of a proper reboot - BPi R2 boots up properly when you powercycle it from eMMC, whereas it doesn't with a simple reboot.. ).

The idea is great, and we need more testing break due to bad testing is something we had to often...

I'm willing to test new images on the boards I've got.
Maybe you could make a checklist with all images that need to be tested. Once tested you check, and it's removed from the list and can be put on download page.

You could also do a button at the download page to let users download the test image, and ask them to give test results. Just an idea.

 

On 3/25/2019 at 6:41 PM, NicoD said:

Maybe you could make a checklist with all images that need to be tested

On 3/25/2019 at 7:05 AM, Tido said:

https://github.com/armbian/testings

  

actually the basics to test are there..

cool so since this a brain storming thread. i wanna try to stay away from thinking about process.  This is more about thinking of creative ways to do testing.

On 3/25/2019 at 7:05 AM, Tido said:

https://github.com/armbian/testings

I didn't see that page. I will use it for my next tests now!

Hi, I tried to push my testing of pineh64-dev compiled from today, but have no access to armbian/testings.git

Is there something I have done in the wrong way?

As you can see I tried 3 times and even with '-f' it does nothing. I tried to push manually but got this error:

On 3/24/2019 at 10:46 PM, lanefu said:

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 design to make testing easier... i2c testing?  bitbang something into the audio input? who knows.

If you are out to test the full functionality of a modern Linux distribution such as Ubuntu including multimedia capabilities, etc, it's quite difficult (I really mean it's rather impossible) to write a script to do it. There are quite simply too many possible use cases. Not even Ubuntu people do it for their x86-64 images. They rely on tens of thousands of users to report on possible bugs.

Personally I test my Amlogic TV boxes running armbian / Ubuntu 18.04 by running a distributed kernel compilation on them. That tests the network functionality, roughly tests the kernel and memory for stability, roughly tests the ext4 filesystem on the SD cards, test the basic functionality of Ubuntu 18.04 on Aarch64 hardware, and... that's it. I am happy to report that for my use case, Armbian Ubuntu has shown exceptional stability on some of the cheapest hardware one can find on the planet.

On 4/2/2019 at 4:17 PM, jeanrhum said:

Is there something I have done in the wrong way?

did you clone your fork when testing? Or did you follow this one?

git clone https://github.com/armbian/testings
cd testings
./createreport.sh

createreport.sh was glued together relatively quickly (I know it cause I wrote it.. ) and its git remote handling is a bit hacky (e.g. upstream and origin).. If you clone from your fork things mess up quickly and then it tries to push directly into armbian/testings for which you don't have commit rights.. I didn't test it recently (just moved a few days ago and more or less all my SBCs are somewhere in boxes.. ).. Once I've a bit more time I'll hopefully clean it up a bit.. can you give me the output of: git remote -v?

On 4/2/2019 at 5:43 PM, AndrewDB said:

If you are out to test the full functionality of a modern Linux distribution such as Ubuntu including multimedia capabilities, etc, it's quite difficult (I really mean it's rather impossible) to write a script to do it. There are quite simply too many possible use cases.

My angle more about any testing vs no testing.

Ya i mostly care about like not seeing dmesg full of noise etc.... extra credit for spi and i2c  and technically the gpu,  and hardware encoding and decoding could be tested headless.

On 4/2/2019 at 7:49 PM, lanefu said:

My angle more about any testing vs no testing.

Oh yes, any testing is way better than no testing. Perhaps document a systematic testing procedure and leave it to the hundreds of Armbian users to do the testing and report on results back here in the forum? I would suggest that would be the better approach to this. Right now most people only bother to report when they have a problem, not when everything works fine for their use case.

On 4/2/2019 at 7:58 PM, AndrewDB said:

Oh yes, any testing is way better than no testing. Perhaps document a systematic testing procedure and leave it to the hundreds of Armbian users to do the testing and report on results back here in the forum? I would suggest that would be the better approach to this. Right now most people only bother to report when they have a problem, not when everything works fine for their use case.

Yes all your points are true, and there are at least some pieces floating around that could be tied together and documented.

I was trying to keep this thread on the creative side and not on the process side.

Ex:

I have a 4 channel relay board and a bag of solder on USB A sockets and the allwinner H3 has like 4 uarts in it.

If we tested images via usb booting its possible a test image could be mounted on another SBC and delivered via usb gadget mode from the OTG port.

On 4/2/2019 at 8:04 PM, lanefu said:

Yes all your points are true, and there are at least some pieces floating around that could be tied together and documented.

I was trying to keep this thread on the creative side and not on the process side.

Ex:

I have a 4 channel relay board and a bag of solder on USB A sockets and the allwinner H3 has like 4 uarts in it.

If we tested images via usb booting its possible a test image could be mounted on another SBC and delivered via usb gadget mode from the OTG port.

That's a little bit complicated, I guess. A much, much simpler approach to testing Armbian images is to network boot them. But then you are not testing an essential functionality that most Armbian users depend upon: the ability to boot from an $4 micro SD card.

Yeah nfs root is would be way simpler.

Main advantage to the theoretical usb boot would being able to test uboot on the image.

Can you chainload uboot from uboot?

On 4/2/2019 at 8:14 PM, lanefu said:

Can you chainload uboot from uboot?

I don't think that's officially supported because both u-boot's would want to load at the same address, so the second one would load on top of the first one and the boot process would crash.

I see there has been some discussion of this in the u-boot mailing list, but you'd have to ask if there is any recent update on this issue.

Also note that some SBC vendors are shipping their boards with u-boot pre-installed on SPI ROM (afaik, Khadas and Libre Computer).

On 4/2/2019 at 7:14 PM, chwe said:

did you clone your fork when testing? Or did you follow this one?

I follow these instructions, but when executing the script it creates a fork on my account. Here is the result of git remote -v:

jeanrhum	https://github.com/jeanrhum/testings.git (fetch)
jeanrhum	https://github.com/jeanrhum/testings.git (push)
origin	https://github.com/armbian/testings (fetch)
origin	https://github.com/armbian/testings (push)

Below is my compile config file and my compilation.log is attached. Any ideas what is going wrong here? I know I don't have the make terget in CLEAN_LEVEL, but I even tried when completely removing the whole armbian-build folder and cloning a fresh repos and removing all apt-cache-ng cache. So it's not due to that.

# Read build script documentation https://docs.armbian.com/Developer-Guide_Build-Options/
# for detailed explanation of these options and for additional options not listed here

KERNEL_ONLY="no"                # leave empty to select each time, set to "yes" or "no" to skip dialog prompt
KERNEL_CONFIGURE="no"            # leave empty to select each time, set to "yes" or "no" to skip dialog prompt
CLEAN_LEVEL="oldcache"    # comma-separated list of clean targets: "make" = make clean for selected kernel and u-boot,
                    # "debs" = delete packages in "./output/debs" for current branch and family,
                    # "alldebs" = delete all packages in "./output/debs", "images" = delete "./output/images",
                    # "cache" = delete "./output/cache", "sources" = delete "./sources"
                    # "oldcache" = remove old cached rootfs except for the newest 8 files

DEST_LANG="en_US.UTF-8"            # sl_SI.UTF-8, en_US.UTF-8

# advanced
EXTERNAL_NEW="prebuilt"            # compile and install or install prebuilt additional packages
INSTALL_HEADERS="no"            # install kernel headers package
LIB_TAG="master"            # change to "branchname" to use any branch currently available.
USE_TORRENT="yes"            # use torrent network for faster toolchain and cache download
ARMBIAN_MIRROR="https://minio.k-space.ee/armbian/dl/"
DOWNLOAD_MIRROR=""            # set to "china" to use mirrors.tuna.tsinghua.edu.cn
CARD_DEVICE=""                # device name /dev/sdx of your SD card to burn directly to the card when done
BOARD="orangepizero"
BRANCH="current"
RELEASE="buster"
BUILD_DESKTOP="no"
BUILD_MINIMAL="yes"

compilation.log

ARMBIAN_MIRROR="https://minio.k-space.ee/armbian/dl/"

the issue disappears. 

I'm not exactly sure where this type of thread goes. If it doesn't go here, can someone please politely move it? Thank you very much!

There seems to be a rogue file in the "/etc/sysfs.d/" directory with the file "20-gpu-governor.conf" on my system. This file is meant to tune the GPU governor to "performance", instead of the default "simple_ondemand".

But I'm confused as to which package supplies this. It is not supplied by sysfsutils, so maybe it's Armbian specific? Not sure. This file is on Armbian for the Helios64.

Here are the contents of the file "/etc/sysfs.d/20-gpu-governor.conf":

# Set "performance" GPU devfreq governor, "simple_ondemand" works bad in recent kernels
devices/platform/ff9a0000.gpu/devfreq/ff9a0000.gpu/governor = performance

Anyway, I just went ahead and APT purged the old-style sysfsutils package, since I wanted to go with something more standardized to systemd, such as tmpfiles.d.

I am using this Arch Wiki page as a reference: https://wiki.archlinux.org/index.php/CPU_frequency_scaling#Make_changes_permanent

Here is the proposed replacement file "/etc/tmpfiles.d/00-armbian-gpu-governor.conf":

# Set "performance" GPU devfreq governor, "simple_ondemand" works bad in recent kernels
w- /sys/devices/platform/ff9a0000.gpu/devfreq/ff9a0000.gpu/governor - - - - performance

I am not sure about udev. However, it seems that as long as "systemd-tmpfiles-setup" is active, it should always set the governor to performance, I did a test with "cat /sys/devices/platform/ff9a0000.gpu/devfreq/ff9a0000.gpu/governor" and it looks like it returned as "performance", so everything is good.

And please, stop using sysfsutils.

apt-update gives the following error -

Err:3 http://repo.aptly.info nightly InRelease

The following signatures couldn't be verified because public key is not available: NO_PUBKEY ED75B5A4483DA07C

but continues.

Is there something I should do or ignore?

I started from scratch and pulled the directory and ./compile'd again and everything seemed to go fine, produced output which I will test today.

https://github.com/150balbes/build/blob/armbian-tv/lib/compilation-prepare.sh

https://github.com/150balbes/wifi

P.S. By the way, I checked the build of all the modules with the source code for Rockchip-legacy, it was enough to add only two new options and all the modules are assembled normally.

• [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 ?) ... What will fail if we update Allwinner to 5.9.y? Mvebu? Rockchip.hf is ready. 
 

@Myy @TonyMac32 @balbes150 @piter75 @sfx2000@ebin-dev @Heisath@chwe@ning@lanefu@gprovost@aprayoga@5kft @JMCC@karabek@Igor@martinayotte@tkaiser@selfbg@Siraj@jock@going 

What else can be squeezed into this mini quick release? Smaller, almost done, things only.

I would also like to point out that we are progressing nicely with:

- updated Desktop variant (sits in our main build repository under the branch "desktop"), where also some other general things has been changed. Merge into master is estimated 2/2021, early adopters are welcome. There are other changes, not just desktop.

- native ARM building. Need more testing, but basics are working.

Today +7 days?

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: downloading using torrent network gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar.xz
gpg: error reading key: No public key
gpg: DBG: locking for '/media/psf/ssd1TB/armbian/cache/.gpg/gnupg_spawn_dirmngr_sentinel.lock' done via O_EXCL
gpg: connecting dirmngr at '/media/psf/ssd1TB/armbian/cache/.gpg/S.dirmngr' failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr
gpg: error reading key: No public key
gpg: DBG: locking for '/media/psf/ssd1TB/armbian/cache/.gpg/gnupg_spawn_dirmngr_sentinel.lock' done via O_EXCL
gpg: connecting dirmngr at '/media/psf/ssd1TB/armbian/cache/.gpg/S.dirmngr' failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr
gpg: assuming signed data in '/media/psf/ssd1TB/armbian/cache/toolchains/gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar.xz'
gpg: Signature made Tue 19 Nov 2013 09:00:03 AM GMT
gpg:                using RSA key D47877808F427EAF
gpg: Can't check signature: No public key
Displaying message: ERROR in function download_and_verify general.sh:1026 err
Displaying message: verification failed  err
Displaying message: Process terminated  info

Any suggestions?

M.

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 @Heisath@chwe@ning@lanefu@gprovost@aprayoga@5kft

@JMCC@karabek@Igor@martinayotte@tkaiser@selfbg@Siraj@jock@going ... (please mention whoever is missed)

Meeting on IRC in Saturday, October 3rd, at 2 pm GMT is being prepared - this is reasonable good timing for US / EU folks.

Agenda:
 

• check meeting attendees (if nick is not self explanatory, add your forum/Github handle. Just say hi or something)
• present tasks, bugs or project you are working on (open discussion if there will not be much people, otherwise meeting officer call people out). Jira should be open in not already.
• cycle Jira backlog:
• discuss task / bug (one at a time)
• assign to person / release / tag
• re-prioritise
• cycle open issues and PR on build engine
• board status update on download pages and build engine (wip, supported, eol)
• choosing upcoming release officer (so far it was Igor and Lane)
• misc / open discussion

Tips:

• when you got a voice, be concise (1-2 min) and make it clear when you stop. ("No more, I'm done")
• channel is recorded so a summary and adjustments to Jira can made afterwards, ideally along with the meeting
• Meeting location is IRC channel #armbian on Freenode. (previous session as an example)

Ideally it would be that prior to this meeting we all update tasks/project statuses in Jira - who still does not have access shall PM to @lanefu or @Igor - reviewing, prioritising and releasing goes faster this way.

  CC [M]  kernel/kheaders.o
[ error ] ERROR in function compile_kernel [ compilation.sh:411 ]
[ error ] Kernel was not built [ @host ]
[ o.k. ] Process terminated 
root@valik-comp:~/armbian-build# 

and no errors in the text above. (full logs in attachments).

please tell me what to do ..?

fulllog.txt.gz

I am trying to build an image based on release 20.08, but kernel does not get compiled.

compile.sh docker BOARD=orangepizero BRANCH=current KERNEL_ONLY=no KERNEL_CONFIGURE=no CLEAN_LEVEL="" NO_APT_CACHER=yes BUILD_MINIMAL=no RELEASE=buster

Displaying message: * [\e[32ml\e[0m][\e[32mc\e[0m] xxx-sun50i-h6-enable-higher-clock.patch  info
Displaying message: Compressing sources for the linux-source package
Displaying message: Compiling current kernel 5.8.16 info
Displaying message: Compiler version arm-none-linux-gnueabihf-gcc 9.2.1 info
Displaying message: Using kernel config file config/kernel/linux-sunxi-current.config info
Displaying message: ERROR in function compile_kernel compilation.sh:411 err
Displaying message: Kernel was not built @host err
Displaying message: Process terminated  info

drivers/net/wireless/rtl8189es/os_dep/linux/ioctl_cfg80211.c:6549:37: error: ‘cfg80211_rtw_mgmt_frame_register’ undeclared here (not in a function)
 6549 |  .update_mgmt_frame_registrations = cfg80211_rtw_mgmt_frame_register,
      |                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[4]: *** [scripts/Makefile.build:281: drivers/net/wireless/rtl8189es/os_dep/linux/ioctl_cfg80211.o] Error 1
make[3]: *** [scripts/Makefile.build:497: drivers/net/wireless/rtl8189es] Error 2
make[2]: *** [scripts/Makefile.build:497: drivers/net/wireless] Error 2
make[1]: *** [scripts/Makefile.build:497: drivers/net] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1754: drivers] Error 2
make: *** Waiting for unfinished jobs....

Am I doing anything wrong? 

Many thanks for the clarification.

Regards

Rostislav

[ o.k. ] Using kernel config provided by user [ userpatches/linux-sunxi64-current.config ]

which is great!

The problem I face is that although the message is shown, the config that takes place seems to be something different, as can be checked when booting the image and looking up the config file in /boot/config-5.9.8-sunxi64

Digging a little bit in compilation.sh, I can see that

cp .config "${DEST}/config/${LINUXCONFIG}.config"

will only be run if KERNEL_CONFIGURE=yes

As I want a fully automated image build, I have set in my config-default.conf:

KERNEL_CONFIGURE="no"

KERNEL_KEEP_CONFIG="no"

How can I run then an automated (no human intervention) build with a custom kernel config? Am I missing something here or is it currently not possible?

I was trying to overclock my RockPro64 and ended up writing a  device tree overlay (and a rather rudimentary one at that).

wasn't sure how to contribute it so I am posting the code here instead. Please note, however, that up until yesterday, I had never written a device tree overlay, so this will not be in the correct format by any stretch of the imagination. I just figured I would post them here as a starting point for anyone who wishes to create a properly formatted dts file to contribute.

I got the values that I used from this page on the pine64 wiki: https://wiki.pine64.org/index.php/Overclocking#Rockchip_RK3399_based_boards

/dts-v1/;
/plugin/;
&{/opp-table0} {
	opp06 {
		opp-hz = /bits/ 64 <2080000000>;
		opp-microvolt = <1250000>;
	};
};

&{/opp-table2} {
	opp06 {
		opp-hz = /bits/ 64 <950000000>;
		opp-microvolt = <1200000>;
	};
};

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.

Application A1, A2,..An

Board B1, B2,...Bn

1) Create multiple compile_Ax_By.sh, containing:

#!/bin/bash
# Define my application
MYAPP=A1
# Call ./compile.sh with predefined parameters
./compile.sh BOARD="orangepipcplus" BRANCH="current" RELEASE="focal" BUILD_DESKTOP="yes" KERNEL_ONLY="no" KERNEL_CONFIGURE="no"

2) In userpatches/customize-image.sh add a single line to my custom my-custom-image.sh (in case original got overwritten by update)

3) In userpatches/my-custom-image.sh put my main logic with case and/or common functions:

# MY VARIABLES
...
# MY MAIN
main() {
 case $MYAPP in
 App1)
  ...
 App2)
  ...
 esac
}
# MY SUBS
...

4) Create userpatches/lib.config and form a similar case structure for variables

case $HKBOX_TYPE in
App1)
  PACKAGE_LIST_ADDITIONAL="$PACKAGE_LIST_ADDITIONAL ..."
  ;;
App2)
...
esac

# common ones here

One thing I couldn't find is the name of the final image. Something like Armbian_MyApp_MyBoard_....img would be nice. Otherwise it overwrites the original...

I'm trying the build environment on VirtualBox and modifying settings and adding new scripting. I have had a habit of testing each modification right away, but the compile/burn/on-device-test is not logical.

How can I emulate a device / setup / install process? Is there any way?

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?

Kernel should have build-in filesystem support, and `RELEASE` have to contain required filesystem utilities. Then all need to be done — add filesystem to build process. Patch for builder attached.

Then image have to be build with separate /boot filesystem.

command should look like

./compile.sh BOARD=rockpi-4a BRANCH=current RELEASE=focal BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=yes BOOTSIZE=250 ROOTFS_TYPE=xfs

add_xfs_root.patch

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/

I recently went through the exercise of getting the Armbian build system set up to create an image with some of my user customizations, similar to the example with OMV. The documentation and forums have been a huge help!

As I am running Fedora and Windows as my main OSes, I did struggle a bit at first. I tried, in order:

• Ignoring the advice of the documentation, and running ./compile.sh on Fedora. Didn't get far
• Running the build with Docker on Fedora. I ran into a number of different problems and ultimately gave up.
• Running on Ubuntu 18.04 on WSL2. I did eventually get a build to complete, but the image may have been corrupt because my device didn't boot at all
• Considered using Vagrant, but decided to give Multipass a try. Worked like a charm on the first try on both my environments!

I didn't find anything on the forums or documentation about using multipass to manage build VMs, so I decided to create a small gist here documenting how I got it working: https://gist.github.com/atomic77/7633fcdbf99dca80f31fd6d64bfd0565

For any not familiar, multipass is a Canonical tool that is optimized for creating Ubuntu VMs, which seems perfect for Armbian since that's the preferred platform anyway. Since it's so focused, it's very simple to use and all the utilities like shared mounts work seamlessly compared to Vagrant.

If this could be helpful to others, I'd be happy to incorporate any feedback into a page for the documentation.

I did the following:

git clone -b v20.08 https://github.com/armbian/build build-orange-pi-v20.08
cd build-orange-pi-v20.08 && git reset --hard 6e9b07e

touch .ignore_changes
./compile.sh docker BRANCH=current BOARD=orangepizero KERNEL_ONLY=no KERNEL_CONFIGURE=no RELEASE=buster BUILD_DESKTOP=no CLEAN_LEVEL="" NO_APT_CACHER=yes

The build ends with "ERROR in function compile_kernel [ compilation.sh:411 ]"

When I clone the master without sticking to a revision, it's working fine.

But I want to stick to an "official" build. How can this be done?

I find that quite confusing and if I am right with my assumption, I would like to add a note to the documentation for future users.

Or: Would it be possible to mount the whole repo to the Guest?

------------------------------------------

Oh well. There IS something wrong but not with the toolchain download...

rock64 focal current desktop

  HOSTLD  tools/mkimage
tools/Makefile:134: recipe for target 'tools/_libfdt.so' failed
Makefile:1278: recipe for target 'tools' failed
[ error ] ERROR in function compile_uboot [ compilation.sh:220 ]
[ error ] U-boot compilation failed 
[ o.k. ] Process terminated 

#compilation log:

tools/libfdt_wrap.c:149:11: fatal error: Python.h: No such file or directory
 # include <Python.h>
           ^~~~~~~~~~
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
make[1]: *** [tools/_libfdt.so] Error 1
make: *** [tools] Error 2

Seems to depend on Python2

   19 | int ____ilog2_NaN(void);
      | ^~~
  File "./tools/dtoc/dtoc", line 50
    print result
               ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(result)?
  File "./tools/dtoc/dtoc", line 50
    print result
               ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(result)?
make[1]: *** [include/generated/dt-structs-gen.h] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [tpl/dts/dt-platdata.c] Error 1
make: *** [tpl/u-boot-tpl.bin] Error 2
make: *** Waiting for unfinished jobs....

Yup. Forcing Python2 works.

Not sure if Python2 was still default on Bionic but I guess so.

Might become an issue with building on Focal in future. Need to test this somewhen...

https://www.freedesktop.org/software/systemd/man/systemd-firstboot.html

Quote

The system locale, more specifically the two locale variables LANG= and LC_MESSAGES

The system keyboard map

The system time zone

The system hostname

The machine ID of the system

The root user's password

archlinux Wiki:

https://wiki.archlinux.org/index.php/systemd-firstboot

git clone --depth 1 https://github.com/armbian/build

cd build/

./compile.sh

I selected full OS, didn't change kernel config, selected rock64, current, focal, image with desktop.

I am getting these errors:

[ o.k. ] Build host OS release [ bionic ]
[ o.k. ] Syncing clock [ host ]
[ o.k. ] Checking for external GCC compilers
[ error ] ERROR in function download_and_verify [ general.sh:1296 ]
[ error ] verification failed
[ o.k. ] Process terminated

I tried selecting different types of builds in configuration menus, but the build always fails.  I tried deleting build directory and starting over several times, but no luck.  I also tried adding USE_TORRENT="no" to the command line, as was suggested in several posts I found on the topic, but that didn't work either.  What am I doing wrong?  How can I build my image?

Sorry if this question had been asked or answered . I didnot find any clues from searching at this forum. Thanks !

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.

Probably not a supported build environment but I figured I'd see if there was a simple fix rather than spinning up another VM... Came back here because I randomly looked and saw that UDOO was no longer obsolete (THANKS!)

CPU configuration:
392000 - 996000 with interactive
Displaying message: Preparing host info
Displaying message: Build host OS release focal info
Displaying message: Syncing clock host info
Displaying message: Checking for external GCC compilers  info
Displaying message: downloading using torrent network gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar.xz
gpg: keybox '/mnt/e/_Code/armbian/build/cache/.gpg/pubring.kbx' created
gpg: /mnt/e/_Code/armbian/build/cache/.gpg/trustdb.gpg: trustdb created
gpg: error reading key: No public key
gpg: connecting dirmngr at '/mnt/e/_Code/armbian/build/cache/.gpg/S.dirmngr' failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr
gpg: error reading key: No public key
gpg: connecting dirmngr at '/mnt/e/_Code/armbian/build/cache/.gpg/S.dirmngr' failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr
gpg: assuming signed data in '/mnt/e/_Code/armbian/build/cache/toolchains/gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar.xz'
gpg: Signature made Tue 19 Nov 2013 02:00:03 AM MST
gpg:                using RSA key D47877808F427EAF
gpg: Can't check signature: No public key
Displaying message: ERROR in function download_and_verify general.sh:1199 err
Displaying message: verification failed  err
Displaying message: Process terminated  info

output.log torrent.log

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 @count-doku @chwe @ning @lanefu @gprovost @aprayoga @5kft @JMCC @Werner @karabek @martinayotte @tkaiser @selfbg @Siraj @jock @going ...

I am preparing a meeting on IRC in Saturday, July 4th, at 2 pm GMT - this is reasonable good timing for US / EU folks.

Agenda:
 

• check meeting attendees (if nick is not self explanatory, add your forum/Github handle. Just say hi or something)
• present tasks, bugs or project you are working on (open discussion if there will not be much people, otherwise meeting officer call people out). Jira should be open in not already.
• cycle Jira backlog:
  • discuss task / bug (one at a time)
  • assign to person / release / tag
  • re-prioritise
• cycle open issues and PR on build engine
• board status update on download pages and build engine (wip, supported, eol)
• choosing upcoming release officer (so far it was me and Lane)
• misc / open discussion

Tips:

• when you got a voice, be concise (1-2 min) and make it clear when you stop. ("No more, I'm done")
• channel is recorded so a summary and adjustments to Jira can made afterwards, ideally along with the meeting
• Meeting location is IRC channel #armbian on Freenode. (previous session as an example)

Ideally it would be that prior to this meeting we all update tasks/project statuses in Jira - who still does not have access shall PM to @lanefu or @Igor - reviewing, prioritising and releasing goes faster this way.

OFFLINE_WORK ( yes | no ): skip downloading and updating sources as well as time and host check. Set to “yes” and you can collect packages without accessing the internet

but also IGNORE_UPDATES=yes. 

Probably because of this is main.sh:

 # ignore updates help on building all images - for internal purposes
if [[ $IGNORE_UPDATES != yes ]]; then
display_alert "Downloading sources" "" "info"

I don't see here in main.sh where is is checking for build-all.....  so it seems that unless i specify IGNORE_UPDATES=yes, the system still downloads  sources.    

No big problem,  but I thought someone more familiar with how the scripts are supposed to work could look into it....

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?

BOARD=tinkerboard RELEASE=buster BRANCH=current BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no INSTALL_HEADERS=yes BUILD_MINIMAL=yes

The system information is as follows (on Tinker Board):

root@tinkerboard:~# cat /etc/armbian-release 
# PLEASE DO NOT EDIT THIS FILE
BOARD=tinkerboard
BOARD_NAME="Tinkerboard"
BOARDFAMILY=rockchip
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=04ae9e4f
DISTRIBUTION_CODENAME=buster
DISTRIBUTION_STATUS=supported
VERSION=20.08.0-trunk
LINUXFAMILY=rockchip
BRANCH=current
ARCH=arm
IMAGE_TYPE=user-built
BOARD_TYPE=conf
INITRD_ARCH=arm
KERNEL_IMAGE_TYPE=Image
root@tinkerboard:~# cat /etc/os-release 
PRETTY_NAME="Armbian 20.08.0-trunk Buster"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@tinkerboard:~# uname -r
5.7.14-rockchip

I also found weird stuff in install.log. I checked out v20.05 but the log said the build.sh was installing v20.08.
I'm missing something. What is it?

# output/debug/install.log
---
dpkg-deb: building package 'armbian-firmware' in 'armbian-firmware_20.08.0-trunk_all.deb'.
dpkg-deb: building package 'armbian-firmware-full' in 'armbian-firmware-full_20.08.0-trunk_all.deb'.
dpkg-deb: building package 'linux-buster-root-current-tinkerboard' in '/home/vagrant/armbian/.tmp/buster/linux-buster-root-current-tinkerboard_20.08.0-trunk_armhf.deb'.
(snip)

Any suggestions are appreciated.

Thanks.

So I spent the bulk of the afternoon and got nowhere.  My desktop is a Fedora System.  I don't want to install VirtualBox again (which is what I did several years ago in order to get the H3 sources).  I tried the Docker thing, but Fedora 32 and Docker don't work together.  Then I remembered that I have access to a system running Fedora 30, and the Docker setup worked fine there, but the process choked with this:

[ o.k. ] Cleaning /root/armbian/output/debs for [ orangepipc2 current ]
[ o.k. ] Cleaning [ arm-trusted-firmware-sunxi-mainline/master ]
[ o.k. ] Compiling ATF
[ o.k. ] Compiler version [ aarch64-none-linux-gnu-gcc 9.2.1 ]
[ o.k. ] Started patching process for [ atf sunxi64-orangepipc2-current ]
[ o.k. ] Looking for user patches in [ userpatches/atf/atf-sunxi64 ]
[ warn ] * [l][c] 0001-Fix-reset-issue-on-H6-by-using-R_WDOG.patch [ failed ]
[ error ] ERROR in function compile_atf [ compilation.sh:78 ]
[ error ] ATF compilation failed
[ o.k. ] Process terminated

So, I don't know quite what is wrong here.  Presumably some patch didn't go in right.

And I am virtually certain this applies to U-Boot, which I don't (at this time anyway) really want the sources for anyway.

So I am thinking.  All I want is the patched sources.  I don't need (or want) to compile anything.  I wonder if I can study the Armbian ./compile.sh script and just pull out the part that fetches kernel source, fetches patches, and applies them.

I looked at this years back and it is quite a monster of a bash script.  Well if anyone has ideas, I am all ears.

     Tom

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?

./compile.sh  BOARD=orangepi3 BRANCH=current RELEASE=buster BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img CLEAN_LEVEL=images OFFLINE_WORK=yes CRYPTROOT_ENABLE=yes CRYPTROOT_PASSPHRASE="MYSECRECTPASS" CRYPTROOT_SSH_UNLOCK=yes CRYPTROOT_SSH_UNLOCK_PORT=2222 CRYPTROOT_PARAMETERS="custom cryptsetup options"

invoke-rc.d: policy-rc.d denied execution of start.
Processing triggers for systemd (241-7~deb10u4) ...
[ o.k. ] Calling image customization script [ customize-image.sh ]
[ o.k. ] Unmounting [ /home/sysadmin/Desktop/nikunj/build/.tmp/rootfs-current-orangepi3-buster-no-yes ]
[ o.k. ] Preparing image file for rootfs [ orangepi3 buster ]
[ o.k. ] Current rootfs size [ 654 MiB ]
[ o.k. ] Creating blank image for rootfs [ 944 MiB ]
[ .... ] dd:  944MiB [ 262MiB/s] [===================================================================================================================================================================>] 100%
[ o.k. ] Creating partitions [ /boot: ext4 root: ext4 ]
[ .... ] Encrypting root partition with LUKS... [ cryptsetup luksFormat /dev/loop0p2 ]
Device custom doesn't exist or access denied.
Device /dev/loop0p2 is not a valid LUKS device.
[ o.k. ] Root partition encryption complete. 
[ error ] ERROR in function check_loop_device [ image-helpers.sh:79 ]
[ error ] Device node /dev/mapper/armbian-root does not exist 
[ o.k. ] Process terminated 
[ o.k. ] Unmounting [ /home/sysadmin/Desktop/nikunj/build/.tmp/rootfs-current-orangepi3-buster-no-yes/ ]
Device armbian-root is not active.
[ error ] ERROR in function unmount_on_exit [ image-helpers.sh:66 ]
[ error ] debootstrap-ng was interrupted 
[ o.k. ] Process terminated 
 

it will be great support if anyone can guide me what should be wrong by me so i can move forward and validating this feature.

Thanks & Best Regards,
Nikunj Patel

I want to flash armbian.img image on olimex rev k board via mini usb to usb cable host machine (Linux ubuntu) without sd card.

Please suggest the way How to do it.

A little help will really be appreciable.

Thanks

Sachin Pundir

Consider adding missing package btrfs-progs to minimal image or warn user when building of such system image is complete so user can resize root manually before the sd card is inserted.

[warn] low disk space [5GB]

I deleted the output directory and still states only 6 GB. I had given virtualbox 30 gb for this drive.

What is the proper way to clean out the drive after a compile? Just ignore it, does it over write?

Sorry if I missed this in the docs somewhere but I didn't find anything about it.

I installed Virtualbox greater than the version noted on the instructions page. (https://docs.armbian.com/Developer-Guide_Build-Preparation/)

Used the mini image at http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/legacy-images/netboot/mini.iso per above page.

During the install I did not check any options for system software.

Started the os and installed git using sudo per the instructions page in the second line above.

After it completed I changed to the build directory and issued the compile

sudo ./compile.sh 

and seems to run as expected. I select Full OS Image -> Show a kernel configuration menu -> (select ANY board) -> Current, and it seems to run fine until it gets to the following error -

2013??

This is the roadblock every time for me. What step did I miss or err?

After a few tries I noticed it has a very brief error on boot -

but I don't see how that would cause a download error or use a file from 2013?

Guidance would be awesome at this point ;]

.

1. build only uboot but don't want to fetch and extract sources again.
2. build only kernel but don't want to fetch and extract sources again.
3. build only rootfs but don't want to fetch and extract sources again.
4. build whole image without internet access in my system

it will be good if anyone can help me for this so i can speed up my development.

https://docs.armbian.com/Developer-Guide_Build-Preparation/

Thanks & Best Regards,

Nikunj Patel

I am on ubuntu so I don't understand why should I have mix of debian and ubuntu packages

I have learned about Clean Levels. I am new to all of this.

So I was not cleaning anything. I wanted to build the kernel locally after config.

I noticed another thread about not seeing the menuconfig during the build

even though it was requested. After hand deleting the target linux image deb,

then menuconfig was invoked properly.  I mention this to indicate that I dont

really have control over this "cleaning" yet but I am getting there.

I really dont want to clean too much but I have started over with a good cleaning.

To simplify things I want to focus on the Minimal Server without Debian packages.

I think there is a bug in main.sh line 344

[[ $BUILD_MINIMAL == yes ]] && EXTERNAL=no

I think if I have BUILD_MINIMAL then I can get no EXTERNAL_NEW

which I want. Otherwise I will get EXTERNAL_NEW since the options are

really local or remote but I want EXTERNAL_NEW=no

but you are setting EXTERNAL=no

a search shows this is an unused variable.

so I changed it to EXTERNAL_NEW=no

otherwise I suppose the config I can ignore the options and set EXTERNAL_NEW to "no" there.

All this takes some time. I could check that but I have started over so it will be awhile LOL.

 I think I will be familiar with the process soon enough.

Thanks, for endurance

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

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:          127M        256K        127M
   3 Swap:          2.0G          0B        2.0G
   1 Swap:          513M          0B        513M
   1 Swap:          617M          0B        617M

So we have 182 times swap usage monitored and get 1 single occasion when swapping occured (the 256KB case here was not swapping but zram instead and the 22MB case there is the only occurence of real swapping and also an 'Out of memory: Kill process' event has been logged with kernel 4.11, no idea what @op1tjaap did back then).

IMO this justifies overthinking our approach especially on boards with low memory since zram is an alternative. Currently there are a few hundred Armbian installations out there running Jessie with Ubuntu's zram-config package installed (zero swap configured, vm.swappiness=0, zram-config defaults resulting in zram area half the size of physical available memory). Not a single complaint so far. But vm.swappiness=0 is a pretty bad setting for such a configuration since as we see above swapping will be avoided anyway if possible.

When using vm.swappiness=100 available DRAM will be used way more efficient. But I've to admit that in my testings available memory has never been an issue anyway. So what about the following:

• add zram-config to Xenial default package list
• modify /etc/init.d/firstrun to skip swap file creation if this package is installed and branch=next|dev and set vm.swappiness=100 instead of vm.swappiness=0

This way we can collect within half a year some details about zram usage (count of complaints and again collecting free output through 'armbianmonitor -u' output)

Edit: Added mainline kernel requirement

Not sure if it is me not understanding (may well be! built my last kernels in 1997 I think...) or a flaw in this patch:

https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/general-sunxi-overlays.patch

which is supposed to fix this bug if I understand correctly:

https://github.com/armbian/build/pull/1663

Looking at the patch file in my built tree: build/patch/kernel/sunxi-dev/general-sunxi-overlays.patch

To my understanding it contains the (re)addition of dts files for sun7i-a20-spi{0..2}, i.e. as of line 3456 it addes the spi0.dts source.

However, building the dev kernel (latest, git updated two days ago), there is no corresponding dtbo file in /boot/dtb/overlays/ afterwards, I checked the resulting .deb.

However, checking the sources deb file that is created, I can find the spi0.dts source file in arch/arm/boot/dts/overlay/sun7i-a20-spi0.dts

SO, my understanding: The patch is applied, it causes the .dts source file to be created, but it never gets compiled.

Looking again at the patch, after line 53 where the makefile is to be updated, it does not enlist the sun7ia-a20-spi{0..2}.dtbo files (as it does for sun5i-a13 after line 37).

I've added three lines in that sun7i makefile block and started another built, which results in those spi{0..2}.dtbo files in the dtb-dev deb file.

Not installed onto my cubietruck yet, so can't say if the patch actually helps with my original problem.

Is the patch broken? Or did I miss the point?

I'm planning to use Armbian for a custom distribution (target is Orange Pi Zero, for now). Usually, for this kind of job I use Yocto.
But this time, I intend to use the board as a ROS server, and quite frankly, integrating ROS into Yocto is quite painful. As it will be used only for a hobby robotics project, I don't really mind using another method.

So, the thing is, I intend to create a customized Armbian distro with ROS preinstalled.

But, I will also need to cross-compile and install some of my own projects.

I was wondering, what is the most standard way to cross-compile (mostly C++, here, but whatever) a project for integration into the image ?

Using Yocto, I can create a "SDK" using the "populate_sdk" command, which creates a self-extractable archive containing toolchain+libs. What would be the equivalent in the Armbian build framework ?

Thanks in advance, and congratulation for the great job accomplished on Armbian !

do you already have SUBJ ?

Thank you

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

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 files that have been part of a previously installed package and leaves all other files in place.

An example:

Preparing to unpack .../38-linux-image-current-sunxi_20.02.11_armhf.deb ...
update-initramfs: Deleting /boot/initrd.img-5.6.3-sven1    <--- There again
Removing obsolete file 5.4.30-sunxi
Removing obsolete file uInitrd-5.6.3-sven1                 <--- Not obsolete but actually a part of the running kernel
Removing obsolete file uInitrd-5.4.30-sunxi
update-initramfs: Deleting /boot/initrd.img-5.4.30-sunxi
Unpacking linux-image-current-sunxi (20.02.11) over (20.02.9) ...

I'd appreciate it if somebody could make this stop.

As I understand the compile.sh script will not auto-update Armbian.

What is the right procedure to update Armbian in this case? Just run git pull from $SRC? Could compile.sh script accomodate this scenario?

I use the amlogic S905W (TX3mini) 

When I would like to start my PPP connection my Kernel says missing Module:

Couldn't open the /dev/ppp device: No such file or directory
modprobe: FATAL: Module ppp_generic not found in directory /lib/modules/5.5.1-arm-64
pppd: You need to create the /dev/ppp device node by
executing the following command as root:
        mknod /dev/ppp c 108 0

Please check kernel 5.5.1-arm-64

Many Thanks

Cheers,

Dolf.

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 information.  I will also update release process documentation as we progress.

I am going to go ahead and cut a release branch to learn and further document the process, but the official release branch won't be cut until the Release Candidate Code Freeze Date.

Tagging a few devs here from memory.. please tag others....  @Igor @gprovost @martinayotte @chwe @TonyMac32 @count-doku @balbes150 @Tido

./compile.sh docker <conf_name>

 It still displays the configuration menu for me.

Thanks in advance.

First issue:

With the 5.4.18-sunxi64 kernel when you select in Armbian-config to install kernel headers it installs the wrong version, it install kernel headers for 5.3 something instead of the 5.4.18. 

The way that I was able to work is by compiling the 5.4.18-sunxi64 Linux version including the Kernel headers.

I have attached it here.

Second issue:

When "make scripts" and make modules_prepare instead of link to the 5.4.18-sunxi64 it creates a link for modules in 5.4.18 which makes the modules useless, since it doesnt go to the correct /lib/modules library.

instead that the modules will be installed in lib/modules/5.4.18-sunxi64, it install it in /lib/modules/5.4.18.

The way to fix it is to modify the Makefile and add the -sunxi64.

VERSION = 5
PATCHLEVEL = 4
SUBLEVEL = 18
EXTRAVERSION = -sunxi64
NAME = Kleptomaniac Octopus

Third issue:

When "make modules_prepare" it fail to finish with this error:

recipe for target 'vdso_prepare' failed and exit.

The way to fix it is to comment out the vdso_prepare in the Makefile at: 

/usr/src/linux-headers-5.4.18-sunxi64/arch/arm64

Edit Makefile:

and search for vdso_prepare

ifeq ($(KBUILD_EXTMOD),)
# We need to generate vdso-offsets.h before compiling certain files in kernel/.
# In order to do that, we should use the archprepare target, but we can't since
# asm-offsets.h is included in some files used to generate vdso-offsets.h, and
# asm-offsets.h is built in prepare0, for which archprepare is a dependency.
# Therefore we need to generate the header after prepare0 has been made, hence
# this hack.
#prepare: vdso_prepare
#vdso_prepare: prepare0
#       $(Q)$(MAKE) $(build)=arch/arm64/kernel/vdso include/generated/vdso-offs$
#       $(if $(CONFIG_COMPAT_VDSO),$(Q)$(MAKE) \
#               $(build)=arch/arm64/kernel/vdso32  \
#               include/generated/vdso32-offsets.h)

After all that I was able to compile and work with the kernel module.

Hope that it helps anyone.

linux-headers-5.4.18-sunxi64.tar.gz

When running ./compile.sh, I get the option to customize the kernel via dialog and I did select some customizations. When saving the config, I choose the default `.config` as output. However, when running `./compile.sh` a second time, all the settings are back at default and I can not find any `.config` file anywhere in the tree.

vagrant@ubuntu-bionic:~/armbian$ tree output
output
├── config
│   └── linux-rockchip64-current.config
├── debs
│   ├── armbian-config_19.11.9_all.deb
│   ├── armbian-firmware-full_19.11.9_all.deb
│   ├── armbian-firmware_19.11.9_all.deb
│   ├── buster
│   │   ├── armbian-buster-desktop_19.11.9_all.deb
│   │   └── linux-buster-root-current-rock64_19.11.9_arm64.deb
│   ├── extra
│   ├── linux-dtb-current-rockchip64_19.11.9_arm64.deb
│   ├── linux-headers-current-rockchip64_19.11.9_arm64.deb
│   ├── linux-image-current-rockchip64_19.11.9_arm64.deb
│   ├── linux-source-current-rockchip64_19.11.9_all.deb
│   └── linux-u-boot-current-rock64_19.11.9_arm64.deb
├── debs-beta
│   └── extra
├── debug
│   ├── compilation.log
│   ├── compiler.log
│   ├── install.log
│   ├── installed-packages-buster.list
│   ├── logs-.tgz
│   ├── logs-30_01_2020-17_09_53.tgz
│   ├── logs-30_01_2020-17_14_25.tgz
│   ├── logs-30_01_2020-17_15_51.tgz
│   ├── logs-30_01_2020-17_16_04.tgz
│   ├── logs-30_01_2020-17_20_34.tgz
│   ├── logs-30_01_2020-17_26_32.tgz
│   ├── logs-31_01_2020-13_12_45.tgz
│   ├── output.log
│   ├── patching.log
│   └── timestamp
├── images
│   ├── Armbian_19.11.9_Rock64_buster_current_5.4.16.img
│   └── Armbian_19.11.9_Rock64_buster_current_5.4.16.img.txt
└── patch


vagrant@ubuntu-bionic:~/armbian$ tree userpatches
userpatches
├── Dockerfile
├── README
├── Vagrantfile
├── atf
│   ├── atf-rk3399
│   ├── atf-rockchip64
│   └── atf-sunxi64
├── config-default.conf -> config-example.conf
├── config-docker.conf
├── config-example.conf
├── config-vagrant.conf
├── customize-image.sh
├── kernel
│   ├── imx6-current
│   ├── meson64-current
│   ├── meson64-dev
│   ├── meson64-legacy
│   ├── mt7623-legacy
│   ├── mvebu-current
│   ├── mvebu-dev
│   ├── mvebu-legacy
│   ├── mvebu64-current
│   ├── mvebu64-dev
│   ├── mvebu64-legacy
│   ├── odroidxu4-current
│   ├── odroidxu4-legacy
│   ├── rk3399-legacy
│   ├── rockchip-current
│   ├── rockchip-legacy
│   ├── rockchip64-current
│   ├── rockchip64-dev
│   ├── rockchip64-legacy
│   ├── rockpis-legacy
│   ├── s5p6818-legacy
│   ├── sunxi-current
│   ├── sunxi-dev
│   └── sunxi-legacy
├── misc
├── overlay
├── rock64.conf
└── u-boot
    ├── u-boot-helios4
    ├── u-boot-imx6
    ├── u-boot-imx7d
    ├── u-boot-meson
    ├── u-boot-meson64
    ├── u-boot-mt7623
    ├── u-boot-mvebu
    ├── u-boot-mvebu-dev
    ├── u-boot-mvebu-next
    ├── u-boot-mvebu64
    ├── u-boot-odroidn2
    ├── u-boot-odroidxu4
    ├── u-boot-rk3399
    ├── u-boot-rockchip
    ├── u-boot-rockchip64
    ├── u-boot-rockchip64-dev
    ├── u-boot-s5p6818
    ├── u-boot-sun50iw2
    ├── u-boot-sun50iw6
    └── u-boot-sunxi


vagrant@ubuntu-bionic:~/armbian$ tree /tmp/
/tmp/
├── headers-debian-byteshift.patch
├── systemd-private-e9159b9661b4464181744cd8fd1f8045-systemd-resolved.service-iF9CdM [error opening dir]
├── tmp.90M3rBtEQs
├── tmp.KebGKiskk9
├── tmp.PEIvp4IFHe
├── tmp.pHeo3L7lGP
└── vagrant-shell

No files in `userpatches` are changed since before running the compile.

Reading https://docs.armbian.com/Developer-Guide_Build-Preparation/#providing-build-configuration suggests new config files should be generated but I can't locate any. The files in userpatches are untocuhed.

I do see `./output/config/linux-rockchip64-current.config` - this seems to contain kernel config (I did a build for rockchip64 here). Is this what I'm looking for? If so, how do I reuse this in a sustainable way?

Lastly, do I get it right if by default I should put generic customizations in `./userpatches/config-default.conf` and board-specific ones in e.g. `./userpatches/rock64.conf`? (Asking since docs seem to be very out of date wrt directory structure)

When I ran compile.sh inside the VM it installed a load of packages as it should, then eventually failed due to dialog not being installed.

A simple apt install dialog fixed everything, presumably the build system needs to be updated to install dialog as well?

I'm trying to compile a new image with armbians build environment.

Basically the process works as expected, as long as i recompile everything.

But i want to make some changes to the KERNEL source before compiling.

Therefore i have enabled the following flags:

CREATE_PATCHES="yes"

KERNEL_ONLY="yes"                            # build kernel only
SOURCE_COMPILE="yes"                        # force source compilation
KERNEL_CLEAN="yes"                          # MAKE clean before compilation

CLEAN_LEVEL="sources"

But, it does not clean the Kernel and it does not recompile it.

Do you have any advice for me?

Thanks

I need to add a second SD card reader to my Orangepi zero. I tried with this link https://github.com/nopnop2002/STM32_TFT_8bit . But it doesn't work. I read that SPI is not enabled in Orangepi kernel and i checked with ls /dev/*spi*  and the output was - ls: cannot access '/dev/*spi*': No such file or directory.

So i edited the /boot/armbinaEnv.txt as adding "overlays=spi-spidev" and rebooted. then checked ls /dev/*spi* and out is - /dev/spidev0.0. But my code is not working..Can you tell me what is wrong here ? These are my pin configuration

SD CARD                           OPI zero

------------------------------------------------------------

GND        (6)                      GND     (6)

VCC        (4)                       3.3V     (1)

MISO     (7)                       Pin#21(SPI MISO)

MOSI     (2)                       Pin#19(SPI MOSI)

SCK       (5)                       Pin#23(SPI SCLK)

CS         (1)                       Pin#26(SPI CE)

After building a DEV Pine64 image successfully, I wanted to build a Dev BananaPI image to update 2 banana pis. Unfortunately I have this error (using this commit  id : e7aeffb1) :

Setting up nplan (0.36.3) ...
Setting up networkd-dispatcher (1.7-0ubuntu3.3) ...
Installing new version of config file /etc/default/networkd-dispatcher ...
Setting up gnupg (2.2.4-1ubuntu1.1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for initramfs-tools (0.130ubuntu3.5) ...
[ o.k. ] Installing packages for [ Armbian ]
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package armbian-firmware
[ error ] ERROR in function create_rootfs_cache [ debootstrap-ng.sh:216 ]
[ error ] Installation of Armbian packages failed
[ o.k. ] Process terminated
[ error ] ERROR in function unmount_on_exit [ image-helpers.sh:60 ]
[ error ] debootstrap-ng was interrupted
[ o.k. ] Process terminated

I'm trying to generate a new image. It's only the second image I'm trying to build, so maybe I forgot some cleanup somewhere.

Thanks in advance.

I'm trying to build debian kernel but using mainline 5.4.12 + patches from patch/kernel/sunxi-current. I took non disabled patches and apply patch -p1 for all of them and it fails at patch 0010-general-h6-add-dma-i2c-ir-spi-uart.patch in first hunk because opp node in dts doesn't exists. It's not in mainline not in patches. I have no idea how this works though. Is this patch then skipped or? Thanks.

Marek

I have been using a pre-built Armbian image on a Nanopi M1 Plus and I have been very happy with it.

However I have several modifications specific to my usage of the board (setup some files in /etc/, create default users, install or remove some packages, etc.) that I would like to add to the image in a repeatable way.

By repeatable I mean that I could add the set of scripts/patches/packages etc. to source control so that other people could them rebuild the same exact image.

All of the advice I have found searching the forum points to this process https://docs.armbian.com/Developer-Guide_User-Configurations/

But it does require rebuilding the whole image, including the kernel, which is very cumbersome and totally unnecessary for my use case, as 95% of what is in the stock image is good for me and I don't actually need to compile anything.

So what I am doing right now is to loop mount the image, copy or edit the files that I need changed,  then use qemu to chroot into the image and install the packages I need.

But it does not feel clean and I wonder if there is a better way using Armbian scripts/tools to accomplish something similar.

Any suggestions ?

I see there is a (buster) image available for my Odroid N2 with kernel 5.4.

A few weeks ago I set up the build environment and started building my own images.

First images were build using the 4.9 kernel from Hardkernel.

Later the images were build with kernel 5.1 (and BRANCH=default).

However, the image with kernel 5.4 was not build today but the kernel 5.1 is

still used for the image, although I changed the BRANCH=default (as it was before) to BRANCH=dev.

How can I create a new armbian image with kernel 5.4 ?

I read some posts about a new u-boot. Is this new u-boot required for the

new kernel ?

I would like to boot, e.g. from USB as well.

Kind regards

Norbert

I bought this relatively new WiFi card from sinovoip based on the MT7615. http://forum.banana-pi.org/t/bpi-mt7615-802-11-ac-wifi-4x4-dual-band-pcie-module-mass-production-version/10037
The kernel drivers for this are already in mainline linux (starting from 5.3 I think).  I'm trying to use it on the clearfogpro though, which only runs up to kernel 4.19 right now (tried compiling 5.3 but it fails). So I wanted to backport the driver to 4.19. Unfortunately multiple things changed and trying to get the driver to compile broke lots of other stuff.

So I came around to backports https://backports.wiki.kernel.org/index.php/Main_Page their documentation isn't really great for starters so I am unsure how to use this with Armbian.

Has anyone used backports with armbian build system and might give me some pointers? Or is there a better way to get the driver working? Or has it even been done somewhere and I just don't find it?

Greetings,

count-doku

/m_mcp251x.c:1042:8: error: implicit declaration of function ‘devm_clk_get_optional’ [-Werror=implicit-function-declaration]
  clk = devm_clk_get_optional(&spi->dev, NULL);
        ^~~~~~~~~~~~~~~~~~~~~
 

if i comment this line it passes compile process but when i do insmod i get these kernel debug messages:

[  583.741089] m_mcp251x: loading out-of-tree module taints kernel.
[  583.741626] m_mcp251x: Unknown symbol can_free_echo_skb (err -2)
[  583.741673] m_mcp251x: Unknown symbol can_put_echo_skb (err -2)
[  583.741707] m_mcp251x: Unknown symbol can_get_echo_skb (err -2)
[  583.741800] m_mcp251x: Unknown symbol open_candev (err -2)
[  583.741874] m_mcp251x: Unknown symbol alloc_can_skb (err -2)
[  583.741921] m_mcp251x: Unknown symbol unregister_candev (err -2)
[  583.741963] m_mcp251x: Unknown symbol can_change_mtu (err -2)
[  583.742005] m_mcp251x: Unknown symbol free_candev (err -2)
[  583.742042] m_mcp251x: Unknown symbol alloc_candev_mqs (err -2)
[  583.742105] m_mcp251x: Unknown symbol close_candev (err -2)
[  583.742327] m_mcp251x: Unknown symbol can_bus_off (err -2)
[  583.742409] m_mcp251x: Unknown symbol alloc_can_err_skb (err -2)
[  583.742464] m_mcp251x: Unknown symbol register_candev (err -2)
 

So what i should do to build this module properly?  (Linux cubieboard2 4.19.62-sunxi #5.92 SMP Wed Jul 31 22:07:23 CEST 2019 armv7l GNU/Linux)

    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:

Quote

QA5:A;SVN:B72;POC:17F;STS:0;BOOT:0;INIT:10;BOOT:1;INIT:0;READ:0;CHECK:0;PASS:1;
-----------------------------------------------------------------------
* Welcome to Hardkernel's ODROID-C... (Built at 19:33:00 Dec  8 2014) *
-----------------------------------------------------------------------
CPU : AMLogic S805
MEM : 1024MB (DDR3@792MHz)
BID : HKC1310001
S/N : HKC11122F37E3A5A
0x0000009f
check SD_boot_type:0x1   card_type:0x1
Loading U-boot...success.

U-boot-00000-gb7b8dc2-dirty(odroidc@b7b8dc21) (Nov 25 2019 - 12:16:58)

I2C:   clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[25]=0
clear pinmux reg8[12]=0
clear pinmux reg1[3]=0
clear pinmux reg1[2]=0
set output en 0xc1108054[20]=1
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[25]=0
clear pinmux reg8[12]=0
clear pinmux reg1[3]=0
clear pinmux reg1[2]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[20]=0
set output val 0xc1108058[20]=0
clear pinmux reg1[25]=0
clear pinmux reg8[12]=0
clear pinmux reg1[3]=0
clear pinmux reg1[2]=0
set output en 0xc1108054[20]=1
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=ffdcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=ffdcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=ffdcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=ffdcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=ffdcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=ffdcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=ffdcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=ffdcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=ffdcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=fffcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=ffdcfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[25]=0
clear pinmux reg8[12]=0
clear pinmux reg1[3]=0
clear pinmux reg1[2]=0
out reg=c1108058,value=ffccfa00
set output en 0xc1108054[20]=0
set output val 0xc1108058[20]=0
clear pinmux reg1[24]=0
clear pinmux reg1[1]=0
out reg=c1108058,value=ffecfa00
set output en 0xc1108054[21]=0
set output val 0xc1108058[21]=0
clear pinmux reg1[25]=0
clear pinmux reg8[12]=0
clear pinmux reg1[3]=0
clear pinmux reg1[2]=0
set output en 0xc1108054[20]=1
clear pinmux reg1[25]=0
clear pinmux reg8[12]=0
clear pinmux reg1[3]=0
clear pinmux reg1[2]=0
set output en 0xc1108054[20]=1
clear pinmux reg1[25]=0
clear pinmux reg8[12]=0
clear pinmux reg1[3]=0
clear pinmux reg1[2]=0
set output en 0xc1108054[20]=1
ready
DRAM:  1 GiB
relocation Offset is: 2ff18000
MMC:   SDCARD: 0, eMMC: 1
IR init is done!
*** Warning - bad CRC, using default environment

mmc save env ok
vpu clk_level = 3
set vpu clk: 182150000Hz, readback: 182150000Hz(0x701)
mode = 6  vic = 4
set HDMI vic: 4
mode is: 6
viu chan = 1
config HPLL
config HPLL done
reconfig packet setting done
MMC read: dev # 0, block # 33984, count 12288 ... 12288 blocks read: OK
Error: Bad gzipped data
There is no valid bmp file at the given address
============================================================
Vendor: Man 1b534d Snr 187804ab Rev: 1.0 Prod: 00000
            Type: Removable Hard Disk
            Capacity: 30528.0 MB = 29.8 GB (62521344 x 512)
------------------------------------------------------------
Partition     Start Sector     Num Sectors     Type
    1                 8192         2236416      83
============================================================
Net:   Meson_Ethernet
init suspend firmware done. (ret:0)
Hit Enter key to stop autoboot -- :  0
exit abortboot: 0

** Unable to use mmc 0:1 for fatload **
Loading file "/boot/boot.ini" from mmc device 0:1 xxa1
3929 bytes read
Loading boot.ini from mmc0:1 (ext4)
Executing the script...
setenv rootdev "UUID=b1585a8b-1daf-459d-b17b-59fc562b1608"
setenv rootfstype "ext4"
setenv m "1080p"                # 1080P@60Hz
setenv vout_mode "hdmi"
setenv m_bpp "32"
setenv monitor_onoff "false" # true or false
setenv hpd "0"
setenv cec "0"
setenv disableuhs "disableuhs"
setenv vpu "1"
setenv hdmioutput "1"
if test -e mmc 0:1 boot/.next; then setenv condev "console=ttyAML0,115200n8"; else setenv condev "console=ttyS0,115200n8 console=tty0"; fi
setenv disable_vu7 "false" # false
setenv max_freq "1536"
if test "${hpd}" = "0"; then setenv hdmi_hpd "disablehpd=true"; fi
if test "${cec}" = "1"; then setenv hdmi_cec "hdmitx=cecf"; fi
if test "${disable_vu7}" = "false"; then setenv hid_quirks "usbhid.quirks=0x0eef:0x0005:0x0004"; fi
setenv bootargs "root=${rootdev} rootwait rw ${condev} rootfstype=${rootfstype} loglevel=3 no_console_suspend consoleblank=0 vdaccfg=0xa000 logo=osd1,loaded,0x7900000,720p,full dmfc=3 cvbsmode=576cvbs hdmimode=${m} m_bpp=${m_bpp} vout=${vout_mode} ${disableuhs} ${hdmi_hpd} ${hdmi_cec} ${enabledac} monitor_onoff=${monitor_onoff} max_freq=${max_freq} ${hid_quirks} ${extraargs}"
ext4load mmc 0:1 0x21000000 /boot/uImage || fatload mmc 0:1 0x21000000 uImage || ext4load mmc 0:1 0x21000000 uImage
Loading file "/boot/uImage" from mmc device 0:1 xxa1
** File not found /boot/uImage

** Unable to use mmc 0:1 for fatload **
Loading file "uImage" from mmc device 0:1 xxa1
** File not found uImage
ext4load mmc 0:1 0x22000000 /boot/uInitrd || fatload mmc 0:1 0x22000000 uInitrd || ext4load mmc 0:1 0x22000000 uInitrd
Loading file "/boot/uInitrd" from mmc device 0:1 xxa1
8811479 bytes read
ext4load mmc 0:1 0x21800000 /boot/dtb/meson8b_odroidc.dtb || fatload mmc 0:1 0x21800000 dtb/meson8b_odroidc.dtb || ext4load mmc 0:1 0x21800000 dtb/meson8b_odroidc.dtb
Loading file "/boot/dtb/meson8b_odroidc.dtb" from mmc device 0:1 xxa1
** File not found /boot/dtb/meson8b_odroidc.dtb

** Unable to use mmc 0:1 for fatload **
Loading file "dtb/meson8b_odroidc.dtb" from mmc device 0:1 xxa1
** File not found dtb/meson8b_odroidc.dtb
ext4load mmc 0:1 0x21800000 /boot/dtb/meson8b-odroidc1.dtb
Loading file "/boot/dtb/meson8b-odroidc1.dtb" from mmc device 0:1 xxa1
17254 bytes read
fdt addr 21800000
if test "${vpu}" = "0"; then fdt rm /mesonstream; fdt rm /vdec; fdt rm /ppmgr; fi
if test "${hdmioutput}" = "0"; then fdt rm /mesonfb; fi
bootm 0x21000000 0x22000000 0x21800000
Wrong Image Format for bootm command
ERROR: can't get kernel image!
▒
Unknown command '▒' - try 'help'
MMC read: dev # 0, block # 1216, count 16384 ... 16384 blocks read: OK
MMC read: dev # 0, block # 1088, count 128 ... 128 blocks read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
odroidc#

Does anyone have an idea on what is the problem and how to fix it?

Thanks in advance

*Ciao

Piero

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?

help me , how to do

spender-ssd1322.patch

vagrant@ubuntu-bionic:/vagrant$ sudo ./compile.sh 

[ o.k. ] Using config file [ /vagrant/userpatches/config-example.conf ]

[ o.k. ] Preparing [ host ]

[ o.k. ] Build host OS release [ bionic ]

[ o.k. ] Syncing clock [ host ]

[ 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:995 ]                                                                                   

[ error ] verification failed 

[ o.k. ] Process terminated 

Quote

New naming convention is getting to its final stage of development. Beside name I also RFC packaging patch which had hard coded dev/next values inside so it was a must to deal with.

 

Since we have new package naming and we will need to create some upgrade automatism in any case ... shell we change to more logical/proper versioning too? We had debate over but can't find it. Was it on Github? @lanefu New thread for that?

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.

 

But when I chose the board 'Tinkerboard' from the Armbian building script CUI menu, the output ko files were all built for 4.4.

How can I create 4.19 ko files for Tinkerboard?

I tried to put userpatches/lib.config in order to overwrite KERNELBRANCH with tag:v4.19.y but not luck.

The error was shown below:

[ o.k. ] Using config file [ /vagrant/userpatches/config-example.conf ]
[ o.k. ] Preparing [ host ]
[ o.k. ] Build host OS release [ bionic ]
[ o.k. ] Syncing clock [ host ]
[ o.k. ] Checking for external GCC compilers 

(snip)

grep: Makefile: No such file or directory
sed: can't read Makefile: No such file or directory
grep: /home/ubuntu/armbian/cache/sources/linux-rockchip/v4.19.y/Makefile: No such file or directory
grep: /home/ubuntu/armbian/cache/sources/linux-rockchip/v4.19.y/Makefile: No such file or directory
grep: /home/ubuntu/armbian/cache/sources/linux-rockchip/v4.19.y/Makefile: No such file or directory
grep: /home/ubuntu/armbian/cache/sources/linux-rockchip/v4.19.y/Makefile: No such file or directory
[ .... ] Compressing sources for the linux-source package 
 570KiB [ 264MiB/s] [======================================================================================>                          ] 77%
cp: cannot stat 'COPYING': No such file or directory
[ o.k. ] Compiling default kernel [ 0 ]
[ o.k. ] Compiler version [ arm-linux-gnueabihf-gcc 7.4.1 ]
[ o.k. ] Using kernel config file [ config/kernel/linux-rockchip-default.config ]
make: *** No rule to make target 'oldconfig'.  Stop.
make: *** No rule to make target 'menuconfig'.  Stop.
[ o.k. ] Exporting new kernel config [ /home/ubuntu/armbian/output/config/linux-rockchip-default.config ]
[ error ] ERROR in function compile_kernel [ compilation.sh:382 ]
[ error ] Kernel was not built [ @host ]
[ o.k. ] Process terminated 

Any suggestions/helps are appreciated.

Thanks.

The board will start and I can SSH in and reach the BusyBox prompt. So far so good but from what I've gathered I should enter the command "unlock" there to display the cryptroot password prompt. However it only results in the message -sh: unlock: not found. I read somewhere else the command might be "cryptroot-unlock" but that instead gives nothing, not even the error message.

Furthermore, regardless whether I enter any commands, around 10 seconds into the SSH session it will freeze and I eventually get kicked off with a broken pipe error. I suspect the board is restarting by itself but it is difficult to verify because it is running headless. After a few seconds I'm able to SSH in again for another ~10 sec session.

Building it without cryptroot works just fine and the board starts normally and I can SSH in. I have not tested building it with cryptroot only (without the SSH-unlock ability), because again it is difficult to verify due to the headless setup.

Has anyone run into these kind of behavior when building Armbian images with cryptroot setup or have any idea what's gone wrong? Is it a bug in the build cryptroot feature?

Below is my config-default.conf

KERNEL_ONLY="no"
KERNEL_CONFIGURE="no"
CLEAN_LEVEL="make,debs,oldcache"

DEST_LANG="en_US.UTF-8"

EXTERNAL_NEW="prebuilt"
INSTALL_HEADERS="yes"
LIB_TAG="master"
USE_TORRENT="yes"
CARD_DEVICE="/dev/sdb"

BOARD="renegade"
RELEASE="buster"
BUILD_MINIMAL="yes"

CRYPTROOT_ENABLE="yes"
CRYPTROOT_PASSPHRASE="password"
CRYPTROOT_SSH_UNLOCK="yes"
CRYPTROOT_SSH_UNLOCK_PORT="2222"

1. This piece

    if [[ $(lsb_release -sc) =~ bionic|buster|cosmic|disco ]]; then
        mkopts[ext4]='-q -m 2 -O ^64bit,^metadata_csum'
    elif [[ $(lsb_release -sc) == xenial ]]; then
        mkopts[ext4]='-q -m 2'
    fi

Why disable metadata_csum?

Why disable 64bit overall, not just for pure 32 bit boards?

Edit on Mar 9 2020

Metadata checksums is a new feature of ext4 since e2fsprogs 1.44 (xenial has 1.42). It makes the fs more robust to data corruption but it requires some extra cpu power to calculate the checksums. It is not a problem for generic cpus with SSE4.2 (= hardware accelerated crc32):  intel since core gen1, amd since bulldozer.

Arm world is not that simple. So we just disable the checksums in distros which have them on by default in /etc/mke2fs.conf to reduce cpu usage.

The 64bit option is only required for the checksums (since armbian is not something for use with really huge storages) hence we disable it as well.

2. This piece 

[[ $ROOTFS_TYPE == ext4 ]] && tune2fs -o journal_data_writeback $rootdevice > /dev/null

Why enable journal_data_writeback feature? What are the pros and cons?

Edit on Mar 9 2020

"Data mode" section in https://www.kernel.org/doc/Documentation/filesystems/ext4.txt

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

The problem is, that nothing is done with it, so i ran into building errors because of to little disksize inside vagrant.

I managed to cincumvent this by adding

     config.disksize.size = '50GB'

into the Vagrantfile , just the line before the line

> END

Question: I am not sure if this is way to much. My HDD runs out of space pretty fast, so it would be nice to get some proper suggestions for this value.

2.

https://docs.armbian.com/Developer-Guide_Using-Vagrant/#armbian-directory-structure  says:

> When you read the Vagrantfile you’ll see that Vagrant will mount local output and userpatches directories.

This is untrue ! There is nothing like this in the Vagrantfile by just following the above steps.

3.

https://docs.armbian.com/Developer-Guide_Using-Vagrant/#creating-the-vagrant-guest-box-used-to-build says:

> # We have to be in the same directory as the Vagrant file.

> cd build

>

> # And now we simply let vagrant create our box and bring it up.

> vagrant up

This does not work. I had to put an

> vagrant init ubuntu/bionic64

in between this two lines to work properly. The Vagrantfile can't be in the "build"-folder following the docuemtation.

4.

https://docs.armbian.com/Developer-Guide_Using-Vagrant/#vagrant-guest-steps says:

> # Let's get building!

> cd armbian

> sudo ./compile.sh

Unfortunately there is not "armbian"-folder.

I could do an

$ cd /vagrant

 sudo ./compile.sh

to get into the host based "build"-folder.

But i wasn't sure if that was what was intended, so i ended up  doing a fresh "git clone" of the armbian build system and just

copying the "output/images" folder to "/vagrant" to get the desired files back to the host.

Question: I am not sure what was suggested to do here?

Question: Is the documentation kinda out of date , or is just the line

> vagrant box add ubuntu/bionic64

from

https://docs.armbian.com/Developer-Guide_Using-Vagrant/#virtualbox-version

pointing to the wrong box ? What just ended up in all this trouble ?

Greetings

Michael