most hard part is build scx from AUR, after last build, all failed.
I have no clue why your build failed but RPi enabled NUMA starting last week.
https://github.com/raspberrypi/linux/commit/27d8bf670fe2ff29e96ce46f80b81df617b14ece
anyone build scx-scheds-git success, in their PKGBUILD set āarch=(āx86_64ā āaarch64ā)ā?
v6.6.59 and v6.11.6 kernel packages pushed to unstable when the mirrors sync.
2 Likes
NUMA testing.
https://forums.raspberrypi.com/viewtopic.php?t=378276
Pushed raspberrypi-utils-20241025-1 to unstable when the mirrors sync.
Will doā¦ And can please push the latest version of xorg-server etc.
Been stuck in the dark for while now.
Done. Wait for the mirrors to sync.
2 Likes
Numa isnāt enabled with 6.12. Probably related to https://github.com/raspberrypi/linux/pull/6443 ?
I read that
As a side note for me 8 is too many, Iāve got memory allocation failures when attempting to do nfs mounts. So I would say itās probably a bad default.
It is not the default for Pi4 (which is 2). If you have a large cma region configured you may hit problems (cma must fit into a single numa region).
In general significant cma (e.g. more than 64M) is not needed on Pi5, where all hardware blocks have iommus and can use non-contiguous system memory.
I donāt remember if cma was enabled by default. I have removed mine.
Edit : I need at least cma-256 to play heavy h265 files smoothly
old monitor is 1600x900@60 dying.
new one will be 1920x1080@100, does it need set something in config.txt or cmdline.txt?
or, just plug&play.
I would start out with Plug & Pray.
thanks, order from China 1111 festival 24" 20% off 
v6.12.rc6 pushed to unstable when the mirrors sync.
Never mind. I just switched. Why am i on arch if i am not gonna go to the very edge 
I always stay on the last kernel I build and test until the next one comes out. So I will be on this one till the end of the week. The -rc kernels of course can be buggy but I very seldom have any major issues with them.
The 6.12 kernel will most likely be the next LTS kernel. RPi will not switch to it as their default kernel though until they feel like it is stable for the piās. Until that time they will be constantly fixing things. So the more testing on our end we do will help speed up the process.
Added 11-08-24:
v6.6.60, v6.11.7 kernel and raspberrypi-bootloader 20241108-1, rpi4/5-eeprom 20241108-1 pushed to unstable when the mirrors sync.
1 Like
Thanks @Darksky for the latest 6.11.7 kernel.
Did you have the chance to take a look at the following commit?
It may help us to boot faster.
Updated 11-11-24:
v6.12.rc7 kernel packages pushed to unstable when the mirrors sync.
1 Like
it seems that youāve erased the previous message. 
BTW, Iāve made some cpupower tests on my RPI4 with 8GB of RAM in a Argonone case with a fan, and it seems that I get 4Ā°C hotter on performance mode.
It trigged my argononed deamon to start the fan all the time but I didnāt want to change my settings yet.
Here is the normal behavior on āondemandā mode:
Fan Status OFF Speed 0%
System Temperature 42Ā°
Hysteresis set to 2Ā°
Fan Speeds set to 33% 66% 100%
Fan Temps set to 44Ā° 48Ā° 50Ā°
Fan Mode [ AUTO ]
Fan Speed Override 0%
Target Temperature 0Ā°
Daemon Status : Waiting for request
Maximum Temperature : 54Ā°
Minimum Temperature : 39Ā°
Daemon Warnings : 0
Daemon Errors : 0
Daemon Critical Errors : 0
And there on performance mode:
Fan Status ON Speed 33%
System Temperature 45Ā°
Hysteresis set to 2Ā°
Fan Speeds set to 33% 66% 100%
Fan Temps set to 44Ā° 48Ā° 50Ā°
Fan Mode [ AUTO ]
Fan Speed Override 0%
Target Temperature 0Ā°
Daemon Status : Waiting for request
Maximum Temperature : 54Ā°
Minimum Temperature : 41Ā°
Daemon Warnings : 0
Daemon Errors : 0
Daemon Critical Errors : 0
I did not read the commit thoroughly the other day when they did it. What they are doing is booting now by default in performance mode only and then switching to ondemand by default via a script in /etc/init.d/ (if a shortcut key is not pressed).
1 Like
So does it mean that youāre going to take this commit into account?