00:01 <osmoz[m]> alexVinarskis: glad to help and provide tests data, I will lauch a kernel compile right now and report back when it's installed

00:06 <steev> that reminds that my oled does not appear to be in the kernel, some sdc 0x419f i should check the datasheet sites, because google doesn't know much about it

00:13 <tobhe[m]> steev: there was https://patchwork.kernel.org/project/linux-arm-msm/patch/20250320-wip-obbardc-qcom-t14s-oled-panel-v1-1-05bc4bdcd82a@linaro.org/

00:14 <tobhe[m]> seems to be the same

00:14 <steev> tobhe[m]: si, but chris (afaik) still hasn't sent v2

00:15 <steev> or christopher, i suppose, i don't know if they go by chris

00:30 <valpackett> oop, just thought the random hang came back, but i could eventually switch vt, it was actually the framebuffer thing

00:30 <valpackett> "[dpu error]failed to prepare framebuffer" / "Page flip failed: drmModeAtomicCommit: No space left on device" mm yeah I'll apply the actual fix linked above

00:31 <valpackett> (just had the WARN_ON commented out, before steev linked to a patch)

04:49 <icecream95> With 6.16.0-rc4-jg-0-qcom-x1e I'm seeing about 1W worse idle power consumption compared to 6.14.0-35-qcom-x1e on Vivobook

05:00 <JensGlathe[m]> The energy eaters are in there

05:00 <JensGlathe[m]> is it the same dtb?

05:36 <icecream95> The latter kernel is ubuntu-concept so using this dts: https://git.launchpad.net/~ubuntu-concept/ubuntu/+source/linux/+git/oracular/tree/arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts?h=qcom-x1e

06:02 <JensGlathe[m]> icecream95: they are different. Mine has sound, codec, quite a few more regulators (don't know if required).

07:39 <alexVinarskis[m]> Re few more regulators: should always do a quick exercise of checking DSDT for actually used LDOs, only enable those. Some may be missing from DSDT and only present in AeoBs (eg. Camera pmic, can be added when adding camera), some may not be listed at all (eg. LDO for lpass) - remove extra LDOs with care, only the otherwise unused ones by your DT. Identifying used LDOs and their voltages should be as simple as cat DSDT.dsl |

07:39 <alexVinarskis[m]> grep LDOx_y -A2 where x 0...17 for x1 so far, y A... . 2nd line will be the target voltage in hex in mV. Ive seen both some deviations in target mV from device to device, and different sets of actually enabled LDOs.

13:10 <jhovold> Here's an updated wip branch for the X13s:

13:10 <jhovold> - https://github.com/jhovold/linux/tree/wip/sc8280xp-6.16-rc5

13:10 <jhovold> Changes include:

13:10 <jhovold> - fix drm gem buffer ref counting (6.16-rc5 regression)

13:10 <jhovold> Here's an updated wip branch for the T14s and X Elite:

13:10 <jhovold> - https://github.com/jhovold/linux/tree/wip/x1e80100-6.16-rc5

13:10 <jhovold> Changes include:

13:10 <jhovold> - fix drm gem buffer ref counting (6.16-rc5 regression)

13:30 <AlekseiNosachev[m]> <JensGlathe[m]> "https://github.com/alexVinarskis..."; <- Added some missing ones from SP11 5G version

14:58 <spawacz> jhovold: Does not boot for me on x13s. Stuck on EFI: Exiting boot services

15:00 <jhovold> spawacz: did you forget to update the devicetree?

15:01 <spawacz> no, I copied it to efi partition

15:02 <jhovold> should be something on your end, which kernel did you update from?

15:03 <spawacz> From 6.15

15:04 <spawacz> I will rebuild the kernel from a clean state

15:09 <spawacz> It booted. The first time, I passed -march=native KCFLAGS...

15:25 <GurneyBuchanan[m]> Has anyone gotten Steam working via FEX on Fedora? I'm currently running steam via FEX from the .deb (unpacked and installed) but I'm hitting this error (causing steam web helper to fail):... (full message at <https://matrix.org/oftc/media/v1/media/download/Ae3PsXO1lLYz4Fx1duZyQxAH2WBqKstcs3IE8eLCeCKM4NK2GjWaWFaW0UiYegvCUyH3JWyaTmtRFaEFQY5gdPhCeYLZdI_AAG1hdHJpeC5vcmcvTk5XU3J2S2ZCc2FNYW5ISEhVa2R4WUtL>)

15:35 <robclark> GurneyBuchanan[m]: https://discussion.fedoraproject.org/t/issues-and-comments-with-fex-on-fedora-42/154860/2

15:35 <robclark> haven't gotten it working yet, fwiw

15:36 <GurneyBuchanan[m]> Rob - you rock! Giving that a try!

15:37 <robclark> not working yet but if you figure something out, add it to the discussion page

15:37 <GurneyBuchanan[m]> Will do!

15:37 <Jasper[m]> Wait it isn't supposed to be working?

15:38 <robclark> seems like a fedora specific issue

15:38 <Jasper[m]> Maybe I haven't used it in a while then, it used to work with no extra issues before

15:38 <robclark> in general fex and steam should work.. just not the fedora packaged thing

15:38 <GurneyBuchanan[m]> Agreed, and now the fedora RPM for steam just calls out to another binary

15:38 <Jasper[m]> (on my X13s)

15:39 <Jasper[m]> @robclark aha, the fedora packaged part. Yeah I built it locally from the git repo. That'd make sense.

15:39 <robclark> the error I get is `pipe:[85132]: command not found` .. so I guess something missing from fedora x86 rootfs that fex-emu uses

15:41 <GurneyBuchanan[m]> Agreed - having the same issue even after disabling use_muvm!

15:42 <GurneyBuchanan[m]> I'll try a different rootfs that azaki whipped up

15:43 <AzkaliManad[m]> Azkali* 😜

15:44 <Jasper[m]> All these A.*a.?i people are making my brain hurt

15:45 <Jasper[m]> s/.*/.+/, s/.?/{1}/

15:45 <Jasper[m]> (I suck at regex)

15:45 <GurneyBuchanan[m]> Oops - sorry Azkali Manad !

15:55 <GurneyBuchanan[m]> Confirmed - hitting the same issue with Azkali Manad 's RootFS-es as well! Likely a fedora issue - asking over there!

16:04 <robclark> lmk if you figure something out.. I'd like to get steam working but haven't had much time to look at that

16:08 <abelvesa> anyone else having issues when connecting a second monitor over DP (second monitor meaning 3rd display)?

16:08 <abelvesa> I have this issue on xps13 where the second monitor gets detected but there is no output on it

16:09 <abelvesa> and it seems to go back all the way to 6.15

16:09 <abelvesa> haven't tried (yet) older kernels

16:10 <alexVinarskis[m]> i used to have that, something to do sith gnome and userland video things + wayland in my case, though not sure if its applicable in your case. rm ~/.config/monitors.xml* and then reboot solved it for me - this wipes all the display config like fps, resolution,location

16:11 <alexVinarskis[m]> I also had that (separate instance) when illegal params were set, eg. for some reason could select 3440x1440 @165 hz, even though that would've required 4 DP lanes, 2 lanes max out of 100hz. Selecting 165hz would be allowed, but would get black screen of course.

16:14 <abelvesa> alexVinarskis[m]: not sure, but I think the "illegal params" are actually allowed due to the panel advertising them on aux

16:16 <abelvesa> as for the issue being userspace, I just tested the same thing on x13s and it works fine (gnome + wayland)

16:17 <abelvesa> so it must be something else

16:17 <alexVinarskis[m]> does it still not work after removing the monitors.xml?

16:17 <abelvesa> kernel related, maybe retimer ?

16:19 <abelvesa> nope, still not working. But I still don't see why that would matter

16:19 <abelvesa> if it works on x13s, it should be working on x elites as well

16:20 <alexVinarskis[m]> not sure why it would matter, but it would solve it for me back in maybe January. Dual monitor setup would typically work, then at some point will give black screen on very specific monitors. Either changing monitors or deleting that config was fixing it for days/weeks/months.

16:20 <abelvesa> it works if you boot up with both monitors connected though

16:21 <\[m]> for people ordering from europe - how long did shipping take from lenovo?

16:22 <alexVinarskis[m]> do you have 4 lane DP series applied? I remember some monitors are not happy with 2 lane HBR3, and want 4 lane HBR2 (i know its also not directly related to your issue, just sharing as it may be related to cold boot working).

16:23 <abelvesa> nope, I don't. That still breaks the USB on unplug, doesn't it ?

16:23 <abelvesa> I don't apply things that are known not to work

16:24 <alexVinarskis[m]> Don't recall if it broke them or not on top of my head :)

16:34 <\[m]> https://www.phoronix.com/news/Qualcomm-MSM-DRM-Linux-6.17 w00t even though likely not affecitng x1p 😆

16:40 <JensGlathe[m]> My builds 6.16.0-rc4-jg-1 and 6.16.0-rc5-jg-0 have this patchset

16:40 <JensGlathe[m]> tb16 says 1107MHz, X14 says 1250, DevKit 1500 😎

16:45 <robclark> \[m]: that branch includes the (non-dts) x1-45 support.. but I guess jhovold/others already have those patches in their branches

17:37 <GurneyBuchanan[m]> robclark: posted over in #Fedora-ARM in the Fedora matrix if you happen to be over there!

17:43 <robclark> I am on #fedora-arm on OFTC, but that doesn't appear to bridged with matrix?

17:46 <\[m]> parallel univers -> https://fedoraproject.org/wiki/Architectures/ARM#Get_Involved_with_Fedora_ARM they're on libera?

17:52 <GurneyBuchanan[m]> Oh wow - I'm not sure - I found their matrix by navigating a bunch of out-of-date wikis 😢

17:58 <robclark> err, src, I meant libera, not OFTC

18:00 <GurneyBuchanan[m]> Are things fairly active over there? Seems hit or miss in Matrix!

18:00 <robclark> not super active but nott completely dead

18:00 <GurneyBuchanan[m]> Time to resurrect my IRC client!