00:20 <steev> bamse: https://paste.debian.net/hidden/741c4cff/ - c630 (null ptr on boot, the other splats when i try to suspend (display also seems to go boom but oddly nothing about it in the logs, the backlight just doesn't seem to come back on) - where is the proper place to report this, kernel bugzilla? mailing lists of anything where sdw_stream_add_slave is in the kernel?

00:25 <HdkR> Looks like T14s is finally customizable for 64GB of RAM and 120Hz display

00:26 <HdkR> In the US market

00:39 <craftyguy> is the RAM replaceable?

00:41 <steev> doubtful

00:43 <steev> now to find someone to give me a small loan so i can get it

00:43 <HdkR> Definitely not replaceable

01:49 <HdkR> Anyone know why X1E-78-100 returns different MIDR_EL1 registers depending on cluster? Looks like I get 0x512f0011 for the first cluster, then 0x511f0011 for the other twoclusters

01:49 <HdkR> Which means the "variant" bits is 1 or 2 depending

02:44 <bamse> steev: if you could pinpoint the commits that broke it, reporting it to regzbot would be the best...otherwise, i don't think we have a bugtracker that people really keep an eye on

03:04 <steev> bamse: afaiui, it broke around 6.7

03:10 <bamse> steev: oops...

03:11 <bamse> i don't even have a tmux session for 845...

03:18 <steev> a while back... jenneron[m] tried to get something reverted to fix the issue, and srini said it was the incorrect fix, and posted a different patch and i tested it...but i tested it against jenneron[m]'s stuff and sent my t-b saying it worked and it turns out that it doesn't, but the revert doesn't work now either

03:20 <steev> you could take the soundwire qcom.c from an older version and drop it in

03:22 <steev> 4830bfa2c812 was the commit to revert, i'll try to piece this together

03:46 <steev> https://lkml.org/lkml/2024/4/13/104 that was what i was talking about

03:55 <steev> actuall based on the mail, i guess since 6.6

04:51 <travmurav[m]> HdkR: I've seen somewhere x1e being described as "8x phoenix big + 4x phoenix mid"

04:54 <HdkR> weird

07:06 <jenneron[m]> steev: the patch applied instead one worked

07:06 <jenneron[m]> the problem is that there is a new breakage

07:06 <jenneron[m]> someone should find what's wrong with soundwire again

07:08 <jenneron[m]> as i said you can just copy-paste older soundwire driver

07:13 <steev> you could pre-6.11

07:14 <jenneron[m]> oh, fun

13:04 <Jasper[m]> Hmmm, updated to 6.10 on my x13s and fingerprint doesn't seem to be functioning

13:04 <Jasper[m]> anyone know what module is needed for it to load?

13:06 <jhovold> Jasper[m]: just the usb controller and phy drivers

13:07 <Jasper[m]> jhovold: Huh, I wonder why it doesn't show up then.

13:07 <Jasper[m]> usb in general just works. fprint reader doesn't show up under fprintd or lsusb

13:08 <jhovold> perhaps you don't have one? or did it work before?

13:08 <jhovold> do you see the third usb controller?

13:08 <Jasper[m]> jhovold: Had only updated to 6.10 now, psref says I should have one according to the machine number

13:09 <Jasper[m]> jhovold: Have to help me a bit here, how do I differentiate

13:09 <Jasper[m]> lsusb lists 2 pairs of root hub devices

13:09 <jhovold> you should see six usb buses

13:10 <Jasper[m]> I see 4

13:10 <jhovold> three pairs

13:10 <Nios34[m]> hexdump01 dts: https://gist.050821.xyz/8

13:10 <jhovold> Jasper[m]: you're probably missing the phy driver

13:11 <jhovold> or maybe not...

13:12 <jhovold> should be the same as for the other controllers

13:12 <jhovold> Jasper[m]: wrong dtb?

13:12 <Jasper[m]> gonna check bios real quick if I may have missed something

13:12 <Jasper[m]> jhovold: OHHH wait yeah

13:13 <Jasper[m]> that might be it

13:13 <Jasper[m]> I forget I have to put it on ESP manually

13:13 <Jasper[m]> Good call, will be back with results

13:17 <Jasper[m]> Yeah that fixed it. Bahahahhaha

13:17 <Jasper[m]> Thanks!

13:45 <abelvesa> anyone noticing any display artifacts on x1e laptops ?

14:47 <robclark> abelvesa: no.. but what does it look like? And does it also show up in a screenshot?

17:05 <anonymix007[m]> abelvesa: Is there any reason why Bluetooth is not enabled on X Elite yet by default? I've tried to port your BT changes for CRD to T14s but it doesn't seem to work

17:09 <steev> anonymix007[m]: you should be able to get most of the info you need for the bt device from the windows driver

17:10 <anonymix007[m]> steev: if only I knew what to look for...

17:10 <steev> what changes for crd did you port to the t14s?

17:11 <anonymix007[m]> 2 last commits here: https://github.com/anonymix007/linux-t14s/commits/wip/x1e80100-6.11-rc4/

17:21 <anonymix007[m]> Also the keyboard on T14s behaves weirdly. For example, Fn key always triggers the "touchpad off". Copilot key behaves as if a key combination was pressed. Do I need to create custom mappings somehow?

17:43 <steev> i am a terrible person who didn't keep notes of what i was digging into in the windows driver stuffs, but somewhere in the folder that has the bluetooth firmware on windows are other files, and if you run "strings" them, you should see some strings that mention the regulators, that's the part of the driver that has the bits to fill out the acpi pep stuff and that is the info you need for the t14s

19:33 <anonymix007[m]> I don't see anything in the directory with Bluetooth firmware (qcbluetooth8380.inf_arm64_*) except bsrc_bt.bin file. It has a TLMMGPIO string, but I have no idea if this is what I was looking for. And even if it is, I have no idea how to use that information: https://katb.in/maroqiwoyek

19:36 <bamse> do we have any written down instructions on how to get Linux (preferrably Debian) installed and up and running on the x1e devices?

20:10 <JosDehaes[m]> I have this: https://gist.github.com/joske/52be3f1e5d0239706cd5a4252606644b

20:11 <JosDehaes[m]> I also have a fixed debian installer, but I'm on holiday and don't have the yoga with me

20:12 <JosDehaes[m]> Oh apparently I've uploaded it some weeks ago to drive : https://drive.google.com/file/d/1XgKX1F5gdph9bUopEVrEFL02Smc0ekPE/view?usp=drivesdk

20:17 <steev> anonymix007[m]: that's it yes

20:18 <steev> the tlmm/gpio and such are the info you need for the correct gpios and (possibly) regulators

20:19 <steev> though regulators for (basic) bringup, you can potentially just use the defaults in the bluetooth driver. i was lucky in that when i posted my patch to the kernel ml, someone reached out and said "one of you with the schematics has permission to give him the correct numbers from it"

20:22 <steev> anonymix007[m]: https://patchew.org/linux/20230129215136.5557-1-steev@kali.org/diff/20230131043816.4525-1-steev@kali.org/ (sorry i can't find the original link at the moment to v1 but, this kinda gives you an idea of how i started out when i added wcn6855 and the thinkpad x13s bits)

20:56 <anonymix007[m]> steev: I'm quite sure there's no need for that. Both WiFi and Bluetooth parts of WCN7851 already work on my x86-64 laptop. Even more, Bluetooth is reported to be working on Vivobook: https://lore.kernel.org/all/20240701-asus-vivobook-s15-v4-0-ce7933b4d4e5@gmail.com/

20:56 <steev> anonymix007[m]: you need the correct gpios

20:57 <steev> saying "it works on x86_64" is pointless though

21:07 <anonymix007[m]> steev: is this bsrc_bt.bin file in some well-known format? I don't really understand what I should do with these bytes after TLMMGPIO string to get gpios

21:10 <steev> it is, afaik, the aci pep file, but there should be more in there than just what you showed. sometimes the numbers are +(or -) 32? i think the number was

21:35 <hexdump01> Nios34[m]: thanks a lot for the galaxy book go paste - i have noted it down and will play around with it / add it as soon as i find some time - sadly that might take a bit

21:36 <hexdump01> Nios34[m]: if you find out anything more about this device, please always highlight me here and maybe post an updated dts if possible

21:54 <anonymix007[m]> steev: that is the full output of xxd. However, there's a separate qcuart8380* directory with BSRC_UART*.bin (with PSTATE, CLOCK, FSTATE, TLMMGPIO and other tags) files. But there doesn't seem to be a reasonable way to extract gpios from them. Do you maybe know one? I can't google anything about this specific format. While it looks like LTV, it's really not clear which bytes in "value" represent gpio number, function and so on

21:55 <steev> i'm not a pro so honestly... i plugged numbers that matched what was in there til something worked (from my email that i linked ` so a lot of this was done via guess work`