00:16 <steev> and sent... though b4 wasn't happy with my msmtp setup, and i didn't feel like debugging it, so just sent via b4 and looks like it sent... oddly

00:23 <bamse> steev: everything has moved since i looked at it last...

00:24 <steev> i think i just need to re-set-up msmtp

00:24 <steev> ohhh

00:24 <steev> i bet i know what it is

00:24 <steev> i was doing it from ssh and my key can't be used without being at the physical keyboard

04:04 <bamse> steev: db845c does not seem to come back after s2idle either...

04:08 <bamse> yes, it does indeed go belly-up when it's time to resume

04:29 <steev> that's with your dp patches applied or without?

04:30 <bamse> either way on c630, and stock v6.6 on db845c

04:34 <steev> hm

04:34 <steev> mine definitely does with https://github.com/steev/linux/tree/c630-linux-6.6.y and https://paste2.org/pMmHByHm as my kernel config

04:37 <bamse> does work, or does crash?

04:37 <steev> i'm able to suspend and resume from suspend

04:40 <steev> Not the greatest video in the world but https://usercontent.irccloud-cdn.com/file/7FuoyGlX/IMG_1639.MP4

04:40 <bamse> steev: but you have so many patches in your tree

04:41 <steev> the c630 specific ones are the top ~9

04:41 <steev> 8

04:42 <steev> that's basically what we run on x13s+my 8 c630 patches

04:43 <steev> it's only 102 patches :P

04:44 <bamse> i have 0 patches on x13s, and 3 on c630

04:45 <steev> fwiw, minus the 8 for c630, i'm only showing 58 outstanding patches against next for the x13s

04:45 <steev> and iirc most of those are config changes

04:47 <steev> venus, a couple asoc, usb bits, and then the... pm8008, which i guess is for the camera, which is still pretty wip

04:57 <steev> Going back to just the 8 specific to c630

05:04 <steev> bamse: https://github.com/steev/linux/tree/c630-linux-6.6.y-8 this also works for me to suspend and resume

10:46 <bryanodonoghue> bamse steev - on debian sid as at yesterday and this kernel based on steev 6.5.1 https://git.codelinaro.org/bryan.odonoghue/kernel/-/commits/65a30636ef2bbf5d0cd86a3b649687f96a13885e

10:46 <bryanodonoghue> I get both ports working with kde plasma, lxqt and sway

10:47 <bryanodonoghue> but definitely some "funky" behaviour with gdm - constantly restarting

10:47 <bryanodonoghue> sddm doesn't bring up the second display unless it was already up

10:47 <bryanodonoghue> and per brian massey's discussion gnome shell crashes all over the place

10:48 <bryanodonoghue> the artifacts persist no matter what the WM with resolutions over 2k

11:32 <jhovold> bryanodonoghue: as we've discussed elsewhere, this is a known issue with mutter: https://gitlab.gnome.org/GNOME/mutter/-/issues/2398

11:33 <jhovold> i assumed someone had fixed it since it's been over a year since it was reported

11:34 <bryanodonoghue> a year ? I thought it was reported recently..

11:34 <jhovold> no, i'm afraid not

11:34 <bryanodonoghue> jeez you're right -> Issue

11:34 <bryanodonoghue> created

11:34 <bryanodonoghue> by

11:34 <bryanodonoghue> Leonard Lausen

11:34 <bryanodonoghue> 1 year ago

11:35 <danielt> I'd expect it to be broken on lots of embedded compositors (any device where planes are not uniquely attached to a single CRTC is likely to crash when there are multiple monitors).

11:36 <danielt> I think some people don't notice it because as soon as the monitor is connected and gdm crashes then it restarts using X11 (which "nearly" works).

11:37 <danielt> It will hurt the next Fedora much more since IIRC they are removing X11!

11:38 <jhovold> danielt: hopefully redhat can find some people to look at it before then...

11:38 <jhovold> ajhalaney[m]: ^

11:41 <javierm> jhovold: I've just asked the mutter developers about that issue

11:44 <jhovold> javierm: thanks!

11:47 <javierm> jhovold: talked with jadahl

11:47 <javierm> he says that is on his list, has an idea on how to fix it but just couldn't find the time to do it

11:50 <jhovold> javierm: ok, hopefully someone will look at it soon

11:55 <danielt> javierm: Is it useful/worthwhile to report visual artifacts during workspace switch on a multi-monitor X13s setup (guessed to be a problem with fencing... final frame on main monitor does not complete the redraw... can be fixed by triggering/dismissing the Activities overview). I confess I've been sitting on this since a) it can only be reproduced with my hacky patch and b) I don't know which component to report it against !

11:59 <javierm> danielt: I believe it is worth to report yes, or at least mention in the issue

12:01 <danielt> javierm: Any idea whether fencing is all handled by mutter or if gnome-shell gets involved? If not I can just report it against mutter and cross my fingers!

12:02 <javierm> danielt: I've no idea to be honest. I would say all is handled by mutter but is just a guess since I don't work on that part of the stack

12:02 <danielt> javierm: No worried... mutter it is then!

12:02 <danielt> s/ied/ies/

12:02 <javierm> yeah, reporting against mutter makes sense to me and then folks can dig from there

12:42 <ajhalaney[m]> Thanks javierm for reaching out about that

13:12 <HdkR> Whoa, displayport connector names changed

13:16 <jhovold> HdkR: yes: https://github.com/jhovold/linux/commit/2ccaebd9b44648da64abf215a1a5f33fc0c6e807

13:16 <HdkR> haha, oops

14:31 <HdkR> Curiously, ath11k_pci started getting really upset with me after some uptime. https://gist.github.com/Sonicadvance1/4706f3659c0b1bb98426b160e0425402

16:46 <steev> HdkR: i've seen that every once in a while... remotely it won't help but i just modprobe ath11k_pci -r; modprobe ath11k_pci

16:47 <HdkR> :D

16:48 <HdkR> That also means I could just block the module which makes my life easier

18:06 <ardb> steev: do you have to .config that goes with your c630 6.6.y tree?

18:06 <steev> ardb: https://paste2.org/pMmHByHm

18:07 <ardb> ta

18:18 <steev> it's the base defconfig and just a couple changes (i use fscrypt so needed to enable some things)

18:21 <steev> that said... i closed it before i went to bed last night, at 97% battery, and just opened it now, and "only" down to 84% batter, and definitely woke from suspend :/ not sure why bamse goes splat

18:22 <steev> bryanodonoghue: yeah, that's that known issue with mutter, and danielt's patch definitely helps, but isn't perfect (but a better workaround than the crashing/x11 defaulting)

18:23 <steev> i haven't kept up on packaging it in mutter though

18:56 <jbowen> Is there wiki/blog with the running status of the state of X13s support? I've asked in here before (and watched Johan's latest Kernel Recipes) talk and I'm pretty much ready to hit "purchase" on my cart

18:58 <jbowen> What's the average battery life of that laptop these days? I think Johan said ~15 hours?

19:17 <Jasper[m]> in standby yes

19:17 <Jasper[m]> At least I've seen people say somewhere around that

19:17 <Jasper[m]> But it's definitely usable if you have a proper aetup

19:17 <Jasper[m]> s/aetup/setup/

19:27 <jhovold> Jasper[m]: 15h is the current idle time on a full battery (Xorg, wifi, 66 % backlight)

19:27 <jhovold> suspend will last about 30 h

19:27 <jhovold> jbowen: take a look at https://github.com/jhovold/linux/wiki/X13s

19:28 <jhovold> i try to keep that one up-to-date to complement the presentation

19:36 <DanaG> I went ahead and ordered one of the HP X2 Qualcomm Chromebooks. I also bought a board somebody made that turns any USB-C cable into a SuzyQ cable, so I don't have to open the case to alter write protection.

20:10 <jbowen> jhovold: Awesome! Thank you so much for all of the work, the presentations, documentation, and for generally being personable :)

22:10 <hexdump0815> DanaG: do you have a link for that suzyqable converter board?