https://bugzilla.kernel.org/show_bug.cgi?id=220705
--- Comment #24 from Adrià Vilanova MartÃnez ([email protected]) --- Hi and thanks again! Here are the results (drumroll please...): 1. 0001-PCI-ASPM-Fix-pci_clear_and_set_config_dword-usage.patch: the behavior remains the same (WiFi doesn't work on boot) as expected. 2. disable_clkpm.patch: bingo! This makes WiFi work on boot, so it seems like the signal was disabled early enough. I guess this confirms that the behavior specified in the erratum is the source of the issue, and thus, this would be a BIOS issue rather than a kernel issue. I'll attach a dmesg output for a compilation that includes disable_clkpm.patch. Thanks for going the extra mile and taking a look into coreboot! Regarding testing a custom coreboot compilation, I could look into that. The pixelbook is my main machine, but everything is backed up and it seems like if things go sideways it can be unbricked,[1] so I am comfortable flashing a custom firmware. [1]: https://docs.mrchromebox.tech/docs/support/unbricking/unbrick-suzyq.html -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
