05:54 <JensGlathe[m]> Internal speakers are operational on HP Omnibook X14

13:58 <jhovold> craftyguy: yeah, I saw that, thanks. Meant to ask whether that's with or without my "rx meta data" corruption fix?

13:59 <jhovold> also, which compiler do you use?

15:16 <craftyguy> jhovold: that's on 6.14rc7, compiled with gcc 14.2

15:55 <jhovold> ok, sounds like you have a good reproducer for that issue too then :)

15:56 <jhovold> can you try the fix I mentioned and see if it makes any difference at all?

16:54 <craftyguy> jhovold: sure I'll try it... could you remind me where it's posted? :P

16:59 <jhovold> craftyguy: this one:

16:59 <jhovold> https://lore.kernel.org/lkml/20250321145302.4775-1-johan+linaro@kernel.org/

16:59 <jhovold> thanks

17:02 <craftyguy> ok, building now. steev says that the msdu msg still appear with that patch though?

17:16 <jhovold> it does, I've seen it here with too, I'm just curious if it makes any difference for the frequency

20:02 <steev> craftyguy definitely sees it more than i do - 15:02:17 up 1 day, 11:27, 3 users, load average: 0.28, 0.35, 0.35 and a wc -l of msdu_done shows 110 times

20:32 <steev> bamse: one thing i do see pretty early with the flattened usb patches applied is "[ 0.128707] Error: Driver 'dwc3-qcom' is already registered, aborting..."

20:52 <smoorgborg[m]> After splitting the T14s dtb into LCD and OLED, I have to fight the system <tm> every time a kernel is installed or upgraded. All the dtbs in /boot for that kernel, and the others get overwritten with the LCD version, breaking all my kernels. What is the plan to handle this, if any?

20:56 <JensGlathe[m]> My way of handling this (on a hotfix basis) would be to add a local /etc/flash/kernel/machine entry with the right name, and maybe a corresponding db entry pointing to the correct dtb. This should resolve this issue for now.

20:58 <JensGlathe[m]> s///-/

22:17 <craftyguy> steev: ya it's quite clear to me at this point that my x13s is special, heh. it seems to find all the wifi, usb-c, and suspend/resume issues 🙃

22:24 <steev> craftyguy: that is a good thing though, you're finding the issues and we are getting them fixed