yes i went through the bios with a fine-tooth comb. In the end the problem still remains unresolved, due to time constraints and not wishing to recompile kernels, i just swapped out the hardware for some DL150's, which it loaded onto fine.

thanks perry. i'll look into that!

Thanks.

Hello.. Sorry to pull up an old thread but I was wondering if this issue still exists IP380's?  Also is there any way to get the NON embedded version on the IP530's? Thanks, Matt

If you current 1.2.2 setup is broken, it wouldn't change must upgrading to 1.2.3 :) release announcement http://blog.pfsense.org/?p=351 Save the config file before a upgrade Diagnostics -> Backup/restore

This the onboard adaptec controller on an IBM eserver 226. Pretty sure it does hardware RAID. Win2008 sees it as a single RAID disk as does Untangle and Endian during install. No worries I've installed it to a single disk and just having a play now. I like pfsense some of the features but am probably going to settle on the commercial version of Endian. HEaps of features. Nice interface. Regards & Thanks Mark

same problem i had in the this post I described in post with subject "upgrade problem"

I also have had an upgrade problem going from 1.2.1 to 1.2.2.  I have the full install of pfsense on an 80gb hard drive, so space isnt an issue.  I did the autoupdate and it found the newer version and downloaded it.  However, as soon as the download finished it just gave an error that it couldnt do the update. So I manually download the image from the updates directory (latest.tgz) and installed it manually.  However, that failed as well of course because the manual update process has to have the file named pfsense*.tgz. Renamed the latest.tgz to pfsense_latest.tgz and it worked perfect. Does the autoupdate process require the file to be named pfsense_* before it will run like the manual process does?

@richardb: Hi Also I have not changed default gateway on PC (200) from the router address (193) If I change it to (221) the pfsense address then I lose internet access Should the default gateway for lan side pc's be the wan address on pfsense or the ip address of the router? If you want the LAN side PCs to connect to the pfSense web GUI then their default gateway needs to know how to get to the pfSense LAN address. When a LAN side PC attempts to connect to the pfSense web GUI at 192.168.1.1 it will see the destination is in a different subnet so will send it to the gateway. Does the gateway know where to send it next? I suspect the router (193) doesn't. If the LAN side PCs run Windows, the commands ping and tracert can be helpful investigating these sort of problems. The equivalents on many Unix systems are ping and traceroute. As to what the default router should be I'll leave that to someone else because I don't have experience or knowledge of how bridge mode works.

working with 1.2.3-PRERELEASE-TESTING-VERSION built on Mon Jan 26 02:55:44 EST 2009 thanks…i guess

4 hours later it started to have issues, no internet, everything on my side looked good. I was about to reinstall my crappy linksys when I decided to allow DHCP on the WAN instead of a static address. Bingo. Got the address and internet works. What is going on???!? lol

Fixed in 1.2.3.

The key here is whats the difference between "normal" mode and "safe" mode? According to http://my.safaribooksonline.com/9781593271510/start_me_upexclamatory_the_boot_process Boot FreeBSD in safe mode FreeBSD's safe mode turns on just about every conservative option in the operating system. ATA hard disks run without DMA or write caching, limiting their speed but increasing their reliability by working around cabling issues and other physical problems. EISA slots are not probed, and ACPI is disabled. On i386 systems, SMP is disabled. USB keyboards will no longer work in single-user mode. This option is useful for disaster recovery and debugging older or otherwise troublesome hardware. If your system's performance in safe mode is adequate for your requirements you could stick with safe mode (though don't you need to be present to force a "safe" mode boot?) otherwise you may be better off investigating the problem so you can attempt to rectify it. If you want to investigate I suggest a place to begin might be to see what happens when you boot without the 4 port Sun card.

Gave up and used a Celeron 1.7, 256mgs, and a Via board. 3 Intel Pro 100 nics. All I did was plug the CF card+adapter into the other system, ran the basic config, and BAM. Works great.

@karsh: What is the performance diff between the embedded and the full version? The performance only depends on the hardware you throw at it. Network throughput doesn't differ by booting from HD or CF.