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

    Powerd error when configuring new setting

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    3 Posts 2 Posters 1.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.
    • GentleJoeG
      GentleJoe
      last edited by

      php-fpm 82404 /system_advanced_misc.php: The command '/usr/sbin/powerd -b hadp -a hadp -n hadp' returned exit code '69', the output was 'powerd: no cpufreq(4) support – aborting: No such file or directory'

      It gives this error when selecting either the None/ACPI or the Intel Core*.

      On bootup it gives this.

      php-cgi rc.bootup: The command '/usr/sbin/powerd -b hadp -a hadp -n hadp' returned exit code '69', the output was 'powerd: no cpufreq(4) support -- aborting: No such file or directory'

      2.4.0-BETA (amd64)
      built on Wed Feb 08 17:43:06 CST 2017
      FreeBSD 11.0-RELEASE-p7

      Intel(R) Atom(TM) CPU D2550 @ 1.86GHz
      4 CPUs: 1 package(s) x 2 core(s) x 2 hardware threads

      I don't see any negative affects from this. I assume I can ignore this?

      1 Reply Last reply Reply Quote 0
      • K
        kpa
        last edited by

        You have an Intel ATOM CPU that very likely does not support EIST and FreeBSD 11 by default disables the p4tcc and apci_throttle drivers leaving no method for cpufreq driver to control the frequencies.

        https://wiki.freebsd.org/TuningPowerConsumption

        You can enable the two drivers with these lines in /boot/loader.conf.local but I don't think you'll get any benefits from it, ATOMs are broken when it comes to power and thermal tuning because they don't support EIST:

        
        hint.p4tcc.0.disabled=0
        hint.acpi_throttle.0.disabled=0
        
        
        1 Reply Last reply Reply Quote 0
        • GentleJoeG
          GentleJoe
          last edited by

          Thanks.

          I followed the instructions in that section, to unload the selected module I selected Non/ACPI and then rebooted.
          Same errors. But as long as there aren't issues with this error, all is good.

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