00:00 <anthony25> bryanodonoghue: I sent it to you

00:00 <anthony25> I still have the same error, so I linked to you the dts I'm using

00:05 <bryanodonoghue> God I'm such a dose

00:05 <anthony25> haha :D

00:05 <bryanodonoghue> ov02c10 config in the driver is 1 lane only

00:05 <bryanodonoghue> :)

00:06 <bryanodonoghue> ok - I'll add the 2 lane option

00:06 <bryanodonoghue> thx

00:06 <anthony25> thank you!

00:06 <bryanodonoghue> ha it has the 2 lane config

00:06 <bryanodonoghue> already but for whatever reason doesn't accept

00:06 <bryanodonoghue> so easier

00:06 <bryanodonoghue> thx for your help/patience

00:07 <anthony25> no thank you for implementing this, it's very cool

00:07 <anthony25> I'm happy if we can get the webcam working on this laptop

00:07 <bryanodonoghue> what I'll do is frig the hardware ID on the Insprion 14p

00:07 <bryanodonoghue> so the next thing you test will be more than compile tested on my end

00:11 <anthony25> just if you can track which commits or files you change, it makes it easier for me to apply the fixes

06:22 <smoorgborg[m]> I've seen Arch mentioned here a couple of times. Is there anyone running the Thinkpad T14s G6 on Arch Linux? If so, any guide or repo to visit?

07:23 <jhovold> smoorgborg[m]: I run arch, and you can run any distro you want as long as you build your own kernel

07:23 <SpieringsAE> smoorborg: You could check out anonymix007 github https://github.com/anonymix007

07:24 <SpieringsAE> There is a x1e-alarm repo with a kernel and such

07:24 <SpieringsAE> you can add that to sources and install linux-x1e

07:24 <SpieringsAE> its my fallback kernel on my asus vivobook

07:24 <jhovold> you should be able to boot the arch distro kernel as well, but cpufreq is still not in mainline for x1e so you probably want to build your own (or use one that someone else has packaged)

07:25 <jhovold> for example, based on my wip branches: https://github.com/jhovold/linux/wiki/T14s

07:26 <SpieringsAE> I am really hoping somebody will merge my usb-a and sd-card reader patches for 6.14

07:27 <SpieringsAE> sent a reminder but no response yet

08:02 <jhovold> steev: thanks for testing the ath11k fix, sounds like it does avoid the corruption

08:02 <jhovold> have you seen any more of those messages over the weekend?

08:04 <steev> a total of 8 messages on the 7th and 8th, nothing yesterday or so far today

08:05 <jhovold> but this was at home were you typically don't see the corruption? or it still happened occasionally?

08:06 <steev> it happens at home when i see the corruption, sometime tomorrow i'll be heading to my sister's place and see what happens

08:06 <steev> i'll be taking the t14s as well, though its still using windows, but something i noticed last time i was there was that even with windows, the ath12k was having issues connecting to their network for some reason (none here at home)

08:07 <jhovold> yeah, the ap definitely seems to be involved in upsetting the fw

08:26 <smoorgborg[m]> Thanks for the input. I think I'll give Arch a try on my ThinkPad then.

08:32 <eirikkar> Hello, I'm having some issues with my asus vivobook s15, I have the 12c 32gb version and I have ran ubuntu 24.10 since november. My issue is that when I power down the laptop the screen goes blue and the laptop restarts, even when I told it to do a poweroff. When I then boot into ubuntu there will be a black screen and I have to power it off with the powerbutton and then power it back on after. Then I will be able to boot into ubuntu and

08:57 <jhovold> eirikkar: try passing efi=noruntime, there are some known uefi bugs which triggered similar issues on previous generations of SoCs

08:58 <jhovold> I no longer see a crash on shutdown (reboot), but there is a page fault when calling into the fw also on x1e

10:26 <eirikkar> Thanks for reply, I tried passing efi=noruntime, but that didnt help. Do you have any other things I can try?

11:40 <jhovold> eirikkar: not really, sorry. maybe make sure you use the latest ubuntu kernel and then report it to them

11:41 <jhovold> if this was a generic issue with the vivobook I assume SpieringsAE would have noticed

11:52 <eirikkar> Alright, thank you.

11:57 <jhovold> Here's an updated wip branch for the X13s:

11:57 <jhovold> - https://github.com/jhovold/linux/tree/wip/sc8280xp-6.14-rc6

11:57 <jhovold> Changes include:

11:57 <jhovold> - fix ath11k ring-buffer corruption

11:57 <jhovold> - update pipewire fixes to v3 + alignment fix

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

11:57 <jhovold> - https://github.com/jhovold/linux/tree/wip/x1e80100-6.14-rc6

11:57 <jhovold> Changes include:

11:57 <jhovold> - update pipewire fixes to v3 + alignment fix

11:57 <jhovold> - rebase on x1-crd.dtsi split

12:20 <Jasper[m]> wheey ring buffer corruption fix

12:20 <Jasper[m]> very nice

12:21 <jhovold> do you hit it often, Jasper[m]?

12:24 <Jasper[m]> Generally after a while and/or sleep

12:25 <Jasper[m]> But I haven't consciously checked dmesg in a bit

12:30 <jhovold> hopefully fixed now, even if the patch itself looks like a bit of a hack

12:34 <Jasper[m]> I'll see when it lands in F41 repo's

12:34 <Jasper[m]> *repos

12:34 <Jasper[m]> Or when I get a local build setup set up

12:34 <maz> it really looks like a memory ordering problem between device and cpu.

12:36 <jhovold> yeah, I think so too

16:02 <steev> abelvesa: so re: your oled patch, how would that work? are distros expected to figure out which t14s one has and copy the correct dtb? end users? will the firmware know about both?

16:05 <tobhe_> steev: unfortunately it won't be easy to figure out. smbios doesn't have enough info at the moment

16:06 <tobhe_> firmware should be identical

16:08 <steev> right, the firmware would be identical, i just don't know how the oled stuff should be handled, it would be nice if this could be done with overlays, but as noted, if we have no way of telling that its oled, we don't know to load the oled overlay

16:09 <tobhe_> indeed. having both work with the same dtb doesn't really seem to work either though so I'm not sure what the best solution is

16:09 <tobhe_> maybe we can ask Lenovo to change their smbios tables, not sure if that is something they can do at this point though

16:10 <travmurav[m]> iirc there was some uefi protocol to read edid

16:11 <tobhe_> hmm... still wouldn't work with hwids but it could work with my nasty grub hack

16:14 <steev> EFI_EDID_DISCOVERED_PROTOCOL

16:14 <steev> at least based on a quick google search for uefi edid :D

16:15 <travmurav[m]> yeah I think that's what I was looking at when future-thinking in case dtbloader ever needs this in the future for code-based fixups

16:16 <travmurav[m]> multi-sourced panels are usual pain on linux-on-phone so we have to detect them on bootloader level to not bring ugly painful hacks into linux

16:16 <travmurav[m]> so I just assumed same pain will apply to laptops, never got around to actually implementing anything though

19:43 <anonymix007[m]> Could it be that this EDID protocol is not implemented here? The following doesn't seem to be working on my T14s: https://github.com/anonymix007/systemd/commit/0ebe7b9a59e44b07b96337310f3c25fff69a1be9