Werner

For those who have missed it the forums offering various ways to display the contents, mentioning here especially the grid view:
 

 
 
To get there simply select it by clicking on the middle button right next to the big red Start new topic:
If you don't see pictures make sure you selected our default forums theme.
 

 
 
 
As you will notice we partially have stock images only and some are even still missing. We would really love to see some nice and shiny artwork there as we might put the grid view as new default setting (no worries, the classic look'n'feel will be still availabe ).
So if you have some graphics designer skills but have no idea about programming you can still contribute to the project by donating a small amount of your time and create some awesome forum images.
 
Looking forward to your ideas

@dhewg: There are more variants of A3720 SOC and they differs in CPU freq. Variant number is printed on SOC. So if you have SOC with 1GHz CPU you should use/flash 1GHz firmware image, if you have only SOC with 800MHz CPU then you should flash 800MHz image. In part order number documents is also 1.2GHz variant of SOC but I have not see it yet. No idea if Marvell started producing it.
 
In this public document https://www.marvell.com/content/dam/marvell/en/public-collateral/embedded-processors/marvell-embedded-processors-armada-37xx-hardware-specifications-2019-09.pdf at page 154 is decoder of numbers printed on SOC and on page 153 is decoder of numbers, important is speed code. Based on SOC chip which you have on your Espressobin you should prepare firmware (WTM+ATF+U-Boot) and flash it.
 
So this if somebody flashed incorrect variant then it is probably reason for instability of Espressobin.

The BPi M5 is just an ODROID C4 clone (check also the serial console output in the wall of text above) so simply look there. They even took the same VL817 hub (a way better choice than the Genesis Logic thingy on the N2+) but of course decided to change the power circuitry so that their users suffer from the usual Banana undervoltage drama (unlike the C4 which is up to the task powering a number of USB3 consumers with stable 5V unlike the M5 here).

I've changed it to 1008000 yesterday, so far all good (though obviously a bit slower):
pedro@nanopim4v2:~$ cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=1008000 MAX_SPEED=1008000 GOVERNOR=userspace  

Invision Community version has been bumped to 4.5.3
Everything is still pretty rough, both at the frontend as well as the backend. Might probably take a few days until everything is in good shape.
The good news is that for the most part the forums are usable

In this tutorial we build a custom .config for OrangePiOnePlus board,
eg: to remove blutooth, WiFi and or USB3.x support since the hardware is not onboard, alternatively you can adjust settings to your needs which is not in the default .config.
 
The section mentions, if file " userpatches/linux-$KERNELFAMILY-$KERNELBRANCH.config " exists, it will be used instead of default one from " config ".
This means for the OPiOnePlus :  " linux-sunxi64-dev.config " should be created,  but please note "dev" is just one of the three options available, which are:  " current ",  " legacy " and  " dev "
The default config files are located in : " /armbian/config/kernel " and thus also holds a "linux-sunxi64-dev.config " config file.
 
#
#If user-provided kernel .config file IS NOT present yet
#
cd ~ git clone --depth 1 https://github.com/armbian/build armbian cd armbian ./compile.sh BRANCH=dev RELEASE=buster BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=yes EXTRAWIFI=no BOARD=orangepioneplus  

Yet rename ".config" and Save to " ~/userpatches/linux-sunxi64-dev.config " , find attached a screenshot
 
 

#
#If user-provided kernel .config file IS present
#
<script> cp -p ~/armbian/userpatches/linux-sunxi64-dev.config ~/ sudo rm -rf armbian git clone --depth 1 https://github.com/armbian/build armbian mkdir ~/armbian/userpatches cp -p ~/linux-sunxi64-dev.config ~/armbian/userpatches/ </script>  
Above can be scripted so you do not need to worry if for some reason you need to remove and rebuild your " armbian " directory from scratch
 
 
Rest would be ( assuming your kernel has been customised to your needs ):
 
cd armbian ./compile.sh BRANCH=dev RELEASE=buster BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no EXTRAWIFI=no BOARD=orangepioneplus  
 
 
Hope this addition to user-provided-kernel-config explains the idea " in depth " .
Happy configuring :-)
 
 

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

I2C standard clock are usually 100KHz or 400KHz, but you can try other values.
Here is the doc, the parameter is "clock-frequency" :
https://www.kernel.org/doc/Documentation/devicetree/bindings/i2c/i2c-designware.txt

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

Dedicated to ARM..yeah, why not?

You can check here: https://forum.armbian.com/clubs/
But it will most likely be deleted again. It was just a random idea by myself and did not expect to get any proponent for it anyways.

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

@Pali praise the LORD Jesus Christ! Got it working! 
 
Here are the specs:
 
espressobin v7
Armbian running Ubuntu Focal 20.04
Linux kernel v5.8.6
Use the latest Flash image for ddr4 1GB 800_800 
 
AR9380 chipset is recognized and stable. Thank you!!!!

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

(A not so serious attempt to) add club for Android fanboys

Drivers are in the kernel, I assume you mean the matching firmware?

I feel left out but it’s 2:30am and the fanciest action in my kitchen is a Molotov cocktail 
 

challenge accepted
 
Todays special:
 
Schweinshaxe mit Knöpfli
Knöpfli is Switzerlands pendant to 'Spätzle'.  Schweinshaxe (Ham hock), and for those not knowing them:
 here we go..
 
user: ~$ time meal.sh real ~2h30min user ~40min sys ~2h First we start with the Haxe. We rost them of both sides for around 2-3mins in a metal bowl on the hotplate.

First on the side where the bones are smaller, then on the other side. We add 2 roughly cutted onions and carrots and let them rost for around 5mins before adding a glass of vine.

We let the vine now reduce a little bit before adding bouillon (as much as needed so that they are not completely covered). They're no cooked for around 1h30mins at 150°C and the last 30mins at 200°C in the oven (use the liquid to 'moisten' them every 15min). 
Knöpfli:
We mix 500g flour with 300mL milk (or 150 milk 150 water), 3 eggs a bit of salt (one teaspoon) and if you like a bit of nutmeg. As soon as it is well mixed we let it rest for 30mins.
 
A big pan is filled with water and heated up until it boils. The knöpfli dough is then pressed through a 'perforated sieve' (there are special ones for 'Knöpfli' but mine comes from a steam cooking set and works also well ).

as soon as they swimm (normally immediately), they can be skimmed wit a normal sieve and collected. If you want you can roast them now in butter and add some roasted onions on top but it also works well without, or as I do add cheese on top. Similar you can add some honey on top of the 'haxen' for the last 5-10minutes for a nice crust (I guess the germans adding Soda in the end for the crust, maybe the Bavarians here knowing it? ).  
In the end, it should look somehow like that:

 
Things you need (for ~4 persons):
2 onions 2 carrots 4 haxen 500g flour 3 eggs 300mL milk a glass vine, a bit of bouillon, salt, oil (butter)  

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

Perhaps this fits here:

ver 20200925 kernel 5.9.0-rc6

The one saying this is the dumbest person on earth. If he is lazy then I'm santa
 
 
Indeed, since our Russian isn't good enough. 

I need to correct my last statement, as the post I was referring to was not deleted: "is to lazy to help any of us with the same problem ".  But I will still say that balbes150 is offended by language like this.
 
Everyone needs to realize that Armbian on Android TV boxes (especially balbes150's builds) are not supported by the Armbian project.  And particularly the s905x3 cpu isn't supported by even balbes150.  Posting in these forums demands for support or calling others lazy for not providing support isn't in the spirit of the armbian community.  We all wish there was better support of mainline linux on all of these boxes, but without active support by the device manufacturers that isn't a reality.  The volunteers here do the best they can (and they do some amazing things when you think about it).

@Igor suggested to put this on jira since there is a related topic, so please study there : https://armbian.atlassian.net/browse/AR-230?focusedCommentId=10278
@balbes150

The simplest thing is to try to take a working u-boot from any working Armbian image (for details on how to pull out u-boot and use it in another image, see this topic earlier).
 
 
Starting from USB is possible, but with the described two options. I think the TWRP startup comes from u-boot which is in eMMC (in service mode).
To completely clean eMMC, you can use the USB Burn Tool (with certain options, the firmware file is not needed).
This is cheating. H6 can't work with 4 GB , this is a hardware limitation. See the topic in the section Allwinner H6, where the developers describe this problem.