Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Temperature Reading on AMD

    Scheduled Pinned Locked Moved Hardware
    55 Posts 14 Posters 24.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      Fahrenhe1t
      last edited by

      Just sent you a PM.

      1 Reply Last reply Reply Quote 0
      • F
        Fahrenhe1t
        last edited by

        Using AT&T 4G, I VPN'd back home.  I have iPerf3 running on another box internally and ran a test.  I got 3.61 Mbits/sec.

        Connecting to a wifi network with 10mbps up and down, I ran the test again and got 8.47mbps.  I'll see if I can find a faster wifi network to test on.

        **Update, got 17.9mbps connecting back to VPN on a friend's wifi with 40down/20up.

        1 Reply Last reply Reply Quote 0
        • J
          jpass022
          last edited by

          Just upgraded to 2.3.1 and temp widget is broken again… :(
          redid your procedure and it's back...  :)

          1 Reply Last reply Reply Quote 0
          • F
            Fahrenhe1t
            last edited by

            @jpass022:

            Just upgraded to 2.3.1 and temp widget is broken again… :(
            redid your procedure and it's back...  :)

            Thanks for the heads up, mine just did the same thing on 2.3.1 (not to be confused with 2.3_1  :o)

            1 Reply Last reply Reply Quote 0
            • J
              jpass022
              last edited by

              haven't done 2.3.1_1 yet…

              1 Reply Last reply Reply Quote 0
              • F
                Fahrenhe1t
                last edited by

                I just did, and had to reload amdtemp.ko.  I ended up writing a shell script to copy the files and enable the service.

                1 Reply Last reply Reply Quote 0
                • J
                  jpass022
                  last edited by

                  Wish they would include your mod. 2.3.2 time….

                  1 Reply Last reply Reply Quote 0
                  • F
                    Fahrenhe1t
                    last edited by

                    @jpass022:

                    Wish they would include your mod. 2.3.2 time….

                    Same.  I think FreeBSD has to include it in their release though.  Someone else already submitted a bug (https://lists.freebsd.org/pipermail/freebsd-bugs/2016-February/066274.html); not sure how to get FreeBSD to include the fix in a release though…

                    1 Reply Last reply Reply Quote 0
                    • M
                      markn62
                      last edited by

                      Fahrenhe1t, I'm running pfSense 2.3.2p1 w/ A6-5400K CPU with set to AMD and dashboard temps read 0C to 1C, varies. No where close to accurate.  So tried your recompiled 10.3 amdtemp.ko file. Didn't change anything. My two other boxes with Intel CPU and A6-6400K work fine without a modified amdtemp.ko file.  Ideas, mistakes I may have made?

                      1 Reply Last reply Reply Quote 0
                      • F
                        Fahrenhe1t
                        last edited by

                        @markn62:

                        Fahrenhe1t, I'm running pfSense 2.3.2p1 w/ A6-5400K CPU with set to AMD and dashboard temps read 0C to 1C, varies. No where close to accurate.  So tried your recompiled 10.3 amdtemp.ko file. Didn't change anything. My two other boxes with Intel CPU and A6-6400K work fine without a modified amdtemp.ko file.  Ideas, mistakes I may have made?

                        Strange!  From the command line, what does the OS report if you run this: sysctl -a | grep temperature

                        1 Reply Last reply Reply Quote 0
                        • M
                          markn62
                          last edited by

                          dev.cpu.1.temperature: 0.0C
                          dev.cpu.0.temperature: 0.0C

                          Same as before the modified file was copied to the box.

                          1 Reply Last reply Reply Quote 0
                          • M
                            markn62
                            last edited by

                            BIOS reports 33C

                            1 Reply Last reply Reply Quote 0
                            • F
                              Fahrenhe1t
                              last edited by

                              Do you know if the temperature is able to be read from a different operating system?

                              Maybe you could boot Ubuntu from USB on your pfSense box (without installing it), install the lm-sensors package, then run: sudo sensors
                              If it returns accurate CPU temperature, then you know it's a problem with FreeBSD not detecting your CPU properly.

                              It looks like the A6-5400K CPU was released in 2012.  If I had to guess, I bet FreeBSD (and the and specifically amdtemp.ko) doesn't detect the CPU properly.  The CPU ID would have to be determined, the new sensor line would have to be added to the amdtemp source code, then it would have to be recompiled with the new CPU information.  I'm just guessing though.

                              1 Reply Last reply Reply Quote 0
                              • M
                                markn62
                                last edited by

                                Thats a good idea but then I still have a broken temperature status. Your right the cpu is a bit old. I think I'll cut my time losses and try an A6-7470K. If it works I'll keep the 5400 as a back up.

                                1 Reply Last reply Reply Quote 0
                                • F
                                  Fahrenhe1t
                                  last edited by

                                  Actually, I think the CPU is fine, it's just that amdtemp.ko isn't always updated with "new" CPU's.  If you don't have any luck with the new CPU, I might be able to try and compile a new amdtemp.ko, you'd just have to tell me what the CPU ID is.  In the source code, the CPU ID's look like this:

                                  
                                  #define        DEVICEID_AMD_MISC14     0x1703
                                  #define        DEVICEID_AMD_MISC15     0x1603
                                  #define        DEVICEID_AMD_MISC16     0x1533
                                  #define        DEVICEID_AMD_MISC16_X3  0X1583
                                  

                                  The last one is the ID for my A10 Micro-6700T.  I have no idea how that can be found though.

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    markn62
                                    last edited by

                                    The newer cpu reports the same. I'll look for the DEVICEID.

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      markn62
                                      last edited by

                                      The only ID I find is 630F81. Not sure where those txt strings come from in the amdtemp.ko file.

                                      1 Reply Last reply Reply Quote 0
                                      • F
                                        Fahrenhe1t
                                        last edited by

                                        Hey, I found a thread which has updated DEVICEID's (http://www.pcengines.info/forums/?page=post&id=795B2ACC-F4B0-4181-9B4A-54EC757D4001&fid=DF5ACB70-99C4-4C61-AFA6-4C0E0DB05B2A).  The guy (Stephan) said he compiled the latest version and uploaded it here: http://s000.tinyupload.com/index.php?file_id=70328254396185987242

                                        Maybe you can try that one?

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          markn62
                                          last edited by

                                          I downloaded the file you linked too, with WinSCP I removed the old /boot/kernel/amdtemp.ko and copied new file to /root, then followed the instructions;

                                          kldunload amdtemp
                                          cp /root/amdtemp.ko /boot/kernel/
                                          kldload /boot/kernel/amdtemp.ko

                                          Still reports 0C.

                                          1 Reply Last reply Reply Quote 0
                                          • Z
                                            z3us
                                            last edited by

                                            I'm receiving:
                                            kldload: an error occurred while loading the module. Please check dmesg(8) for more details.

                                            Followed every step as described.
                                            Using pfSense 2.3.2-RELEASE-p1

                                            Any ideas?

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.