* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
@ 2012-09-13 15:06 ` Guenter Roeck
2012-09-14 11:56 ` Jean Delvare
` (15 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Guenter Roeck @ 2012-09-13 15:06 UTC (permalink / raw)
To: lm-sensors
On Thu, Sep 13, 2012 at 09:19:39AM +0100, MrNice wrote:
> Hi,
>
> I try to get the measurements from my hardware motherboard. I
> installed lm_sensors-3.3.2 and the driver groeck-w83627ehf-d0f3584
>
> As, when I run sensors, I get 0 RPM (min = 0 RPM)
>
> +++++++++++++++++++++++++
> ~$ sensors
> nct6776-isa-0290
> Adapter: ISA adapter
> Vcore: +0.90 V (min = +0.00 V, max = +1.74 V)
> in1: +1.85 V (min = +0.00 V, max = +0.00 V) ALARM
> AVCC: +3.31 V (min = +2.98 V, max = +3.63 V)
> +3.3V: +3.30 V (min = +2.98 V, max = +3.63 V)
> in4: +0.02 V (min = +0.00 V, max = +0.00 V) ALARM
> in5: +1.72 V (min = +0.00 V, max = +0.00 V) ALARM
> 3VSB: +3.46 V (min = +2.98 V, max = +3.63 V)
> Vbat: +0.00 V (min = +2.70 V, max = +3.30 V) ALARM
> Fan_01: 0 RPM (min = 0 RPM) ALARM
> fan2: 0 RPM (min = 0 RPM) ALARM
> fan3: 0 RPM (min = 0 RPM) ALARM
> fan4: 0 RPM (min = 500 RPM) ALARM
> SYSTIN: +27.0°C (high = +0.0°C, hyst = +0.0°C) ALARM
> sensor = thermistor
> CPUTIN: +24.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
> AUXTIN: +127.5°C (high = +114.0°C, hyst = +114.0°C) ALARM
> sensor = thermistor
> cpu0_vid: +0.000 V
> intrusion0: ALARM
> intrusion1: OK
>
> fam15h_power-pci-00c4
> Adapter: PCI adapter
> power1: 117.23 W (crit = 124.95 W)
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1: +5.6°C (high = +70.0°C)
> (crit = +70.0°C, hyst = +67.0°C)
> ++++++++++++++++++++++++++++
>
>
> Following the advice
> http://lm-sensors.org/browser/lm-sensors/trunk/doc/fan-divisors
> I added the divisor in the sensors3.conf:
>
> +++++++++++++++++++++++++
> chip "w83627ehf-*" "w83627dhg-*" "w83667hg-*" "nct6775-*" "nct6776-*"
>
> label in0 "Vcore"
> label in2 "AVCC"
> label in3 "+3.3V"
> label in7 "3VSB"
> label in8 "Vbat"
>
> set in2_min 3.3 * 0.90
> set in2_max 3.3 * 1.10
> set in3_min 3.3 * 0.90
> set in3_max 3.3 * 1.10
> set in7_min 3.3 * 0.90
> set in7_max 3.3 * 1.10
> set in8_min 3.0 * 0.90
> set in8_max 3.0 * 1.10
>
> # For parser test
> label fan1 "Fan_01"
> ignore fan5
> set fan4_min 500
> set fan4_div 8 # Parser error
>
> # label temp1 "w83627 TEMPERATURE 01" # OK parser
>
> chip "k10temp-*"
>
> # label temp1 "k10 TEMPERATURE 01" # OK parser
>
> chip "fam15h_power-*"
>
> # label power1 "fam15h POWER 01" # OK parser
> ++++++++++++++++++++++++
>
> When I run sensors -s with the line
> set fan4_div 8
> I get the error
>
> ++++++++++++++++++++++++
> ~$ sudo sensors -s
> Error: File /etc/sensors3.conf, line 41: Unknown feature name
> nct6776-isa-0290: No such subfeature known
nct6776 does not have fan divisor registers, so this is not really surprising.
> ++++++++++++++++++++++++
>
> You can see in the sensors3.conf, other lines are OK with the parser.
> I tried with different divisors and different fan numbers.
> Could you tell me whether it's my mistake or a bug?
>
> Configuration:
> ASRock 970 Extreme4 UEFI v2.00
> AMD FX-8120
> Kernel 3.2.0-30-generic
> Ubuntu 12.04 64-bit
> lm_sensors-3.3.2 (manual install)
> driver groeck-w83627ehf-d0f3584 (manual install)
>
>
> BTW, could you give me a link where I could get the definition/info
> regarding the labels SYSTIN, CPUTIN, etc...
The labels are derived from the chip datasheet. SYSTIN = system temperature,
probably a board temperature sensor CPUTIN = CPU temperature sensor.
> You can see I have AUXTIN: +127.5°C. I don't know what is this value
> but looks for me very suspicious.
Most likely it is not connected.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
2012-09-13 15:06 ` Guenter Roeck
@ 2012-09-14 11:56 ` Jean Delvare
2012-09-14 13:45 ` Guenter Roeck
` (14 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Jean Delvare @ 2012-09-14 11:56 UTC (permalink / raw)
To: lm-sensors
Sorry I forgot to reply to the list last time, adding it back...
On Thu, 13 Sep 2012 15:07:30 +0100, MrNice wrote:
> On 13/09/12 10:15, Jean Delvare wrote:
> > On Thu, 13 Sep 2012 09:19:39 +0100, MrNice wrote:
> >> Following the advice
> >> http://lm-sensors.org/browser/lm-sensors/trunk/doc/fan-divisors
> > This doesn't apply to the NCT6776. See in the output above, there is no
> > "div =" on the fan lines.
> >
> > Maybe the document should be clarified.
I just did so [1], hopefully the updated document is clearer and users
will understand whether they have to read it or not.
[1] http://www.lm-sensors.org/changeset/6071
> Do you know if is there any way to collect the right speeds as UEFI
> values are good.
No idea. Check the motherboard documentation. If the fans are really
connected to the NCT6776, this may be a driver bug. BTW you said you're
using the w83627ehf driver from groeck, but there is a better driver
for the NCT6776 now:
https://github.com/groeck/nct6775
Guenter, maybe this driver should be listed at
http://roeck-us.net/linux/drivers/
so that users find it?
If the new driver doesn't help, maybe the fans are connected to another
monitoring chip.
> Does the mean all the AMD FX CPU have the same issue? What to do? Is a
> patch on the way?
There's no relation between fan speed monitoring and the CPU your
system is using.
> Temperatures in the hardware area have a load of loose vocabulary.
> I try to be accurate:
> Could you confirm that CPUTIN is the temperature read by the sensor in
> the socket of the motherboard called Tjunction?
I don't think so. AFAIK Tjunction refers to a temperature limit inside
the CPU, and it related to the digital thermal sensor in the CPU.
CPUTIN OTOH is an analog thermal sensor. As it is a thermistor in your
case, it is likely under the CPU, in the middle of the CPU socket.
> Could you confirm that K10temp, temp1 is what AMD call Tctl (sliding
> scale) accessible through D18F3xA4[CurTmp] register (from BIOS and
> Kernel Developer's Guide)?
Yes, this is correct.
> Could you tell me what is SYSTIN (system temp input) and AUXTIN
> (auxiliary temp input)?
These are analog thermal sensor inputs. As already mentioned, AUXTIN is
apparently not used on your board, you can ignore it. SYSTIN could be
anywhere on the motherboard, we can't tell. Maybe the technical
documentation for your board has the information.
> Are they in the list bellow?
I have no idea where this list comes from, so I can't really comment on
that, sorry. Other than:
> TJunction is the temperature where the pins hit the board
>
> TJunction is still a diode on the board, under the processor
This is completely wrong. At least this is not what the rest of the
world, starting with Intel technical documentation, refers to as
Tjunction.
--
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] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
2012-09-13 15:06 ` Guenter Roeck
2012-09-14 11:56 ` Jean Delvare
@ 2012-09-14 13:45 ` Guenter Roeck
2012-09-14 16:14 ` MrNice
` (13 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Guenter Roeck @ 2012-09-14 13:45 UTC (permalink / raw)
To: lm-sensors
On Fri, Sep 14, 2012 at 01:56:40PM +0200, Jean Delvare wrote:
> Sorry I forgot to reply to the list last time, adding it back...
>
> On Thu, 13 Sep 2012 15:07:30 +0100, MrNice wrote:
> > On 13/09/12 10:15, Jean Delvare wrote:
> > > On Thu, 13 Sep 2012 09:19:39 +0100, MrNice wrote:
> > >> Following the advice
> > >> http://lm-sensors.org/browser/lm-sensors/trunk/doc/fan-divisors
> > > This doesn't apply to the NCT6776. See in the output above, there is no
> > > "div =" on the fan lines.
> > >
> > > Maybe the document should be clarified.
>
> I just did so [1], hopefully the updated document is clearer and users
> will understand whether they have to read it or not.
>
> [1] http://www.lm-sensors.org/changeset/6071
>
> > Do you know if is there any way to collect the right speeds as UEFI
> > values are good.
>
> No idea. Check the motherboard documentation. If the fans are really
> connected to the NCT6776, this may be a driver bug. BTW you said you're
> using the w83627ehf driver from groeck, but there is a better driver
> for the NCT6776 now:
> https://github.com/groeck/nct6775
> Guenter, maybe this driver should be listed at
> http://roeck-us.net/linux/drivers/
> so that users find it?
>
Thought it did. I'll check (and remove the old one).
> If the new driver doesn't help, maybe the fans are connected to another
> monitoring chip.
>
Some of the Intel motherboards use MEI to control the fans. Best way to
find out is to read the motherboard specification - it is usually mentioned
somewhere in there.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (2 preceding siblings ...)
2012-09-14 13:45 ` Guenter Roeck
@ 2012-09-14 16:14 ` MrNice
2012-09-14 16:37 ` Guenter Roeck
` (12 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: MrNice @ 2012-09-14 16:14 UTC (permalink / raw)
To: lm-sensors
On 14/09/12 12:56, Jean Delvare wrote:
> Sorry I forgot to reply to the list last time, adding it back...
>
> On Thu, 13 Sep 2012 15:07:30 +0100, MrNice wrote:
>> On 13/09/12 10:15, Jean Delvare wrote:
>>> On Thu, 13 Sep 2012 09:19:39 +0100, MrNice wrote:
>>>> Following the advice
>>>> http://lm-sensors.org/browser/lm-sensors/trunk/doc/fan-divisors
>>> This doesn't apply to the NCT6776. See in the output above, there is no
>>> "div =" on the fan lines.
>>>
>>> Maybe the document should be clarified.
> I just did so [1], hopefully the updated document is clearer and users
> will understand whether they have to read it or not.
>
> [1] http://www.lm-sensors.org/changeset/6071
>
>> Do you know if is there any way to collect the right speeds as UEFI
>> values are good.
> No idea. Check the motherboard documentation. If the fans are really
> connected to the NCT6776, this may be a driver bug. BTW you said you're
> using the w83627ehf driver from groeck, but there is a better driver
> for the NCT6776 now:
> https://github.com/groeck/nct6775
> Guenter, maybe this driver should be listed at
> http://roeck-us.net/linux/drivers/
> so that users find it?
>
> If the new driver doesn't help, maybe the fans are connected to another
> monitoring chip.
>
>> Does the mean all the AMD FX CPU have the same issue? What to do? Is a
>> patch on the way?
> There's no relation between fan speed monitoring and the CPU your
> system is using.
>
>> Temperatures in the hardware area have a load of loose vocabulary.
>> I try to be accurate:
>> Could you confirm that CPUTIN is the temperature read by the sensor in
>> the socket of the motherboard called Tjunction?
> I don't think so. AFAIK Tjunction refers to a temperature limit inside
> the CPU, and it related to the digital thermal sensor in the CPU.
> CPUTIN OTOH is an analog thermal sensor. As it is a thermistor in your
> case, it is likely under the CPU, in the middle of the CPU socket.
>
>> Could you confirm that K10temp, temp1 is what AMD call Tctl (sliding
>> scale) accessible through D18F3xA4[CurTmp] register (from BIOS and
>> Kernel Developer's Guide)?
> Yes, this is correct.
>
>> Could you tell me what is SYSTIN (system temp input) and AUXTIN
>> (auxiliary temp input)?
> These are analog thermal sensor inputs. As already mentioned, AUXTIN is
> apparently not used on your board, you can ignore it. SYSTIN could be
> anywhere on the motherboard, we can't tell. Maybe the technical
> documentation for your board has the information.
>
>> Are they in the list bellow?
> I have no idea where this list comes from, so I can't really comment on
> that, sorry. Other than:
>
>> TJunction is the temperature where the pins hit the board
>>
>> TJunction is still a diode on the board, under the processor
> This is completely wrong. At least this is not what the rest of the
> world, starting with Intel technical documentation, refers to as
> Tjunction.
>
The new document version is now clear to understand and moreover we know
why we don't need the divisor in some chips.
I installed the new driver. For around 15 minutes I had fan2 value
(about 1150 RPM).
I did some changes in the sensors3.conf file, then sensors -s, was OK.
After some try I have fan2 = 0 RPM. I did cold boot, reinstall driver,
reinstall lm-sensors, still 0 RPM.
I can't find why it's not working any more.
Any idea?
TJunction and vocabulary:
This term is for me as well the temperature of a PN/NP, etc junction in
a electronic component mainly used to calculate the radiator.
In the CPU/motherboard environment it seems to be the temperature at the
junction between CPU and motherboard, at the pins.
I had this info and I wrote the vocabulary list from the following link
http://www.overclock.net/t/1128821/amd-temp-information-and-guide/70
in the post #73
These are mails from AMD support so I suppose the definitions are good
at least for AMD.
However this other link is more like I use to know.
http://www.alcpu.com/forums/viewtopic.php?fc&t‰2
I will try to have again the fan value and let you know
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (3 preceding siblings ...)
2012-09-14 16:14 ` MrNice
@ 2012-09-14 16:37 ` Guenter Roeck
2012-09-16 6:44 ` Jean-Pierre Thibert
` (11 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Guenter Roeck @ 2012-09-14 16:37 UTC (permalink / raw)
To: lm-sensors
On Fri, Sep 14, 2012 at 05:14:45PM +0100, MrNice wrote:
> On 14/09/12 12:56, Jean Delvare wrote:
> >Sorry I forgot to reply to the list last time, adding it back...
> >
> >On Thu, 13 Sep 2012 15:07:30 +0100, MrNice wrote:
> >>On 13/09/12 10:15, Jean Delvare wrote:
> >>>On Thu, 13 Sep 2012 09:19:39 +0100, MrNice wrote:
> >>>>Following the advice
> >>>>http://lm-sensors.org/browser/lm-sensors/trunk/doc/fan-divisors
> >>>This doesn't apply to the NCT6776. See in the output above, there is no
> >>>"div =" on the fan lines.
> >>>
> >>>Maybe the document should be clarified.
> >I just did so [1], hopefully the updated document is clearer and users
> >will understand whether they have to read it or not.
> >
> >[1] http://www.lm-sensors.org/changeset/6071
> >
> >>Do you know if is there any way to collect the right speeds as UEFI
> >>values are good.
> >No idea. Check the motherboard documentation. If the fans are really
> >connected to the NCT6776, this may be a driver bug. BTW you said you're
> >using the w83627ehf driver from groeck, but there is a better driver
> >for the NCT6776 now:
> > https://github.com/groeck/nct6775
> >Guenter, maybe this driver should be listed at
> > http://roeck-us.net/linux/drivers/
> >so that users find it?
> >
> >If the new driver doesn't help, maybe the fans are connected to another
> >monitoring chip.
> >
> >>Does the mean all the AMD FX CPU have the same issue? What to do? Is a
> >>patch on the way?
> >There's no relation between fan speed monitoring and the CPU your
> >system is using.
> >
> >>Temperatures in the hardware area have a load of loose vocabulary.
> >>I try to be accurate:
> >>Could you confirm that CPUTIN is the temperature read by the sensor in
> >>the socket of the motherboard called Tjunction?
> >I don't think so. AFAIK Tjunction refers to a temperature limit inside
> >the CPU, and it related to the digital thermal sensor in the CPU.
> >CPUTIN OTOH is an analog thermal sensor. As it is a thermistor in your
> >case, it is likely under the CPU, in the middle of the CPU socket.
> >
> >>Could you confirm that K10temp, temp1 is what AMD call Tctl (sliding
> >>scale) accessible through D18F3xA4[CurTmp] register (from BIOS and
> >>Kernel Developer's Guide)?
> >Yes, this is correct.
> >
> >>Could you tell me what is SYSTIN (system temp input) and AUXTIN
> >>(auxiliary temp input)?
> >These are analog thermal sensor inputs. As already mentioned, AUXTIN is
> >apparently not used on your board, you can ignore it. SYSTIN could be
> >anywhere on the motherboard, we can't tell. Maybe the technical
> >documentation for your board has the information.
> >
> >>Are they in the list bellow?
> >I have no idea where this list comes from, so I can't really comment on
> >that, sorry. Other than:
> >
> >>TJunction is the temperature where the pins hit the board
> >>
> >>TJunction is still a diode on the board, under the processor
> >This is completely wrong. At least this is not what the rest of the
> >world, starting with Intel technical documentation, refers to as
> >Tjunction.
> >
>
> The new document version is now clear to understand and moreover we
> know why we don't need the divisor in some chips.
>
> I installed the new driver. For around 15 minutes I had fan2 value
> (about 1150 RPM).
> I did some changes in the sensors3.conf file, then sensors -s, was OK.
> After some try I have fan2 = 0 RPM. I did cold boot, reinstall
> driver, reinstall lm-sensors, still 0 RPM.
> I can't find why it's not working any more.
> Any idea?
>
ASRock uses GPIO pins to multiplex multiple fan speed inputs to a single pin
at the NCT6776. It might be that you somehow triggered or changed a multiplexer
configuration.
Do you see fan speed(s) in the BIOS ? If you do, it might well be that you have
to do that once after powerup to connect a fan to the fan speed input of the
NCT6776, and then you might see it in the driver.
[ And, no, it is practically impossible to get the necessary information to set
the GPIO multiplexer from the board vendor. AFAIK they are using GPIO pins,
but which ones on which board is a mystery. ]
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (4 preceding siblings ...)
2012-09-14 16:37 ` Guenter Roeck
@ 2012-09-16 6:44 ` Jean-Pierre Thibert
2012-09-16 18:53 ` Guenter Roeck
` (10 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Jean-Pierre Thibert @ 2012-09-16 6:44 UTC (permalink / raw)
To: lm-sensors
On 14/09/12 17:37, Guenter Roeck wrote:
> On Fri, Sep 14, 2012 at 05:14:45PM +0100, MrNice wrote:
>> On 14/09/12 12:56, Jean Delvare wrote:
>>> Sorry I forgot to reply to the list last time, adding it back...
>>>
>>> On Thu, 13 Sep 2012 15:07:30 +0100, MrNice wrote:
>>>> On 13/09/12 10:15, Jean Delvare wrote:
>>>>> On Thu, 13 Sep 2012 09:19:39 +0100, MrNice wrote:
>>>>>> Following the advice
>>>>>> http://lm-sensors.org/browser/lm-sensors/trunk/doc/fan-divisors
>>>>> This doesn't apply to the NCT6776. See in the output above, there is no
>>>>> "div =" on the fan lines.
>>>>>
>>>>> Maybe the document should be clarified.
>>> I just did so [1], hopefully the updated document is clearer and users
>>> will understand whether they have to read it or not.
>>>
>>> [1] http://www.lm-sensors.org/changeset/6071
>>>
>>>> Do you know if is there any way to collect the right speeds as UEFI
>>>> values are good.
>>> No idea. Check the motherboard documentation. If the fans are really
>>> connected to the NCT6776, this may be a driver bug. BTW you said you're
>>> using the w83627ehf driver from groeck, but there is a better driver
>>> for the NCT6776 now:
>>> https://github.com/groeck/nct6775
>>> Guenter, maybe this driver should be listed at
>>> http://roeck-us.net/linux/drivers/
>>> so that users find it?
>>>
>>> If the new driver doesn't help, maybe the fans are connected to another
>>> monitoring chip.
>>>
>>>> Does the mean all the AMD FX CPU have the same issue? What to do? Is a
>>>> patch on the way?
>>> There's no relation between fan speed monitoring and the CPU your
>>> system is using.
>>>
>>>> Temperatures in the hardware area have a load of loose vocabulary.
>>>> I try to be accurate:
>>>> Could you confirm that CPUTIN is the temperature read by the sensor in
>>>> the socket of the motherboard called Tjunction?
>>> I don't think so. AFAIK Tjunction refers to a temperature limit inside
>>> the CPU, and it related to the digital thermal sensor in the CPU.
>>> CPUTIN OTOH is an analog thermal sensor. As it is a thermistor in your
>>> case, it is likely under the CPU, in the middle of the CPU socket.
>>>
>>>> Could you confirm that K10temp, temp1 is what AMD call Tctl (sliding
>>>> scale) accessible through D18F3xA4[CurTmp] register (from BIOS and
>>>> Kernel Developer's Guide)?
>>> Yes, this is correct.
>>>
>>>> Could you tell me what is SYSTIN (system temp input) and AUXTIN
>>>> (auxiliary temp input)?
>>> These are analog thermal sensor inputs. As already mentioned, AUXTIN is
>>> apparently not used on your board, you can ignore it. SYSTIN could be
>>> anywhere on the motherboard, we can't tell. Maybe the technical
>>> documentation for your board has the information.
>>>
>>>> Are they in the list bellow?
>>> I have no idea where this list comes from, so I can't really comment on
>>> that, sorry. Other than:
>>>
>>>> TJunction is the temperature where the pins hit the board
>>>>
>>>> TJunction is still a diode on the board, under the processor
>>> This is completely wrong. At least this is not what the rest of the
>>> world, starting with Intel technical documentation, refers to as
>>> Tjunction.
>>>
>> The new document version is now clear to understand and moreover we
>> know why we don't need the divisor in some chips.
>>
>> I installed the new driver. For around 15 minutes I had fan2 value
>> (about 1150 RPM).
>> I did some changes in the sensors3.conf file, then sensors -s, was OK.
>> After some try I have fan2 = 0 RPM. I did cold boot, reinstall
>> driver, reinstall lm-sensors, still 0 RPM.
>> I can't find why it's not working any more.
>> Any idea?
>>
> ASRock uses GPIO pins to multiplex multiple fan speed inputs to a single pin
> at the NCT6776. It might be that you somehow triggered or changed a multiplexer
> configuration.
>
> Do you see fan speed(s) in the BIOS ? If you do, it might well be that you have
> to do that once after powerup to connect a fan to the fan speed input of the
> NCT6776, and then you might see it in the driver.
>
> [ And, no, it is practically impossible to get the necessary information to set
> the GPIO multiplexer from the board vendor. AFAIK they are using GPIO pins,
> but which ones on which board is a mystery. ]
>
> Guenter
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
>
I have an ASRock 970 Extreme4 UEFI version P2.00
In the H/W Monitor page of the UEFI/BIOS, I have the following:
CPU Temperature : 36.5 °C
M/B Temperature : 28.0 °C
CPU Fan 1 Speed : 1065 RPM (this is a pwm connector with 4 pins. I
have a pwm fan) called CPU_FAN1 on the motherboard
CPU Fan 2 Speed : N/A (this is a 3 pins connector. No connected fan)
called CPU_FAN2 on the motherboard
Chassis Fan 1 Speed : N/A (this is a pwm connector with 4 pins. No
connected fan) called CHA_FAN1 on the motherboard
Chassis Fan 2 Speed : 730 RPM (this is a 3 pins connector. I have a 3
pins connected fan) called CHA_FAN2 on the motherboard
Chassis Fan 3 Speed : 760 RPM (this is a 3 pins connector. I have a 3
pins connected fan) called CHA_FAN3 on the motherboard
Power Fan Speed : N/A (this is a 3 pins connector. No connected fan)
called PWR_FAN1 on the motherboard
Vcore : +1.328 V
+ 12.00V : +12.144 V
+ 5.00V : +5.136 V
+ 3.30V : +3.280 V
lm-sensors has almost all the values but no fan speed.
I don't know why I had the CPU_FAN2 for a short time and it disappeared.
I can't understand what you suggest to have the value back. Could you be
more accurate?
Thanks
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (5 preceding siblings ...)
2012-09-16 6:44 ` Jean-Pierre Thibert
@ 2012-09-16 18:53 ` Guenter Roeck
2012-09-16 22:19 ` Guenter Roeck
` (9 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Guenter Roeck @ 2012-09-16 18:53 UTC (permalink / raw)
To: lm-sensors
On Sun, Sep 16, 2012 at 07:44:58AM +0100, Jean-Pierre Thibert wrote:
[ ... ]
> >
> >
> I have an ASRock 970 Extreme4 UEFI version P2.00
> In the H/W Monitor page of the UEFI/BIOS, I have the following:
> CPU Temperature : 36.5 °C
> M/B Temperature : 28.0 °C
>
> CPU Fan 1 Speed : 1065 RPM (this is a pwm connector with 4 pins.
> I have a pwm fan) called CPU_FAN1 on the motherboard
> CPU Fan 2 Speed : N/A (this is a 3 pins connector. No connected
> fan) called CPU_FAN2 on the motherboard
> Chassis Fan 1 Speed : N/A (this is a pwm connector with 4 pins.
> No connected fan) called CHA_FAN1 on the motherboard
> Chassis Fan 2 Speed : 730 RPM (this is a 3 pins connector. I have
> a 3 pins connected fan) called CHA_FAN2 on the motherboard
> Chassis Fan 3 Speed : 760 RPM (this is a 3 pins connector. I have
> a 3 pins connected fan) called CHA_FAN3 on the motherboard
> Power Fan Speed : N/A (this is a 3 pins connector. No connected
> fan) called PWR_FAN1 on the motherboard
>
> Vcore : +1.328 V
> + 12.00V : +12.144 V
> + 5.00V : +5.136 V
> + 3.30V : +3.280 V
>
> lm-sensors has almost all the values but no fan speed.
> I don't know why I had the CPU_FAN2 for a short time and it disappeared.
> I can't understand what you suggest to have the value back. Could
I did not suggest anything.
I found some information about the board. The chassis fans are connected to
memory mapped IO, so there is nothing we can do there. There are two CPU fans,
multiplexed to the SuperIO chip through GPIO pins. It _might be possible that
we can manually set those pins.
Please send the output of the following commands:
isadump -y -k 0x87,0x87 0x2e 0x2f
isadump -y -k 0x87,0x87 0x2e 0x2f 8
dmidecode
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (6 preceding siblings ...)
2012-09-16 18:53 ` Guenter Roeck
@ 2012-09-16 22:19 ` Guenter Roeck
2012-09-17 10:37 ` MrNice
` (8 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Guenter Roeck @ 2012-09-16 22:19 UTC (permalink / raw)
To: lm-sensors
On Sun, Sep 16, 2012 at 09:03:17PM +0100, Jean-Pierre Thibert wrote:
> On 16/09/12 19:53, Guenter Roeck wrote:
> >On Sun, Sep 16, 2012 at 07:44:58AM +0100, Jean-Pierre Thibert wrote:
> >[ ... ]
> >>>
> >>I have an ASRock 970 Extreme4 UEFI version P2.00
> >>In the H/W Monitor page of the UEFI/BIOS, I have the following:
> >>CPU Temperature : 36.5 °C
> >>M/B Temperature : 28.0 °C
> >>
> >>CPU Fan 1 Speed : 1065 RPM (this is a pwm connector with 4 pins.
> >>I have a pwm fan) called CPU_FAN1 on the motherboard
> >>CPU Fan 2 Speed : N/A (this is a 3 pins connector. No connected
> >>fan) called CPU_FAN2 on the motherboard
> >>Chassis Fan 1 Speed : N/A (this is a pwm connector with 4 pins.
> >>No connected fan) called CHA_FAN1 on the motherboard
> >>Chassis Fan 2 Speed : 730 RPM (this is a 3 pins connector. I have
> >>a 3 pins connected fan) called CHA_FAN2 on the motherboard
> >>Chassis Fan 3 Speed : 760 RPM (this is a 3 pins connector. I have
> >>a 3 pins connected fan) called CHA_FAN3 on the motherboard
> >>Power Fan Speed : N/A (this is a 3 pins connector. No connected
> >>fan) called PWR_FAN1 on the motherboard
> >>
> >>Vcore : +1.328 V
> >>+ 12.00V : +12.144 V
> >>+ 5.00V : +5.136 V
> >>+ 3.30V : +3.280 V
> >>
> >>lm-sensors has almost all the values but no fan speed.
> >>I don't know why I had the CPU_FAN2 for a short time and it disappeared.
> >>I can't understand what you suggest to have the value back. Could
> >I did not suggest anything.
> >
> >I found some information about the board. The chassis fans are connected to
> >memory mapped IO, so there is nothing we can do there. There are two CPU fans,
> >multiplexed to the SuperIO chip through GPIO pins. It _might be possible that
> >we can manually set those pins.
> >
> >Please send the output of the following commands:
> > isadump -y -k 0x87,0x87 0x2e 0x2f
> > isadump -y -k 0x87,0x87 0x2e 0x2f 8
> > dmidecode
> >
> >Thanks,
> >Guenter
> >
> >
> >
> >
> sudo isadump -y -k 0x87,0x87 0x2e 0x2f
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: ff ff 00 ff ff ff ff 0b ff ff ff ff ff ff ff ff
> 10: ff ff ff ff ff ff ff ff ff ff f8 ce 00 00 ff ff
> 20: c3 33 ff 00 5c 00 00 90 00 ff 60 04 81 00 00 01
> 30: e1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 60: 02 90 00 00 ff ff ff ff ff ff ff ff ff ff ff ff
> 70: 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> e0: 7f 7f ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> f0: 00 00 00 a4 ff 10 00 87 47 00 00 ff ff ff ff ff
>
>
> sudo isadump -y -k 0x87,0x87 0x2e 0x2f 8
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: ff ff 00 ff ff ff ff 08 ff ff ff ff ff ff ff ff
> 10: ff ff ff ff ff ff ff ff ff ff f8 ce 00 00 ff ff
> 20: c3 33 ff 00 5c 00 00 90 00 ff 60 04 81 00 00 01
> 30: 01 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 60: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> f0: f3 f3 00 ff 00 00 00 00 ff ff ff ff ff ff ff ff
>
I just noticed that you dropped the mailing list in your reply.
Please don't do that; others may need the information later on,
and I myself use it for searches.
I initially thought the above does not help, but it kind of makes sense.
You can try the following command sequence (at your own risk):
isaset -y -f 0x2e 0x87
isaset -y -f 0x2e 0x87
isaset -y 0x2e 0x2f 0x7 0x8
isaset -y 0x2e 0x2f 0xf0 0xb2
isaset -y 0x2e 0x2f 0xf1 0xb3
The 0xb3 in the last command should select CPUFANIN. Replace it with 0xf2 to
select CPUFANIN2.
You'll have to copy the commands into a file and execute it as shell script.
Do _not_ play with other settings of register 0xf0 or 0xf1. The information
in the ASRock tool suggests that one of the bits is used to control the DDR3
voltage.
Guenter
> sudo dmidecode
> # dmidecode 2.11
> SMBIOS 2.6 present.
> 28 structures occupying 1531 bytes.
> Table at 0x000EF110.
>
> Handle 0x0001, DMI type 1, 27 bytes
> System Information
> Manufacturer: To Be Filled By O.E.M.
> Product Name: To Be Filled By O.E.M.
> Version: To Be Filled By O.E.M.
> Serial Number: To Be Filled By O.E.M.
> UUID: 03000200-0400-0500-0006-000700080009
> Wake-up Type: Power Switch
> SKU Number: To Be Filled By O.E.M.
> Family: To Be Filled By O.E.M.
>
> Handle 0x0002, DMI type 2, 15 bytes
> Base Board Information
> Manufacturer: ASRock
> Product Name: 970 Extreme4
> Version:
> Serial Number:
> Asset Tag:
> Features:
> Board is a hosting board
> Board is replaceable
> Location In Chassis:
> Chassis Handle: 0x0003
> Type: Motherboard
> Contained Object Handles: 0
>
> Handle 0x0003, DMI type 3, 21 bytes
> Chassis Information
> Manufacturer: To Be Filled By O.E.M.
> Type: Desktop
> Lock: Not Present
> Version: To Be Filled By O.E.M.
> Serial Number: To Be Filled By O.E.M.
> Asset Tag: To Be Filled By O.E.M.
> Boot-up State: Safe
> Power Supply State: Safe
> Thermal State: Safe
> Security Status: None
> OEM Information: 0x00000000
> Height: Unspecified
> Number Of Power Cords: 1
> Contained Elements: 0
>
> Handle 0x0004, DMI type 4, 42 bytes
> Processor Information
> Socket Designation: CPUSocket
> Type: Central Processor
> Family: <OUT OF SPEC>
> Manufacturer: AMD
> ID: 12 0F 60 00 FF FB 8B 17
> Version: AMD FX(tm)-8120 Eight-Core Processor
> Voltage: 1.4 V
> External Clock: 200 MHz
> Max Speed: 3100 MHz
> Current Speed: 3100 MHz
> Status: Populated, Enabled
> Upgrade: Socket AM3
> L1 Cache Handle: 0x0005
> L2 Cache Handle: 0x0006
> L3 Cache Handle: 0x0007
> Serial Number: To Be Filled By O.E.M.
> Asset Tag: To Be Filled By O.E.M.
> Part Number: To Be Filled By O.E.M.
> Core Count: 8
> Core Enabled: 8
> Thread Count: 8
> Characteristics:
> 64-bit capable
>
> Handle 0x0005, DMI type 7, 19 bytes
> Cache Information
> Socket Designation: L1-Cache
> Configuration: Enabled, Not Socketed, Level 1
> Operational Mode: Write Back
> Location: Internal
> Installed Size: 384 kB
> Maximum Size: 384 kB
> Supported SRAM Types:
> Pipeline Burst
> Installed SRAM Type: Pipeline Burst
> Speed: 1 ns
> Error Correction Type: Multi-bit ECC
> System Type: Unified
> Associativity: 2-way Set-associative
>
> Handle 0x0006, DMI type 7, 19 bytes
> Cache Information
> Socket Designation: L2-Cache
> Configuration: Enabled, Not Socketed, Level 2
> Operational Mode: Write Back
> Location: Internal
> Installed Size: 8192 kB
> Maximum Size: 8192 kB
> Supported SRAM Types:
> Pipeline Burst
> Installed SRAM Type: Pipeline Burst
> Speed: 1 ns
> Error Correction Type: Multi-bit ECC
> System Type: Unified
> Associativity: 16-way Set-associative
>
> Handle 0x0007, DMI type 7, 19 bytes
> Cache Information
> Socket Designation: L3-Cache
> Configuration: Enabled, Not Socketed, Level 3
> Operational Mode: Write Back
> Location: Internal
> Installed Size: 8192 kB
> Maximum Size: 8192 kB
> Supported SRAM Types:
> Pipeline Burst
> Installed SRAM Type: Pipeline Burst
> Speed: 1 ns
> Error Correction Type: Multi-bit ECC
> System Type: Unified
> Associativity: 64-way Set-associative
>
> Handle 0x0008, DMI type 9, 17 bytes
> System Slot Information
> Designation: PCI1
> Type: 32-bit PCI
> Current Usage: In Use
> Length: Short
> ID: 1
> Characteristics:
> 3.3 V is provided
> Opening is shared
> PME signal is supported
>
> Handle 0x0009, DMI type 9, 17 bytes
> System Slot Information
> Designation: PCI2
> Type: 32-bit PCI
> Current Usage: In Use
> Length: Short
> ID: 2
> Characteristics:
> 3.3 V is provided
> Opening is shared
> PME signal is supported
>
> Handle 0x000A, DMI type 9, 17 bytes
> System Slot Information
> Designation: PCIE1
> Type: x1 PCI Express
> Current Usage: In Use
> Length: Short
> ID: 17
> Characteristics:
> 3.3 V is provided
> Opening is shared
> PME signal is supported
> Bus Address: 0000:00:0f.0
>
> Handle 0x000B, DMI type 9, 17 bytes
> System Slot Information
> Designation: PCIE2
> Type: x16 PCI Express
> Current Usage: In Use
> Length: Short
> ID: 18
> Characteristics:
> 3.3 V is provided
> Opening is shared
> PME signal is supported
> Bus Address: 0000:00:02.0
>
> Handle 0x000C, DMI type 9, 17 bytes
> System Slot Information
> Designation: PCIE3
> Type: x1 PCI Express
> Current Usage: In Use
> Length: Short
> ID: 19
> Characteristics:
> 3.3 V is provided
> Opening is shared
> PME signal is supported
> Bus Address: 0000:00:0f.1
>
> Handle 0x000D, DMI type 9, 17 bytes
> System Slot Information
> Designation: PCIE4
> Type: x16 PCI Express
> Current Usage: In Use
> Length: Short
> ID: 20
> Characteristics:
> 3.3 V is provided
> Opening is shared
> PME signal is supported
> Bus Address: 0000:00:0b.0
>
> Handle 0x000E, DMI type 9, 17 bytes
> System Slot Information
> Designation: PCIE5
> Type: x4 PCI Express
> Current Usage: In Use
> Length: Short
> ID: 21
> Characteristics:
> 3.3 V is provided
> Opening is shared
> PME signal is supported
> Bus Address: 0000:00:0d.0
>
> Handle 0x000F, DMI type 11, 5 bytes
> OEM Strings
> String 1: To Be Filled By O.E.M.
>
> Handle 0x0010, DMI type 16, 15 bytes
> Physical Memory Array
> Location: System Board Or Motherboard
> Use: System Memory
> Error Correction Type: None
> Maximum Capacity: 32 GB
> Error Information Handle: Not Provided
> Number Of Devices: 4
>
> Handle 0x0011, DMI type 19, 15 bytes
> Memory Array Mapped Address
> Starting Address: 0x00000000000
> Ending Address: 0x0021F0003FF
> Range Size: 8688 MB
> Physical Array Handle: 0x0010
> Partition Width: 255
>
> Handle 0x0012, DMI type 17, 28 bytes
> Memory Device
> Array Handle: 0x0010
> Error Information Handle: Not Provided
> Total Width: Unknown
> Data Width: 64 bits
> Size: No Module Installed
> Form Factor: DIMM
> Set: None
> Locator: A1_DIMM0
> Bank Locator: A1_BANK0
> Type: Unknown
> Type Detail: Synchronous
> Speed: Unknown
> Manufacturer: A1_Manufacturer0
> Serial Number: A1_SerNum0
> Asset Tag: A1_AssetTagNum0
> Part Number: Array1_PartNumber0
> Rank: Unknown
>
> Handle 0x0013, DMI type 126, 19 bytes
> Inactive
>
> Handle 0x0014, DMI type 17, 28 bytes
> Memory Device
> Array Handle: 0x0010
> Error Information Handle: Not Provided
> Total Width: 64 bits
> Data Width: 64 bits
> Size: 4096 MB
> Form Factor: DIMM
> Set: None
> Locator: A1_DIMM1
> Bank Locator: A1_BANK1
> Type: DDR3
> Type Detail: Synchronous
> Speed: 667 MHz
> Manufacturer: Corsair
> Serial Number: 00000000
> Asset Tag: A1_AssetTagNum1
> Part Number: CMZ8GX3M2A1600C9
> Rank: 2
>
> Handle 0x0015, DMI type 20, 19 bytes
> Memory Device Mapped Address
> Starting Address: 0x00000000000
> Ending Address: 0x000FFFFFFFF
> Range Size: 4 GB
> Physical Device Handle: 0x0014
> Memory Array Mapped Address Handle: 0x0011
> Partition Row Position: 1
>
> Handle 0x0016, DMI type 17, 28 bytes
> Memory Device
> Array Handle: 0x0010
> Error Information Handle: Not Provided
> Total Width: Unknown
> Data Width: 64 bits
> Size: No Module Installed
> Form Factor: DIMM
> Set: None
> Locator: A1_DIMM2
> Bank Locator: A1_BANK2
> Type: Unknown
> Type Detail: Synchronous
> Speed: Unknown
> Manufacturer: A1_Manufacturer2
> Serial Number: A1_SerNum2
> Asset Tag: A1_AssetTagNum2
> Part Number: Array1_PartNumber2
> Rank: Unknown
>
> Handle 0x0017, DMI type 126, 19 bytes
> Inactive
>
> Handle 0x0018, DMI type 17, 28 bytes
> Memory Device
> Array Handle: 0x0010
> Error Information Handle: Not Provided
> Total Width: 64 bits
> Data Width: 64 bits
> Size: 4096 MB
> Form Factor: DIMM
> Set: None
> Locator: A1_DIMM3
> Bank Locator: A1_BANK3
> Type: DDR3
> Type Detail: Synchronous
> Speed: 667 MHz
> Manufacturer: Corsair
> Serial Number: 00000000
> Asset Tag: A1_AssetTagNum3
> Part Number: CMZ8GX3M2A1600C9
> Rank: 2
>
> Handle 0x0019, DMI type 20, 19 bytes
> Memory Device Mapped Address
> Starting Address: 0x00100000000
> Ending Address: 0x001FFFFFFFF
> Range Size: 4 GB
> Physical Device Handle: 0x0018
> Memory Array Mapped Address Handle: 0x0011
> Partition Row Position: 1
>
> Handle 0x001A, DMI type 32, 20 bytes
> System Boot Information
> Status: No errors detected
>
> Handle 0x0000, DMI type 0, 24 bytes
> BIOS Information
> Vendor: American Megatrends Inc.
> Version: P2.00
> Release Date: 08/30/2012
> Address: 0xF0000
> Runtime Size: 64 kB
> ROM Size: 4096 kB
> Characteristics:
> PCI is supported
> BIOS is upgradeable
> BIOS shadowing is allowed
> Boot from CD is supported
> Selectable boot is supported
> BIOS ROM is socketed
> EDD is supported
> 5.25"/1.2 MB floppy services are supported (int 13h)
> 3.5"/720 kB floppy services are supported (int 13h)
> 3.5"/2.88 MB floppy services are supported (int 13h)
> Print screen service is supported (int 5h)
> 8042 keyboard services are supported (int 9h)
> Serial services are supported (int 14h)
> Printer services are supported (int 17h)
> ACPI is supported
> USB legacy is supported
> BIOS boot specification is supported
> Targeted content distribution is supported
> BIOS Revision: 4.6
>
> Handle 0x001B, DMI type 127, 4 bytes
> End Of Table
>
>
> Many thanks for you help.
> Don't hesitate to ask me more info if needed
>
> Jean-Pierre
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (7 preceding siblings ...)
2012-09-16 22:19 ` Guenter Roeck
@ 2012-09-17 10:37 ` MrNice
2012-09-17 10:51 ` MrNice
` (7 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: MrNice @ 2012-09-17 10:37 UTC (permalink / raw)
To: lm-sensors
On Sun, Sep 16, 2012 at 09:03:17PM +0100, Jean-Pierre Thibert wrote:
> On 16/09/12 19:53, Guenter Roeck wrote:
> >On Sun, Sep 16, 2012 at 07:44:58AM +0100, Jean-Pierre Thibert wrote:
> >[ ... ]
> >>>
> >>I have an ASRock 970 Extreme4 UEFI version P2.00
> >>In the H/W Monitor page of the UEFI/BIOS, I have the following:
> >>CPU Temperature : 36.5 °C
> >>M/B Temperature : 28.0 °C
> >>
> >>CPU Fan 1 Speed : 1065 RPM (this is a pwm connector with 4 pins.
> >>I have a pwm fan) called CPU_FAN1 on the motherboard
> >>CPU Fan 2 Speed : N/A (this is a 3 pins connector. No connected
> >>fan) called CPU_FAN2 on the motherboard
> >>Chassis Fan 1 Speed : N/A (this is a pwm connector with 4 pins.
> >>No connected fan) called CHA_FAN1 on the motherboard
> >>Chassis Fan 2 Speed : 730 RPM (this is a 3 pins connector. I have
> >>a 3 pins connected fan) called CHA_FAN2 on the motherboard
> >>Chassis Fan 3 Speed : 760 RPM (this is a 3 pins connector. I have
> >>a 3 pins connected fan) called CHA_FAN3 on the motherboard
> >>Power Fan Speed : N/A (this is a 3 pins connector. No connected
> >>fan) called PWR_FAN1 on the motherboard
> >>
> >>Vcore : +1.328 V
> >>+ 12.00V : +12.144 V
> >>+ 5.00V : +5.136 V
> >>+ 3.30V : +3.280 V
> >>
> >>lm-sensors has almost all the values but no fan speed.
> >>I don't know why I had the CPU_FAN2 for a short time and it disappeared.
> >>I can't understand what you suggest to have the value back. Could
> >I did not suggest anything.
> >
> >I found some information about the board. The chassis fans are connected to
> >memory mapped IO, so there is nothing we can do there. There are two CPU fans,
> >multiplexed to the SuperIO chip through GPIO pins. It _might be possible that
> >we can manually set those pins.
> >
> >Please send the output of the following commands:
> > isadump -y -k 0x87,0x87 0x2e 0x2f
> > isadump -y -k 0x87,0x87 0x2e 0x2f 8
> > dmidecode
> >
> >Thanks,
> >Guenter
> >
> >
> >
> >
> sudo isadump -y -k 0x87,0x87 0x2e 0x2f
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: ff ff 00 ff ff ff ff 0b ff ff ff ff ff ff ff ff
> 10: ff ff ff ff ff ff ff ff ff ff f8 ce 00 00 ff ff
> 20: c3 33 ff 00 5c 00 00 90 00 ff 60 04 81 00 00 01
> 30: e1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 60: 02 90 00 00 ff ff ff ff ff ff ff ff ff ff ff ff
> 70: 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> e0: 7f 7f ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> f0: 00 00 00 a4 ff 10 00 87 47 00 00 ff ff ff ff ff
>
>
> sudo isadump -y -k 0x87,0x87 0x2e 0x2f 8
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: ff ff 00 ff ff ff ff 08 ff ff ff ff ff ff ff ff
> 10: ff ff ff ff ff ff ff ff ff ff f8 ce 00 00 ff ff
> 20: c3 33 ff 00 5c 00 00 90 00 ff 60 04 81 00 00 01
> 30: 01 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 60: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> f0: f3 f3 00 ff 00 00 00 00 ff ff ff ff ff ff ff ff
>
Not good :(. The problem is "30: 01" above; it suggests that the SuperIO GPIO pins
which I thought would be used to control the fan multiplexer are in fact disabled.
One more try ... please download superiotool fromhttp://roeck-us.net/linux/bin/superiotool
and run it with "sudo ./superiotool -d -e".
If you don't want to run untrusted binaries, please clone the latest version
of coreboot (git clonehttp://review.coreboot.org/p/coreboot) and build and run
superiotool from it (cd util/superiotool; make; sudo ./superiotool -d -e).
Thanks,
Guenter
sudo ./superiotool -d -e
superiotool r4.0-2514-gf419483
Found Nuvoton NCT6776F (C) (id=0xc333) at 0x2e
Register dump:
idx 10 11 13 14 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 2a 2b 2c 2d 2e 2f
val ff ff ff ff ff ff ff ff f8 ce 00 00 ff ff c3 33 ff 00 5c 00 00 90 00 60 04 81 00 00 01
def ff ff 00 00 ff ff ff ff f0 78 00 00 ff ff c3 33 ff 00 64 00 MM 00 00 c0 00 81 00 00 MM
LDN 0x00 (FDC)
idx 30 60 61 70 74 f0 f1 f2 f4 f5
val 00 03 f0 06 02 0e 00 ff 00 00
def 01 03 f0 06 02 0e 00 ff 00 00
LDN 0x01 (Parallel Port)
idx 30 60 61 70 74 f0
val 00 03 78 07 04 3f
def 01 03 78 07 04 3f
LDN 0x02 (UART A)
idx 30 60 61 70 f0 f2
val 00 03 f8 04 00 00
def 01 03 f8 04 00 00
LDN 0x03 (UART B, IR)
idx 30 60 61 70 f0 f1 f2
val 00 02 f8 03 00 00 00
def 01 02 f8 03 00 00 00
LDN 0x05 (Keyboard Controller)
idx 30 60 61 62 63 70 72 f0
val 01 00 60 00 64 01 0c 83
def 00 00 00 00 00 00 00 83
LDN 0x06 (CIR)
idx 30 60 61 70 f0 f1 f2 f3
val 00 00 00 00 08 09 32 00
def 00 00 00 00 08 09 32 00
LDN 0x07 (GPIO6, GPIO7, GPIO8, GPIO9)
idx 30 e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ec ed ee f4 f5 f6 f7 f8
val 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
def 03 ff 00 00 00 ef 00 00 00 ff 00 00 00 00 00 00 ff 00 00 00 00
LDN 0x08 (WDT1, GPIO0, GPIO1, GPIOA)
idx 30 60 61 e0 e1 e2 e3 e4 f0 f1 f2 f3 f4 f5 f6 f7
val 01 00 00 ff ff ff ff ff f3 f3 00 f3 00 00 00 00
def 02 00 00 ff 00 00 00 ef ff 00 00 00 00 00 00 00
LDN 0x09 (GPIO2, GPIO3, GPIO4, GPIO5)
idx 30 e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 ea eb ee f0 f1 f2 f4 f5 f6 f7 fe
val 36 ff 00 00 00 ff ff ff ff 4c 00 ff 00 00 ff 0c 00 ff 00 00 00 00
def 04 df 00 00 00 ff 00 00 00 00 00 00 00 00 ff 00 00 ff 00 00 00 00
LDN 0x0a (ACPI)
idx e0 e1 e2 e3 e4 e5 e6 e7 e9 ee f0 f2 f3 f4 f6 f7 fe
val 01 00 00 05 00 02 4c 00 00 00 00 5c 00 00 00 c0 00
def 01 00 00 00 00 02 1c 00 00 00 00 00 00 00 00 c0 00
LDN 0x0b (Hardware Monitor, Front Panel LED)
idx 30 60 61 62 63 70 e0 e1 e2 f0 f1 f2 f5 f6 f7 f8 f9 fa
val e1 02 90 00 00 00 7f 7f ff 00 00 00 10 00 87 47 00 00
def 00 00 00 00 00 00 7f 7f ff 00 00 00 10 00 87 47 00 00
LDN 0x0d (VID)
idx e0 e1 e2 e3 e4 e5 e6 e9 ee ef f0 f4 f5
val 00 00 00 00 00 00 00 00 88 00 00 00 00
def 00 00 00 00 00 00 00 00 88 00 00 00 00
LDN 0x0e (CIR WAKE-UP)
idx 30 60 61 70
val 00 00 00 00
def 00 00 00 00
LDN 0x0f (GPIO Push-Pull or Open-drain)
idx e0 e1 e2 e3 e4 e5 e6 e7 e8 e9 f0 f1 f2
val ff df ff fe f6 ff ff d3 ff 9f 00 00 00
def ff df ff fe f6 ff ff d3 ff 9f 00 00 00
LDN 0x14 (SVID)
idx e0 e1 e3 e4
val 00 80 00 00
def 00 80 00 00
LDN 0x16 (Deep Sleep)
idx 30 e0 e1 e2
val 20 20 04 05
def 20 20 04 05
LDN 0x17 (GPIOA)
idx e0 e1 e2 e3 e4 e5
val ff ff ff ff 01 ff
def 01 00 00 00 01 00
Bank 0:
00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
00: 04 ff 04 c0 00 ff ff ff ff ff ff ff ff ff ff ff
01: 04 ff 00 00 00 00 ff ff 40 00 00 00 00 00 00 00
02: 72 e7 cf ce 03 d6 03 1c ff ff ff da 00 00 00 e3
03: ba e3 ba 00 00 00 00 00 00 00 00 ff ff ff ff ff
04: 03 de 30 ff ff 00 3f ff 2d ff ff ff 08 05 00 a3
05: ff ff ff ff ff ff ff ff c1 ff ff ff ff 01 00 ff
06: cf ff ff ff ff 01 00 ff ff ff ff ff ff ff ff ff
07: 00 0a 00 1c 80 1a 00 7f 80 ff ff ff ff ff ff ff
08: ff 03 1f 0f ff 3c 3c 3c 00 00 00 00 00 00 00 00
09: 0a 00 00 00 00 0a 0a 0a 0a aa ef 80 ff 40 46 c4
0a: 0e 01 00 00 ff 00 00 ff 00 00 80 66 66 06 00 01
0b: 00 00 00 00 00 00 27 00 1c 00 00 34 28 c0 c4 ff
0c: 01 00 00 00 00 00 00 00 00 08 01 ff ff ff ff ff
0d: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Bank 1:
00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
00: 01 00 00 0a 0a 01 01 3c ff ff ff ff 00 ff ff ff
01: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
02: 00 19 23 2d 37 ff ff 8c aa c8 e6 ff ff ff ff ff
03: ff 00 ff ff 00 7f ff ff 00 01 00 00 00 00 00 00
04: ff ff ff ff ff a4 00 ff ff ff ff ff ff ff 01 ff
05: 1a 00 00 4b 00 50 00 ff ff ff ff ff ff ff ff ff
06: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
07: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
08: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0b: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Bank 2:
00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
00: 82 2d 12 0a 0a c0 ff 60 ff c0 ff ff 00 ff ff ff
01: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
02: 00 28 32 3c 46 ff ff 8c aa c8 e6 ff ff ff ff ff
03: ff 00 ff ff 00 7f ff ff 00 01 00 00 00 00 00 00
04: ff ff ff ff ff a4 00 ff ff ff ff ff ff ff 02 ff
05: 7f 80 00 72 00 72 00 ff ff ff ff ff ff ff ff ff
06: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
07: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
08: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0b: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Bank 3:
00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
00: 03 00 00 0a 0a 01 01 3c ff ff ff ff 00 ff ff ff
01: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
02: 00 19 23 2d 37 ff ff 8c aa c8 e6 ff ff ff ff ff
03: ff 00 ff ff 00 3c ff ff 00 01 00 00 00 00 00 00
04: ff ff ff ff ff a4 00 ff ff ff ff ff ff ff 03 ff
05: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
06: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
07: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
08: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0b: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Bank 4:
00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01: 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff
02: ff ff ff 96 64 96 64 e1 96 ff ff ff ff ff ff ff
03: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
04: 3f 00 03 ff ff ff ff ff ff ff ff ff ff ff 04 ff
05: 33 13 ff ff 00 00 00 ff 00 d2 3b b2 09 ff ff ff
06: ff 01 00 00 00 00 00 00 ff ff ff ff ff ff ff ff
07: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
08: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0b: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Bank 5:
00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
00: ff ff 00 00 00 00 ff ff ff ff ff ff ff 00 00 ff
01: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
02: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
03: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
04: ff ff ff ff ff ff ff ff ff ff ff ff ff ff 05 ff
05: d8 d1 80 ff e3 ba ce a9 ff ff ff ff ff ff ff ff
06: 00 00 00 00 00 00 07 00 00 ff ff ff ff ff ff ff
07: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
08: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0b: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Bank 6:
00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
00: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
01: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
02: ff 01 02 03 01 01 01 ff 00 00 00 1c 1c 1c 07 ff
03: ff 1f ff 1f ff 1f ff 1f ff 1f 00 00 00 00 00 00
04: ff 1f 00 00 02 02 02 ff ff ff ff ff ff ff 06 ff
05: 7f 7f 7f 7f 7f 7f 00 a4 00 a4 00 a4 00 a4 00 a4
06: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
07: 7f 7f 50 4b 04 7f 7f 50 4b 04 7f 7f 50 4b 04 ff
08: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0b: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Bank 7:
00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
00: ff 10 02 00 00 00 00 00 00 00 00 00 00 00 00 00
01: 00 00 00 00 00 00 00 f8 80 f8 80 f8 80 f8 80 00
02: 28 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03: 00 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff
04: ff ff ff ff ff ff ff ff ff ff ff ff ff ff 07 ff
05: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
06: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
07: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
08: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
09: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0a: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0b: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0c: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0d: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0e: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0f: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (8 preceding siblings ...)
2012-09-17 10:37 ` MrNice
@ 2012-09-17 10:51 ` MrNice
2012-09-17 15:14 ` Guenter Roeck
` (6 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: MrNice @ 2012-09-17 10:51 UTC (permalink / raw)
To: lm-sensors
On Sun, Sep 16, 2012 at 09:03:17PM +0100, Jean-Pierre Thibert wrote:
> On 16/09/12 19:53, Guenter Roeck wrote:
> >On Sun, Sep 16, 2012 at 07:44:58AM +0100, Jean-Pierre Thibert wrote:
> >[ ... ]
> >>>
> >>I have an ASRock 970 Extreme4 UEFI version P2.00
> >>In the H/W Monitor page of the UEFI/BIOS, I have the following:
> >>CPU Temperature : 36.5 °C
> >>M/B Temperature : 28.0 °C
> >>
> >>CPU Fan 1 Speed : 1065 RPM (this is a pwm connector with 4 pins.
> >>I have a pwm fan) called CPU_FAN1 on the motherboard
> >>CPU Fan 2 Speed : N/A (this is a 3 pins connector. No connected
> >>fan) called CPU_FAN2 on the motherboard
> >>Chassis Fan 1 Speed : N/A (this is a pwm connector with 4 pins.
> >>No connected fan) called CHA_FAN1 on the motherboard
> >>Chassis Fan 2 Speed : 730 RPM (this is a 3 pins connector. I have
> >>a 3 pins connected fan) called CHA_FAN2 on the motherboard
> >>Chassis Fan 3 Speed : 760 RPM (this is a 3 pins connector. I have
> >>a 3 pins connected fan) called CHA_FAN3 on the motherboard
> >>Power Fan Speed : N/A (this is a 3 pins connector. No connected
> >>fan) called PWR_FAN1 on the motherboard
> >>
> >>Vcore : +1.328 V
> >>+ 12.00V : +12.144 V
> >>+ 5.00V : +5.136 V
> >>+ 3.30V : +3.280 V
> >>
> >>lm-sensors has almost all the values but no fan speed.
> >>I don't know why I had the CPU_FAN2 for a short time and it disappeared.
> >>I can't understand what you suggest to have the value back. Could
> >I did not suggest anything.
> >
> >I found some information about the board. The chassis fans are connected to
> >memory mapped IO, so there is nothing we can do there. There are two CPU fans,
> >multiplexed to the SuperIO chip through GPIO pins. It _might be possible that
> >we can manually set those pins.
> >
> >Please send the output of the following commands:
> > isadump -y -k 0x87,0x87 0x2e 0x2f
> > isadump -y -k 0x87,0x87 0x2e 0x2f 8
> > dmidecode
> >
> >Thanks,
> >Guenter
> >
> >
> >
> >
> sudo isadump -y -k 0x87,0x87 0x2e 0x2f
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: ff ff 00 ff ff ff ff 0b ff ff ff ff ff ff ff ff
> 10: ff ff ff ff ff ff ff ff ff ff f8 ce 00 00 ff ff
> 20: c3 33 ff 00 5c 00 00 90 00 ff 60 04 81 00 00 01
> 30: e1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 60: 02 90 00 00 ff ff ff ff ff ff ff ff ff ff ff ff
> 70: 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> e0: 7f 7f ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> f0: 00 00 00 a4 ff 10 00 87 47 00 00 ff ff ff ff ff
>
>
> sudo isadump -y -k 0x87,0x87 0x2e 0x2f 8
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: ff ff 00 ff ff ff ff 08 ff ff ff ff ff ff ff ff
> 10: ff ff ff ff ff ff ff ff ff ff f8 ce 00 00 ff ff
> 20: c3 33 ff 00 5c 00 00 90 00 ff 60 04 81 00 00 01
> 30: 01 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 60: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> f0: f3 f3 00 ff 00 00 00 00 ff ff ff ff ff ff ff ff
>
I just noticed that you dropped the mailing list in your reply.
Please don't do that; others may need the information later on,
and I myself use it for searches.
I initially thought the above does not help, but it kind of makes sense.
You can try the following command sequence (at your own risk):
isaset -y -f 0x2e 0x87
isaset -y -f 0x2e 0x87
isaset -y 0x2e 0x2f 0x7 0x8
isaset -y 0x2e 0x2f 0xf0 0xb2
isaset -y 0x2e 0x2f 0xf1 0xb3
The 0xb3 in the last command should select CPUFANIN. Replace it with 0xf2 to
select CPUFANIN2.
You'll have to copy the commands into a file and execute it as shell script.
Do _not_ play with other settings of register 0xf0 or 0xf1. The information
in the ASRock tool suggests that one of the bits is used to control the DDR3
voltage.
Guenter
I am a bit afraid with "(at your own risk):"
Do I really need to do that?
Could you check again the hexa values to be sure.
The last command I have to add should be:
isaset -y 0x2e 0x2f 0xf1 0xf2
yes?
What will I to do after that? directly run sensors or something else?
Sorry for my hesitation.
JP
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (9 preceding siblings ...)
2012-09-17 10:51 ` MrNice
@ 2012-09-17 15:14 ` Guenter Roeck
2012-09-17 17:19 ` MrNice
` (5 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Guenter Roeck @ 2012-09-17 15:14 UTC (permalink / raw)
To: lm-sensors
On Mon, Sep 17, 2012 at 11:51:08AM +0100, MrNice wrote:
> On Sun, Sep 16, 2012 at 09:03:17PM +0100, Jean-Pierre Thibert wrote:
> >On 16/09/12 19:53, Guenter Roeck wrote:
> >>On Sun, Sep 16, 2012 at 07:44:58AM +0100, Jean-Pierre Thibert wrote:
> >>[ ... ]
> >>>>
> >>>I have an ASRock 970 Extreme4 UEFI version P2.00
> >>>In the H/W Monitor page of the UEFI/BIOS, I have the following:
> >>>CPU Temperature : 36.5 °C
> >>>M/B Temperature : 28.0 °C
> >>>
> >>>CPU Fan 1 Speed : 1065 RPM (this is a pwm connector with 4 pins.
> >>>I have a pwm fan) called CPU_FAN1 on the motherboard
> >>>CPU Fan 2 Speed : N/A (this is a 3 pins connector. No connected
> >>>fan) called CPU_FAN2 on the motherboard
> >>>Chassis Fan 1 Speed : N/A (this is a pwm connector with 4 pins.
> >>>No connected fan) called CHA_FAN1 on the motherboard
> >>>Chassis Fan 2 Speed : 730 RPM (this is a 3 pins connector. I have
> >>>a 3 pins connected fan) called CHA_FAN2 on the motherboard
> >>>Chassis Fan 3 Speed : 760 RPM (this is a 3 pins connector. I have
> >>>a 3 pins connected fan) called CHA_FAN3 on the motherboard
> >>>Power Fan Speed : N/A (this is a 3 pins connector. No connected
> >>>fan) called PWR_FAN1 on the motherboard
> >>>
> >>>Vcore : +1.328 V
> >>>+ 12.00V : +12.144 V
> >>>+ 5.00V : +5.136 V
> >>>+ 3.30V : +3.280 V
> >>>
> >>>lm-sensors has almost all the values but no fan speed.
> >>>I don't know why I had the CPU_FAN2 for a short time and it disappeared.
> >>>I can't understand what you suggest to have the value back. Could
> >>I did not suggest anything.
> >>
> >>I found some information about the board. The chassis fans are connected to
> >>memory mapped IO, so there is nothing we can do there. There are two CPU fans,
> >>multiplexed to the SuperIO chip through GPIO pins. It _might be possible that
> >>we can manually set those pins.
> >>
> >>Please send the output of the following commands:
> >> isadump -y -k 0x87,0x87 0x2e 0x2f
> >> isadump -y -k 0x87,0x87 0x2e 0x2f 8
> >> dmidecode
> >>
> >>Thanks,
> >>Guenter
> >>
> >>
> >>
> >>
> >sudo isadump -y -k 0x87,0x87 0x2e 0x2f
> > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> >00: ff ff 00 ff ff ff ff 0b ff ff ff ff ff ff ff ff
> >10: ff ff ff ff ff ff ff ff ff ff f8 ce 00 00 ff ff
> >20: c3 33 ff 00 5c 00 00 90 00 ff 60 04 81 00 00 01
> >30: e1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >60: 02 90 00 00 ff ff ff ff ff ff ff ff ff ff ff ff
> >70: 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >e0: 7f 7f ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >f0: 00 00 00 a4 ff 10 00 87 47 00 00 ff ff ff ff ff
> >
> >
> >sudo isadump -y -k 0x87,0x87 0x2e 0x2f 8
> > 0 1 2 3 4 5 6 7 8 9 a b c d e f
> >00: ff ff 00 ff ff ff ff 08 ff ff ff ff ff ff ff ff
> >10: ff ff ff ff ff ff ff ff ff ff f8 ce 00 00 ff ff
> >20: c3 33 ff 00 5c 00 00 90 00 ff 60 04 81 00 00 01
> >30: 01 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >60: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >f0: f3 f3 00 ff 00 00 00 00 ff ff ff ff ff ff ff ff
> >
>
> I just noticed that you dropped the mailing list in your reply.
> Please don't do that; others may need the information later on,
> and I myself use it for searches.
>
> I initially thought the above does not help, but it kind of makes sense.
>
> You can try the following command sequence (at your own risk):
>
> isaset -y -f 0x2e 0x87
> isaset -y -f 0x2e 0x87
> isaset -y 0x2e 0x2f 0x7 0x8
> isaset -y 0x2e 0x2f 0xf0 0xb2
> isaset -y 0x2e 0x2f 0xf1 0xb3
>
> The 0xb3 in the last command should select CPUFANIN. Replace it with 0xf2 to
> select CPUFANIN2.
>
> You'll have to copy the commands into a file and execute it as shell script.
>
> Do _not_ play with other settings of register 0xf0 or 0xf1. The information
> in the ASRock tool suggests that one of the bits is used to control the DDR3
> voltage.
>
> Guenter
>
> I am a bit afraid with "(at your own risk):"
> Do I really need to do that?
Only if you want to see the CPU fan speed.
> Could you check again the hexa values to be sure.
You are welcome to check yourself. You can find the ASRock board parameters in
the Conf subdirectory of the ASRock performance tuning utility. The file for
your board is named 970E4.xml. The datasheet for the SuperIO chip is available
from Nuvoton's web site. The datasheet for NCT6776F is marked as "Request",
but you can download and use the datasheet for NCT5577D instead; it is mostly
the same.
> The last command I have to add should be:
> isaset -y 0x2e 0x2f 0xf1 0xf2
> yes?
If your fan is connected to CPUFANIN2, yes. Otherwise it would be "isaset -y
0x2e 0x2f 0xf1 0xb3".
> What will I to do after that? directly run sensors or something else?
>
Yes, if you run the sensors command, you should see the CPUFAN speed.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (10 preceding siblings ...)
2012-09-17 15:14 ` Guenter Roeck
@ 2012-09-17 17:19 ` MrNice
2012-09-17 20:43 ` Guenter Roeck
` (4 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: MrNice @ 2012-09-17 17:19 UTC (permalink / raw)
To: lm-sensors
On 17/09/12 16:14, Guenter Roeck wrote:
> On Mon, Sep 17, 2012 at 11:51:08AM +0100, MrNice wrote:
>> On Sun, Sep 16, 2012 at 09:03:17PM +0100, Jean-Pierre Thibert wrote:
>>> On 16/09/12 19:53, Guenter Roeck wrote:
>>>> On Sun, Sep 16, 2012 at 07:44:58AM +0100, Jean-Pierre Thibert wrote:
>>>> [ ... ]
>>>>> I have an ASRock 970 Extreme4 UEFI version P2.00
>>>>> In the H/W Monitor page of the UEFI/BIOS, I have the following:
>>>>> CPU Temperature : 36.5 °C
>>>>> M/B Temperature : 28.0 °C
>>>>>
>>>>> CPU Fan 1 Speed : 1065 RPM (this is a pwm connector with 4 pins.
>>>>> I have a pwm fan) called CPU_FAN1 on the motherboard
>>>>> CPU Fan 2 Speed : N/A (this is a 3 pins connector. No connected
>>>>> fan) called CPU_FAN2 on the motherboard
>>>>> Chassis Fan 1 Speed : N/A (this is a pwm connector with 4 pins.
>>>>> No connected fan) called CHA_FAN1 on the motherboard
>>>>> Chassis Fan 2 Speed : 730 RPM (this is a 3 pins connector. I have
>>>>> a 3 pins connected fan) called CHA_FAN2 on the motherboard
>>>>> Chassis Fan 3 Speed : 760 RPM (this is a 3 pins connector. I have
>>>>> a 3 pins connected fan) called CHA_FAN3 on the motherboard
>>>>> Power Fan Speed : N/A (this is a 3 pins connector. No connected
>>>>> fan) called PWR_FAN1 on the motherboard
>>>>>
>>>>> Vcore : +1.328 V
>>>>> + 12.00V : +12.144 V
>>>>> + 5.00V : +5.136 V
>>>>> + 3.30V : +3.280 V
>>>>>
>>>>> lm-sensors has almost all the values but no fan speed.
>>>>> I don't know why I had the CPU_FAN2 for a short time and it disappeared.
>>>>> I can't understand what you suggest to have the value back. Could
>>>> I did not suggest anything.
>>>>
>>>> I found some information about the board. The chassis fans are connected to
>>>> memory mapped IO, so there is nothing we can do there. There are two CPU fans,
>>>> multiplexed to the SuperIO chip through GPIO pins. It _might be possible that
>>>> we can manually set those pins.
>>>>
>>>> Please send the output of the following commands:
>>>> isadump -y -k 0x87,0x87 0x2e 0x2f
>>>> isadump -y -k 0x87,0x87 0x2e 0x2f 8
>>>> dmidecode
>>>>
>>>> Thanks,
>>>> Guenter
>>>>
>>>>
>>>>
>>>>
>>> sudo isadump -y -k 0x87,0x87 0x2e 0x2f
>>> 0 1 2 3 4 5 6 7 8 9 a b c d e f
>>> 00: ff ff 00 ff ff ff ff 0b ff ff ff ff ff ff ff ff
>>> 10: ff ff ff ff ff ff ff ff ff ff f8 ce 00 00 ff ff
>>> 20: c3 33 ff 00 5c 00 00 90 00 ff 60 04 81 00 00 01
>>> 30: e1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> 60: 02 90 00 00 ff ff ff ff ff ff ff ff ff ff ff ff
>>> 70: 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> e0: 7f 7f ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> f0: 00 00 00 a4 ff 10 00 87 47 00 00 ff ff ff ff ff
>>>
>>>
>>> sudo isadump -y -k 0x87,0x87 0x2e 0x2f 8
>>> 0 1 2 3 4 5 6 7 8 9 a b c d e f
>>> 00: ff ff 00 ff ff ff ff 08 ff ff ff ff ff ff ff ff
>>> 10: ff ff ff ff ff ff ff ff ff ff f8 ce 00 00 ff ff
>>> 20: c3 33 ff 00 5c 00 00 90 00 ff 60 04 81 00 00 01
>>> 30: 01 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> 60: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> f0: f3 f3 00 ff 00 00 00 00 ff ff ff ff ff ff ff ff
>>>
>> I just noticed that you dropped the mailing list in your reply.
>> Please don't do that; others may need the information later on,
>> and I myself use it for searches.
>>
>> I initially thought the above does not help, but it kind of makes sense.
>>
>> You can try the following command sequence (at your own risk):
>>
>> isaset -y -f 0x2e 0x87
>> isaset -y -f 0x2e 0x87
>> isaset -y 0x2e 0x2f 0x7 0x8
>> isaset -y 0x2e 0x2f 0xf0 0xb2
>> isaset -y 0x2e 0x2f 0xf1 0xb3
>>
>> The 0xb3 in the last command should select CPUFANIN. Replace it with 0xf2 to
>> select CPUFANIN2.
>>
>> You'll have to copy the commands into a file and execute it as shell script.
>>
>> Do _not_ play with other settings of register 0xf0 or 0xf1. The information
>> in the ASRock tool suggests that one of the bits is used to control the DDR3
>> voltage.
>>
>> Guenter
>>
>> I am a bit afraid with "(at your own risk):"
>> Do I really need to do that?
> Only if you want to see the CPU fan speed.
>
>> Could you check again the hexa values to be sure.
> You are welcome to check yourself. You can find the ASRock board parameters in
> the Conf subdirectory of the ASRock performance tuning utility. The file for
> your board is named 970E4.xml. The datasheet for the SuperIO chip is available
> from Nuvoton's web site. The datasheet for NCT6776F is marked as "Request",
> but you can download and use the datasheet for NCT5577D instead; it is mostly
> the same.
>
>> The last command I have to add should be:
>> isaset -y 0x2e 0x2f 0xf1 0xf2
>> yes?
> If your fan is connected to CPUFANIN2, yes. Otherwise it would be "isaset -y
> 0x2e 0x2f 0xf1 0xb3".
>
>> What will I to do after that? directly run sensors or something else?
>>
> Yes, if you run the sensors command, you should see the CPUFAN speed.
>
> Guenter
>
>
I had a look on the NCT5577D datasheet but it's not for me ;-)
So I tried your commands in a file named cpufan:
#!/bin/bash
isaset -y -f 0x2e 0x87
isaset -y -f 0x2e 0x87
isaset -y 0x2e 0x2f 0x7 0x8
isaset -y 0x2e 0x2f 0xf0 0xb2
isaset -y 0x2e 0x2f 0xf1 0xf2
I have this error
sudo ./cpufan
Data mismatch, wrote 0x87, read 0xff back.
Data mismatch, wrote 0x87, read 0x09 back.
Nothing more with sensors
What can I do?
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (11 preceding siblings ...)
2012-09-17 17:19 ` MrNice
@ 2012-09-17 20:43 ` Guenter Roeck
2012-09-23 18:07 ` MrNice
` (3 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Guenter Roeck @ 2012-09-17 20:43 UTC (permalink / raw)
To: lm-sensors
On Mon, Sep 17, 2012 at 06:19:34PM +0100, MrNice wrote:
[ ... ]
> I had a look on the NCT5577D datasheet but it's not for me ;-)
> So I tried your commands in a file named cpufan:
> #!/bin/bash
> isaset -y -f 0x2e 0x87
> isaset -y -f 0x2e 0x87
> isaset -y 0x2e 0x2f 0x7 0x8
> isaset -y 0x2e 0x2f 0xf0 0xb2
> isaset -y 0x2e 0x2f 0xf1 0xf2
>
> I have this error
> sudo ./cpufan
> Data mismatch, wrote 0x87, read 0xff back.
> Data mismatch, wrote 0x87, read 0x09 back.
>
> Nothing more with sensors
> What can I do?
I am out of ideas. At this point I would need a board to be able to play with
it. Reboot and live with it...
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (12 preceding siblings ...)
2012-09-17 20:43 ` Guenter Roeck
@ 2012-09-23 18:07 ` MrNice
2012-09-23 18:39 ` Jean Delvare
` (2 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: MrNice @ 2012-09-23 18:07 UTC (permalink / raw)
To: lm-sensors
On 09/17/2012 09:43 PM, Guenter Roeck wrote:
> On Mon, Sep 17, 2012 at 06:19:34PM +0100, MrNice wrote:
> [ ... ]
>
>> I had a look on the NCT5577D datasheet but it's not for me ;-)
>> So I tried your commands in a file named cpufan:
>> #!/bin/bash
>> isaset -y -f 0x2e 0x87
>> isaset -y -f 0x2e 0x87
>> isaset -y 0x2e 0x2f 0x7 0x8
>> isaset -y 0x2e 0x2f 0xf0 0xb2
>> isaset -y 0x2e 0x2f 0xf1 0xf2
>>
>> I have this error
>> sudo ./cpufan
>> Data mismatch, wrote 0x87, read 0xff back.
>> Data mismatch, wrote 0x87, read 0x09 back.
>>
>> Nothing more with sensors
>> What can I do?
> I am out of ideas. At this point I would need a board to be able to play with
> it. Reboot and live with it...
>
> Guenter
>
>
For the last few days I was testing different programs to monitor M/B
and CPU with Ubuntu and Windows 7, FYI:
AMD Overdrive
Core Temp
Hardware Monitor
None has the good values and are complete.
AMD Overdrive
has the 2 chassis fan value but not the CPU_fan pwm. It has a board temp
TMPIN1 value (64.7 degrees C) very high compare to other program. I
can't find what is TMPIN1.
It has a CPU temp (around 7 degrees C) so this is Tctl.
Core Temp
has CPU temp around 6 degrees C, so this is Tctl.
has "Tj. Max:" 70 degrees C.
More info here for the Tj. Max definition:
http://www.alcpu.com/forums/viewtopic.php?t‰2
Do you agree with 70 C for the AMD FX-8120 CPU?
This program has no fan value area.
Hardware Monitor
has AUXTIN in the same way than sensors. Wrong value, should be idle
like with sensors.
has CPU Core temp around 6 C, so this is Tctl.
This program has no fan value area.
This afternoon, for some reason, sensors has CPU_Fan1 pwm value again:
fan1: 0 RPM (min = 0 RPM) ALARM
CPU_Fan1 pwm: 1036 RPM (min = 0 RPM) ALARM
fan3: 0 RPM (min = 0 RPM) ALARM
fan4: 0 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM) ALARM
this value is right compared to UEFI.
Do you want some info to understand why it's appear again?
Let me know.
Question: What program do you advise to heavy load the CPU and get
higher temp?
JP
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (13 preceding siblings ...)
2012-09-23 18:07 ` MrNice
@ 2012-09-23 18:39 ` Jean Delvare
2012-09-26 14:01 ` MrNice
2012-09-26 18:21 ` Guenter Roeck
16 siblings, 0 replies; 18+ messages in thread
From: Jean Delvare @ 2012-09-23 18:39 UTC (permalink / raw)
To: lm-sensors
On Sun, 23 Sep 2012 19:07:05 +0100, MrNice wrote:
> Question: What program do you advise to heavy load the CPU and get
> higher temp?
$ md5sum /dev/zero &
once per logical CPU.
--
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] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (14 preceding siblings ...)
2012-09-23 18:39 ` Jean Delvare
@ 2012-09-26 14:01 ` MrNice
2012-09-26 18:21 ` Guenter Roeck
16 siblings, 0 replies; 18+ messages in thread
From: MrNice @ 2012-09-26 14:01 UTC (permalink / raw)
To: lm-sensors
On 09/23/2012 07:39 PM, Jean Delvare wrote:
> On Sun, 23 Sep 2012 19:07:05 +0100, MrNice wrote:
>> Question: What program do you advise to heavy load the CPU and get
>> higher temp?
> $ md5sum /dev/zero &
>
> once per logical CPU.
>
Thanks Jean.
Unfortunately after the next boot, fan2 (CPU_FAN1 for ASROCK 970) was
again at 0 RPM.
I tried more reboots, changes in the UEFI but nothing.
Very strange...
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [lm-sensors] No such subfeature known when sensors -s
2012-09-13 8:19 [lm-sensors] No such subfeature known when sensors -s MrNice
` (15 preceding siblings ...)
2012-09-26 14:01 ` MrNice
@ 2012-09-26 18:21 ` Guenter Roeck
16 siblings, 0 replies; 18+ messages in thread
From: Guenter Roeck @ 2012-09-26 18:21 UTC (permalink / raw)
To: lm-sensors
On Wed, Sep 26, 2012 at 03:01:55PM +0100, MrNice wrote:
> On 09/23/2012 07:39 PM, Jean Delvare wrote:
> >On Sun, 23 Sep 2012 19:07:05 +0100, MrNice wrote:
> >>Question: What program do you advise to heavy load the CPU and get
> >>higher temp?
> >$ md5sum /dev/zero &
> >
> >once per logical CPU.
> >
> Thanks Jean.
>
> Unfortunately after the next boot, fan2 (CPU_FAN1 for ASROCK 970)
> was again at 0 RPM.
> I tried more reboots, changes in the UEFI but nothing.
> Very strange...
>
The only idea I have at this point is for you to run superiotool (the version I
pointed you to earlier) when you see the fan output, and then again when you
don't. If we are lucky, we might see a difference in GPIO programming for the
two cases.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 18+ messages in thread