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

    Thermal sensor feature broken

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    15 Posts 5 Posters 3.4k 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.
    • M
      m3usv0x
      last edited by

      As of April 24th, the latest snapshot does not rectify the loss of sensor data.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Are/were you using ACPI or coretemp to read the temperatures?

        Steve

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

          @stephenw10:

          Are/were you using ACPI or coretemp to read the temperatures?

          Steve

          I was and am using coretemp to read temperatures.

          Thank you.

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Try using ACPI instead if your BIOS is sending that info correctly. Other than that I guess the coretemp kernel module isn't being loaded. A whole load of kernel modules were left out of some builds recently so it's probably related.

            You could try loading the module manually to test if it's just not loading or has not been built into the kernel:

            kldload coretemp
            

            If it is in the kernel that command should tell you that.

            Steve

            1 Reply Last reply Reply Quote 0
            • chpalmerC
              chpalmer
              last edited by

              I just did a firmware update on the UTM 510 and lost the thermal sensor as well…

              It was working under 2.1.2

              Triggering snowflakes one by one..
              Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Well I guess 2.2 is still alpha! ;)

                I assume coretemp doesn't appear in dmesg and sysctls don't get created?
                I've had to turn off my xtm5 test box while I'm doing some building work. I'll try and set it up somewhere temporarily.

                Steve

                1 Reply Last reply Reply Quote 0
                • chpalmerC
                  chpalmer
                  last edited by

                  Ive just routed my desktop through this box for the first time and it does all the basic stuff without a hitch other than what is the subject of a new post.

                  But for your entertainment.  ;D

                  $ dmesg
                  Copyright (c) 1992-2014 The FreeBSD Project.
                  Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
                      The Regents of the University of California. All rights reserved.
                  FreeBSD is a registered trademark of The FreeBSD Foundation.
                  FreeBSD 10.0-STABLE #13 7d93aa7(HEAD)-dirty: Sat Apr 26 15:17:54 CDT 2014
                      root@builder-10.0-b3-amd64:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10 amd64
                  FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
                  CPU: Intel(R) Celeron(R) CPU          440  @ 2.00GHz (1995.04-MHz K8-class CPU)
                    Origin = "GenuineIntel"  Id = 0x10661  Family = 0x6  Model = 0x16  Stepping = 1
                    Features=0xafebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,tm,pbe>Features2=0xe31d <sse3,dtes64,mon,ds_cpl,tm2,ssse3,cx16,xtpr,pdcm>AMD Features=0x20100800 <syscall,nx,lm>AMD Features2=0x1 <lahf>TSC: P-state invariant, performance statistics
                  real memory  = 1073741824 (1024 MB)
                  avail memory = 967188480 (922 MB)
                  Event timer "LAPIC" quality 400
                  ACPI APIC Table: <020310 APIC1727>
                  ioapic0 <version 2.0="">irqs 0-23 on motherboard
                  iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                  iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                  module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff805f18a0, 0) error 1
                  iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                  iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                  module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff805f1950, 0) error 1
                  wlan: mac acl policy registered
                  ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                  ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                  module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff805cb3c0, 0) error 1
                  ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                  ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                  module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff805cb470, 0) error 1
                  ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                  ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                  module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff805cb520, 0) error 1
                  iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                  iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                  module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff805f17f0, 0) error 1
                  random: <software, yarrow="">initialized
                  kbd1 at kbdmux0
                  cryptosoft0: <software crypto="">on motherboard
                  padlock0: No ACE support.
                  acpi0: <020310 RSDT1727> on motherboard
                  acpi0: Power Button (fixed)
                  acpi0: reservation of 0, a0000 (3) failed
                  acpi0: reservation of 100000, 3dd00000 (3) failed
                  cpu0: <acpi cpu="">on acpi0
                  attimer0: <at timer="">port 0x40-0x43 irq 0 on acpi0
                  Timecounter "i8254" frequency 1193182 Hz quality 0
                  Event timer "i8254" frequency 1193182 Hz quality 100
                  atrtc0: <at realtime="" clock="">port 0x70-0x71 irq 8 on acpi0
                  Event timer "RTC" frequency 32768 Hz quality 0
                  Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
                  acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
                  pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
                  pci0: <acpi pci="" bus="">on pcib0
                  pcib1: <acpi pci-pci="" bridge="">irq 16 at device 1.0 on pci0
                  pci8: <acpi pci="" bus="">on pcib1
                  pci8: <encrypt decrypt,="" network="" computer="" crypto="">at device 0.0 (no driver attached)
                  vgapci0: <vga-compatible display="">port 0x6800-0x6807 mem 0xfe000000-0xfe3fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0
                  agp0: <intel g41="" svga="" controller="">on vgapci0
                  agp0: aperture size is 256M, detected 32764k stolen memory
                  vgapci0: Boot video device
                  pcib2: <acpi pci-pci="" bridge="">irq 16 at device 28.0 on pci0
                  pci2: <acpi pci="" bus="">on pcib2
                  em0: <intel(r) 1000="" pro="" network="" connection="" 7.3.8="">port 0x9c00-0x9c1f mem 0xfe6e0000-0xfe6fffff,0xfe6dc000-0xfe6dffff irq 16 at device 0.0 on pci2
                  em0: Using MSIX interrupts with 3 vectors
                  pcib3: <acpi pci-pci="" bridge="">irq 17 at device 28.1 on pci0
                  pci3: <acpi pci="" bus="">on pcib3
                  em1: <intel(r) 1000="" pro="" network="" connection="" 7.3.8="">port 0xac00-0xac1f mem 0xfe7e0000-0xfe7fffff,0xfe7dc000-0xfe7dffff irq 17 at device 0.0 on pci3
                  em1: Using MSIX interrupts with 3 vectors
                  pcib4: <acpi pci-pci="" bridge="">irq 18 at device 28.2 on pci0
                  pci4: <acpi pci="" bus="">on pcib4
                  em2: <intel(r) 1000="" pro="" network="" connection="" 7.3.8="">port 0xbc00-0xbc1f mem 0xfe8e0000-0xfe8fffff,0xfe8dc000-0xfe8dffff irq 18 at device 0.0 on pci4
                  em2: Using MSIX interrupts with 3 vectors
                  pcib5: <acpi pci-pci="" bridge="">irq 19 at device 28.3 on pci0
                  pci5: <acpi pci="" bus="">on pcib5
                  em3: <intel(r) 1000="" pro="" network="" connection="" 7.3.8="">port 0xcc00-0xcc1f mem 0xfe9e0000-0xfe9fffff,0xfe9dc000-0xfe9dffff irq 19 at device 0.0 on pci5
                  em3: Using MSIX interrupts with 3 vectors
                  pcib6: <acpi pci-pci="" bridge="">irq 16 at device 28.4 on pci0
                  pci6: <acpi pci="" bus="">on pcib6
                  em4: <intel(r) 1000="" pro="" network="" connection="" 7.3.8="">port 0xdc00-0xdc1f mem 0xfeae0000-0xfeafffff,0xfeadc000-0xfeadffff irq 16 at device 0.0 on pci6
                  em4: Using MSIX interrupts with 3 vectors
                  pcib7: <acpi pci-pci="" bridge="">irq 17 at device 28.5 on pci0
                  pci7: <acpi pci="" bus="">on pcib7
                  em5: <intel(r) 1000="" pro="" network="" connection="" 7.3.8="">port 0xec00-0xec1f mem 0xfebe0000-0xfebfffff,0xfebdc000-0xfebdffff irq 17 at device 0.0 on pci7
                  em5: Using MSIX interrupts with 3 vectors
                  uhci0: <intel 82801g="" (ich7)="" usb="" controller="" usb-a="">port 0x7080-0x709f irq 23 at device 29.0 on pci0
                  usbus0 on uhci0
                  uhci1: <intel 82801g="" (ich7)="" usb="" controller="" usb-b="">port 0x7000-0x701f irq 19 at device 29.1 on pci0
                  usbus1 on uhci1
                  uhci2: <intel 82801g="" (ich7)="" usb="" controller="" usb-c="">port 0x6c00-0x6c1f irq 18 at device 29.2 on pci0
                  usbus2 on uhci2
                  uhci3: <intel 82801g="" (ich7)="" usb="" controller="" usb-d="">port 0x6880-0x689f irq 16 at device 29.3 on pci0
                  usbus3 on uhci3
                  ehci0: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller="">mem 0xfe4ff800-0xfe4ffbff irq 23 at device 29.7 on pci0
                  usbus4: EHCI version 1.0
                  usbus4 on ehci0
                  pcib8: <acpi pci-pci="" bridge="">at device 30.0 on pci0
                  pci1: <acpi pci="" bus="">on pcib8
                  fxp0: <intel 10="" 100="" 82801gb="" (ich7)="" ethernet="">port 0x8c00-0x8c3f mem 0xfe5ff000-0xfe5fffff irq 20 at device 8.0 on pci1
                  miibus0: <mii bus="">on fxp0
                  inphy0: <i82562et 10="" 100="" media="" interface="">PHY 1 on miibus0
                  inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
                  isab0: <pci-isa bridge="">at device 31.0 on pci0
                  isa0: <isa bus="">on isab0
                  atapci0: <intel ich7="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
                  ata0: <ata channel="">at channel 0 on atapci0
                  atapci1: <intel ich7="" sata300="" controller="">port 0x7c00-0x7c07,0x7880-0x7883,0x7800-0x7807,0x7480-0x7483,0x7400-0x740f mem 0xfe4ffc00-0xfe4fffff irq 19 at device 31.2 on pci0
                  ata2: <ata channel="">at channel 0 on atapci1
                  ata3: <ata channel="">at channel 1 on atapci1
                  pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
                  acpi_button0: <power button="">on acpi0
                  uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
                  uart0: console (115200,n,8,1)
                  uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
                  ppc0: <parallel port="">port 0x378-0x37f irq 7 on acpi0
                  ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
                  ppbus0: <parallel port="" bus="">on ppc0
                  lpt0: <printer>on ppbus0
                  lpt0: Interrupt-driven port
                  ppi0: <parallel i="" o="">on ppbus0
                  sc0: <system console="">at flags 0x100 on isa0
                  sc0: VGA <16 virtual consoles, flags=0x100>
                  vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
                  atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
                  atkbd0: <at keyboard="">irq 1 on atkbdc0
                  kbd0 at atkbd0
                  atkbd0: [GIANT-LOCKED]
                  p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
                  Timecounters tick every 1.000 msec
                  IPsec: Initialized Security Association Processing.
                  random: unblocking device.
                  usbus0: 12Mbps Full Speed USB v1.0
                  usbus1: 12Mbps Full Speed USB v1.0
                  usbus2: 12Mbps Full Speed USB v1.0
                  usbus3: 12Mbps Full Speed USB v1.0
                  ugen0.1: <intel>at usbus0
                  uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
                  ugen1.1: <intel>at usbus1
                  uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
                  ugen2.1: <intel>at usbus2
                  uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
                  ugen3.1: <intel>at usbus3
                  uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus3
                  usbus4: 480Mbps High Speed USB v2.0
                  ugen4.1: <intel>at usbus4
                  uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4
                  uhub0: 2 ports with 2 removable, self powered
                  uhub1: 2 ports with 2 removable, self powered
                  uhub2: 2 ports with 2 removable, self powered
                  uhub3: 2 ports with 2 removable, self powered
                  ada0 at ata0 bus 0 scbus0 target 0 lun 0
                  ada0: <ts4gcf133 20110407="">CFA-7 device
                  ada0: Serial Number B049316729126E0000DA
                  ada0: 16.700MB/s transfers (PIO4, PIO 512bytes)
                  ada0: 3823MB (7831152 512 byte sectors: 16H 63S/T 7769C)
                  ada0: Previously was known as ad0
                  Timecounter "TSC" frequency 1995041130 Hz quality 1000
                  Root mount waiting for: usbus4
                  Root mount waiting for: usbus4
                  uhub4: 8 ports with 8 removable, self powered
                  Trying to mount root from ufs:/dev/ufs/pfsense1 [ro,sync,noatime]...
                  WARNING: / was not properly dismounted
                  em0: link state changed to UP
                  pflog0: promiscuous mode enabled
                  em1: link state changed to UP
                  pid 57680 (sh), uid 0: exited on signal 11 (core dumped)
                  pid 58853 (sh), uid 0: exited on signal 11 (core dumped)
                  pid 59758 (sh), uid 0: exited on signal 11 (core dumped)
                  pid 55936 (.pbirun), uid 0: exited on signal 11 (core dumped)
                  pid 57789 (sh), uid 0: exited on signal 11 (core dumped)
                  pid 59396 (.pbirun), uid 0: exited on signal 11 (core dumped)
                  pid 58110 (.pbirun), uid 0: exited on signal 11 (core dumped)
                  pid 56738 (.pbirun), uid 0: exited on signal 11 (core dumped)
                  pid 5185 (sh), uid 0: exited on signal 11
                  pid 5146 (.pbirun), uid 0: exited on signal 11
                  pid 5573 (sh), uid 0: exited on signal 11
                  pid 5044 (.pbirun), uid 0: exited on signal 11
                  em1: link state changed to DOWN
                  em1: link state changed to UP
                  fxp0: link state changed to DOWN</ts4gcf133></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></cpu></at></keyboard></generic></system></parallel></printer></parallel></parallel></power></serial></ata></ata></intel></ata></intel></isa></pci-isa></i82562et></mii></intel></acpi></acpi></intel></intel></intel></intel></intel></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel></vga-compatible></encrypt></acpi></acpi></acpi></acpi></at></at></acpi></software></software,></version></lahf></syscall,nx,lm></sse3,dtes64,mon,ds_cpl,tm2,ssse3,cx16,xtpr,pdcm></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,tm,pbe> 
                  

                  Triggering snowflakes one by one..
                  Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

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

                    @stephenw10:

                    Well I guess 2.2 is still alpha! ;)

                    I assume coretemp doesn't appear in dmesg and sysctls don't get created?
                    I've had to turn off my xtm5 test box while I'm doing some building work. I'll try and set it up somewhere temporarily.

                    Steve

                    Point being is that it was my hope that in reporting an issue, I was helping with the progress of working on the build.

                    Having said thus, entering kldload coretemp restored thermal sensor functionality.

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Ah, so the module is included but not built into the kernel. Perhaps that's a deliberate change or if not maybe a useful clue for the devs.

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • jimpJ
                        jimp Rebel Alliance Developer Netgate
                        last edited by

                        It's always been that way for coretemp. That's why the selector is there to pick the thermal sensor module on System > Advanced on the Misc tab. It should be doing a kldload for whichever module is selected in that area.

                        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                        Need help fast? Netgate Global Support!

                        Do not Chat/PM for help!

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

                          @jimp:

                          It's always been that way for coretemp. That's why the selector is there to pick the thermal sensor module on System > Advanced on the Misc tab. It should be doing a kldload for whichever module is selected in that area.

                          But it isn't, presently.
                          First thing I tried was going through the drop menu and selecting each package to see if it would work. No dice.

                          1 Reply Last reply Reply Quote 0
                          • D
                            drclaw
                            last edited by

                            Yeah it used to work in the build I previously had (4th of April from memory), but now it doesn't.

                            If I go manually load the module it works fine

                            [2.2-ALPHA][root@pfSense]/root(1): kldstat
                            Id Refs Address            Size    Name
                            1    1 0xffffffff80200000 20245a0  kernel

                            [2.2-ALPHA][root@pfSense]/root(5): kldload amdtemp
                            amdtemp0: <amd cpu="" on-die="" thermal="" sensors="">on hostb4

                            [2.2-ALPHA][root@pfSense]/root(3): kldstat
                            Id Refs Address            Size    Name
                            1    3 0xffffffff80200000 20245a0  kernel
                            2    1 0xffffffff82412000 1043    amdtemp.ko

                            There's definitely an option in the config file…

                            [2.2-ALPHA][root@pfSense]/cf/conf(13): grep -i amdtemp config.xml     
                                            <thermal_hardware>amdtemp</thermal_hardware>

                            [2.2-ALPHA][root@pfSense]/cf/conf(14): uname -a
                            FreeBSD pfSense 10.0-STABLE FreeBSD 10.0-STABLE #7 e852cd6(HEAD)-dirty: Mon Apr 28 16:58:54 CDT 2014    root@builder-10.0-b3-amd64:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10  amd64

                            This is on an APU1C if that makes any difference.

                            $0.02</amd>

                            1 Reply Last reply Reply Quote 0
                            • jimpJ
                              jimp Rebel Alliance Developer Netgate
                              last edited by

                              I just pushed a fix, try a snapshot from later today. Something changed in the output from kldstat at the OS level which caused a problem with the code that detects if a module is loaded already. It believed it was already loaded so it didn't try to load it again.

                              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                              Need help fast? Netgate Global Support!

                              Do not Chat/PM for help!

                              1 Reply Last reply Reply Quote 0
                              • D
                                drclaw
                                last edited by

                                Looks fixed here - just tried it out :)

                                Module loaded all by itself after reboot :)

                                [2.2-ALPHA][admin@pfSense]/root(1): kldstat
                                Id Refs Address            Size    Name
                                1    3 0xffffffff80200000 20245a0  kernel
                                2    1 0xffffffff82412000 1043    amdtemp.ko
                                [2.2-ALPHA][admin@pfSense]/root(2):
                                [2.2-ALPHA][admin@pfSense]/root(2): uname -a
                                FreeBSD pfSense 10.0-STABLE FreeBSD 10.0-STABLE #16 e852cd6(HEAD)-dirty: Thu May  1 22:16:16 CDT 2014    root@builder-10.0-b3-amd64:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10  amd64

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