diff options
Diffstat (limited to 'static/netbsd/man4/aibs.4 3.html')
| -rw-r--r-- | static/netbsd/man4/aibs.4 3.html | 143 |
1 files changed, 0 insertions, 143 deletions
diff --git a/static/netbsd/man4/aibs.4 3.html b/static/netbsd/man4/aibs.4 3.html deleted file mode 100644 index be7783b4..00000000 --- a/static/netbsd/man4/aibs.4 3.html +++ /dev/null @@ -1,143 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">AIBS(4)</td> - <td class="head-vol">Device Drivers Manual</td> - <td class="head-rtitle">AIBS(4)</td> - </tr> -</table> -<div class="manual-text"> -<section class="Sh"> -<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1> -<p class="Pp"><code class="Nm">aibs</code> — <span class="Nd">ASUSTeK AI - Booster voltage, temperature, and fan sensor</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1> -<p class="Pp"><code class="Cd">aibs* at acpi?</code></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <code class="Nm">aibs</code> driver provides support for - voltage, temperature, and fan sensors available as an ACPI device on ASUSTeK - motherboards. The number of sensors of each type, as well as the description - of each sensor, varies according to the motherboard.</p> -<p class="Pp">The driver supports an arbitrary set of sensors, provides - descriptions regarding what each sensor is used for, and reports whether - each sensor is within the specifications as defined by the motherboard - manufacturer through ACPI.</p> -<p class="Pp">The <code class="Nm">aibs</code> driver supports - <a class="Xr">envsys(4)</a> sensor states as follows:</p> -<ul class="Bl-bullet"> - <li>Voltage sensors can have a state of ‘valid’, - ‘critunder’, or ‘critover’; temperature - sensors can have a state of ‘valid’, - ‘warnover’, ‘critover’, or - ‘invalid’; and fan sensors can have a state of - ‘valid’, ‘warnunder’, or - ‘warnover’.</li> - <li>Temperature sensors that have a reading of 0 are marked - ‘invalid’, whereas all other sensors are always assumed - valid.</li> - <li>Voltage sensors have a lower and an upper limit, ‘critunder’ - and ‘critover’, temperature sensors have two upper limits, - ‘warnover’ and ‘critover’, whereas fan sensors - may either have only the lower limit ‘warnunder’, or, - depending on the vendor's ACPI implementation, one lower and one upper - limit, ‘warnunder’ and ‘warnover’.</li> -</ul> -<p class="Pp">Sensor values and limits are made available through the - <a class="Xr">envsys(4)</a> interface, and can be monitored with - <a class="Xr">envstat(8)</a>. For example, on an ASUS V3-P5G965 - barebone:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>$ envstat -d aibs0 - Current CritMax WarnMax WarnMin CritMin Unit - Vcore Voltage: 1.152 1.600 0.850 V - +3.3 Voltage: 3.312 3.630 2.970 V - +5 Voltage: 5.017 5.500 4.500 V - +12 Voltage: 12.302 13.800 10.200 V - CPU Temperature: 27.000 95.000 80.000 degC - MB Temperature: 58.000 95.000 60.000 degC - CPU FAN Speed: 878 7200 600 RPM -CHASSIS FAN Speed: 0 7200 700 RPM</pre> -</div> -<p class="Pp">Generally, sensors provided by the <code class="Nm">aibs</code> - driver may also be supported by a variety of other drivers, such as - <a class="Xr">lm(4)</a> or <a class="Xr">itesio(4)</a>. The precise - collection of <code class="Nm">aibs</code> sensors is comprised of the - sensors specifically utilised in the motherboard design, which may be - supported through a combination of one or more physical hardware monitoring - chips.</p> -<p class="Pp">The <code class="Nm">aibs</code> driver, however, provides the - following advantages when compared to the native hardware monitoring - drivers:</p> -<ul class="Bl-bullet"> - <li>Sensor values from <code class="Nm">aibs</code> are expected to be more - reliable. For example, voltage sensors in many hardware monitoring chips - can only sense voltage from 0 to 2 or 4 volts, and the excessive voltage - is removed by the resistors, which may vary with the motherboard and with - the voltage that is being sensed. In <code class="Nm">aibs</code>, the - required resistor factors are provided by the motherboard manufacturer - through ACPI; in the native drivers, the resistor factors are encoded into - the driver based on the chip manufacturer's recommendations. In essence, - sensor values from <code class="Nm">aibs</code> are very likely to be - identical to the readings from the Hardware Monitor screen in the - BIOS.</li> - <li>Sensor descriptions from <code class="Nm">aibs</code> are more likely to - match the markings on the motherboard.</li> - <li>Sensor states are supported by <code class="Nm">aibs</code>. The state is - reported based on the acceptable range of values for each individual - sensor as suggested by the motherboard manufacturer. For example, the - threshold for the CPU temperature sensor is likely to be significantly - higher than that for the chassis temperature sensor.</li> - <li>Support for newer chips in <code class="Nm">aibs</code>. Newer chips may - miss a native driver, but should be supported through - <code class="Nm">aibs</code> regardless.</li> -</ul> -<p class="Pp">As a result, sensor readings from the actual native hardware - monitoring drivers are redundant when <code class="Nm">aibs</code> is - present, and may be ignored as appropriate. Whereas on some supported - operating systems the native drivers may have to be specifically disabled - should their presence be judged unnecessary, on others the drivers like - <a class="Xr">lm(4)</a> are not probed provided that - <a class="Xr">acpi(4)</a> is configured and the system potentially supports - the hardware monitoring chip through ACPI.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE - ALSO</a></h1> -<p class="Pp"><a class="Xr">acpi(4)</a>, <a class="Xr">envsys(4)</a>, - <a class="Xr">envstat(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">aibs</code> driver first appeared in - <span class="Ux">OpenBSD 4.7</span>, <span class="Ux">DragonFly 2.4.1</span> - and <span class="Ux">NetBSD 6.0</span>. An earlier version of the driver, - named <code class="Nm">aiboost</code>, first appeared in - <span class="Ux">FreeBSD 7.0</span> and <span class="Ux">NetBSD - 5.0</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp">The <code class="Nm">aibs</code> driver was written for - <span class="Ux">OpenBSD</span>, <span class="Ux">DragonFly</span> BSD, and - <span class="Ux">NetBSD</span> by <span class="An">Constantine A. - Murenin</span> - ⟨<a class="Lk" href="http://cnst.su/">http://cnst.su/</a>⟩, - Raouf Boutaba Research Group, David R. Cheriton School of Computer Science, - University of Waterloo. <span class="An">Jukka Ruohonen</span> - ⟨jruohonen@iki.fi⟩ later reworked and adjusted the driver to - support new ASUSTeK motherboards. The earlier version of the driver, - <code class="Nm">aiboost</code>, was written for - <span class="Ux">FreeBSD</span> by <span class="An">Takanori Watanabe</span> - and adapted to <span class="Ux">NetBSD</span> by <span class="An">Juan - Romero Pardines</span>.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">June 8, 2020</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |