laptop fan control via FreeBSD

[Polytropon]

On Sat, 19 Jan 2013 18:19:39 +0100, Xavier wrote:
> On Sat, Jan 19, 2013 at 05:04:36PM +0100, Polytropon wrote:
> 
> Hi Polytropon,
> 
> > On Sat, 19 Jan 2013 16:55:23 +0100, Xavier wrote:
> > > On Sat, Jan 19, 2013 at 03:13:58PM +0100, Fabian Keil wrote:
> > >
> > > Hi Fabian,
> > >
> > > > Xavier <xavierfreebsdquestions at gmail.com> wrote:
> > > >
> > > > > Is there any way to control the on and off the fan on a laptop using FreeBSD?
> > > >
> > > > It depends on the laptop. On mine it works:
> > > >
> > > > fk at r500 ~ $sysctl -ad | grep fan
> > > > dev.acpi_ibm.0.fan_speed: Fan speed
> > > > dev.acpi_ibm.0.fan_level: Fan level
> > > > dev.acpi_ibm.0.fan: Fan enable
> > > >
> > >
> > > My output of 'sysctl -ad | grep fan' don't show these parameters. Why ?
> > > Because, my BIOS don't support these aparameters ? Another answer ?
> >
> > For laptops, you usually load a kernel module for interfacing
> > with the specific ACPI functions, like acpi_ibm.ko. There are
> > several others, but see "man acpi_ibm" for some impressions.
> >
> 
> Yes, but I have an acer Aspire 5634WLMi, and:
> 
> % ls /boot/kernel/acpi*
> /boot/kernel/acpi_asus.ko               /boot/kernel/acpi_panasonic.ko
> /boot/kernel/acpi_asus.ko.symbols
> /boot/kernel/acpi_panasonic.ko.symbols
> /boot/kernel/acpi_dock.ko               /boot/kernel/acpi_sony.ko
> /boot/kernel/acpi_dock.ko.symbols
> /boot/kernel/acpi_sony.ko.symbols
> /boot/kernel/acpi_fujitsu.ko            /boot/kernel/acpi_toshiba.ko
> /boot/kernel/acpi_fujitsu.ko.symbols
> /boot/kernel/acpi_toshiba.ko.symbols
> /boot/kernel/acpi_hp.ko                 /boot/kernel/acpi_video.ko
> /boot/kernel/acpi_hp.ko.symbols
> /boot/kernel/acpi_video.ko.symbols
> /boot/kernel/acpi_ibm.ko                /boot/kernel/acpi_wmi.ko
> /boot/kernel/acpi_ibm.ko.symbols        /boot/kernel/acpi_wmi.ko.symbols
> 
> I don't have an acer kernel module for ACPI.

Two options:

If you can derive from the documentation of your Acer laotop
if it is _compatible_ to one of the implementations provided
by the system, use that instead.

You can do "trial & error" to see if one of the modules works,
even though the name is different. In worst case, load them
all (by using * wildcard) and check with "kldstat".




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...