01:32 <genius1237[m]> Is anyone familiar with why this is happening for me https://github.com/TravMurav/slbounce/issues/10

02:24 <dgilmore> Anyone else find bluetooth broken on the x13s with the latest linux-firmware

02:24 <dgilmore> btmgmt --index 0 public-addr C2:17:05:C6:A0:00

02:24 <dgilmore> Unable to send Set Public Address cmd

02:39 <steev> i'm still on 20250410

02:40 <steev> the bluetooth firmware hasn't been updated since 2025-03-06

02:40 <dgilmore> i downgraded the firmware.. its not that

02:40 <steev> are you using the udev rule?

02:42 <dgilmore> I had a overlay to the bluetooth service that was setting the mac address

03:28 <craftyguy> I think there was a bug recently in bluez that broke bootmac / setting MAC. We backported a fix in pmOS for things that use bootmac. I just updated the x13s port in the OS to use dtbloader so now bootmac isn't required for us 😛

03:30 <craftyguy> https://github.com/bluez/bluez/issues/1319

07:05 <jdb[m]> Sleep / suspend is not totally stable yet on Surface Pro 11

07:05 <jdb[m]> it works when I trigger a few commands manually over a short period of time but I can get a system crash when using the device over a longer period

07:06 <jdb[m]> I'll need to look at dmesg messages to see if I can detect a specific error

10:00 <steveej[m]> is there documentation on using fwupdmgr safely on x13s?

10:24 <steveej[m]> also, i'm wondering if code that i'm using (but didn't write) is still correct for linux 6.16. which is: it extracts graphics firmware from lenovo's n3hdr20w.exe like so: cp -v code\$GetExtractPath\$/*/*.mbn "$out/lib/firmware/qcom/sc8280xp/LENOVO/21BX/. i'm wondering this because on 6.16-rc1 i'm getting a fatal error in initrd about missing "a660_sqw.fw"

10:28 <steveej[m]> turns out it's a non-fatal error and i could actually input the luks password and continue to boot despite the error

18:19 <steev> steveej[m]: https://gitlab.com/TheOneWithTheBraid/x13s-firmware-update/-/merge_requests/1

18:21 <steev> both craftyguy and myself (and someone else iirc) but know know they and myself have done this method

18:25 <steev> fwiw though re: gpu firmware, it's already in the linux-firmware repo, and hasn't been updated on lenovo's site since 2023

18:25 <steveej[m]> steev: thanks for that link. and i do that from my usual linux system?

18:25 <steev> no, you'd do that on the x13s

18:26 <steev> it's just 2 commands (assuming you have the bios file extracted)

18:26 <steveej[m]> that is my usual linux system :-D i mean, i don't have to boot from USB?

18:26 <steev> nope, you just reboot and it installs the update (be sure to be plugged in!)

18:27 <steveej[m]> looks good so far! rebooting.. (hopefully no famous last words)

18:46 <steveej[m]> all good after a reboot too :-)

19:03 <steev> :)

19:09 <deathmist> so it appears MST testing could be on the table again with https://patchwork.kernel.org/project/linux-arm-msm/cover/20250609-msm-dp-mst-v2-0-a54d8902a23d@quicinc.com/ out now, has someone tried it on X1E yet? see some bits also in https://patchwork.kernel.org/project/linux-arm-msm/cover/20250530-dp_mst_bindings-v2-0-f925464d32a8@oss.qualcomm.com/

19:15 <deathmist> actually nvm apparently it wasn't tested over USB DP

19:52 <konradybcio> the dp controller shouldn't be too bothered with what receptacle houses the signal lines

20:37 <bamse> konradybcio: there's some differences depending on the HPD (hotplug) signal coming over a physical GPIO straight into the DP controller, or via the tcpm...but beyond that, i believe you're correct

22:52 <genius1237[m]> On my x1p42, launching a VM with KVM crashes unless I have this boot arg `id_aa64mmfr0.ecv=1`. This was pointed out to me by kuruczgy . Does anyone know what this does?

22:54 <genius1237[m]> *crashes the host unless the host is booted with that arg

22:57 <HdkR> Does the VM try using ECV but the host disables it for some reason?

22:58 <HdkR> so booting the VM with ecv=0 but the host with nothing also worksaround it?

22:58 <konradybcio> see commit 358dd4a9bdac63a0a8fb13773bfce6f599e25433

22:59 <konradybcio> although i would assume =0 would be the fix..

23:00 <HdkR> hah, wacky.

23:09 <kuruczgy[m]> Haha love a nice snarky commit message :D

23:09 <kuruczgy[m]> So I gather that the bug is in the EL3 firmware, is that something that will ever have a chance of getting fixed?