* No sensors found!
2005-05-19 6:24 No sensors found! Jennifer Villar
@ 2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Mark Studebaker @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
That's your problem then.
Perhaps Redhat 9 includes the module but it is lost :);
perhaps it includes it but it wasn't built by default, and you'll have to build it;
perhaps it doesn't include it and you'll need to install our package from our website.
If you don't know how to do this it will be a good learning experience :)
good luck
mds
Jennifer Villar wrote:
> I get the following error even though I believe I ran it before without
> error.
>
> modprobe: Can't locate module w83627hf
>
> Attached is the dmesg file. I didn't see anything in it that refers the
> the w83627hf module.
>
> When I said I am new to Linux I mean several days new so if I miss
> something I wouldn't be surprised.
>
>
> Thanks for your speedy response.
>
> -Jenn
>
> -----Original Message-----
> From: Mark Studebaker [mailto:mds4@verizon.net]
> Sent: Friday, March 26, 2004 5:07 PM
> To: Jennifer Villar
> Cc: sensors@Stimpy.netroedge.com
> Subject: Re: No sensors found!
>
> you don't show w83627hf loaded.
> modprobe it again to be sure then check dmesg for clues.
>
> Jennifer Villar wrote:
>
>> -->
>>
>>I am a complete newbie here cutting my teeth on RedHat 9 Kernel
>>2.4.20-8smp. I am trying to get lm_sensors to work but I continually
>
> get
>
>>the "No Sensors found!" error. I have followed the instructions that
>>sensors-detect has provided (except the /etc/rc* entries as I am not
>>sure which file to put the entries into, any?).
>>
>>
>>
>>I am using a Supermicro server with an Intel 857 chipset and the Super
>
>
>>P4SCA motherboard. Unfortunately I cannot look at the mother board as
>>the system is racked.
>>
>>
>>
>>Here is some of the information I have that may shed light to someone
>>who knows a thing or two about this stuff.
>>
>>
>>
>># Results from lsmod
>>
>>
>>
>>Module Size Used by Not tainted
>>
>>i2c-isa 1868 0 (unused)
>>
>>i2c-dev 5636 0
>>
>>i2c-philips-par 3360 0 (unused)
>>
>>parport 39072 0 [i2c-philips-par]
>>
>>i2c-elv 2408 0
>>
>>i2c-algo-bit 8872 1 [i2c-philips-par i2c-elv]
>>
>>i2c-proc 9232 0
>>
>>i2c-core 19908 0 [i2c-isa i2c-dev i2c-algo-bit
>
> i2c-proc]
>
>>autofs 13684 0 (autoclean) (unused)
>>
>>e1000 70400 1
>>
>>ipt_REJECT 3928 0 (autoclean)
>>
>>iptable_filter 2412 0 (autoclean)
>>
>>ip_tables 15864 2 [ipt_REJECT iptable_filter]
>>
>>keybdev 2976 0 (unused)
>>
>>mousedev 5656 0 (unused)
>>
>>hid 22308 0 (unused)
>>
>>input 6208 0 [keybdev mousedev hid]
>>
>>usb-uhci 27404 0 (unused)
>>
>>ehci-hcd 20456 0 (unused)
>>
>>usbcore 82592 1 [hid usb-uhci ehci-hcd]
>>
>>ext3 73376 2
>>
>>jbd 56336 2 [ext3]
>>
>>
>>
>># Output of sensors-detect
>>
>> Detects correctly:
>>
>> * ISA bus address 0x0290 (Busdriver `i2c-isa')
>>
>> Chip `Winbond W83627HF Super IO 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)? Driver `w83627hf' (should be inserted):
>>
>> Detects correctly:
>>
>> * ISA bus address 0x0290 (Busdriver `i2c-isa')
>>
>> Chip `Winbond W83627HF Super IO Sensors' (confidence: 9)
>>
>>
>>
>>To make the sensors modules behave correctly, add these lines to
>>
>>/etc/modules.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
>>
>>modprobe w83627hf
>>
>># sleep 2 # optional
>>
>>/usr/bin/sensors -s # recommended
>>
>>#----cut here----
>>
>>
>>
>>Any information would be greatly appreciated.
>>
>>
>>
>>-Jennifer
>
>
>
^ permalink raw reply [flat|nested] 9+ messages in thread* No sensors found!
2005-05-19 6:24 No sensors found! Jennifer Villar
2005-05-19 6:24 ` Mark Studebaker
@ 2005-05-19 6:24 ` Mark Studebaker
2006-01-26 17:53 ` [lm-sensors] " samag70-2
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Mark Studebaker @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
you don't show w83627hf loaded.
modprobe it again to be sure then check dmesg for clues.
Jennifer Villar wrote:
> -->
>
> I am a complete newbie here cutting my teeth on RedHat 9 Kernel
> 2.4.20-8smp. I am trying to get lm_sensors to work but I continually get
> the ?No Sensors found!? error. I have followed the instructions that
> sensors-detect has provided (except the /etc/rc* entries as I am not
> sure which file to put the entries into, any?).
>
>
>
> I am using a Supermicro server with an Intel 857 chipset and the Super
> P4SCA motherboard. Unfortunately I cannot look at the mother board as
> the system is racked.
>
>
>
> Here is some of the information I have that may shed light to someone
> who knows a thing or two about this stuff.
>
>
>
> # Results from lsmod
>
>
>
> Module Size Used by Not tainted
>
> i2c-isa 1868 0 (unused)
>
> i2c-dev 5636 0
>
> i2c-philips-par 3360 0 (unused)
>
> parport 39072 0 [i2c-philips-par]
>
> i2c-elv 2408 0
>
> i2c-algo-bit 8872 1 [i2c-philips-par i2c-elv]
>
> i2c-proc 9232 0
>
> i2c-core 19908 0 [i2c-isa i2c-dev i2c-algo-bit i2c-proc]
>
> autofs 13684 0 (autoclean) (unused)
>
> e1000 70400 1
>
> ipt_REJECT 3928 0 (autoclean)
>
> iptable_filter 2412 0 (autoclean)
>
> ip_tables 15864 2 [ipt_REJECT iptable_filter]
>
> keybdev 2976 0 (unused)
>
> mousedev 5656 0 (unused)
>
> hid 22308 0 (unused)
>
> input 6208 0 [keybdev mousedev hid]
>
> usb-uhci 27404 0 (unused)
>
> ehci-hcd 20456 0 (unused)
>
> usbcore 82592 1 [hid usb-uhci ehci-hcd]
>
> ext3 73376 2
>
> jbd 56336 2 [ext3]
>
>
>
> # Output of sensors-detect
>
> Detects correctly:
>
> * ISA bus address 0x0290 (Busdriver `i2c-isa')
>
> Chip `Winbond W83627HF Super IO 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)? Driver `w83627hf' (should be inserted):
>
> Detects correctly:
>
> * ISA bus address 0x0290 (Busdriver `i2c-isa')
>
> Chip `Winbond W83627HF Super IO Sensors' (confidence: 9)
>
>
>
> To make the sensors modules behave correctly, add these lines to
>
> /etc/modules.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
>
> modprobe w83627hf
>
> # sleep 2 # optional
>
> /usr/bin/sensors -s # recommended
>
> #----cut here----
>
>
>
> Any information would be greatly appreciated.
>
>
>
> -Jennifer
>
^ permalink raw reply [flat|nested] 9+ messages in thread* [lm-sensors] No sensors found!
2005-05-19 6:24 No sensors found! Jennifer Villar
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
@ 2006-01-26 17:53 ` samag70-2
2006-01-26 18:36 ` Jim Cromie
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: samag70-2 @ 2006-01-26 17:53 UTC (permalink / raw)
To: lm-sensors
I have followed the directions, but I am having a tough time making this work. After going through all the steps, I still get the messageNo sensors found!
Here are the steps I went through, sorry if this is long.
[root at dieppe ~]# rpm -qa | grep lm_sensors
lm_sensors-devel-2.9.2-42.rhfc4.at
lm_sensors-2.9.2-42.rhfc4.at
[root at dieppe ~]# lsmod
Module Size Used by
eeprom 7377 0
i2c_piix4 9041 0
i2c_core 22081 2 eeprom,i2c_piix4
ipv6 249761 18
autofs4 19653 2
sunrpc 141437 1
ipt_REJECT 5953 1
ipt_state 1985 8
ip_conntrack 51953 1 ipt_state
nfnetlink 6617 1 ip_conntrack
iptable_filter 3137 1
ip_tables 20033 3 ipt_REJECT,ipt_state,iptable_filter
video 16197 0
button 6737 0
battery 9541 0
ac 4933 0
uhci_hcd 32465 0
eepro100 30673 0
e100 36545 0
mii 5313 2 eepro100,e100
floppy 61957 0
dm_snapshot 17773 0
dm_zero 2113 0
dm_mirror 22421 0
ext3 129993 8
jbd 57813 1 ext3
dm_mod 56797 12 dm_snapshot,dm_zero,dm_mirror
sym53c8xx 79193 2
scsi_transport_spi 21185 1 sym53c8xx
sd_mod 18625 3
scsi_mod 135529 3 sym53c8xx,scsi_transport_spi,sd_mod
[root at dieppe ~]# rmmod eeprom i2c_piix4 i2c_core
[root at dieppe ~]# sensors-detect
# sensors-detect revision 1.393 (2005/08/30 18:51:18)
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
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.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): YES
Probing for PCI bus adapters...
Use driver `i2c-piix4' for device 00:14.3: Intel 82371AB PIIX4 ACPI
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-piix4' (say NO if built into your kernel)? (YES/no): YES
Module loaded succesfully.
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 not loaded. Do you want to load it now? (YES/no): YES
Module loaded succesfully.
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 PIIX4 adapter at fc00
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x32
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x52
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
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): YES
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
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): YES
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
Failed! (skipping family)
Do you want to scan for secondary Super I/O sensors? (YES/no): YES
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
Failed! (skipping family)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus PIIX4 adapter at fc00'
Busdriver `i2c-piix4', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus PIIX4 adapter at fc00'
Busdriver `i2c-piix4', I2C address 0x51
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus PIIX4 adapter at fc00'
Busdriver `i2c-piix4', I2C address 0x52
Chip `SPD EEPROM' (confidence: 8)
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)? smbus
To make the sensors modules behave correctly, add these lines to
/etc/modules.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-piix4
# I2C chip drivers
modprobe eeprom
# 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): YES
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
[root at dieppe ~]# modprobe i2c-piix4
[root at dieppe ~]# modprobe eeprom
[root at dieppe ~]# /usr/bin/sensors -s
No sensors found!
---------
Any suggestions?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060126/59286516/attachment.html
^ permalink raw reply [flat|nested] 9+ messages in thread* [lm-sensors] No sensors found!
2005-05-19 6:24 No sensors found! Jennifer Villar
` (2 preceding siblings ...)
2006-01-26 17:53 ` [lm-sensors] " samag70-2
@ 2006-01-26 18:36 ` Jim Cromie
2006-01-26 18:44 ` samag70-2
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Jim Cromie @ 2006-01-26 18:36 UTC (permalink / raw)
To: lm-sensors
samag70-2 at yahoo.ca wrote:
<snip>
> 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)? smbus
I suspect youre running afoul on this question (which IIRC is going away
soon,
since ISA is faster when its available)
anyway, in sensors-detect packaged in lm_sensors-2.9.1-3.FC4.2,
the answer is being parsed by this:
my $use_isa = not <STDIN> =~ /\s*[Ss]/;
since your answer started with 's', youve told it not to use isa.
try rerunning, hit return for this question, and youll get ISA used.
Then see what it recommends next.
good luck.
pls report back ok/not
^ permalink raw reply [flat|nested] 9+ messages in thread* [lm-sensors] No sensors found!
2005-05-19 6:24 No sensors found! Jennifer Villar
` (3 preceding siblings ...)
2006-01-26 18:36 ` Jim Cromie
@ 2006-01-26 18:44 ` samag70-2
2006-01-26 19:16 ` Rudolf Marek
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: samag70-2 @ 2006-01-26 18:44 UTC (permalink / raw)
To: lm-sensors
Thanks for the fast response.
I get the exact same output and results even if I choose ISA at that step. I have tried removing/reinstalling the software, unloading/loading modules, re-running sensors-detect many times and I'm not having any luck. I think I am missing something. Or my hardware is not supported.
Sam
Jim Cromie <jim.cromie at gmail.com> wrote: samag70-2 at yahoo.ca wrote:
> 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)? smbus
I suspect youre running afoul on this question (which IIRC is going away
soon,
since ISA is faster when its available)
anyway, in sensors-detect packaged in lm_sensors-2.9.1-3.FC4.2,
the answer is being parsed by this:
my $use_isa = not =~ /\s*[Ss]/;
since your answer started with 's', youve told it not to use isa.
try rerunning, hit return for this question, and youll get ISA used.
Then see what it recommends next.
good luck.
pls report back ok/not
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060126/67ffc6af/attachment-0001.html
^ permalink raw reply [flat|nested] 9+ messages in thread* [lm-sensors] No sensors found!
2005-05-19 6:24 No sensors found! Jennifer Villar
` (4 preceding siblings ...)
2006-01-26 18:44 ` samag70-2
@ 2006-01-26 19:16 ` Rudolf Marek
2006-01-27 13:46 ` samag70-2
2006-01-27 17:06 ` Rudolf Marek
7 siblings, 0 replies; 9+ messages in thread
From: Rudolf Marek @ 2006-01-26 19:16 UTC (permalink / raw)
To: lm-sensors
Hello,
What motherboard it is? What model/brand?
thanks,
Regards
Rudolf
^ permalink raw reply [flat|nested] 9+ messages in thread* [lm-sensors] No sensors found!
2005-05-19 6:24 No sensors found! Jennifer Villar
` (5 preceding siblings ...)
2006-01-26 19:16 ` Rudolf Marek
@ 2006-01-27 13:46 ` samag70-2
2006-01-27 17:06 ` Rudolf Marek
7 siblings, 0 replies; 9+ messages in thread
From: samag70-2 @ 2006-01-27 13:46 UTC (permalink / raw)
To: lm-sensors
The server is a Compaq Prosignia 720.
http://h18002.www1.hp.com/products/quickspecs/10536_div/10536_div.HTML
I think the motherboard is a 141534-001 Compaq Motherboard
http://www.dectrader.com/Motherboard-processor-board-Does-not-include-processor-pr-36998.html
Sam
Rudolf Marek <r.marek at sh.cvut.cz> wrote: Hello,
What motherboard it is? What model/brand?
thanks,
Regards
Rudolf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060127/88d4839e/attachment.html
^ permalink raw reply [flat|nested] 9+ messages in thread* [lm-sensors] No sensors found!
2005-05-19 6:24 No sensors found! Jennifer Villar
` (6 preceding siblings ...)
2006-01-27 13:46 ` samag70-2
@ 2006-01-27 17:06 ` Rudolf Marek
7 siblings, 0 replies; 9+ messages in thread
From: Rudolf Marek @ 2006-01-27 17:06 UTC (permalink / raw)
To: lm-sensors
samag70-2 at yahoo.ca wrote:
> The server is a Compaq Prosignia 720.
Aha, I think compaq has its own utillity called cpqhealth.
Please google for it. (we do not have any clue how the sensors are done on compaq)
Thanks,
Regards
Rudolf
^ permalink raw reply [flat|nested] 9+ messages in thread