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

    2.4B APU Memstick install issue fix

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

      I have started a new thread on this so it shows as a fix:

      Please read  this…

      https://randomproblem.wordpress.com/2016/03/31/installing-opnsense-16-1-on-pc-engines-apu2/

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

        Are you seeing the exact same error as the person on that page? That isn't pfSense, so there is no guarantee the behavior would be similar.

        Mount the memstick image in another pfSense or FreeBSD box and edit /boot/loader.conf or /boot/loader.conf.local on the stick (create one if it does not exist) and add this line:

        kern.cam.boot_delay=”10000″

        See if that helps.

        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
        • H
          hda
          last edited by

          Case of working install, booting, then it helps readable output to adjust the /boot/loader.conf by removing "vidconsole".
          No need for it, just only "comconsole" for the APU2 is good enough ;)

          But, hey then after reboot "repairs" itself including "vidconsole" again…

          Must be in /boot/loader.conf.local ?

          
          console="comconsole"
          kern.cam.boot_delay=10000
          
          

          …Yep.

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

            @hda:

            Case of working install, booting, then it helps readable output to adjust the /boot/loader.conf by removing "vidconsole".
            No need for it, just only "comconsole" for the APU2 is good enough ;)

            But, hey then after reboot "repairs" itself including "vidconsole" again…

            Must be in /boot/loader.conf.local ?

            
            console="comconsole"
            kern.cam.boot_delay=10000
            
            

            …Yep.

            That's a completely separate issue unrelated to this at all.

            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
            • ?
              Guest
              last edited by

              @jimp:

              Are you seeing the exact same error as the person on that page? That isn't pfSense, so there is no guarantee the behavior would be similar.

              Mount the memstick image in another pfSense or FreeBSD box and edit /boot/loader.conf or /boot/loader.conf.local on the stick (create one if it does not exist) and add this line:

              kern.cam.boot_delay=”10000″

              See if that helps.

              I saw it, I did a fresh install at the weekend and I cannot remember what I did to fix it as I thought at the time it was just me. Whatever I did I got past it and all was good.

              However, one of my testers was doing fresh install of 2.4b and sent a nice picture..

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