Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #190386 > unrolled thread

lm-sensors doesn't see the cpu rpm.....

Started byMichael Fothergill <michael.fothergill@gmail.com>
First post2017-12-28 13:10 +0100
Last post2017-12-28 21:20 +0100
Articles 15 — 3 participants

Back to article view | Back to linux.debian.user

Contents

  lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 13:10 +0100
    Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 13:40 +0100
      Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 14:10 +0100
        Re: lm-sensors doesn't see the cpu rpm..... Greg Wooledge <wooledg@eeg.ccf.org> - 2017-12-28 15:00 +0100
          Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 16:00 +0100
          Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 16:10 +0100
          Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 16:20 +0100
          Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 16:40 +0100
          Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 17:00 +0100
          Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 18:00 +0100
    Re: lm-sensors doesn't see the cpu rpm..... deloptes <deloptes@gmail.com> - 2017-12-28 19:20 +0100
      Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 19:50 +0100
        Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 20:00 +0100
      Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 20:20 +0100
      Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 21:20 +0100

#190386 — lm-sensors doesn't see the cpu rpm.....

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 13:10 +0100
Subjectlm-sensors doesn't see the cpu rpm.....
Message-ID<v1Fax-8gH-9@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Dear Folks,

I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
cooler.

I installed lm-sensors and ran the /etc module update command.

The output looks like this:

root@bong:/home/mikef# sensors
asus-isa-0000
Adapter: ISA adapter
cpu_fan:        0 RPM

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +21.9°C  (high = +70.0°C)
                       (crit = +90.0°C, hyst = +87.0°C)

nouveau-pci-0700
Adapter: PCI adapter
GPU core:     +0.90 V  (min =  +0.88 V, max =  +1.08 V)
temp1:        +35.0°C  (high = +95.0°C, hyst =  +3.0°C)
                       (crit = +105.0°C, hyst =  +5.0°C)
                       (emerg = +135.0°C, hyst =  +5.0°C)

fam15h_power-pci-00c4
Adapter: PCI adapter
power1:        6.75 W  (crit = 125.19 W)


it8721-isa-0290

Adapter: ISA
adapter

in0:          +2.83 V  (min =  +2.02 V, max =  +2.95
V)
in1:          +2.83 V  (min =  +1.68 V, max =  +1.73 V)
ALARM
in2:          +0.98 V  (min =  +2.40 V, max =  +1.08 V)
ALARM
+3.3V:        +3.31 V  (min =  +0.38 V, max =  +0.96 V)
ALARM
in4:          +0.25 V  (min =  +0.41 V, max =  +0.20 V)  ALARM
in5:          +2.51 V  (min =  +0.12 V, max =  +0.00 V)  ALARM
in6:          +1.98 V  (min =  +1.54 V, max =  +0.59 V)  ALARM
3VSB:         +3.94 V  (min =  +3.31 V, max =  +0.89 V)  ALARM
Vbat:         +3.29 V
fan1:        1814 RPM  (min =   87 RPM)
fan2:           0 RPM  (min =   46 RPM)  ALARM
fan3:        1125 RPM  (min =   29 RPM)
temp1:        +37.0°C  (low  = +34.0°C, high = +91.0°C)  sensor = thermistor
temp2:        +30.0°C  (low  = +45.0°C, high =  +9.0°C)  ALARM  sensor =
thermistor
temp3:       -128.0°C  (low  = -60.0°C, high =  +4.0°C)  sensor = disabled
intrusion0:  OK

root@bong:/home/mikef#

The cpu fan is running at around 2500 rpm.

If the connector were 3 pin rather than 4 pin could that explain the zero
here?

Suggestions on a tweak that could awaken the sensor or stimulate lm-sensors
truffle hound hunting skills here would be appreciated.

Googling around gives quite complex suggestions.

Is there something simple I could try here?

Regards

Michael Fothergill

[toc] | [next] | [standalone]

#190387

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 13:40 +0100
Message-ID<v1FDz-8rd-7@gated-at.bofh.it>
In reply to#190386

[Multipart message — attachments visible in raw view] — view raw

I have 3 case fans in the box here but lm-sensors only sees two of them
apparently as well as not seeing the cpu fan.

Funny stuff.

Regards

MF

On 28 December 2017 at 11:50, Michael Fothergill <
michael.fothergill@gmail.com> wrote:

> Dear Folks,
>
> I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> cooler.
>
> I installed lm-sensors and ran the /etc module update command.
>
> The output looks like this:
>
> root@bong:/home/mikef# sensors
> asus-isa-0000
> Adapter: ISA adapter
> cpu_fan:        0 RPM
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1:        +21.9°C  (high = +70.0°C)
>                        (crit = +90.0°C, hyst = +87.0°C)
>
> nouveau-pci-0700
> Adapter: PCI adapter
> GPU core:     +0.90 V  (min =  +0.88 V, max =  +1.08 V)
> temp1:        +35.0°C  (high = +95.0°C, hyst =  +3.0°C)
>                        (crit = +105.0°C, hyst =  +5.0°C)
>                        (emerg = +135.0°C, hyst =  +5.0°C)
>
> fam15h_power-pci-00c4
> Adapter: PCI adapter
> power1:        6.75 W  (crit = 125.19 W)
>
>
> it8721-isa-0290
>
> Adapter: ISA adapter
>
> in0:          +2.83 V  (min =  +2.02 V, max =  +2.95
> V)
> in1:          +2.83 V  (min =  +1.68 V, max =  +1.73 V)
> ALARM
> in2:          +0.98 V  (min =  +2.40 V, max =  +1.08 V)
> ALARM
> +3.3V:        +3.31 V  (min =  +0.38 V, max =  +0.96 V)
> ALARM
> in4:          +0.25 V  (min =  +0.41 V, max =  +0.20 V)  ALARM
> in5:          +2.51 V  (min =  +0.12 V, max =  +0.00 V)  ALARM
> in6:          +1.98 V  (min =  +1.54 V, max =  +0.59 V)  ALARM
> 3VSB:         +3.94 V  (min =  +3.31 V, max =  +0.89 V)  ALARM
> Vbat:         +3.29 V
> fan1:        1814 RPM  (min =   87 RPM)
> fan2:           0 RPM  (min =   46 RPM)  ALARM
> fan3:        1125 RPM  (min =   29 RPM)
> temp1:        +37.0°C  (low  = +34.0°C, high = +91.0°C)  sensor =
> thermistor
> temp2:        +30.0°C  (low  = +45.0°C, high =  +9.0°C)  ALARM  sensor =
> thermistor
> temp3:       -128.0°C  (low  = -60.0°C, high =  +4.0°C)  sensor = disabled
> intrusion0:  OK
>
> root@bong:/home/mikef#
>
> The cpu fan is running at around 2500 rpm.
>
> If the connector were 3 pin rather than 4 pin could that explain the zero
> here?
>
> Suggestions on a tweak that could awaken the sensor or stimulate
> lm-sensors truffle hound hunting skills here would be appreciated.
>
> Googling around gives quite complex suggestions.
>
> Is there something simple I could try here?
>
> Regards
>
> Michael Fothergill
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

[toc] | [prev] | [next] | [standalone]

#190388

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 14:10 +0100
Message-ID<v1G6H-vq-25@gated-at.bofh.it>
In reply to#190387

[Multipart message — attachments visible in raw view] — view raw

Dear All,

I looked at the config-4.9.0-4-amd64 file for the current kernel:

# Native drivers
#
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ABITUGURU3=m
# CONFIG_SENSORS_AD7314 is not set
CONFIG_SENSORS_AD7414=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
# CONFIG_SENSORS_ADT7310 is not set
# CONFIG_SENSORS_ADT7410 is not set
CONFIG_SENSORS_ADT7411=m
CONFIG_SENSORS_ADT7462=m
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7475=m
CONFIG_SENSORS_ASC7621=m
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_K10TEMP=m
CONFIG_SENSORS_FAM15H_POWER=m
CONFIG_SENSORS_APPLESMC=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS620=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_DELL_SMM=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHMD=m
CONFIG_SENSORS_FTSTEUTATES=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_G760A=m
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_GPIO_FAN is not set
# CONFIG_SENSORS_HIH6130 is not set
CONFIG_SENSORS_IBMAEM=m
CONFIG_SENSORS_IBMPEX=m
# CONFIG_SENSORS_IIO_HWMON is not set
CONFIG_SENSORS_I5500=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_JC42=m
# CONFIG_SENSORS_POWR1220 is not set
CONFIG_SENSORS_LINEAGE=m
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2990 is not set
CONFIG_SENSORS_LTC4151=m
CONFIG_SENSORS_LTC4215=m
# CONFIG_SENSORS_LTC4222 is not set
CONFIG_SENSORS_LTC4245=m
# CONFIG_SENSORS_LTC4260 is not set
CONFIG_SENSORS_LTC4261=m
CONFIG_SENSORS_MAX1111=m
CONFIG_SENSORS_MAX16065=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX1668=m
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX31722 is not set
CONFIG_SENSORS_MAX6639=m
CONFIG_SENSORS_MAX6642=m
CONFIG_SENSORS_MAX6650=m
# CONFIG_SENSORS_MAX6697 is not set
# CONFIG_SENSORS_MAX31790 is not set
# CONFIG_SENSORS_MCP3021 is not set
CONFIG_SENSORS_MENF21BMC_HWMON=m
CONFIG_SENSORS_ADCXX=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM70=m
CONFIG_SENSORS_LM73=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
# CONFIG_SENSORS_LM95234 is not set
CONFIG_SENSORS_LM95241=m
CONFIG_SENSORS_LM95245=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_NTC_THERMISTOR=m
CONFIG_SENSORS_NCT6683=m
CONFIG_SENSORS_NCT6775=m
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
CONFIG_SENSORS_PCF8591=m
# CONFIG_PMBUS is not set
# CONFIG_SENSORS_SHT15 is not set
CONFIG_SENSORS_SHT21=m
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHTC1 is not set
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_EMC1403=m
CONFIG_SENSORS_EMC2103=m
CONFIG_SENSORS_EMC6W201=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_SCH56XX_COMMON=m
CONFIG_SENSORS_SCH5627=m
CONFIG_SENSORS_SCH5636=m
CONFIG_SENSORS_SMM665=m
# CONFIG_SENSORS_ADC128D818 is not set
CONFIG_SENSORS_ADS1015=m
CONFIG_SENSORS_ADS7828=m
CONFIG_SENSORS_ADS7871=m
CONFIG_SENSORS_AMC6821=m
# CONFIG_SENSORS_INA209 is not set
# CONFIG_SENSORS_INA2XX is not set
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_TC74 is not set
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_TMP102=m
# CONFIG_SENSORS_TMP103 is not set
CONFIG_SENSORS_TMP401=m
CONFIG_SENSORS_TMP421=m
CONFIG_SENSORS_VIA_CPUTEMP=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83795=m
# CONFIG_SENSORS_W83795_FANCTRL is not set
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83L786NG=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m

It seems that the kernel is configured with the module m setting
consistently not the internal y setting so debian does not use the built in
option by default here it would seem

- see discussion here

https://www.linux.com/learn/intro-to-linux/2017/9/advanced-lm-sensors-tips-and-tricks-linux-0

so modifying the /etc/modules file works here.

I notice that
# CONFIG_SENSORS_W83795_FANCTRL is not set
has been commented out

and

# CONFIG_SENSORS_GPIO_FAN is not set

is in a similar state

I will continue looking at this in more detail.

Regards

MF











On 28 December 2017 at 12:14, Michael Fothergill <
michael.fothergill@gmail.com> wrote:

> I have 3 case fans in the box here but lm-sensors only sees two of them
> apparently as well as not seeing the cpu fan.
>
> Funny stuff.
>
> Regards
>
> MF
>
> On 28 December 2017 at 11:50, Michael Fothergill <
> michael.fothergill@gmail.com> wrote:
>
>> Dear Folks,
>>
>> I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
>> cooler.
>>
>> I installed lm-sensors and ran the /etc module update command.
>>
>> The output looks like this:
>>
>> root@bong:/home/mikef# sensors
>> asus-isa-0000
>> Adapter: ISA adapter
>> cpu_fan:        0 RPM
>>
>> k10temp-pci-00c3
>> Adapter: PCI adapter
>> temp1:        +21.9°C  (high = +70.0°C)
>>                        (crit = +90.0°C, hyst = +87.0°C)
>>
>> nouveau-pci-0700
>> Adapter: PCI adapter
>> GPU core:     +0.90 V  (min =  +0.88 V, max =  +1.08 V)
>> temp1:        +35.0°C  (high = +95.0°C, hyst =  +3.0°C)
>>                        (crit = +105.0°C, hyst =  +5.0°C)
>>                        (emerg = +135.0°C, hyst =  +5.0°C)
>>
>> fam15h_power-pci-00c4
>> Adapter: PCI adapter
>> power1:        6.75 W  (crit = 125.19 W)
>>
>>
>> it8721-isa-0290
>>
>> Adapter: ISA adapter
>>
>> in0:          +2.83 V  (min =  +2.02 V, max =  +2.95
>> V)
>> in1:          +2.83 V  (min =  +1.68 V, max =  +1.73 V)
>> ALARM
>> in2:          +0.98 V  (min =  +2.40 V, max =  +1.08 V)
>> ALARM
>> +3.3V:        +3.31 V  (min =  +0.38 V, max =  +0.96 V)
>> ALARM
>> in4:          +0.25 V  (min =  +0.41 V, max =  +0.20 V)  ALARM
>> in5:          +2.51 V  (min =  +0.12 V, max =  +0.00 V)  ALARM
>> in6:          +1.98 V  (min =  +1.54 V, max =  +0.59 V)  ALARM
>> 3VSB:         +3.94 V  (min =  +3.31 V, max =  +0.89 V)  ALARM
>> Vbat:         +3.29 V
>> fan1:        1814 RPM  (min =   87 RPM)
>> fan2:           0 RPM  (min =   46 RPM)  ALARM
>> fan3:        1125 RPM  (min =   29 RPM)
>> temp1:        +37.0°C  (low  = +34.0°C, high = +91.0°C)  sensor =
>> thermistor
>> temp2:        +30.0°C  (low  = +45.0°C, high =  +9.0°C)  ALARM  sensor =
>> thermistor
>> temp3:       -128.0°C  (low  = -60.0°C, high =  +4.0°C)  sensor = disabled
>> intrusion0:  OK
>>
>> root@bong:/home/mikef#
>>
>> The cpu fan is running at around 2500 rpm.
>>
>> If the connector were 3 pin rather than 4 pin could that explain the zero
>> here?
>>
>> Suggestions on a tweak that could awaken the sensor or stimulate
>> lm-sensors truffle hound hunting skills here would be appreciated.
>>
>> Googling around gives quite complex suggestions.
>>
>> Is there something simple I could try here?
>>
>> Regards
>>
>> Michael Fothergill
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>

[toc] | [prev] | [next] | [standalone]

#190389

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2017-12-28 15:00 +0100
Message-ID<v1GT0-QQ-3@gated-at.bofh.it>
In reply to#190388
On Thu, Dec 28, 2017 at 01:11:56PM +0000, Michael Fothergill wrote:
> root@bong:/boot#  sudo modprobe coretemp
> modprobe: ERROR: could not insert 'coretemp': No such device
> 
> 
> This is odd because coretemp is set as a module option in the config file:
> 
> CONFIG_SENSORS_CORETEMP=m
> 
> Comments appreciared

Well, it *should* work with a standard Debian kernel and applicable
hardware.

wooledg:~$ /sbin/modinfo coretemp
filename:       /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.ko
license:        GPL
description:    Intel Core temperature monitor
author:         Rudolf Marek <r.marek@assembler.cz>
alias:          cpu:type:x86,ven0000fam*mod*:feature:*01C0*
depends:        
intree:         Y
vermagic:       4.9.0-4-amd64 SMP mod_unload modversions 
parm:           tjmax:TjMax value in degrees Celsius (int)

Your "No such device" error sounds like it probed for hardware and didn't
find any.  If the module itself were missing from the file system, then
I would have expected "FATAL: Module coretemp not found in directory ...".

It says "Intel" in the description.  Are you using an Intel CPU?

[toc] | [prev] | [next] | [standalone]

#190394

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 16:00 +0100
Message-ID<v1HP3-1v8-1@gated-at.bofh.it>
In reply to#190389

[Multipart message — attachments visible in raw view] — view raw

On 28 December 2017 at 13:55, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +0000, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>
> wooledg:~$ /sbin/modinfo coretemp
> filename:       /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:        GPL
> description:    Intel Core temperature monitor
> author:         Rudolf Marek <r.marek@assembler.cz>
> alias:          cpu:type:x86,ven0000fam*mod*:feature:*01C0*
> depends:
> intree:         Y
> vermagic:       4.9.0-4-amd64 SMP mod_unload modversions
> parm:           tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>


> It says "Intel" in the description.  Are you using an Intel CPU?
>

​Here is the output of lscpu:​


​root@bong:/home/mikef# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    2
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             AuthenticAMD
CPU family:            21
Model:                 2
Model name:            AMD FX(tm)-8350 Eight-Core Processor
Stepping:              0
CPU MHz:               4334.834
BogoMIPS:              8669.66
Virtualization:        AMD-V
L1d cache:             16K
L1i cache:             64K
L2 cache:              2048K
L3 cache:              8192K
NUMA node0 CPU(s):     0-7
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid
aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2
popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm
sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce
nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1
arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid
decodeassists pausefilter pfthreshold
root@bong:/home/mikef#
​

​It looks like an FX8350 chip to me.

Comments appreciated

Regards

MF​
​

[toc] | [prev] | [next] | [standalone]

#190397

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 16:10 +0100
Message-ID<v1HYJ-1PA-15@gated-at.bofh.it>
In reply to#190389

[Multipart message — attachments visible in raw view] — view raw

On 28 December 2017 at 13:55, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +0000, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

​Perhaps you could suggest some other module names I could try to turn on
using
the modprobe command that I do not have turned on at present based on the
lsmod output.

​Maybe one or to might work.

Cheers

MF



>
> wooledg:~$ /sbin/modinfo coretemp
> filename:       /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:        GPL
> description:    Intel Core temperature monitor
> author:         Rudolf Marek <r.marek@assembler.cz>
> alias:          cpu:type:x86,ven0000fam*mod*:feature:*01C0*
> depends:
> intree:         Y
> vermagic:       4.9.0-4-amd64 SMP mod_unload modversions
> parm:           tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>

[toc] | [prev] | [next] | [standalone]

#190398

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 16:20 +0100
Message-ID<v1I8p-1TW-13@gated-at.bofh.it>
In reply to#190389

[Multipart message — attachments visible in raw view] — view raw

On 28 December 2017 at 13:55, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +0000, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

​The output of lspci is here:
https://pastebin.com/AAXTq8Uh
​


>
> wooledg:~$ /sbin/modinfo coretemp
> filename:       /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:        GPL
> description:    Intel Core temperature monitor
> author:         Rudolf Marek <r.marek@assembler.cz>
> alias:          cpu:type:x86,ven0000fam*mod*:feature:*01C0*
> depends:
> intree:         Y
> vermagic:       4.9.0-4-amd64 SMP mod_unload modversions
> parm:           tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>
>

[toc] | [prev] | [next] | [standalone]

#190403

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 16:40 +0100
Message-ID<v1IrL-23C-9@gated-at.bofh.it>
In reply to#190389

[Multipart message — attachments visible in raw view] — view raw

On 28 December 2017 at 13:55, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +0000, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>
> wooledg:~$ /sbin/modinfo coretemp
> filename:       /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:        GPL
> description:    Intel Core temperature monitor
> author:         Rudolf Marek <r.marek@assembler.cz>
> alias:          cpu:type:x86,ven0000fam*mod*:feature:*01C0*
> depends:
> intree:         Y
> vermagic:       4.9.0-4-amd64 SMP mod_unload modversions
> parm:           tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>

​I now realise that coretemp only works with Intel chips not AMD ones....

Ooops!

I will look up module names that work for the FX 8350 and see of I can find
any that are not listed in lsmod and try installing them
with modprobe.

Cheers

MF​

[toc] | [prev] | [next] | [standalone]

#190407

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 17:00 +0100
Message-ID<v1IL8-2cF-13@gated-at.bofh.it>
In reply to#190389

[Multipart message — attachments visible in raw view] — view raw

On 28 December 2017 at 13:55, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +0000, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

​If you look here:

https://askubuntu.com/questions/748615/lm-sensors-not-returning-cpu-temp-it87

it says that You need to append acpi_enforce_resources=lax at the end of
> the line GRUB_CMDLINE_LINUX
>
​in /etc/default/grub to make e.g. the it87 module work for the FX8350 chip
AFAICT

BUT

If you look at my /etc/default/grub:

root@bong:/etc/default# more grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX="initrd=/install/initrd.gz"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to
Linux
#GRUB_DISABLE_LINUX_UUID=true


# Uncomment to disable generation of recovery mode menu
entries
#GRUB_DISABLE_RECOVERY="true"



# Uncomment to get a beep at grub
start
#GRUB_INIT_TUNE="480 440
1"
root@bong:/etc/default#


​I don't have any acpi command in there but lsmod does list it87 as a
module for my install:

​root@bong:/etc/default# lsmod | grep it87
it87                   57344

0
hwmon_vid              16384  1 it87


Does it need to have a 1 not a zero in there for the it87 to actually be
working even if it is installed?

Cheers

MF









>
> wooledg:~$ /sbin/modinfo coretemp
> filename:       /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:        GPL
> description:    Intel Core temperature monitor
> author:         Rudolf Marek <r.marek@assembler.cz>
> alias:          cpu:type:x86,ven0000fam*mod*:feature:*01C0*
> depends:
> intree:         Y
> vermagic:       4.9.0-4-amd64 SMP mod_unload modversions
> parm:           tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>
>

[toc] | [prev] | [next] | [standalone]

#190411

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 18:00 +0100
Message-ID<v1JHb-2PZ-5@gated-at.bofh.it>
In reply to#190389

[Multipart message — attachments visible in raw view] — view raw

On 28 December 2017 at 13:55, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +0000, Michael Fothergill wrote:
> > root@bong:/boot#  sudo modprobe coretemp
> > modprobe: ERROR: could not insert 'coretemp': No such device
> >
> >
> > This is odd because coretemp is set as a module option in the config
> file:
> >
> > CONFIG_SENSORS_CORETEMP=m
> >
> > Comments appreciared
>
> Well, it *should* work with a standard Debian kernel and applicable
> hardware.
>

​Dear All,

It's sad but I think I need install Windows 10 on this machine to sort out
the fan control and cpu cooler problems.

This machine overheats when I run pov-ray benchmark on it and shuts down.

see here (first page only)

https://forums.gentoo.org/viewtopic-t-1056576-start-0.html


Then I can install the ASUS Fan Xpert and ROG software etc on top of the FX
990 sabertooth motherboard I have.......

I think I might need to change the thermal paste compound between the CPU
and Arctic Freezer 13 heatsink to cure the cooling problem.

I am going to use Artic MX-4 paste.

While Debian and Gentoo are OK to work with here, I cannot tolerate the
machine shutting down now and again due to overheating any longer.

I am corresponding with the ASUS technical folks at present.

I need the extra special bloodhound Passau Cathedral Organ factor here to
help check on the temps and the fan activity once I start doing
surgery on the cpu/fan-heatsink thermal interface...........

CPUs cost money.

Thanks for the help to date.

Regards

MF



​


>
> wooledg:~$ /sbin/modinfo coretemp
> filename:       /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp.
> ko
> license:        GPL
> description:    Intel Core temperature monitor
> author:         Rudolf Marek <r.marek@assembler.cz>
> alias:          cpu:type:x86,ven0000fam*mod*:feature:*01C0*
> depends:
> intree:         Y
> vermagic:       4.9.0-4-amd64 SMP mod_unload modversions
> parm:           tjmax:TjMax value in degrees Celsius (int)
>
> Your "No such device" error sounds like it probed for hardware and didn't
> find any.  If the module itself were missing from the file system, then
> I would have expected "FATAL: Module coretemp not found in directory ...".
>
> It says "Intel" in the description.  Are you using an Intel CPU?
>
>

[toc] | [prev] | [next] | [standalone]

#190416

Fromdeloptes <deloptes@gmail.com>
Date2017-12-28 19:20 +0100
Message-ID<v1KWB-3RP-11@gated-at.bofh.it>
In reply to#190386
Michael Fothergill wrote:

> I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> cooler.

I'm just wondering if you used the correct switch for the cpu fan - what is
your mother board?

also from the gentoo link

$ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
CONFIG_SENSORS_FAM15H_POWER=m
grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
CONFIG_SENSORS_K10TEMP=m

$ lsmod | grep temp
k10temp                16384  0
$ lsmod | grep fam15
fam15h_power           16384  0

does this apply to your kernel?

regards

[toc] | [prev] | [next] | [standalone]

#190417

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 19:50 +0100
Message-ID<v1LpD-46r-1@gated-at.bofh.it>
In reply to#190416

[Multipart message — attachments visible in raw view] — view raw

On 28 December 2017 at 18:14, deloptes <deloptes@gmail.com> wrote:

> Michael Fothergill wrote:
>
> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> > cooler.
>
> I'm just wondering if you used the correct switch for the cpu fan - what is
> your mother board?
>

​This is an interesting idea.  I built the PC myself.  Maybe I connected up
the CPU fan lead incorrectly..........

The motherboard is an ASUS FX 990 Sabertooth R2.0; the bios version is 2501.

Here is some of the info sent to the ASUS support folks:

[Product Information]
Product Type : Motherboard
Product Model : SABERTOOTH 990FX R2.0
Product S/N : EAM0BX019177
Operation System / Firmware or BIOS version : Debian 9 (Linuc) OS/Bios that
came with product

[Graphics Card Vendor/model/Chipset/Driver]
Nvidia engt 430 model

[CPU vendor/processor number]
AMD FX 8350

[Memory vendor/model/specification]
Memory Vengeance LP Upgrade: Corsair 8GB 1600Mhz Vengeance LP DDR3​


>
> also from the gentoo link
>
> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
> CONFIG_SENSORS_FAM15H_POWER=m
> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
> CONFIG_SENSORS_K10TEMP=m
>
> $ lsmod | grep temp
> k10temp                16384  0
> $ lsmod | grep fam15
> fam15h_power           16384  0
>
> does this apply to your kernel?
>

​I will login to the machine, fire up debian and run

lsmod | grep temp

and

lsmod | grep fam 15

and get you the output.

I think fam15 module is installed - check the lsmod output I already posted.

Please let me know any other commands/diagnostics you want running here.

Regards and thanks.

Michael Fothergill

​




>
> regards
>
>

[toc] | [prev] | [next] | [standalone]

#190420

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 20:00 +0100
Message-ID<v1Lzj-4c1-1@gated-at.bofh.it>
In reply to#190417

[Multipart message — attachments visible in raw view] — view raw

On 28 December 2017 at 18:30, Michael Fothergill <
michael.fothergill@gmail.com> wrote:

>
>
> On 28 December 2017 at 18:14, deloptes <deloptes@gmail.com> wrote:
>
>> Michael Fothergill wrote:
>>
>> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer
>> 13
>> > cooler.
>>
>> I'm just wondering if you used the correct switch for the cpu fan - what
>> is
>> your mother board?
>>
>
> ​This is an interesting idea.  I built the PC myself.  Maybe I connected
> up the CPU fan lead incorrectly..........
>

​Wait a minute here.......

When I said I build the PC, what I mean is I screwed the motherboard into
the PC and then connected up the 3 case fans to it.

The CPU cooler and FAN were actually attached to the motherboard by the
company I bought the entire motherboard bundle from (ie I purchased the
board, 8GB RAM preinstalled plus the Arctic Freezer
cooler thermal pasted (and baisted - its Christmas remember!) the firm here
in the UK offering it as a job lot.

I can't quite remember if the cpu cooler lead was already attached to the
motherboard at that point - I might have done that bit myself (and maybe
bungled it - you could be on the money here).

So some thought and imagination could be required here.​

​MF​


> The motherboard is an ASUS FX 990 Sabertooth R2.0; the bios version is
> 2501.
>
> Here is some of the info sent to the ASUS support folks:
>
> [Product Information]
> Product Type : Motherboard
> Product Model : SABERTOOTH 990FX R2.0
> Product S/N : EAM0BX019177
> Operation System / Firmware or BIOS version : Debian 9 (Linuc) OS/Bios
> that came with product
>
> [Graphics Card Vendor/model/Chipset/Driver]
> Nvidia engt 430 model
>
> [CPU vendor/processor number]
> AMD FX 8350
>
> [Memory vendor/model/specification]
> Memory Vengeance LP Upgrade: Corsair 8GB 1600Mhz Vengeance LP DDR3​
>
>
>>
>> also from the gentoo link
>>
>> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
>> CONFIG_SENSORS_FAM15H_POWER=m
>> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
>> CONFIG_SENSORS_K10TEMP=m
>>
>> $ lsmod | grep temp
>> k10temp                16384  0
>> $ lsmod | grep fam15
>> fam15h_power           16384  0
>>
>> does this apply to your kernel?
>>
>
> ​I will login to the machine, fire up debian and run
>
> lsmod | grep temp
>
> and
>
> lsmod | grep fam 15
>
> and get you the output.
>
> I think fam15 module is installed - check the lsmod output I already
> posted.
>
> Please let me know any other commands/diagnostics you want running here.
>
> Regards and thanks.
>
> Michael Fothergill
>
> ​
>
>
>
>
>>
>> regards
>>
>>
>

[toc] | [prev] | [next] | [standalone]

#190421

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 20:20 +0100
Message-ID<v1LSF-4A4-11@gated-at.bofh.it>
In reply to#190416

[Multipart message — attachments visible in raw view] — view raw

On 28 December 2017 at 18:14, deloptes <deloptes@gmail.com> wrote:

> Michael Fothergill wrote:
>
> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> > cooler.
>
> I'm just wondering if you used the correct switch for the cpu fan - what is
> your mother board?
>
> also from the gentoo link
>
> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
> CONFIG_SENSORS_FAM15H_POWER=m
> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
> CONFIG_SENSORS_K10TEMP=m
>
> $ lsmod | grep temp
> k10temp                16384  0
> $ lsmod | grep fam15
> fam15h_power           16384  0
>
> does this apply to your kernel?


​Here is the output from lsmod on this:​



> mikef@bong:~$ lsmod | grep fam15
> fam15h_power           16384  0
> mikef@bong:~$ lsmod | grep temp
> k10temp                16384  0
> mikef@bong:~$
>
>
​Cheers

MF​



>
> regards
>
>

[toc] | [prev] | [next] | [standalone]

#190427

FromMichael Fothergill <michael.fothergill@gmail.com>
Date2017-12-28 21:20 +0100
Message-ID<v1MOJ-5eO-1@gated-at.bofh.it>
In reply to#190416

[Multipart message — attachments visible in raw view] — view raw

On 28 December 2017 at 18:14, deloptes <deloptes@gmail.com> wrote:

> Michael Fothergill wrote:
>
> > I am running stretch on an AMD FX8350 box which uses an Arctic Freezer 13
> > cooler.
>
> I'm just wondering if you used the correct switch for the cpu fan - what is
> your mother board?
>
> also from the gentoo link
>
> $ grep CONFIG_SENSORS_FAM15H_POWER /boot/config-4.12.10
> CONFIG_SENSORS_FAM15H_POWER=m
> grep CONFIG_SENSORS_K10TEMP /boot/config-4.12.10
> CONFIG_SENSORS_K10TEMP=m
>
> $ lsmod | grep temp
> k10temp                16384  0
> $ lsmod | grep fam15
> fam15h_power           16384  0
>
> does this apply to your kernel?
>

​I am going to suggest to the asus support folks that I might have
misconnected the cpu fan up to the motherboard.

I already told them that I wasn't sure if I was using a 3 pin instead of a
4 pin lead which might be a limitation here.

The Windows software diagnostics might also give clues to an erroneous mobo
hook up here.

I need to use all the divining rods available on this.

Regards

MF







​


>
> regards
>
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web