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?










share|improve this question


























    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?










    share|improve this question
























      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?










      share|improve this question













      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 26 at 20:50









      b00n

      63




      63






















          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






          share|improve this answer





















          • 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










          • 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













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          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

























          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






          share|improve this answer





















          • 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










          • 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

















          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






          share|improve this answer





















          • 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










          • 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















          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






          share|improve this answer












          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







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 27 at 14:28









          rtaft

          407211




          407211












          • 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










          • 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




















          • 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










          • 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


















          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




















          draft saved

          draft discarded




















































          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.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          mysqli_query(): Empty query in /home/lucindabrummitt/public_html/blog/wp-includes/wp-db.php on line 1924

          How to change which sound is reproduced for terminal bell?

          Can I use Tabulator js library in my java Spring + Thymeleaf project?