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

    2.0 ACPI Errors

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    3 Posts 2 Posters 3.6k 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.
    • P
      ptaylor
      last edited by

      I have an old Compaq workstation that I'm trying to use as a pfSense box.

      I've installed 2.0 Beta and have a few issues so far:

      1. When Shutting down or rebooting, it never seems to complete.  I have to physically hold down the power button for a while to get it to power off, then I can power it back on normally.
      2. When running a speed test (at speedtest.net), on the download test when it gets to the higher end of the test, I start getting these errors on the console and in my log:

      Jan 17 22:28:58 kernel: ACPI Error: Illegal I/O port address/length above 64K: 0x0x400020/4 20090521 hwvalid-241
      Jan 17 22:28:58 kernel: ACPI Exception: AE_LIMIT, Returned by Handler for [SystemIO] 20090521 evregion-531
      Jan 17 22:28:58 kernel: ACPI Error (psparse-0633): Method parse/execution failed [_GPE._L09] (Node 0xc428eb80), AE_LIMIT
      Jan 17 22:28:58 kernel: ACPI Exception: AE_LIMIT, while evaluating GPE method [_L09] 20090521 evgpe-705

      I'm using a 3COM card for my WAN interface, and the on-board for my LAN interface.

      This motherboard uses an ATI chipset with an AMD processor.

      I've tried adding the command to disable acpi in /boot/device.hints, but then it wouldn't completely boot up.

      Any other suggestions?

      Thanks,
      Paul

      1 Reply Last reply Reply Quote 0
      • P
        ptaylor
        last edited by

        Nevermind - Using this box for pfSense is probably not a great idea anyhow.  I have a net4801 that I'm going to try the nanobsd version on instead.

        1 Reply Last reply Reply Quote 0
        • C
          cmb
          last edited by

          Either hardware bugs or FreeBSD ACPI bugs, you'll have to replicate on a stock FreeBSD and report there to get it fixed. BIOS update might fix it.

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