Open autrimpo opened 1 week ago
can confirm. same here
I am experiencing the same issue. I also noticed that home-manager
outputs the following warning: libEGL warning: egl: failed to create dri2 screen
.
During the update, there was the following diff of packages (perhaps one of the removed packages is causing the problem):
Version changes:
[U.] #1 asahi-audio 2.2 -> 2.3
[U*] #2 cpupower 6.9.12-asahi -> 6.10.6-asahi
[U.] #3 initrd-linux 6.9.12-asahi -> 6.10.6-asahi
[U.] #4 linux 6.9.12-asahi, 6.9.12-asahi-modules, 6.9.12-asahi-modules-shrunk -> 6.10.6-asahi, 6.10.6-asahi-modules, 6.10.6-asahi-modules-shrunk
[C.] #5 udev-rules <none> x2 -> <none>
Removed packages:
[R.] #1 extra-utils <none>
[R.] #2 initrd-fsinfo <none>
[R.] #3 initrd-kmod-blacklist-ubuntu <none>
[R.] #4 keymap <none>
[R.] #5 link-units <none>
[R.] #6 rust-lib-src <none>
[R.] #7 stage 1-init.sh
I cannot reproduce this with a NixOS unstable + M2 Max + non-homemanger hyprland. Could someone post their kernel log?
I use NixOS stable on an M1. Here is the kernel.log
I believe the issue lies in the following error: apple-dcp 38bc00000.dcp: RTKit: syslog message: PPipeDCP_H13P.cpp:11109: IOMFB updateFrequencies EDT ERROR: getClockFrequency(0) (237333328) < videoClock 402278400! Giving up on frequencies.
This error points to a mismatch between getClockFrequency()
and videoClock
, indicating that the system is unable to properly synchronize the display frequency. The system is attempting to set a clock frequency of 237.333328 MHz
, while the expected video clock is 402.278400 MHz
.
I will also review my kernel log to check for any additional details.
My kernel log is different, but I am still encountering errors related to getClockFrequency()
. Specifically, I find this error: PPipeDCP_H13P.cpp:11092: IOMFB updateFrequencies: minimum-frequency property not found, using getClockFrequency(0) instead.
It seems to be connected to the kernel log of @jmastr.
kernel.log
Here's mine, I also see the frequency error. kernel.log
The issue does not seem to be related to getClockFrequency()
as I initially thought, because it occurs in both kernels. However, when comparing the kernel logs between versions 6.9.12 and 6.10.6, the following differences emerge:
Missing initialization of the Asahi GPU in kernel 6.10.6:
[ 2.336925] asahi 206400000.gpu: MMU: initialized
[ 2.336927] asahi 206400000.gpu: GPU ID registers: 0x4021100 0x40a04 0x30808 0x40404 0x1320300 0x101311
[ 2.336931] asahi 206400000.gpu: GPU Information:
[ 2.336932] asahi 206400000.gpu: Type: G13G
[ 2.336933] asahi 206400000.gpu: Clusters: 1
[ 2.336934] asahi 206400000.gpu: Cores: 8 (8)
[ 2.336934] asahi 206400000.gpu: Frags: 8 (8)
[ 2.336935] asahi 206400000.gpu: GPs: 4 (4)
[ 2.336936] asahi 206400000.gpu: Getting configuration from device tree...
[ 2.337151] asahi 206400000.gpu: Dynamic configuration fetched
Initialization of the simpledrm
framebuffer:
simpledrm
framebuffer is initialized correctly in both kernel versions. However, in kernel 6.10.6, it seems to be the only display-related component that is loaded, with no further initialization of the GPU.This is my kernel.log when switching to nixos-unstable
. after that GPU is working fine, which means it is "just" a missing dependency on stable
?
Does anyone have an idea about how to fix this dependency issue on stable 24.05?
Same thing happens to me, Hyprland doesn't launch
Do we know what packages are causing the issue? I can try various overlays in my flake if not.
After updating to 2024-09-03 I'm getting issues loading the mesa driver:
LIBGL_DEBUG=verbose glxinfo -B
with 2024-07-31:LIBGL_DEBUG=verbose glxinfo -B
with 2024-09-03: