[lm-sensors] LPC47M192-NC Fans

[lm-sensors] LPC47M192-NC Fans

[Sean Fidler]

Hello,

I recently installed Ubuntu Server 9.10 on a Compaq Presario 
S4000NX. Sensor info: chip is LPC47M192-NC and the bus is 
bus "i2c-2" "SMBus I801 adapter at 1880"

When running "sensors" no information is shown for the CPU fan (there 
are no entries for fans at all.) Only entries for voltages and 
temperatures are available.

pwmconfig states that there are no modules installed. Am I out of luck 
with trying to control the CPU fan speed? Thanks!

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Jean Delvare]

Hi Sean,

On Mon, 30 Nov 2009 16:30:42 -0500 (EST), Sean Fidler wrote:
> I recently installed Ubuntu Server 9.10 on a Compaq Presario 
> S4000NX. Sensor info: chip is LPC47M192-NC and the bus is 
> bus "i2c-2" "SMBus I801 adapter at 1880"
> 
> When running "sensors" no information is shown for the CPU fan (there 
> are no entries for fans at all.) Only entries for voltages and 
> temperatures are available.
> 
> pwmconfig states that there are no modules installed. Am I out of luck 
> with trying to control the CPU fan speed? Thanks!

Full output of sensors-detect please. The SMSC LPC47M192 is supported
by two drivers: smsc47m1 for the fans and smsc47m192 for the voltages
and temperatures. Make sure both are loaded. If it still doesn't work,
please also provide the contents of /proc/ioports and check for error
messages in your kernel logs when loading the smsc47m1 driver.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Sean Fidler]

Thanks for your assistance.

Please find the requested information below: output of sensors-detect,
/proc/ioports and the kernel log entry after attempting to load smsc47m1

##############################
#sensors-detect revision 5249# 
##############################

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): Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801DB ICH4

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported I2C/SMBus adapters, you can have
them scanned by manually loading the modules before running this script.

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 1880 (i2c-0)
Do you want to scan it? (YES/no/selectively): Client found at address 0x2d
Handled by driver `smsc47m192' (already loaded), chip type `smsc47m192'
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 0x51
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

Next adapter: intel drm CRTDDC_A (i2c-1)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
     (confidence 8, not a hardware monitoring chip)

Next adapter: bt878 #0 [sw] (i2c-2)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
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): 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): Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     Yes
Found `SMSC LPC47M15x/192/997 Super IO Fan Sensors'
     (but not activated)
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): 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: 
Driver `smsc47m192' (should be inserted):
   Detects correctly:
   * Bus `SMBus I801 adapter at 1880'
     Busdriver `i2c-i801', I2C address 0x2d
     Chip `smsc47m192' (confidence: 6)

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----
# I2C adapter drivers
i2c-i801
# Chip drivers
smsc47m192
#----cut here----

Do you want to add these lines automatically? (yes/NO)

################
# /proc/ioports#
################

0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-0060 : keyboard
0064-0064 : keyboard
0070-0071 : rtc0
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : 0000:00:1f.1
   0170-0177 : ata_piix
01f0-01f7 : 0000:00:1f.1
   01f0-01f7 : ata_piix
0376-0376 : 0000:00:1f.1
   0376-0376 : ata_piix
0378-037a : parport0
03c0-03df : vga+
03f2-03f2 : floppy
03f4-03f5 : floppy
03f6-03f6 : 0000:00:1f.1
   03f6-03f6 : ata_piix
03f7-03f7 : floppy
03f8-03ff : serial
04d0-04d1 : pnp 00:01
0778-077a : parport0
0cf8-0cff : PCI conf1
1000-107f : 0000:00:1f.0
   1000-107f : pnp 00:01
     1000-1003 : ACPI PM1a_EVT_BLK
     1004-1005 : ACPI PM1a_CNT_BLK
     1008-100b : ACPI PM_TMR
     1010-1015 : ACPI CPU throttle
     1020-1020 : ACPI PM2_CNT_BLK
     1028-102f : ACPI GPE0_BLK
1180-11bf : 0000:00:1f.0
   1180-11bf : pnp 00:01
1800-181f : 0000:00:1d.0
   1800-181f : uhci_hcd
1820-183f : 0000:00:1d.1
   1820-183f : uhci_hcd
1840-185f : 0000:00:1d.2
   1840-185f : uhci_hcd
1860-186f : 0000:00:1f.1
   1860-186f : ata_piix
1880-189f : 0000:00:1f.3
   1880-189f : i801_smbus
2000-2fff : PCI Bus 0000:02
   2000-20ff : 0000:02:02.0
     2000-20ff : 8139too
fe00-fe00 : pnp 00:01

############
#kernal log#
############

Nov 30 17:44:21 ubuntu kernel: [  728.046978] smsc47m1: Found SMSC LPC47M15x/LPC47M192/LPC47M997
Nov 30 17:44:21 ubuntu kernel: [  728.046997] smsc47m1: Device is disabled, will not use

On Mon, 30 Nov 2009, Jean Delvare wrote:

> Hi Sean,
>
> On Mon, 30 Nov 2009 16:30:42 -0500 (EST), Sean Fidler wrote:
>> I recently installed Ubuntu Server 9.10 on a Compaq Presario
>> S4000NX. Sensor info: chip is LPC47M192-NC and the bus is
>> bus "i2c-2" "SMBus I801 adapter at 1880"
>>
>> When running "sensors" no information is shown for the CPU fan (there
>> are no entries for fans at all.) Only entries for voltages and
>> temperatures are available.
>>
>> pwmconfig states that there are no modules installed. Am I out of luck
>> with trying to control the CPU fan speed? Thanks!
>
> Full output of sensors-detect please. The SMSC LPC47M192 is supported
> by two drivers: smsc47m1 for the fans and smsc47m192 for the voltages
> and temperatures. Make sure both are loaded. If it still doesn't work,
> please also provide the contents of /proc/ioports and check for error
> messages in your kernel logs when loading the smsc47m1 driver.
>
> -- 
> Jean Delvare
>

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Jean Delvare]

Hi Sean,

On Mon, 30 Nov 2009 18:08:46 -0500 (EST), Sean Fidler wrote:
> Thanks for your assistance.
> 
> Please find the requested information below: output of sensors-detect,
> /proc/ioports and the kernel log entry after attempting to load smsc47m1
> 
> ##############################
> #sensors-detect revision 5249# 
> ##############################
> (...)
> 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): Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor'...                   No
> Trying family `SMSC'...                                     Yes
> Found `SMSC LPC47M15x/192/997 Super IO Fan Sensors'
>      (but not activated)

I see. The fan sensors block is disabled, which is why sensors-detect
doesn't pick it up...

> (...)
> Nov 30 17:44:21 ubuntu kernel: [  728.046978] smsc47m1: Found SMSC LPC47M15x/LPC47M192/LPC47M997
> Nov 30 17:44:21 ubuntu kernel: [  728.046997] smsc47m1: Device is disabled, will not use

... and neither does the smsc47m1 driver.

Please look in your BIOS if there is any option to enable fan speed
monitoring and/or control. BTW, does the BIOS display any voltage,
temperature or fan speed data?

If you can't find a suitable option in your BIOS, we can try to
manually enable the fan sensors block. However, in most cases disabled
sensors block are disabled because they are effectively unused
(physically not wired on the board.) So there are good chances that
this will not lead us anywhere. Do you have any reason to believe that
fan speed can be monitored and/or controlled on this system in the
first place?

If you want to continue, I will need the output of the following
command:

isadump -k 0x55 0x2e 0x2f 0x0a

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Sean Fidler]

Hi Jean,

That's the mystery, the BIOS does show the temperature and the fan 
speed.

Here's the information you requested (isadump -k 0x55 0x2e 0x2f 0x0a):


      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: 00 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 00 
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
20: 60 01 19 00 44 00 2e 00 00 00 00 00 00 00 00 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
60: 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff 
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
f0: 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Thanks!

On Tue, 1 Dec 2009, Jean Delvare wrote:

> Hi Sean,
>
> On Mon, 30 Nov 2009 18:08:46 -0500 (EST), Sean Fidler wrote:
>> Thanks for your assistance.
>>
>> Please find the requested information below: output of sensors-detect,
>> /proc/ioports and the kernel log entry after attempting to load smsc47m1
>>
>> ##############################
>> #sensors-detect revision 5249#
>> ##############################
>> (...)
>> 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): Probing for Super-I/O at 0x2e/0x2f
>> Trying family `National Semiconductor'...                   No
>> Trying family `SMSC'...                                     Yes
>> Found `SMSC LPC47M15x/192/997 Super IO Fan Sensors'
>>      (but not activated)
>
> I see. The fan sensors block is disabled, which is why sensors-detect
> doesn't pick it up...
>
>> (...)
>> Nov 30 17:44:21 ubuntu kernel: [  728.046978] smsc47m1: Found SMSC LPC47M15x/LPC47M192/LPC47M997
>> Nov 30 17:44:21 ubuntu kernel: [  728.046997] smsc47m1: Device is disabled, will not use
>
> ... and neither does the smsc47m1 driver.
>
> Please look in your BIOS if there is any option to enable fan speed
> monitoring and/or control. BTW, does the BIOS display any voltage,
> temperature or fan speed data?
>
> If you can't find a suitable option in your BIOS, we can try to
> manually enable the fan sensors block. However, in most cases disabled
> sensors block are disabled because they are effectively unused
> (physically not wired on the board.) So there are good chances that
> this will not lead us anywhere. Do you have any reason to believe that
> fan speed can be monitored and/or controlled on this system in the
> first place?
>
> If you want to continue, I will need the output of the following
> command:
>
> isadump -k 0x55 0x2e 0x2f 0x0a
>
> -- 
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
>

--
Twitter: endersyrinx
GTalk: fidlersean

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Jean Delvare]

Hi Sean,

On Tue, 1 Dec 2009 12:49:59 -0500 (EST), Sean Fidler wrote:
> That's the mystery, the BIOS does show the temperature and the fan 
> speed.

What does it list exactly? Labels and values please.

Do the values somehow correlate with what the smsc47m192 driver
provides?

As this is a vendor machine, it is possible that it is using custom
logic for hardware monitoring.

> Here's the information you requested (isadump -k 0x55 0x2e 0x2f 0x0a):
> 
> 
>       0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: 00 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 00 
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> 20: 60 01 19 00 44 00 2e 00 00 00 00 00 00 00 00 00 
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> 60: 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff 
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
> f0: 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Hmm. Not activated, but I/O port set (0x600 at 0x60). Nothing there
according to your /proc/ioports. Let's try to enable it:

# isaset -y -f 0x2e 0x55
# isaset -y 0x2e 0x2f 0x07 0x0a
# isaset -y 0x2e 0x2f 0x30 0x01
# isaset -y -f 0x2e 0xaa

After that, check with isadump that register 0x30 has value 0x01
instead of 0x00:

# isadump -k 0x55 0x2e 0x2f 0x0a

If it worked, try loading the smsc47m1 driver, and see if "sensors"
shows something new. If not, search your kernel logs for a new error
message.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Sean Fidler]

Hi Jean,

Your instructions worked!

I'm assuming I have to load up fancontrol manually (via a script) each time, isaset instructions need to be 
repeated after each boot up, right? Maybe I'm missing something.

I was able to set up fancontrol via the pwmconfig and the fan slowed 
down. Hopefully, it will speed up when necessary.

The first and last isaset lines returned the following:
isaset -y -f 0x2e 0x55 -> Data mismatch, wrote 0x0a, read 0xff back.
isaset -y -f 0x2e 0xaa -> Data mismatch, wrote 0xaa, read 0xff back.

These mismatches, of course, didn't effect the end result. Maybe they 
indicate something that I'm obviously not aware of.

Your help with this issue is greatly appreciated. Thanks.

On Tue, 1 Dec 2009, Jean Delvare wrote:

> Hi Sean,
>
> On Tue, 1 Dec 2009 12:49:59 -0500 (EST), Sean Fidler wrote:
>> That's the mystery, the BIOS does show the temperature and the fan
>> speed.
>
> What does it list exactly? Labels and values please.
>
> Do the values somehow correlate with what the smsc47m192 driver
> provides?
>
> As this is a vendor machine, it is possible that it is using custom
> logic for hardware monitoring.
>
>> Here's the information you requested (isadump -k 0x55 0x2e 0x2f 0x0a):
>>
>>
>>       0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>> 00: 00 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 00
>> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 20: 60 01 19 00 44 00 2e 00 00 00 00 00 00 00 00 00
>> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 60: 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> a0: 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff
>> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> f0: 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> Hmm. Not activated, but I/O port set (0x600 at 0x60). Nothing there
> according to your /proc/ioports. Let's try to enable it:
>
> # isaset -y -f 0x2e 0x55
> # isaset -y 0x2e 0x2f 0x07 0x0a
> # isaset -y 0x2e 0x2f 0x30 0x01
> # isaset -y -f 0x2e 0xaa
>
> After that, check with isadump that register 0x30 has value 0x01
> instead of 0x00:
>
> # isadump -k 0x55 0x2e 0x2f 0x0a
>
> If it worked, try loading the smsc47m1 driver, and see if "sensors"
> shows something new. If not, search your kernel logs for a new error
> message.
>
> -- 
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
>

--
Twitter: endersyrinx
GTalk: fidlersean

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Jean Delvare]

Hi Sean,

On Tue, 1 Dec 2009 16:03:24 -0500 (EST), Sean Fidler wrote:
> Your instructions worked!

Wow. This is more than I hoped for :)

> I'm assuming I have to load up fancontrol manually (via a script) each time, isaset instructions need to be 
> repeated after each boot up, right? Maybe I'm missing something.

Yes, you are correct, the changes done by the isaset commands are lost
on reboot.

> I was able to set up fancontrol via the pwmconfig and the fan slowed 
> down. Hopefully, it will speed up when necessary.

You should be able to check this easily by putting fake load on the CPU
(for example with "md5sum /dev/zero").

What does the output of "sensors" look like?

> The first and last isaset lines returned the following:
> isaset -y -f 0x2e 0x55 -> Data mismatch, wrote 0x0a, read 0xff back.
                                                 ^^^^
It really said 0x55, not 0x0a, right?

> isaset -y -f 0x2e 0xaa -> Data mismatch, wrote 0xaa, read 0xff back.
> 
> These mismatches, of course, didn't effect the end result. Maybe they 
> indicate something that I'm obviously not aware of.

These warning messages were expected, sorry for not telling you in
advance.

> Your help with this issue is greatly appreciated. Thanks.

You're welcome.

Would you be able to test kernel patches? I think it would make sense
to let the smsc47m1 driver enable access to the fan speed monitoring
and control registers at least on your specific machine, and possibly
on all systems where the base I/O address is properly defined (as the
w83627hf and w83627ehf drivers are doing for example.) I can do these
changes but I don't have any chip here to test the smsc47m1 driver, so
I need someone to do the testing for me.

To test kernel patches (or more specifically to build a patched
standalone driver) you will need gcc, make, the sources of your running
kernel (usually available as package "kernel-source" or similar) and
probably some distribution-specific knowledge on the topic.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Sean Fidler]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 3377 bytes --]

Hi Jean,

Sensors output:

smsc47m192-i2c-0-2d
Adapter: SMBus I801 adapter at 1880
+2.5V:       +0.00 V  (min =  +2.90 V, max =  +2.90 V)   ALARM
VCore:       +0.00 V  (min =  +2.99 V, max =  +2.99 V)   ALARM
+3.3V:       +0.00 V  (min =  +4.38 V, max =  +4.35 V)   ALARM
+5V:         +0.00 V  (min =  +6.64 V, max =  +6.64 V)   ALARM
+12V:        +3.12 V  (min = +15.81 V, max = +15.88 V)   ALARM
VCC:         +3.35 V  (min =  +4.38 V, max =  +3.83 V)   ALARM
+1.5V:       +0.05 V  (min =  +1.49 V, max =  +1.99 V)   ALARM
+1.8V:       +0.00 V  (min =  +2.39 V, max =  +2.39 V)   ALARM
Chip Temp:   +34.0°C  (low  = -17.0°C, high =  -1.0°C)  ALARM 
CPU Temp:    +28.0°C  (low  =  -1.0°C, high = -33.0°C)  ALARM 
Sys Temp:      FAULT  (low  = -65.0°C, high =  -1.0°C)  ALARM 
cpu0_vid:   +1.475 V

smsc47m1-isa-0600
Adapter: ISA adapter
fan1:       2925 RPM  (min = 2560 RPM, div = 2)  ALARM
fan2:          0 RPM  (min = 3072 RPM, div = 4)  ALARM


isaset -y -f 0x2e 0x55: "…wrote 0x55, read 0xaa back." Sorry about the 
discrepancy.

I wouldn't mind test kernel patches. I'll have to figure out how to
implement them, but I think I'll be able to manage *fingers crossed*. Whatever I can do to
help.

On Wed, 2 Dec 2009, Jean Delvare wrote:

> Hi Sean,
>
> On Tue, 1 Dec 2009 16:03:24 -0500 (EST), Sean Fidler wrote:
>> Your instructions worked!
>
> Wow. This is more than I hoped for :)
>
>> I'm assuming I have to load up fancontrol manually (via a script) each time, isaset instructions need to be
>> repeated after each boot up, right? Maybe I'm missing something.
>
> Yes, you are correct, the changes done by the isaset commands are lost
> on reboot.
>
>> I was able to set up fancontrol via the pwmconfig and the fan slowed
>> down. Hopefully, it will speed up when necessary.
>
> You should be able to check this easily by putting fake load on the CPU
> (for example with "md5sum /dev/zero").
>
> What does the output of "sensors" look like?
>
>> The first and last isaset lines returned the following:
>> isaset -y -f 0x2e 0x55 -> Data mismatch, wrote 0x0a, read 0xff back.
>                                                 ^^^^
> It really said 0x55, not 0x0a, right?
>
>> isaset -y -f 0x2e 0xaa -> Data mismatch, wrote 0xaa, read 0xff back.
>>
>> These mismatches, of course, didn't effect the end result. Maybe they
>> indicate something that I'm obviously not aware of.
>
> These warning messages were expected, sorry for not telling you in
> advance.
>
>> Your help with this issue is greatly appreciated. Thanks.
>
> You're welcome.
>
> Would you be able to test kernel patches? I think it would make sense
> to let the smsc47m1 driver enable access to the fan speed monitoring
> and control registers at least on your specific machine, and possibly
> on all systems where the base I/O address is properly defined (as the
> w83627hf and w83627ehf drivers are doing for example.) I can do these
> changes but I don't have any chip here to test the smsc47m1 driver, so
> I need someone to do the testing for me.
>
> To test kernel patches (or more specifically to build a patched
> standalone driver) you will need gcc, make, the sources of your running
> kernel (usually available as package "kernel-source" or similar) and
> probably some distribution-specific knowledge on the topic.
>
> -- 
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
>

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Jean Delvare]

Hi Sean,

On Wed, 2 Dec 2009 14:55:37 -0500 (EST), Sean Fidler wrote:
> Sensors output:
> 
> smsc47m192-i2c-0-2d
> Adapter: SMBus I801 adapter at 1880
> +2.5V:       +0.00 V  (min =  +2.90 V, max =  +2.90 V)   ALARM
> VCore:       +0.00 V  (min =  +2.99 V, max =  +2.99 V)   ALARM
> +3.3V:       +0.00 V  (min =  +4.38 V, max =  +4.35 V)   ALARM
> +5V:         +0.00 V  (min =  +6.64 V, max =  +6.64 V)   ALARM
> +12V:        +3.12 V  (min = +15.81 V, max = +15.88 V)   ALARM
> VCC:         +3.35 V  (min =  +4.38 V, max =  +3.83 V)   ALARM
> +1.5V:       +0.05 V  (min =  +1.49 V, max =  +1.99 V)   ALARM
> +1.8V:       +0.00 V  (min =  +2.39 V, max =  +2.39 V)   ALARM
> Chip Temp:   +34.0°C  (low  = -17.0°C, high =  -1.0°C)  ALARM 
> CPU Temp:    +28.0°C  (low  =  -1.0°C, high = -33.0°C)  ALARM 
> Sys Temp:      FAULT  (low  = -65.0°C, high =  -1.0°C)  ALARM 
> cpu0_vid:   +1.475 V

Not many inputs wired, and the min voltage and high temperature limits
are pretty wrong, but other than that it's not too bad, except for
+12V. Do the temperature values appear to match anything you've seen in
the BIOS?

> smsc47m1-isa-0600
> Adapter: ISA adapter
> fan1:       2925 RPM  (min = 2560 RPM, div = 2)  ALARM
> fan2:          0 RPM  (min = 3072 RPM, div = 4)  ALARM

Looks reasonable. Only one fan on this system? If there are more, you
can try increasing fan2_div to 8 if the other fan is a slow one. I
guess that the first ALARM wears off when running "sensors" again? 2925
is above the min limit so there should be no ALARM.

From the above output, the following configuration section would seem
appropriate for your system:

chip "smsc47m192-i2c-*-2d"

   ignore in0
   ignore in1
   ignore in2
   ignore in3
   label  in5 "+3.3V"
   ignore in6
   ignore in7

   set in4_min   0
   set in5_min 3.3 * 0.95
   set in5_max 3.3 * 1.05

   ignore temp3

   set temp1_min  5
   set temp1_max 50
   set temp2_min  5
   set temp2_max 50

Needs to be confirmed:
* What is wired on in4.
* Temperature input labels.
* Whether cpu0_vid is real. What CPU is there on this machine?
* Which fan is connected to fan1.
* Is there anything connected to fan2.

If you can answer the questions above then we can put a good
configuration file for your machine on the wiki.

> I wouldn't mind test kernel patches. I'll have to figure out how to
> implement them, but I think I'll be able to manage *fingers crossed*. Whatever I can do to
> help.

I've put a modified smsc47m1 driver here:
http://khali.linux-fr.org/devel/misc/smsc47m1/

I would like you to download it and test it. With that driver, you
should no longer have to do the isaset magic at boot time. It include
other changes which should hopefully be transparent to you if I didn't
mess up.

This is a standalone driver, you'll need a proper build environment
(install make, gcc and the kernel headers) then type "make" then load
the driver (with insmod.)

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Sean Fidler]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 3736 bytes --]

Hi Jean,

On Sat, 5 Dec 2009, Jean Delvare wrote:

> Hi Sean,
>
> On Wed, 2 Dec 2009 14:55:37 -0500 (EST), Sean Fidler wrote:
>> Sensors output:
>>
>> smsc47m192-i2c-0-2d
>> Adapter: SMBus I801 adapter at 1880
>> +2.5V:       +0.00 V  (min =  +2.90 V, max =  +2.90 V)   ALARM
>> VCore:       +0.00 V  (min =  +2.99 V, max =  +2.99 V)   ALARM
>> +3.3V:       +0.00 V  (min =  +4.38 V, max =  +4.35 V)   ALARM
>> +5V:         +0.00 V  (min =  +6.64 V, max =  +6.64 V)   ALARM
>> +12V:        +3.12 V  (min = +15.81 V, max = +15.88 V)   ALARM
>> VCC:         +3.35 V  (min =  +4.38 V, max =  +3.83 V)   ALARM
>> +1.5V:       +0.05 V  (min =  +1.49 V, max =  +1.99 V)   ALARM
>> +1.8V:       +0.00 V  (min =  +2.39 V, max =  +2.39 V)   ALARM
>> Chip Temp:   +34.0°C  (low  = -17.0°C, high =  -1.0°C)  ALARM
>> CPU Temp:    +28.0°C  (low  =  -1.0°C, high = -33.0°C)  ALARM
>> Sys Temp:      FAULT  (low  = -65.0°C, high =  -1.0°C)  ALARM
>> cpu0_vid:   +1.475 V
>
> Not many inputs wired, and the min voltage and high temperature limits
> are pretty wrong, but other than that it's not too bad, except for
> +12V. Do the temperature values appear to match anything you've seen in
> the BIOS?

The CPU temperature in the BIOS is 35 and the CPU temperature shown by 
"sensors" is 31. The "sensors" reading for Chip Temp is closer to what 
the BIOS shows, 34 degrees.

>
>> smsc47m1-isa-0600
>> Adapter: ISA adapter
>> fan1:       2925 RPM  (min = 2560 RPM, div = 2)  ALARM
>> fan2:          0 RPM  (min = 3072 RPM, div = 4)  ALARM
>
> Looks reasonable. Only one fan on this system? If there are more, you
> can try increasing fan2_div to 8 if the other fan is a slow one. I
> guess that the first ALARM wears off when running "sensors" again? 2925
> is above the min limit so there should be no ALARM.

There's one fan.
ALARM show up most of the time.

>
> From the above output, the following configuration section would seem
> appropriate for your system:
>
> chip "smsc47m192-i2c-*-2d"
>
>   ignore in0
>   ignore in1
>   ignore in2
>   ignore in3
>   label  in5 "+3.3V"
>   ignore in6
>   ignore in7
>
>   set in4_min   0
>   set in5_min 3.3 * 0.95
>   set in5_max 3.3 * 1.05
>
>   ignore temp3
>
>   set temp1_min  5
>   set temp1_max 50
>   set temp2_min  5
>   set temp2_max 50
>
> Needs to be confirmed:
> * What is wired on in4.

I don't know how to find out this information.

> * Temperature input labels.

Clarify, please.

> * Whether cpu0_vid is real. What CPU is there on this machine?

CPU: Intel Celeron 2.4GHz, 400MHz (Willamette, Northwood according to HP 
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bph07813)

> * Which fan is connected to fan1.

This is the CPU fan.

> * Is there anything connected to fan2.

Nothing connected.

>
> If you can answer the questions above then we can put a good
> configuration file for your machine on the wiki.
>
>> I wouldn't mind test kernel patches. I'll have to figure out how to
>> implement them, but I think I'll be able to manage *fingers crossed*. Whatever I can do to
>> help.
>
> I've put a modified smsc47m1 driver here:
> http://khali.linux-fr.org/devel/misc/smsc47m1/
>
> I would like you to download it and test it. With that driver, you
> should no longer have to do the isaset magic at boot time. It include
> other changes which should hopefully be transparent to you if I didn't
> mess up.
>
> This is a standalone driver, you'll need a proper build environment
> (install make, gcc and the kernel headers) then type "make" then load
> the driver (with insmod.)

Fans are now controlled at startup. Any test I should run?

>
> -- 
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
>

--
Twitter: endersyrinx
GTalk: fidlersean

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Jean Delvare]

Hi Sean,

On Sun, 13 Dec 2009 19:55:58 -0500 (EST), Sean Fidler wrote:
> On Sat, 5 Dec 2009, Jean Delvare wrote:
> 
> > Hi Sean,
> >
> > On Wed, 2 Dec 2009 14:55:37 -0500 (EST), Sean Fidler wrote:
> >> Sensors output:
> >>
> >> smsc47m192-i2c-0-2d
> >> Adapter: SMBus I801 adapter at 1880
> >> +2.5V:       +0.00 V  (min =  +2.90 V, max =  +2.90 V)   ALARM
> >> VCore:       +0.00 V  (min =  +2.99 V, max =  +2.99 V)   ALARM
> >> +3.3V:       +0.00 V  (min =  +4.38 V, max =  +4.35 V)   ALARM
> >> +5V:         +0.00 V  (min =  +6.64 V, max =  +6.64 V)   ALARM
> >> +12V:        +3.12 V  (min = +15.81 V, max = +15.88 V)   ALARM
> >> VCC:         +3.35 V  (min =  +4.38 V, max =  +3.83 V)   ALARM
> >> +1.5V:       +0.05 V  (min =  +1.49 V, max =  +1.99 V)   ALARM
> >> +1.8V:       +0.00 V  (min =  +2.39 V, max =  +2.39 V)   ALARM
> >> Chip Temp:   +34.0°C  (low  = -17.0°C, high =  -1.0°C)  ALARM
> >> CPU Temp:    +28.0°C  (low  =  -1.0°C, high = -33.0°C)  ALARM
> >> Sys Temp:      FAULT  (low  = -65.0°C, high =  -1.0°C)  ALARM
> >> cpu0_vid:   +1.475 V
> >
> > Not many inputs wired, and the min voltage and high temperature limits
> > are pretty wrong, but other than that it's not too bad, except for
> > +12V. Do the temperature values appear to match anything you've seen in
> > the BIOS?
> 
> The CPU temperature in the BIOS is 35 and the CPU temperature shown by 
> "sensors" is 31. The "sensors" reading for Chip Temp is closer to what 
> the BIOS shows, 34 degrees.

The BIOS and "sensors" temperatures for the CPU aren't expected to
match exactly, because often the BIOS stands in a busy loop (waiting
for keys to be pressed) which keeps the CPU busy and thus hot.

And actually... reading the SMSC LPC47M192's datasheet again, it
happens that temp1 is internal to that chip. Which means that temp2 has
to be the CPU temperature.

> >> smsc47m1-isa-0600
> >> Adapter: ISA adapter
> >> fan1:       2925 RPM  (min = 2560 RPM, div = 2)  ALARM
> >> fan2:          0 RPM  (min = 3072 RPM, div = 4)  ALARM
> >
> > Looks reasonable. Only one fan on this system? If there are more, you
> > can try increasing fan2_div to 8 if the other fan is a slow one. I
> > guess that the first ALARM wears off when running "sensors" again? 2925
> > is above the min limit so there should be no ALARM.
> 
> There's one fan.

OK, good.

> ALARM show up most of the time.

This is odd and unexpected, but I am not too familiar with the smsc47m1
driver. A quick look at the code did not reveal anything obviously
incorrect.

> > (...)
> > Needs to be confirmed:
> > * What is wired on in4.
> 
> I don't know how to find out this information.

It might be difficult, especially if the BIOS doesn't display anything.
Is the reported value stable? With a voltage like that, it could be the
battery. Without help from Compaq, it will be difficult to come to a
conclusion.

> > * Temperature input labels.
> 
> Clarify, please.

Whether CPU temp was temp1 or temp2, but already clarified above.

> > * Whether cpu0_vid is real. What CPU is there on this machine?
> 
> CPU: Intel Celeron 2.4GHz, 400MHz (Willamette, Northwood according to HP 
> http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bph07813)

HP is probably right, the fastest Willamette-based Celeron was running
at 1.8 GHz.

The good news is that 1.475V is a valid Vcore for your CPU, which
suggests that cpu0_vid is correct.

> > * Which fan is connected to fan1.
> 
> This is the CPU fan.
> 
> > * Is there anything connected to fan2.
> 
> Nothing connected.

OK.

I've created the following config:
http://www.lm-sensors.org/wiki/Configurations/Compaq/Presario-S4000NX

Let me know if you think it needs changes.

> > (...)
> > I've put a modified smsc47m1 driver here:
> > http://khali.linux-fr.org/devel/misc/smsc47m1/
> >
> > I would like you to download it and test it. With that driver, you
> > should no longer have to do the isaset magic at boot time. It include
> > other changes which should hopefully be transparent to you if I didn't
> > mess up.
> >
> > This is a standalone driver, you'll need a proper build environment
> > (install make, gcc and the kernel headers) then type "make" then load
> > the driver (with insmod.)
> 
> Fans are now controlled at startup. Any test I should run?

If the driver is working fine, that's great. Please test that you are
able to unload and reload it. I would also appreciate if you could
report the contents of /proc/ioports while the driver is loaded.

Thanks,
-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

[lm-sensors] LPC47M192-NC Fans

[b13johnson]

[-- Attachment #1.1: Type: text/plain, Size: 2716 bytes --]

Hi Jean, 

I am having what I believe is a similar problem to what Sean had. I have an HP pavilion desktop computer. I couldn't get sensors-detect to work with my smsc47m1 driver to work until I downloaded and built your modified one. Once I installed it, I got the following snippet from sensors-detect: 

---------------------------------------------------------- 
Some Super I/O chips contain embedded 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): y 
Probing for Super-I/O at 0x2e/0x2f 
Trying family `National Semiconductor'... No 
Trying family `SMSC'... Yes 
Found `SMSC LPC47M15x/192/997 Super IO Fan Sensors' Success! 
(address 0x600, driver `smsc47m1') 
Probing for Super-I/O at 0x4e/0x4f 
Trying family `National Semiconductor'... No 
Trying family `SMSC'... No 
Trying family `VIA/Winbond/Nuvoton/Fintek'... No 
Trying family `ITE'... No 
---------------------------------------------------------- 

However, at the end I get: 

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

Driver `smsc47m1': 
* ISA bus, address 0x600 
Chip `SMSC LPC47M15x/192/997 Super IO Fan Sensors' (confidence: 9) 

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): y 
Starting lm_sensors: loading module smsc47m1 No sensors found! 
Make sure you loaded all the kernel drivers you need. 
Try sensors-detect to find out which these are. 
[FAILED] 
Unloading i2c-dev... OK 
---------------------------------------------------------- 

If I answer no to the last question, and try to run modprobe manually, I get: 

---------------------------------------------------------- 
[root@Backup-P4 smsc47m1_driver]# modprobe smsc47m1 
FATAL: Error inserting smsc47m1 (/lib/modules/2.6.31.9-174.fc12.i686.PAE/kernel/drivers/hwmon/smsc47m1.ko): Device or resource busy 
---------------------------------------------------------- 

The log file "messages" has the following: 

---------------------------------------------------------- 
Jan 18 23:06:51 localhost kernel: i2c /dev entries driver 
Jan 18 23:07:05 localhost kernel: smsc47m1: Found SMSC LPC47M15x/LPC47M192/LPC47M997 
Jan 18 23:07:05 localhost kernel: ACPI: I/O resource smsc47m1 [0x604-0x604] conflicts with ACPI region SMC_ [0x600 
-0x65f] 
Jan 18 23:07:05 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead 
of the native driver 
---------------------------------------------------------- 

I'm running Fedora Core kernel 2.6.31.9-174.fc12.i686.PAE 

Do you have any ideas? I really appreciate your help. 

Thanks, 
Bob 


[-- Attachment #1.2: Type: text/html, Size: 4423 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Gabriel C]

On 20.01.2010 05:30, b13johnson@comcast.net wrote:

Hello,

...
> [root@Backup-P4 smsc47m1_driver]# modprobe smsc47m1 
> FATAL: Error inserting smsc47m1 (/lib/modules/2.6.31.9-174.fc12.i686.PAE/kernel/drivers/hwmon/smsc47m1.ko): Device or resource busy 
> ---------------------------------------------------------- 
> 
> The log file "messages" has the following: 
> 
> ---------------------------------------------------------- 
> Jan 18 23:06:51 localhost kernel: i2c /dev entries driver 
> Jan 18 23:07:05 localhost kernel: smsc47m1: Found SMSC LPC47M15x/LPC47M192/LPC47M997 
> Jan 18 23:07:05 localhost kernel: ACPI: I/O resource smsc47m1 [0x604-0x604] conflicts with ACPI region SMC_ [0x600 
> -0x65f] 
> Jan 18 23:07:05 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead 
> of the native driver 
> ---------------------------------------------------------- 
> 
> I'm running Fedora Core kernel 2.6.31.9-174.fc12.i686.PAE 
> 
> Do you have any ideas? I really appreciate your help. 
>


I guess you have to boot your kernel with :

acpi_enforce_resources=no

> Thanks, 
> Bob 

Best Regards,

Gabriel C

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Jean Delvare]

On Wed, 20 Jan 2010 09:20:19 +0100, Gabriel C wrote:
> On 20.01.2010 05:30, b13johnson@comcast.net wrote:
> 
> Hello,
> 
> ...
> > [root@Backup-P4 smsc47m1_driver]# modprobe smsc47m1 
> > FATAL: Error inserting smsc47m1 (/lib/modules/2.6.31.9-174.fc12.i686.PAE/kernel/drivers/hwmon/smsc47m1.ko): Device or resource busy 
> > ---------------------------------------------------------- 
> > 
> > The log file "messages" has the following: 
> > 
> > ---------------------------------------------------------- 
> > Jan 18 23:06:51 localhost kernel: i2c /dev entries driver 
> > Jan 18 23:07:05 localhost kernel: smsc47m1: Found SMSC LPC47M15x/LPC47M192/LPC47M997 
> > Jan 18 23:07:05 localhost kernel: ACPI: I/O resource smsc47m1 [0x604-0x604] conflicts with ACPI region SMC_ [0x600-0x65f] 

Unfortunately, in your case ACPI reserved the whole port range. It may
or may not need all these ports, one would have to disassemble the DSDT
to tell. I changed the smsc47m1 driver to play fair and only request
the ports it needs, but if ACPI on its side isn't fair, it doesn't help
at all.

> > Jan 18 23:07:05 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead 
> > of the native driver 
> > ---------------------------------------------------------- 
> > 
> > I'm running Fedora Core kernel 2.6.31.9-174.fc12.i686.PAE 
> > 
> > Do you have any ideas? I really appreciate your help. 
> >
> 
> 
> I guess you have to boot your kernel with :
> 
> acpi_enforce_resources=no

This will certainly work, but if ACPI really accesses these ports, you
might get in trouble (although the smsc47m1 case is probably one of the
least dangerous, thanks to the flat I/O access model.)

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Jean Delvare]

Hi Sean,

Please keep the list in the loop.

On Thu, 11 Feb 2010 19:25:49 -0500, Sean Fidler wrote:
> The driver unloaded and loaded again without issue.
> /proc/ioports output:
> (...)
> 0600-067f : smsc47m1
>   0604-0604 : smsc47m1
>   0633-0636 : smsc47m1
>   0656-065c : smsc47m1

OK, looks very good.

> I have a question regarding sensors.conf, I updated the file with the text
> from the configuration you posted, however, when I run sensors I see the
> same information as before (i.e. sensors.conf not being used). If I run
> sensors -c /etc/sensors.conf then the output is as expected. Just wanted to
> confirm that this is correct functionality.

Maybe you have /etc/sensors3.conf too? It takes precedence
over /etc/sensors.conf for lm-sensors 3.x. If you are using lm-sensors
3.x then you want to edit /etc/sensors3.conf, not /etc/sensors.conf.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Sean Fidler]

Hi, Jean,

I've run into a problem with the driver you wrote, smsc47m1.c
(http://khali.linux-fr.org/devel/misc/smsc47m1/). The server has been
moved from Ubuntu 9.10 to 8.04 (same hardware, Compaq Presario
S4000NX). When running "make" the following errors occur:

CC [M]  /home/sean/smsc47m1.o
/home/sean/smsc47m1.c: In function ‘smsc47m1_handle_resources’:
/home/sean/smsc47m1.c:558: error: implicit declaration of function
‘acpi_check_region’
make[2]: *** [/home/sean/smsc47m1.o] Error 1
make[1]: *** [_module_/home/sean] Error 2
make: *** [modules] Error 2

The steps (i.e. isaset…) that were indicated in this thread work
correctly, as before.

—Sean—

On Fri, Feb 12, 2010 at 3:42 AM, Jean Delvare <khali@linux-fr.org> wrote:
>
> Hi Sean,
>
> Please keep the list in the loop.
>
> On Thu, 11 Feb 2010 19:25:49 -0500, Sean Fidler wrote:
> > The driver unloaded and loaded again without issue.
> > /proc/ioports output:
> > (...)
> > 0600-067f : smsc47m1
> >   0604-0604 : smsc47m1
> >   0633-0636 : smsc47m1
> >   0656-065c : smsc47m1
>
> OK, looks very good.
>
> > I have a question regarding sensors.conf, I updated the file with the text
> > from the configuration you posted, however, when I run sensors I see the
> > same information as before (i.e. sensors.conf not being used). If I run
> > sensors -c /etc/sensors.conf then the output is as expected. Just wanted to
> > confirm that this is correct functionality.
>
> Maybe you have /etc/sensors3.conf too? It takes precedence
> over /etc/sensors.conf for lm-sensors 3.x. If you are using lm-sensors
> 3.x then you want to edit /etc/sensors3.conf, not /etc/sensors.conf.
>
> --
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Jean Delvare]

Hi Sean,

On Mon, 8 Mar 2010 02:26:26 -0500, Sean Fidler wrote:
> I've run into a problem with the driver you wrote, smsc47m1.c
> (http://khali.linux-fr.org/devel/misc/smsc47m1/). The server has been
> moved from Ubuntu 9.10 to 8.04 (same hardware, Compaq Presario
> S4000NX). When running "make" the following errors occur:
> 
> CC [M]  /home/sean/smsc47m1.o
> /home/sean/smsc47m1.c: In function ‘smsc47m1_handle_resources’:
> /home/sean/smsc47m1.c:558: error: implicit declaration of function
> ‘acpi_check_region’
> make[2]: *** [/home/sean/smsc47m1.o] Error 1
> make[1]: *** [_module_/home/sean] Error 2
> make: *** [modules] Error 2
> 
> The steps (i.e. isaset…) that were indicated in this thread work
> correctly, as before.

I have put an updated driver at:
http://khali.linux-fr.org/devel/misc/smsc47m1/

The new version should work with both recent and older kernels, at
least down to kernel version 2.6.24, maybe even older.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Sean Fidler]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1397 bytes --]

Hi, Jean,

Thanks for the updated driver.

I've run into a second issue: I have to manually insmod the smsc47m1.ko 
file before I'm able to modprobe smsc47m1.

Previously, I used insmod once and the smsc47m1 module loaded properly 
at boot.

Thanks,
Sean

On Mon, 8 Mar 2010, Jean Delvare wrote:

> Hi Sean,
>
> On Mon, 8 Mar 2010 02:26:26 -0500, Sean Fidler wrote:
>> I've run into a problem with the driver you wrote, smsc47m1.c
>> (http://khali.linux-fr.org/devel/misc/smsc47m1/). The server has been
>> moved from Ubuntu 9.10 to 8.04 (same hardware, Compaq Presario
>> S4000NX). When running "make" the following errors occur:
>>
>> CC [M]  /home/sean/smsc47m1.o
>> /home/sean/smsc47m1.c: In function ‘smsc47m1_handle_resources’:
>> /home/sean/smsc47m1.c:558: error: implicit declaration of function
>> ‘acpi_check_region’
>> make[2]: *** [/home/sean/smsc47m1.o] Error 1
>> make[1]: *** [_module_/home/sean] Error 2
>> make: *** [modules] Error 2
>>
>> The steps (i.e. isaset…) that were indicated in this thread work
>> correctly, as before.
>
> I have put an updated driver at:
> http://khali.linux-fr.org/devel/misc/smsc47m1/
>
> The new version should work with both recent and older kernels, at
> least down to kernel version 2.6.24, maybe even older.
>
> -- 
> Jean Delvare
> http://khali.linux-fr.org/wishlist.html
>

--
Twitter: endersyrinx
GTalk: fidlersean

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Jean Delvare]

Hi Sean,

On Wed, 10 Mar 2010 11:19:44 -0500 (EST), Sean Fidler wrote:
> Thanks for the updated driver.
> 
> I've run into a second issue: I have to manually insmod the smsc47m1.ko 
> file before I'm able to modprobe smsc47m1.
> 
> Previously, I used insmod once and the smsc47m1 module loaded properly 
> at boot.

I doubt it. insmod and modprobe do pretty much the same thing, except
that modprobe has some magic added. If you run "insmod ./smsc47m1.ko",
then a subsequent "modprobe smsc47m1" is a no-op: modprobe sees that the
module is already loaded and does nothing.

If you want to load the driver at boot time, you have 2 options:
1* Use insmod, with the full path to the new module file.
2* Copy the new module file over the old one in /lib/modules, and then
   you can call modprobe.

Maybe you did 2* last time, and don't remember the step where you
copied the module file around.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] LPC47M192-NC Fans

[Sean Fidler]

Thanks! Yeah, I must have missed a step that step during this round.

On Wed, 10 Mar 2010, Jean Delvare wrote:

> Hi Sean,
>
> On Wed, 10 Mar 2010 11:19:44 -0500 (EST), Sean Fidler wrote:
>> Thanks for the updated driver.
>>
>> I've run into a second issue: I have to manually insmod the smsc47m1.ko
>> file before I'm able to modprobe smsc47m1.
>>
>> Previously, I used insmod once and the smsc47m1 module loaded properly
>> at boot.
>
> I doubt it. insmod and modprobe do pretty much the same thing, except
> that modprobe has some magic added. If you run "insmod ./smsc47m1.ko",
> then a subsequent "modprobe smsc47m1" is a no-op: modprobe sees that the
> module is already loaded and does nothing.
>
> If you want to load the driver at boot time, you have 2 options:
> 1* Use insmod, with the full path to the new module file.
> 2* Copy the new module file over the old one in /lib/modules, and then
>   you can call modprobe.
>
> Maybe you did 2* last time, and don't remember the step where you
> copied the module file around.
>
> -- 
> Jean Delvare
>

--
Twitter: endersyrinx
GTalk: fidlersean

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors