marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | "Does XXX work yet?": https://alx.sh/fs | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-alt #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
zerdox has quit [Read error: Connection reset by peer]
zerdox has joined #asahi
zerdox has quit [Ping timeout: 480 seconds]
ivabus has joined #asahi
ivabus has quit [Ping timeout: 480 seconds]
capta1nt0ad has quit [Ping timeout: 480 seconds]
Guest5788 has quit []
vx has joined #asahi
vx is now known as Guest5798
zerdox has joined #asahi
overholts has joined #asahi
lawt2 has joined #asahi
xcpy0 has quit [Remote host closed the connection]
xcpy0 has joined #asahi
crabbedhaloablut has quit []
Guest5798 has quit []
vx has joined #asahi
vx is now known as Guest5807
atlashands has quit [Remote host closed the connection]
as400 has quit [Remote host closed the connection]
as400 has joined #asahi
Brainium has quit [Quit: Konversation terminated!]
capta1nt0ad has joined #asahi
zerdox has quit [Ping timeout: 480 seconds]
zerdox has joined #asahi
zerdox has quit [Ping timeout: 480 seconds]
zerdox has joined #asahi
kidplayer666 has quit [Quit: Connection closed for inactivity]
<jmr2>
Conclusion 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.
zerdox has joined #asahi
zerdox has quit [Ping timeout: 480 seconds]
capta1nt0ad has quit [Ping timeout: 480 seconds]
jmr2 has quit [Quit: Page closed]
<amw>
X11 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
<amw>
Yes I believe I am still trying to use the simple frame buffer set up before boot - is that no longer supported?
<amw>
I believe it is this CONFIG_DRM_SIMPLE - drivers/gpu/drm/tiny/simpledrm.c code
<amw>
Is there some magic apple-dart protection that no longer allows the allocation?
capta1nt0ad has quit [Remote host closed the connection]
capta1nt0ad has joined #asahi
ivabus has quit [Ping timeout: 480 seconds]
ivabus has joined #asahi
capta1nt0ad has quit [Ping timeout: 480 seconds]
zerdox has joined #asahi
zerdox has quit [Ping timeout: 480 seconds]
ivabus has quit [Remote host closed the connection]
ivabus has joined #asahi
zerdox has joined #asahi
ivabus has quit [Ping timeout: 480 seconds]
zerdox has quit [Ping timeout: 480 seconds]
crabbedhaloablut has joined #asahi
zerdox has joined #asahi
ciomtaur^ has quit [Ping timeout: 480 seconds]
ciomtaur^ has joined #asahi
zerdox has quit [Ping timeout: 480 seconds]
ivabus has joined #asahi
ivabus_ has joined #asahi
ivabus has quit [Ping timeout: 480 seconds]
chadmed has joined #asahi
ivabus_ has quit [Remote host closed the connection]
zerdox has joined #asahi
zerdox has quit [Ping timeout: 480 seconds]
capta1nt0ad has joined #asahi
zerdox has joined #asahi
frekko has joined #asahi
frekko has quit [Remote host closed the connection]
frekko has joined #asahi
<j`ey>
amw: that should be supported still. I got that error when I had the EFI FB driver enabled
zerdox has quit [Ping timeout: 480 seconds]
qyliss has quit [Quit: bye]
frekkson has joined #asahi
qyliss has joined #asahi
<j`ey>
amw: you can test if thats the issue with: initcall_blacklist=efifb_driver_init and make sure that error goes away
<PaulFertser>
For 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
<PaulFertser>
properly yet.
zerdox has joined #asahi
<j`ey>
but it's weird because we also have simpledrm that does that too
<amw>
j`ey: My working 6.4 kernel has CONFIG_FB_EFI but my failing 6.5 doesn't
zerdox has quit [Ping timeout: 480 seconds]
<MichaelLong>
hmm I have a similar issue with 6.5 after applying the 6.3 kernel config
<j`ey>
MichaelLong: are you using X11?
<MichaelLong>
j`ey, probably, because of SDDM is not showing. I remember SDDM runs as X11, my KDE plasma environment with wayland.
<j`ey>
ok, that looks like the same issue that janneg was seeing at some point
<MichaelLong>
I 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
<amw>
Actually CONFIG_FB_EFI is in all configs - must have muck'ed up my grep
<j`ey>
amw: ok, try that kernel command line option first then, should be quick to see if that helps
<amw>
j`ey: I've been trying to rebuild my kernel alone but it keeps falling through to initramdisk now very frustrating
<amw>
Only working kernel requires complete bindeb-pkg which takes a long time to buid everything...
chadmed has quit [Ping timeout: 480 seconds]
<amw>
j`ey: ok
ciomtaur^ has quit [Ping timeout: 480 seconds]
ciomtaur^ has joined #asahi
<MichaelLong>
j`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.
<MichaelLong>
thx for the hints.
<j`ey>
MichaelLong: but you should just try enable wayland anyway!
<MichaelLong>
j`ey, you mean in SDDM?
<j`ey>
yeah
<j`ey>
MichaelLong: check the wiki link above, if you want to try it
<j`ey>
amw: so maybe for you, enabling FB EFI will "fix" x11
flom84 has joined #asahi
<MichaelLong>
j`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.
<j`ey>
I see, and you have a workaround now at least
flom84 has quit []
zerdox has joined #asahi
<MichaelLong>
I would be more invested into checking those irregularities but at the moment I'm not yet using the linux installation in a serious manner :/
<PaulFertser>
Oh hm, the code actually says otherwise.
flom84 has joined #asahi
Guest5807 has quit []
<PaulFertser>
No, I was reading it right. If there's no error creating DRM device then it just proceeds to unlock the mutex and exit the function, so the efifb device isn't created.
vx has joined #asahi
vx is now known as Guest5840
<j`ey>
are you sure sysfb_create_simplefb is creating a DRM device?
<amw>
j`ey: I'm doing the full bindeb-pkg thingie - Sigh
<j`ey>
it calls: sysfb_set_efifb_fwnode(pd);
<PaulFertser>
It's supposed to do that according to 8633ef82f101c040427b57d4df7b706261420b94 commit message.
zerdox has quit [Ping timeout: 480 seconds]
<j`ey>
I don't understand the code, but I was definitely getting an EFI FB before simpledrm
<j`ey>
but anyway it seems that EFI FB works with X11 whereas simpledrm might no
<j`ey>
t
<PaulFertser>
j`ey: sysfb_create_simplefb creates platform_device_alloc("simple-framebuffer", 0); while the other path creates name = "efi-framebuffer"; so the nodes end up being different and should be handled by different drivers.
<j`ey>
ah right
<j`ey>
well I dont want to start debuggign it again, but I'm not sure what happened for me
<PaulFertser>
Indeed not worth it when there exists a real great driver.
<MichaelLong>
for what it's worth I'm seeing: [ 0.037309] simple-framebuffer 107d36f2880.framebuffer: [drm] *ERROR* could not acquire memory range [io 0xffff00000e0f7700-0xffff800080ad17d8 flags 0xffff0007ce1da760]: -16 followed by [ 0.037361] simple-framebuffer: probe of 107d36f2880.framebuffer failed with error -16 in my dmesg output.
<j`ey>
amw: and x11 works?
<amw>
Yes - it's all working again... - beautiful
<j`ey>
confusing
<amw>
From my earlier dmesg - the first FB works ok and the 2nd fails and I guess screws it up.
<amw>
I have to go now - so I can debug some more later - but thanks - greatly - this has been a real pain for me - Yeah!
<j`ey>
but simpledrm should just not do anything in that case
chadmed has joined #asahi
chadmed has quit [Remote host closed the connection]
flom84 has quit [Quit: Leaving]
chadmed has joined #asahi
sefidel has quit [Remote host closed the connection]