laibsch

Great news and thank you for reporting back. Do you have any idea what they changed or where they host their sources so we can have a look? There is for example this. There is another user who reported running into problems that sounded a lot like yours.

Thank you for that information, @Mechano. Did you ever get this board to work, with armbian or another image?

looks like a really cool machine. unfortunately, no maintainer in armbian and I am not aware if any of the regular developpers has that SBC. It seems to be based on the H618 which it shares with the Orange Pi Zero3 which is reported working with the latest Armbian release. Did this board ever work with an older release? Is this a regression? I see somebody else mentioning they have issues with the board booting, , apparently due to issues with thermal management. And your crash apparently started in pstate.

Nice. To help other users of the forum, it would be good if you shared what fixed the issue.

To be honest, I'm confused. You reference three different systems and it is unclear to me which one it is that FTBFS for you. Let's take a step back. Do you have the latest git tree of armbian/build? Do you have any local changes? What is the exact command you for compile.sh? I will try to reproduce the problem here.

I do not understand what is "not working". Please elaborate. Also, providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

are you sure all storage devices are working without issues?

I am not very familiar with Radxa and Rock. But I cannot find the board among those supported by armbian. Let me ask you where you got your image and kernel?

Can you point to a patch or some code from Ubuntu how they achieve that?

@Diego Dagum are you using an apt caching mirror like apt-cacher-ng?

Ubuntu is not just Debian. Ubuntu has very different policies and sits on top of Debian. For example, Ubuntu is more tolerant with regards to binary blobs and it very much possible that this would explain your finding. I guess the question you should answer first is why not simply use Ubuntu if it works for you and Debian does not?

Be aware that the answer might depend on the filesystem you are using on your board Be aware that a resize operation can easily destroy your data or at least make it inaccessible have a look at shrink-backup for "reverse"

shot in the dark. maybe this is a regression due to a recent commit @sakittelsen Try "git revert 9eaa276457e11" and try again.

/etc/apt/sources.list:1 and /etc/apt/sources.list.d/debian.sources:1 Those are the files and lines that are duplicate that apt tells you about

... but at the same time, others with H3-based boards seem to have similarly high idle temps reported. @Domas Do you own one of those infrared themometers or have another way to ascertain the true temperature of your board? As the title of this thread says, I am curious about the accuracy of the onboard sensors. Maybe the sensors are even accurate but they need proper software calibration.