Hi Ohno On Thu, Jun 20, 2024, at 9:10 AM, Yutaro Ohno wrote: > Hi, Mark. > > On Wed Jun 19, 2024 at 8:28 AM JST, Mark Pearson wrote: >> We're doing Linux enablement on the T14 G5 right now - and if this is an issue in the Lenovo FW I would rather fix it there instead of introducing a quirk into the kernel that might later need to be removed. This platform is getting full Linux support. > > That sounds wonderful! I agree that my change is more of a workaround solution. > >> I'd like to collect some debug details from you (if preferred you can ping me off thread using this email address): > > Sure. But first, please note that my machine is AMD, not Intel. Ooops - my bad! Thanks for the clarification. > >> - Can I get your BIOS, EC and ME versions (easiest is to get these from the BIOS setup screen - F1 during early boot) > > - BIOS: R2LET23W (1.04) > - EC: R2LHT18W (1.01) > - ME: Not applicable, as my machine is AMD, not Intel. Thanks > >> - Get a report from running the Intel S0ix test tool - https://github.com/intel/S0ixSelftestTool. Run it with the -S option > > It may not work as my machine is not Intel, but here's the output: <snip> Yeah - that won't work. The AMD test tool is here: https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py Can you try that please? > >> - There is a known issue if the ethernet is plugged in on this system that Intel are working on - can you confirm if you're using wired networking please? > > I haven't used the ethernet on my machine. It's not plugged in. > >> - Do you have WWAN enabled? If you have it can you try with WWAN disabled. > > No, I don't. My machine doesn't have a WWAN module. > One more question - which Wifi module do you have? The Qualcomm NCM825 Wifi7 device still has a lot of problems (it's currently the main thing gating our Linux certification of the platform). >> I'll also highlight that Linux enablement is not complete on this platform yet, so some patience might be needed. > > Sure! > > Please let me know if there's anything else I can do. > Thanks for the details. I've created internal ticket LO-3140 for tracking and we'll see if we can reproduce Mark
