That isn't BIOS fan management - it is completely handled by the chip itself.
Whatever it is, it seems to be "automatic" - i.e. I don't determine what
needs to be done, but the BIOS/the driver does this "on my behalf",
which is good enough for me, provided I know how to avoid the ACPI
conflict, because I am not about to start playing Russian roulette with
my hardware.
I've spend some time earlier today looking at the ACPI code and it seems
as though the first conflicting region (\_TZ_.IP__ 1) is from the ACPI
thermal driver. I think I could easily deactivate this with
"thermal.off=1". The second region though (\_SB_.PCI0.LPCB.SIO1.RNTR)
is a complete mystery to me.
There are a couple of lines in my dmesg file where these IO regions are
mentioned:
[ 0.117903] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[...]
[ 0.117952] pci 0000:00:00.0: [8086:0bf3] type 0 class 0x000600
[...]
[ 0.203459] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[...]
[ 0.203550] pci_bus 0000:04: resource 4 [io 0x0000-0x0cf7]
So, provided I could avoid the first conflict by using thermal.off=1, I
need to find out what is causing the second one and find out how to
prevent it...
Problem is most likely that the BIOS does not "kick-start" the fan(s),
and the chip does not have a register to set a "start fan" pwm value (other
chips such as the NCT677X do have a register for that purpose).
Yep, that seems to be the case indeed.
So you may
be stuck with your manual method if you want to keep the fan running at speeds
lower than pwm=190.
Would it be possible for such feature to be implemented in the f71882fg
driver? Most of the stuff which is done with my bash script will be very
easy to implement in the driver as it involves nothing more than playing
with the registry values and adding a bit of logic to it. Would that be
possible?
Another option might be to find a fan which starts at lower
pwm values, and/or does not need to be kick-started.
I've had enough problem selecting the fans which suit my needs (i.e.
noise levels, RPM speed, power consumption etc) and I am not prepared to
go through that again, no way!
MZ
_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
