Igor

Expensive research is usually needed to fully understand why this is happening. But as most developers knows that Rockchip legacy kernel is a consumer demo-grade trash, its unlikely this will happen. Repairing deep problems just for this kernel is usually futile. It is not Armbian problem, but Rockchip's which provides this fork and currently the only stable(ish) kernel you can run on those devices. It is worth trying to build image from latest sources. They have been greatly improved, but can't tell if your problem will be gone. I assume you are using stock power supply? Not sufficient power can help in crashing ... If you need to run some serious things on your device, move to test 6.5.y kernel (CI builds at the bottom of the page). This is the only sane way, but they come without video output. We are running several build runners on few Rock 5 devices and so far it does the job. Here are logs: https://paste.armbian.com/gupidarusa BTW, Welcome!

Debugging and fixing is not automatic. You will need to fix it first. When your fix will be merged, then new build will provide fixed results ... It could be this.

Try latest images from CI automated build section - should be fixed by now. Stable images rebuild = soon. https://www.armbian.com/download/

https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one

Yes. Vendor kernels are traditionally a pile of sh*, as cheap production as possible. We provide images with experimental kernels v6.5 to try out (at the end of download page). There it might work, but don't complain about several non/badly working things - its not production quality / stability. We are running several GitHub runners on two devices. With vendor kernel, this job was very fragile, while here, so far, it just work.

Welcome to Armbian community support forums! Adjust expectations ? We also need to. Even small group of contributors are throwing thousands of our hours into supporting you, this is not on the plug and play Raspberry Pi level. Developers base here is smaller facing much bigger hardware diversity. You don't have many options. Stock, Armbian or Armbian based OS (with the same problems). I believe stock is best at such things, but also on Armbian this should work ... just analysing and fixing is perhaps not on the consumer grade time frame. Support, where 99% contribute with demand and questions, can only be best effort. Next time, when you will run into problems, provide logs, try to help someone in between, make friends. This helps you most when you are in trouble.

Strange. Vendor asked us to update images with new boot loader that should support most recent board revisions with new memory chips. I don't have that latest board, but those images are: - automatically tested on stable and unstable kernels https://github.com/armbian/os#latest-smoke-tests-results (no issues found, but testing is limited) - manually tested Bookworm with Cinnamon desktop (this) on M2PRO (which is identical to M5, just different size and comes with onboard wireless) . Logs https://paste.armbian.com/elogateles For further diagnosis: - console boot log - pcb photo

Now unpack both files (DTB to DTS) and run diff on files. That might reveal some clues.

Sources are here https://github.com/armbian/build Take a look. To be sure to be ignored? Your second identical post was deleted as its obviously against the rules. This is community forum, not a satisfaction machinery or customer support mixed with forums (Radxa, Odroid, ...). You are not our customer, Armbian community or maintainers owes you nothing. Here we help each other. How you can help? Be different. Look around if you can help someone ... or act shocked on my patronising. Welcome! 🙃

That is off topic. But if you brought that up - I show you opportunity to help changing precisely that problem, to help yourself and others that helps you with very little problem, where you can't say "I don't know, its too hard", as this is the only way things can improve. Armbian team, people you hate because they don't provide you top software, lost 100 hours every day, donations covers perhaps 3-5 minutes. Everything else we need to cover with our private resources. This also bring a lot of FOSS predators they are stealing in organised manner, including vendors. Some are playing very dirty. If few people would add their small contribution, like this one, without me spending hours and hours trying to convince you to help yourself, that changes a lot.

Are you changing kernel version with a patch?

So you managed to build a good image after all?

This script works (almost) on any .deb OS and also on Windows / WSL, x86 or arm64. Build system is containerised and container inside container is calling for troubles OK. Perhaps rather focus on this part and try to make a PR for both WiFi chips. Enabling this module is certainly not a reason why board doesn't boot. It can be your build host or there is some f* up in around u-boot. What about nightly / rolling releases from bottom of the page - that is fresh https://www.armbian.com/rock-3a/ Do you have a serial console perhaps? First build system didn't work on weird host, now image doesn't work. Well, I don't have this hardware, can't check. Perhaps @vamzi @catalinii @ZazaBr @amazingfate can provide some hints - is latest build working well or not. P.S. As you can see, in software development, we can easily blow a day achieve nothing (except learning for those that don't know this)

Exactly. You can get first hand information only if you will be investing your time to help us: https://www.armbian.com/participate/ If you will be asking from users perspective, "access denied" comes by default. We are not Lenovo employees or contractors.

Image is not made by installing .deb package. You need to use https://github.com/armbian/build and you will receive no support. As build target is not supported. You should also find that in the documentation. Not just your rights. This world is not as simple and organised as x86 Debian world you must be coming from ... sources are on Git. We don't hide anything, just support is extremely limited. Next cycle perhaps. https://docs.armbian.com/Process_Release-Model/#release-cycle

No. This task was assigned to general public as we are completely overloaded with work. If you (anyone) will not provide a PR, this will not get it. I don't need this feature.

I changed what you suppose to change, recompile, it works. It also works for many people and many automated scenarios. Strange ... but deep hidden problems absolutely can exist. Open a ticket here: https://github.com/armbian/build/issues and provide everything that is asked in that wizard. Then we might understand why you have issues.

We have two major changes at PR stage that needs to be merged and fully tested. Alongside with fixes on HW side. Then whole system stabilisation has to begun ... How you can help? Providing status of any board labelled as supported, that is not covered with our automated testings, helps: https://github.com/armbian/os#latest-smoke-tests-results This testing is primitive, so manual checking also helps. If there is a bug, open a ticket: https://www.armbian.com/participate/ If you can, fix it, sent a PR. Few people that contribute to Armbian anyway can't fix all bugs found in open source software.

Stock CLI image is already fully optimised, comes with configured ZRAM, everything is ready for you. Nothing more, that would have any noticeable effect, could be done. This is one of the core advantages of Armbian. If you have a fast storage you and your processes get OOM (killed due to lack of memory) then try to add swap file. If that doesn't work out, consider HW with more memory ... BTW, 2Gb that comes with C2 is plenty of memory for what you plan to do unless you will have "millions of records" in your database.

You are using some old randomly assembled development kernel. It is miracle that it worked this far. No development kernels receive end user support, because costs of supporting you goes sky high and you are involved in cost covering with cold 0%. Free hint: use unchanged OS from download section, which comes with a kernel that received things 6.2.3-RC3 never will = stabilisation. That is troublesome enough.

This information tells close to nothing. A picture of board would help to determine if any help is possible.

Once operational, remember to enable for nightly builds. I just added Rock 5 yesterday https://github.com/armbian/os/commit/c18ab86105e88571453afadf9dd72432a94b75b1

Registration https://id.atlassian.com/login is covered by Jira software. I just tried with some Gmail account and it worked ... Anyway, sent an invite and this should work ...

https://www.armbian.com/participate/ (register to Jira, open a ticket similar to this one https://armbian.atlassian.net/browse/AR-1803 assign yourself to AR-1803 and the one you will be creating for MT7915E solve both in one PR https://docs.armbian.com/Process_Contribute/ (specific instructions on what you need to do are in AR-1803) Its a great and simple way to make a contribution to the open source project. Once merged, changes will be automatically pushed to beta.armbian.com within <24h.