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

[Michael Fothergill]

On 28 December 2017 at 18:14, deloptes  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
> k10temp16384  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
>
>

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

[Michael Fothergill]

On 28 December 2017 at 18:14, deloptes  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
> k10temp16384  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
> k10temp16384  0
> mikef@bong:~$
>
>
​Cheers

MF​



>
> regards
>
>

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

[Michael Fothergill]

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

>
>
> On 28 December 2017 at 18:14, deloptes  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
>> k10temp16384  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
>>
>>
>

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

[Michael Fothergill]

On 28 December 2017 at 18:14, deloptes  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
> k10temp16384  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
>
>

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

[deloptes]

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
k10temp16384  0
$ lsmod | grep fam15
fam15h_power   16384  0

does this apply to your kernel?

regards

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

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, 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 
> alias:  cpu:type:x86,venfam*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?
>
>

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

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, 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 
> alias:  cpu:type:x86,venfam*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?
>
>

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

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, 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 
> alias:  cpu:type:x86,venfam*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​

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

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, 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 
> alias:  cpu:type:x86,venfam*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?
>
>

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

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, 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 
> alias:  cpu:type:x86,venfam*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?
>

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

[Michael Fothergill]

On 28 December 2017 at 13:55, Greg Wooledge  wrote:

> On Thu, Dec 28, 2017 at 01:11:56PM +, 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 
> alias:  cpu:type:x86,venfam*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​
​

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

[Greg Wooledge]

On Thu, Dec 28, 2017 at 01:11:56PM +, 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 
alias:  cpu:type:x86,venfam*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?

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

[Michael Fothergill]

Dear All,

The output of lsmod looks like this:

root@bong:/boot# lsmod

Module  Size  Used by
uinput 20480  1
snd_hda_codec_hdmi 49152  4
edac_mce_amd   28672  0
edac_core  57344  0
kvm_amd  2179072  0
kvm   589824  1 kvm_amd
snd_hda_codec_realtek90112  1
eeepc_wmi  16384  0
asus_wmi   28672  1 eeepc_wmi
sparse_keymap  16384  1 asus_wmi
serio_raw  16384  0
snd_hda_codec_generic69632  1 snd_hda_codec_realtek
snd_hda_intel  36864  6
snd_hda_codec 135168  4
snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_core   81920  5
snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
rfkill 24576  4 asus_wmi
irqbypass  16384  1 kvm
crct10dif_pclmul   16384  0
fam15h_power   16384  0
k10temp16384  0
pcspkr 16384  0
crc32_pclmul   16384  0
snd_hwdep  16384  1 snd_hda_codec
snd_pcm   110592  5
snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi
ghash_clmulni_intel16384  0
evdev  24576  9
snd_timer  32768  1 snd_pcm
snd86016  19
snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek,snd_pcm
shpchp 36864  0
sg 32768  0
soundcore  16384  1 snd
tpm_infineon   20480  0
sp5100_tco 16384  0
fuse   98304  1
it87   57344  0
hwmon_vid  16384  1 it87
parport_pc 28672  0
ppdev  20480  0
lp 20480  0
sunrpc344064  1
parport49152  3 lp,parport_pc,ppdev
ip_tables  24576  0
x_tables   36864  1 ip_tables
autofs440960  2
ext4  585728  1
crc16  16384  1 ext4
jbd2  106496  1 ext4
crc32c_generic 16384  0
fscrypto   28672  1 ext4
ecb16384  0
mbcache16384  2 ext4
hid_generic16384  0
usbhid 53248  0
hid   122880  2 hid_generic,usbhid
sd_mod 45056  3
ohci_pci   16384  0
crc32c_intel   24576  0
aesni_intel   167936  1
aes_x86_64 20480  1 aesni_intel
glue_helper16384  1 aesni_intel
lrw16384  1 aesni_intel
gf128mul   16384  1 lrw
ablk_helper16384  1 aesni_intel
cryptd 24576  3 ablk_helper,ghash_clmulni_intel,aesni_intel
nouveau  1544192  9
mxm_wmi16384  1 nouveau
i2c_piix4  24576  0
video  40960  2 asus_wmi,nouveau
i2c_algo_bit   16384  1 nouveau
r8169  81920  0
ttm98304  1 nouveau
ahci   36864  2
mii16384  1 r8169
xhci_pci   16384  0
libahci32768  1 ahci
drm_kms_helper155648  1 nouveau
ehci_pci   16384  0
ohci_hcd   53248  1 ohci_pci
xhci_hcd  188416  1 xhci_pci
ehci_hcd   81920  1 ehci_pci
libata249856  2 ahci,libahci
drm   360448  12 nouveau,ttm,drm_kms_helper
usbcore   249856  7
usbhid,ehci_hcd,ohci_pci,xhci_pci,ohci_hcd,xhci_hcd,ehci_pci
usb_common 16384  1 usbcore
scsi_mod  225280  3 sd_mod,libata,sg
wmi16384  3 asus_wmi,mxm_wmi,nouveau
button 16384  1 nouveau
root@bong:/boot#

I tried running


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

Regards

MF







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

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

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

[Michael Fothergill]

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_MAX=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.fotherg...@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.fotherg...@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 

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

[Michael Fothergill]

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.fotherg...@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-
> 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
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

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

[Michael Fothergill]

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