#
…

2024-01-21

00:08mkurz has joined #asahi-alt
00:39eiln has quit [Ping timeout: 480 seconds]
01:05hightower3 has joined #asahi-alt
01:09maxg_ has joined #asahi-alt
01:10maxg_ has quit []
01:11maxg_ has joined #asahi-alt
01:12hightower2 has quit [Ping timeout: 480 seconds]
01:30maxg_ has quit [Remote host closed the connection]
01:53kloenk has quit [Remote host closed the connection]
01:54kloenk has joined #asahi-alt
05:17RoundDuckKira has quit [Quit: RoundDuckKira]
05:17RoundDuckKira has joined #asahi-alt
06:01eiln has joined #asahi-alt
06:08RoundDuckKira has quit [Quit: RoundDuckKira]
06:08RoundDuckKira has joined #asahi-alt
06:11possiblemeatball has quit [Quit: Quit]
11:25kidplayer666 has joined #asahi-alt
11:41u154ss has joined #asahi-alt
11:50u154ssStill on my ailing M2 Mini again.. Did a fresh install of Debian (Glanzmann) with a minimal flavour - xinit, blackbox, lightdm and terminator - still the same Xorg error(s) as reported last week. Full logs - xorg - https://paste.debian.net/1304797/ dmesg - https://paste.debian.net/1304798/ journalctl - https://paste.debian.net/1304799/, https://paste.debian.net/1304800/ and https://paste.debian.net/1304801/
11:52u154ssI know this is a bother, but I would appreciate any bright ideas.
11:58leiofeels like something in DRI2 stuff is messing up memory badly, hitting a crash and then backtrace is just gibberish and nonsense
11:59leiodid wayland work?
12:01u154ss@leio as reported previously, on the M2 Mini, Fedora/KDE Plasma (Wayland) works. Fedora(XFCE) works. Debian more-or-less-minimal fails, as does Debian/XFCE - same errors.
12:07leioI was asking about wayland on that debian install
12:13u154ss@leio No, I do not even get that far.
12:15u154ss@leio as my preferred DE is XFCE, wayland wil not be relevant is my case anyway.
12:21u154sswil not be relevant is my case anyway = will not be relevant in my case anyway.
12:38jacksonchen666 has quit [Quit: WeeChat 4.1.2]
12:52leioit is relevant for figuring out what is wrong
12:53leioas-is it seems like we don't even know if it's Xorg-specific or not
12:57j`eyyeah trying wayland seems like a good idea
12:57j`eythat's an older kernel, 6.5, maybe there's an issue with that and the mesa you have
13:08u154ss has quit [Remote host closed the connection]
13:28u154ss has joined #asahi-alt
13:29mkurz has quit [Ping timeout: 480 seconds]
13:30u154ssUpdate - just tried Debian/Gnome (Wayland-ready) on the M2 Mini. Same results - backtrace with offset 0x1070000051e in Xorg.0.log. Bah!
13:32j`eyis that still with lightdm? if that's gdm maybe gdm is still X11 based
13:34u154ss@j'ey I installed Gnome using tasksel. The DM will be whatever Gnome uses for default. I do not think it is Lightdm. GDM most likely.
13:35j`eypresumably xorg if xorg crahses
13:37u154ss@j'ey, I will have to port the whole build chain from the M1 Mini to the M2 Mini and try and build a 6.6.x kernel. The stuff from Glanzmann is from November 2023.
13:38j`eydunno the easiest way to get a full wayland DE+login manager, maybe KDE
13:39u154ss@j'ey Gnome is supposed to be "ready", I could try KDE though.. will take some time.
13:39j`eyseems that GDM itself is using xorg, even if gnome is using wayland
13:40u154ss@j'ey what a f**king mess.
13:40u154sswill report back.
13:44leioGDM uses wayland
13:44leiounless it's a hybrid nvidia card or some such
13:44leioin fact GDM can only start wayland sessions (including GNOME itself) when GDM itself is using wayland - if it uses Xorg, it only allows choosing xorg sessions
13:44leiotesting GDM and GNOME in Xorg doesn't really give any additional debugging information here
13:45leioit falling back to Xorg instead of Wayland may be a symptom; journal might tell something.
13:45leioi.e. wayland crashes too, fallbacks to Xorg, that crashes too, and you see just the Xorg crash but should be looking at the wayland using one too
13:46leio(GDM uses gnome-shell to draw the UI; this shuts down on timeout when the active VT isn't on GDM to save resources, but only with wayland)
13:49u154ss@all starting from scratch again, this time with Debian/KDE. I am not sure what version of KDE debian will pull from the repos though. Surely not as "polished" as Fedora though.
13:54KxCORP has quit [Quit: Bye!]
13:55KxCORP has joined #asahi-alt
13:56KxCORP has quit []
13:58KxCORP has joined #asahi-alt
14:01KxCORP has quit []
14:02KxCORP has joined #asahi-alt
14:20u154ss@all The Debian/KDE install did not work either. Strangely, Xorg.0.log has the same error text and offset value as my previous efforts. I took a photo from the recovery console - https://ibb.co/DGGZrfc
14:23leioYou shouldn't even have a Xorg.0.log for wayland testing though?
14:25leiodon't start a DE as root; if you want to start it from command line instead of something like sddm, you may need to take care of many things manually like I see a struggle in the photo
14:25u154ss@leio would have thought so, yes.
14:26leiosomething like `dbus-launch --exit-with-session startplasma-wayland` maybe, but I haven't used that ever
14:26possiblemeatball has joined #asahi-alt
14:26leioas NOT root.
14:30u154ss@leio whether with Debian/XFCE or Debian/DKE, I do not even get as far enough to login with another userid.
14:31u154ssDKE = KDE.
14:32j`eyyou can use the 'su' command to change user from the recovery shell to try that manuallly
14:32u154ss@j'ey have tried already.
14:32leioor disable the desktop manager service in the rescue shell and boot into proper system
14:32leiodidn't realize that's at play here
14:45u154ss@leio from the rescue console, I can find no references to kde or plasma using systemctl and grepping.
14:52u154ss@leio no references to sddm using systemctl.
14:53u154ss@leio there is also no dbus-launch binary on this system.
14:56u154ss@leio https://packages.debian.org/sid/dbus-x11 is where this binary is found, but as I have to network in the recovery console, I am snookered here.
14:57leioI don't think you see sddm with just `systemctl` as it's not started due to rescue session
14:57leiou154ss: thus look at `systemctl list-unit-files` maybe
14:57leio`dbus-run-session -- startplasma-wayland` then maybe; or maybe it's just not working because even system dbus session isn't working due to rescue shell
14:59leiomaybe `systemctl disable sddm` will tell you that it removes a symlink and then it shouldn't start after reboot to normal mode
15:01leio(as in, maybe startplastma-wayland already would take care of the user dbus session that dbus-run-session/dbus-launch concern itself with, but the problem is elsewhere with dbus, e.g. lacking system bus if this is a /bin/bash rescue shell)
15:03j`eyor sudo systemctl set-default multi-user.target, to boot to a tty
15:07u154ss@all back in a few mins.
15:11hightower3 has quit [Ping timeout: 480 seconds]
15:21u154ss@j'ey systemctl set-default multi-user.target - am at a console now.
15:29u154ss@all photo - https://ibb.co/12kXB8p something amiss.
15:31hightower2 has joined #asahi-alt
15:52u154ss has quit [Remote host closed the connection]
16:07jacksonchen666 has joined #asahi-alt
17:08kidplayer666 has quit [Quit: Connection closed for inactivity]
17:10jacksonchen666 has quit [Quit: --help]
17:32mkurz has joined #asahi-alt
18:11JayBeeFOSS has quit [Ping timeout: 480 seconds]
18:12JayBeeFOSS has joined #asahi-alt
18:51Burger has joined #asahi-alt
18:51leiodon't use dbus-launch, as you found it's X11-specific; use dbus-run-session then, if it's even needed. Not saying that's your problem - doesn't look like it
18:52leiomight as well just try weston or something to start with
18:52leiooh, they aren't here right now
19:16kidplayer666 has joined #asahi-alt
22:54maxg_ has joined #asahi-alt
23:01maxg_ has quit [Quit: maxg_]
23:01maxg_ has joined #asahi-alt
23:26kidplayer666 has quit [Quit: Connection closed for inactivity]
23:30maxg_ has quit [Quit: maxg_]
…