6.10.9 breake dtb overlay

[mantouboji]

In the latest update，kenel 6.10.9 changes the layout of dtb overlays , all dtbo in one single folder, no “/boot/dtb/allwinner/overlay” folder.

 

Is it a new feather?

[Stephen Graf]

2 hours ago, mantouboji said:

kenel 6.10.9 changes the layout of dtb overlays

I assume you have built an edge image with a 6.10.9 kernel. Is it debian or ubuntu? I will try to replicate such a build.

[Stephen Graf]

I built a debian edge image and yes the overlays are not where they used to be.  Armbian-config does not even have a hardware option to work on the overlays.

I suspect that work on armbian-config is causing changes that have not yet been fully completed.

If you need to use overlays, I suggest that you stick with the current releases where overlays still work through armbian-config.

[mantouboji]

I don’t build , just only apt full-upgrade .

 

 

[robertoj]

Is it just for allwinner chips? Is this a change for good and toward stability, or is it a mistake?

[Stephen Graf]

8 hours ago, robertoj said:

Is it just for allwinner chips? Is this a change for good and toward stability, or is it a mistake?

Too many questions. Not enough answers.

[mantouboji]

I got it.

 

There is no  un8i-h3-fixup.scr in /boot/dtb . All of  other *-fixup.scr  files are missing .  

 

Please fix it .

[Stephen Graf]

The official image works as it should. 

The edge image may in time be fixed when whoever is working on the changes finishes. It is called the "bleeding edge" for a reason. One can not expect all things to work properly with edge images.

[mantouboji]

I build the latest edge image, and in 6.11.6 this bug still exists. 

 

Why the developer remove all -fixup.scr ?

[Igor]

On 11/7/2024 at 8:36 AM, mantouboji said:

I build the latest edge image, and in 6.11.6 this bug still exists. 

If this was not mentioned in a release log https://docs.armbian.com/Release_Changelog/ and since you already asked, there is no need and you should not ask again.

 

On 10/9/2024 at 10:57 AM, mantouboji said:

Please fix it .

https://forum.armbian.com/store/category/2-support/ and I will try to hire someone for you or fix on your own. This is your problem, not ours. Buy some other hardware. it is cheaper then fixing this.

I hate being an ass-hole, but If we don't stand for ourselves, nobody will, certainly not constantly unhappy and desperate free-software-riders users.
 

Remember this rule once and forever: applying a pressure to open source developers is worse thing you can do here. There are thousands of other problems when we can only address one. And you cover 0.5% for that one: https://github.com/sponsors/armbian Do the math. There is build framework https://github.com/armbian/build download it, dig into the code and fix it. Then open a pull requests. As you can see, we are physically, emotionally and financially unable to support your (endless) greed for software perfection. Don't take this personally as its not. Most of people on cheap hardware, that fully relies on exploiting open source developers, acts similar.

 

We develop and maintain open source software for fun and we chose what that is! With little time that is available. Average resolution time for bugs in open source software is 5-7 years and there is nothing we can do. If you scream, complain or emotionally blackmail us.

 

Closing. @Werner Feel free to re-open, once this kernel will be supported, probably Q1 - Q2 / 2025. Only confirmation that "it works" is expected to be added here, we don't need yet another "still doesn't work" ... ever.

[going]

This is an error in the build script.
The discussion is here: issues/7456

[mantouboji]

It seems in 6.11.9 has fixed , but made  new bug in sunxi64 , dtb path = /boot/dtb/allwinner , not /boot/dtb. so overlay load failed. 

[Stephen Graf]

On 11/28/2024 at 11:05 PM, mantouboji said:

It seems in 6.11.9 has fixed

@mantouboji Yes in testing for the Nov release I tested legacy, current and edge builds for the orangepione.  Ambian-config managed the overlays properly.

If you think there is a further problem with other builds you should document it thoroughly and submit a bug report.

 

Would you also please remove the solution tag from your post of Oct 8. Telling someone to go fix it is not a solution for anything. Thankfully a number of people put in effort to determine that the root cause was in the build procedure and then corrected the procedure. That was the solution.