#
…

2024-01-15

00:57kidplayer666 has quit [Quit: Connection closed for inactivity]
01:43opticron has quit [Ping timeout: 480 seconds]
01:56opticron has joined #asahi-alt
02:32JayBeeFOSS has quit [Ping timeout: 480 seconds]
02:33JayBeeFOSS has joined #asahi-alt
03:55aead has joined #asahi-alt
04:10aead has quit [Remote host closed the connection]
04:14aead has joined #asahi-alt
04:58r0ni has quit [Write error: connection closed]
05:23possiblemeatball has quit [Quit: Quit]
07:47kdb424 has quit [Quit: The Lounge - https://thelounge.chat]
07:48kdb424 has joined #asahi-alt
08:00kujeger has quit [Remote host closed the connection]
08:53kujeger has joined #asahi-alt
09:05hightower2 has quit [Ping timeout: 480 seconds]
09:07u154ss has joined #asahi-alt
09:10u154ssM2-Mini-Debian-XFCE-libunwind-OSLookupColor-+0x188 again, still noboby with bright ideas/pointers?
09:10u154ssnoboby = nobody.
09:36kidplayer666 has joined #asahi-alt
09:55tobhelibunwind was broken with 16k pages, but that was a while ago
10:07u154ss@tobhe thanks. Glanzmann originally reported this in December 2022. I am told that even though libunwind appears in the xorg.log, it is NOT in fact libunwind, it is something else...
10:08u154ss@tobhe, I uploaded logs on Saturday.
10:11j`eyu154ss: the logs have expired btw
10:19u154ss@j'ey that is a pity. The backtrace is still there - https://filebin.net/f753xwi6cz3bf2ae
10:20j`eyu154ss: that's a binary file?
10:20u154ss@j'ey yes.
10:21j`eynot sure what Im meant to do with that
10:21j`eyor is it a coredump?
10:22u154ss@j'ey and the tail end of the xorg log is here - https://ibb.co/JKmJpsN
10:22svenisn't that binary just the xorg executable?
10:23j`eyoh, I guess so we could look up the address or something..
10:24j`eysomeone here had the same issue, not on m2 tho https://forum.pine64.org/showthread.php?tid=8915
10:25j`eymaybe a mesa issue then?
10:26u154ss@all most likely. You are right, it is the xorg executable. The second last line of the xorg log states that I should look for a log, I am not sure where though. As stated already, Fedora 39/KDE Plasma works with the M2 Mini. All of the Mesa stuf is release 24.x I my (Debian) environment, the Mesa stuf is at release level 23.x
10:27u154ssI am not sure whether that has an influence on things though.
10:27j`eyyeah because KDE plasma is wayland :)
10:27u154ssj'ey I know.
10:28j`eyu154ss: are you using the exact same versions for mesa on the m1 and m2 machine?
10:28j`eyit seems that OsLookupColor is a place that crashes a lot, according to google
10:29u154ssAgain, on the M1 Mini everything works (Debian/XFCE). Using the (exact) same installation procedure on the M2 Mini - see above :(
10:29leiou154ss: I presume it's on systemd, so journalctl should have stuff. I don't know under which unit file for you to filter for it, but you can scroll through the whole log of the boot with journalctl -b0 or just reproduce and look immediately
10:29leio(xorg log)
10:29leiobut I think you had something already shared to that effect?
10:29j`eyhttps://bugzilla.redhat.com/show_bug.cgi?id=957915#c24 heh 'OsLookupColor is just a default function the backtracer seems to pick up when it craps itself out.'
10:30u154ss@j'ey "are you using the exact same versions for mesa on the m1 and m2 machine?" - yes. I am using Debian testing in both cases.
10:34j`eyyou might have to try run it in gdb or.. file a bug on GH, in case it is a GPU driver issue
10:34j`eybut not sure if anyone will look at if it's only affecting X11..
10:36u154ss@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?
10:37j`eynot much for the CPU, not sure about the GPU, there is definitely some changes
10:38u154ss@j'ey there we have it...
10:38j`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
10:38j`ey(for CPU changes, that's why I suggested the arm64.nobti option)
10:38leiou154ss: as it's a segfault, have you checked with coredumpctl?
10:39leioyou 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)
10:41u154ss@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..
10:41leiothe 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.
10:41leiocoredumpctl
10:41leionote that last Xorg crash, then something like
10:41leiocoredumpctl info <PID of last Xorg crash>
10:42leioor debug instead of info to enter debugger, though info should give the crashing threads backtrace too
10:42leio(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)
10:43u154ss@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.
10:43leiook, guess the coredump history is gone then :)
10:43j`eyjanneg: I guess that `nomodeset` doesn't actually disable GPU rendering for us, just DCP..
10:43leiodon't think GPU can draw on actual screen without DCP, just offscreen?
11:12u154ss@all here is the coredumpctl text - https://paste.debian.net/1304137/
11:24u154ss@all and the appropriate binary - https://filebin.net/u5vw5gcca3plfw0o
11:29u154ss@leio/j'ey with nomodeset set, no difference, still segfaults.
11:31j`eyu154ss: do you have the dmesg for the boot with nomodeset?
11:33j`eyok, asahi gpu driver doesnt explicitly call drm_firmware_drivers_only, so maybe the GPU is still in use
11:34j`eyyou could try blacklist the GPU module (DRM_ASAHI) from loading
11:36u154ssblacklist /etc/modprobe.d/drm_asahi.conf?
11:36u154ssThis 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
11:38u154ss@j'ey to reiterate blacklist asahi in /etc/modprobe.d/drm_asahi.conf?
11:39j`eydouble check the module name
11:39j`eyif its just asahi or drm_asahi, not sure
11:40u154ss@j'ey no sign of drm_asahi anywhere.
11:40u154ss@j'ey methinks asahi.
11:43leioI would also install debug symbols package for Xorg
11:50u154ss@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.
11:58j`eyu154ss: can you check that the blacklist actually worked, and the module isnt loaded
12:05u154ss@j'ey, I an only check (lsmod) from Debian recovery. There is no asahi loaded.
12:05j`eyu154ss: and dmesg | grep gpu shows nothing?
12:06j`eywell that's weird then :) no idea why it's crashing, other reports from the internet seemed to be related to the GPU driver..
12:06j`eymight need the blacklist *and* nomodeset.. but im just randomly guessing :)
12:11u154ss@j'ey did so.
12:18kidplayer666 has quit [Quit: Connection closed for inactivity]
12:45u154ss@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?
12:51cy8aerit is in kernel.
12:52cy8aerexcept there is a boot option for the kernel to ignore it?
12:54eiln has joined #asahi-alt
13:09cy8aerI just checked it, Glanzmann like kernels are able to work with "CONFIG_DRM_ASAHI=y".
13:09cy8aerAhem "CONFIG_DRM_ASAHI=m" of course
13:09cy8aerAnd then a module "asahi" is loaded.
13:18kidplayer666 has joined #asahi-alt
13:23u154ss@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
13:24j`eyok, so the blacklist isn't working / the module is built in
13:25j`eyso it could still be related to the GPU drive
13:26u154ss@j'ey correct. Glanzmann's asahi is in-stream i,e, CONFIG_DRM_ASAHI=y. That is his latest and greatest (newest). Strangely, all of this works on the M1 Mini.
13:26j`eyu154ss: are you building the kernel yourself, or using a .deb?
13:30u154ss@j'ey on the M1 Mini, I roll my own kernels. On the M2 Mini, I am not in the position to do anything, as things die before I can even get started. Om my M1 Mini, I still have the same driver (old timestamp??) - Initialized asahi 0.0.0 20220831 for 206400000.gpu on minor 1, but things work.
13:32u154ss@j'ey, i.e. I am using Glanzmann's insteller (tg.st/d). It has always word, at least for the M1 Mini.
13:32j`eyyou could build the kernel on another machne and copy it across
13:32j`eyor try install xfce on fedora, see if it repros there
13:35u154ss@j'ey could do, but a bit of work involved. As I stated earlier, the mesa stuff is up to date on Fedora (maybe taking the M2 requirements/specifics into account), not so with Debian testing.
13:40u154ssAgain, speculation on my part..
13:41u154ssword = worked; insteller = installer. All thumbs today.
13:47leiou154ss: CONFIG_DRM_ASAHI is not supported, it doesn't bring up HDMI output for example.
13:47leiou154ss: sorry, I meant built-in is not supported; it needs to be a module
13:48j`eyleio: are you thinking of DRM_APPLE?
13:49leioI am, I'm referring to whatever CONFIG_DRM for apple was there and was just repeating from above. I wasn't aware there's two of them
13:49leioor am I?
13:49leioI'm scrolling back history of channel where it was stated, I should use the web logs instead :)
13:50j`eyleio: APPLE is DCP ASAHI is GPU
13:51u154ss@j'ey/leio no, CONFIG_DRM_ASAHI=y is what is delivered in Glanzmann's .config. I know things have changed. On this machine (M1), I have CONFIG_DRM_ASAHI=m. I believe Glanzmann built his latest offering in October '23.
13:53leiook, DRM_APPLE is what has to be module indeed, unsure about DRM_ASAHI
13:53leiosorry for the mixup
13:54leio(can't we rename these to be clearer?)
13:54u154ss@leio Glamzmann's .config has CONFIG_DRM_APPLE=y
13:55u154ssOn this machime (m1 Mini), I have CONFIG_DRM_APPLE=m
13:56leiook, that's good, with DRM_APPLE=y at least on M2 Ultra there's no HDMI output, unsure if affects m1 mini
14:11u154ssAs per j'ey's suggestion, I have installed (again :() fedora fc39 on the M2 Mini, also XFCE (4.19) - things work. What does that tell us?
14:11u154ss4.19 = 4.18
14:11j`eyI guess that tells us that there isn't a GPU driver bug?
14:11j`eythat it could be mesa
14:12j`eyI mean, at least it's a debian issue, not asahi directly?
14:16u154ss@j'ey it would seem so. As the M2 has not been as well tested as the M1 (Desktop Environments etc.), things will happen... Again, I prefer Debian and a very lean .config :)
14:17j`eyand Xorg doubly so
14:17j`ey(less tested)
14:19j`eyso yeah, next think would be to try upgrade mesa
14:19mpsjust note, xorg works fine with asahi kernel
14:22u154ss@mps depends on the machine, I would have thought.
14:23j`eyu154ss: could try another Xorg WM
14:23j`eyor or try start it from the terminal, not lightdm
14:26u154ss@all I know Glanzmann has a mesa build script - https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/commit/798a6b5d4be24b4df40e90ce7574f6161b901b79 I am not sure how actual that is. That said, fedora kde plasma and even XFCE is a pleasure for the peepers!
14:35kraem has quit [Remote host closed the connection]
14:40kraem has joined #asahi-alt
14:52kraem has quit [Remote host closed the connection]
14:54kraem has joined #asahi-alt
15:16u154ss has quit [Remote host closed the connection]
15:58kidplayer666 has quit [Quit: Connection closed for inactivity]
16:08eiln has quit [Ping timeout: 480 seconds]
16:20kujeger has quit [Remote host closed the connection]
16:39kujeger has joined #asahi-alt
16:58tobhe has quit [Remote host closed the connection]
17:05tobhe has joined #asahi-alt
17:18possiblemeatball has joined #asahi-alt
17:51kidplayer666 has joined #asahi-alt
18:11JTL has quit [Ping timeout: 480 seconds]
18:18zerdox has joined #asahi-alt
18:19zerdoxchadmed: ive opened a pr. make and cmake are now under dev-build/
18:29chadmed has quit [Quit: Konversation terminated!]
18:30chadmed has joined #asahi-alt
18:31chadmed has quit []
18:31chadmed has joined #asahi-alt
18:32chadmed has quit []
18:33chadmed has joined #asahi-alt
18:48kujeger has quit [Remote host closed the connection]
18:48kujeger has joined #asahi-alt
19:39qyliss has quit [Quit: bye]
20:53qyliss has joined #asahi-alt
23:23zerdox has quit [Read error: Connection reset by peer]
23:23zerdox has joined #asahi-alt
…