15:21 <cy8aer> @Glanzmann: your 6.3.0 #9 does not look as stable as the last one you published: I now had two situations of reboot when closing the lid (and with that set s2idle).

15:21 <cy8aer> (deb of course)

19:47 <qdot> chadmed: Yeah - that's what I'm doing, CONFIG_DRM_APPLE=m is selected, appledrm is loaded as a module.. found my issue, X11 is entirely unsupported and the default setup has sddm running through X11.. dbus-run-session startplasma-wayland worked for me with acceleration, now to figure out a canonical way to have a display mananger.

19:50 <qdot> I swear Asahi ALARM runs sddm - are we running 0.20 via wayland, or something more unusual there?

19:50 <ChaosPrincess> alarm runs sddm via X, but kde via wayland

19:51 <qdot> Hmm.. any weird way to get X running on DRM_APPLE=m ? I'm getting " Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices

19:52 <qdot> Or is it some wayland/Xwayland/sddm stack?

19:52 <ChaosPrincess> what are you running

19:52 <ChaosPrincess> what distro

19:53 <qdot> Gentoo - got fed up with ALARM's partial arm64 support.

19:53 <ChaosPrincess> sec, let me send you my .config

19:54 <ChaosPrincess> https://paste.bingner.com/paste/u6vvo

20:02 <qdot> Hmm.. 6.3.0? Is that merged in somewhere? Or is it just asahi git-tip? I don't see any tags above 6.2.12 on github?

20:03 <ChaosPrincess> its asahi-wip, but you shouldnt run it

20:03 <ChaosPrincess> can make syncconfig downgrade? i dont remember

20:04 <qdot> It might.. hopefully without hiccups.

20:06 <qdot> The diff is pretty huge to whatever I'm running (which is -edge from ALARM after syncconfig), but that's expected

20:06 <ChaosPrincess> yea, its a manually configured one with a lot of useless stuff set to N

20:07 <qdot> Understandable, when I was building it before I was wondering why these were set to M in the first place..

20:08 <ChaosPrincess> alarm distro kernel, who knows what hardware you end up running it on

20:10 <qdot> Hmm.. it looks like your config doesn't have CONFIG_DRM_ASAHI set..

20:10 <qdot> (I had it working reasonably well without DRM, but wanted to add mesa acceleration)

20:11 <ChaosPrincess> right, that one is annoying since it gets randomly reset if you dare run make menuconfig w/o rust in PATH

20:13 <qdot> Yeah, it seems it got switched off in the file you posted..

20:14 <jannau> are we shipping https://github.com/AsahiLinux/PKGBUILDs/blob/main/asahi-configs/30-modeset.conf in gentoo?

20:14 <ChaosPrincess> probably?

20:14 <yuka> I still have issues with usb devices not being recognized after I re-plug them after boot. This worked fine on the 5.19 based kernel and broke when upgrading to the 6.1 based kernel.

20:17 <jannau> ChaosPrincess: there are appropiate dev-util/bindgen and dev-lang/rust versions in portage

20:17 <qdot> jannau: Don't think so?

20:18 <ChaosPrincess> i believe that there was an incorrect bindgen when i first set it up and so i have a setup with a system rust for whatever needs it and a rustup rust/bindgen for kernel

20:19 <jannau> qdot: yes, it's not in asahi-scripts and no other package looks likely. copy it to /etc/X11/xorg.conf.d/30-modeset-apple.conf and I hope the X issues are solved

20:21 <qdot> jannau: bingo - it worked!

20:21 <jannau> yuka: you might want to update to 6.2-asahi-11 or -12, although I doubt that resolves your issue

20:21 <qdot> jannau: thanks!

20:22 <jannau> I'm only aware of the inverse problem. some usb-device do not work if they are plugged during booting

20:23 <jannau> yuka: please tell us more about your setup

20:26 <yuka> sorry my wording was inaccurate.

20:26 <yuka> > I'm only aware of the inverse problem. some usb-device do not work if they are plugged during booting

20:26 <yuka> > that's exactly what I meant

20:26 <yuka> usb devices not being recognized _until_ I re-plug them after boot

20:27 <yuka> I am on asahi-6.2-11

20:28 <yuka> the same issue that bcrumb reported on 2022/12/08 in #asahi

20:29 <yuka> bcrumb and I both reported it when it first came up, but since then I have kept upgrading kernels and it is still there

20:31 <yuka> > bcrumb: yeah, so from rc6 5-1 to rc8 3-1; was the upgrade; scripts 1129 1206

20:31 <yuka> > sven: ugh…. This might be tipd probing before dwc3 and atcphy and firing off the plug event into nowhere

20:33 <jannau> I think nobody has looked into it since then. the usb-c setup is unfortuantely complicated and consists of components requiring special handling

21:09 <yuka> okay, thanks