Igor

It takes some time before OpenHab initialises. How long did you wait? Can you provide some logs?

From our point of view, end users cover less then 0.5% of the software investment we provide for everyone, including projects that competes with us with our investments ... Hardware dealers sells hardware with promise of software support. You buy numbers and features ... and then there is new HW coming out. And new, and new ... This is everyone's biz case. The more HW sell the better for them, the bigger is the pressure on us and the rest of developers community. Sadly a lot of Linux distributions contributes close to nothing, or 1/1000 of what we contribute, but can sell the same. Investing even more into development + support and less in sales is self-destructive. Remember, you want this for free, while getting here costs are extreme. Than you for your support!. Sadly expressions of love and support doesn't pay our bills You have to improve your share One day of support financial damages are not collected at GitHub in one year. For those that have time, but no money, we support them instead of you. We do everything possible to improve software and this huge discrepancy.

Thank you! Perhaps try to implement those findings into main documentation? Similar to those ideas: https://github.com/armbian/documentation/issues/467 https://github.com/armbian/documentation/issues/471 We also have some stimulation in place. There are so many useful things made by community, but it is impossible to integrate most of them due to small resources on maintainers side. Either into the codebase or documentation.

I found a workaround for this problem. Need someone to confirm if this works: 1. Download https://archive.armbian.com/pinebook-pro/archive/Armbian_24.2.1_Pinebook-pro_jammy_current_6.6.16_gnome_desktop.img.xz 2. sudo apt update & sudo apt upgrade 3. reboot 4. install to eMMC or nvme Does it survives?

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

Should be fixed but we didn't have time to test. Those images are getting ready for release: https://fi.mirror.armbian.de/incoming/igorpecovnik/rock-5-itx/archive/

https://github.com/armbian/build/blob/main/packages/bsp/common/usr/lib/armbian/armbian-firstlogin

Its known issue. We don't have a fix yet.

Recently we have experienced build runner related corruption, also on other images. Try to build image from sources: https://github.com/armbian/build

This is unmaintained. bsp packages are going to main repo, which is release independent like kernel ... and here is the problem. Fix is to not update this package. For future: - use maintained builds - we can fix this on our side, but don't know when.

This is just enabling disabling armbian logo on boot time and i think it might be deprecated functionality since inteoduction of playmouth. We user to bake logo to the kernel. Wrote on mobile

Or latest image from download section: https://dl.armbian.com/renegade/Bookworm_current_minimal-homeassistant Then we try to resolve. I don't have this hardware to be able to test. I tested on some other devices.

I think he want to pass URL to his kernel GIT source. Which I also don't know from head but was asked before here. I think something like: ./compile.sh kernel KERNELSOURCE=git KERNELBRANCH=main

This was not designed to be user configurable, but you might find something on forums. If you are a business user, sponsor and we will rework it. I have added this task to those that are in award pool. Once you find out, make notes and submit this to main documentation. You might make someone else happy. And yourself if you win a cool mini PC https://github.com/armbian/documentation/issues/471 It would be best if both is done, rework to be user configurable and some notes in documentation.

This information can only be provided by maintainer of this hardware. If there is none, its not possible to know. I can assure you that Armbian images worked at some point, but don't know when problem started or which works and which don't. I don't have this info. This board is waiting for love from someone.

unsupported builds have weekly auto-builds and at one point it started working. i already removed that part of the text.

Logs says you are compiling quartz64 ?!

I suggested you something entirely different based on knowledge and experience. Not sure that it will work, but success ratio is much bigger. What Does Community Support Mean? Community maintained boards are not officially supported by the Armbian project. These boards are maintained (or not maintained) by community members (like you). These builds are provided by the Armbian project as a service to the community. They are automatically generated and untested! Maintaining custom devices is extremely costly and this level of support from your side (for whole project) is not sufficient (1/100 of needed for current level of work) for proper maintenance or R&D. For every USD of donation, we need to find 500-1000, often a lot more, from our own pockets, do it for free, to keep those devices operational. At one point we need to cut devices off to random community maintenance. Community help exists, yes, but it is small and fragile. You can't or don't want to support us financially? No problem. There are volunteering positions. If they are not filled, project struggles - if project struggle, we can't address common nor egoistic technical issues. If you help to refactor documentation, for example, and have some luck, you can get a high end workstation from us. See? Your contribution to common work is essential, not telling us what is wrong. We know for many many problems, but we can't resolve them. We lack people / resources / your support to fight them. Still, we provide images and they might work good to some degree. If they break, yes, you are welcome to report it here, but don't expect solutions. Team is overloaded with, very limited, officially supported hardware. And this board is not among. I would naturally like to help you with this problem, but I (or people that helps) could realistically look into this once mid next year as there are many other unresolved problems waiting in the list. You probably expect this to be fixed "yesterday" ... impossible, even if you start to respect our time and buy at least one hour at this level. No you will not. Why would you? There is another workaround / hint - use older images from archive. Some will work, but yes, update will kill them - don't update. Remember, not even officially supported hardware has professional level of support. Only better.

If this is minimal image - we have changed networking config to NetPlan: https://docs.armbian.com/User-Guide_Networking/

No, pathches will not apply for this kernel. That is just an idea. Path suggested by Nico might work. But that kernel is old ... With other limitations. Wrote on mobile

Oh. I didn't looked into the code ... We have a few of patches for previous generation in order to work (better), but on mainline: https://github.com/armbian/build/pull/6057 https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.6/rk3399-rp64-pcie-Reimplement-rockchip-PCIe-bus-scan-delay.patch

Known problem. https://armbian.atlassian.net/issues/AR-2434 It is probably solvable with enabling correct overlay. I can see we don't have a dedicated for ITX board, but try others. @amazingfate Should we put this into main DT instead so its just enabled by default?

Try to build Noble with EDGE 6.10.y kernel - I think all this already works. Legacy kernel, especially 5.10.y, is too broken in many aspects and will never be updated = waste of time.

OK, then its something else apparently. We'll keep an eye on it, but if Ubuntu based variant just works, use it. There are no Canonical services in it so its more similar to Debian then regular Ubuntu for desktops, just better as packages are a bit more recent, more polished.

Vendors kernels are frozen in time and maintained only at HW stack level, while the rest is "as is". Which is why we all want mainline ... which is even a lot more expensive to make and maintain. It could be days, which can extend to weeks, of work with no warranty of success to sort this out - porting this kernel feature from upstream patches: https://www.kernel.org/ Here is best to wait for next kernel update by Amlogic, which is usually based on updated kernel stack.