Igor

There are known / unknown issues with Allwinner ATM: https://github.com/armbian/build/pull/6887 Use some older image from archive, not latest builds. And freeze kernel updates until this is resolved.

https://github.com/armbian/build/blob/main/config/kernel/linux-rockchip64-current.config#L3541 It seems they got disabled here https://github.com/armbian/build/pull/6202 Size reason? Perhaps they don't compile? I have open a PR and lets see what others say about.

What about this? Should already be fixed if you make image from sources.

How long did you wait? Was 1st boot without interruptions? Is your SD card really good? Which image did you try?

But you are running kernel 6.1.y WHICH IS NOT KERNEL 6.10.y, that is mainline derived and still unfinished. It is clearly marked on the download side. Kernel 6.1.y works with Armbian perfectly and on weird HW. Mainline (6.10.y) has been in development for several years by a company and several full time engineers. Not by single person. Joushua uses identical kernel - bugs are identical too on low level. Use images with kernel 6.1.y recommended for end users. They work perfectly. It's hardware interface. Use the one that works, 6.1.y, distro jumping makes no diff. But you should know that by now and you are of course free to choose. Just remember to make a donation to support developers - we don't compete for free riders, we work together to make it best for all!

https://imola.armbian.com/apt/pool/bookworm/b/base-files/ Files / index needs to get synced but I think its ready. Try now.

What about custom hardware, called Pinebook PRO, that needed years before opensource routines were developed by 3rd party (community)? Until then, hardware already become obsolete, maintainace expensive. I am sure Armbian works perfectly on it I am running it on my x86 Lenovo laptop and it works perfectly too. Armbian Ubuntu is exactly the Ubuntu I want & need for everyday work. Do you run Armbian there too and why not? Are you sure? Start volunteering and after a year, you will understand something, after few years you could understand our perspective. I totally agree with you. We do have a mechanism to determine when to adjust status, but it runs every 3 months and with best effort principle. Its not a professional service and runs without any budget. We have no interest to fool you or deliberately waste your time, like everyone wants to waste ours. We try to educate people, but that is usually difficult and expensive as general expectations are shaped by much bigger forces and not with common in mind. This is our try: https://docs.armbian.com/#what-is-supportedmaintained vs. trash proprietary hardware and naivety of people. This is the only way: "Supported/maintained is not a guarantee." As in this world, this is the best you can expect. They sold you demo device without software support and you don't support us to support you! And other big side is telling you something else. We can't compete with that brainwashing. Keeping status synchronized with reality is also expensive, a professional service and also paid from our private pockets. If we would have a volunteer to talk and motivate maintainers, testers round the clock - perhaps you? - we would know faster, before you complaining that something is not o.k. Its a serious logistic operation, while nobody support that so its a complete waste of our time. Why would you waste your time to save everyone's time? While telling me how we should do thing differently to save everyone's time. Step up, make this change so that everyone's time won't be wasted. Also feel free to use any other Linux for Pinebook PRO if ours stop working. Why there are so many alternatives on non-proprietary hardware? And all of them works perfectly. Everyone covers only 0.5% of all maintainers time. Think from that perspective. Armbian is not random Linux me-too distribution. There are no justifications for that and is IMO stupid. It might get fixed upstream, someone might sponsor our work to fix it for you & everyone and you will be happy again. Once support is moved to community, it costs us close to nothing / same as other Linux distributions, which "supports" the hardware. And most people understand that they have nothing to complain about. And are happy when downloaded image works. We needed several years to come out with something that works better then chaos - if you care to understand: https://docs.armbian.com/User-Guide_Board-Support-Rules/

Can you provide some logs and at least content of this: cat /etc/apt/sources.list.d/armbian.list Files are present: https://mirror-eu-de1.armbian.airframes.io/apt/pool/bookworm/b/base-files/ Try to uninstall armbian-bsp-cli-odroidxu4 and install it again. Edit: Oh, I see, armhf files are missing for some reason. Rebuilding.

Use nightly builds. Now they are present. Its 6.6.y kernel. You can try to switch to alternative kernel (EDGE) via armbian-config -> system -> alternative kernel ... however none of this is tested. "Rolling" means, its just shipped and if you are lucky, it works, you have latest kernel, if not, it breaks and you need to DIY to get it back. This is philosophy behind Arch / Manjaro.

Rolling releases are at the bottom of download pages - for each device. https://www.armbian.com/rpi4b/ But for some reason, we didn't produce rolling images for Rpi. I did move it back on. https://github.com/armbian/os/commit/6304fa14b309103eab302b1df9b1e6efec36ff1b But any image you can switch to rolling - at least from kernel perspective: https://www.armbian.com/newsflash/armbian-leaflet-25/ If you need rolling user-space too, then wait (few hours) for new rolling builds or DIY. Beware that rolling user-space variants contains bleeding edge software, which is not tested well.

Then you should buy a MacBook in first place? 😺 From general maintaining perspective it never was - loosing hundreds of hours / several ten thousands to get few hundred from never satisfied - there is always something - customers (of somebody else) is the best deal what we can expect from such low end hardware made for end users that want to buy as cheap as possible. This never cover investments of our time, not even at 1%. It is terrible frustrating. Amateurs maintainers and people that collect donations (our competitors that contributes nothing and waits that we fix problem for you, so they can remain profitable) based on our work are even convinced that once hardware is mainlined that the job is done, but that is right the opposite. Software support in constantly changing software stack needs constant assistance or it breaks down. And you don't believe until its too late. At one point wasting time for software, support and education, goes from stupid to disastrous stupid, Concorde Fallacy is just too obvious, and you cry? I can understand your position, but we are in worse. There is a build framework we happily maintain for you, there is this community you are a part of, instructions for debugging can be found anywhere on internet. Here you can DIY, that's the point - learn, debug it. And, if you want internal experience of making something good - share the fix with others (we don't need this to work, you do!). We will integrate it (if done right) and provide you automatically made image. This is the best what we can do, once we ran out of options.

Possible. I am still the only person behind repo management and everyone just see this as granted or not important. Even things collapsed here and there. If we want that repository function better, someone(s) must step up and and start helping. There are many people and 3rd party projects relying on its well functioning. https://github.com/armbian/build/tree/main/tools https://github.com/armbian/os/blob/main/.github/workflows/repository-update.yml https://github.com/armbian/os/blob/main/.github/workflows/repository-sync.yml

This looks like armhf: https://armbian.hosthatch.com/apt/pool/bookworm/b/base-files/base-files_24.5.1-12.4%2Bdeb12u5-bookworm_armhf__1-bookworm-1armbian1-Bbba0-U12.4--deb12u5-R55fa.deb Don't understand what is wrong?

It is, since moving network bits into extensions. Here it is installed: https://github.com/armbian/build/blob/main/extensions/network/net-systemd-networkd.sh#L11

This was dropped out from kernel by mistake, but it was already fixed at sources https://github.com/armbian/build/pull/6984 You need to build kernel from sources or use kernel from nightly repository that is already having this fix.

"systemd-network doesn’t quite play well with docker." Perhaps this https://blog.kylemanna.com/linux/docker-systemd-network-surprise/ is the problem.

This means Docker works. Minimal Armbian images comes with very minimal systemd-networking since several weeks. This brought much smaller OS images, but could cause this kind of troubles. Try to do some research into this direction.

This is custom hardware world. There are many models, some are similar, some different, some very different. Some vendors sets names with complete absence of any logic ... and there is little we can do about. Orangepi Debian and Orangepi Ubuntu are Armbian fork. They generate those images with Armbian tools that were forked few years ago and where they removed all other vendors out. Instead of cooperating with us on the same code base of the build FW, they "maintain" their own. Also kernels are maintained by https://github.com/orangepi-xunlong/linux-orangepi/commits/orange-pi-5.10-rk35xx/ (one person) vs. Armbian + community maintained (10+ people) https://github.com/armbian/linux-rockchip/branches. We have ditched this very old (named legacy at Armbian) kernel 5.10 few months ago and we just released 3rd version of (named vendor at Armbian) kernel 6.1.y. Both, legacy and vendor are provided by Rockchip and are containing many non-standard solutions that cannot and will never be mainlined. Then there are mainline based kernels, named current and edge, which are derived from kernel.org but heavily patched to provide as good as possible functionality. This latter does not interest HW vendors much as its beyond their control. You need to have a strong reason to run their software. It's purpose is to sell hardware. Armbian bookworm current is what you want. Only problem here is that we (Armbian staff) don't have re$ources to spent on this device, so it will remain community supported. There is also a version of this board that is broken and will only cause additional expenses. And our time is too precious. Absolutely not. Forget about kernel 5.1.y Its dead end, nobody is maintaining it anymore.

We are thrilled to launch this initiative to recognize and reward the incredible contributors who help keep Armbian running smoothly. All existing and new contributors will be entering the pool to win modern powerful and sleek Intel powered workstation: 1 x Khadas Mind Premium + dock and 1 x Khadas Mind Standard + dock Review: https://www.servethehome.com/khadas-mind-is-a-different-mini-pc-our-review-intel-1360p/ About: More info: https://www.armbian.com/newsflash/armbian-khadas-are-rewarding-contributors/ How to nominate? Post into reply why you think certain forum member contributions stands out and should be added to the pool.

Just a tip. Wireless chips (drivers) on those boards are often terrible quality ... Try same method on USB wireless to see if it behaves the same. It might be the driver.

I am glad you are able to understand. Yeah, its done different for each device, untested on all combo and stressful to support. In embedded Linux you need to support specific use case and you tune u-boot to support that ... Oh, we are well aware Here is, perhaps little outdated, attempt to come up with something better:

If you expect something in return, then perhaps you could consider sponsoring, consulting, ... instead? Donations are a gift. Nobody knows that you need this particular hardware to work, while all HW can not be supported. For every USD of donation, we can easily lost 500 USD to get the job done. It is that twisted. FYI. SW developers needs respect and/or financial security while fixing your computers problems instead of you. Nobody prevents you hiring people that will help us maintaining this hardware. Perhaps we stop because we can't afford? Have you thought into that direction? This is open source. There are only a few of people that can afford and want to help everyone, others you need to sponsor. New hardware keeps coming. Software is always changing, maintaining custom hardware remain complex and costly. We need more then just your 50 USD to cover bill that is 100-1000x bigger. Still I thank you as if everyone would donate, it would work out and it would be a big change. Most people don't and many people donates to our downstream that contributes (close to) nothing to you, nothing to us. Perhaps people don't donate as they are constantly unhappy as their expectations are out of the charts. Like paying 0.5% of needed money to cover for the service, but one still expect full blown quick response that is not possible to provide regardless of payment. This software is supported by this community and you are also a part of that support staff. Perhaps helping others is the key? I am personally a lot more motivated when someone helps resolving problems then making a donation. There are too many devices, things are very complex and a lot of time needs to be sacrificed. If someone needs a week to fix this and there is 10 USD of reward waiting for the job ... motivation is clearly something else. Response can only be super slow as we don't have a dedicated person on this hardware, vendor doesn't help us neither, we already do more then possible. We stop supporting some hardware when there is nothing more to be done. Donations don't cover a single support person. And behind support person, there are developers in many areas, project managers and other support staff. We need them all in order to operate, and millions to provide software support to people the way they / you expect. Not few thousands. But we don't give up neither. We keep going. I will tell you from my personal perspective. I would need several days of silence, that nobody else would want anything from me, to look into the problem. While looking into I will find more problems and will try to fix them. I have to deal with so many other things that this week can't come anytime soon. Not this year, not next. Having 10, 50 or 500 USD of donation (and to blow additional few thousands of my own) makes no change. And in this time I need to earn those few thousands to fix your problem. Then its a thin line between donations and something else. Conditioned donations are professional services. But since local McDonald's pays significantly better hourly rate without requiring high-end education on top of 20-30 years experiences ... If we need to keep some hardware operational, its up to the maintainers first. Volunteers decide and we (Armbian pro support) support them if possible https://docs.armbian.com/User-Guide_Board-Support-Rules/ If we have nobody that will be sponsoring you / taking care of hardware, there is nothing we can do. Donations won't change this, but you can try sponsoring a person within Armbian that will be supporting this hardware for you. Even this is very hard to arrange. And this is also open source with no (c) protection. For authors this is hard place, there are bad players and many traps to fall into.

Armbian aim its to make and maintain Linux (firmware) from when the power is connected to the board. This is much closer to embedded Linux then normal Linux distributions. Nothing less then full control. Ofc this is not always possible, but we know how to do it ... and when / where this is achieved, this is fun. That heals frustrations and depression Problem starts with maintaining all this. As this is everything but fun, require different mindset, gets boring and is easy developed into full time job that brings no / too little food on the table. Average (x86/Rpi) Linux distro users, who doesn't understand any of this, would "only like that everything works". Armbian is Debian from outside, but it could / can be Arch or whatever flavor, if someone would be crazy enough / have have too much time to add extension to make Arch output / rework that that kind of customization are possible. Why doing that if the aim is to run Linux firmware / some use case / and that is already very difficult as this everything but standard made hardware. Vendors don't want that you run (mainline) Linux. They want to sell hardware with their partially closed SW, similar to / with Android. We want to help users running Linux on those exotics, often for single purpose made, devices. In embedded / custom Linux world, where we are, distribution philosophies are usually wrong. Yes, you / we would like to have UEFI to spare troubles ... well, making it is Concorde fallacy by default except mainstream hw. Do you have required funds and / or enough power to motivate volunteers to make it? Users are scattered around many many devices, which will (never) be under UEFI. If you move device to mainline Linux with basic functions, its already a (great) success. Costs millions (core work can not be done and its not done by volonteers) on top and around community help. Where masses are behind - Rpi, now RK3588 and similar variants are going to get this, others too late or never ... Many things should exists but they do not Making hardware was never this cheap and Rpi model proved that community will make firmware instead of them or not at all. Something is always provided by SoC maker. This is what they hope for. Some helps and invest into SW, some not at all. And most users have don't know this nor care about. Armbian is Linux build framework first. A framework that helps us and community maintain this endless crowd of custom hardware. They were purposefully made not to be standard and what is under Armbian is already a lot of standardization applied. Because power of build framework and people that made and maintain this. Regulars, part timers, random people that shows up. We could do more, but we don't have re$ources or sufficient level of support. There are some people that will be very helpful for this, but usually they do not have the know-how to pick it from here. Volunteer developers do that anyway, but majority of solutions are never integrated as core team is simply too small. And this is never to be changed. We are surviving with keeping the focus on some devices, leaving others "to community / anyone that wants / upstream / * ". Line has to be set somewhere as otherwise doers would burn out, level of sadness would eat us out. Some exotic devices nobody will ever pick it up if some of developers won't donate months of his time. Then this works is picked up by some other distributions. We have noticed ArchLinux re-packing and serving our Rockchip kernel, others are too exotic. This market function this way. They design hardware and provide support for business clients. Amateurs are often collateral damage. This is hard to change. Expectations are set with marketing and are often set with different objectives. Then you add complete lack of technical understanding from end users and you get a clash. People that come for help are frustrated, support givers are 1/1000 and totally milked out ... Armbian supports (in term of ordinary Linux distro) lets say 200 devices. In reality we only know for those, where we have maintainers - "standard Armbian support" https://www.armbian.com/download/?device_support=Standard support which are volunteer and they come and go. We (core team, partially pro) maintain framework, ecosystem, some devices. They don't maintain devices for us (Armbian), they maintain devices for you, users, community. Device that works good with Armbian, can easily run any other distro. Well, not UEFI easy. Still some devices were made in small quantities or were largely abandoned for better new models. Many people run do-not-touch-as-it-works glued together image which nobody can ever recompile. This problem Armbian solves very well. And closer to humans as some industrial grade tool such as Yocto.

Ebin Ultra is very similar as this one, I even have one device somewhere at home, introducing several new troubles ... I think it even boots and works to some degree with normal Ebin image without changes. This is pretty normal in this world. Most of custom hardware does not have UEFI nor need it. UEFI is expensive to make and they sell hardware at BOM + profit only. Software support is buyers problem at the end. Time is the problem. I can spent sharing some experiences, not sure if valuable ... We have lost insane amount of time in past years trying to keep functional Linux image for this hardware. User space plays absolutely no role, kernel little. And this is just one custom hardware out of many. We received hardware valued 50 USD as a support for this in all those years in exchange for hundreds of hours to keep this device usable ... and Armbian team mainly don't need this to work. Users do, while costs of keeping this (terrible made and supported) is over extreme for our hobby / private time / pockets. And users, which are in 99% unable to see pain and frustration, mainly complains how something doesn't work ... never happy people never rewards maintainers. Work here is "only" related to keeping boot loader functional. Which is ofc not small nor simple. From there on, standard generic aarch64 kernel boots. For several years now. I don't think we can count anything from end users / amateur distributions as they require standard way of booting, but there was help from kernel.org communities. As this board can be moved under generic kernel, so whole marvel SoC mvebu64 kernel family can be dropped. Which would need to be expense on overloaded Armbian team. Or good will of someone from community. My 2c.

Try this method: Not sure if prebuild exists for this target but you can follow instructions and DIY.