xref: /netbsd-src/share/man/man4/aibs.4 (revision 919267d79b0de85197852ed83e6d7dca8e973455)
1.\"	$NetBSD: aibs.4,v 1.10 2020/06/08 20:19:12 sevan Exp $
2.\"	$OpenBSD: aibs.4,v 1.4 2009/07/30 06:30:45 jmc Exp $
3.\"
4.\" Copyright (c) 2009 Constantine A. Murenin <cnst+netbsd@bugmail.mojo.ru>
5.\"
6.\" Permission to use, copy, modify, and distribute this software for any
7.\" purpose with or without fee is hereby granted, provided that the above
8.\" copyright notice and this permission notice appear in all copies.
9.\"
10.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
11.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
12.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
13.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
14.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
15.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
16.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
17.\"
18.Dd June 8, 2020
19.Dt AIBS 4
20.Os
21.Sh NAME
22.Nm aibs
23.Nd ASUSTeK AI Booster voltage, temperature, and fan sensor
24.Sh SYNOPSIS
25.Cd "aibs* at acpi?"
26.Sh DESCRIPTION
27The
28.Nm
29driver provides support for voltage, temperature, and fan sensors
30available as an
31.Tn ACPI
32device on
33.Tn ASUSTeK
34motherboards.
35The number of sensors of each type,
36as well as the description of each sensor,
37varies according to the motherboard.
38.Pp
39The driver supports an arbitrary set of sensors,
40provides descriptions regarding what each sensor is used for,
41and reports whether each sensor is within the specifications
42as defined by the motherboard manufacturer through
43.Tn ACPI .
44.Pp
45The
46.Nm
47driver supports
48.Xr envsys 4
49sensor states as follows:
50.Bl -bullet
51.It
52Voltage sensors can have a state of
53.Sq valid ,
54.Sq critunder ,
55or
56.Sq critover ;
57temperature sensors can have a state of
58.Sq valid ,
59.Sq warnover ,
60.Sq critover ,
61or
62.Sq invalid ;
63and fan sensors can have a state of
64.Sq valid ,
65.Sq warnunder ,
66or
67.Sq warnover .
68.It
69Temperature sensors that have a reading of 0
70are marked
71.Sq invalid ,
72whereas all other sensors are always assumed valid.
73.It
74Voltage sensors have a lower and an upper limit,
75.Sq critunder
76and
77.Sq critover ,
78temperature sensors have two upper limits,
79.Sq warnover
80and
81.Sq critover ,
82whereas fan sensors may either have only the lower limit
83.Sq warnunder ,
84or, depending on the vendor's
85.Tn ACPI
86implementation, one lower and one upper limit,
87.Sq warnunder
88and
89.Sq warnover .
90.El
91.Pp
92Sensor values and limits are made available through the
93.Xr envsys 4
94interface,
95and can be monitored with
96.Xr envstat 8 .
97For example, on an ASUS V3-P5G965 barebone:
98.Bd -literal -offset 2n
99$ envstat -d aibs0
100                     Current  CritMax  WarnMax  WarnMin  CritMin Unit
101    Vcore Voltage:     1.152    1.600                      0.850    V
102     +3.3 Voltage:     3.312    3.630                      2.970    V
103       +5 Voltage:     5.017    5.500                      4.500    V
104      +12 Voltage:    12.302   13.800                     10.200    V
105  CPU Temperature:    27.000   95.000   80.000                   degC
106   MB Temperature:    58.000   95.000   60.000                   degC
107    CPU FAN Speed:       878              7200      600           RPM
108CHASSIS FAN Speed:         0              7200      700           RPM
109.Ed
110.Pp
111Generally, sensors provided by the
112.Nm
113driver may also be supported by a variety of other drivers,
114such as
115.Xr lm 4
116or
117.Xr itesio 4 .
118The precise collection of
119.Nm
120sensors is comprised of the sensors
121specifically utilised in the motherboard
122design, which may be supported through
123a combination of one or more physical hardware monitoring chips.
124.Pp
125The
126.Nm
127driver, however, provides the following advantages
128when compared to the native hardware monitoring drivers:
129.Bl -bullet
130.It
131Sensor values from
132.Nm
133are expected to be more reliable.
134For example, voltage sensors in many hardware monitoring chips
135can only sense voltage from 0 to 2 or 4 volts, and the excessive
136voltage is removed by the resistors, which may vary with the motherboard
137and with the voltage that is being sensed.
138In
139.Nm ,
140the required resistor factors are provided by
141the motherboard manufacturer through
142.Tn ACPI ;
143in the native drivers, the resistor factors
144are encoded into the driver based on the chip manufacturer's recommendations.
145In essence, sensor values from
146.Nm
147are very likely to be identical to the readings from the
148Hardware Monitor screen in the BIOS.
149.It
150Sensor descriptions from
151.Nm
152are more likely to match the markings on the motherboard.
153.It
154Sensor states are supported by
155.Nm .
156The state is reported based on the acceptable range of values
157for each individual sensor as suggested by the motherboard manufacturer.
158For example, the threshold for the CPU temperature sensor is likely
159to be significantly higher than that for the chassis temperature sensor.
160.It
161Support for newer chips in
162.Nm .
163Newer chips may miss a native driver,
164but should be supported through
165.Nm
166regardless.
167.El
168.Pp
169As a result, sensor readings from the actual
170native hardware monitoring drivers
171are redundant when
172.Nm
173is present, and
174may be ignored as appropriate.
175Whereas on
176some supported operating systems
177the native drivers may have to be specifically disabled should
178their presence be judged unnecessary,
179on
180others
181the drivers like
182.Xr lm 4
183are not probed provided that
184.Xr acpi 4
185is configured and the system potentially supports
186the hardware monitoring chip through
187.Tn ACPI .
188.Sh SEE ALSO
189.Xr acpi 4 ,
190.Xr envsys 4 ,
191.Xr envstat 8
192.Sh HISTORY
193The
194.Nm
195driver first appeared in
196.Ox 4.7 ,
197.Dx 2.4.1
198and
199.Nx 6.0 .
200An earlier version of the driver, named
201.Nm aiboost ,
202first appeared in
203.Fx 7.0
204and
205.Nx 5.0 .
206.Sh AUTHORS
207.An -nosplit
208The
209.Nm
210driver was written for
211.Ox ,
212.Dx
213BSD, and
214.Nx
215by
216.An Constantine A. Murenin Aq Lk http://cnst.su/ ,
217Raouf Boutaba Research Group,
218David R. Cheriton School of Computer Science,
219University of Waterloo.
220.An Jukka Ruohonen
221.Aq jruohonen@iki.fi
222later reworked and adjusted the driver to support new
223.Tn ASUSTeK
224motherboards.
225The earlier version of the driver,
226.Nm aiboost ,
227was written for
228.Fx
229by
230.An Takanori Watanabe
231and
232adapted to
233.Nx
234by
235.An Juan Romero Pardines .
236