#asahi · 2023-11-05 09:49
MichaelLongj`ey, sure. At time long time ago I did. I even remembered the arch wiki. But no matter what I've configured the gentoo varian of SDDM always irgnored my config and started a X11 session. I did not follow up on this.#asahi · 2023-11-05 09:48
j`eyamw: so maybe for you, enabling FB EFI will "fix" x11#asahi · 2023-11-05 09:48
j`eyMichaelLong: check the wiki link above, if you want to try it#asahi · 2023-11-05 09:47
j`eyyeah#asahi · 2023-11-05 09:47
MichaelLongj`ey, you mean in SDDM?#asahi · 2023-11-05 09:47
j`eyMichaelLong: but you should just try enable wayland anyway!#asahi · 2023-11-05 09:46
MichaelLongthx for the hints.#asahi · 2023-11-05 09:46
MichaelLongj`ey, amw: I've checked my kernel config and FB_EFI was missing. Initially I've exectly experienced what janneg described. Now with FB_EFI enabled I can see all kernel out and SDDM is loading/showing again.#asahi · 2023-11-05 09:39
amwj`ey: ok#asahi · 2023-11-05 09:38
amwOnly working kernel requires complete bindeb-pkg which takes a long time to buid everything...#asahi · 2023-11-05 09:38
amwj`ey: I've been trying to rebuild my kernel alone but it keeps falling through to initramdisk now very frustrating#asahi · 2023-11-05 09:38
j`eyamw: ok, try that kernel command line option first then, should be quick to see if that helps#asahi · 2023-11-05 09:36
amwActually CONFIG_FB_EFI is in all configs - must have muck'ed up my grep#asahi · 2023-11-05 09:36
j`eyMichaelLong: https://wiki.archlinux.org/title/SDDM#Running_under_Wayland#asahi · 2023-11-05 09:36
j`eyamw: could try https://termbin.com/2x1o and share dmesg after#asahi · 2023-11-05 09:35
MichaelLongI haven't followed the development in detail but I remember SDDM gained wayland support at some time? I'm running gentoo so I'll have to check the versions later#asahi · 2023-11-05 09:34
j`eysee before/after this message https://oftc.irclog.whitequark.org/asahi-dev/2023-10-08#32552389;#asahi · 2023-11-05 09:34
j`eyok, that looks like the same issue that janneg was seeing at some point#asahi · 2023-11-05 09:33
MichaelLongj`ey, probably, because of SDDM is not showing. I remember SDDM runs as X11, my KDE plasma environment with wayland.#asahi · 2023-11-05 09:32
j`eyMichaelLong: are you using X11?#asahi · 2023-11-05 09:31
MichaelLonghmm I have a similar issue with 6.5 after applying the 6.3 kernel config#asahi · 2023-11-05 09:28
amwj`ey: My working 6.4 kernel has CONFIG_FB_EFI but my failing 6.5 doesn't#asahi · 2023-11-05 09:20
j`eybut it's weird because we also have simpledrm that does that too#asahi · 2023-11-05 09:13
PaulFertserproperly yet.#asahi · 2023-11-05 09:12
PaulFertserFor more context, EFI FB is basically when the bootloader does everything needed to bring the display up and showing pictures and just passes the kernel information about the size, format and memory address where it's mapped to, no EFI Runtime Services interaction required, no dirty trickery at all. So in general it's worth having it as a fallback when Linux doesn't support the display hardware#asahi · 2023-11-05 09:11
j`eyamw: you can test if thats the issue with: initcall_blacklist=efifb_driver_init and make sure that error goes away#asahi · 2023-11-05 09:03
j`eyamw: that should be supported still. I got that error when I had the EFI FB driver enabled#asahi · 2023-11-05 04:45
amwIs there some magic apple-dart protection that no longer allows the allocation?#asahi · 2023-11-05 04:45
amwI believe it is this CONFIG_DRM_SIMPLE - drivers/gpu/drm/tiny/simpledrm.c code#asahi · 2023-11-05 04:43
amwYes I believe I am still trying to use the simple frame buffer set up before boot - is that no longer supported?#asahi · 2023-11-05 04:42
amwX11 working on 6.4 but failing on 6.5 - suspect it is related to this kernel error: simple-framebuffer bd58dc000.framebuffer: [drm] *ERROR* could not acquire memory range [??? 0xffff6e1d8629d580-0x2a5000001a7 flags 0x0]: -16#asahi · 2023-11-05 04:24
jmr2Conclusion for my recent issues (System rOS stuck @ 12.2.1 and missing SystemRecovery in iSCPreboot): idevicerestore (in revive mode, with the 14.1 files) fixed both without any data loss. YMMV.#asahi · 2023-11-04 22:59
Tramtristhopefully it comes in time then#asahi · 2023-11-04 22:56
j`eyTramtrist: the reason (from janne_g) is that sway doesnt implement v3 of the xdg_wm_shell protocol#asahi · 2023-11-04 22:33
Tramtristthat explains that i guess#asahi · 2023-11-04 22:33
Tramtristoh so uhh.. krunvm doesnt work in sway... #asahi · 2023-11-04 20:52
karpouziany asahi folks at the hackday conference?#asahi · 2023-11-04 20:27
ydaltonand only recently it was possible to get hdmi out working on those models #asahi · 2023-11-04 20:24
ydaltonas far as i understand it, the hdmi out on m2 mac mini is nothing like that on the m1 mac mini#asahi · 2023-11-04 20:23
svenor, well, maybe I pushed that dpaltmode.py at some point but that only works on t8103 with my display :D#asahi · 2023-11-04 20:23
ydaltonthat was hdmi out i think#asahi · 2023-11-04 20:22
svenno#asahi · 2023-11-04 20:22
ydaltonbut hold on, isn't dp alt mode a thing already on m1n1? #asahi · 2023-11-04 20:22
ydaltoninteresting, will be looking forward to when dp alt mode drops #asahi · 2023-11-04 20:21
ChaosPrincessyes#asahi · 2023-11-04 20:20
ydaltonm1#asahi · 2023-11-04 20:20
ydaltonbut not on the mac mini#asahi · 2023-11-04 20:20
ydaltonso on the m2 mac mini one of the display controllers can be either on the hdmi port or the thunderbolt ports#asahi · 2023-11-04 20:19
jannegnot on the m1 mac mini. they can be both used on the m2 mac mini when the hdmi port is not used#asahi · 2023-11-04 20:19
ChaosPrincesson m2 they can