Well, so far 5.11.y is an interesting release. It works fine on my Raspberry Pi 4, but is unstable on the Rock64 (acts fine at first, but eventually the board locks up and stops responding entirely), and acts REALLY strange on the Pinebook.

For the Pinebook, even the two images give different behavior. The base image will boot all the way to a command prompt, and you can build up a system from there, but eventually random features do not work as expected, like shutting down or rebooting.

The xfce image is even weirder: on first boot it hangs right after displaying the ssh keys random art, right before the "devpts /dev/pts" line. It never gets through even the first boot completely. This only happens on the xfce image, which is beyond strange.

I even tried using an older image and upgrading the kernel on that one to 5.11.y. It acts like the base image above: random features go away such as rebooting.

This is happening on both 5.11.10 and 5.11.11 so far. I have tried multiple builds on multiple machines, and the behavior has been repeatable. I have not had the time to generate and look at logs yet. That might happen over the weekend (depending on my workload, I am trying to meet multiple deadlines in the next 2-3 weeks...). I just thought I would let you know that so far it is super buggy. Does it have all the right patches and configurations for the Pinebook's quirks? Just checking.....

I still need to do some long-term debugging on 5.4.y and 5.10.y. Both eventually give some sort of instability to the X server, either crashing or just plain locking up, after they have been up and running for a while. I still am having the best experience on 5.6.19, for what it is worth....

thanks much, as always.

UPDATE: I was able to grab some log files from a fresh xfce 5.11.11 image's first boot. I put them all here.

shelldweller, thanks for the logs provided.

for allwinner the patches are the same as 5.10.y.
confused by this error: drivers/clocksource/arm_arch_timer.c:364 sun50i_a64_read_cntpct_el0+0x30/0x40. parsing

Rock64 which version of the bootloader, stable work with DDR blobs.

update:
I checked 5.11.11 on Rock64 there are no freezes.

1 members found this post helpful.

Ah,that would explain it then. I had only updated the kernel files on my LAN server, I did not update the bootloader at the same time. I will try that when I get the chance next. It might not be for another few weeks before I can really test it thoroughly. If I run into anything interesting, I will post in the appropriate forum.


Regarding the Pinebook stuff, it makes sense that it is all connected to cpufreq somehow. I went back to an old 5.5.19 image just to see what was so great about it, and one thing I noticed is that there was no cpufreq capabilities at all. It would just spit out an error message saying that no governor had been loaded. So, no wonder I was not having those issues back then. The cpufreq driver probably did not work at all then, and now it works but is buggy.

In any case, thanks for that Armbian link. I had checked there a while ago, but had not seen the newest posts. Appreciated.