[UPDATE] A solution to issue #1 has been found:
I just wanted to provide this update in case it might be helpful to others. This solution may have already been posted in these forums elsewhere. I know that I had read it a couple of times during my web searches about the issue, but I didn't understand the fix at the time.
As described in the issue below, when you manually set the fans to a percentage speed, it doesn't permanently save to the onboard memory. In order to ensure that the fans don't spin up to 100% on boot, you have to set a 'failsafe speed' for all of the fans. Create a software sensor that references a real sensor. Then set the 'failsafe speed' to something reasonable. I went with 35%, but this build is packed with 140s. Then save the settings as a profile (not sure if this step is necessary, but it can't hurt). The fans should now run at the failsafe speed upon boot until the Aquasuite service or your preferred software takes over control. If you are using a different software for fan management, be sure to disable the Aquasuite service from startup to avoid any potential conflicts.
Hi, did you have to set the "failsafe speed" via Aquasuite in Windows, or is it possible to configure it from linux as well?
Also, do you use the direct PWM control via CoolerControl in linux, or do you rely on the Quadro's own temp sensor readings and fan curve settings?
What I'm getting at is whether the
curve[1-8]_power_fallback settings (or something else) mentioned
here can be used for the "failsafe speed" while the CoolerControl then sets its own speeds based on its configured curves and sensor readings.
I'm thinking about getting the Quadro since my mobo's fan controller is not fully supported in linux. But I want to be sure it will work as expected before I make the purchase.