#asahi · 2026-03-15 17:47
lukaskelHey everyone. I'm eagerly following the Fairydust branch - been 2 months since I last tried it and was amazed by the work already done. Does anyone know if there had been any updates regarding color management? On my LG C2 the colors had been really over saturated back then, and just wanted to check in before I give it another whirl. :)#asahi · 2026-01-03 00:31
lukaskelThanks a lot for your work of looking into it. :) Most people might be quiet about this stuff, but for everyone using linux in production this will be huge and contribute tons.#asahi · 2026-01-03 00:29
lukaskelFingers crossed. Wish I could help but still to early in my coding life to contribute aside testing and reporting potential bugs. If any tests are ever needed for color ranges and hdr, I‘ll be there.#asahi · 2026-01-03 00:22
lukaskelAhh thats amazing. Already super happy that DP is now working. Will experiment more and report any bugs, but first impression is super smooth. Hats off to everyone#asahi · 2026-01-03 00:19
lukaskelThanks everyone!#asahi · 2026-01-03 00:19
lukaskelMy external screen is now working, which is amazing! 4k, 120hz. Super smooth and hot plugging seems smooth as well. Sadly no HDR showing, but that could also be KDE or my cable. Or in general linux being semi hdr friendly still#asahi · 2026-01-03 00:18
lukaskelNvm, I got it to work with setting new default with grubby command. :)#asahi · 2026-01-02 23:51
lukaskelThe kernel now compiled without issues and but after make modules_install and make install, as well as grub2-mkconfig it still boots the old kernel which is now with the new dtb laggy as hell.#asahi · 2026-01-02 21:18
lukaskelThank you so much so far!#asahi · 2026-01-02 21:17
lukaskelGotcha. Will double check, was sure I checked in there but maybe I just searched for secure boot#asahi · 2026-01-02 21:16
lukaskelconfig from existing install always throws me an error during compile that "no rule to make target 'kernel.sbat' needed by 'arch/arm64/boot/zboot-header.o', so I went from defconfig#asahi · 2026-01-02 21:11
lukaskeldoes "make defconf" and afterwards "make asahi.config" need any additional configuration if that module ends up in my kernel? Was also suprised to see it connected to mostly broadcom cards from my lil research and no apple information at all#asahi · 2026-01-02 21:09
lukaskelAny idea where the p2p-dev error comes from when booting? Or is that also a cause of the missing rustavailable part potentially? Sometimes needing more than 10 reboots to get past that error again and into fedora#asahi · 2026-01-02 21:07
lukaskelGoing crazy if that was my only issue now, lol#asahi · 2026-01-02 21:07
lukaskelThanks. Aside of that my whole pipeline seems correct though, right? Stage 2 boot.bin with the right .dtb is mandatory at that point, right?#asahi · 2026-01-02 21:03
lukaskelEnding up with still laggy display performance, no usb c dp compability and very often boot errors that say tat p2p-dev-wlp1s0f type 10 failed#asahi · 2026-01-02 21:02
lukaskelCloning fairydust branch and setting it up with its own defconf and adding asahi.config. Compiling is with usual make command. Afterwards I update grub with mkconfig and end up the new kernel. Weirdly the whole macbook (m1 pro) alr feels laggy at that point. Someone on reddit pointed out that the dtb is not correct, so I follow the asahi documentation and build stage 2 boot.bin with newly compiled m1n1, u-boot and the correct .dtb for my macboo#asahi · 2026-01-02 20:59
lukaskelCurrently experimenting with the fairydust kernel to see if usb c -> hdmi adapters for 4k 120hz displays like the LG C2 work. Sadly I keep stumbling upon issues. Maybe someone sees a major issue in my logic of fairydust branch setup. Would appreciate any help! Will just give a rough outline, so if anyone might have a clue, that'd be great! #asahi · 2026-01-02 20:57
lukaskelHey everone :)