* [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
@ 2005-06-13 11:44 ` Jean Delvare
2005-06-13 12:25 ` Jean Delvare
` (13 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2005-06-13 11:44 UTC (permalink / raw)
To: lm-sensors
Hi Sukhdeep,
> I am using the chip W83697F chip.
I assume W83697_H_F?
> I am getting this error when loading the w83781d driver.
> w83781d.o: Subclient 0 registration at address 0x49 failed
This is quite strange, the W83697HF is an ISA-only chip, so it isn't
supposed to have subclients. Which version of lm_sensors are you using?
On which kernel?
> I have tried modprobe w83781d init=0 force_subclients=0,0x2c,0x4a,0x4b
> without any succes..
Which isn't surprising, as force_subclients only works for I2C chips,
not ISA ones.
> Can you please provide some insights.. I have run out of options :(
Please try the w83627hf driver instead. The support of ISA-only chips in
the w83781d driver is deprecated and will be removed soon.
--
Jean Delvare
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
2005-06-13 11:44 ` Jean Delvare
@ 2005-06-13 12:25 ` Jean Delvare
2005-06-13 12:41 ` Sukhdeep Johar
` (12 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2005-06-13 12:25 UTC (permalink / raw)
To: lm-sensors
Hi Sukhdeep,
> The chip is W83697F - that's what written on the chip.
This chip doesn't have hardware monitoring capabilities. So the values
you get may be from a different chip.
> I think it's the W83697_T_H_F chip..
I don't think so. The only THF chip is the the W836_2_7THF, as least as
far as I know.
> Is W83697_THF also ISA-only ?
All W826x7 chips are Super-I/O chips, so they do at least have ISA
access, which is better anyway. I think only the older W83627HF chip has
I2C access in addition.
What motherboard is it?
Please provide the full output of sensors-detect. Don't forget to unload
the w83781d driver beforehand (or any other i2c chip driver).
--
Jean Delvare
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
2005-06-13 11:44 ` Jean Delvare
2005-06-13 12:25 ` Jean Delvare
@ 2005-06-13 12:41 ` Sukhdeep Johar
2005-06-13 19:15 ` [lm-sensors] w83781d.o: Subclient 0 registration at address Jean Delvare
` (11 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Sukhdeep Johar @ 2005-06-13 12:41 UTC (permalink / raw)
To: lm-sensors
Jean,
The Motherbowrd is from VIAPRO, it's similar to kt400. The
sensors-detect output is given below :
>> This chip doesn't have hardware monitoring capabilities. So the values
>> you get may be from a different chip.
Oh, but i see only W83697F on the motherboard.
WS5K#sensors-detect
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.
IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW!
IBM Thinkpads have a severely broken i2c/SMBus implementation, just scanning
the bus will break your Thinkpad forever!
If this is a non-Thinkpad IBM, we still suggest you press CTRL+C. We have
had users reporting system breakage on other IBM systems as well.
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-viapro' for device 00:11.0: VIA Technologies VT8233
VLink South Bridge
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Module `i2c-viapro' 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 Via Pro adapter at 0400
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x29
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Success!
(confidence 8, driver `w83781d'), other addresses: 0x48 0x49
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Analog Devices ADM1021'... Failed!
Probing for `Analog Devices ADM1021A/ADM1023'... Failed!
Probing for `Maxim MAX1617'... Failed!
Probing for `Maxim MAX1617A'... Failed!
Probing for `TI THMC10'... Failed!
Probing for `National Semiconductor LM84'... Failed!
Probing for `Genesys Logic GL523SM'... Failed!
Probing for `Onsemi MC1066'... Failed!
Probing for `Maxim MAX1619'... Failed!
Probing for `National Semiconductor LM82'... Failed!
Probing for `National Semiconductor LM83'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed!
Client found at address 0x2d
Probing for `Myson MTP008'... Failed!
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `National Semiconductor LM85 or LM96000'... Failed!
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... Failed!
Probing for `SMSC EMC6D100 or EMC6D101'... Failed!
Probing for `National Semiconductor LM87'... Failed!
Probing for `National Semiconductor LM93'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Success!
(confidence 8, driver `w83781d'), other addresses: 0x48 0x49
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Winbond W83L784R/AR'... Failed!
Probing for `Winbond W83L785R'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x00'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x80'... Failed!
Probing for `Genesys Logic GL520SM'... Failed!
Probing for `Genesys Logic GL525SM'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1026'... Failed!
Probing for `Analog Devices ADM1025'... Failed!
Probing for `Philips NE1619'... Failed!
Probing for `Analog Devices ADM1024'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `Analog Devices ADM1030'... Failed!
Probing for `Analog Devices ADM1031'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed!
Probing for `ALi M5879'... Failed!
Client found at address 0x48
Probing for `National Semiconductor LM75'... Failed!
Probing for `National Semiconductor LM77'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6650/MAX6651'... Failed!
Probing for `National Semiconductor LM92'... Failed!
Probing for `National Semiconductor LM76'... Failed!
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x49
Probing for `National Semiconductor LM75'... Failed!
Probing for `National Semiconductor LM77'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `National Semiconductor LM92'... Failed!
Probing for `National Semiconductor LM76'... Failed!
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
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 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 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 IT8705F / IT8712F / 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! (0x60)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x60)
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0x60)
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x60)
Probing for `Winbond W83697HF Super IO Sensors'
Success... but not activated
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0x60)
Probing for `Winbond W83L517D Super IO'
Failed! (0x60)
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)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83781d' (should be inserted):
Detects correctly:
* Bus `SMBus Via Pro adapter at 0400' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x29 (and 0x48 0x49)
Chip `Winbond W83782D' (confidence: 8)
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus Via Pro adapter at 0400' (Non-I2C SMBus adapter)
Busdriver `i2c-viapro', I2C address 0x50
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)?
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-viapro
# I2C chip drivers
modprobe w83781d
modprobe eeprom
# sleep 2 # optional
/usr/local/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.
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
WS5K#
regards,
Sukhdee[
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (2 preceding siblings ...)
2005-06-13 12:41 ` Sukhdeep Johar
@ 2005-06-13 19:15 ` Jean Delvare
2005-06-13 22:25 ` [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Yani Ioannou
` (10 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2005-06-13 19:15 UTC (permalink / raw)
To: lm-sensors
Hi Sukhdeep,
> The Motherbowrd is from VIAPRO, it's similar to kt400.
VIA Pro / KT400 is the name of the South Bridge. This doesn't tell me
the motherboard itself is. Have you no idea? dmidecode [1] may help.
[1] http://www.nongnu.org/dmidecode/
> Client found at address 0x29
> (...)
> Probing for `Winbond W83782D'... Success!
> (confidence 8, driver `w83781d'), other addresses: 0x48 0x49
> (...)
> Client found at address 0x2d
> (...)
> Probing for `Winbond W83782D'... Success!
> (confidence 8, driver `w83781d'), other addresses: 0x48 0x49
Wow. So it does actually find *two* W83782D chips, which share the same
subclient addresses. This is no good.
Can you please provide the output of the following commands:
i2cdump -y 0 0x29
i2cdump -y 0 0x2d
(I assume this is on i2c bus 0; if not, put the correct ID.)
> Probing for `Winbond W83697HF Super IO Sensors'
> Success... but not activated
And the Super-I/O is there. I suspect that the W83697F has the same ID,
so we cannot differenciate, but the W83697F has no hardware monitoring
logical device - which would explain why it is listed as 'not activated"
here.
So... the correct modprobe line for you would be:
modprobe w83781d force_subclient=0,0x29,0x4a,0x4b
Try it :)
--
Jean Delvare
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (3 preceding siblings ...)
2005-06-13 19:15 ` [lm-sensors] w83781d.o: Subclient 0 registration at address Jean Delvare
@ 2005-06-13 22:25 ` Yani Ioannou
2005-06-13 22:34 ` [lm-sensors] w83781d.o: Subclient 0 registration at address Jean Delvare
` (9 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Yani Ioannou @ 2005-06-13 22:25 UTC (permalink / raw)
To: lm-sensors
For what its worth I get the same problem on a new machine I just put
together (ironically enough so I could test ipmi_sensors on a more
modern BMC - using the Tyan SMDC add-on). The motherboard is a Tyan
2882-D (an updated 2882) and I get:
w83781d 1-0028: Duplicate addresses 0x48 for subclients.
when trying to use w83781d. sensors-detect says I should be able to
access the chip through the ISA bus too, but loading i2c-isa and
w83781d no chip seems to be detected. The motherboard has two smbus
interfaces, one an Smbus 2.0 interface through i2c_amd8111 and
i2c_amd756. Nothing seems to be using i2c_amd8111 though. An adm1027
is also detected and works fine.
Thanks,
Yani
On 6/13/05, Jean Delvare <khali@linux-fr.org> wrote:
> Hi Sukhdeep,
>
> > The Motherbowrd is from VIAPRO, it's similar to kt400.
>
> VIA Pro / KT400 is the name of the South Bridge. This doesn't tell me
> the motherboard itself is. Have you no idea? dmidecode [1] may help.
>
> [1] http://www.nongnu.org/dmidecode/
>
> > Client found at address 0x29
> > (...)
> > Probing for `Winbond W83782D'... Success!
> > (confidence 8, driver `w83781d'), other addresses: 0x48 0x49
> > (...)
> > Client found at address 0x2d
> > (...)
> > Probing for `Winbond W83782D'... Success!
> > (confidence 8, driver `w83781d'), other addresses: 0x48 0x49
>
> Wow. So it does actually find *two* W83782D chips, which share the same
> subclient addresses. This is no good.
>
> Can you please provide the output of the following commands:
> i2cdump -y 0 0x29
> i2cdump -y 0 0x2d
>
> (I assume this is on i2c bus 0; if not, put the correct ID.)
>
> > Probing for `Winbond W83697HF Super IO Sensors'
> > Success... but not activated
>
> And the Super-I/O is there. I suspect that the W83697F has the same ID,
> so we cannot differenciate, but the W83697F has no hardware monitoring
> logical device - which would explain why it is listed as 'not activated"
> here.
>
> So... the correct modprobe line for you would be:
>
> modprobe w83781d force_subclient=0,0x29,0x4a,0x4b
>
> Try it :)
>
> --
> Jean Delvare
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (4 preceding siblings ...)
2005-06-13 22:25 ` [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Yani Ioannou
@ 2005-06-13 22:34 ` Jean Delvare
2005-06-13 23:01 ` [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Yani Ioannou
` (8 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2005-06-13 22:34 UTC (permalink / raw)
To: lm-sensors
Hi Yani,
> For what its worth I get the same problem on a new machine I just put
> together (ironically enough so I could test ipmi_sensors on a more
> modern BMC - using the Tyan SMDC add-on). The motherboard is a Tyan
> 2882-D (an updated 2882) and I get:
>
> w83781d 1-0028: Duplicate addresses 0x48 for subclients.
Try:
modprobe w83781d force_subclients=1,0x28,0x4a,0x4b
And/or ask Tyan for a fixed BIOS.
Which chip is it exactly? Which address(es) is sensors-detect reporting
in the first place? Tyan have a long history of conflicting sucblient
addresses.
> when trying to use w83781d. sensors-detect says I should be able to
> access the chip through the ISA bus too, but loading i2c-isa and
> w83781d no chip seems to be detected.
You may try w83627hf instead of w83781d, as the former can auto-detect
the ISA address and the latter cannot.
--
Jean Delvare
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (5 preceding siblings ...)
2005-06-13 22:34 ` [lm-sensors] w83781d.o: Subclient 0 registration at address Jean Delvare
@ 2005-06-13 23:01 ` Yani Ioannou
2005-06-13 23:11 ` [lm-sensors] w83781d.o: Subclient 0 registration at address Jean Delvare
` (7 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Yani Ioannou @ 2005-06-13 23:01 UTC (permalink / raw)
To: lm-sensors
On 6/13/05, Jean Delvare <khali@linux-fr.org> wrote:
> Hi Yani,
>
> > For what its worth I get the same problem on a new machine I just put
> > together (ironically enough so I could test ipmi_sensors on a more
> > modern BMC - using the Tyan SMDC add-on). The motherboard is a Tyan
> > 2882-D (an updated 2882) and I get:
> >
> > w83781d 1-0028: Duplicate addresses 0x48 for subclients.
>
> Try:
> modprobe w83781d force_subclients=1,0x28,0x4a,0x4b
Same thing :-(
>
> And/or ask Tyan for a fixed BIOS.
>
> Which chip is it exactly? Which address(es) is sensors-detect reporting
> in the first place? Tyan have a long history of conflicting sucblient
> addresses.
It looks like its a W83627HF, here is the output of sensors-detect
(note I get the same thing if I remove the IPMI BMC daughterboard):
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):
Probing for PCI bus adapters...
Use driver `i2c-amd756' for device 00:07.3: AMD-8111 ACPI
Use driver `i2c-amd8111' for device 00:07.2: AMD-8111 SMBus 2.0
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-amd756' (say NO if built into your kernel)? (YES/no):
Module loaded succesfully.
Load `i2c-amd8111' (say NO if built into your kernel)? (YES/no):
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):
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: SMBus2 AMD8111 adapter at cc00
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Next adapter: SMBus AMD8111 adapter at 10e0
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x0c
Client found at address 0x10
Client found at address 0x28
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83627HF'... Success!
(confidence 7, driver `w83781d')
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `ITE IT8712F'... Failed!
Probing for `ITE IT8705F / SiS 950'... Failed!
Client found at address 0x2e
Probing for `Myson MTP008'... Failed!
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `National Semiconductor LM85 or LM96000'... Failed!
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... Success!
(confidence 8, driver `lm85')
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'... Failed!
Probing for `Analog Devices ADT7467'... Failed!
Probing for `National Semiconductor LM87'... Failed!
Probing for `National Semiconductor LM93'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Winbond W83L785TS-S'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1026'... Failed!
Probing for `Analog Devices ADM1025'... Failed!
Probing for `Analog Devices ADM1024'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `Analog Devices ADM1030'... Failed!
Probing for `Analog Devices ADM1031'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `Analog Devices ADM1028'... Failed!
Probing for `ITE IT8712F'... Failed!
Probing for `ITE IT8705F / SiS 950'... Failed!
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 0x54
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x55
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):
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... Success!
(confidence 8, driver `w83781d')
Alias of the chip on I2C bus `SMBus AMD8111 adapter at 10e0',
address 0x0028Probing 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... Success!
(confidence 4, driver `bmcsensors')
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):
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! (0x52)
Probing for `Winbond W83627HF Super IO Sensors'
Success... found at address 0x0290
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0x52)
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x52)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0x52)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0x52)
Probing for `Winbond W83L517D Super IO'
Failed! (0x52)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (0x5241)
Do you want to scan for secondary Super I/O sensors? (YES/no):
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 Super IO Sensors'
Failed! (skipping family)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83781d' (may not be inserted):
Misdetects:
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x28
ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627HF' (confidence: 7)
Driver `lm85' (should be inserted):
Detects correctly:
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x2e
Chip `Analog Devices ADM1027, ADT7460 or ADT7463' (confidence: 8)
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x51
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x54
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x55
Chip `SPD EEPROM' (confidence: 8)
Driver `bmcsensors' (should be inserted):
Detects correctly:
* ISA bus address 0x0ca0 (Busdriver `i2c-isa')
Chip `IPMI BMC KCS' (confidence: 4)
Driver `w83627hf' (should be inserted):
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)?
If you want to load the modules at startup, generate a config file
below and make sure lm_sensors gets started; e.g
$ rc-update add lm_sensors default.
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
#----end 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.
To load everything that is needed, execute the commands above...
#----cut here----
# I2C adapter drivers
modprobe i2c-amd756
modprobe i2c-isa
# You must also install and load the IPMI modules
modprobe i2c-ipmi
# I2C chip drivers
modprobe lm85
modprobe eeprom
# Warning: the required module bmcsensors is not currently installed
on your system.
# For status of 2.6 kernel ports see
http://secure.netroedge.com/~lm78/supported.html
# If driver is built-in to the kernel, or unavailable, comment out the
following line.
modprobe bmcsensors
modprobe w83627hf
# sleep 2 # optional
/usr/bin/sensors -s # recommended
> > when trying to use w83781d. sensors-detect says I should be able to
> > access the chip through the ISA bus too, but loading i2c-isa and
> > w83781d no chip seems to be detected.
>
> You may try w83627hf instead of w83781d, as the former can auto-detect
> the ISA address and the latter cannot.
Sorry, I meant to say w83627hf there.
Yani
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (6 preceding siblings ...)
2005-06-13 23:01 ` [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Yani Ioannou
@ 2005-06-13 23:11 ` Jean Delvare
2005-06-14 8:09 ` [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (6 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2005-06-13 23:11 UTC (permalink / raw)
To: lm-sensors
Hi Yani,
> It looks like its a W83627HF,
Yup.
> Client found at address 0x28
> (...)
> Probing for `Winbond W83627HF'... Success!
> (confidence 7, driver `w83781d')
The odd thing is that NO subclient address are then scanned. Weird.
Could mean that they are disabled, the w83627hf driver does that so it
wouldn't be that surprising if you loaded it and did not reboot since.
It's quite possible that the "force_subclients" option of the w83781d
driver can change the addresses but not reenable disabled subclients.
Maybe you could try sensors-detect again after a cold reboot and the
subclients will show. If you load w83781d with force_subclients before
ever loading w83627hf, it might work.
> > You may try w83627hf instead of w83781d, as the former can
> > auto-detect the ISA address and the latter cannot.
>
> Sorry, I meant to say w83627hf there.
2.6 kernel with CONFIG_PNPACPI? Check /proc/ioports, see if there's
something conflicting at 0x290-0x297.
Thanks,
--
Jean Delvare
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (7 preceding siblings ...)
2005-06-13 23:11 ` [lm-sensors] w83781d.o: Subclient 0 registration at address Jean Delvare
@ 2005-06-14 8:09 ` Sukhdeep Johar
2005-06-14 8:18 ` Sukhdeep Johar
` (5 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Sukhdeep Johar @ 2005-06-14 8:09 UTC (permalink / raw)
To: lm-sensors
Thanks Jean !
Our motherboard is a custom one (used for our(Symbol) wireless switches )
They are similar to the kt400 is what i know.
Here is the i2cdump :
WS5K #i2cdump -y 0 0x29
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
20: 71 5e ca bc c5 9d ca 1b ff 4c 2d 72 68 72 68 d8 q^??????.L-rhrh?
30: c4 c3 b0 d9 b2 31 15 3b 31 58 02 00 24 02 00 00 ?????1?;1X?.$?..
40: 01 00 10 00 00 00 00 56 29 02 32 44 41 95 00 a3 ?.?....V)?2DA?.?
50: ff ff 80 ff ff ff 00 00 30 70 ff ff 11 00 ff ff ..?.....0p..?...
60: 71 5e cb bc c4 9c ca 1b ff 4b 2e 72 68 72 68 d8 q^??????.K.rhrh?
70: c4 c3 b0 d9 b2 31 15 3b 31 58 02 00 24 02 00 00 ?????1?;1X?.$?..
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
a0: 71 5e cb bb c4 9c ca 1b ff 4c 2d 72 68 72 68 d8 q^??????.L-rhrh?
b0: c4 c3 b0 d9 b2 31 15 3b 31 58 02 00 24 02 00 00 ?????1?;1X?.$?..
c0: 01 00 10 00 00 00 00 56 29 02 32 44 41 95 00 a3 ?.?....V)?2DA?.?
d0: ff ff 80 ff ff ff 00 00 30 70 ff ff 11 00 ff ff ..?.....0p..?...
e0: 71 5e ca bc c4 9d ca 1b ff 4c 2d 72 68 72 68 d8 q^??????.L-rhrh?
f0: c4 c3 b0 d9 b2 31 15 3b 31 58 02 00 24 02 00 00 ?????1?;1X?.$?..
WS5K #i2cdump -y 0 0x2d
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
20: 53 00 00 bb 00 00 00 7f 2e 2d 2f 00 00 00 00 d8 S..?...?.-/....?
30: c4 c3 b0 d9 b2 31 15 3b 31 08 40 40 00 00 00 00 ?????1?;1?@@....
40: 01 20 00 00 00 00 00 5f 2d 03 01 44 41 95 00 a3 ? ....._-??DA?.?
50: ff ff 00 ff ff ff 00 00 30 70 ff ff 11 00 ff ff ........0p..?...
60: 53 00 00 bc 00 00 00 7f 2e 2d 2e 00 00 00 00 d8 S..?...?.-.....?
70: c4 c3 b0 d9 b2 31 15 3b 31 08 40 40 00 00 00 00 ?????1?;1?@@....
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
a0: 53 00 00 bb 00 00 00 7f 2e 2e 2e 00 00 00 00 d8 S..?...?.......?
b0: c4 c3 b0 d9 b2 31 15 3b 31 08 40 40 00 00 00 00 ?????1?;1?@@....
c0: 01 20 00 00 00 00 00 5f 2d 03 01 44 41 95 00 a3 ? ....._-??DA?.?
d0: ff ff 00 ff ff ff 00 00 30 70 ff ff 11 00 ff ff ........0p..?...
e0: 53 00 00 bb 00 00 00 7f 2f 2d 2e 00 00 00 00 d8 S..?...?/-.....?
f0: c4 c3 b0 d9 b2 31 15 3b 31 08 40 40 00 00 00 00 ?????1?;1?@@....
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The warning went after loading with :
#modprobe w83781d init=0 force_subclients=0,0x29,0x4a,0x4b
But, I now see that the sensors command gives _TWO_ results :
WS5K #sensors
w83782d-i2c-0-29
Adapter: SMBus Via Pro adapter at 0400
VCore 1: +1.81 V (min = +1.66 V, max = +1.82 V)
VCore 2: +1.50 V (min = +1.66 V, max = +1.82 V)
+3.3V: +3.23 V (min = +3.14 V, max = +3.46 V)
+5V: +5.06 V (min = +4.74 V, max = +5.24 V)
+12V: +11.97 V (min = +10.83 V, max = +13.19 V)
-12V: -2.01 V (min = -13.16 V, max = -10.90 V)
-5V: +2.43 V (min = -5.26 V, max = -4.76 V)
V5SB: +5.02 V (min = +4.74 V, max = +5.24 V)
VBaT: +2.13 V (min = +2.40 V, max = +3.60 V)
My fan: 0 RPM (min = -1 RPM, div = 2)
fan2: 9000 RPM (min = 18750 RPM, div = 2)
fan3: 14673 RPM (min = 337500 RPM, div = 2)
temp1: +28 C (high = +88 C, hyst = +2 C) sensor = thermistor
temp2: +70.5 C (high = +80 C, hyst = +75 C) sensor = thermistor
temp3: -48.0 C (high = +80 C, hyst = +75 C) sensor = thermistor
vid: +1.750 V (VRM Version 8.2)
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled
w83782d-i2c-0-2d
Adapter: SMBus Via Pro adapter at 0400
VCore 1: +1.33 V (min = +0.00 V, max = +4.08 V)
VCore 2: +0.00 V (min = +0.00 V, max = +4.08 V)
+3.3V: +0.00 V (min = +2.82 V, max = +3.79 V)
+5V: +5.02 V (min = +3.49 V, max = +0.00 V)
+12V: +0.00 V (min = +4.14 V, max = +0.00 V)
-12V: -14.91 V (min = -4.37 V, max = -14.91 V)
-5V: -7.71 V (min = -7.71 V, max = +2.24 V)
V5SB: +0.00 V (min = +0.22 V, max = +0.50 V)
VBaT: +0.00 V (min = +0.13 V, max = +0.00 V)
My fan: 14361 RPM (min = 10546 RPM, div = 2)
fan2: 14673 RPM (min = -1 RPM, div = 2)
fan3: 14673 RPM (min = -1 RPM, div = 2)
temp1: +127 C (high = +8 C, hyst = +64 C) sensor = thermistor
temp2: +79.5 C (high = +80 C, hyst = +75 C) sensor = thermistor
temp3: +63.0 C (high = +80 C, hyst = +75 C) sensor = thermistor
vid: +0.000 V (VRM Version 8.2)
alarms:
beep_enable:
Sound alarm disabled
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The first one is what I was seeing earlier. Only temp3 is now -49C
in place of 16C.
And if you see the first line of output - w83782d-i2c-0-29
I guess, it was actually being loaded at 0x29 only.
The second output seems quite vague.
I also see two directories created in the /proc -
WS5K #cat /proc/sys/dev/sensors/
chips w83782d-i2c-0-29 w83782d-i2c-0-2d
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Can you make out what's going wrong ?
regards,
Sukhdeep
On 6/13/05, Jean Delvare <khali@linux-fr.org> wrote:
> Hi Sukhdeep,
>
> > The Motherbowrd is from VIAPRO, it's similar to kt400.
>
> VIA Pro / KT400 is the name of the South Bridge. This doesn't tell me
> the motherboard itself is. Have you no idea? dmidecode [1] may help.
>
> [1] http://www.nongnu.org/dmidecode/
>
> > Client found at address 0x29
> > (...)
> > Probing for `Winbond W83782D'... Success!
> > (confidence 8, driver `w83781d'), other addresses: 0x48 0x49
> > (...)
> > Client found at address 0x2d
> > (...)
> > Probing for `Winbond W83782D'... Success!
> > (confidence 8, driver `w83781d'), other addresses: 0x48 0x49
>
> Wow. So it does actually find *two* W83782D chips, which share the same
> subclient addresses. This is no good.
>
> Can you please provide the output of the following commands:
> i2cdump -y 0 0x29
> i2cdump -y 0 0x2d
>
> (I assume this is on i2c bus 0; if not, put the correct ID.)
>
> > Probing for `Winbond W83697HF Super IO Sensors'
> > Success... but not activated
>
> And the Super-I/O is there. I suspect that the W83697F has the same ID,
> so we cannot differenciate, but the W83697F has no hardware monitoring
> logical device - which would explain why it is listed as 'not activated"
> here.
>
> So... the correct modprobe line for you would be:
>
> modprobe w83781d force_subclient=0,0x29,0x4a,0x4b
>
> Try it :)
>
> --
> Jean Delvare
>
--
Everybody has the right to be stupid..... But some abuse the privilege
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (8 preceding siblings ...)
2005-06-14 8:09 ` [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
@ 2005-06-14 8:18 ` Sukhdeep Johar
2005-06-14 8:53 ` Yani Ioannou
` (4 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Sukhdeep Johar @ 2005-06-14 8:18 UTC (permalink / raw)
To: lm-sensors
And here is the dmidecode output :
WS5K #./dmidecode
# dmidecode 1.8
SMBIOS 2.3 present.
DMI 2.3 present.
25 structures occupying 945 bytes.
DMI table at 0x000F0670.
Handle 0x0000
DMI type 0, 20 bytes.
BIOS Information Block
Vendor: American Megatrends Inc.
Version: 2.2
Release: 07/09/02
BIOS base: 0xF0000
ROM size: 256K
Capabilities:
Flags: 0x000000006FCBDE90
Handle 0x0001
DMI type 1, 25 bytes.
System Information Block
Vendor: American Megatrends Inc.
Product: Uknown
Version: 1.0
Serial Number: 1PCC5000RSWW0419S5450EC
Handle 0x0002
DMI type 2, 8 bytes.
Board Information Block
Vendor: USI
Product: PA-PR66T
Version: 2.0
Serial Number: SYMBOLWS-02-1.11
Handle 0x0003
DMI type 3, 17 bytes.
Chassis Information Block
Vendor: Uknown Chassis Manufacture
Chassis Type: Desktop
Version: Version 1.00
Serial Number: 123456890
Asset Tag: 0123ABC
Handle 0x0004
DMI type 4, 32 bytes.
Processor
Socket Designation: Socket-1
Processor Type: Central Processor
Processor Family:
Processor Manufacturer: Intel
Processor Version: Pentium III
Handle 0x0005
DMI type 7, 19 bytes.
Cache
Socket: Internal Cache
L1 Internal Cache: write-back
L1 Cache Size: 32K
L1 Cache Maximum: 1024K
L1 Cache Type: Synchronous
Handle 0x0006
DMI type 7, 19 bytes.
Cache
Socket: Internal Cache
L2 Internal Cache: write-back
L2 Cache Size: 256K
L2 Cache Maximum: 1024K
L2 Cache Type: Synchronous
Handle 0x0007
DMI type 5, 24 bytes.
Memory Controller
Handle 0x0008
DMI type 6, 12 bytes.
Memory Bank
Socket: DIMM1
Banks: 1 0
Type:
Installed Size: 128Mbyte
Enabled Size: 128Mbyte
Handle 0x0009
DMI type 6, 12 bytes.
Memory Bank
Socket: DIMM2
Banks: 3 2
Type: UNKNOWN
Installed Size: Not Installed
Enabled Size: Not Installed
Handle 0x000A
DMI type 6, 12 bytes.
Memory Bank
Socket: DIMM3
Banks: 5 4
Type: UNKNOWN
Installed Size: Not Installed
Enabled Size: Not Installed
Handle 0x000B
DMI type 6, 12 bytes.
Memory Bank
Socket: DIMM4
Banks: 7 6
Type: UNKNOWN
Installed Size: Not Installed
Enabled Size: Not Installed
Handle 0x000C
DMI type 9, 13 bytes.
Card Slot
Slot: PCI1
Type: 32bit Long PCI
Status: Available.
Slot Features: 3.3v Shared
Handle 0x000D
DMI type 9, 13 bytes.
Card Slot
Slot: PCI2
Type: 32bit Long PCI
Status: Available.
Slot Features: 3.3v Shared
Handle 0x000E
DMI type 9, 13 bytes.
Card Slot
Slot: PCI3
Type: 32bit Long PCI
Slot Features: 3.3v Shared
Handle 0x000F
DMI type 9, 13 bytes.
Card Slot
Slot: PCI4
Type: 32bit Long PCI
Slot Features: 3.3v Shared
Handle 0x0010
DMI type 9, 13 bytes.
Card Slot
Slot: PCI5
Type: 32bit Long PCI
Slot Features: 3.3v Shared
Handle 0x0011
DMI type 9, 13 bytes.
Card Slot
Slot: ISA1
Type: 16bit Long ISA
Slot Features: 3.3v Shared
Handle 0x0012
DMI type 9, 13 bytes.
Card Slot
Slot: ISA2
Type: 16bit Long ISA
Slot Features: 3.3v Shared
Handle 0x0013
DMI type 11, 5 bytes.
OEM Data
SMBIOS Support from AMI
Tested by James
Handle 0x0014
DMI type 8, 9 bytes.
Port Connector
Internal Designator: USB
Internal Connector Type: Mini Centronics
External Designator: Def
External Connector Type: DB-25 pin male
Port Type: SSA SCSI
Handle 0x0015
DMI type 12, 5 bytes.
Configuration Information
System Management BIOS from Atlanta
SMBIOS from AMI
Handle 0x0016
DMI type 13, 22 bytes.
BIOS Language Information
Installable Languages: 4
English
Traditional Chinese
Simplified Chinese
Japanese
Currently Installed Language: English
Handle 0x0017
DMI type 15, 27 bytes.
Event Log
Log Area: 4096 bytes.
Log Header At: 0.
Log Data At: 0.
Log Type: 4.
Log Valid: Yes.
Handle 0x0018
DMI type 127, 4 bytes.
End-of-Table
PNP 1.0 present.
Event Notification: Not Supported
Real Mode Code Address: F000:6493
Real Mode Data Address: F000:0000
Protected Mode Code Address: 0x000F64BB
Protected Mode Data Address: 0x000F0000
PCI Interrupt Routing 1.0 present.
Table Size: 160 bytes
Router ID: 00:11.0
Exclusive IRQs: None
Compatible Router: 1106:3074
BIOS32 Service Directory present.
Calling Interface Address: 0x000FDB30
-sukhdeep
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (9 preceding siblings ...)
2005-06-14 8:18 ` Sukhdeep Johar
@ 2005-06-14 8:53 ` Yani Ioannou
2005-06-14 10:20 ` Jean Delvare
` (3 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Yani Ioannou @ 2005-06-14 8:53 UTC (permalink / raw)
To: lm-sensors
> The odd thing is that NO subclient address are then scanned. Weird.
> Could mean that they are disabled, the w83627hf driver does that so it
> wouldn't be that surprising if you loaded it and did not reboot since.
> It's quite possible that the "force_subclients" option of the w83781d
> driver can change the addresses but not reenable disabled subclients.
>
> Maybe you could try sensors-detect again after a cold reboot and the
> subclients will show. If you load w83781d with force_subclients before
> ever loading w83627hf, it might work.
>
Ok, here it is after a cold reboot, looks a bit different:
-----------------------------------
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):
Probing for PCI bus adapters...
Use driver `i2c-amd756' for device 00:07.3: AMD-8111 ACPI
Use driver `i2c-amd8111' for device 00:07.2: AMD-8111 SMBus 2.0
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-amd756' (say NO if built into your kernel)? (YES/no):
Module loaded succesfully.
Load `i2c-amd8111' (say NO if built into your kernel)? (YES/no):
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):
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: SMBus2 AMD8111 adapter at cc00
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Next adapter: SMBus AMD8111 adapter at 10e0
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x10
Client found at address 0x28
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83627HF'... Success!
(confidence 7, driver `w83781d')
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `ITE IT8712F'... Failed!
Probing for `ITE IT8705F / SiS 950'... Failed!
Client found at address 0x2e
Probing for `Myson MTP008'... Failed!
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `National Semiconductor LM85 or LM96000'... Failed!
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... Success!
(confidence 8, driver `lm85')
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'... Failed!
Probing for `Analog Devices ADT7467'... Failed!
Probing for `National Semiconductor LM87'... Failed!
Probing for `National Semiconductor LM93'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Winbond W83L785TS-S'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1026'... Failed!
Probing for `Analog Devices ADM1025'... Failed!
Probing for `Analog Devices ADM1024'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `Analog Devices ADM1030'... Failed!
Probing for `Analog Devices ADM1031'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `Analog Devices ADM1028'... Failed!
Probing for `ITE IT8712F'... Failed!
Probing for `ITE IT8705F / SiS 950'... Failed!
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 0x54
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x55
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):
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... Success!
(confidence 4, driver `bmcsensors')
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):
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! (0x52)
Probing for `Winbond W83627HF Super IO Sensors'
Success... found at address 0x0290
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0x52)
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x52)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0x52)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0x52)
Probing for `Winbond W83L517D Super IO'
Failed! (0x52)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (0x5241)
Do you want to scan for secondary Super I/O sensors? (YES/no):
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 Super IO Sensors'
Failed! (skipping family)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83781d' (should be inserted):
Detects correctly:
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x28
Chip `Winbond W83627HF' (confidence: 7)
Driver `lm85' (should be inserted):
Detects correctly:
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x2e
Chip `Analog Devices ADM1027, ADT7460 or ADT7463' (confidence: 8)
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x51
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x54
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus AMD8111 adapter at 10e0'
Busdriver `i2c-amd756', I2C address 0x55
Chip `SPD EEPROM' (confidence: 8)
Driver `bmcsensors' (should be inserted):
Detects correctly:
* ISA bus address 0x0ca0 (Busdriver `i2c-isa')
Chip `IPMI BMC KCS' (confidence: 4)
Driver `w83627hf' (should be inserted):
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)?
If you want to load the modules at startup, generate a config file
below and make sure lm_sensors gets started; e.g
$ rc-update add lm_sensors default.
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
#----end 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.
To load everything that is needed, execute the commands above...
#----cut here----
# I2C adapter drivers
modprobe i2c-amd756
modprobe i2c-isa
# You must also install and load the IPMI modules
modprobe i2c-ipmi
# I2C chip drivers
modprobe w83781d
modprobe lm85
modprobe eeprom
# Warning: the required module bmcsensors is not currently installed
on your system.
# For status of 2.6 kernel ports see
http://secure.netroedge.com/~lm78/supported.html
# If driver is built-in to the kernel, or unavailable, comment out the
following line.
modprobe bmcsensors
modprobe w83627hf
# sleep 2 # optional
/usr/bin/sensors -s # recommended
-----------------------------------
> 2.6 kernel with CONFIG_PNPACPI? Check /proc/ioports, see if there's
> something conflicting at 0x290-0x297.
Running 2.6.11.12 with CONFIG_PNPACPI=y and in /proc/ioports:
-----------------------------------
...
0295-0296 : pnp 00:07
..
-----------------------------------
modprobe w83781d force_subclients=1,0x28,0x4a,0x4b seems to fail with
the same message again even though the w83627hf driver hasn't been
loaded.
Thanks,
Yani
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (10 preceding siblings ...)
2005-06-14 8:53 ` Yani Ioannou
@ 2005-06-14 10:20 ` Jean Delvare
2005-06-14 15:18 ` Jean Delvare
` (2 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2005-06-14 10:20 UTC (permalink / raw)
To: lm-sensors
Hi Yani,
> Ok, here it is after a cold reboot, looks a bit different:
Looks very similar to me, except that the W83627HF ISA detection fails,
right? Not really surprising, as part of this detection is experimental
and known to be broken for recent Super-I/O chips.
> > 2.6 kernel with CONFIG_PNPACPI? Check /proc/ioports, see if there's
> > something conflicting at 0x290-0x297.
> Running 2.6.11.12 with CONFIG_PNPACPI=y and in /proc/ioports:
> -----------------------------------
> ...
> 0295-0296 : pnp 00:07
> ..
> -----------------------------------
Known problem then. The ISA interface of the W83627HF won't work until
you disable PNPACPI.
http://bugzilla.kernel.org/show_bug.cgi?id@14
I think that it means that your ACPI tables are broken and Tyan should
fix them (they advertise 0x295-0x296 as the W83627HF hardware monitoring
address range, instead of 0x290-0x297).
> modprobe w83781d force_subclients=1,0x28,0x4a,0x4b seems to fail with
> the same message again even though the w83627hf driver hasn't been
> loaded.
I took a look at the w83781d driver and it doesn't play nicely when
subclients are disabled. However, using force_subclients should not only
change the addresses but also reenable the subclients, so I'm surprised
it didn't work.
Could you please provide a dump of your chip? The register I am
interested in is 0x4A. You may try to write 0x01 to it and see if the
subclients show and it it helps the w83781d driver loading.
Thanks,
--
Jean Delvare
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (11 preceding siblings ...)
2005-06-14 10:20 ` Jean Delvare
@ 2005-06-14 15:18 ` Jean Delvare
2005-06-14 17:13 ` Sukhdeep Johar
2005-06-14 20:46 ` [lm-sensors] w83781d.o: Subclient 0 registration at address Jean Delvare
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2005-06-14 15:18 UTC (permalink / raw)
To: lm-sensors
Hi Sukhdeep,
> Our motherboard is a custom one (used for our(Symbol) wireless switches )
> They are similar to the kt400 is what i know.
>
> Here is the i2cdump :
This looks like two distinct Winbond W83782D chips to me, one at 0x29 and
one at 0x2d.
> The warning went after loading with :
> #modprobe w83781d init=0 force_subclients=0,0x29,0x4a,0x4b
Yes, the two chips previously had their subclients colliding (BIOS
didn't intialize them properly). The force_sublients option let you fix
that.
> But, I now see that the sensors command gives _TWO_ results :
Well, there are two chips, what did you expect?
> The second output seems quite vague.
Looks like the voltage inputs are not wired. Fans and temperatures may be
though.
> I also see two directories created in the /proc -
>
> WS5K #cat /proc/sys/dev/sensors/
> chips w83782d-i2c-0-29 w83782d-i2c-0-2d
One directory per chip. What's the problem?
> Can you make out what's going wrong ?
Nothing is going wrong (anymore). Once the subclient addresses are fixed
not to collide, you get two working chips. You said it was a custom
board, if you are the one building it, you *should* know which chips are
on it and how they are wired. Don't expect us to tell you, that's not
something we can guess.
As for strange temperature values, you may try changing the sensor types
(/proc/sys/dev/sensors/w83782d-i2c-0-*/sensor* or /etc/sensors.conf).
Maybe your board uses thermal diodes rather than thermistors.
--
Jean Delvare
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (12 preceding siblings ...)
2005-06-14 15:18 ` Jean Delvare
@ 2005-06-14 17:13 ` Sukhdeep Johar
2005-06-14 20:46 ` [lm-sensors] w83781d.o: Subclient 0 registration at address Jean Delvare
14 siblings, 0 replies; 16+ messages in thread
From: Sukhdeep Johar @ 2005-06-14 17:13 UTC (permalink / raw)
To: lm-sensors
>> Well, there are two chips, what did you expect?
Hmmm..
The problem is that I can see only one W83697F chip on the
motherboard. I am puzzled where the two W83782D's are.
I booted the device using Win 2K HDD and ran SpeedFan over it. And the
results were the same.
At least the second chip is reading the fan speeds correctly. There
are 4 external fans, and 2nd chip is reading out the fan speeds for
the 3 of them.
>> Don't expect us to tell you, that's not
>> something we can guess.
Right. I guess I need to check with the HW gs.
Thanks a lot for helping out on this Jean. Things are in a better shape now.
And one more question ... Is it possible to configure the fan1,
fan2... settings in sensors.conf for the two chips separately ?
regards,
Sukhdeep
^ permalink raw reply [flat|nested] 16+ messages in thread* [lm-sensors] w83781d.o: Subclient 0 registration at address
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
` (13 preceding siblings ...)
2005-06-14 17:13 ` Sukhdeep Johar
@ 2005-06-14 20:46 ` Jean Delvare
14 siblings, 0 replies; 16+ messages in thread
From: Jean Delvare @ 2005-06-14 20:46 UTC (permalink / raw)
To: lm-sensors
Hi Sukhdeep,
> I booted the device using Win 2K HDD and ran SpeedFan over it. And the
> results were the same.
> At least the second chip is reading the fan speeds correctly. There
> are 4 external fans, and 2nd chip is reading out the fan speeds for
> the 3 of them.
You may need to change the clock dividers to get proper reading.
> And one more question ... Is it possible to configure the fan1,
> fan2... settings in sensors.conf for the two chips separately ?
It is under Linux 2.4, but unfortunately no more under Linux 2.6. Just
create sections with the full chip name:
chip "w83782d-i2c-0-29"
label fan1 "Foo Fan"
(...)
chip "w83782d-i2c-0-2d"
label fan1 "Bar Fan"
(...)
--
Jean Delvare
^ permalink raw reply [flat|nested] 16+ messages in thread