2023-05-13.log

+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)00:46
- klardotsh (QUIT: Ping timeout: 240 seconds) (~klardotsh@98.97.35.74)00:51
- mtm- (QUIT: Ping timeout: 264 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)02:03
- mjw (QUIT: Ping timeout: 268 seconds) (~mjw@gnu.wildebeest.org)02:29
- nsc (QUIT: Ping timeout: 240 seconds) (~nicolas@86-49-142-46.pool.kielnet.net)03:17
+ nsc (~nicolas@212-49-142-46.pool.kielnet.net)03:19
- bluerise (QUIT: Ping timeout: 268 seconds) (~bluerise@user/bluerise)03:32
+ bluerise_ (~bluerise@p5b0ac2a4.dip0.t-ipconnect.de)03:32
+ mtm- (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)04:09
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)09:54
* bluerise_ -> bluerise12:41
- bluerise (QUIT: Changing host) (~bluerise@p5b0ac2a4.dip0.t-ipconnect.de)12:41
+ bluerise (~bluerise@user/bluerise)12:41
BoostisbetterI am now at 32 succesful wake from standby actions on the Reform using the 5.12 kernel. 12:53
BoostisbetterThe only tradeoff right now would seem to be some display instability that occasionally glitches workspaces. It comes quickly and goes quickly. It absolutely has to do with the graphics driver, as it just seems like the screen buffer isn't being refreshed. 12:53
+ mjw (~mjw@gnu.wildebeest.org)13:06
BoostisbetterIt is only about .5% of my working experience though, so I really don't mind. Just doesn't happen on 6.113:18
minuteBoostisbetter: now one would have to test all versions in between to find where it regressed 13:47
- mtm- (QUIT: Ping timeout: 240 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)14:03
+ mtm- (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)16:09
- ec0 (QUIT: Ping timeout: 265 seconds) (~ec0@vps-446f4f39.vps.ovh.ca)16:21
+ ec0 (~ec0@vps-446f4f39.vps.ovh.ca)16:26
- swivel (QUIT: Ping timeout: 240 seconds) (~swivel@shells.gnugeneration.com)18:51
+ swivel (~swivel@shells.gnugeneration.com)18:52
Boostisbetterminute: I think it might just be easier to look at the deltas between the GPU driver source between those two kernels19:45
joschBisecting: 70211 revisions left to test after this (roughly 16 steps)19:57
joschwhover does the bisecting has to do 16 tests to figure out the commit breaking this between 5.12 and 6.119:58
sigridgl. hope it finds it19:58
joschsigrid: nobody is doin that work yet... :(20:16
BoostisbetterYou know, one thing that 6.1 permits is the battery reporting to the waybar, but for me, while that feature is cool and useful, it doesn't work that well for me. I tend to have the waybar hidden, as I hate the space it takes up. Still I think it is awesome the LPC can report to the OS now. 21:18
BoostisbetterRegarding the work being done, are you saying there are 70k in changes to the video driver portion of the kernel?21:18
Boostisbetterjosch: Regarding the work being done, are you saying there are 70k in changes to the video driver portion of the kernel?21:19
pandora[m]i am curious ... is there any advantage to stick to 5.12 over 6.1?21:21
joschBoostisbetter: no, those are all commits between 5.12 and 6.121:32
joschBoostisbetter: but thanks to bisection, you only do 16 tests to figure out where it breaks21:32
joschpandora[m]: apparently 5.12 can still resume from suspend quite reliably21:33
Booster[m]pandora I'm at 38 succesful resumes into sway from suspend.21:33
Booster[m]there is still an unknown condition in 5.12 which causes it to crash on resume but for the most part this is about 98% successful as far as suspend goes.21:34
Boostisbetterjosch: if no one else steps up to the plate before me, then 16 doesn't sound bad at all. 21:34
Boostisbetterjosch: and I could probably cheat and just look at the Librem 5 gpu driver source for their current kernel, and just check the deltas there. 21:36

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!