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

    Can't boot with Epia EK800EG

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    3 Posts 2 Posters 1.8k 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.
    • J
      Jarhead
      last edited by

      I see from searching that the Epia EK800 has been used before. I can boot m0n0wall fine and I can boot the memstick version of pfsense but I cannot boot the 512 version.
      I get a Fatal trap 18: integer divide fault while in kernel mode.
      Then it says cannot dump. Device not defined or unavailable.
      This is with the vga 512 version, with the plain 512 version it never gets past the Verifying DMI pool.
      I only have 256M RAM, could this be the reason??

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

        Is this the right forum?? No one has any idea what this issue is?

        1 Reply Last reply Reply Quote 0
        • W
          wallabybob
          last edited by

          @Jarhead:

          I only have 256M RAM, could this be the reason??

          I doubt it. I have a Jetway motherboard with VIA CPU and 256MB RAM and it runs pfSense "Full" version just fine.

          @Jarhead:

          I can boot m0n0wall fine and I can boot the memstick version of pfsense but I cannot boot the 512 version.

          So why are you trying to boot the "512" version?

          @Jarhead:

          I get a Fatal trap 18: integer divide fault while in kernel mode.
          Then it says cannot dump. Device not defined or unavailable.

          FreeBSD writes crash dumps to swap file. If the kernel crashes before there is a swap file established (e.g. early in the startup if you are running the "full" version or anytime if you are running the nano BSD version) then the kernel has nowhere to write the crash dump.

          @Jarhead:

          This is with the vga 512 version, with the plain 512 version it never gets past the Verifying DMI pool.

          Its a while since I watched a pfSense startup and "Verifying DMI pool" doesn't appear in the recorded startup output of my system (output of dmesg pfSense shell command). "Verifying DMI data" is BIOS output?

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