Werner

Recently we announced that we are going to drop support for bulk of boards to secure better quality for those that will remain. But which will remain? Those who will have at least one dedicated maintainer - anyone can become one. 

Check new "Armbian standard" support policy:
 
Armbian team took over what was possible while the remaining boards, which won't get a maintainer by December 1st, will loose support status and will be removed from the download pages.
https://github.com/armbian/build/pull/3148

Apply and help
 
Apply for maintainership by contacting @yang or @Werner

Even though Ansible is not going to cut it we are open for suggestions in any case
 

Origin:
https://forum.armbian.com/topic/16933-armbian-config-rfc-ideas/?do=findComment&comment=119703
https://armbian.atlassian.net/browse/AR-638
 
Description:
 
Our code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-config tool shall be refactored or as a modular framework rewritten from scratch.
We are looking for both experienced bash scriptwriters as well as somebody who takes a overall look at task execution.
 
 
Destination:
https://github.com/armbian/config
 
Skills required:
Bash
 
 

IIRC Bullseye has been promoted to stable already. Strange...

Perhaps increase boot verbosity like suggested in the documentation.
https://docs.armbian.com/User-Guide_Fine-Tuning/#how-to-toggle-verbose-boot

Release Candidate Code Freeze Date: TBD
Release Planning Meeting Date: 2021-10-16 1400GMT
Release Date: TDB
Release Candidate Branch Link: TBD 
Release Changelog: TBD
Release Coordinator: @igor
 
We are in doubts to make this release at all due to overall project strengthening and focus on securing maintainers and cut HW which doesn't have it. Alternative idea is to produce a release as is with minimal changes and focus on bug fixing straight from today.

Meeting is this Saturday, to get on common grounds.
 
@Igor@Werner @TonyMac32 @martinayotte@piter75 @ning@Myy@balbes150 @sfx2000 @ebin-dev@chwe@gprovost@aprayoga@5kft@JMCC@going@jeanrhum@dolphs @jock@belfastraven@TRS-80@Bozza@Rich Neese@sgjava@Mangix@tony013

Offhand, probably not a great idea to mix and match Debian and Ubuntu repositories. You may want to reinstall with the Debian derived Armbian before continuing. There's a very good chance you'll end up with library versioning issues, unless you know what you're doing.
 
That said, it looks like you put "stable/updates" instead of "stable-updates" in your /etc/apt/sources.list ...
 

Considering this a TVbox might not the best choice for you since there would be lots of frustration.
If you want an ARM board with well supported SoC I'd recommend something with RK3399 onboard. Yeah it is slightly older and there is a new generation of Rockchips now but remember that development for ARM is still rather slow and it takes several years to get a chip almost fully functional.
The Station P1 (which in a nutshell is a T-Firefly RK3399 ROC-PC PLUS board in a fancy case) is working quite well in the meantime and @balbes150 is actively supporting it. Yes, it is also a bit more expensive but you get is what you pay for.
Having Debian on it you can use it as PC and installing Kodi will give you TVbox "feeling".

yes
 
the driver is responsible for this, it has nothing to do with the support of specific hardware.
I didn't check, but I saw that to add the desired screen resolution, you can add it at the user settings level.
try adding a parameter to extlinux.conf with your screen resolution
 
drm.edid_firmware=edid/1920x1200.bin

New version 20211007-edge with 5.14.9 core. All equipment works, including analog sound and remote control.
 
@JMCC
I checked the operation of your KODI-18 packages on this kernel, KODI starts, but there is still an error and the video does not play, maybe I forgot some kernel options or a patch. I plan to check it again in the near future.

As stated above, you can install the packages from this link: https://users.armbian.com/jmcc/packages/kodi-mainline/arm64/
 
I am planning to build Kodi 19 packages and integrate them into the Armbian repos, but no ETA yet.

Hello @Heisath! This is known problem. QCA98xx wifi chips are buggy, have timing and detection issues related to PCIe, which Qualcomm confirmed. Qualcomm recommendation is to increase PCIe pulse detection and for some (x86) motherboards, vendors released a new BIOS which do it. To make it worse, Marvell A38x SoC has also buggy PCIe which cause other issues and therefore combination of QCA98xx and A38x cause even more issues.
 
I'm preparing patches for pci-mvebu.c kernel driver to fix some issues, but they are not ready yet.
 
For QCA98xx I have prepared patch which are currently on linux-pci mailing list: https://lore.kernel.org/linux-pci/20210505163357.16012-1-pali@kernel.org/
 
Could you test it and check if it helps with new kernel versions?

tl;dr: irc://irc.libera.chat/armbian
 
 
 
Feel free to join us:
Server: irc.libera.chat Ports: 6697 / non-SSL: 6667 Channels: #armbian, #armbian-commits, #armbian-rss  
There are even more channels available. Information about those and our services can be found in our documentation: https://docs.armbian.com/Community_IRC/
 
Registration with Nickserv is mandatory to join primary #armbian channel.
 
Don't hesitate to get in touch with us
 
 
 

I had the board before I met armbian XD although I was not disappointed, I do several things:
- Edit documents with WPS Office(better looking than LibreOffice)
- Listen to YouTube music with FreeTube (configured for audio only)
- Browse with Firefox but only non-demanding pages (no YouTube XD)
- I have arduino-IDE installed although I have not yet tried to program a board (Chinese version-Aliexpress)
When someone understands the limitations of the board or the software being used then they can enjoy it  , that's my opinion as "average Joe" who knows next to nothing about Linux XD.
[I thank balbes150, translated with google translator]

It probably would too but I forgot that it has one built in

CSC stands for community supported configuration which means somebody took time to make Armbian work on specific device. However the device may not have an active maintainer that takes care of future kernel versions and supporting so it could break any time with upgrading since Armbian often does not even have a sample of the device in the lab to make basic functional tests. Also if something breaks and nobody is around that knows the device and how to fix it it stays broken. Armbian developers may/can/will not help.

I haven't noticed any eth related problems on 5.13.y and RK3399, but when moving to 5.14.y I also found that eth no longer worked. I corrected the issue by reverting the following commit: https://github.com/torvalds/linux/commit/2d26f6e39afb88d32b8f39e76a51b542c3c51674
 
I understand its not a true fix. This was tested on the NanoPC-T4.
 
--- a/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c 2021-09-12 03:01:00.000000000 -0400 +++ b/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c 2021-09-14 07:19:24.402736613 -0400 @@ -21,6 +21,7 @@ #include <linux/delay.h> #include <linux/mfd/syscon.h> #include <linux/regmap.h> +#include <linux/pm_runtime.h> #include "stmmac_platform.h" @@ -1528,6 +1529,9 @@ return ret; } + pm_runtime_enable(dev); + pm_runtime_get_sync(dev); + if (bsp_priv->integrated_phy) rk_gmac_integrated_phy_powerup(bsp_priv); @@ -1536,9 +1540,14 @@ static void rk_gmac_powerdown(struct rk_priv_data *gmac) { + struct device *dev = &gmac->pdev->dev; + if (gmac->integrated_phy) rk_gmac_integrated_phy_powerdown(gmac); + pm_runtime_put_sync(dev); + pm_runtime_disable(dev); + phy_power_on(gmac, false); gmac_clk_enable(gmac, false); }  

Thankfully there is the -U fallback option

I usually do the noob way finding the trigger files for LEDs
code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } du -a /sys | grep led | grep trigger
 
I don't know what trigger is needed for mmc but heartbeat is self-explaining. code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } echo heartbeat > trigger
 
 

New version of images 20210915-edge with 5.15.0-rc1 kernel.
Please note, this version does not have an HDMI output, control is performed via SSH or UART. The wired network works, both LAN1 and LAN2 interfaces work on P2, M2 - LAN1.
Please note that this is the primary test version and unpredictable behaviors are possible.

The size requirements have been updated.
 
Since we now share images with various desktop environments as well the size of all torrents have now grown to around 500GB.
To become future-proof again the free space requirement has been raised to 1TB.
 
For those who did not notice yet. It became rather simple to become an Armbian http/s mirror as well if you do not like torrent stuff: https://github.com/armbian/mirror

LIB_TAG has nothing to do with kernel branches. You should always build from master unless you know what you do or being told otherwise.
I suggest to start over with a clean workspace since I yesterday successfully built an OPi02 bullseye legacy image without issues.

Done.

Unfortunately userspace upgrades like Bionic to Focal or Stretch to Buster have never been officially supported by Armbian due to lack of resources for proper testing. It probably works if you freeze your firmware packages and follow official Ubuntu/Debian guide how to upgrade but if something goes wrong you won't receive help from Armbian.