HOW TO: Install and configure lm-sensors

[miegiel]

This is probably a dumb question, but how do set a minimum fan speed? I don't care about the noise (it's minimal), but I do want to cool down the CPU in my laptop.

No experience with that, but try: Search: Keyword(s): fan, control

[coller_girl]

hi i need help with this my fan speeds al over the shop, so i tried installing lm-sensors and got this output... what to do next?

sara@sara-desktop:~$ gksudo sama
sara@sara-desktop:~$ sudo apt-get install lm-sensors
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  libsensors4
Suggested packages:
  sensord read-edid i2c-tools
The following NEW packages will be installed
  libsensors4 lm-sensors
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 188kB of archives.
After this operation, 782kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get: 1 http://gb.archive.ubuntu.com jaunty/main libsensors4 1:3.0.2-2ubuntu4 [63.0kB]
Get: 2 http://gb.archive.ubuntu.com jaunty/main lm-sensors 1:3.0.2-2ubuntu4 [125kB]
Fetched 188kB in 1s (183kB/s)     
Selecting previously deselected package libsensors4.
(Reading database ... 134714 files and directories currently installed.)
Unpacking libsensors4 (from .../libsensors4_1%3a3.0.2-2ubuntu4_i386.deb) ...
Selecting previously deselected package lm-sensors.
Unpacking lm-sensors (from .../lm-sensors_1%3a3.0.2-2ubuntu4_i386.deb) ...
Processing triggers for man-db ...
Setting up libsensors4 (1:3.0.2-2ubuntu4) ...
.udevdb or .udev presence implies active udev.  Aborting MAKEDEV invocation.

Creating config file /etc/sensors3.conf with new version

Setting up lm-sensors (1:3.0.2-2ubuntu4) ...

Processing triggers for libc6 ...
ldconfig deferred processing now taking place
sara@sara-desktop:~$ sudo nano
sara@sara-desktop:~$ chmod 755 mkdev.sh
chmod: changing permissions of `mkdev.sh': Operation not permitted
sara@sara-desktop:~$ sudo chmod 755 mkdev.sh
sara@sara-desktop:~$ 
sara@sara-desktop:~$ sudo ./mkdev.sh
/dev/i2c-0
/dev/i2c-1
/dev/i2c-2
/dev/i2c-3
/dev/i2c-4
/dev/i2c-5
/dev/i2c-6
/dev/i2c-7
/dev/i2c-8
/dev/i2c-9
/dev/i2c-10
/dev/i2c-11
/dev/i2c-12
/dev/i2c-13
/dev/i2c-14
/dev/i2c-15
/dev/i2c-16
/dev/i2c-17
/dev/i2c-18
/dev/i2c-19
/dev/i2c-20
/dev/i2c-21
/dev/i2c-22
/dev/i2c-23
/dev/i2c-24
/dev/i2c-25
/dev/i2c-26
/dev/i2c-27
/dev/i2c-28
/dev/i2c-29
/dev/i2c-30
/dev/i2c-31
sara@sara-desktop:~$ sudo sensors-detect
# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): yes
Module loaded successfully.
If you have undetectable or unsupported I2C/SMBus adapters, you can have
them scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
Do you want to load `i2c-dev' now? (YES/no): yes
Module loaded successfully.

We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.

Next adapter: SMBus I801 adapter at 0500 (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x4e
Probing for `National Semiconductor LM75'...                No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `Dallas Semiconductor DS1621/DS1631'...         No
Probing for `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `Maxim MAX1668'...                              No
Probing for `Maxim MAX1805'...                              No
Probing for `Maxim MAX1989'...                              No
Probing for `Maxim MAX6655/MAX6656'...                      No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `Maxim MAX6659'...                              No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `National Semiconductor LM64'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `ITE IT8201R/IT8203R/IT8206R/IT8266R'...        Yes
    (confidence 6, not a hardware monitoring chip)
Probing for `Fintek F75111R/RG/N (GPIO)'...                 No
Probing for `Fintek F75121R/F75122R/RG (VID+GPIO)'...       No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' at 0x290...     No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Trying family `ITE'...                                      Yes
Found `ITE IT8712F Super IO Sensors'                        Success!
    (address 0x290, driver `it87')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Trying family `ITE'...                                      No

Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): yes
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD K10 thermal sensors...                                  No
Intel Core family thermal sensor...                         No
Intel AMB FB-DIMM thermal sensor...                         No

Now follows a summary of the probes I have just done.
Just press ENTER to continue: yes

Driver `it87' (should be inserted):
  Detects correctly:
  * ISA bus, address 0x290
    Chip `ITE IT8712F Super IO Sensors' (confidence: 9)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue: 

To load everything that is needed, add this to /etc/modules:

#----cut here----
# Chip drivers
it87
#----cut here----

Do you want to add these lines automatically? (yes/NO)yes
sara@sara-desktop:~$

[miegiel]

hi i need help with this my fan speeds al over the shop, so i tried installing lm-sensors and got this output... what to do next?

1st of all, lm-sensors is only a monitoring program, it doesn't control your fan speed.

You can open /etc/modules in a text editor to make sure your it87 is there. If it isn't just add it (you'll need root rights to edit it). The modules file gets read during boot up, to read the sensor's values run sensors in a terminal.

[limejuice]

If you have Intel i7 chip and 1366 mobo, see this thread http://ubuntuforums.org/showthread.php?t=1056681


This said I needed to get lm-sensors 3.1.0 and build it from source. The current version in the Ubuntu repository for 09.04 release is 3.0.2.

However, you only need 3.1.0 to get sensors-detect to recognize the correct modules for you.
Here are the correct modules for i7. This works even with 3.0.2 lm-sensors.

#Chip drivers
coretemp
w83627ehf force_id=0x8860

[Feelin_froggy8877]

I cannot get past "sudo sensors-detect" Sorry, no sensors were detected.
Either your sensors are not supported, or they are connected to an
I2C or SMBus adapter that is not supported. See
http://www.lm-sensors.org/wiki/FAQ/Chapter3 for further information.
If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.

k-dawg@k-dawg-desktop:~$ sudo lshw
k-dawg-desktop
description: Desktop Computer
product: OptiPlex GX270
vendor: Dell Computer Corporation
width: 32 bits
capabilities: smbios-2.3 dmi-2.3 smp-1.4 smp
configuration: administrator_password=enabled boot=normal chassis=desktop cpus=1 power-on_password=enabled uuid=44454C4C-0000-1020-8020-80C04F202020
*-core
description: Motherboard
product: 0CG566
vendor: Dell Computer Corp.
physical id: 0
serial: ..CN1374046O058I.
*-firmware
description: BIOS
vendor: Dell Computer Corporation
physical id: 0
version: A07 (06/26/2006)
size: 64KiB
capacity: 448KiB
capabilities: pci pnp apm upgrade shadowing escd cdboot bootselect edd int13floppytoshiba int5printscreen int9keyboard int14serial int17printer acpi usb agp ls120boot biosbootspecification netboot
*-cpu
description: CPU
product: Intel(R) Pentium(R) 4 CPU 2.40GHz
vendor: Intel Corp.
physical id: 400
bus info: cpu@0
version: 15.2.9
slot: Microprocessor
size: 2400MHz
capacity: 3600MHz
width: 32 bits
clock: 800MHz
capabilities: boot fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts cid xtpr
configuration: id=1
*-cache:0
description: L1 cache
physical id: 700
size: 8KiB
capacity: 16KiB
capabilities: internal write-back data
*-cache:1
description: L2 cache
physical id: 701
size: 512KiB
capacity: 512KiB
capabilities: internal varies unified
*-logicalcpu:0
description: Logical CPU
physical id: 1.1
width: 32 bits
capabilities: logical
*-logicalcpu:1
description: Logical CPU
physical id: 1.2
width: 32 bits
capabilities: logical
*-memory
description: System Memory
physical id: 1000
slot: System board or motherboard
size: 1536MiB
*-bank:0
description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
physical id: 0
slot: DIMM_1
size: 256MiB
width: 64 bits
clock: 333MHz (3.0ns)
*-bank:1
description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
physical id: 1
slot: DIMM_2
size: 512MiB
width: 64 bits
clock: 333MHz (3.0ns)
*-bank:2
description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
physical id: 2
slot: DIMM_3
size: 256MiB
width: 64 bits
clock: 333MHz (3.0ns)
*-bank:3
description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
physical id: 3
slot: DIMM_4
size: 512MiB
width: 64 bits
clock: 333MHz (3.0ns)
*-pci
description: Host bridge
product: 82865G/PE/P DRAM Controller/Host-Hub Interface
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 02
width: 32 bits
clock: 33MHz
configuration: driver=agpgart-intel module=intel_agp
*-pci:0
description: PCI bridge
product: 82865G/PE/P PCI to AGP Controller
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: 02
width: 32 bits
clock: 66MHz
capabilities: pci bus_master
*-display
description: VGA compatible controller
product: NV18 [GeForce4 MX 440 AGP 8x]
vendor: nVidia Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a2
width: 32 bits
clock: 66MHz
capabilities: pm agp agp-3.0 bus_master cap_list
configuration: driver=nvidia latency=248 maxlatency=1 mingnt=5 module=nvidia
*-usb:0
description: USB Controller
product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usb:1
description: USB Controller
product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2
vendor: Intel Corporation
physical id: 1d.1
bus info: pci@0000:00:1d.1
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usb:2
description: USB Controller
product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3
vendor: Intel Corporation
physical id: 1d.2
bus info: pci@0000:00:1d.2
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usb:3
description: USB Controller
product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4
vendor: Intel Corporation
physical id: 1d.3
bus info: pci@0000:00:1d.3
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usb:4
description: USB Controller
product: 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller
vendor: Intel Corporation
physical id: 1d.7
bus info: pci@0000:00:1d.7
version: 02
width: 32 bits
clock: 33MHz
capabilities: pm debug bus_master cap_list
configuration: driver=ehci_hcd latency=0 module=ehci_hcd
*-pci:1
description: PCI bridge
product: 82801 PCI Bridge
vendor: Intel Corporation
physical id: 1e
bus info: pci@0000:00:1e.0
version: c2
width: 32 bits
clock: 33MHz
capabilities: pci bus_master
*-multimedia
description: Multimedia audio controller
product: SB Audigy
vendor: Creative Labs
physical id: 8
bus info: pci@0000:02:08.0
version: 04
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=EMU10K1_Audigy latency=64 maxlatency=20 mingnt=2 module=snd_emu10k1
*-firewire
description: FireWire (IEEE 1394)
product: SB Audigy FireWire Port
vendor: Creative Labs
physical id: 8.2
bus info: pci@0000:02:08.2
version: 04
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=ohci1394 latency=64 maxlatency=4 mingnt=2 module=ohci1394
*-network
description: Ethernet interface
product: 82540EM Gigabit Ethernet Controller
vendor: Intel Corporation
physical id: c
bus info: pci@0000:02:0c.0
logical name: eth0
version: 02
serial: 00:1a:a0:aa:03:0f
size: 100MB/s
capacity: 1GB/s
width: 32 bits
clock: 66MHz
capabilities: pm pcix msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.21-k3-NAPI duplex=full firmware=N/A ip=98.240.112.82 latency=64 link=yes mingnt=255 module=e1000 multicast=yes port=twisted pair speed=100MB/s
*-isa
description: ISA bridge
product: 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: isa bus_master
configuration: latency=0
*-ide:0
description: IDE interface
product: 82801EB/ER (ICH5/ICH5R) IDE Controller
vendor: Intel Corporation
physical id: 1f.1
bus info: pci@0000:00:1f.1
logical name: scsi0
logical name: scsi1
version: 02
width: 32 bits
clock: 33MHz
capabilities: ide bus_master emulated
configuration: driver=ata_piix latency=0
*-disk:0
description: ATA Disk
product: QUANTUM FIREBALL
vendor: Quantum
physical id: 0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: APL.
serial: 052123205633
size: 19GiB (20GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=81108110
*-volume:0
description: Windows NTFS volume
physical id: 1
bus info: scsi@0:0.0.0,1
logical name: /dev/sda1
version: 3.1
serial: 8074442b-808b-9d4a-94dd-c5dfffc703e5
size: 10001MiB
capacity: 10001MiB
capabilities: primary bootable ntfs initialized
configuration: clustersize=4096 created=2009-07-25 11:51:43 filesystem=ntfs label=Microshit state=clean
*-volume:1
description: Extended partition
physical id: 2
bus info: scsi@0:0.0.0,2
logical name: /dev/sda2
size: 9467MiB
capacity: 9467MiB
capabilities: primary extended partitioned partitioned:extended
*-logicalvolume
description: Linux filesystem partition
physical id: 5
logical name: /dev/sda5
logical name: /
capacity: 9467MiB
configuration: mount.fstype=ext3 mount.options=rw,relatime,errors=remount-ro,data=ordered state=mounted
*-disk:1
description: ATA Disk
product: Maxtor 6Y120P0
vendor: Maxtor
physical id: 1
bus info: scsi@0:0.1.0
logical name: /dev/sdb
version: YAR4
serial: Y33YD2BE
size: 114GiB (122GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=000784c4
*-volume:0
description: EXT3 volume
vendor: Linux
physical id: 1
bus info: scsi@0:0.1.0,1
logical name: /dev/sdb1
version: 1.0
serial: 63fc02f9-c191-4ec9-bd2c-0afd3eddd597
size: 4094MiB
capacity: 4094MiB
capabilities: primary bootable journaled extended_attributes large_files ext3 ext2 initialized
configuration: created=2009-07-25 17:56:26 filesystem=ext3 label=AntiX modified=2009-08-30 23:36:45 mounted=2009-08-30 23:36:45 state=clean
*-volume:1
description: Extended partition
physical id: 2
bus info: scsi@0:0.1.0,2
logical name: /dev/sdb2
size: 110GiB
capacity: 110GiB
capabilities: primary extended partitioned partitioned:extended
*-logicalvolume:0
description: W95 FAT32 partition
physical id: 5
logical name: /dev/sdb5
logical name: /media/myshit
capacity: 101GiB
configuration: mount.fstype=vfat mount.options=rw,fmask=0000,dmask=0000,allow_utime =0022,codepage=cp437,iocharset=utf8 state=mounted
*-logicalvolume:1
description: Linux filesystem partition
physical id: 6
logical name: /dev/sdb6
capacity: 2933MiB
*-logicalvolume:2
description: Linux swap / Solaris partition
physical id: 7
logical name: /dev/sdb7
capacity: 2557MiB
capabilities: nofs
*-logicalvolume:3
description: Linux filesystem partition
physical id: 8
logical name: /dev/sdb8
capacity: 3851MiB
*-cdrom
description: CD-R/CD-RW writer
physical id: 2
bus info: scsi@1:0.0.0
logical name: /dev/cdrom
logical name: /dev/cdrw
logical name: /dev/scd0
logical name: /dev/sr0
capabilities: audio cd-r cd-rw
configuration: status=nodisc
*-disk:2
description: ATA Disk
product: WDC WD100EB-00BH
vendor: Western Digital
physical id: 3
bus info: scsi@1:0.1.0
logical name: /dev/sdc
version: 15.1
serial: WD-WMA713523734
size: 9541MiB (10GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=00730072
*-volume
description: EXT3 volume
vendor: Linux
physical id: 1
bus info: scsi@1:0.1.0,1
logical name: /dev/sdc1
version: 1.0
serial: d498af98-c9af-411b-aeb4-4942469e8d9d
size: 9538MiB
capacity: 9538MiB
capabilities: primary bootable journaled large_files ext3 ext2 initialized
configuration: created=2009-07-26 19:03:58 filesystem=ext3 label=Sabayon modified=2009-08-30 23:36:56 mounted=2009-08-30 23:36:55 state=clean
*-ide:1
description: IDE interface
product: 82801EB (ICH5) SATA Controller
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
version: 02
width: 32 bits
clock: 66MHz
capabilities: ide bus_master
configuration: driver=ata_piix latency=0
*-serial
description: SMBus
product: 82801EB/ER (ICH5/ICH5R) SMBus Controller
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 02
width: 32 bits
clock: 33MHz
configuration: driver=i801_smbus latency=0 module=i2c_i801
*-network DISABLED
description: Ethernet interface
physical id: 1
logical name: pan0
serial: 76:45:b1:89:5d:86
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

[jlh68]

On my Laptop, I can only get one temperature to show: ACPI THRM CPU and lmsensors temp1, actually they are both reporting the same thing. I do not get my HDD temp or any other data. I can get my HDD temp by using the following command "sudo hddtemp /dev/sda", so I know it is available. I do get the HDD temp on my desktop.

OK, please help me to get more data from lm-sensors.
thanks

[abdusamed]

can u recreate this thread.. because the thread is old..and mkdev isn't used now.. i REALLY want to slow my fan DOWN in xubuntu 9.04


sensors-detect doesn'[t detect anny sensors what so ever in my old ***** p4.

[miegiel]

can u recreate this thread.. because the thread is old..and mkdev isn't used now.. i REALLY want to slow my fan DOWN in xubuntu 9.04


sensors-detect doesn'[t detect anny sensors what so ever in my old ***** p4.

AFAIK you don't need to run that mkdev script anymore. Just install > detect > add detected sensor to /etc/modules > reboot.

sudo apt-get install lm-sensors
sudo sensors-detect
sudo nano /etc/modules

Also, lm-sensors is just a monitor. So it will only tell you your fan speed and not change the speed. I normally set the fan speed in the BIOS, but not every BIOS gives you the option to change it.

[whitethorn]

AFAIK you don't need to run that mkdev script anymore. Just install > detect > add detected sensor to /etc/modules > reboot.

sudo apt-get install lm-sensors
sudo sensors-detect
sudo nano /etc/modules

Also, lm-sensors is just a monitor. So it will only tell you your fan speed and not change the speed. I normally set the fan speed in the BIOS, but not every BIOS gives you the option to change it.

Once you have lm-sensors installed and after running sensors-detect. When you run sensors if it shows some fan speeds then running pwmconfig might be able to let you control your fan speeds. pwmconfig is pretty straightforward. Afterwards you only need a couple small steps to get fancontrol to start on boot and you can control your fanspeeds. Maybe I should write a howto about it

[abdusamed]

okay..thanks..ill give it a try... and yes.. the module did open.. now to remember what to do