* Re: [lm-sensors] Intel DP35DP - P35 Sensor Support?
2007-10-15 2:23 [lm-sensors] Intel DP35DP - P35 Sensor Support? d.d.
@ 2007-10-28 14:26 ` Jean Delvare
2007-10-28 15:43 ` d. d. gmane
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Jean Delvare @ 2007-10-28 14:26 UTC (permalink / raw)
To: lm-sensors
On Mon, 15 Oct 2007 02:23:17 +0000 (UTC), d.d. wrote:
> I'm seeing only 2 CPU core temperatures, but am unable to pick off any other
> sensors (but I know they are there...)
>
> Any luck with the Intel Desktop DP35DP Motherboard / P35 / ICH9 ?
The ICH9 integrates sensors we don't support yet. Your motherboard may
or may not use these.
> Running Linux Kernel:
> 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 x86_64 x86_64
> GNU/Linux
Did you try running the latest version of sensors-detect? What did it
find?
--
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] 9+ messages in thread* Re: [lm-sensors] Intel DP35DP - P35 Sensor Support?
2007-10-15 2:23 [lm-sensors] Intel DP35DP - P35 Sensor Support? d.d.
2007-10-28 14:26 ` Jean Delvare
@ 2007-10-28 15:43 ` d. d. gmane
2007-10-28 15:58 ` d. d. gmane
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: d. d. gmane @ 2007-10-28 15:43 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 7126 bytes --]
Thank you for the response. Below is what I get with the latest
release...I am unable to gather the fan data or motherboard temps.
Using lmsensors with my prior motherboard (a 975xbx), I was able to
gather the data. I mention this because I know that I'm using the same
case fans, hence they work. As a side note, the BIOS hardware
monitoring does display the case fans as well.
Full details here -- are there other scans/probes that you would recommend?
[root@skippy detect]# ./sensors-detect
# sensors-detect revision 4966 (2007-10-20 01:41:53 -0700)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
Do you want to load `i2c-dev' now? (YES/no):
Module loaded successfully.
We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.
Next adapter: SMBus I801 adapter at 4000 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Next adapter: NVIDIA i2c adapter (i2c-1)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: NVIDIA i2c adapter (i2c-2)
Do you want to scan it? (YES/no/selectively):
Next adapter: NVIDIA i2c adapter (i2c-3)
Do you want to scan it? (YES/no/selectively):
Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM78-J' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Probing for `Silicon Integrated Systems SIS5595'... No
Probing for `VIA VT82C686 Integrated Sensors'... No
Probing for `VIA VT8231 Integrated Sensors'... No
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... Yes
Found `Nat. Semi. PC8374L Super IO Sensors'
(but not activated)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no):
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp' (should be inserted):
Detects correctly:
* Chip `Intel Core family thermal sensor' (confidence: 9)
I will now generate the commands needed to load the required modules.
Just press ENTER to continue:
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# Chip drivers
modprobe coretemp
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----
If you have some drivers 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 the needed
modules are loaded.
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
[root@skippy detect]#
Jean Delvare wrote:
> On Mon, 15 Oct 2007 02:23:17 +0000 (UTC), d.d. wrote:
>
>> I'm seeing only 2 CPU core temperatures, but am unable to pick off any other
>> sensors (but I know they are there...)
>>
>> Any luck with the Intel Desktop DP35DP Motherboard / P35 / ICH9 ?
>>
>
> The ICH9 integrates sensors we don't support yet. Your motherboard may
> or may not use these.
>
>
>> Running Linux Kernel:
>> 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 x86_64 x86_64
>> GNU/Linux
>>
>
> Did you try running the latest version of sensors-detect? What did it
> find?
>
>
[-- Attachment #1.2: Type: text/html, Size: 12913 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [lm-sensors] Intel DP35DP - P35 Sensor Support?
2007-10-15 2:23 [lm-sensors] Intel DP35DP - P35 Sensor Support? d.d.
2007-10-28 14:26 ` Jean Delvare
2007-10-28 15:43 ` d. d. gmane
@ 2007-10-28 15:58 ` d. d. gmane
2007-10-30 14:22 ` Jean Delvare
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: d. d. gmane @ 2007-10-28 15:58 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 13499 bytes --]
Correction...here's the proper sensors detection using 3.0.0rc3:
[root@skippy detect]# pwd
/home/david/lm_sensors-3.0.0-rc3/prog/detect
[root@skippy detect]# ./sensors-detect
# sensors-detect revision 4968 (2007-10-20 10:47:54 +0200)
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
*We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9*
We will now try to load each adapter module in turn.
*Module `i2c-i801' already loaded.*
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.
Next adapter: SMBus I801 adapter at 4000 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'...
Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'...
Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Next adapter: NVIDIA i2c adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: NVIDIA i2c adapter (i2c-2)
Do you want to scan it? (YES/no/selectively):
Next adapter: NVIDIA i2c adapter (i2c-3)
Do you want to scan it? (YES/no/selectively):
Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM78-J' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Probing for `Silicon Integrated Systems SIS5595'... No
Probing for `VIA VT82C686 Integrated Sensors'... No
Probing for `VIA VT8231 Integrated Sensors'... No
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... Yes
Found `Nat. Semi. PC8374L Super IO Sensors'
(but not activated)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no):
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
*Intel Core family thermal sensor... Success!*
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp' (should be inserted):
Detects correctly:
* Chip `Intel Core family thermal sensor' (confidence: 9)
I will now generate the commands needed to load the required modules.
Just press ENTER to continue:
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# Chip drivers
modprobe coretemp
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----
If you have some drivers 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 the needed
modules are loaded.
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
d. d. gmane wrote:
> Thank you for the response. Below is what I get with the latest
> release...I am unable to gather the fan data or motherboard temps.
> Using lmsensors with my prior motherboard (a 975xbx), I was able to
> gather the data. I mention this because I know that I'm using the
> same case fans, hence they work. As a side note, the BIOS hardware
> monitoring does display the case fans as well.
>
> Full details here -- are there other scans/probes that you would
> recommend?
>
> [root@skippy detect]# ./sensors-detect
> # sensors-detect revision 4966 (2007-10-20 01:41:53 -0700)
>
> This program will help you determine which kernel modules you need
> to load to use lm_sensors most effectively. It is generally safe
> and recommended to accept the default answers to all questions,
> unless you know what you're doing.
>
> We can start with probing for (PCI) I2C or SMBus adapters.
> Do you want to probe now? (YES/no):
> Probing for PCI bus adapters...
> Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
>
> We will now try to load each adapter module in turn.
> Module `i2c-i801' already loaded.
> If you have undetectable or unsupported adapters, you can have them
> scanned by manually loading the modules before running this script.
>
> To continue, we need module `i2c-dev' to be loaded.
> Do you want to load `i2c-dev' now? (YES/no):
> Module loaded successfully.
>
> We are now going to do the I2C/SMBus adapter probings. Some chips may
> be double detected; we choose the one with the highest confidence
> value in that case.
> If you found that the adapter hung after probing a certain address,
> you can specify that address to remain unprobed.
>
> Next adapter: SMBus I801 adapter at 4000 (i2c-0)
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x44
> Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
> Client found at address 0x50
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... Yes
> (confidence 8, not a hardware monitoring chip)
> Probing for `EDID EEPROM'... No
> Client found at address 0x51
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... Yes
> (confidence 8, not a hardware monitoring chip)
> Probing for `EDID EEPROM'... No
> Client found at address 0x52
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... Yes
> (confidence 8, not a hardware monitoring chip)
> Probing for `EDID EEPROM'... No
> Client found at address 0x53
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... Yes
> (confidence 8, not a hardware monitoring chip)
> Probing for `EDID EEPROM'... No
>
> Next adapter: NVIDIA i2c adapter (i2c-1)
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x50
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... No
> Probing for `EDID EEPROM'... Yes
> (confidence 8, not a hardware monitoring chip)
>
> Next adapter: NVIDIA i2c adapter (i2c-2)
> Do you want to scan it? (YES/no/selectively):
>
> Next adapter: NVIDIA i2c adapter (i2c-3)
> Do you want to scan it? (YES/no/selectively):
>
> Some chips are also accessible through the ISA I/O ports. We have to
> write to arbitrary I/O ports to probe them. This is usually safe though.
> Yes, you do have ISA I/O ports even if you do not have any ISA slots!
> Do you want to scan the ISA I/O ports? (YES/no):
> Probing for `National Semiconductor LM78' at 0x290... No
> Probing for `National Semiconductor LM78-J' at 0x290... No
> Probing for `National Semiconductor LM79' at 0x290... No
> Probing for `Winbond W83781D' at 0x290... No
> Probing for `Winbond W83782D' at 0x290... No
> Probing for `Silicon Integrated Systems SIS5595'... No
> Probing for `VIA VT82C686 Integrated Sensors'... No
> Probing for `VIA VT8231 Integrated Sensors'... No
> Probing for `IPMI BMC KCS' at 0xca0... No
> Probing for `IPMI BMC SMIC' at 0xca8... No
>
> Some Super I/O chips may also contain sensors. We have to write to
> standard I/O ports to probe them. This is usually safe.
> Do you want to scan for Super I/O sensors? (YES/no):
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor'... Yes
> Found `Nat. Semi. PC8374L Super IO Sensors'
> (but not activated)
> Probing for Super-I/O at 0x4e/0x4f
> Trying family `National Semiconductor'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Fintek'... No
> Trying family `ITE'... No
>
> Some CPUs or memory controllers may also contain embedded sensors.
> Do you want to scan for them? (YES/no):
> AMD K8 thermal sensors... No
> AMD K10 thermal sensors... No
> Intel Core family thermal sensor... Success!
> (driver `coretemp')
> Intel AMB FB-DIMM thermal sensor... No
>
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
>
> Driver `coretemp' (should be inserted):
> Detects correctly:
> * Chip `Intel Core family thermal sensor' (confidence: 9)
>
> I will now generate the commands needed to load the required modules.
> Just press ENTER to continue:
>
> To load everything that is needed, add this to some /etc/rc* file:
>
> #----cut here----
> # Chip drivers
> modprobe coretemp
> # sleep 2 # optional
> /usr/bin/sensors -s # recommended
> #----cut here----
>
> If you have some drivers 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 the needed
> modules are loaded.
>
> Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
> [root@skippy detect]#
>
>
> Jean Delvare wrote:
>> On Mon, 15 Oct 2007 02:23:17 +0000 (UTC), d.d. wrote:
>>
>>> I'm seeing only 2 CPU core temperatures, but am unable to pick off any other
>>> sensors (but I know they are there...)
>>>
>>> Any luck with the Intel Desktop DP35DP Motherboard / P35 / ICH9 ?
>>>
>>
>> The ICH9 integrates sensors we don't support yet. Your motherboard may
>> or may not use these.
>>
>>
>>> Running Linux Kernel:
>>> 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 x86_64 x86_64
>>> GNU/Linux
>>>
>>
>> Did you try running the latest version of sensors-detect? What did it
>> find?
>>
>>
[-- Attachment #1.2: Type: text/html, Size: 24507 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [lm-sensors] Intel DP35DP - P35 Sensor Support?
2007-10-15 2:23 [lm-sensors] Intel DP35DP - P35 Sensor Support? d.d.
` (2 preceding siblings ...)
2007-10-28 15:58 ` d. d. gmane
@ 2007-10-30 14:22 ` Jean Delvare
2007-10-30 22:26 ` d. d. gmane
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Jean Delvare @ 2007-10-30 14:22 UTC (permalink / raw)
To: lm-sensors
Please do not send HTML mails to this mailing list. This makes your
post very large for no benefit.
On Sun, 28 Oct 2007 08:58:48 -0700, d. d. gmane wrote:
> Correction...here's the proper sensors detection using 3.0.0rc3:
In fact, both branches of lm-sensors have the same version of
sensors-detect.
> (...)
> Some Super I/O chips may also contain sensors. We have to write to
> standard I/O ports to probe them. This is usually safe.
> Do you want to scan for Super I/O sensors? (YES/no):
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor'... Yes
> Found `Nat. Semi. PC8374L Super IO Sensors'
> (but not activated)
> Probing for Super-I/O at 0x4e/0x4f
> Trying family `National Semiconductor'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Fintek'... No
> Trying family `ITE'... No
It it possible, though unlikely, that the PC8374L sensors are used. I
say "unlikely" because sensors should be activated if they were used.
But we can still investigate this. Please provide the output of:
isadump 0x2e 0x2f 0x08
The other possibility is that the ICH9 internal sensors are used, but
we do not support them yet. Well we do not support the PC8374L sensors
either...
The DP35DP technical documentation suggests that the ICH9 is used for
the fan speed control and monitoring. It's not so clear about
temperature and voltage sensors, however it claims automatic fan speed
control, which usually means that the fan and temperature sensors are
in the same chip. So my guess is that the only thing that may actually
be monitored by the PC8374L on your board are the voltages.
--
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] 9+ messages in thread* Re: [lm-sensors] Intel DP35DP - P35 Sensor Support?
2007-10-15 2:23 [lm-sensors] Intel DP35DP - P35 Sensor Support? d.d.
` (3 preceding siblings ...)
2007-10-30 14:22 ` Jean Delvare
@ 2007-10-30 22:26 ` d. d. gmane
2007-10-31 19:40 ` Jean Delvare
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: d. d. gmane @ 2007-10-30 22:26 UTC (permalink / raw)
To: lm-sensors
Here are the results of: isadump 0x2e 0x2f 0x08
[root@skippy dump]# pwd
/home/david/lm_sensors-3.0.0-rc3/prog/dump
[root@skippy dump]# ./isadump 0x2e 0x2f 0x08
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x2e and data register 0x2f.
Probing bank 8 using bank register 0x07.
Continue? [Y/n] Y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41
20: f1 91 00 00 c1 01 00 91 00 91 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [lm-sensors] Intel DP35DP - P35 Sensor Support?
2007-10-15 2:23 [lm-sensors] Intel DP35DP - P35 Sensor Support? d.d.
` (4 preceding siblings ...)
2007-10-30 22:26 ` d. d. gmane
@ 2007-10-31 19:40 ` Jean Delvare
2007-11-01 3:50 ` d. d. gmane
2007-11-02 10:32 ` Jean Delvare
7 siblings, 0 replies; 9+ messages in thread
From: Jean Delvare @ 2007-10-31 19:40 UTC (permalink / raw)
To: lm-sensors
On Tue, 30 Oct 2007 15:26:55 -0700, d. d. gmane wrote:
> Here are the results of: isadump 0x2e 0x2f 0x08
>
> [root@skippy dump]# pwd
> /home/david/lm_sensors-3.0.0-rc3/prog/dump
>
> [root@skippy dump]# ./isadump 0x2e 0x2f 0x08
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address register 0x2e and data register 0x2f.
> Probing bank 8 using bank register 0x07.
> Continue? [Y/n] Y
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41
> 20: f1 91 00 00 c1 01 00 91 00 91 00 00 00 00 00 00
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
OK, access to the hardware monitoring device is disabled. If you want
to investigate a bit further, you can attempt to enable it:
* Search in /proc/ioports for a free space of at least 256 bytes,
aligned on a 256-byte boundary (e.g. 0x0a00 to 0x0aff).
* Write the address in question to the PC8374L chip and
enable the logical device:
isaset 0x2e 0x2f 0x07 0x08
isaset 0x2e 0x2f 0x60 0x0a # <-- high byte of the address
isaset 0x2e 0x2f 0x61 0x00 # <-- low byte of the address
isaset 0x2e 0x2f 0x30 0x01
* Run isadump again and check that the writes were successful:
isadump 0x2e 0x2f 0x08
* If registers 0x30, 0x60 and 0x61 have the expected values, try
dumping the logical device's I/O area:
isadump -f 0x0a00 # <-- adjust with the address you used
Only do that if you are really motivated in getting the voltage
readings. I don't know the PC8374L very well and it seems to be a
somewhat complex chip - or at least different from what I'm used to.
Even if the sequence above reveals something interesting, there's
probably a long way to go before you can get the voltage readings, and
I am almost certain that you won't get temperatures nor fan speeds from
that device anyway.
--
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] 9+ messages in thread* Re: [lm-sensors] Intel DP35DP - P35 Sensor Support?
2007-10-15 2:23 [lm-sensors] Intel DP35DP - P35 Sensor Support? d.d.
` (5 preceding siblings ...)
2007-10-31 19:40 ` Jean Delvare
@ 2007-11-01 3:50 ` d. d. gmane
2007-11-02 10:32 ` Jean Delvare
7 siblings, 0 replies; 9+ messages in thread
From: d. d. gmane @ 2007-11-01 3:50 UTC (permalink / raw)
To: lm-sensors
Jean, Hmm.. Strange results indeed. It's odd that via BIOS HW
monitoring, that the values are available. Has intel (un)intentionally
used a chip that's hard to access?
When looking for open ioports, 0x0a00 was open, so I used it for all of
the rest of the testing. Sadly, I think it's going to be difficult just
as you predicted. Thank you for your time in looking at the prior
messages. You're doing great work with lm sensors!
[root@skippy ]# isaset 0x2e 0x2f 0x07 0x08
WARNING! Running this program can cause system crashes, data loss and worse!
I will write value 0x08 to address 0x07 of chip with address register 0x2e
and data register 0x2f.
Continue? [Y/n] Y
[root@skippy ]# isaset 0x2e 0x2f 0x60 0x0a
WARNING! Running this program can cause system crashes, data loss and worse!
I will write value 0x0a to address 0x60 of chip with address register 0x2e
and data register 0x2f.
Continue? [Y/n] y
[root@skippy ]# isaset 0x2e 0x2f 0x61 0x00
WARNING! Running this program can cause system crashes, data loss and worse!
I will write value 0x00 to address 0x61 of chip with address register 0x2e
and data register 0x2f.
Continue? [Y/n] Y
[root@skippy ]# isaset 0x2e 0x2f 0x30 0x01
WARNING! Running this program can cause system crashes, data loss and worse!
I will write value 0x01 to address 0x30 of chip with address register 0x2e
and data register 0x2f.
Continue? [Y/n] Y
[root@skippy ]# isadump 0x2e 0x2f 0x08
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x2e and data register 0x2f.
Probing bank 8 using bank register 0x07.
Continue? [Y/n] Y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41
20: f1 91 00 00 c1 01 00 91 00 91 00 00 00 00 00 00
30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[root@skippy ]# isadump -f 0x0a00
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address range 0xa00 to 0xaff.
Continue? [Y/n] Y
0 1 2 3 4 5 6 7 8 9 a b c d e f
0a00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0aa0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ab0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ac0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ad0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0ae0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0af0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[root@skippy ]#
Jean Delvare wrote:
> On Tue, 30 Oct 2007 15:26:55 -0700, d. d. gmane wrote:
>
>> Here are the results of: isadump 0x2e 0x2f 0x08
>>
>> [root@skippy dump]# pwd
>> /home//lm_sensors-3.0.0-rc3/prog/dump
>>
>> [root@skippy dump]# ./isadump 0x2e 0x2f 0x08
>> WARNING! Running this program can cause system crashes, data loss and worse!
>> I will probe address register 0x2e and data register 0x2f.
>> Probing bank 8 using bank register 0x07.
>> Continue? [Y/n] Y
>> 0 1 2 3 4 5 6 7 8 9 a b c d e f
>> 00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
>> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41
>> 20: f1 91 00 00 c1 01 00 91 00 91 00 00 00 00 00 00
>> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00
>> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>
>
> OK, access to the hardware monitoring device is disabled. If you want
> to investigate a bit further, you can attempt to enable it:
>
> * Search in /proc/ioports for a free space of at least 256 bytes,
> aligned on a 256-byte boundary (e.g. 0x0a00 to 0x0aff).
>
> * Write the address in question to the PC8374L chip and
> enable the logical device:
>
> isaset 0x2e 0x2f 0x07 0x08
> isaset 0x2e 0x2f 0x60 0x0a # <-- high byte of the address
> isaset 0x2e 0x2f 0x61 0x00 # <-- low byte of the address
> isaset 0x2e 0x2f 0x30 0x01
>
> * Run isadump again and check that the writes were successful:
>
> isadump 0x2e 0x2f 0x08
>
> * If registers 0x30, 0x60 and 0x61 have the expected values, try
> dumping the logical device's I/O area:
>
> isadump -f 0x0a00 # <-- adjust with the address you used
>
> Only do that if you are really motivated in getting the voltage
> readings. I don't know the PC8374L very well and it seems to be a
> somewhat complex chip - or at least different from what I'm used to.
> Even if the sequence above reveals something interesting, there's
> probably a long way to go before you can get the voltage readings, and
> I am almost certain that you won't get temperatures nor fan speeds from
> that device anyway.
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [lm-sensors] Intel DP35DP - P35 Sensor Support?
2007-10-15 2:23 [lm-sensors] Intel DP35DP - P35 Sensor Support? d.d.
` (6 preceding siblings ...)
2007-11-01 3:50 ` d. d. gmane
@ 2007-11-02 10:32 ` Jean Delvare
7 siblings, 0 replies; 9+ messages in thread
From: Jean Delvare @ 2007-11-02 10:32 UTC (permalink / raw)
To: lm-sensors
On Wed, 31 Oct 2007 20:50:13 -0700, d. d. gmane wrote:
> Jean, Hmm.. Strange results indeed. It's odd that via BIOS HW
> monitoring, that the values are available. Has intel (un)intentionally
> used a chip that's hard to access?
>
> When looking for open ioports, 0x0a00 was open, so I used it for all of
> the rest of the testing. Sadly, I think it's going to be difficult just
> as you predicted. Thank you for your time in looking at the prior
> messages. You're doing great work with lm sensors!
>
>
>
> [root@skippy ]# isaset 0x2e 0x2f 0x07 0x08
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will write value 0x08 to address 0x07 of chip with address register 0x2e
> and data register 0x2f.
> Continue? [Y/n] Y
>
> [root@skippy ]# isaset 0x2e 0x2f 0x60 0x0a
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will write value 0x0a to address 0x60 of chip with address register 0x2e
> and data register 0x2f.
> Continue? [Y/n] y
>
> [root@skippy ]# isaset 0x2e 0x2f 0x61 0x00
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will write value 0x00 to address 0x61 of chip with address register 0x2e
> and data register 0x2f.
> Continue? [Y/n] Y
>
> [root@skippy ]# isaset 0x2e 0x2f 0x30 0x01
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will write value 0x01 to address 0x30 of chip with address register 0x2e
> and data register 0x2f.
> Continue? [Y/n] Y
>
> [root@skippy ]# isadump 0x2e 0x2f 0x08
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address register 0x2e and data register 0x2f.
> Probing bank 8 using bank register 0x07.
> Continue? [Y/n] Y
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41
> 20: f1 91 00 00 c1 01 00 91 00 91 00 00 00 00 00 00
> 30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> [root@skippy ]# isadump -f 0x0a00
> WARNING! Running this program can cause system crashes, data loss and worse!
> I will probe address range 0xa00 to 0xaff.
> Continue? [Y/n] Y
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 0a00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0a90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0aa0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ab0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ac0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ad0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0ae0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 0af0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [root@skippy ]#
I expected to see something here, but it's desperately empty. I have no
idea why enabling the I/O area didn't work as expected. And I don't
have the time to investigate further, sorry.
--
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] 9+ messages in thread