I take it that output is from the serial console? It's a known bug. There are several work arounds, this is the one I used: http://forum.pfsense.org/index.php/topic,7458.msg241783.html#msg241783 Of course to do that you need access to the box. If you have setup the interfaces on the first boot, it looks like you have, you should be able to connect to the web GUI on LAN. Alternatively you can try mounting the CF card under OSX and editing the files there. Steve

It's still a capable box, like you say easily able to keep up with an ADSL connection. The Pentium 3 Tualatin was a highly efficient CPU, when the Pentium 4 was introduced many people saw it as a backwards step. The actual CPU in the X-Core is a 1.2GHz Celeron but it has the same architecture. It uses about the same power as the X-e but has less processing power. Don't dismiss it yet. There are many users who have no trouble with the Realtek NICs. It does seem to be largely dependent on what they're connected to but no hard facts have been established. It's shiny and red!  :) Steve

Thanks, I changed on the BIOS and the installation continued. I removed the LIVEcd but it seems stuck on the configurations it doesnt get to the web interface

@stephenw10: The first thing to check is that your updater settings are correct. Go to System: Firmware: Settings: in the WebGUI. Select one of the 'Default Auto Update URLs'. Make sure you select the correct one, i386 for 32bit amd64 for 64bit, for your system. Don't select the development snapshots unless you really want that.  ;) Steve It worked. I though I tried that before though. Thank you very much.

Did you notice the output you posted shows an incomplete copy to the output device? Maybe it is broken and you need a new flash drive.

if you couldn't run the 64 bit version, it wouldn't boot. There is no config diff between 32 and 64 bit.

Thank you is solved. ;D

Thanks for the reply guys. I was aiming for a fresh full installed. It turned out to be quit easy. I did not even had to filddle around with /etc/fstab…

Well I figured it out - turns out there was an entry in Snort's Blocked list for the pfSense.org IP address.  Removing that and I was able to access the site.  That said, why if Snort was disabled on the WAN interface would it still be using the Blocked list?

One tip about PPPoE problems : try to disable ACPI on boot menu (option 2).

@podilarius: Have you tried one intel and 1 realtek? If they are onboard, perhaps one is disabled in bios. IIRC there are some things you can do either in BIOS or in start up scripts that pertain to realtek nics. Search the forums :/ thanks sir. i solved the problem by changing my nic.

How did I miss that page! Thanks Biggsy.  :) http://doc.pfsense.org/index.php/PfSense_2_on_VMware_ESXi_5 Steve

Yeah, couldn't care less about that wireless card. I might replace it with something more useful down the road, but for now I'm using an external AP. And you're right, that pciconf is from the working system. So, if there's no interest in fixing this hardware for 2.0 (or understanding why 2.1 works where 2.0 doesn't), then I think we can call this one solved. :)

@Jimp I am very grateful … thanks.  ;D Ana

yup, ad0, that worked.  Thanks.  Time to read up on BSD disk layouts, me thinks.

Hi Jason Thanks for the prompt reply.

@steve_eo: The only thing that was missing from what you told me . . . Thanks for completing the story. I've never had to do this because my WAN interfaces have always used DHVP or PPPoE.