having reread your comment, i see where you linked to a package on github that appears to have fixed it for you. It seems like implementing a fancontrol tool,

having reread your comment, i see where you linked to a package on github that appears to have fixed it for you. It seems like implementing a fancontrol tool, and perhaps making a one line edit to /etc/udev/rules.d/60-fan-control.rules so that the tool presets the content as a rule for udevadm to make it controllable for users without sudo. That seems like it might work for your system, maybe for many laptops with similar firmware. This 'closure' instead of engaging with the potential solution might not feel fun when you're proposing a band-aid. However, instead of directing your conversation to the firmware developer, the comment used system76's github repository to directly speak to system76 customers, and try to shame the one developer into 'being motivated' So, I can see the reasoning behind the closure as it has gone off the topic of reporting a bug, does not add details useful for improving development toward a fix of the bug, and proposes an assumed solution which would potentially add more noise to later responses from other users who attempted that solution whom it didn't help which has the potential to add more noise to the diagnostics process for this particular bug. As you say, not a firmaware expert, and i understand the frustration at the lack of explanation from system76 in 'Hidden as off-topic' for your comment, but it's not deleted, anyone who want to read it can click the 'expand' button and read it. Sorry that fan at "0"rpm and the heat spike from that seems to have cooked off your RAM, that really hurts. I would expect that system76 should honor the full extent of the warranty that came with your purchase, if that includes the RAM it would be simply inconvenient, not inconvenient and costly. That has happened to me, not from this kind of firmware driven failure, but lots of time pushing systems to the limit of design has given me maybe too much experience with 'little puffs of blue smoke.' If it's of any relevance, my experience going back 20+ years at this point makes me almost exclusively purchase Kingston RAM. Simply because I have had them honor a no-questions lifetime warranty for sticks of RAM. Even recovered from eWaste, physically damaged, off the floor. If it has the KVM number legible, I've had replacement sticks shipped to me for the cost of postage. Once even had them offer an option to upgrade from DDR to DDR2 as they didn't actually have much DDR "1" in stock, and it was better for me also at the time. It makes me purchase new systems with a minimum of RAM installed, and then swap whatever brand it comes with for matched sets of Kingston after a basic functionality test on arrival. I keep the original as fail-back for warranty / service. Hope your new RAM is performant, and hope the udev solves the issue until the firmware gets fixed.