New toy need a little help...

sinister · 2016-01-25 07:16:37

nothing... ive tried every variable on the conky docs page on both my laptops.

sinister · 2016-01-25 15:56:28

output from inxi

snstr@hp-notebook:~$ inxi
CPU~Dual core AMD E-300 APU with Radeon HD Graphics (-MCP-) clocked at Min:780.000Mhz Max:1114.000Mhz Kernel~3.16.0-4-amd64 x86_64 Up~49 min Mem~474.8/3562.4MB HDD~320.1GB(2.1% used) Procs~150 Client~Shell inxi~2.1.28

output from sensors-detect & sensors

snstr@hp-notebook:~$ sudo sensors-detect
# sensors-detect revision 6209 (2014-01-14 22:51:58 +0100)
# System: Hewlett-Packard HP 2000 Notebook PC [0886130003305910000620100] (laptop)
# Board: Hewlett-Packard 188B

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   Success!
    (driver `k10temp')
AMD Family 15h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0x8517
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): 
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): 
Using driver `i2c-piix4' for device 0000:00:14.0: AMD Hudson-2 SMBus
Module i2c-dev loaded successfully.

Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x94 (i2c-4)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x95 (i2c-5)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x96 (i2c-6)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x97 (i2c-7)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-8)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: SMBus PIIX4 adapter at 0b20 (i2c-9)
Do you want to scan it? (YES/no/selectively): 


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

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 12h and 14h thermal sensors' (confidence: 9)

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK
Unloading cpuid... OK

snstr@hp-notebook:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +52.0°C  (crit = +120.0°C)

radeon-pci-0008
Adapter: PCI adapter
temp1:        +51.0°C  (crit = +120.0°C, hyst = +90.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +52.2°C  (high = +70.0°C)
                       (crit = +100.0°C, hyst = +97.0°C)

there has to be something im missing a module i need to load? ive exhausted myself googling. and lm-sensors.org is down so i cant look through the config files there.

Sector11 · 2016-01-25 16:34:52

Doesn't look good.

According to your "sensors" output you have no fan speeds.

Maybe (note the italics - I'm thinking out loud on the keyboard: fancontrol

 25 Jan 16 @ 13:27:37 ~
  $ sho fancontrol
aptitude show filename
Package: fancontrol               
State: not installed
Version: 1:3.3.5-2
Priority: extra
Section: utils
Maintainer: Aurelien Jarno <aurel32@debian.org>
Architecture: all
Uncompressed Size: 74.8 k
Depends: lsb-base (>= 3.2-13), init-system-helpers (>= 1.18~)
Conflicts: lm-sensors (< 1:3.1.1-6), lm-sensors (< 1:3.1.1-6)
Replaces: lm-sensors (< 1:3.1.1-6), lm-sensors (< 1:3.1.1-6)
Description: utilities to read temperature/voltage/fan sensors
 Lm-sensors is a hardware health monitoring package for Linux. It allows you to access information from
 temperature, voltage, and fan speed sensors. It works with most newer systems. 
 
 This package contains a daemon that calculates fan speeds from temperatures and sets the corresponding PWM
 outputs to the computed values.
Homepage: http://www.lm-sensors.org

Tags: admin::hardware, hardware::TODO, implemented-in::shell, interface::daemon, role::program, scope::utility,
      use::driver
 
 25 Jan 16 @ 13:27:49 ~
  $

Installed to take a look ... read the man pade and removed. Not my first choice:

WARNING
       Please be careful when using the fan control features of your mainboard, in addition to  the  risk  of
       burning  your CPU, at higher temperatures there will be a higher wearout of your other hardware compo‐
       nents, too. So if you plan to use these components in 50 years, maybe you shouldn't use fancontrol  at
       all.  Also please keep in mind most fans aren't designed to be powered by a PWMed voltage.

       In  practice  it  doesn't seem to be a major issue, the fans will get slightly warmer, just be sure to
       have a temperature alarm and/or shutdown call, in case some fan fails, because you probably won't hear
       it anymore ;)

ohnonot · 2016-01-25 16:44:05

it looks like your system is not detecting any fans (*).
i'm not sure whether there's other linux tools that can do that.
according to this page you can also look directly in /sys/class/hwmon.
try this command:

grep -Ri fan /sys/class/hwmon/* 2>/dev/null

(you must cancel it after a few seconds, with ctrl+c; grep goes into an endless loop)
when i run this command, i get one result that talks about fan speed:

/sys/class/hwmon/hwmon0/subsystem/hwmon1/fan1_label:CPU FAN Speed

so i guess the file "/sys/class/hwmon/hwmon0/subsystem/hwmon1/fan1_label" contains the info i want.
afaics, this would translate into

${hwmon 1 fan 1}

in conky.

(*)
on my system it looks like this:

$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +35.0°C  (crit = +100.0°C)

atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage:      +1.22 V  (min =  +0.85 V, max =  +1.60 V)
 +3.3 Voltage:      +3.30 V  (min =  +3.00 V, max =  +3.60 V)
 +5.0 Voltage:      +5.09 V  (min =  +4.50 V, max =  +5.50 V)
+12.0 Voltage:     +12.13 V  (min = +11.20 V, max = +13.20 V)
CPU FAN Speed:     1622 RPM  (min =    0 RPM, max = 1800 RPM)
CHASSIS FAN Speed:    0 RPM  (min =    0 RPM, max = 1800 RPM)
CPU Temperature:    +35.0°C  (high = +90.0°C, crit = +125.0°C)
MB Temperature:     +41.0°C  (high = +45.0°C, crit = +90.0°C)

k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:   +37.0°C  
Core0 Temp:   +23.0°C  
Core1 Temp:   +41.0°C  
Core1 Temp:   +28.0°C

yes, i have only 1 fan in there.

edit:
how's your re-install coming along?
did you go back into bios to re-enable that fan reading?

Last edited by ohnonot (2016-01-25 16:51:32)

sinister · 2016-01-26 00:04:16

The re-install went fine. Running Debian 8.3 on 4.3.0-0.bpo.1-amd64 kernel. I re-installed firmware-linux-nonfree, firmware-linux-free, and firmware-linux, aswell as lm-sensors. I also installed acpi, when i run

snstr@hp-notebook:~$ acpi -c
Cooling 0: Fan 1 of 1

So i guess that's a start right?

edit: i tried BL 64 but using xfce4 some of the openbox stuff conflicts or something? Tbh I'm feeling a bit clueless atm...

Last edited by sinister (2016-01-26 00:08:03)

Sector11 · 2016-01-26 00:31:22

OH Yea ... there's a light on somewhere.
Did you install inxi? Hope so ... see below.

Did you run

sudo sensors-detect

If not do so and answer yes to "everything" and post the results of sensors && inxi -s

- sensors will tell you 'what' you have: ie: fan1 3600, temp1 51°, temp2 52°,
- 'inxi -s' will tell you what it belongs to ie: Fan Speeds: cpu 3600, mobo: 52° cpu: 51°

Makes it easier to match thing up in conky.

If you have already run sensors-detect ... or after doing so, please post the contents of: /etc/modules (mine) :

  $ cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.


# Generated by sensors-detect on Mon Jul  6 19:02:20 2015
# Chip drivers
f71882fg

I use "platform" - more reliable than hwmon that at time moves things around.

${alignc}${color7}Sensors
${color7}CPU${color} ${platform f71882fg.2560 temp 1}°
 ${color7}MB${color} ${platform f71882fg.2560 temp 2}°
${color7}SDA${color} ${hddtemp /dev/sda}°
${color7}GPU${color} ${nvidia temp}°
${color7}CPU Fan${color}
  ${platform f71882fg.2560 fan 1}

sinister · 2016-01-26 00:44:15

Yeah i reinstalled inxi & lm-sensors after the kernel upgrade and ran sensors-detect. Here's the output of sensors & inxi

snstr@hp-notebook:~$ sensors
radeon-pci-0008
Adapter: PCI adapter
temp1:        +54.0°C  (crit = +120.0°C, hyst = +90.0°C)

acpitz-virtual-0
Adapter: Virtual device
temp1:        +55.0°C  (crit = +120.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +55.0°C  (high = +70.0°C)
                       (crit = +100.0°C, hyst = +97.0°C)

snstr@hp-notebook:~$ inxi -s
Sensors:   System Temperatures: cpu: 54.2C mobo: N/A gpu: 56.0 
           Fan Speeds (in rpm): cpu: N/A

And cat /etc/modules

snstr@hp-notebook:~$  cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

Showing no modules loaded. After the kernel upgrade I get a Failed to start Load Kernel Modules during boot up.

Sector11 · 2016-01-26 01:31:52

Ooooooooooooo try this:

/etc/init.d/kmod start

Xing fingers, toes N eyes!

Because 'sometimes':

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

  28 Aug 12 | 14:18:20 ~
         $ /etc/init.d/kmod start
[info] Loading kernel module fuse.
[info] Loading kernel module loop.
[info] Loading kernel module f71882fg.
[info] Loading kernel module f71882fg.
[info] Loading kernel module f71882fg.
[info] Loading kernel module nvidia.
[info] Loading kernel module f71882fg.
[info] Loading kernel module f71882fg.

  28 Aug 12 | 14:18:47 ~
         $

Look at that date!

Xing continues...

sinister · 2016-01-26 02:11:09

tried with and without sudo...

snstr@hp-notebook:~$ sudo /etc/init.d/kmod start
[sudo] password for snstr: 
[....] Starting kmod (via systemctl): kmod.serviceJob for systemd-modules-load.service failed. See 'systemctl status systemd-modules-load.service' and 'journalctl -xn' for details.
 failed!
snstr@hp-notebook:~$

edit:
Booted into 3.16.0-4-amd64 kernel and the above loaded.

Last edited by sinister (2016-01-26 02:14:38)

ohnonot · 2016-01-26 06:16:18

^ ok, so how is all this going (everything posted up to here) with the 3.16 kernel???

have you tried the suggestions from my previous post?

sinister wrote:

i tried BL 64 but using xfce4 some of the openbox stuff conflicts or something? Tbh I'm feeling a bit clueless atm...

i think you should start a separate thread for this.

Last edited by ohnonot (2016-01-26 06:17:49)

sinister · 2016-01-26 08:23:35

ohnonot wrote:

^ ok, so how is all this going (everything posted up to here) with the 3.16 kernel???
have you tried the suggestions from my previous post?

Yes I did and there where entries that said fan but none said fan speed or fan rpm

As far as xfce4 on BL it acts totally different than it does when i install the Debian Jessie Xfce4 iso. I'll fire up the Acer laptop tomorrow, i have BL 32bit on it and installed xfce, see if i can pinpoint and describe some of the bugs or "weirdness". It's already bit past 3am here. When i installed Xfce i didn't remove openbox, possibly some of the config files are conflicting? I honestly don't know.

I seriously appreciate the awesome support and help that all have contributed here. Many thanks to all of you!

becker_11 · 2016-02-07 09:08:42

Okay I get that legacy support was needed to boot "from" usb however once you've installed to HD you "aren't" booting from usb any more so why can't you turn legacy mode off now and the fan speed should appear again in bios?

#21 2016-01-25 07:16:37

Re: New toy need a little help...

#22 2016-01-25 15:56:28

Re: New toy need a little help...

#23 2016-01-25 16:34:52

Re: New toy need a little help...

#24 2016-01-25 16:44:05

Re: New toy need a little help...

#25 2016-01-26 00:04:16

Re: New toy need a little help...

#26 2016-01-26 00:31:22

Re: New toy need a little help...

#27 2016-01-26 00:44:15

Re: New toy need a little help...

#28 2016-01-26 01:31:52

Re: New toy need a little help...

#29 2016-01-26 02:11:09

Re: New toy need a little help...

#30 2016-01-26 06:16:18

Re: New toy need a little help...

#31 2016-01-26 08:23:35

Re: New toy need a little help...

#32 2016-02-07 09:08:42

Re: New toy need a little help...

Board footer