Issue #445 has been updated by Martin Roth.
It's entirely possible that coreboot is violating some of the power-on timings of that wifi module. This could cause it to work some of the time, but fail at other times.
To fix this, or determine if this actually is a problem, someone would have to grab the datasheet for the the chip on that module and see what the timings are supposed to be. There are probably GPIOs to control the various power and enable signals to the chip. We'd have to see when those are actually being set to tell if the spec is being violated.
This is entirely a guess on my part based on the work I've done on chromebooks getting the power-on timings for the PCIe slots to meet the specs for all of the modules we were using on a build.
It's also possible as you mentioned that there's just something wrong with your individual module that's causing it to be flaky.
---------------------------------------- Bug #445: Thinkpad X200 wifi issue https://ticket.coreboot.org/issues/445#change-1362
* Author: Masc Masc * Status: New * Priority: Normal * Target version: none * Start date: 2023-01-06 * Affected versions: 4.18 ---------------------------------------- Compiled coreboot latest revision from source and built a coreboot rom image for X200 with SeaBIOS (also tried with Grub as a payload). The laptop beeps and the power LED flashes at startup and the wifi card does not work (cannot enable wifi in OS). The operating system is Debian Bullseye and the wifi card is an Atheros AR5B95. The OS boots normally, but no wifi is available. The wifi card has been tested and works fine with latest stable libreboot release.
---Files-------------------------------- config (18.1 KB) cbmem.txt (42.4 KB) dmesg.txt (62.8 KB) lspci_nn_libreboot.txt (2.42 KB) lspci_tv_libreboot.txt (1.47 KB) lspci_vvvxx_libreboot.txt (31.1 KB) lspci_nn_coreboot.txt (2.42 KB) lspci_tv_coreboot.txt (1.48 KB) lspci_vvvxx_coreboot.txt (31.6 KB)