02:27 <bamse> craftyguy: successfully as in come back alive, or as in consume very little power when doing so?

02:28 <bamse> steev: last i tested the problem was still there

02:29 <steev> moot point now... i dunno what is up with my flex5g but as soon as the lenovo screen shows, it immediately reboots

03:28 <freekurt[m]> After unplugging my x13s from its external monitor today it started acting strange so I turned it off. Upon reboot it went to the normal screen to enter in my encrypted password. The keyboard wasn't responsive though, so I couldn't type it in. Also when I plugged in the power cable the red indicator light didn't come on. When I held down the power button the computer wouldn't turn off. I ended up taking the bottom off the computer

03:28 <freekurt[m]> and disconnecting the battery to get the thing to turn off. When I turned it back on everything was normal.

04:07 <robclark> freekurt[m]: iirc the x13s had a pinhole on the bottom that could reset the EC? I might be confusing the x13s with something else..

04:08 <robclark> maybe steev could confirm?

04:10 <steev> i think i've heard that, but i haven't tried it myself

04:11 <steev> i mean it does have a pinhole next to the middle screw

04:52 <freekurt[m]> Hopefully there isn't a next time, but if there is I will try the pinhole.

04:53 <freekurt[m]> Had no idea that it might be an EC reset.

05:49 <craftyguy> bamse: successful as in, come back alive. it seems to lock up pretty hard, where even magic sysrq keys do nothing and I have to force it off by holding the power button

05:50 <craftyguy> (magic sysrq is enabled and works fine normally)

05:51 <craftyguy> also, ya the x13s has a pinhole on the bottom that resets the EC. I have to do this sometimes when the trackpoint goes out to lunch and never comes back

05:58 <valpackett> do all thinkpads have an ec reset button?? 0.o my amd thinkpad sometimes has the keyboard stuck in the ec (keeps typing the same key as if it was never released), i was curing that with a suspend-resume

06:04 <valpackett> meanwhile in x1e land we really need to solve the mysterious random freeze >_< i might have to still use the aforementioned thinkpad for running live events because the last thing i want is to reboot in the middle of an event and lose recordings etc x_x

06:08 <steev> sometimes resetting the ec is like, 30-60 seconds of holding down the power button

06:18 <krzk> valpackett: what random freezes do you experience? I wonder if this is the same as me - freeze of entire UI and then reboot after 3 secs - I have it all the time, every 1 hour, sometimes every minute on my T14s which makes this X1E totally unusable, just junk :/

06:31 <albsen[m]> krzk: which t14s variant do you have? I have the 64gb ram oled and it does that. the 32gb variant is supposed to be much better.

06:33 <krzk> 32

06:33 <krzk> 32 LCD. One day was reboot every login/boot, till I let it to sit for 10 minutes in the console before logging in :/

06:51 <albsen[m]> thats odd, which distro?

06:51 <albsen[m]> and kernel version

06:57 <krzk> Ubuntu, all kernels starting from v6.14

06:58 <krzk> Why odd? Considering how buggy the firmware is - still 10% fails, even with Johan's workaround, to properly exit uefi services and boot fails - no wonder everything else fails

06:58 <albsen[m]> u dual boot and keep the firmware up to date?

06:58 <krzk> No, I don't dual boot, but I updated the firmware to latest

06:59 <krzk> issue started on old firmware and update did not help, that was the first thing to check

06:59 <albsen[m]> its odd because even my t14s that has 64gb and oled was (with all workarounds) semi usable ... only crashing when pushing memory usage close to the 32gb

07:00 <krzk> well, was working fine for 2 months and this started... and since then I removed all known changes I did and still see it, so indeed that's odd

07:01 <albsen[m]> ah, ok. maybe they broke something in the new firmware

07:03 <krzk> issue was on old firmware as well

07:03 <krzk> when it started to appear I performed update

07:37 <jdb[m]> krzk: valpackett: I'm quite new to x1e land but I haven't faced a mysterious random freeze yet (on SP11 / Denali)

07:39 <jdb[m]> What's the (expected) status of suspend / s2idle on x1e btw? Normally working but consuming too much power? Or can it be device-specific at this stage?

08:02 <JensGlathe[m]> It feels like device specific. The HP X14 can be closed, enters a deeper sleep after a while, you open it after a day or so, it comes up. The ThinkBook 16 doesn't seem to like the deeper sleep, but suspend with open lid works well. Ah well, the GPU is not really supported yet, this could be the difference. And maybe the hdmi bridge

08:09 <valpackett> jdb[m]: suspend generally works great (for now: as long as you make sure you have https://github.com/jhovold/linux/commit/f079d098b5703002e5e78f14356f2fdce0b1c9c2 as there was a weird bug introduced in 6.15 that kills nvme on resume from deep suspend) and yeah it's still not as deep as we'd like

08:11 <valpackett> krzk: definitely not every 1 hour. had 4 days of uptime just fine

11:06 <albsen[m]> I'm on 6.14.10 for my x13s and suspend works just fine. cat /sys/power/state says: "freeze mem disk" and I've not configured anything special so it will use the systemd default. which might be mem.

12:09 <steveej[m]> valpackett: what's the dependency (just more work hours, missing firmware blob, etc.) for the remainder of the deep sleep functionality?

12:22 <albsen[m]> I'm not sure if the x13s has deep sleep functionality. t14s with xelite might

14:00 <dgilmore> steev: a technician will apparently be here between 10-12 to replace the screen

17:00 <dgilmore> Less than 24 hours later and it's replaced

18:08 <Lirox> Hi! I'm trying to get Linux running on the Samsung Galaxy Book S (Snapdragon 8cx / Windows on ARM). I've tested various distros (Debian, Fedora, Ubuntu, Armbian…), but most don’t boot at all. Archboot gets the furthest and reaches "EFI stub: Exiting boot services…" before freezing. The Debian Installer does boot, but there’s no keyboard or Wi-Fi – so I assume some critical drivers (input, WLAN, may

18:09 <Lirox> People had it working in 2021 with a custom kernel/initrd by pierro78, but the setup doesn’t seem to work anymore. References: https://github.com/aarch64-laptops/debian-cdimage/issues/16 https://github.com/pierro78/galaxybooks8cxkerneldeb/releases/tag/v0.1 I’d be grateful for any suggestions: updated kernel/DTB/initramfs, working branches, or boot args. Thanks!

18:18 <valpackett> steveej[m]: i thiiiink it's more work hours but very preferably from someone with internal knowledge

18:23 <valpackett> albsen[m]: /sys/power/mem_sleep not state is the part that says "deep or not deep", on x1e it defaults to deep

18:27 <Lirox> @steveej Thank you for your honesty. I’ve been working on this device for about 6 months. It’s a lot of work because Samsung uses custom firmware and they are very strict about the hardware lines. If there are any experts here, it would be great to get some feedback or advice.

18:53 <steev> dgilmore: wow that was quick

18:54 <dgilmore> steev: indeed. They overnighted the new screen to the tech and she came and replaced it this morning. Makes me glad I opted for the top option

18:57 <Lirox> Does anyone know if there is a newer version than https://github.com/aarch64-laptops/debian-cdimage/releases/tag/v0.4 available?

19:05 <valpackett> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=4ba960e75bab4a4e5f328d22a7a9b253abd3c214 hmmm is the pcie global irq related to the nvme wakeup issue caused by the irq related pcie change we reverted?

21:01 <jdb[m]> lirox: the official Debian images exist for arm64 / aarch64, that's what is recommended to install on some "supported" models

21:01 <jdb[m]> https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s

21:05 <jdb[m]> This is the guide for the Thinkpad X13s based on the newer sc8280xp (and not the sc8180x / Snapdragon 8cx)

21:06 <jdb[m]> But you'll have to build and load the .dtb file matching your model (or a similar one)

21:08 <jdb[m]> That's the current difficulty (pain?) with devicetree-based devices and Linux, it doesn't scale automatically to other devices

21:08 <jdb[m]> (but a lot can be reused)