fixed no irq problem any more still only ONE wan connection at a time i can only connect to 1 modem at a time and only true dhcp, static does not work at all ????

http://forum.pfsense.org/index.php/topic,1828.0.html –> http://devwiki.pfsense.org/FullInstallOnWRAP

@jrpadilla: System is hanging on boot up when recognizing COMPAQ motherboard? HARD LOCK system locked. Please help. Just today I was installing pfSense 1.2 RC release in our HP D220 MT desktop and was frustrated all day coz the install always hang, I thought at first it was caused by the corrupt cd installer so I downloaded and burned a new copy but still have the same problem, simply it won't go away. I also changed the cdrom drive as mentioned on another thread in this forum but to no avail, still have the same problem, it always says that pnp bios bad checksum. I almost called it a day until I gave it one more try, I found two workarounds in order to install pfSense 1.2 RC3 in this particular hardware. 1. Press F10 during bootup to enter setup and Disable ACPI in bios, save the changes and let the system boot from the cd installer and let the default mode load. 2. Instead of disabling ACPI in the BIOS, when the FreeBSD loader appear press 2 to load  FreeBSD ACPI disabled and you're good to go. HTH

Wow I though I would have an e-mail if someone replied. So I totally forgot to check back!. But I fixed it a while ago! How? Not sure. First off, I have a ASUS A8V-VM. Its a cheap socket 939 VIA chipset motherboard. I first tested the 80GB SATA harddrive with pfsense in another machine. Booted with no problem. Put back into my router box, no go. reset cmos on the motherboard just 'cause, no go. I reset all my cmos settings, like date,time,turn off serial port etc. Until i got the SATA controller settings. I didn't remember if I had it in SATA or RAID mode, or RAID with BOOTROM. So I left it in SATA mode, No go. Okay frustrated, I tried RAID mode with bootrom off, no go. Bootrom on, booted. Bootrom shows with a large yellow warning about unix file system detected. So I continue. It worked!. Still today I don't understand the yellow warning. To my memory I never had RAID enabled in bios ever. I was running this box for 8-10 months before this happened one day. It been running great ever since. Why this fixed it? I don't know. I'm more of a Power user than an advance user. But if anyone has this problem. They should 'fiddle' with their drive controller setting? Or try an IDE drive over SATA for testing?

Hi all I installed pfsense on gmirror devices (/dev/gm0) and I noticed that every time that I do a reboot the mirror do a rebuild (at boot time). After some minutes the mirror is again complete and the pfsense is fully working. Any idea ? thanks Giacomo

Aren't assumptions interesting critters… :) gm...

M'kay.  It appears to have been a combination of a flakey CDROM drive, (the vm_fault errors when mounting root), and I needed to disable PCI bus mastering, (the other random errors while it was sitting there).

That is an update file. You seek http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/embedded/pfSense.img.gz

I posted this under hardware. On of my guys thought that might be a better place to ask. Thanks http://forum.pfsense.org/index.php/topic,7120.0.html

Hey, great, glad to hear it!!

Guess I have to reinstall :(

http://forum.pfsense.org/index.php/topic,7001.0.html –> The embedded version does not have any VGA output. Connect and configue per Serial port.

Upgrade the secondary first, then the primary. We recommend reinstalling on the embedded platforms.  We are still ironing the upgrade bugs out.

@cmb: Not when the BIOS has bugs that we can't easily work around, that's why you have to upgrade the BIOS. I'll second this.  We have a pfSense box in production that started out rather randomly flakey.  After some experimentation we checked the manufacturer website and found there was a new BIOS that fixed some PCI timing issues.  Loaded it and everything works great since!

From memory this has come up before - search the forum.

I can confirm this crash also.

You have more than one core so the multi-processor option is probably the best choice.