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

    Unable to Install pfsense on Nortel Contivity 400 using embedded version on CF

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    5 Posts 2 Posters 2.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.
    • A
      artbybart
      last edited by

      I'm pretty new at installing pfsense.  So far, I have been successful twice in installing it (ver. 1.0.1): one install on a PC (using LiveCD) and the other install on Nortel Contivity 100 (using embedded ver. on SanDisk CF).

      This is my third time, and I'm having a hard time getting it to work.

      I'm trying to install it on Nortel Contivity 400: CPU AMD-K6-2+/500; RAM 256Mb.
      I'm using SanDisk CF with 1GB of space.

      I'm using physdiskwrite for both versions.

      Here's where it stops loading (flashing cursor underneath /):

      –----------------------------

      Using pfSense-1.0.1-Embedded.img.gz

      Verifying DMI Pool Date …......

      BTX loader 1.00  BTX version is 1.01
      Consoles: internal video/keyboard
      BIOS drive C: is disk0
      BIOS 639kb/257024kb available memory

      FreeBSD/ i386 bootstrap loader, Revision 1.1
      (sullrich@builder.livebsd.com, Sun Oct 29 01:30:00 UTC 2006)
      Loading /boot/defaults/loader.conf
      /


      Using pfSense-1.2-RC3-Embedded.img.gz

      Verifying DMI Pool Date …......

      BTX loader 1.00  BTX version is 1.01
      Consoles: internal video/keyboard
      BIOS drive C: is disk0
      BIOS 639kb/257024kb available memory

      FreeBSD/ i386 bootstrap loader, Revision 1.1
      (sullrich@builder.livebsd.com, Sun Oct 29 01:30:00 UTC 2006)
      Loading /boot/defaults/loader.conf
      /

      I then suspected the problem to be with the CF, so I decided to install m0n0wall on it.  To my surprise, the m0n0wall booted just fine and I'm able to work with it.  So now I know the CF is fine.

      I also have a NIC, wireless NIC, and a VGA card connected.  I tried booting the Nortel with just the VGA card connected, but it gets stuck at the same place (flashing cursor underneath /).

      I don't think the problem is with the embedded version since I have used it once before and so have other people.  I'm guessing that I'm doing something wrong with my steps or missing something, but I don't know what it is.

      Any suggestions?

      Thank you for your time.

      1 Reply Last reply Reply Quote 0
      • Cry HavokC
        Cry Havok
        last edited by

        You did note the part where it mentions that the Embedded version doesn't have VGA/keyboard support and that after the boat loader you need to use a serial cable ;)

        1 Reply Last reply Reply Quote 0
        • A
          artbybart
          last edited by

          "Cry Havok"….thank you for the tip.  :)

          I was able to see the boot menu through the console port using Tera Term.

          For some reason, on the web interface I don't see the wireless NIC setting.  It's almost as if that card is not installed, which means I'll have to install it separately.  I'll look around in the forums and see if I can find an answer.

          Thanks again for the tip.

          1 Reply Last reply Reply Quote 0
          • Cry HavokC
            Cry Havok
            last edited by

            The wireless NIC may not be supported - have you checked the supported hardware list?  In theory anything that FreeBSD 6.2 supports can be made to work even if it isn't on that list.

            1 Reply Last reply Reply Quote 0
            • A
              artbybart
              last edited by

              Quick Update:

              I found out what the problem was…..I had to go to Interfaces -->then choose "assign" then choose and add the actual MAC address of the wireless NIC (from the drop down menu).  Once I did that, I saw the actual interface listed as OPT1 (which you can rename it if you like i.e. WLAN).

              Needless to say, there was one more step left and that was to "Enable" the interface that I had just added.  For some odd reason, I kept thinking that the wireless NIC interface will "automatically" be detected and listed in the "Interfaces" menu (goes to show you how little I know!!)

              Eventually, I got it working through my wireless NIC.

              Thanks for the help.

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