00:19 <steev> not sure if it helps anyone, but this is the dmesg output i got resuming from suspend earlier on 6.9-rc5 and having the wifi shit itself - http://sprunge.us/0INHgo

01:14 <dgilmore> steev: looks like things I've seen before

01:40 <steev> it does not happen here on 6.8

01:55 <konradybcio> I'd be surprised if there were no issues :p

05:30 <albsen[m]> my Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter is acting up. its not loading. modprobe ath11k_pci -r ... and so on I was able to wake it up (only after the machine crashed). the x13s install used to work just fine on my previous x13s (with 5g adapter)

05:30 <albsen[m]> I'm on debian testing

06:02 <albsen[m]> I've checked and it looks like the correct firmware is installed: ls /usr/lib/firmware/ath11k/WCN6855/hw2.1 64%

06:02 <albsen[m]> amss.bin board-2.bin m3.bin regdb.bin

06:35 <albsen[m]> fixed the ath11k_pci loading issue using the most recent firmware from linaro (thx linaro) https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware installed it as described into /lib/firmware and now all is working.

06:52 <Segfault[m]> alright i'm giving up on the SN740 in the X13s, i've tried everything i can think of and it's still giving me random dropouts, i've ordered a drive which uses a phison controller that'll hopefully work better

07:20 <steev> albsen[m]: the latest in linaro is the same as in linux-firmware

07:20 <steev> though

07:21 <steev> debian testing doesn't have that version yet

07:28 <steev> albsen[m]: which kernel btw

07:44 <albsen[m]> <steev> "debian testing doesn't have that..." <- hm, I checked sid ... I have both in my apt but preference is given to testing

07:48 <albsen[m]> <steev> "albsen: which kernel btw" <- 6.7.1-jglathe-20240129

07:48 <albsen[m]> custom build from the repo

07:49 <albsen[m]> this is the latest commit I have in there: commit d7da5073ce3d88a0ed4dc55dd4dc2ae200b41898 (HEAD -> jg/blackrock-v6.7.y, origin/jg/blackrock-v6.7.y)

07:49 <albsen[m]> Date: Thu Jan 25 19:55:14 2024 -0800

07:50 <albsen[m]> for context, this all used to work just fine on my previous x13s (16gb, 5g, touch screen) now I upgrade to (32gb, no 5g, touch screen) and got issues that were resolved with the firmware install

08:02 <Segfault[m]> hey jhovold have you poked at the ec in the x13s at all by any chance? it seems to live at 0x28 on i2c8 and its driver appears to be fully implemented in acpi afaict so far

08:03 <Segfault[m]> i'm tempted to have a play with it and maybe see if i can lower the s2idle power draw at all

08:06 <jhovold> Segfault[m]: no, I haven't but I think konradybcio has poked at it

08:07 <jhovold> it won't help with the s2idle power consumption, though

08:07 <Segfault[m]> ah damn

08:09 <Segfault[m]> travmurav[m]: > * <@travmurav:matrix.org> wonders what does that poor thing even do beyond being a keyboard scanner given all the charging stuff is in dsp firmware and (afaiu?) only allows "online" charging

08:09 <Segfault[m]> i mean as far as i can tell so far the only stuff this i2c endpoint might even control is the keyboard backlight and the little blinking led on the back of the lid lol

08:09 <travmurav[m]> ah kb bl would make sense yeah

08:10 <travmurav[m]> hm on windows the led turns off when the device is off/suspended?

08:10 <Segfault[m]> yeah the led starts flashing slowly

08:10 <Segfault[m]> and it automatically turns off the keyboard backlight

08:10 <travmurav[m]> I'd assume it's just AP_SUSPEND line from the pmic connected to the ec tbh, this is what aspire1 has

08:10 <travmurav[m]> I guess someone who has schematics could confirm that

08:10 <Segfault[m]> ¯\_(ツ)_/¯

08:11 <travmurav[m]> but I'd expect it would do the same on linux when someone fixes stuff that holds the soc from going low pwoer

08:11 <Segfault[m]> i do see an acpi dsm notifying the ec of state changes though so that's why i'm curious

08:12 <travmurav[m]> I think I skimmed at the thing and most of it was wmi stuff?

08:12 <travmurav[m]> not sure which acpi I was looking at but iirc it was x13s

08:12 <travmurav[m]> did someone try to decode wmi blobs to get strings from them?

08:12 <travmurav[m]> on aspire1 there are fields to read the mac address :P

08:14 <Segfault[m]> dunno but around line 3113 of the x13s dsdt.dsl on the aarch64-laptops git repo there's a bunch of calls to SB.I2C9.ECNT, and the function they're in gets called by windows to notify of a bunch of different s0ix related state changes

08:15 <Segfault[m]> they all seem to write different magic bytes to an i2c register

09:16 <Segfault[m]> oh the ec endpoint handles hotkeys too

09:16 <Segfault[m]> it seems like it triggers a gpio interrupt and then you read a register to get the key

09:30 <KieranBingham[m]> Running libinput debug-events (fedora-rawhide, x13s) I get events from 'some' of the function keys, such as volume, brightness, but not all of them. F7, F8, F9, F10, F11, F12 all seem to generate no event (where they are pictured as switch monitor, flightmode, disable camera, phones? and a star?) ... Does anyone know how/why they don't make an event all the way into libevent/wayland? Are they being managed by the bios directly

09:30 <KieranBingham[m]> or such ?

09:31 <KieranBingham[m]> (that is they generate Fx signals, but not the event/signal when fnlock is not enabled)

09:32 <travmurav[m]> probably handled via WMI and not hid-over-i2c like Segfault suggested

09:33 <travmurav[m]> so one would need to write a driver for that to catch the events and present them via a dedicated input device

09:35 <Segfault[m]> i can have a look at it some time soonish, i've somehow borked the linux install on my old ssd though and i don't feel like hacking something together until the new one arrives (and hopefully works unlike the sn740)

09:38 <KieranBingham[m]> aha, I didn't realise the conversation above was actually closely related ;-)

09:45 <Jasper[m]> @konradybcio time to post ec work here

09:50 <Segfault[m]> oh it seems like there's some event system that sends the same codes as acpi thinkpad ecs

09:51 <Segfault[m]> there seems to be stuff related to hotkeys, thermals and some hid helper

09:52 <Jasper[m]> Actually wait I may have Konrad's tree for ec worj

09:52 <Segfault[m]> oh nice that'd be useful

09:53 <Jasper[m]> https://github.com/somainline/linux/commits/topic/ecdumper might only do as described, but there may be some work done otherwise

09:55 <travmurav[m]> tbh I'd assume the "thinkpad" wmi driver in x86 would be compatible with ^^ acpi but pretty obvious it would be challenging to use

09:55 <travmurav[m]> think-lmi.c I think

09:56 <Segfault[m]> i was looking at platform/x86/thinkpad_acpi.c since it seems to have the EC code stuff

09:57 <travmurav[m]> that feels like older stuff to me, dunno if they use both or moved on to wmi only

09:59 <Segfault[m]> i saw reference to someone getting an error from that driver on a T14 so it seems to be getting use on new machines

09:59 <travmurav[m]> I guess can ^F for the pnp ids

09:59 <Segfault[m]> anyway i doubt it'd be super useful here but once i've got a working environment i'm more than willing to throw together a quick PoC driver

10:00 <travmurav[m]> but well, since we use DT, would need to do something like what I did for aspire1 and talk to the ec directly

20:48 <steev> Segfault[m]: https://lore.kernel.org/all/20240315-aspire1-ec-v5-0-f93381deff39@trvn.ru/ fwiw that's what travmurav[m] is talking about

21:55 <Dantheman825[m]> what does the ec stand for in this context?

22:01 <Jasper[m]> embedded controller