#
#asahi-alt · 2024-01-15 13:24
j`eyok, so the blacklist isn't working / the module is built in
#asahi-alt · 2024-01-15 13:23
u154ss@cy8aer - I would have thought so. See - https://unix.stackexchange.com/questions/676201/modprobe-blacklist-not-working-debian-11. However the GPU is still being probed - see photo - https://ibb.co/HdCJn0w
#asahi-alt · 2024-01-15 13:09
cy8aerAnd then a module "asahi" is loaded.
#asahi-alt · 2024-01-15 13:09
cy8aerAhem "CONFIG_DRM_ASAHI=m" of course
#asahi-alt · 2024-01-15 13:09
cy8aerI just checked it, Glanzmann like kernels are able to work with "CONFIG_DRM_ASAHI=y".
#asahi-alt · 2024-01-15 12:52
cy8aerexcept there is a boot option for the kernel to ignore it?
#asahi-alt · 2024-01-15 12:51
cy8aerit is in kernel.
#asahi-alt · 2024-01-15 12:45
u154ss@all on Glanzmann's Debian initial image, the asahi module in built in-stream (CONFIG_DRM_ASAHI=y), so the blacklist exercise will not work anyway or?
#asahi-alt · 2024-01-15 12:11
u154ss@j'ey did so.
#asahi-alt · 2024-01-15 12:06
j`eymight need the blacklist *and* nomodeset.. but im just randomly guessing :)
#asahi-alt · 2024-01-15 12:06
j`eywell that's weird then :) no idea why it's crashing, other reports from the internet seemed to be related to the GPU driver..
#asahi-alt · 2024-01-15 12:05
j`eyu154ss: and dmesg | grep gpu shows nothing?
#asahi-alt · 2024-01-15 12:05
u154ss@j'ey, I an only check (lsmod) from Debian recovery. There is no asahi loaded.
#asahi-alt · 2024-01-15 11:58
j`eyu154ss: can you check that the blacklist actually worked, and the module isnt loaded
#asahi-alt · 2024-01-15 11:50
u154ss@j'ey, the blacklist thing did not work. Still the same, segfault. Console inaccessible, cursor on top LH corner - reboot into Debian recovery (single mode) with limited possibilities.
#asahi-alt · 2024-01-15 11:43
leioI would also install debug symbols package for Xorg
#asahi-alt · 2024-01-15 11:40
j`eyok
#asahi-alt · 2024-01-15 11:40
u154ss@j'ey methinks asahi.
#asahi-alt · 2024-01-15 11:40
u154ss@j'ey no sign of drm_asahi anywhere.
#asahi-alt · 2024-01-15 11:39
j`eyif its just asahi or drm_asahi, not sure
#asahi-alt · 2024-01-15 11:39
j`eydouble check the module name
#asahi-alt · 2024-01-15 11:38
u154ss@j'ey to reiterate blacklist asahi in /etc/modprobe.d/drm_asahi.conf?
#asahi-alt · 2024-01-15 11:37
j`eyyeah
#asahi-alt · 2024-01-15 11:36
u154ssThis is what is loaded on the M1 - appledrm 49152 1 apple_dcp 114688 1 appledrm drm_dma_helper 49152 2 appledrm,apple_dcp root@debian:/Transit# lsmod |grep asahi asahi 1245184 0
#asahi-alt · 2024-01-15 11:36
u154ssblacklist /etc/modprobe.d/drm_asahi.conf?
#asahi-alt · 2024-01-15 11:34
j`eyyou could try blacklist the GPU module (DRM_ASAHI) from loading
#asahi-alt · 2024-01-15 11:33
j`eyok, asahi gpu driver doesnt explicitly call drm_firmware_drivers_only, so maybe the GPU is still in use
#asahi-alt · 2024-01-15 11:31
j`eyu154ss: do you have the dmesg for the boot with nomodeset?
#asahi-alt · 2024-01-15 11:29
u154ss@leio/j'ey with nomodeset set, no difference, still segfaults.
#asahi-alt · 2024-01-15 11:24
u154ss@all and the appropriate binary - https://filebin.net/u5vw5gcca3plfw0o
#asahi-alt · 2024-01-15 11:12
u154ss@all here is the coredumpctl text - https://paste.debian.net/1304137/
#asahi-alt · 2024-01-15 10:43
leiodon't think GPU can draw on actual screen without DCP, just offscreen?
#asahi-alt · 2024-01-15 10:43
j`eyjanneg: I guess that `nomodeset` doesn't actually disable GPU rendering for us, just DCP..
#asahi-alt · 2024-01-15 10:43
leiook, guess the coredump history is gone then :)
#asahi-alt · 2024-01-15 10:43
u154ss@leio, I scrubbed the installation and put fedora back on, subsequently wiped that too. Things are virginal at the moment. I will have to start from scratch again using Glanzmann's installer.
#asahi-alt · 2024-01-15 10:42
leio(or process name instead of PID, I just don't recall it after not using Xorg for 3+ years or know what it is for sure on debian)
#asahi-alt · 2024-01-15 10:42
leioor debug instead of info to enter debugger, though info should give the crashing threads backtrace too
#asahi-alt · 2024-01-15 10:41
leiocoredumpctl info <PID of last Xorg crash>
#asahi-alt · 2024-01-15 10:41
leionote that last Xorg crash, then something like
#asahi-alt · 2024-01-15 10:41
leiocoredumpctl
#asahi-alt · 2024-01-15 10:41
leiothe coredump is probably still there and can check it out unless you had disk too full and it had to quickly clean it up or you changed binaries.
#asahi-alt · 2024-01-15 10:41
u154ss@all No, I am not a developer, I will have to get my head around these things. I will have to reproduce this again, will take some time..
#asahi-alt · 2024-01-15 10:39
leioyou should be able to just get a gdb backtrace from there (and maybe confirm the stack is nuts and no useful backtrace there, but who knows)
#asahi-alt · 2024-01-15 10:38
leiou154ss: as it's a segfault, have you checked with coredumpctl?
#asahi-alt · 2024-01-15 10:38
j`ey(for CPU changes, that's why I suggested the arm64.nobti option)
#asahi-alt · 2024-01-15 10:38
j`eyproblem is that there's not much to gone on really. I mean you could try boot with `nomodeset` that will confirm it's the GPU kinda
#asahi-alt · 2024-01-15 10:38
u154ss@j'ey there we have it...
#asahi-alt · 2024-01-15 10:37
j`eynot much for the CPU, not sure about the GPU, there is definitely some changes
#asahi-alt · 2024-01-15 10:36
u154ss@j'ey understand, but I am loath to change to fedora and/or kde. Not my thing. Is the instruction set so different between the M1 and M2?
#asahi-alt · 2024-01-15 10:34
j`eybut not sure if anyone will look at if it's only affecting X11..

plus ›