Igor

Problem you have is not possible to reproduce by using latest source from main branch. Which is the only source that can be maintained. If you are using different sources that the main in main branch, you need to adjust them accordingly. Build framework needs clear instructions and code that builds. IMO its less work supporting our common goal - get this working with latest version.

Installation is not the strongest part yet as we are developing / extending our own installer. Installation is possible but its easy to hit into problems: https://armbian.atlassian.net/browse/AR-1592 (probably others yet to be found) Thank you for trying and encouragements!

It is temporally issue that is present in Rockchip kernel for at least 6 months. And its not the only one. With modern kernel, headers works OOB, which proves bug is in the (Rockchip) vendor code. I already spent a week trying to fix this problem for everyone but I can't afford to touch this problem anytime soon. If there are no records of fixing this problem in the logs, update mentioned in the leaflet, won't fix this problem.

Thank you. It was never Debian but Armbian (with Debian user space packages) since the day 1 but at some point we had to stop maintaining hw interface / kernel, also Kobol went out of business. When this happens, things starts to fall apart and if you would take our work more serious, you could have this hardware well supported.

You mean Linux kernel related troubles? Documents about progress and problems is scattered around many forums and mailing lists. We are focusing to troubles related to hardware we cover, but there are also general problems we all face. If you have a lot of time, if you are dealing with this daily, you can get a better picture about, but it will be far from complete. I only told you how I see it. If you are talking about build framework documentation, than yes, its not in a good shape. We have reworked framework completely and made a switch several months ago. We had to, even documentation was not completed yet. Person who had to deal with this couldn't afford to continue working on that, while I can't hire a person as users want everything for free. Recently I have started to engage with another person, to put documentation together, but he needs weeks / months to get familiar ... Build framework supports it, but we don't use DOS partition to store DTB files and yes, enabling UART is just editing it and enabling within. Or by make + loading overlays that contains that change. I understand users frustration. This is not a professional support service and there are 1000 x more people that asks questions than those that can answer. This ratio hasn't been changed in past 10 years and it won't. Its a complex world, a lot of time has to be wasted to answer and users (including experts like you) don't care about perspective from the side you are addressing to. Reality looks this way: to answer you, I had to tell my wife and my kids to shut off as I have to focus to answer to someone that is stealing our family budget, to answer everyone that needs help, I can waste all my wake hours every day ... and you are pissed off? Nobody here is responsible for troubles end users have - this is the base of our contract. If 3 days response for hardware that is specifically marked as "not supported" on the project that only provides best effort support via forums is too much, we provide commercial support - which is just one way to respond on violence from people that think we are responsible for the misery and we have to solve their problems. No, we are not. We are in this sh* together. Just we spent 24/7 to work on problem, we pay for most of costs and for most of you this is a hobby. Neither me and many people around here. Scene is also changing. Market is overloaded with cheap hardware that is becoming more and more complicated ... while back in 90" it was a huge privilege and thrill having a root access to some big bad-ass Unix machine. We don't have time for holy wars here, Debian vs Ubuntu vs Arch vs FreeBSD vs ... That part is so not important for the problems we deal with.

IIRC, kernel headers on this (proprietary / private) kernel are anyway broken.

That is correct. Many people already tried to fix this, I also spent few days but more I can't ... but I got information that someone else succeeded and its "just" integration and testing. But there are more problems to be resolved before cheapest WiFi on one board. Perhaps in 23.08, but in free software we can't give promises.

It seems kernel 6.1.y is broken in several places. Use more adult kernel 5.15.y (legacy). We are very close to this scene and are running into many many problems. Also I am desperately trying to improve and enlarge Allwinner section (with no budget and very little help from users side) to fight those already known problems. Elsewhere is just more dust, so I am not sure if you have much luxury of choosing different hardware interfaces. Updating is expensive and hard to do for mainly amateur projects. We would need at least one full time person to keep our documentation on the level you would be satisfied. Depends where this documentation will end. If we limit only on our tools, then this we might be able to polish it on satisfactory level in about a year. Likewise. 🍻 Welcome to Armbian. Please keep in mind that most people that develop and maintain software for you with their private resources don't like to feel any pressure. Don't bump topics. Leave manual configuration. Use armbian-config, system -> hardware ... It should work, but perhaps not with latest kernel / image.

Did you try legacy kernel (5.15.y). With 6.1.y many things are wrong ...

IMO its best to remove this half working Tow-Boot and use boot loader shipped with Armbian. From the chat:

Rescued ... there is something wrong with bootloader on SPI flash. Instructions were updated. You also need to erase SPI flash, then proceed standard Armbian way. Flash to SD media, boot from it, then install to eMMC. We will look deeper once possible: https://armbian.atlassian.net/browse/AR-1787

There is indeed something wrong but I managed to brick my board ...

We have tested VIM3. Are you sure you are downloading correct VIM3? https://www.armbian.com/khadas-vim3/ or https://www.armbian.com/khadas-vim3l/

Please provide link to the exact image. We will check shortly.

I am glad you have asked. We do a lot of testings, but the task is gigantic and not many people understand the sacrifice that is needed: A few people can't test 1000+ different features of a Linux system and especially not on different hardware platform. Here we have unique problem, a lot bigger then any other Linux distribution. Which usually just distribute this (our) work. Since our resources are super limited and most of users help is in reporting and complaining problems (mainly useless doubled information), we have to focus to test basic features only. Which are basic you can see in that testing topic. Automated test system - we are looking for help for years (hiring is not possible) - people that have experiences with this to help us setup automated test infrastructure. Which is the only answer to your questions. Still, when things are tested, our team and budget is way too small to address issues that are found. This is something most of end user are unable to understand. Small testing is happening daily, while this larger testing is happening at each release, 4 x per year, and it costs us weeks of our private(!) time. Time is money and in several decades, your donations will match the time that is lost in one such event. To give you perspective of your question and an some of the "why" answer. As we understand not all images will work and we care about you and your precious time, we provide you several viable workarounds! Older images can be downloaded for years back (https://archive.armbian.com/), you can try to build from sources. It is very much possible that bug has nothing to do with our code. As this is open source, anyone can dig in and if you will fix the bug, you will help everyone, Linux community, not us specifically as other distributions are also using Armbian as a base. Armbian is far from perfect, but gift community receives is IMHO beyond reward that is given to developers that provides you this. Even when you have problem with. We listen to you, but we can't help in real time or before you notice as team is too small. Fixing issues can take a week, a year, perhaps bug will never be resolved, perhaps it already is. People that are fighting thousands of issues found in open source software are scarce resource you should only thanks. We are in this sh* together. https://docs.armbian.com/#what-is-armbian This is Linux / open source. Look into logs, ask on forums (you did), ... good luck in resolving a problem you have with open source software. We help best way possible and advise you to start this way https://www.armbian.com/bugs/

Likewise. You don't drive us, our development.

It was fixed right away by adding a text "1GB version is not supported" as there are no plans to fix this anytime soon. Why? You don't need our help. If not here https://docs.armbian.com/Release_Changelog/ or https://www.google.com/ then https://calendly.com/armbian/consultation Why proprietary kernel images works? https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one Here you can add your share for R&D and for the damages your questions generate.

FYI. Bullseye does not add or remove anything related to hardware on Armbian Linux. If you build Bullseye / Jammy / Focal / whatever image today with our build tools https://github.com/armbian/build your WiFi will also work.

We set maintainership conditions pretty low - he/she doesn't need to fix any low level troubles, keeping a list of them is already a great value or taking such burden away. As I am not paying attention to this hardware (to remain sane) I didn't notice there were no images at all, while we usually provide images for community/no supported targets too. Images would be up, but one bug prevent them from building correctly - you can build then on your own, but they fail to build in automation.

WIP is this device, while you are mainly asking for things that are unrelated to the device. Yes, we would like to hear from you, but try to understand your & project limits. General ideas goes to forum https://forum.armbian.com/forum/38-feature-requests/ but since project does not have 100-1000 full time employees or any coverage for their food, it will unlikely that ideas will be processed. This is open project - when you see a problem, you are welcome to fix it. This is how things works. Make sure to be around when we need you to help yourself. This information is in the FAQ, but anyway this changes a little as Debian Bullseye is not the same as Armbian Bullseye. Its based on, userland packages are used from respective upstream variants, while critical hardware components are always ours. The way images are assembled too. Just packages versions and updates are related / connected. If we spent 2 months to bring up video acceleration within Ubuntu packages base, we won't even try to do the same for Debian package base, because you are some die hard Debian user. Your request will be denied on the spot. The same would go if support would be initiated on Debian first. When it comes to hardware acceleration question is usually about severe changes that needs to be applied to base OS. Its nothing about Debian or Ubuntu anymore ... We would like to avoid fights of what should be present on the images and what not, so we tend to provide as minimal as possible. Nobody can't say - why this and that comes preinstalled ... We want to cover this with armbian-config / some installer, that would install this in no time. With armbian-config it is possible to cover any kind of installation, even build from sources, To have own pre-configured perfect system with latest packages and upgrades one can deploy to various of devices regardless of resources and architecture? Our project fits somewhere between embedded and amateur user Linux, those that comes with distro branded Debian or Calamares installer. Where setup is tailored for average Joe which can select several things in the install process. Here, you download Live system which you flash and use. You can install it to internal memory, but this is more or less transferring unchanged root file-system to different media. Many of build framework users are using Armbian as a base for their images. That comes with one application - which is pretty much default case in embedded Linux. And then you have people in the segment of Gentoo, LFS and similar that just need to build from sources. There are different type of end users ...

Developers asks users for testing when something needs to be tested. Not the other way around. One of the difference between people that are selling hardware (with promise of support) and us is that we will be straight with you. Support that is provided to this hardware is amateur and best effort. Vendor support is usually a lot worse than ours, but they / we all are trying to do what is possible. Hardware that has Armbian platinum support badge (vendors covers a little bit) has better support, there is a person behind, here is not (report = /dev/null), we don't have hardware nor any budget, images are provided "for testing" until they are one day removed. Even when customer (you) pays for R&D, which is not the case, they/you don't decide development/support priorities. End users should never harass developers directly. You open a (Jira) ticket, supply all info you can and wait. A day, month, year, never ... This is how development usually works in open source where developers pays for software you use. If you need support certainty, like it sounds, then this is understood as a professional service, you pay (or in some other form) first, then you become treated as a customer. It is still possible that problem is not getting resolved, but we will not be blowing 100% of our family budget to work for you, our competitors and vendors. If you buy hardware on Aliexpress and download software that is free for download, you didn't become a customer. Just FYI to straighten things up. Things are changing https://docs.armbian.com/User-Guide_FAQ/ Otherwise, welcome to the club Many people behind Armbian comes with lifetime Linux/Unix/IT experience. I hope we as a Project don't look too old school 😂 They always promise ... Reporting a solution is valuable, but integration and testing requires serious resources. Radxa is fighting this with one full time person, we have to skip like 80% of hints and solutions that are reported to this forum with a group of people that is able to do a lot more then a single person ... to give you some perspective. Welcome to open a pull request https://github.com/armbian/build/pulls Welcome to help fighting problems.

Looking into the script and debugging it? armbian-config just calls this: https://github.com/armbian/build/blob/main/packages/bsp/common/usr/sbin/armbian-install There are known bugs https://armbian.atlassian.net/browse/AR-1592 and ongoing tasks https://armbian.atlassian.net/browse/AR-1001 that might be related to the problem you are facing.

@jaffac Works for me, logs: https://paste.armbian.com/feyuxegepo _ ___ _ __ _____ __ __ _____ _ | |/ / |__ __ _ __| | __ _ ___ \ \ / /_ _| \/ |___ /| | | ' /| '_ \ / _` |/ _` |/ _` / __| \ \ / / | || |\/| | |_ \| | | . \| | | | (_| | (_| | (_| \__ \ \ V / | || | | |___) | |___ |_|\_\_| |_|\__,_|\__,_|\__,_|___/ \_/ |___|_| |_|____/|_____| Welcome to Armbian 23.05.1 Jammy with Linux 6.1.30-meson64 System load: 40% Up time: 2 min Local users: 2 Memory usage: 31% of 1.90G IP: 10.0.10.236 CPU temp: 59°C Usage of /: 38% of 15G RX today: 35.6 KiB Installation: Download Khadas Rescue system (flash to SD card, insert, power on, hold FUNCTION and short press RESET button) Download Armbian image and place it to the USB drive (copy .xz or .img file, do not flash with Etcher) Boot into Khadas OOWOW and install to eMMC by selecting image from USB drive This will soon be simplified as we are going to get into OOWOW.