Thanks for the quick reply and your help. Highly appreciated. I tried out the two angles of attack in order to fix the problem. As I'm new to Linux, I will try to describe the issues and what happened to the best of my abilities. So bear with me if some things are a bit off or don't describe the problems in the correct terms.
What I have tried so far: 1. Installing and using Frank Crawford's it87 driver. Sadly, the driver is till not working since it - as it seems - doesn't have a valid cryptographic signature and thus is rejected by safe boot and the Linux kernel. While some succesfuld attempts of reading the correct fan rpm values with the "sensors" command in the terminal could be made, the driver didn't alleviate nor fix the ongoing issue with the EC-failsafe kicking in which usually happens 20-30 minutes after booting into Linux Mint Cinnamon. 2. I followed your advice to update the BIOS for my X870 AORUS ELITE WIFI7 (Rev. 1.1) motherboard and was able to successfully flash and update to the latest BIOS version, the previous "F12", to the latest "F13g" under this link --> https://www.gigabyte.com/Motherboard/X870-AORUS-ELITE- WIFI7-rev-10-11/support#Support-Bios However, the update didn't fix the problem nor did changing the fan speed curve manually directly in the BIOS settings. The issue persists and time and again, the fans run on the maximum speed level. Which brings me to the final conclusion which is, that I currently only see two solutions to this issue... a) Seemingly, Linux Mint isn't compatible with my current hardware setup and as such or until there will be some kernel/driver, which does, the only option if i want to keep using an Open Source OS is to find another Linux distro, that actually does work with this hardware setup without triggering the aforementioned fan issues. Problem is, that I don't know if that OS actually exists or if someone knows, which one to choose if there is any at all. b) If option a) is not feasible, then I'll have no choice but to go back to Windows. I'm aware of the fact that you are just trying to help out and are probably just a volunteer on this forum, so don't take the following personal. But in part, I am writing this report in the hopes of addressing the actual Ubuntu/Mint developers and other involved parties behind this project as to make them both aware of the issue in the first place as well as to get them to create a fix for this problem. Since April 2026, I have ran Linux Mint without any of these issues on my brand new pc, which I mainly use for high-end tasks - primarily gaming, 3D-modeling etc. as well as some more menial everyday tasks. Therefore, I am not only puzzled but deeply irritated about the fact, that one simple kernel update basically breaks the whole previous stability, which in fact - was - possible throughout a period of more than half a year. That strongly indicates that there isn't any deeper check on what hardware the kernel actually affects before release, which can create the possibility of rendering the entire system useless - as is the case here. This report is currently listed under "Importance" as "Undecided" but my take is, that this should have been listed as having the highest priority right from the start and be looked into right away. Although I know, that this isn't a direct security-bug in the OS, this is an - extremely - serious issue that affects the actual use of the hardware (nevermind the fact that the OS might still function without any problems during the former). Having fans suddenly blast away on maximum speed after only 30 minutes without any break nor any end in sight until a complete shutdown (after which the process repeats itself) is both indefensible, untenable and outright unacceptable. For one, the noise is so loud (akin to the decibel levels of my vacuum-cleaner), that neighbors or myself are unable to neither sleep, work, game nor do anything else for that sake at say, 3. am. in the morning. For the other, electricity consumption is completely unhinged and with the current energy prices, will ran rampant and out of control while at the same time, there isn't an actual need for cooling this much at all. And last but not least, the fans, bearings and other moving parts will wear and tear within a short period of time if this issue persists and is left unchecked. Also, dust sucked into the system and the moving parts will accumulate and settle on the motherboard, RAM, NVME, in the bearings of the fans and clog other parts of the system as well as age the entire hardware in no time. So, while I am trying to be extremely diplomatic here in choosing my words, I will say that if anybody in the Open Source community believes, that this is acceptable and that users just have to live with these type of serious bugs and hardware-problems instead of doing something about it, then that is not only unacceptable but outright insane. This should be fixed on the highest level and urgency. Although I understand the predicament, that the chipmakers aren't very forthcoming in providing the Open Source community with the datasheets or code, that isn't and never should be the average end user headache, when simply choosing, installing, and running an OS or alternatively, they should be warned about the potential for those issues before installing the system. I am sincerely and wholeheartedly trying to support the Open Source community - in part by attempting to shift away from a large Redmond- based company - but if this is the present state of affairs, then that'll just prove to be impossible. And the only logic consequence of these persistent hardware bugs will be that if those issues persist and aren't fixed, then I'll have to go back to the aforementioned scenario I am trying to get away from - which would be a loss for everyone involved. Free software and volunteers or not - you cannot use an OS, that doesn't function correctly on all the levels required. Below, I'm adding a more technical overview on what has been tried out until now... Update on troubleshooting steps and system status: - Attempted to load Frank Crawford's it87 hardware monitoring driver. The module was rejected by the Linux kernel due to Secure Boot and an invalid cryptographic signature. Although temporary terminal sensor readings could occasionally be achieved, it did not resolve the underlying EC-failsafe fan issue. - Successfully flashed the motherboard BIOS from version F12 to the latest F13g (Rev. 1.1) following the official vendor guidelines. - Tested multiple kernel versions up to the current 7.0.0 branch (including testing newer kernel iterations via the Linux Mint Kernel Manager), but the EC-failsafe behavior under sustained loads persists. - Configured and verified memory speeds to run stably at 6000 MT/s using the EXPO profile via dmidecode verification. - Implemented and evaluated environment configurations including GRUB parameters (such as acpi_enforce_resources=lax) and manual PWM fan curves directly in the BIOS Smart Fan 6 utility, none of which prevented the Embedded Controller from reverting to 100% failsafe mode after approximately 30 minutes of operation. Looking forward to a reply. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2173636 Title: ITE Super I/O chip (IDs 0x8696 / 0x8883) unsupported on Gigabyte X870 AORUS ELITE WIFI7, causing sensor read-out failures and erratic maximum fan speed behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173636/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
