[lm-sensors] Can't load smsc47m1: no such device

[lm-sensors] Can't load smsc47m1: no such device

[Williams, Kevin C]

My fan speed is at the highest possible speed when booted into linux on
this system(same as speed during POST).  Load is 0.00 and x-windows is
not installed. Winxp has a no audible fan noise unless doing high
computation but never as high as with linux.  So, I decided to figure
out how to tweak the fan speed.

'sensors-detect' found SMSC 47M15x/192 and I found that in the drivers
section of the website, I(think) can use the 'smsc47m1' driver.  So I
tried it:
~]# modprobe smsc47m1 force_addr=0x0800
FATAL: Error inserting smsc47m1
(/lib/modules/2.6.11-1.1369_FC4smp/kernel/drivers/i2c/chips/smsc47m1.ko)
: No such device

'dmesg' has no reference of the smsc47m1 device, but it was found at
0x800 by sensors-detect with a cofidence of 9. Output of sensors-detect
is below.  I should mention that I had  run it before and 2 modules are
already loaded but they are just give me info about my RAM.  


~]# /usr/sbin/sensors-detect

This program will help you determine which I2C/SMBus modules

<snip>

 We can start with probing for (PCI) I2C or SMBus adapters.
 You do not need any special privileges for this.
 Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB ICH5
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported 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.
 If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.

 We are now going to do the adapter probings. Some adapters may hang
halfway
 through; we can't really help that. Also, some chips will 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. That often
 includes address 0x69 (clock chip).

Next adapter: SMBus I801 adapter at 0500
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
Client found at address 0x2d

<snip - failed probings>

Client at address 0x50 can not be probed - unload all client drivers
first!
Client at address 0x52 can not be probed - unload all client drivers
first!
Client found at address 0x68
Client found at address 0x69

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): y
<snip - failed probings>

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): y

<snip failed probings>

Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
  Success... found at address 0x0800

<snip failed probings>

Do you want to scan for secondary Super I/O sensors? (YES/no): y

<snip failed probings>

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

Driver `to-be-written' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0800 (Busdriver `i2c-isa')
    Chip `SMSC 47M15x/192 Super IO Fan Sensors' (confidence: 9)


 I will now generate the commands needed to load the I2C modules.
 Sometimes, a chip is available both through the ISA bus and an I2C bus.
 ISA bus access is faster, but you need to load an additional driver
module
 for it. If you have the choice, do you want to use the ISA bus or the
 I2C/SMBus (ISA/smbus)? ISA

To make the sensors modules behave correctly, add these lines to
/etc/modprobe.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
# no driver for SMSC 47M15x/192 Super IO Fan Sensors yet
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----

WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really
should
try these commands right now to make sure everything is working
properly.
Monitoring programs won't work until it's done.

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.

'sensors' output:
 ~]# sensors
eeprom-i2c-0-52
Adapter: SMBus I801 adapter at 0500
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 0500
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

-Kevin

[lm-sensors] Can't load smsc47m1: no such device

[C Sylla]

Do you need to force an address possibly?  A lot of the sensor devices have
fixed addresses.  When you use a 'compatible' driver, it still tries by
default to use the 'right' address for the device it was written for.  For
example, for the LM63 you can use the LM90 driver - but you have to force
the address otherwise you get the same kind of error.

You also may not get full functionality of the device, depending on how
different the feature sets are.

The lm-sensors site has some examples and descriptions of how to force
addresses.

Craig


On 2/10/06, Williams, Kevin C <kevin.c.williams3 at boeing.com> wrote:
>
> My fan speed is at the highest possible speed when booted into linux on
> this system(same as speed during POST).  Load is 0.00 and x-windows is
> not installed. Winxp has a no audible fan noise unless doing high
> computation but never as high as with linux.  So, I decided to figure
> out how to tweak the fan speed.
>
> 'sensors-detect' found SMSC 47M15x/192 and I found that in the drivers
> section of the website, I(think) can use the 'smsc47m1' driver.  So I
> tried it:
> ~]# modprobe smsc47m1 force_addr=0x0800
> FATAL: Error inserting smsc47m1
> (/lib/modules/2.6.11-1.1369_FC4smp/kernel/drivers/i2c/chips/smsc47m1.ko)
> : No such device
>
> 'dmesg' has no reference of the smsc47m1 device, but it was found at
> 0x800 by sensors-detect with a cofidence of 9. Output of sensors-detect
> is below.  I should mention that I had  run it before and 2 modules are
> already loaded but they are just give me info about my RAM.
>
>
> ~]# /usr/sbin/sensors-detect
>
> This program will help you determine which I2C/SMBus modules
>
> <snip>
>
> We can start with probing for (PCI) I2C or SMBus adapters.
> You do not need any special privileges for this.
> Do you want to probe now? (YES/no): y
> Probing for PCI bus adapters...
> Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB ICH5
> Probe succesfully concluded.
>
> We will now try to load each adapter module in turn.
> Module `i2c-i801' already loaded.
> If you have undetectable or unsupported 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.
> If it is built-in into your kernel, you can safely skip this.
> i2c-dev is already loaded.
>
> We are now going to do the adapter probings. Some adapters may hang
> halfway
> through; we can't really help that. Also, some chips will 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. That often
> includes address 0x69 (clock chip).
>
> Next adapter: SMBus I801 adapter at 0500
> Do you want to scan it? (YES/no/selectively): y
> Client found at address 0x08
> Client found at address 0x2d
>
> <snip - failed probings>
>
> Client at address 0x50 can not be probed - unload all client drivers
> first!
> Client at address 0x52 can not be probed - unload all client drivers
> first!
> Client found at address 0x68
> Client found at address 0x69
>
> Some chips are also accessible through the ISA bus. ISA probes are
> typically a bit more dangerous, as we have to write to I/O ports to do
> this. This is usually safe though.
>
> Do you want to scan the ISA bus? (YES/no): y
> <snip - failed probings>
>
> Some Super I/O chips may also contain sensors. Super I/O probes are
> typically a bit more dangerous, as we have to write to I/O ports to do
> this. This is usually safe though.
>
> Do you want to scan for Super I/O sensors? (YES/no): y
>
> <snip failed probings>
>
> Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
> Success... found at address 0x0800
>
> <snip failed probings>
>
> Do you want to scan for secondary Super I/O sensors? (YES/no): y
>
> <snip failed probings>
>
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
>
> Driver `to-be-written' (should be inserted):
> Detects correctly:
> * ISA bus address 0x0800 (Busdriver `i2c-isa')
>    Chip `SMSC 47M15x/192 Super IO Fan Sensors' (confidence: 9)
>
>
> I will now generate the commands needed to load the I2C modules.
> Sometimes, a chip is available both through the ISA bus and an I2C bus.
> ISA bus access is faster, but you need to load an additional driver
> module
> for it. If you have the choice, do you want to use the ISA bus or the
> I2C/SMBus (ISA/smbus)? ISA
>
> To make the sensors modules behave correctly, add these lines to
> /etc/modprobe.conf:
>
> #----cut here----
> # I2C module options
> alias char-major-89 i2c-dev
> #----cut here----
>
> To load everything that is needed, add this to some /etc/rc* file:
>
> #----cut here----
> # I2C adapter drivers
> modprobe i2c-isa
> # I2C chip drivers
> # no driver for SMSC 47M15x/192 Super IO Fan Sensors yet
> # sleep 2 # optional
> /usr/bin/sensors -s # recommended
> #----cut here----
>
> WARNING! If you have some things built into your kernel, the list above
> will contain too many modules. Skip the appropriate ones! You really
> should
> try these commands right now to make sure everything is working
> properly.
> Monitoring programs won't work until it's done.
>
> Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
> Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
> for initialization at boot time.
>
> 'sensors' output:
> ~]# sensors
> eeprom-i2c-0-52
> Adapter: SMBus I801 adapter at 0500
> Memory type:            DDR SDRAM DIMM
> Memory size (MB):       512
>
> eeprom-i2c-0-50
> Adapter: SMBus I801 adapter at 0500
> Memory type:            DDR SDRAM DIMM
> Memory size (MB):       512
>
> -Kevin
>
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors at lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060210/87f31a55/attachment.html

[lm-sensors] Can't load smsc47m1: no such device

[Williams, Kevin C]

I did read about the force address feature and sensor-detect did report
that my device was found at 0x800 so I did "modprobe smsc47m1 force_addr
0x800" but it didn't make a difference.  Also, in 'dmesg', the error was
reported "unknown option force_addr".
 
-Kevin


________________________________

	From: C Sylla [mailto:csyllac at gmail.com] 
	Sent: Friday, February 10, 2006 12:25 PM
	To: Williams, Kevin C
	Cc: lm-sensors at lm-sensors.org
	Subject: Re: [lm-sensors] Can't load smsc47m1: no such device
	
	
	Do you need to force an address possibly?  A lot of the sensor
devices have fixed addresses.  When you use a 'compatible' driver, it
still tries by default to use the 'right' address for the device it was
written for.  For example, for the LM63 you can use the LM90 driver -
but you have to force the address otherwise you get the same kind of
error. 
	 
	You also may not get full functionality of the device, depending
on how different the feature sets are.
	 
	The lm-sensors site has some examples and descriptions of how to
force addresses.
	 
	Craig

	 
	On 2/10/06, Williams, Kevin C <kevin.c.williams3 at boeing.com>
wrote: 

		My fan speed is at the highest possible speed when
booted into linux on
		this system(same as speed during POST).  Load is 0.00
and x-windows is
		not installed. Winxp has a no audible fan noise unless
doing high
		computation but never as high as with linux.  So, I
decided to figure
		out how to tweak the fan speed.
		
		'sensors-detect' found SMSC 47M15x/192 and I found that
in the drivers 
		section of the website, I(think) can use the 'smsc47m1'
driver.  So I
		tried it:
		~]# modprobe smsc47m1 force_addr=0x0800
		FATAL: Error inserting smsc47m1
	
(/lib/modules/2.6.11-1.1369_FC4smp/kernel/drivers/i2c/chips/smsc47m1.ko
)
		: No such device
		
		'dmesg' has no reference of the smsc47m1 device, but it
was found at
		0x800 by sensors-detect with a cofidence of 9. Output of
sensors-detect
		is below.  I should mention that I had  run it before
and 2 modules are 
		already loaded but they are just give me info about my
RAM.
		
		
		~]# /usr/sbin/sensors-detect
		
		This program will help you determine which I2C/SMBus
modules
		
		<snip>
		
		We can start with probing for (PCI) I2C or SMBus
adapters. 
		You do not need any special privileges for this.
		Do you want to probe now? (YES/no): y
		Probing for PCI bus adapters...
		Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB
ICH5
		Probe succesfully concluded. 
		
		We will now try to load each adapter module in turn.
		Module `i2c-i801' already loaded.
		If you have undetectable or unsupported 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.
		If it is built-in into your kernel, you can safely skip
this.
		i2c-dev is already loaded.
		
		We are now going to do the adapter probings. Some
adapters may hang 
		halfway
		through; we can't really help that. Also, some chips
will 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. That often
		includes address 0x69 (clock chip).
		
		Next adapter: SMBus I801 adapter at 0500
		Do you want to scan it? (YES/no/selectively): y
		Client found at address 0x08 
		Client found at address 0x2d
		
		<snip - failed probings>
		
		Client at address 0x50 can not be probed - unload all
client drivers
		first!
		Client at address 0x52 can not be probed - unload all
client drivers 
		first!
		Client found at address 0x68
		Client found at address 0x69
		
		Some chips are also accessible through the ISA bus. ISA
probes are
		typically a bit more dangerous, as we have to write to
I/O ports to do 
		this. This is usually safe though.
		
		Do you want to scan the ISA bus? (YES/no): y
		<snip - failed probings>
		
		Some Super I/O chips may also contain sensors. Super I/O
probes are
		typically a bit more dangerous, as we have to write to
I/O ports to do 
		this. This is usually safe though.
		
		Do you want to scan for Super I/O sensors? (YES/no): y
		
		<snip failed probings>
		
		Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
		Success... found at address 0x0800 
		
		<snip failed probings>
		
		Do you want to scan for secondary Super I/O sensors?
(YES/no): y
		
		<snip failed probings>
		
		Now follows a summary of the probes I have just done.
		Just press ENTER to continue: 
		
		Driver `to-be-written' (should be inserted):
		Detects correctly:
		* ISA bus address 0x0800 (Busdriver `i2c-isa')
		   Chip `SMSC 47M15x/192 Super IO Fan Sensors'
(confidence: 9)
		
		
		I will now generate the commands needed to load the I2C
modules. 
		Sometimes, a chip is available both through the ISA bus
and an I2C bus.
		ISA bus access is faster, but you need to load an
additional driver
		module
		for it. If you have the choice, do you want to use the
ISA bus or the 
		I2C/SMBus (ISA/smbus)? ISA
		
		To make the sensors modules behave correctly, add these
lines to
		/etc/modprobe.conf:
		
		#----cut here----
		# I2C module options
		alias char-major-89 i2c-dev
		#----cut here---- 
		
		To load everything that is needed, add this to some
/etc/rc* file:
		
		#----cut here----
		# I2C adapter drivers
		modprobe i2c-isa
		# I2C chip drivers
		# no driver for SMSC 47M15x/192 Super IO Fan Sensors yet

		# sleep 2 # optional
		/usr/bin/sensors -s # recommended
		#----cut here----
		
		WARNING! If you have some things built into your kernel,
the list above
		will contain too many modules. Skip the appropriate
ones! You really 
		should
		try these commands right now to make sure everything is
working
		properly.
		Monitoring programs won't work until it's done.
		
		Do you want to generate /etc/sysconfig/lm_sensors?
(YES/no): y
		Copy prog/init/lm_sensors.init to
/etc/rc.d/init.d/lm_sensors 
		for initialization at boot time.
		
		'sensors' output:
		~]# sensors
		eeprom-i2c-0-52
		Adapter: SMBus I801 adapter at 0500
		Memory type:            DDR SDRAM DIMM
		Memory size (MB):       512
		
		eeprom-i2c-0-50 
		Adapter: SMBus I801 adapter at 0500
		Memory type:            DDR SDRAM DIMM
		Memory size (MB):       512
		
		-Kevin
		
		
		
		_______________________________________________
		lm-sensors mailing list
		lm-sensors at lm-sensors.org
		http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
		


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060210/c0854d3a/attachment-0001.html

[lm-sensors] Can't load smsc47m1: no such device

[Jean Delvare]

Hi Kevin,

> My fan speed is at the highest possible speed when booted into linux on
> this system(same as speed during POST).  Load is 0.00 and x-windows is
> not installed. Winxp has a no audible fan noise unless doing high
> computation but never as high as with linux.  So, I decided to figure
> out how to tweak the fan speed.
> 
> 'sensors-detect' found SMSC 47M15x/192 and I found that in the drivers
> section of the website, I(think) can use the 'smsc47m1' driver.  So I
> tried it:
> ~]# modprobe smsc47m1 force_addr=0x0800
> FATAL: Error inserting smsc47m1
> (/lib/modules/2.6.11-1.1369_FC4smp/kernel/drivers/i2c/chips/smsc47m1.ko)
> : No such device

Support for the SMSC LPC47M15x/192 chip was added to the smsc47m1
driver in Linux 2.6.13. Your kernel is older so the support is simply
not there. Unfortunately, there is no way to force a device with that
kind of driver. So your only hope is a newer kernel (or a self compiled
kernel from patched sources).

-- 
Jean Delvare

[lm-sensors] Can't load smsc47m1: no such device

[Williams, Kevin C]

OK great!  At least I have somewhere to go.  I shall update my kernel
and return :)

Thanks
-kevin 

> -----Original Message-----
> From: Jean Delvare [mailto:khali at linux-fr.org] 
> Sent: Friday, February 10, 2006 2:13 PM
> To: Williams, Kevin C
> Cc: LM Sensors
> Subject: Re: [lm-sensors] Can't load smsc47m1: no such device
> 
> Hi Kevin,
> 
> > My fan speed is at the highest possible speed when booted 
> into linux 
> > on this system(same as speed during POST).  Load is 0.00 
> and x-windows 
> > is not installed. Winxp has a no audible fan noise unless 
> doing high 
> > computation but never as high as with linux.  So, I decided 
> to figure 
> > out how to tweak the fan speed.
> > 
> > 'sensors-detect' found SMSC 47M15x/192 and I found that in 
> the drivers 
> > section of the website, I(think) can use the 'smsc47m1' 
> driver.  So I 
> > tried it:
> > ~]# modprobe smsc47m1 force_addr=0x0800
> > FATAL: Error inserting smsc47m1
> > 
> (/lib/modules/2.6.11-1.1369_FC4smp/kernel/drivers/i2c/chips/smsc47m1.k
> > o)
> > : No such device
> 
> Support for the SMSC LPC47M15x/192 chip was added to the 
> smsc47m1 driver in Linux 2.6.13. Your kernel is older so the 
> support is simply not there. Unfortunately, there is no way 
> to force a device with that kind of driver. So your only hope 
> is a newer kernel (or a self compiled kernel from patched sources).
> 
> --
> Jean Delvare
> 

[lm-sensors] Can't load smsc47m1: no such device

[Williams, Kevin C]

Boy, I love yum.  2.6.15-1.1831FC4smp kernel is installed now.

I ran sensor-detect and got the same output as before. i.e. no driver
for smsc47m14x/192.  So I did a 'modprobe smsc47m1' just in case and
didn't get any error.  Output from 'dmesg' was:
smsc47m1: Found SMSC LPC47M15x/LPC47M192/LPC47M997
-------

Ouput from 'sensors' now, is:
~]# sensors
smsc47m1-isa-0800
Adapter: ISA adapter
fan1:        0 RPM  (min = 2560 RPM, div = 2)
fan2:        0 RPM  (min = 2560 RPM, div = 2)
--------

Obviously, it's not 0. So I ran 'pwmconfig' and instantly, the processor
fans shutoff(because this is SFF, there are 2 fans each side of the
heatsink).  Here's the output:
~]# pwmconfig
Found the following PWM controls:
   9191-0800/pwm1
   9191-0800/pwm2

Found the following fan sensors:
   9191-0800/fan1_input     current speed: 5585 RPM
   9191-0800/fan2_input     current speed: 5461 RPM

Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue:

Testing pwm control 9191-0800/pwm1 ...
  9191-0800/fan1_input ... speed was 5585 now 0
    It appears that fan 9191-0800/fan1_input
    is controlled by pwm 9191-0800/pwm1
    Fan 9191-0800/fan1_input has not returned to speed, please
investigate!
  9191-0800/fan2_input ... speed was 5461 now 0
    It appears that fan 9191-0800/fan2_input
    is controlled by pwm 9191-0800/pwm1
    Fan 9191-0800/fan2_input has not returned to speed, please
investigate!

Testing pwm control 9191-0800/pwm2 ...
  9191-0800/fan1_input ... speed was 5585 now 0
    It appears that fan 9191-0800/fan1_input
    is controlled by pwm 9191-0800/pwm2
    Fan 9191-0800/fan1_input has not returned to speed, please
investigate!
  9191-0800/fan2_input ... speed was 5461 now 0
    It appears that fan 9191-0800/fan2_input
    is controlled by pwm 9191-0800/pwm2
    Fan 9191-0800/fan2_input has not returned to speed, please
investigate!

Testing is complete.
Please verify that all fans have returned to their normal speed.

The fancontrol script can automatically respond to temperature changes
of your system by changing fanspeeds.
Do you want to set up its configuration file now (y)? y
/usr/sbin/pwmconfig: There are no temperature-capable sensor modules
installed
-----

In the beginning you can see that it reports the fan speeds correctly.
In the bios, it reports similar values.  However, while it is able to
successfully shut the fans down, it can't bring them back up(which I
verified was true...and bad, so I rebooted into bios).

Any suggestions here, it looks like there's a way to detect fan speed
and turn it off, now I just need to fine tune it.

-Kevin

> -----Original Message-----
> From: Jean Delvare [mailto:khali at linux-fr.org] 
> Sent: Friday, February 10, 2006 2:13 PM
> To: Williams, Kevin C
> Cc: LM Sensors
> Subject: Re: [lm-sensors] Can't load smsc47m1: no such device
> 
> Hi Kevin,
> 
> > My fan speed is at the highest possible speed when booted 
> into linux 
> > on this system(same as speed during POST).  Load is 0.00 
> and x-windows 
> > is not installed. Winxp has a no audible fan noise unless 
> doing high 
> > computation but never as high as with linux.  So, I decided 
> to figure 
> > out how to tweak the fan speed.
> > 
> > 'sensors-detect' found SMSC 47M15x/192 and I found that in 
> the drivers 
> > section of the website, I(think) can use the 'smsc47m1' 
> driver.  So I 
> > tried it:
> > ~]# modprobe smsc47m1 force_addr=0x0800
> > FATAL: Error inserting smsc47m1
> > 
> (/lib/modules/2.6.11-1.1369_FC4smp/kernel/drivers/i2c/chips/smsc47m1.k
> > o)
> > : No such device
> 
> Support for the SMSC LPC47M15x/192 chip was added to the 
> smsc47m1 driver in Linux 2.6.13. Your kernel is older so the 
> support is simply not there. Unfortunately, there is no way 
> to force a device with that kind of driver. So your only hope 
> is a newer kernel (or a self compiled kernel from patched sources).
> 
> --
> Jean Delvare
> 

[lm-sensors] Can't load smsc47m1: no such device

[Jean Delvare]

Hi Kevin,

> I ran sensor-detect and got the same output as before. i.e. no driver
> for smsc47m14x/192.  So I did a 'modprobe smsc47m1' just in case and
> didn't get any error.  Output from 'dmesg' was:
> smsc47m1: Found SMSC LPC47M15x/LPC47M192/LPC47M997
> -------
> 
> Ouput from 'sensors' now, is:
> ~]# sensors
> smsc47m1-isa-0800
> Adapter: ISA adapter
> fan1:        0 RPM  (min = 2560 RPM, div = 2)
> fan2:        0 RPM  (min = 2560 RPM, div = 2)
> --------
> 
> Obviously, it's not 0.

This is strange. I would have suggested that you increase the fan clock
dividers (fan1_div and fan2_div in /etc/sensors.conf) but the output of
pwmconfig below suggest that it was able to measure the speed of the
fans, and that this speed is over 5000 RPM so a clock divider of 2
should work just fine. I can't explain why pwmconfig was able to
monitor the fans when "sensors" wasn't - it doesn't make much sense.

> So I ran 'pwmconfig' and instantly, the processor
> fans shutoff(because this is SFF, there are 2 fans each side of the
> heatsink).  Here's the output:
> ~]# pwmconfig
> Found the following PWM controls:
>    9191-0800/pwm1
>    9191-0800/pwm2
> 
> Found the following fan sensors:
>    9191-0800/fan1_input     current speed: 5585 RPM
>    9191-0800/fan2_input     current speed: 5461 RPM
> 
> Warning!!! This program will stop your fans, one at a time,
> for approximately 5 seconds each!!!
> This may cause your processor temperature to rise!!!
> If you do not want to do this hit control-C now!!!
> Hit return to continue:
> 
> Testing pwm control 9191-0800/pwm1 ...
>   9191-0800/fan1_input ... speed was 5585 now 0
>     It appears that fan 9191-0800/fan1_input
>     is controlled by pwm 9191-0800/pwm1
>     Fan 9191-0800/fan1_input has not returned to speed, please
> investigate!
>   9191-0800/fan2_input ... speed was 5461 now 0
>     It appears that fan 9191-0800/fan2_input
>     is controlled by pwm 9191-0800/pwm1
>     Fan 9191-0800/fan2_input has not returned to speed, please
> investigate!
> 
> Testing pwm control 9191-0800/pwm2 ...
>   9191-0800/fan1_input ... speed was 5585 now 0
>     It appears that fan 9191-0800/fan1_input
>     is controlled by pwm 9191-0800/pwm2
>     Fan 9191-0800/fan1_input has not returned to speed, please
> investigate!
>   9191-0800/fan2_input ... speed was 5461 now 0
>     It appears that fan 9191-0800/fan2_input
>     is controlled by pwm 9191-0800/pwm2
>     Fan 9191-0800/fan2_input has not returned to speed, please
> investigate!
> 
> Testing is complete.
> Please verify that all fans have returned to their normal speed.
> 
> The fancontrol script can automatically respond to temperature changes
> of your system by changing fanspeeds.
> Do you want to set up its configuration file now (y)? y
> /usr/sbin/pwmconfig: There are no temperature-capable sensor modules
> installed
> -----
> 
> In the beginning you can see that it reports the fan speeds correctly.
> In the bios, it reports similar values.  However, while it is able to
> successfully shut the fans down, it can't bring them back up(which I
> verified was true...and bad, so I rebooted into bios).

That's bad :(

> Any suggestions here, it looks like there's a way to detect fan speed
> and turn it off, now I just need to fine tune it.

Well I think you jumped the gun. You should take some time to get
"sensors" to work, then to manually control the speed of your fans.
Once this is OK, and only then, you should consider running pwmconfig
again.

First, if you have the opportunity to upgrade the version of lm_sensors
you are using, take it. I have no particular fix in mind, but this
can't hurt.

Then, you must get "sensors" to display the speed of your fans. You may
try changing the low speed limits too, just to make sure your chip is
behaving as intended. This tweaking is done in file /etc/sensors.conf,
section "smsc47m1-*". Try the following for example, and see if it
works:

   set fan1_div 4
   set fan2_div 4
   set fan1_min 2000
   set fan2_min 2000

Once you have proper readings, try changing the fan speeds manually.
This is done by writing values to sysfs files.
Under /sys/class/hwmon/hwmon0/device, you should find files named:

  fan1_div
  fan1_input
  fan1_min
  fan2_div
  fan2_input
  fan2_min
  pwm1
  pwm1_enable
  pwm2
  pwm2_enable

fan* files are for monitoring ("sensors" reads its values from there),
pwm* files are for speed control. pwmN_enable is a boolean switch, 0
disables PWM (pulse width modulation), which means that the
corresponing fan is running at full speed); 1 means enabled. When
pwmN_enable is set to 1, pwmN controls the speed. Values range from 0
(fan stopped, don't do that) to 254 (fan at full speed).

Usually pwm1 corresponds to fan1 and pwm2 corresponds to fan2, but it
doesn't have to be the case so you'll have to experiment with your
actual hardware setup.

As pwmconfig was not able to restore your fans to full speed, I'd
expect you to have some problems too. Try decreasing the fan speeds
step by step. I can't tell much more at this point as I can't explain
what you observed, but maybe playing with the controls by yourself will
make you understand what went wrong. If you can figure out, please
report so that we can see what can be done to improve the situation.

-- 
Jean Delvare