That is: it manages to turn them on or off, but not to ramp in between the extremes, so it stays at 100% during the auto-detect phase, until I use ctrl+c to abort (and then the fans stay at 100% until the next reboot…). Unfortunately, it then fails to auto-detect the pwm setting at which the fans stop spinning. I thought that this might be an issue with the fan speed sensor (either directly, or due to it not being supported in some way), but when I boot from a live USB image (also Manjaro), the fan speed is detected and indicated without any issues, and the setup in pwmconfig continues. The fans then keep spinning at 100% until I reboot the machine. When I then run pwmconfig, it starts by spinning the fans up to 100%, (very audibly),īut the fan speed sensor stays at 0, and pwmconfig aborts. I have the case opened, and the fans are indeed not spinning. While trying to find the issue, I ran sensors-detect to find the temperature readings for the GPU, and it found the following:įan1: 0 RPM (min = 0 RPM, max = 3400 RPM)Įdge: +37.0☌ (crit = +110.0☌, hyst = -273.1☌) I have the following problem with my graphics card (Radeon 5500XT):īefore configuring anything manually, the fan speed was handled by the card, but did not exceed 1000/min, which lead to overheat problems (sure took me a while to figure out why games kept knocking out the machine, sometimes, but sometimes not…).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |