Fan not detected is back, although the fan works on its own, without needing to usr fw-fanctrl.
I have tried resetting the bios to defaults and resetting the ec, next will try a mainboard reset and force reinstalling the bios. I will take a look to see if there are official instructions for the 13" 13th gen board.
If those fail, back to Support.
Though not enjoyable, have you tried messing around with the cable and connectors to the fan? It might be a bad sensor on the fan too or the cable has a bad pin. Just a thought to try. Intermittent issues are some of rhe hardest.
Thanks. I had re-connected the fan. I just finished taking the machine apart, performing the chassis-intrusion mainboard reset (which I honestly am not sure worked, but oh well), draining power from the battery, and reinstalling the bios. I rebooted after the mainboard reset/power drain, and still got the fan not found alert.
Reinstalling the bios has resulted in the alert no longer being present, which is nice. The bios installer did not check if it was reinstalling the same version, it just ran. It also will happily run in a loop, so to anyone installing it, sit at the machine and watch, then remove the USB drive (I used the EFI installer) after the update is complete - it looks like it is a two stage updater, BIOS/EC/PD1, then a second stage for the ME. It likely would be best to have that updater check the version present before installing, with an override flag that can be used to reinstall the same version.
Happy not to get the seemingly spurious alert at boot any longer. This all started back up after I stupidly pulled the expansion card that the system was booted from, and then had to hold the power button down to force the system to shut down. Oops. Surprising that it somehow retriggered that alert, though.
Replying to myself here - the BIOS update prevents the spurious(?) alert from showing at boot until the machine is powered off - presumably under the hood, until an ec reset happens.
So, I need to open another Support case and figure out if I do in fact have a hardware issue, if this can be handled by a yet-to-be-released BIOS update, or what.
Oh no! That is frustrating to hear. Definitely open another support ticket so they are aware of the issue and what was tried. There is a GitHub firmware tracker too for Framework. Might be worth starting an issue there so they can investigate it further or maybe others can chime in if they have had a similar issue. This is presuming that support determines if it is NOT a hardware issue.
Let us know how it turns out!
Good thought re github - will take a look. I did open a ticket with Support. Fortunately the machine is and has been operating normally other than the alert at boot, so it’s a minor annoyance for now. It will be interesting to find out what the root cause was. I will update here once that has been determined.
I’ve got reply from support confirming this is a known issue (they only say they’ll “work on a software solution”, but didn’t say it’s a “software issue”).
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.