How to convert “sensor” names to a /sys path?
up vote
1
down vote
favorite
Programs such as sensor
list sensors by name, such as package ID 0
and core 0
. However, /etc/fancontrol
uses things like /sys/device/...
. How do I figure out the path from the name?
fan temperature devices fancontrol
add a comment |
up vote
1
down vote
favorite
Programs such as sensor
list sensors by name, such as package ID 0
and core 0
. However, /etc/fancontrol
uses things like /sys/device/...
. How do I figure out the path from the name?
fan temperature devices fancontrol
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Programs such as sensor
list sensors by name, such as package ID 0
and core 0
. However, /etc/fancontrol
uses things like /sys/device/...
. How do I figure out the path from the name?
fan temperature devices fancontrol
Programs such as sensor
list sensors by name, such as package ID 0
and core 0
. However, /etc/fancontrol
uses things like /sys/device/...
. How do I figure out the path from the name?
fan temperature devices fancontrol
fan temperature devices fancontrol
asked Nov 26 at 20:50
b00n
63
63
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Take a look in /etc/sensors3.conf. This is where sensors will label and convert many of the values in /sys/devices/platform/* to what you see in the sensors output. You may also be able to find custom entries on the internet for your motherboard, and could even create your own if you know how.
For instance, my board is nct6791-isa-0290 and there is a default entry for "nct6791-*" already in /etc/sensors.conf. After searching around, I found several versions of other configs for my motherboard out there, like this thread that discusses how it was generated. http://www.spinics.net/lists/lm-sensors/msg42249.html
On my system,sensors
shows one calledPackage id 0
. I looked in/etc/sensors3.conf
but I do not see anything like that -- not even a partial match. Underpsensor
, I see the same name. If I right-click on it and look at details, it describes it aslmsensor coretemp-isa-0000
, but again I do not see anything obvious in the.conf
file. Is there another place to look for definitions? Thanks.
– b00n
Nov 28 at 16:45
What you see in coretemp is hard coded into the driver. github.com/torvalds/linux/blob/master/drivers/hwmon/coretemp.c
– rtaft
Nov 28 at 18:33
Thanks, this led me to the answer. For example,/sys/devices/platform/coretemp.0/hwmon/hwmon1
has various filestemp*_*
-- and the*_label
for each is the label used bysensors
andpsensor
. For example, on my systemtemp1_label
isPhysical id 0
,temp2_label
isCore 0
, and so on. So I can read the_label
file and that tells me the corresponding/sys/device/...
to use.
– b00n
Dec 6 at 8:17
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Take a look in /etc/sensors3.conf. This is where sensors will label and convert many of the values in /sys/devices/platform/* to what you see in the sensors output. You may also be able to find custom entries on the internet for your motherboard, and could even create your own if you know how.
For instance, my board is nct6791-isa-0290 and there is a default entry for "nct6791-*" already in /etc/sensors.conf. After searching around, I found several versions of other configs for my motherboard out there, like this thread that discusses how it was generated. http://www.spinics.net/lists/lm-sensors/msg42249.html
On my system,sensors
shows one calledPackage id 0
. I looked in/etc/sensors3.conf
but I do not see anything like that -- not even a partial match. Underpsensor
, I see the same name. If I right-click on it and look at details, it describes it aslmsensor coretemp-isa-0000
, but again I do not see anything obvious in the.conf
file. Is there another place to look for definitions? Thanks.
– b00n
Nov 28 at 16:45
What you see in coretemp is hard coded into the driver. github.com/torvalds/linux/blob/master/drivers/hwmon/coretemp.c
– rtaft
Nov 28 at 18:33
Thanks, this led me to the answer. For example,/sys/devices/platform/coretemp.0/hwmon/hwmon1
has various filestemp*_*
-- and the*_label
for each is the label used bysensors
andpsensor
. For example, on my systemtemp1_label
isPhysical id 0
,temp2_label
isCore 0
, and so on. So I can read the_label
file and that tells me the corresponding/sys/device/...
to use.
– b00n
Dec 6 at 8:17
add a comment |
up vote
0
down vote
Take a look in /etc/sensors3.conf. This is where sensors will label and convert many of the values in /sys/devices/platform/* to what you see in the sensors output. You may also be able to find custom entries on the internet for your motherboard, and could even create your own if you know how.
For instance, my board is nct6791-isa-0290 and there is a default entry for "nct6791-*" already in /etc/sensors.conf. After searching around, I found several versions of other configs for my motherboard out there, like this thread that discusses how it was generated. http://www.spinics.net/lists/lm-sensors/msg42249.html
On my system,sensors
shows one calledPackage id 0
. I looked in/etc/sensors3.conf
but I do not see anything like that -- not even a partial match. Underpsensor
, I see the same name. If I right-click on it and look at details, it describes it aslmsensor coretemp-isa-0000
, but again I do not see anything obvious in the.conf
file. Is there another place to look for definitions? Thanks.
– b00n
Nov 28 at 16:45
What you see in coretemp is hard coded into the driver. github.com/torvalds/linux/blob/master/drivers/hwmon/coretemp.c
– rtaft
Nov 28 at 18:33
Thanks, this led me to the answer. For example,/sys/devices/platform/coretemp.0/hwmon/hwmon1
has various filestemp*_*
-- and the*_label
for each is the label used bysensors
andpsensor
. For example, on my systemtemp1_label
isPhysical id 0
,temp2_label
isCore 0
, and so on. So I can read the_label
file and that tells me the corresponding/sys/device/...
to use.
– b00n
Dec 6 at 8:17
add a comment |
up vote
0
down vote
up vote
0
down vote
Take a look in /etc/sensors3.conf. This is where sensors will label and convert many of the values in /sys/devices/platform/* to what you see in the sensors output. You may also be able to find custom entries on the internet for your motherboard, and could even create your own if you know how.
For instance, my board is nct6791-isa-0290 and there is a default entry for "nct6791-*" already in /etc/sensors.conf. After searching around, I found several versions of other configs for my motherboard out there, like this thread that discusses how it was generated. http://www.spinics.net/lists/lm-sensors/msg42249.html
Take a look in /etc/sensors3.conf. This is where sensors will label and convert many of the values in /sys/devices/platform/* to what you see in the sensors output. You may also be able to find custom entries on the internet for your motherboard, and could even create your own if you know how.
For instance, my board is nct6791-isa-0290 and there is a default entry for "nct6791-*" already in /etc/sensors.conf. After searching around, I found several versions of other configs for my motherboard out there, like this thread that discusses how it was generated. http://www.spinics.net/lists/lm-sensors/msg42249.html
answered Nov 27 at 14:28
rtaft
407211
407211
On my system,sensors
shows one calledPackage id 0
. I looked in/etc/sensors3.conf
but I do not see anything like that -- not even a partial match. Underpsensor
, I see the same name. If I right-click on it and look at details, it describes it aslmsensor coretemp-isa-0000
, but again I do not see anything obvious in the.conf
file. Is there another place to look for definitions? Thanks.
– b00n
Nov 28 at 16:45
What you see in coretemp is hard coded into the driver. github.com/torvalds/linux/blob/master/drivers/hwmon/coretemp.c
– rtaft
Nov 28 at 18:33
Thanks, this led me to the answer. For example,/sys/devices/platform/coretemp.0/hwmon/hwmon1
has various filestemp*_*
-- and the*_label
for each is the label used bysensors
andpsensor
. For example, on my systemtemp1_label
isPhysical id 0
,temp2_label
isCore 0
, and so on. So I can read the_label
file and that tells me the corresponding/sys/device/...
to use.
– b00n
Dec 6 at 8:17
add a comment |
On my system,sensors
shows one calledPackage id 0
. I looked in/etc/sensors3.conf
but I do not see anything like that -- not even a partial match. Underpsensor
, I see the same name. If I right-click on it and look at details, it describes it aslmsensor coretemp-isa-0000
, but again I do not see anything obvious in the.conf
file. Is there another place to look for definitions? Thanks.
– b00n
Nov 28 at 16:45
What you see in coretemp is hard coded into the driver. github.com/torvalds/linux/blob/master/drivers/hwmon/coretemp.c
– rtaft
Nov 28 at 18:33
Thanks, this led me to the answer. For example,/sys/devices/platform/coretemp.0/hwmon/hwmon1
has various filestemp*_*
-- and the*_label
for each is the label used bysensors
andpsensor
. For example, on my systemtemp1_label
isPhysical id 0
,temp2_label
isCore 0
, and so on. So I can read the_label
file and that tells me the corresponding/sys/device/...
to use.
– b00n
Dec 6 at 8:17
On my system,
sensors
shows one called Package id 0
. I looked in /etc/sensors3.conf
but I do not see anything like that -- not even a partial match. Under psensor
, I see the same name. If I right-click on it and look at details, it describes it as lmsensor coretemp-isa-0000
, but again I do not see anything obvious in the .conf
file. Is there another place to look for definitions? Thanks.– b00n
Nov 28 at 16:45
On my system,
sensors
shows one called Package id 0
. I looked in /etc/sensors3.conf
but I do not see anything like that -- not even a partial match. Under psensor
, I see the same name. If I right-click on it and look at details, it describes it as lmsensor coretemp-isa-0000
, but again I do not see anything obvious in the .conf
file. Is there another place to look for definitions? Thanks.– b00n
Nov 28 at 16:45
What you see in coretemp is hard coded into the driver. github.com/torvalds/linux/blob/master/drivers/hwmon/coretemp.c
– rtaft
Nov 28 at 18:33
What you see in coretemp is hard coded into the driver. github.com/torvalds/linux/blob/master/drivers/hwmon/coretemp.c
– rtaft
Nov 28 at 18:33
Thanks, this led me to the answer. For example,
/sys/devices/platform/coretemp.0/hwmon/hwmon1
has various files temp*_*
-- and the *_label
for each is the label used by sensors
and psensor
. For example, on my system temp1_label
is Physical id 0
, temp2_label
is Core 0
, and so on. So I can read the _label
file and that tells me the corresponding /sys/device/...
to use.– b00n
Dec 6 at 8:17
Thanks, this led me to the answer. For example,
/sys/devices/platform/coretemp.0/hwmon/hwmon1
has various files temp*_*
-- and the *_label
for each is the label used by sensors
and psensor
. For example, on my system temp1_label
is Physical id 0
, temp2_label
is Core 0
, and so on. So I can read the _label
file and that tells me the corresponding /sys/device/...
to use.– b00n
Dec 6 at 8:17
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1096289%2fhow-to-convert-sensor-names-to-a-sys-path%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown