00:04 <steev> oh nice that will make HdkR happy

00:05 <HdkR> steev: What? Who? When?

00:06 <steev> xnox is working on ubuntu support to make it installer install

00:06 <HdkR> Oh cool, that's a lot easier than building off the cloud image

01:57 <clover[m]> displayport not working:... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/UdhraJvCUlVZOWAOWBvrGsXK>)

02:02 <steev> flip it?

02:10 <clover[m]> [ 264.204330] usb 3-1: new high-speed USB device number 5 using xhci-hcd... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/kcAMaPMDIjYfuYzRSjwNrUon>)

02:13 <clover[m]> Looks like that if I try to mirror it. Completely blank if I try to Join.

02:13 <clover[m]> Its weird cause my other monitor works with HDMI

02:18 <clover[m]> e

02:34 <steev> not my fault!

02:34 <steev> i blame bamse

02:46 <HdkR> But what if you try flipping it again?

03:26 <HdkR> "1802: Unauthorized network card is plugged in - Power off and remove the network card"

03:37 <HdkR> https://twitter.com/Sonicadvance1/status/1632948451070873601

03:50 <steev> oh no :(

03:51 <bamse> steev: what kernel is that blame on?

03:51 <steev> clover[m]: what kernel is it?

03:55 <steev> holy

04:59 <HdkR> I guess with the WWAN connector being a wash, the only hope I have is that the USB ports become fast

13:59 <steev> mani_s: entirely unscientific, because i don't have any sort of power measurement

14:00 <steev> but, with patchset applied, and power_supersave=y (can't recall exact option), at least suspended over night (charged to 100), up time of 7 hours 49 minutes, battery at 55%

14:11 <arnd> HdkR: The old Yoga 3 11 (Intel Core M) did the same thing on the WLAN slot even with a non-Lenovo branded card but using the right chip, though IIRC I was eventually able to get it to boot without WLAN and then managed to bring it up by poking some chipset registers.

14:11 <arnd> HdkR: are you able to enter the BIOS setup and disable the WWAN slot?

14:15 <arnd> Or possibly I used this trick http://web.archive.org/web/20080608221623/http://www.srcf.ucam.org/~mjg59/thinkpad/hacks.html

14:19 <mani_s> steev, wow

14:20 <mani_s> I'm hoping to do some real power measurements on the CRD device in the coming days

14:20 <mani_s> that should reveal how much power that is being saved

14:36 <HdkR> arnd: It can be disabled in the uefi. don't know if it can then be reenabled at some point

14:37 <HdkR> robclark: https://twitter.com/TheDayvanCowboy/status/1633043543986954240 Portal on Chromebook/ChromeOS? :P

14:40 <arnd> HdkR: if you can boot into a running kernel with WWAN disabled, there is a fairly good chance you can get it up again by reprobing the PCIe port, the trick is finding the right registers. E.g. if the root port is held in reset state, you'd have to know the right reset line.

14:42 <arnd> HdkR: do you see the PCIe root port that the card is normally connected to if you boot with WWAN disabled?

14:42 <HdkR> moment, let me go flail a bit

14:51 <robclark> HdkR: nice

15:45 <clover[m]> <steev> "clover: what kernel is it?" <- 6.2.1 based on your 6.2.y branch

15:46 <bamse> clover[m]: thanks, then i will ignore steev's passing of the blame :)

15:47 <clover[m]> steevs fault! :P

15:47 <clover[m]> jk

15:47 <bamse> steev: what's the plans for moving to v6.3?

16:01 <HdkR> Hm, went to check my PCIe roots and the laptop was flat

16:02 <HdkR> Seems like it has an issue maintaining charging

16:03 <danielt> HdkR: I had that problem from time to time when I as using an unpowered dock (e.g. a dock powered by X13s own power supply). Arguably is shouldn't happen: there should have been >45 watts "spare" to power the laptop but I suspect it failed to draw power in some cases.

16:04 <danielt> HdkR: I'm afraid I fixed it the dumb way (either by powering the laptop directly rather than through the dock... and later by switching to a Lenovo dock with a stronger power supply).

16:05 <danielt> HdkR: I always meant to do some testing in Windows to see if it was a generic problem or not... but that would involved running Windows on it for a week and I'm not super enthusiastic about that.

16:05 <HdkR> Shamefully I'm using both USB plugs to try and spread the USB load between the two ports. So I need to use a powered dock on one

16:07 <bamse> have any of you ran into the problem where the LED by the power button just blinks continuously?

16:07 <bamse> danielt, HdkR ^^

16:07 <HdkR> I haven't noticed that one

16:08 <bamse> i get that occasionally when leaving my x13s connected to one of my monitors...

16:08 <danielt> bamse: Maybe... I found closing the lid whilst docked was a "high risk" activity... so I stopped doing it.

16:09 <bamse> danielt: maybe that's what i'm doing to trigger this

16:09 <danielt> bamse: I don't remember exactly how it broke though (it wasn't every time but I remember having to long press the power-button to get the system back)

16:09 <bamse> but i think it's something on the display-side that we trigger...because it keeps doing that in uefi as well...haven't tried booting windows

16:25 <HdkR> arnd: https://gist.github.com/Sonicadvance1/d58f6a6e6d0e6094c8c7788956bcf08d Looks like it goes away when disabled

16:29 <bamse> mani_s: on the subject of power...we have a pm_runtime_forbid() in both dwc3-qcom and xhci-plft...holding the interconnects and power-domains higher than they need to be when nothing is connected...

16:29 <arnd> HdkR: ok, so the entire pcie@1c10000 bridge device is not there. sc8280xp-lenovo-thinkpad-x13s.dts sets it to status="okay", so it's probably a probe failure. Anything in the boot log about it?

16:31 <HdkR> arnd: https://gist.github.com/Sonicadvance1/0f63e1e54f5b15f6f6884cd25819bb9f Powerful failure to probe

16:34 <bamse> so presumably we're relying on some clock initialization by the bootloader for whatever feeds aux_clk...

16:44 <arnd> Right. I got very confused for a bit by the naming pcie4 pcie3 pcie2 etc that does not match the domain 6/4/2 numbers, but I see now that gcc_pcie_3a_aux_clk is indeed the clock used by pcie3a with domain 4.

16:45 <arnd> If it's indeed one of the clocks that is missing, a possible approach may be to just dump the status of all clocks at boot and see what changes with WWAN enabled

16:59 <bamse> arnd: not unlikely there's an issue with the current definition of "all clocks"...

16:59 <bamse> arnd: will have to dig into the documentation

17:02 <HdkR> Ideally the 10gbe USB-C ports will just be fast so I don't need to fuss with WWAN though :P

18:05 <steev> bamse: afaik, the only real hold out for 6.3 is the pmic_glink device links not being correct/working correctly

18:06 <bamse> steev: worried about your statement i booted linux-next (+ iommu-fix, battery defconfig and the gpu patches) on the crd and i have external display

18:06 <bamse> steev: so what's there in the future is what we want

18:09 <steev> bamse: i'm not sure what you mean exactly; i have external display here too?

18:09 <bamse> steev: i am trying to say that i don't have any issues with what landed in v6.3-rc1...

18:10 <bamse> steev: i.e. i don't see the issue you're referring to wrt device links

18:10 <bamse> steev: ahh, but i do see "Failed to create device link..." in the log

18:11 <steev> bamse: https://paste.debian.net/1273278/ this - i had previously said i see those messages, but don't actually have any issues and jhovold said that they are correct messages and something isn't correct

18:12 <Caterpillar> any progress on x13s power usage optimization?

18:12 <steev> scroll back a bit

18:16 <steev> i figured since things were working, they were just a modern probe defer :P

18:17 <bamse> well, the "Failed" part could quite likely hide some future errors...so i'm with jhovold on this one...but i haven't looked at it...and i have pixels on my screen :)

18:38 <steev> bamse: sure :) i have working things too

18:38 <steev> that's the only thing i've really noticed in 6.3

18:40 <steev> 12 hours 32 minutes and 22% battery left

18:41 <bamse> steev: only difference being mani_s' aspm patch(es)?

18:41 <steev> and setting pcie_powersupersaver or something

18:43 <steev> steev@wintermute:~/kernels$ grep SUPERSAVE /boot/config-6.3.0-rc1

18:43 <steev> CONFIG_PCIEASPM_POWER_SUPERSAVE=y

18:43 <bamse> sounds like a big hammer :)

18:44 <steev> sure, but i'm okay with hammers

21:00 <xnox> i managed to install Ubuntu on x13s using installer image, side by side with windows, without destroying bitlocker (had to recover it twice) but otherwise can use Enter+F12 to boot into either bitlocked Windows 11 or Ubuntu 23.04

21:00 <xnox> it would be shame if anyone would discover https://launchpad.net/~ubuntu-concept/+archive/ubuntu/x13s by accident and tried to use ubuntu desktop installer linked from there

21:01 <xnox> on X13s

21:05 <steev> hope no one like HdkR finds it

21:21 <HdkR> Oh no, I might try and recover my drive

21:57 <steev> 15 hours 49 minutes, 5% battery

22:10 <clover[m]> during suspend or is that regular use

22:14 <steev> suspend, mostly but there was some usage

22:15 <steev> i did say it's entirely unscientific, i actually expected it to be dead battery when i got back from my place, but no, it still had the 5% battery left

23:09 <steev> bamse: the real question... has kalle had any more time to look at our board file ? :D

23:13 <bamse> steev: yes

23:13 <steev> in a way that will make 5.4 very happy?

23:29 <bamse> that would be nice

23:29 <steev> indeed

23:35 <xnox> about x13s => somehow i only have 2.4ghz networks on the wifi, and no 5ghz ones..... am i missing something?

23:37 <HdkR> Known issue