Follow-up to this note:
At one of the times the current
#Armbian #linux kernel didn't crash, but booted on my #RockPro64 I installed #GotoSocial and yes: no more strange error messages running it. The only time I remember that I updated a linux kernel to make an application work.
Preparations to get the production system running with the newer kernel:
- in case of problems I'd need to know my way back to boot the old kernel: u-boot recap and learning
- test suspected problems with the #sata #pcie ctrl beforehand (get a second Pine64 sata ctrl for the test system)
Meanwhile Dragan had patched the device tree and asked to check on a few reboots whether this would make a difference or cause any regressions.
Further down the #RabbitHole the tunnel forks…
On my #yunohost I tried to update #gotosocial from 0.17.4~ynh1
to 0.18.1~ynh1
and the update failed.
GotoSocial just showed some cryptical error messages when started.
@dumpsterqueer@superseriousbusiness.org traced the problem back to a changed lib version used in the new GotoSocial version and the developer of the lib answered my #linux kernel would be too old.
The old #armbian legacy kernel is running, because … I don't remember.
I need a kernel update for my #rockpro64.
Down the #RabbitHole…