Orange Pi Zero 3

[c0rnelius]

8 hours ago, mantouboji said:

Maybe we should rollback to commit d502356d0271f0d5748b67e4b4d998b51e588c6a (tag: v25.8.0-trunk.293) and remove all patches from pyavitz@gmail.com,

 

Could do that. Or you could do a PR and turn on what is now missing from the defconfiigs that is required for your use case. Probably more productive than endlessly complaining.

 

Nothing got intentionally disabled or turned off. They are two new defconfigs that are getting re-worked so everyone with in the community can profit. Not just the OPi crew.

 

[c0rnelius]

The defconfigs are also just one piece of the problem here. There are patches getting applied to Sunxi for the Rockchip platform, why? Patches for the Pinephone, why? Last I checked that's not supported in either standard or community. Allwinner on Armbian has also been plagued with Bluetooth issues for years. I would venture to guess this is related to unchecked and unverified patching along with a defconfig that looks like a 5 year old went through and just ticked everything on.

 

You tell me. Who wants to deal with this? Who wants to help fix it? and whom would want to do any work in this muddled up environment.

 

[ABhomeuser]

Hello there! I was looking at the new images from May 28th and noticed that for the minimal/IOT section there was two Debian Bookworm images with the exact same name. They appear to have a different sizes (230 and 241 mb) but no explanation is given for what exactly is different between the two. Does anyone here know what the difference between these two images are?

[ag123]

@ABhomeuser

the board page is a bit out of date

https://www.armbian.com/orange-pi-zero-3/

Debian 12 (Bookworm)	Minimal / IOT			SHA 	  ASC	241.1 MB
Debian 12 (Bookworm)	Minimal / IOT			SHA 	  ASC	230.3 MB

@Igor  ^ how do we update that on the boards page?

 

are actually the same file. proof:

download the sha file for each of them and look at the content, you can see that both the filename and hash is identical in both sha texts.

this means that both files are in fact identical  and actually the same size, despite the incorrect file size indication on the front page.

 

in fact that is currently linked to this release on github

https://github.com/armbian/community/releases/tag/25.8.0-trunk.375

^ this is released last week 

there are in fact 'earlier' releases, I'm running an image from this release

https://github.com/armbian/community/releases/tag/25.8.0-trunk.309

 

I'd suggest going with the 'latest and greatest'  (trunk 375) (which is that on the boards page currently) and if there are issues,  then try that a little earlier e.g. in the latter link (trunk 309).

armbian community images are rolling releases, they are 'fast moving' and perhaps come back in a few weeks, and it could be another trunk release number.

but simply take an image 'as of now' and normally it 'just works' e.g. from the  boards page.