by
by
Then what about suggesting consulting the respective lscpu output of one's local configuration?
But isn't the whole issue more relevant for professional users buying in batches? – So they could start with one sample. Anyway, any best practices from other manufacturers?
P.S.: Same situation with kernel 6.6 (no RT) from rpi-update rpi-6.6.y (rpi-update rpi-6.7.y fails w/ *** Invalid hash given): Sep 20 14:15:14 xxx kernel: Booting Linux on physical CPU 0x0000000000...
P.S.2: fakehwclock is uninstalled in all cases.
Purchased a Pi5, problem solved.