[13:10] Hi all [21:24] RikMills[m] Eickmeyer: FYI, night color + intel + steam == flicker fest [21:25] I've explicitly disabled it by default in next setting update; also document on site. [21:26] This on 5.19 kernel. I believe it is the same on oem kernel, but since I can't uncook that egg ... :P [21:26] 5.19 hwe vs. 5.17 oem. [21:28] mmikowski: I mean, is there anything keeping you from installing the 5.17 OEM kernel stack and then uninstalling the 5.19 HWE stack on an installed system? [21:28] I've documented how to switch kernel stacks before. [21:28] https://discourse.lubuntu.me/t/lubuntu-22-04-2-lts-upgrades-still-using-the-5-15-ga-kernel/4042/8?u=arraybolt3 This is for switching from HWE to GA on Lubuntu, but with some tweaks it could likely work for witching from HWE to OEM 5.17. [21:37] Aye, sorry Aaron! I should have put you into the cc list. [21:37] Well, no. [21:37] But I don't think 5.17 fixes it. [21:38] The flicker was there before. I can look a little deeper, but it appears almost all the fixes that matter to us have moved forward to 5.19 HWE. [21:38] It is the interaction between Intel GPU and night vision. [21:39] We already found and fixed a number of i915 flicker related settings (mostly modules), but I think what made this come up again is for some reason night color was getting set during burn-in. [21:39] So the Steam tests got all flickery. [21:39] Turn off the night color, and it's fixed. [21:40] Of course, absolutely no issue with NV graphics. [21:40] Haven't search the bug db for this yet; it's definite on X11. Haven't checked wayland yet. [21:40] just wanted to give you a heads up. [21:41] For RikMills[m] and Eickmeyer, I think it's very important for a default settings consideration. [21:41] Also for documentations. +cc ahoneybun[m] [21:42] mmikowski: #ubuntu-kernel [21:42] Since Kubuntu ships with 5.19 HWE IIRC, and its probably better to start with something that doesn't have night color but works on demanding gfx out of the box. [21:42] Hi Eickmeyer! [21:42] Hi! [21:43] Ok, I'll add that to my lurk list. [21:43] Basically, if it's a kernel issue (and not hardware-specific), that's a place to talk to. [21:44] I, personally, have seen no issues on any of my hardware with i915. Tells me it's specific to whatever hardware you are testing on. [21:44] Thanks. It may be limited access. [21:44] But, you haven't mentioned the hardware you're testing on. [21:44] That's the nxg2 and xeg2 [21:44] 1260p [21:44] i7-1260p [21:45] Ok, might be limited to that hardware then. [21:45] It might [21:45] Remember how intel gets very specific in their own MB manufacturing? [21:45] Not generic at all as you'd hope. [21:45] Just thought I'd let you know. It is definitely confirmed on there, and those are very popular CPUs. [21:45] Oh yeah. [21:45] CPUs, yes, but not MBs. [21:45] right [21:47] Like I said, just an fyi. We'll look at earlier revisions and see if it replicates. [21:50] IIRC, xeg2 also had that issue. But we'll see. === guiverc2 is now known as guiverc