In the Web GUI, go to Diagnostics/Command and type in the following in the Execute Shell Command box dmesg | grep -i smp If the SMP kernel is installed, you'll see some resulting text.

doesnt seem to matter what I do. i get the invalid mount option message every time i try to install 2.0 to a sata disk drive. tried putting the drive in an old machine and running delpart and fdisk /mbr to completely wipe the partitions off the drive and redo the MBR. did not help at all. im kinda stuck at the moment. I dont have access to a MAC  to try that method but it seems the delpart and fdisk /mbr should have worked. any other ideas? or am i just gonna be hosed and have to use a flashdisk module or SSD or something? [edit] it actually does not matter at all which type of disk i use. flashdisk module, IDE hard disk, SATA hard disk. I get that error message about invalid mount options. how do i fix this? FreeBSD 8.2 installs no problem so im not sure how to proceed. [2nd edit] I have discovered that MY particular issue came from attempting to install from a USB CD-ROM drive. the drive is detected and the install begins, but during the hardware detect/driver load phase in the boot process of the installation, it fails to work. if i plug in an IDE CD-ROM the installer works as it should. just a heads up there. bug i guess. trivial bug.

@Cry: NanoBSD (and embedded) use the serial console, not VGA output. I'd suggest you try that, with a serial console cable, before you try modifying images. If I use the hacom pfsense 1.2.3 nanobsd and then upgrade to the new pfsense 2.0 though the update feature do I need to access the console by serial cable first to assign the NIC again or I just use GUI. Current I don't have a serial cable, do you think will this work?

For the logs, 2 versions : one w/ the original configuration, another w/ only the first serial port enabled Now, w/ pfSense v2, "sio" ports were renamed "uart" pfHacom boot logs Still haven't bought serial port pci cards + null modem cable but, one friend gave me still his "usual packge used to configure various branded routers" : still a USB/DB9 cable + a DB9 cable (which i suppose null modem). Still the same problem : Putty (or any other terminal client) keeps blinking on the upper left corner but w/o any interaction possible… Thank you

Thanks for the rapidity. I think that I will test the version 2.0 because the PC just has one network interface. Thanks too for the French forum link ;)

I had the same issue on an Alix 1C. Managed to solve it just now. http://forum.pfsense.org/index.php/topic,20405.15.html gave the answer. Set the power management from ACPI to APM and it should boot up normaly now. Update 1: Turns out http://doc.pfsense.org/index.php/Boot_Troubleshooting also listed the above solution. Apparantly the Alix boards with Award BIOS haven't been working for a while with BSD. – Nephi

We run pfsense on an IBM x3250 M3 without any trouble.  We did however run into some issues with the graphics card on an x3550 M3 when we installed Fedora on it a few years ago.    To fix that I used the vesa graphics driver by adding xdriver=vesa to the boot options.  I'm guessing thats not the issue with pfsense though since there is not a gui. Found this on the freebsd forumns - http://forums.freebsd.org/archive/index.php/t-6022.html

Start here and then go looking for a file called pfSense-2.0-RC1-i386-YYYYMMDD-HHMM.iso.gz Where YYYYMMDD-HHMM is a date and time.

Congrats. Looks like I forgot to warn you about leaving only and only the installation HDD hooked up to the surrogate computer.  Otherwise, the boot time options will try and find the previous mounting point (non-ad0) when you transfer it.

well i had to punch in the dns servers by hand now its been up and running for 2 days

Well I know it can run on a PIII but this IBM server already required a number of manual modifications to make it work so my worry is it will be even worse on 2.0 Just because an old version worked on something does not mean it will on a new on. At some point all things hit EOL and they dont make drivers for or write the software to talk to it properly. I am in hopes someone with the exact model (x330) can confirm it works ehe. This is a critical box but I really would like to upgrade the firewall.

It's an unsupported controller. Trying to talk Dell into swapping it out for a supported one.

Everything looks okay. What about option under Advanced? Some new stuff you can disable. The webgui rule dont work and I have compared against one rule that works and it looks fine. So why dont it work?

@dreamslacker: Try Ebay.  You are probably stuck on getting a Single GBe NIC and having to use VLANs with an appropriate switch. The RB250GS is a good choice for the switch.  Check in on Lowyat forums to find out more details on the configuration since a lot of TM UniFi users use it for connecting their own routers along with the IPTV STB. For the NIC, I'd recommend getting the Intel PT Gigabit adapter. True indeed, maybe i rather get this RB250GS switch and run it ADSL-> Pfsense -> RB250GS ->  Workstations/ laptop  , but how about connecting through wifi such as iphone /Acryan ?

Nice one.  :) You should be aware, however, that even after disabling swap you will still be waring out your usb stick pretty quickly. You should really be using either embedded or Nano, that would restrict which packages you can use though. Steve

Hello everyone I returned to report that I had a small evolution in my problem but is not complete The solution would be a dirty at the time of mountroot> I apply the command msdosfs: ​​da0s1 to automate or do I insert the file loarder.conf set vfs.root.mountfrom=msdosfs:da0s1 set vfs.root.mountfrom.options=rw An important detail and make the iso image extracted at the root of the pendrive This will load normally but still a problem occurs later on Trying to mount root from msdosfs:ad0s1a ___ ___/ f \ / p ___/ Sense _/      _/ Welcome to pfSense 2.0 RC1  … Mounting filesystems... done. Creating symlinks......done. Launching the init system... At this point it freezes completely stopped what can be done?

This topic is old.  However folks seeing problems should check this document out: http://doc.pfsense.org/index.php/Boot_Troubleshooting