Why doesn't ACPI report voltage?

u666sa

New Member
Joined
Nov 26, 2019
Messages
24
Reaction score
6
Credits
122
Point me to the right direction. I used to have Fedora with XFCE and it showed voltage in sensors plugin. Now I switched distros to Ubuntu, and sensors plugin does not show voltage. I even tried to compile a brand new version from github and nothing special about it, didn't fix the problem. Tell me which way to look into?

I have Ubuntu on primary HDD and I have a scrap HDD which I can plugin with Fedora, if something needs to be looked up on Fedora I can do that quickly.
 


acpi isn't what shows the temperature and voltage. This is usually used to "auto-restart" computers that lose power, when the power comes back on.

In fedora lm_sensors is the package that shows the temp and voltage.


This isn't installed on Ubuntu by default.

 
This isn't installed on Ubuntu by default.
By default no, but I did install it.

libsensors4/bionic,now 1:3.4.0-4 amd64 [installed,automatic]
library to read temperature/voltage/fan sensors

libsensors4-dev/bionic,now 1:3.4.0-4 amd64 [installed]
lm-sensors development kit

lm-sensors/bionic,now 1:3.4.0-4 amd64 [installed]
utilities to read temperature/voltage/fan sensors


Running sensors-detect only detects core temps.


Code:
# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +48.0°C  (high = +80.0°C, crit = +90.0°C)
Core 2:       +48.0°C  (high = +80.0°C, crit = +90.0°C)

root@mb2:/home/alex# sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: Acer Aspire 5742G [V1.30] (laptop)
# Kernel: 5.3.0-42-generic x86_64
# Processor: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz (6/37/5)

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): y
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...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 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): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
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): YES
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): YES
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 3400/5 Series (PCH)
Module i2c-i801 loaded successfully.

Next adapter: i915 gmbus ssc (i2c-0)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: i915 gmbus vga (i2c-1)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: i915 gmbus panel (i2c-2)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: i915 gmbus dpb (i2c-4)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: i915 gmbus dpd (i2c-5)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: DPDDC-B (i2c-6)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: NVIDIA i2c adapter 0 at 1:00.0 (i2c-7)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-8)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: NVIDIA i2c adapter 2 at 1:00.0 (i2c-9)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: NVIDIA i2c adapter 5 at 1:00.0 (i2c-10)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: NVIDIA i2c adapter 6 at 1:00.0 (i2c-11)
Do you want to scan it? (yes/NO/selectively): YES

Next adapter: SMBus I801 adapter at 4000 (i2c-12)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x48
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)


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

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)YES
Successful!

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

Unloading i2c-i801... OK
Unloading cpuid... OK

root@mb2:/home/alex# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +49.0°C  (high = +80.0°C, crit = +90.0°C)
Core 2:       +48.0°C  (high = +80.0°C, crit = +90.0°C)
 
Sorry, it's a link to nowhere. I did read that article. Perhaps I missed something? I did run sensors detect and answered YES to everything and config file was written. But all it did detect is cores, as shown in my previous post.
 
That’s just the way it is with some systems.
The sensor detect script will attempt to find sensors on various bits of hardware. But there’s no guarantee it will find any sensors. That depends entirely on the hardware.

On all of the Linux PCs I’ve owned (Mostly laptops), the only sensors detected have been the temperature sensors on each core in the CPU.

The only exception was an old desktop, which had some additional voltage sensors on the motherboard.
 
On all of the Linux PCs I’ve owned (Mostly laptops
You don’t understand my delema. Same exact laptop, Fedora shows battery voltage, Ubuntu does not. As a matter of fact if I run sensors detect in Fedora I get same exact output, but xfce sensors app shows battery voltage.... So I don’t know what gives.
 

Staff online

Members online


Top