All of lore.kernel.org
 help / color / mirror / Atom feed
* [lm-sensors] Zotac ION ITX-G Synergy Edition
@ 2011-09-23 11:28 Josu Lazkano
  2011-09-23 15:53 ` Guenter Roeck
                   ` (8 more replies)
  0 siblings, 9 replies; 10+ messages in thread
From: Josu Lazkano @ 2011-09-23 11:28 UTC (permalink / raw)
  To: lm-sensors

Hello all, this is my first post on the list. I am searching for some
help to check my board sensors. I have a ZOTAC ION ITX-G Synergy
Edition board with Debian Squeeze (2.6.32), it has MCP79 and it is
supported by lm-sensors.

I have some problems with my board voltage and I want to check all
sensors available. When I execute "sensors" this is the output:

# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +27.0°C  (crit = +90.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +29.0°C  (crit = +90.0°C)

This is just CPU temperature. Is it possible to get more info about my board?

I read some forums and I found this interesting things:

# modprobe i2c-dev
# modprobe i2c-nforce2
# echo "10de 0aa2" > /sys/bus/pci/drivers/nForce2_smbus/new_id
# i2cdetect -l
i2c-0	smbus     	SMBus nForce2 adapter at 4d00   	SMBus adapter
i2c-1	i2c       	cx23885[0]                      	I2C adapter
i2c-2	i2c       	cx23885[0]                      	I2C adapter
i2c-3	i2c       	cx23885[0]                      	I2C adapter
i2c-4	i2c       	NVIDIA i2c adapter 0 at 3:00.0  	I2C adapter
i2c-5	i2c       	NVIDIA i2c adapter 2 at 3:00.0  	I2C adapter
i2c-6	i2c       	NVIDIA i2c adapter 3 at 3:00.0  	I2C adapter

I don't know what I am doing with the echo command, but it looks like
it found some i2c devices.

I will appreciate any help on this, I read lots of webs but I don't
understand kernel/module compiling.

Thanks and best regards.

-- 
Josu Lazkano

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

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: [lm-sensors] Zotac ION ITX-G Synergy Edition
  2011-09-23 11:28 [lm-sensors] Zotac ION ITX-G Synergy Edition Josu Lazkano
@ 2011-09-23 15:53 ` Guenter Roeck
  2011-09-23 15:57 ` Josu Lazkano
                   ` (7 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: Guenter Roeck @ 2011-09-23 15:53 UTC (permalink / raw)
  To: lm-sensors

On Fri, 2011-09-23 at 07:28 -0400, Josu Lazkano wrote:
> Hello all, this is my first post on the list. I am searching for some
> help to check my board sensors. I have a ZOTAC ION ITX-G Synergy
> Edition board with Debian Squeeze (2.6.32), it has MCP79 and it is
> supported by lm-sensors.
> 
> I have some problems with my board voltage and I want to check all
> sensors available. When I execute "sensors" this is the output:
> 
> # sensors
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +27.0째C  (crit = +90.0째C)
> 
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +29.0째C  (crit = +90.0째C)
> 
> This is just CPU temperature. Is it possible to get more info about my board?
> 
> I read some forums and I found this interesting things:
> 
> # modprobe i2c-dev
> # modprobe i2c-nforce2
> # echo "10de 0aa2" > /sys/bus/pci/drivers/nForce2_smbus/new_id
> # i2cdetect -l
> i2c-0	smbus     	SMBus nForce2 adapter at 4d00   	SMBus adapter
> i2c-1	i2c       	cx23885[0]                      	I2C adapter
> i2c-2	i2c       	cx23885[0]                      	I2C adapter
> i2c-3	i2c       	cx23885[0]                      	I2C adapter
> i2c-4	i2c       	NVIDIA i2c adapter 0 at 3:00.0  	I2C adapter
> i2c-5	i2c       	NVIDIA i2c adapter 2 at 3:00.0  	I2C adapter
> i2c-6	i2c       	NVIDIA i2c adapter 3 at 3:00.0  	I2C adapter
> 
> I don't know what I am doing with the echo command, but it looks like
> it found some i2c devices.
> 
> I will appreciate any help on this, I read lots of webs but I don't
> understand kernel/module compiling.
> 
Did you try to run sensors-detect ?

Guenter



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

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: [lm-sensors] Zotac ION ITX-G Synergy Edition
  2011-09-23 11:28 [lm-sensors] Zotac ION ITX-G Synergy Edition Josu Lazkano
  2011-09-23 15:53 ` Guenter Roeck
@ 2011-09-23 15:57 ` Josu Lazkano
  2011-09-23 16:17 ` Guenter Roeck
                   ` (6 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: Josu Lazkano @ 2011-09-23 15:57 UTC (permalink / raw)
  To: lm-sensors

2011/9/23 Guenter Roeck <guenter.roeck@ericsson.com>:
> On Fri, 2011-09-23 at 07:28 -0400, Josu Lazkano wrote:
>> Hello all, this is my first post on the list. I am searching for some
>> help to check my board sensors. I have a ZOTAC ION ITX-G Synergy
>> Edition board with Debian Squeeze (2.6.32), it has MCP79 and it is
>> supported by lm-sensors.
>>
>> I have some problems with my board voltage and I want to check all
>> sensors available. When I execute "sensors" this is the output:
>>
>> # sensors
>> coretemp-isa-0000
>> Adapter: ISA adapter
>> Core 0:      +27.0°C  (crit = +90.0°C)
>>
>> coretemp-isa-0001
>> Adapter: ISA adapter
>> Core 1:      +29.0°C  (crit = +90.0°C)
>>
>> This is just CPU temperature. Is it possible to get more info about my board?
>>
>> I read some forums and I found this interesting things:
>>
>> # modprobe i2c-dev
>> # modprobe i2c-nforce2
>> # echo "10de 0aa2" > /sys/bus/pci/drivers/nForce2_smbus/new_id
>> # i2cdetect -l
>> i2c-0 smbus           SMBus nForce2 adapter at 4d00           SMBus adapter
>> i2c-1 i2c             cx23885[0]                              I2C adapter
>> i2c-2 i2c             cx23885[0]                              I2C adapter
>> i2c-3 i2c             cx23885[0]                              I2C adapter
>> i2c-4 i2c             NVIDIA i2c adapter 0 at 3:00.0          I2C adapter
>> i2c-5 i2c             NVIDIA i2c adapter 2 at 3:00.0          I2C adapter
>> i2c-6 i2c             NVIDIA i2c adapter 3 at 3:00.0          I2C adapter
>>
>> I don't know what I am doing with the echo command, but it looks like
>> it found some i2c devices.
>>
>> I will appreciate any help on this, I read lots of webs but I don't
>> understand kernel/module compiling.
>>
> Did you try to run sensors-detect ?
>
> Guenter
>
>
>

Thanks for the reply, yes, I run it:

# sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: To Be Filled By O.E.M. To Be Filled By O.E.M.
# Board: To be filled by O.E.M. To be filled by O.E.M.

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.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
Intel Core family thermal sensor...                         No
Intel Atom thermal sensor...                                Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
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

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are 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 LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-nforce2' for device 0000:00:03.2: nVidia Corporation
nForce SMBus (MCP79)

Next adapter: SMBus nForce2 adapter at 4d00 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x4c
Probing for `National Semiconductor LM75'...                No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `Analog Devices ADT7466'...                     No
Probing for `Andigilog aSC7511'...                          No
Probing for `Dallas Semiconductor DS1621/DS1631'...         No
Probing for `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `Maxim MAX1668'...                              No
Probing for `Maxim MAX1805'...                              No
Probing for `Maxim MAX1989'...                              No
Probing for `Maxim MAX6655/MAX6656'...                      No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1618'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `National Semiconductor LM90'...                No
Probing for `National Semiconductor LM89/LM99'...           No
Probing for `National Semiconductor LM86'...                No
Probing for `Analog Devices ADM1032'...                     No
Probing for `Maxim MAX6654/MAX6690'...                      No
Probing for `Maxim MAX6657/MAX6658/MAX6659'...              No
Probing for `Maxim MAX6648/MAX6649/MAX6692'...              No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `Winbond W83L771W/G'...                         No
Probing for `Winbond W83L771AWG/ASG'...                     Success!
    (confidence 6, driver `lm90')
Probing for `Texas Instruments TMP401'...                   No
Probing for `Texas Instruments TMP411'...                   No
Probing for `Texas Instruments TMP421'...                   No
Probing for `Texas Instruments TMP422'...                   No
Probing for `Texas Instruments TMP423'...                   No
Probing for `Texas Instruments AMC6821'...                  No
Probing for `National Semiconductor LM63'...                No
Probing for `Fintek F75363SG'...                            No
Probing for `National Semiconductor LM73'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `Analog Devices ADT7461'...                     No
Probing for `Analog Devices ADT7481'...                     No
Probing for `Fintek F75383S/M'...                           No
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
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No

Next adapter: cx23885[0] (i2c-1)
Do you want to scan it? (yes/NO/selectively):

Next adapter: cx23885[0] (i2c-2)
Do you want to scan it? (yes/NO/selectively):

Next adapter: cx23885[0] (i2c-3)
Do you want to scan it? (yes/NO/selectively):

Next adapter: NVIDIA i2c adapter 0 at 3:00.0 (i2c-4)
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA i2c adapter 2 at 3:00.0 (i2c-5)
Do you want to scan it? (YES/no/selectively):

Next adapter: NVIDIA i2c adapter 3 at 3:00.0 (i2c-6)
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)

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

Driver `coretemp':
  * Chip `Intel Atom thermal sensor' (confidence: 9)

Driver `lm90':
  * Bus `SMBus nForce2 adapter at 4d00'
    Busdriver `i2c_nforce2', I2C address 0x4c
    Chip `Winbond W83L771AWG/ASG' (confidence: 6)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
lm90
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/module-init-tools start'
to load them.

# /etc/init.d/module-init-tools
Loading kernel modules...done.

But it just is showing the CPU temperature.

Thanks and best regards.

-- 
Josu Lazkano

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

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: [lm-sensors] Zotac ION ITX-G Synergy Edition
  2011-09-23 11:28 [lm-sensors] Zotac ION ITX-G Synergy Edition Josu Lazkano
  2011-09-23 15:53 ` Guenter Roeck
  2011-09-23 15:57 ` Josu Lazkano
@ 2011-09-23 16:17 ` Guenter Roeck
  2011-09-25 16:27 ` Josu Lazkano
                   ` (5 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: Guenter Roeck @ 2011-09-23 16:17 UTC (permalink / raw)
  To: lm-sensors

On Fri, 2011-09-23 at 11:57 -0400, Josu Lazkano wrote:
> 2011/9/23 Guenter Roeck <guenter.roeck@ericsson.com>:
> > On Fri, 2011-09-23 at 07:28 -0400, Josu Lazkano wrote:
> >> Hello all, this is my first post on the list. I am searching for some
> >> help to check my board sensors. I have a ZOTAC ION ITX-G Synergy
> >> Edition board with Debian Squeeze (2.6.32), it has MCP79 and it is
> >> supported by lm-sensors.
> >>
> >> I have some problems with my board voltage and I want to check all
> >> sensors available. When I execute "sensors" this is the output:
> >>
> >> # sensors
> >> coretemp-isa-0000
> >> Adapter: ISA adapter
> >> Core 0:      +27.0째C  (crit = +90.0째C)
> >>
> >> coretemp-isa-0001
> >> Adapter: ISA adapter
> >> Core 1:      +29.0째C  (crit = +90.0째C)
> >>
> >> This is just CPU temperature. Is it possible to get more info about my board?
> >>
> >> I read some forums and I found this interesting things:
> >>
> >> # modprobe i2c-dev
> >> # modprobe i2c-nforce2
> >> # echo "10de 0aa2" > /sys/bus/pci/drivers/nForce2_smbus/new_id
> >> # i2cdetect -l
> >> i2c-0 smbus           SMBus nForce2 adapter at 4d00           SMBus adapter
> >> i2c-1 i2c             cx23885[0]                              I2C adapter
> >> i2c-2 i2c             cx23885[0]                              I2C adapter
> >> i2c-3 i2c             cx23885[0]                              I2C adapter
> >> i2c-4 i2c             NVIDIA i2c adapter 0 at 3:00.0          I2C adapter
> >> i2c-5 i2c             NVIDIA i2c adapter 2 at 3:00.0          I2C adapter
> >> i2c-6 i2c             NVIDIA i2c adapter 3 at 3:00.0          I2C adapter
> >>
> >> I don't know what I am doing with the echo command, but it looks like
> >> it found some i2c devices.
> >>
> >> I will appreciate any help on this, I read lots of webs but I don't
> >> understand kernel/module compiling.
> >>
> > Did you try to run sensors-detect ?
> >
> > Guenter
> >
> >
> >
> 
> Thanks for the reply, yes, I run it:
> 
> # sensors-detect
> # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
> # System: To Be Filled By O.E.M. To Be Filled By O.E.M.
> # Board: To be filled by O.E.M. To be filled by O.E.M.
> 
> 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.
> 
> Some south bridges, CPUs or memory controllers contain embedded sensors.
> Do you want to scan for them? This is totally safe. (YES/no):
> Silicon Integrated Systems SIS5595...                       No
> VIA VT82C686 Integrated Sensors...                          No
> VIA VT8231 Integrated Sensors...                            No
> AMD K8 thermal sensors...                                   No
> AMD Family 10h thermal sensors...                           No
> AMD Family 11h thermal sensors...                           No
> Intel Core family thermal sensor...                         No
> Intel Atom thermal sensor...                                Success!
>     (driver `coretemp')
> Intel AMB FB-DIMM thermal sensor...                         No
> VIA C7 thermal sensor...                                    No
> VIA Nano thermal sensor...                                  No
> 
> 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):
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor'...                   No
> Trying family `SMSC'...                                     No
> Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
> Trying family `ITE'...                                      No
> 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
> 
> Some systems (mainly servers) implement IPMI, a set of common interfaces
> through which system health data may be retrieved, amongst other things.
> We first try to get the information from SMBIOS. If we don't find it
> there, we have to read from arbitrary I/O ports to probe for such
> interfaces. This is normally safe. Do you want to scan for IPMI
> interfaces? (YES/no):
> Probing for `IPMI BMC KCS' at 0xca0...                      No
> Probing for `IPMI BMC SMIC' at 0xca8...                     No
> 
> Some hardware monitoring chips are 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 LM79' at 0x290...       No
> Probing for `Winbond W83781D' at 0x290...                   No
> Probing for `Winbond W83782D' at 0x290...                   No
> 
> Lastly, we can probe the I2C/SMBus adapters for connected hardware
> monitoring devices. This is the most risky part, and while it works
> reasonably well on most systems, it has been reported to cause trouble
> on some systems.
> Do you want to probe the I2C/SMBus adapters now? (YES/no):
> Using driver `i2c-nforce2' for device 0000:00:03.2: nVidia Corporation
> nForce SMBus (MCP79)
> 
> Next adapter: SMBus nForce2 adapter at 4d00 (i2c-0)
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x4c
> Probing for `National Semiconductor LM75'...                No
> Probing for `Dallas Semiconductor DS75'...                  No
> Probing for `Analog Devices ADT7466'...                     No
> Probing for `Andigilog aSC7511'...                          No
> Probing for `Dallas Semiconductor DS1621/DS1631'...         No
> Probing for `Analog Devices ADM1021'...                     No
> Probing for `Analog Devices ADM1021A/ADM1023'...            No
> Probing for `Maxim MAX1617'...                              No
> Probing for `Maxim MAX1617A'...                             No
> Probing for `Maxim MAX1668'...                              No
> Probing for `Maxim MAX1805'...                              No
> Probing for `Maxim MAX1989'...                              No
> Probing for `Maxim MAX6655/MAX6656'...                      No
> Probing for `TI THMC10'...                                  No
> Probing for `National Semiconductor LM84'...                No
> Probing for `Genesys Logic GL523SM'...                      No
> Probing for `Onsemi MC1066'...                              No
> Probing for `Maxim MAX1618'...                              No
> Probing for `Maxim MAX1619'...                              No
> Probing for `National Semiconductor LM82/LM83'...           No
> Probing for `National Semiconductor LM90'...                No
> Probing for `National Semiconductor LM89/LM99'...           No
> Probing for `National Semiconductor LM86'...                No
> Probing for `Analog Devices ADM1032'...                     No
> Probing for `Maxim MAX6654/MAX6690'...                      No
> Probing for `Maxim MAX6657/MAX6658/MAX6659'...              No
> Probing for `Maxim MAX6648/MAX6649/MAX6692'...              No
> Probing for `Maxim MAX6680/MAX6681'...                      No
> Probing for `Winbond W83L771W/G'...                         No
> Probing for `Winbond W83L771AWG/ASG'...                     Success!
>     (confidence 6, driver `lm90')
> Probing for `Texas Instruments TMP401'...                   No
> Probing for `Texas Instruments TMP411'...                   No
> Probing for `Texas Instruments TMP421'...                   No
> Probing for `Texas Instruments TMP422'...                   No
> Probing for `Texas Instruments TMP423'...                   No
> Probing for `Texas Instruments AMC6821'...                  No
> Probing for `National Semiconductor LM63'...                No
> Probing for `Fintek F75363SG'...                            No
> Probing for `National Semiconductor LM73'...                No
> Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
> Probing for `Analog Devices ADT7461'...                     No
> Probing for `Analog Devices ADT7481'...                     No
> Probing for `Fintek F75383S/M'...                           No
> 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
> Client found at address 0x51
> Probing for `Analog Devices ADM1033'...                     No
> Probing for `Analog Devices ADM1034'...                     No
> Probing for `SPD EEPROM'...                                 No
> Client found at address 0x52
> Probing for `Analog Devices ADM1033'...                     No
> Probing for `Analog Devices ADM1034'...                     No
> Probing for `SPD EEPROM'...                                 No
> Client found at address 0x53
> Probing for `Analog Devices ADM1033'...                     No
> Probing for `Analog Devices ADM1034'...                     No
> Probing for `SPD EEPROM'...                                 No
> 
> Next adapter: cx23885[0] (i2c-1)
> Do you want to scan it? (yes/NO/selectively):
> 
> Next adapter: cx23885[0] (i2c-2)
> Do you want to scan it? (yes/NO/selectively):
> 
> Next adapter: cx23885[0] (i2c-3)
> Do you want to scan it? (yes/NO/selectively):
> 
> Next adapter: NVIDIA i2c adapter 0 at 3:00.0 (i2c-4)
> Do you want to scan it? (YES/no/selectively):
> 
> Next adapter: NVIDIA i2c adapter 2 at 3:00.0 (i2c-5)
> Do you want to scan it? (YES/no/selectively):
> 
> Next adapter: NVIDIA i2c adapter 3 at 3:00.0 (i2c-6)
> 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)
> 
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
> 
> Driver `coretemp':
>   * Chip `Intel Atom thermal sensor' (confidence: 9)
> 
> Driver `lm90':
>   * Bus `SMBus nForce2 adapter at 4d00'
>     Busdriver `i2c_nforce2', I2C address 0x4c
>     Chip `Winbond W83L771AWG/ASG' (confidence: 6)
> 
> To load everything that is needed, add this to /etc/modules:
> #----cut here----
> # Chip drivers
> coretemp
> lm90
> #----cut here----
> If you have some drivers built into your kernel, the list above will
> contain too many modules. Skip the appropriate ones!
> 
> Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
> Successful!
> 
> Monitoring programs won't work until the needed modules are
> loaded. You may want to run '/etc/init.d/module-init-tools start'
> to load them.
> 
> # /etc/init.d/module-init-tools
> Loading kernel modules...done.
> 
Are you sure you loaded the lm90 driver ? If yes, your version of the
driver is probably too old. Support for W83L771AWG was added to it in
October 2010. You might have to get a new driver from a recent kernel
version and compile and install it manually.

Guenter



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

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: [lm-sensors] Zotac ION ITX-G Synergy Edition
  2011-09-23 11:28 [lm-sensors] Zotac ION ITX-G Synergy Edition Josu Lazkano
                   ` (2 preceding siblings ...)
  2011-09-23 16:17 ` Guenter Roeck
@ 2011-09-25 16:27 ` Josu Lazkano
  2011-09-25 17:08 ` Guenter Roeck
                   ` (4 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: Josu Lazkano @ 2011-09-25 16:27 UTC (permalink / raw)
  To: lm-sensors

2011/9/23 Guenter Roeck <guenter.roeck@ericsson.com>:
> On Fri, 2011-09-23 at 11:57 -0400, Josu Lazkano wrote:
>> 2011/9/23 Guenter Roeck <guenter.roeck@ericsson.com>:
>> > On Fri, 2011-09-23 at 07:28 -0400, Josu Lazkano wrote:
>> >> Hello all, this is my first post on the list. I am searching for some
>> >> help to check my board sensors. I have a ZOTAC ION ITX-G Synergy
>> >> Edition board with Debian Squeeze (2.6.32), it has MCP79 and it is
>> >> supported by lm-sensors.
>> >>
>> >> I have some problems with my board voltage and I want to check all
>> >> sensors available. When I execute "sensors" this is the output:
>> >>
>> >> # sensors
>> >> coretemp-isa-0000
>> >> Adapter: ISA adapter
>> >> Core 0:      +27.0°C  (crit = +90.0°C)
>> >>
>> >> coretemp-isa-0001
>> >> Adapter: ISA adapter
>> >> Core 1:      +29.0°C  (crit = +90.0°C)
>> >>
>> >> This is just CPU temperature. Is it possible to get more info about my board?
>> >>
>> >> I read some forums and I found this interesting things:
>> >>
>> >> # modprobe i2c-dev
>> >> # modprobe i2c-nforce2
>> >> # echo "10de 0aa2" > /sys/bus/pci/drivers/nForce2_smbus/new_id
>> >> # i2cdetect -l
>> >> i2c-0 smbus           SMBus nForce2 adapter at 4d00           SMBus adapter
>> >> i2c-1 i2c             cx23885[0]                              I2C adapter
>> >> i2c-2 i2c             cx23885[0]                              I2C adapter
>> >> i2c-3 i2c             cx23885[0]                              I2C adapter
>> >> i2c-4 i2c             NVIDIA i2c adapter 0 at 3:00.0          I2C adapter
>> >> i2c-5 i2c             NVIDIA i2c adapter 2 at 3:00.0          I2C adapter
>> >> i2c-6 i2c             NVIDIA i2c adapter 3 at 3:00.0          I2C adapter
>> >>
>> >> I don't know what I am doing with the echo command, but it looks like
>> >> it found some i2c devices.
>> >>
>> >> I will appreciate any help on this, I read lots of webs but I don't
>> >> understand kernel/module compiling.
>> >>
>> > Did you try to run sensors-detect ?
>> >
>> > Guenter
>> >
>> >
>> >
>>
>> Thanks for the reply, yes, I run it:
>>
>> # sensors-detect
>> # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
>> # System: To Be Filled By O.E.M. To Be Filled By O.E.M.
>> # Board: To be filled by O.E.M. To be filled by O.E.M.
>>
>> 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.
>>
>> Some south bridges, CPUs or memory controllers contain embedded sensors.
>> Do you want to scan for them? This is totally safe. (YES/no):
>> Silicon Integrated Systems SIS5595...                       No
>> VIA VT82C686 Integrated Sensors...                          No
>> VIA VT8231 Integrated Sensors...                            No
>> AMD K8 thermal sensors...                                   No
>> AMD Family 10h thermal sensors...                           No
>> AMD Family 11h thermal sensors...                           No
>> Intel Core family thermal sensor...                         No
>> Intel Atom thermal sensor...                                Success!
>>     (driver `coretemp')
>> Intel AMB FB-DIMM thermal sensor...                         No
>> VIA C7 thermal sensor...                                    No
>> VIA Nano thermal sensor...                                  No
>>
>> 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):
>> Probing for Super-I/O at 0x2e/0x2f
>> Trying family `National Semiconductor'...                   No
>> Trying family `SMSC'...                                     No
>> Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
>> Trying family `ITE'...                                      No
>> 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
>>
>> Some systems (mainly servers) implement IPMI, a set of common interfaces
>> through which system health data may be retrieved, amongst other things.
>> We first try to get the information from SMBIOS. If we don't find it
>> there, we have to read from arbitrary I/O ports to probe for such
>> interfaces. This is normally safe. Do you want to scan for IPMI
>> interfaces? (YES/no):
>> Probing for `IPMI BMC KCS' at 0xca0...                      No
>> Probing for `IPMI BMC SMIC' at 0xca8...                     No
>>
>> Some hardware monitoring chips are 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 LM79' at 0x290...       No
>> Probing for `Winbond W83781D' at 0x290...                   No
>> Probing for `Winbond W83782D' at 0x290...                   No
>>
>> Lastly, we can probe the I2C/SMBus adapters for connected hardware
>> monitoring devices. This is the most risky part, and while it works
>> reasonably well on most systems, it has been reported to cause trouble
>> on some systems.
>> Do you want to probe the I2C/SMBus adapters now? (YES/no):
>> Using driver `i2c-nforce2' for device 0000:00:03.2: nVidia Corporation
>> nForce SMBus (MCP79)
>>
>> Next adapter: SMBus nForce2 adapter at 4d00 (i2c-0)
>> Do you want to scan it? (YES/no/selectively):
>> Client found at address 0x4c
>> Probing for `National Semiconductor LM75'...                No
>> Probing for `Dallas Semiconductor DS75'...                  No
>> Probing for `Analog Devices ADT7466'...                     No
>> Probing for `Andigilog aSC7511'...                          No
>> Probing for `Dallas Semiconductor DS1621/DS1631'...         No
>> Probing for `Analog Devices ADM1021'...                     No
>> Probing for `Analog Devices ADM1021A/ADM1023'...            No
>> Probing for `Maxim MAX1617'...                              No
>> Probing for `Maxim MAX1617A'...                             No
>> Probing for `Maxim MAX1668'...                              No
>> Probing for `Maxim MAX1805'...                              No
>> Probing for `Maxim MAX1989'...                              No
>> Probing for `Maxim MAX6655/MAX6656'...                      No
>> Probing for `TI THMC10'...                                  No
>> Probing for `National Semiconductor LM84'...                No
>> Probing for `Genesys Logic GL523SM'...                      No
>> Probing for `Onsemi MC1066'...                              No
>> Probing for `Maxim MAX1618'...                              No
>> Probing for `Maxim MAX1619'...                              No
>> Probing for `National Semiconductor LM82/LM83'...           No
>> Probing for `National Semiconductor LM90'...                No
>> Probing for `National Semiconductor LM89/LM99'...           No
>> Probing for `National Semiconductor LM86'...                No
>> Probing for `Analog Devices ADM1032'...                     No
>> Probing for `Maxim MAX6654/MAX6690'...                      No
>> Probing for `Maxim MAX6657/MAX6658/MAX6659'...              No
>> Probing for `Maxim MAX6648/MAX6649/MAX6692'...              No
>> Probing for `Maxim MAX6680/MAX6681'...                      No
>> Probing for `Winbond W83L771W/G'...                         No
>> Probing for `Winbond W83L771AWG/ASG'...                     Success!
>>     (confidence 6, driver `lm90')
>> Probing for `Texas Instruments TMP401'...                   No
>> Probing for `Texas Instruments TMP411'...                   No
>> Probing for `Texas Instruments TMP421'...                   No
>> Probing for `Texas Instruments TMP422'...                   No
>> Probing for `Texas Instruments TMP423'...                   No
>> Probing for `Texas Instruments AMC6821'...                  No
>> Probing for `National Semiconductor LM63'...                No
>> Probing for `Fintek F75363SG'...                            No
>> Probing for `National Semiconductor LM73'...                No
>> Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
>> Probing for `Analog Devices ADT7461'...                     No
>> Probing for `Analog Devices ADT7481'...                     No
>> Probing for `Fintek F75383S/M'...                           No
>> 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
>> Client found at address 0x51
>> Probing for `Analog Devices ADM1033'...                     No
>> Probing for `Analog Devices ADM1034'...                     No
>> Probing for `SPD EEPROM'...                                 No
>> Client found at address 0x52
>> Probing for `Analog Devices ADM1033'...                     No
>> Probing for `Analog Devices ADM1034'...                     No
>> Probing for `SPD EEPROM'...                                 No
>> Client found at address 0x53
>> Probing for `Analog Devices ADM1033'...                     No
>> Probing for `Analog Devices ADM1034'...                     No
>> Probing for `SPD EEPROM'...                                 No
>>
>> Next adapter: cx23885[0] (i2c-1)
>> Do you want to scan it? (yes/NO/selectively):
>>
>> Next adapter: cx23885[0] (i2c-2)
>> Do you want to scan it? (yes/NO/selectively):
>>
>> Next adapter: cx23885[0] (i2c-3)
>> Do you want to scan it? (yes/NO/selectively):
>>
>> Next adapter: NVIDIA i2c adapter 0 at 3:00.0 (i2c-4)
>> Do you want to scan it? (YES/no/selectively):
>>
>> Next adapter: NVIDIA i2c adapter 2 at 3:00.0 (i2c-5)
>> Do you want to scan it? (YES/no/selectively):
>>
>> Next adapter: NVIDIA i2c adapter 3 at 3:00.0 (i2c-6)
>> 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)
>>
>> Now follows a summary of the probes I have just done.
>> Just press ENTER to continue:
>>
>> Driver `coretemp':
>>   * Chip `Intel Atom thermal sensor' (confidence: 9)
>>
>> Driver `lm90':
>>   * Bus `SMBus nForce2 adapter at 4d00'
>>     Busdriver `i2c_nforce2', I2C address 0x4c
>>     Chip `Winbond W83L771AWG/ASG' (confidence: 6)
>>
>> To load everything that is needed, add this to /etc/modules:
>> #----cut here----
>> # Chip drivers
>> coretemp
>> lm90
>> #----cut here----
>> If you have some drivers built into your kernel, the list above will
>> contain too many modules. Skip the appropriate ones!
>>
>> Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
>> Successful!
>>
>> Monitoring programs won't work until the needed modules are
>> loaded. You may want to run '/etc/init.d/module-init-tools start'
>> to load them.
>>
>> # /etc/init.d/module-init-tools
>> Loading kernel modules...done.
>>
> Are you sure you loaded the lm90 driver ? If yes, your version of the
> driver is probably too old. Support for W83L771AWG was added to it in
> October 2010. You might have to get a new driver from a recent kernel
> version and compile and install it manually.
>
> Guenter
>
>
>

Thanks for your reply, I have loaded the lm90 module:

$ lsmod | grep lm90
lm90                    7728  0
i2c_core               12795  9
i2c_dev,lm90,ds3000,cx23885,v4l2_common,videodev,nvidia,tveeprom,i2c_nforce2

Sorry, but I have no idea how to compile the driver for my kernel.
Could you help with some steps?

I have the last BIOS version: 2K091210

Thanks for your great help.

Best regards.

-- 
Josu Lazkano

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

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: [lm-sensors] Zotac ION ITX-G Synergy Edition
  2011-09-23 11:28 [lm-sensors] Zotac ION ITX-G Synergy Edition Josu Lazkano
                   ` (3 preceding siblings ...)
  2011-09-25 16:27 ` Josu Lazkano
@ 2011-09-25 17:08 ` Guenter Roeck
  2011-09-25 17:42 ` Josu Lazkano
                   ` (3 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: Guenter Roeck @ 2011-09-25 17:08 UTC (permalink / raw)
  To: lm-sensors

On Sun, Sep 25, 2011 at 12:27:48PM -0400, Josu Lazkano wrote:
[ ... ]
> 
> Thanks for your reply, I have loaded the lm90 module:
> 
> $ lsmod | grep lm90
> lm90                    7728  0
> i2c_core               12795  9
> i2c_dev,lm90,ds3000,cx23885,v4l2_common,videodev,nvidia,tveeprom,i2c_nforce2
> 
> Sorry, but I have no idea how to compile the driver for my kernel.
> Could you help with some steps?
> 
Download all files from http://khali.linux-fr.org/devel/misc/lm90 into some directory,
then run
	make
	sudo make install
	sudo modprobe -r lm90
	sudo modprobe lm90

Guenter

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

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: [lm-sensors] Zotac ION ITX-G Synergy Edition
  2011-09-23 11:28 [lm-sensors] Zotac ION ITX-G Synergy Edition Josu Lazkano
                   ` (4 preceding siblings ...)
  2011-09-25 17:08 ` Guenter Roeck
@ 2011-09-25 17:42 ` Josu Lazkano
  2011-09-25 18:12 ` Guenter Roeck
                   ` (2 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: Josu Lazkano @ 2011-09-25 17:42 UTC (permalink / raw)
  To: lm-sensors

2011/9/25 Guenter Roeck <guenter.roeck@ericsson.com>:
> On Sun, Sep 25, 2011 at 12:27:48PM -0400, Josu Lazkano wrote:
> [ ... ]
>>
>> Thanks for your reply, I have loaded the lm90 module:
>>
>> $ lsmod | grep lm90
>> lm90                    7728  0
>> i2c_core               12795  9
>> i2c_dev,lm90,ds3000,cx23885,v4l2_common,videodev,nvidia,tveeprom,i2c_nforce2
>>
>> Sorry, but I have no idea how to compile the driver for my kernel.
>> Could you help with some steps?
>>
> Download all files from http://khali.linux-fr.org/devel/misc/lm90 into some directory,
> then run
>        make
>        sudo make install
>        sudo modprobe -r lm90
>        sudo modprobe lm90
>
> Guenter
>

Thanks!!! Now I have more data, I make this:

$ make
  CC [M]  /home/lazkano/Desktop/lm90_driver/lm90.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/lazkano/Desktop/lm90_driver/lm90.mod.o
  LD [M]  /home/lazkano/Desktop/lm90_driver/lm90.ko

# make install
test -d /lib/modules/2.6.32-5-686/kernel/drivers/hwmon || mkdir
/lib/modules/2.6.32-5-686/kernel/drivers/hwmon
cp lm90.ko /lib/modules/2.6.32-5-686/kernel/drivers/hwmon
depmod -a -F /boot/System.map-2.6.32-5-686 2.6.32-5-686

# modprobe -r lm90

# modprobe lm90

Then sensor-detect and I got this:

# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +34.0°C  (crit = +90.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +34.0°C  (crit = +90.0°C)

w83l771-i2c-0-4c
Adapter: SMBus nForce2 adapter at 4d00
temp1:       +54.0°C  (low  = -40.0°C, high = +70.0°C)
                      (crit = +85.0°C, hyst = +75.0°C)
temp2:       +65.4°C  (low  = -40.0°C, high = +70.0°C)
                      (crit = +110.0°C, hyst = +100.0°C)

Are this temps for my GPU?

I want to get USB voltage of my board, is this possible?

Thanks for your great help.

Best regards.

-- 
Josu Lazkano

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

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: [lm-sensors] Zotac ION ITX-G Synergy Edition
  2011-09-23 11:28 [lm-sensors] Zotac ION ITX-G Synergy Edition Josu Lazkano
                   ` (5 preceding siblings ...)
  2011-09-25 17:42 ` Josu Lazkano
@ 2011-09-25 18:12 ` Guenter Roeck
  2011-09-25 18:40 ` Josu Lazkano
  2011-09-28 12:43 ` Jean Delvare
  8 siblings, 0 replies; 10+ messages in thread
From: Guenter Roeck @ 2011-09-25 18:12 UTC (permalink / raw)
  To: lm-sensors

On Sun, Sep 25, 2011 at 01:42:19PM -0400, Josu Lazkano wrote:
> 2011/9/25 Guenter Roeck <guenter.roeck@ericsson.com>:
> > On Sun, Sep 25, 2011 at 12:27:48PM -0400, Josu Lazkano wrote:
> > [ ... ]
> >>
> >> Thanks for your reply, I have loaded the lm90 module:
> >>
> >> $ lsmod | grep lm90
> >> lm90                    7728  0
> >> i2c_core               12795  9
> >> i2c_dev,lm90,ds3000,cx23885,v4l2_common,videodev,nvidia,tveeprom,i2c_nforce2
> >>
> >> Sorry, but I have no idea how to compile the driver for my kernel.
> >> Could you help with some steps?
> >>
> > Download all files from http://khali.linux-fr.org/devel/misc/lm90 into some directory,
> > then run
> >        make
> >        sudo make install
> >        sudo modprobe -r lm90
> >        sudo modprobe lm90
> >
> > Guenter
> >
> 
> Thanks!!! Now I have more data, I make this:
> 
> $ make
>   CC [M]  /home/lazkano/Desktop/lm90_driver/lm90.o
>   Building modules, stage 2.
>   MODPOST 1 modules
>   CC      /home/lazkano/Desktop/lm90_driver/lm90.mod.o
>   LD [M]  /home/lazkano/Desktop/lm90_driver/lm90.ko
> 
> # make install
> test -d /lib/modules/2.6.32-5-686/kernel/drivers/hwmon || mkdir
> /lib/modules/2.6.32-5-686/kernel/drivers/hwmon
> cp lm90.ko /lib/modules/2.6.32-5-686/kernel/drivers/hwmon
> depmod -a -F /boot/System.map-2.6.32-5-686 2.6.32-5-686
> 
> # modprobe -r lm90
> 
> # modprobe lm90
> 
> Then sensor-detect and I got this:
> 
> # sensors
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +34.0°C  (crit = +90.0°C)
> 
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +34.0°C  (crit = +90.0°C)
> 
> w83l771-i2c-0-4c
> Adapter: SMBus nForce2 adapter at 4d00
> temp1:       +54.0°C  (low  = -40.0°C, high = +70.0°C)
>                       (crit = +85.0°C, hyst = +75.0°C)
> temp2:       +65.4°C  (low  = -40.0°C, high = +70.0°C)
>                       (crit = +110.0°C, hyst = +100.0°C)
> 
> Are this temps for my GPU?
> 
No idea.

> I want to get USB voltage of my board, is this possible?
> 
sensors-detect did not find any known chips, so this is unlikely. 
The chipset seems to be NVIDIA MCP7A-ION, and Nvidia is not really
known to publish much if anything about their chips.

You could try to download and install linux drivers available from Zotac
and/or from Nvidia, but I don't know if that would help. I did not find a 
linux hw monitoring driver to download anyway.

Guenter

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

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: [lm-sensors] Zotac ION ITX-G Synergy Edition
  2011-09-23 11:28 [lm-sensors] Zotac ION ITX-G Synergy Edition Josu Lazkano
                   ` (6 preceding siblings ...)
  2011-09-25 18:12 ` Guenter Roeck
@ 2011-09-25 18:40 ` Josu Lazkano
  2011-09-28 12:43 ` Jean Delvare
  8 siblings, 0 replies; 10+ messages in thread
From: Josu Lazkano @ 2011-09-25 18:40 UTC (permalink / raw)
  To: lm-sensors

2011/9/25 Guenter Roeck <guenter.roeck@ericsson.com>:
> On Sun, Sep 25, 2011 at 01:42:19PM -0400, Josu Lazkano wrote:
>> 2011/9/25 Guenter Roeck <guenter.roeck@ericsson.com>:
>> > On Sun, Sep 25, 2011 at 12:27:48PM -0400, Josu Lazkano wrote:
>> > [ ... ]
>> >>
>> >> Thanks for your reply, I have loaded the lm90 module:
>> >>
>> >> $ lsmod | grep lm90
>> >> lm90                    7728  0
>> >> i2c_core               12795  9
>> >> i2c_dev,lm90,ds3000,cx23885,v4l2_common,videodev,nvidia,tveeprom,i2c_nforce2
>> >>
>> >> Sorry, but I have no idea how to compile the driver for my kernel.
>> >> Could you help with some steps?
>> >>
>> > Download all files from http://khali.linux-fr.org/devel/misc/lm90 into some directory,
>> > then run
>> >        make
>> >        sudo make install
>> >        sudo modprobe -r lm90
>> >        sudo modprobe lm90
>> >
>> > Guenter
>> >
>>
>> Thanks!!! Now I have more data, I make this:
>>
>> $ make
>>   CC [M]  /home/lazkano/Desktop/lm90_driver/lm90.o
>>   Building modules, stage 2.
>>   MODPOST 1 modules
>>   CC      /home/lazkano/Desktop/lm90_driver/lm90.mod.o
>>   LD [M]  /home/lazkano/Desktop/lm90_driver/lm90.ko
>>
>> # make install
>> test -d /lib/modules/2.6.32-5-686/kernel/drivers/hwmon || mkdir
>> /lib/modules/2.6.32-5-686/kernel/drivers/hwmon
>> cp lm90.ko /lib/modules/2.6.32-5-686/kernel/drivers/hwmon
>> depmod -a -F /boot/System.map-2.6.32-5-686 2.6.32-5-686
>>
>> # modprobe -r lm90
>>
>> # modprobe lm90
>>
>> Then sensor-detect and I got this:
>>
>> # sensors
>> coretemp-isa-0000
>> Adapter: ISA adapter
>> Core 0:      +34.0°C  (crit = +90.0°C)
>>
>> coretemp-isa-0001
>> Adapter: ISA adapter
>> Core 1:      +34.0°C  (crit = +90.0°C)
>>
>> w83l771-i2c-0-4c
>> Adapter: SMBus nForce2 adapter at 4d00
>> temp1:       +54.0°C  (low  = -40.0°C, high = +70.0°C)
>>                       (crit = +85.0°C, hyst = +75.0°C)
>> temp2:       +65.4°C  (low  = -40.0°C, high = +70.0°C)
>>                       (crit = +110.0°C, hyst = +100.0°C)
>>
>> Are this temps for my GPU?
>>
> No idea.
>
>> I want to get USB voltage of my board, is this possible?
>>
> sensors-detect did not find any known chips, so this is unlikely.
> The chipset seems to be NVIDIA MCP7A-ION, and Nvidia is not really
> known to publish much if anything about their chips.
>
> You could try to download and install linux drivers available from Zotac
> and/or from Nvidia, but I don't know if that would help. I did not find a
> linux hw monitoring driver to download anyway.
>
> Guenter
>

Thanks, I will try to ask Zotac.

Thanks for your help, best regards.

-- 
Josu Lazkano

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

^ permalink raw reply	[flat|nested] 10+ messages in thread
* Re: [lm-sensors] Zotac ION ITX-G Synergy Edition
  2011-09-23 11:28 [lm-sensors] Zotac ION ITX-G Synergy Edition Josu Lazkano
                   ` (7 preceding siblings ...)
  2011-09-25 18:40 ` Josu Lazkano
@ 2011-09-28 12:43 ` Jean Delvare
  8 siblings, 0 replies; 10+ messages in thread
From: Jean Delvare @ 2011-09-28 12:43 UTC (permalink / raw)
  To: lm-sensors

On Sun, 25 Sep 2011 11:12:08 -0700, Guenter Roeck wrote:
> On Sun, Sep 25, 2011 at 01:42:19PM -0400, Josu Lazkano wrote:
> > w83l771-i2c-0-4c
> > Adapter: SMBus nForce2 adapter at 4d00
> > temp1:       +54.0°C  (low  = -40.0°C, high = +70.0°C)
> >                       (crit = +85.0°C, hyst = +75.0°C)
> > temp2:       +65.4°C  (low  = -40.0°C, high = +70.0°C)
> >                       (crit = +110.0°C, hyst = +100.0°C)

Glad it works :)

> > Are this temps for my GPU?
>
> No idea.

Given that the chip is on the SMBus and not the graphics chip I2C
channels, it is more likely to be monitoring come component on the main
board. That being said, with these small form factor machines, it's
hard to tell for sure. OTOH you may be able to get an answer from
Zotac, as I recall they have good technical documentation including
that kind of details.

> > I want to get USB voltage of my board, is this possible?
>
> sensors-detect did not find any known chips, so this is unlikely. 
> The chipset seems to be NVIDIA MCP7A-ION, and Nvidia is not really
> known to publish much if anything about their chips.

If memory serves, the MCP7A embeds its own hardware monitoring sensors.
I seem to recall that someone (possibly Zotac themselves, but I'm not
sure so I won't blame anyone) was supposed to send me one of these
machines so that I can write a driver, but it never happened, so we
still don't have support.

Offer is still valid, BTW. If anyone sends me one of these Zotac
systems with the MCP7A, I'll write the driver.

> You could try to download and install linux drivers available from Zotac
> and/or from Nvidia, but I don't know if that would help. I did not find a 
> linux hw monitoring driver to download anyway.

The documentation I have at hand suggests that the MCP7A only cares
about thermal management - temperatures and fans - not voltages. So
unfortunately it probably won't help Josu for USB voltage. Josu, you're
probably better off with an external voltmeter.

-- 
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

^ permalink raw reply	[flat|nested] 10+ messages in thread
end of thread, other threads:[~2011-09-28 12:43 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-23 11:28 [lm-sensors] Zotac ION ITX-G Synergy Edition Josu Lazkano
2011-09-23 15:53 ` Guenter Roeck
2011-09-23 15:57 ` Josu Lazkano
2011-09-23 16:17 ` Guenter Roeck
2011-09-25 16:27 ` Josu Lazkano
2011-09-25 17:08 ` Guenter Roeck
2011-09-25 17:42 ` Josu Lazkano
2011-09-25 18:12 ` Guenter Roeck
2011-09-25 18:40 ` Josu Lazkano
2011-09-28 12:43 ` Jean Delvare

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.