Just to clarify: Does the "No dump device" message appear BEFORE the console prompts for the installation parameters OR does it occur on the reboot after an apparently successful install? If you completed an install did you select GRUB as the boot loader or the FreeBSD boot loader? (I have no experience with GRUB as the boot loader for pfSense but have seen a couple of reports that people haven't been able to get it to work.) On my installed system the startup reports: vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 udav0: <shantou 0="" 2="" st268="" usb="" nic,="" class="" 0,="" rev="" 1.10="" 1.01,="" addr="">on uhub0 udav0: Ethernet address 00:60:6e:30:32:26</shantou></generic> so after the ISA VGA report it looks as if the kernel is looking for USB devices. Do you get a different result if you remove all USB devices from the system? How about if you disable USB devices in the BIOS before booting. (I needed to do this on my AMD Athlon based system before I could get pfSense 1.2.2 to boot but that problem went away with pfSense 1.2.3.)

It works fine. Glad I could get rid of those awful 2Wire gateways.  ;D

From everything I have read, it should "Just Work" as long as the disk is dedicated to FreeBSD.  Since I accepted all of the defaults, I assume that this is what was set up. I have run lots of tests.  Can someone who understands this tell me what information I might post, or what I might try, or tell me "Clearly this will never work because xyz" ? Thanks. I have tried the following permutations of BIOS settings and Geometry: AUTO (Disk Config) and LBA USER (Disk Config) and LBA with 3148 16 63 (I changed to a 1.6G disk) USER (Disk Config) and LBA with 787 64 63 AUTO (Disk Config) and NORMAL With AUTO, 3148 16 63 was offered and accepted in the PFSense "Select Geometry" dialog in both cases. I always put the same geometry in the BIOS and the PFSense "Select Geometry" dialog. For each of these four permutations, I tried the default Boot Boot configuration (No Packet, no Grub), with "Packet", and with "Grub" In all cases the Default Boot configuration and the Packet install fine then fail on boot as described previously with the one second Beep every 10 seconds. In all cases the Grub configuration failed installation, saying "Cannot mount selected partition".

yes, i had same problem, and i have 2 disks in RAID. Playing with bios fixed my problem. When trying to instal pfs sees two disks and one raid one disk, install only to raid disk no probs…

This was already reported in 1.2.1/1.2.3 http://forum.pfsense.org/index.php/topic,13278.0.html As mentioned there, it has been updated and is current in snaps and 1.2.3RC1

Excellent post grab3. I would love to see a tutorial for this. If you want I could host a tutorial on my website. This is something that really interest me and I am sure many people!

hansru, that only works for D series. I don't think ALIX C series support boot from a usb cdrom.

Hi Yes  I apologise just put last two sections of IP address I used these address4s before and pfsense seemed to work fine however I think that I must have bridged lan to Wan I have now kept same addresses and bridged and it appears to be working. Should I simply give wan card an "odd" address say 198.162.1.158 and unbridge What is the advantage/disadvantage of bridged Thank you again for your time

If you are trying to install pfSense to an embedded platform other than a …. How to setup NIC team on a HP ProLiant DL 380 for fault tolerance and Load

Ok I solved it.  Seems like my hard  disk had some remnants left over from an earlier OpenBSD install, and after that an IPCop install.  So this messed up the partition tables and hence the reason I got the warning about the broken GPT. I used dd if=/dev/zero of=/dev/ad4 and wrote zero blocks to the beginning couple of gigs and end couple of gigs of the disk.  This cleared the error and now pfsense installed just fine. HTH someone else.

Obtained a copy of 1.2 and it works fine. Please can someone fill me in on the bug reporting proceedure? Phil

Don't you guys think its funny that you all seem to have the same type of problem but no one has posted any help? Its because the problem has been covered a gazzillion times all ready. So I went back to the forum and searched again and some bloke said you need to disable UDMA in the BIOS, PIO only. I did this and bang both drives boot! http://forum.pfsense.org/index.php/topic,11016.0.html

The same with 1.2.3 from Apr 7 I guess I will just use kern.hz=100 and no polling.

See http://forum.pfsense.org/index.php/topic,14994.0.html and http://forum.pfsense.org/index.php/topic,15157.0.html

Can I suggest you actually perform those searches I suggested and look at that page.  The hardware that happily supports 100 users in one network may not be enough to support 10 users in a different network. Here's a bunch of things mentioned elsewhere that affect the answer: Type of NICs - server grade NICs have a lower performance impact than desktop NICs.  Some cards are known to be a bad choice. Traffic profile - of that 100 Mb/s how much do you actually use?  How much would you be pushing through pfSense?  What does that traffic look like, is it all long sessions, short sessions, UDP, TCP, little packets, big packets, what? What kind of Internet bandwidth do you have, 512 Kb/s, 50 Mb/s? What services are you running on the pfSense host? And so on, and so on, and so on.  As I said, this has been asked and answered many times before.  I'm not going to repeat the answers for everybody who can't be bothered to search.

Have you tried a base FreeBSD 7.1 install?

Hello, I have IPCOP and PFSENSE connected to the same router (82.102.x.x/29). Both subnet's use the same default GW (82.102.x.1) The subnet 192.168.16.0/24 work fine. The subnet 192.168.1.0/24 work's fine until it stop's, after a while it returns. I monitored the default gw IP (82.102.x.1) and it's stop's responding only in this subnet!

There are a lot of files in there. You want the latest one in the format of: http://snapshots.pfsense.org/FreeBSD7/HEAD/pfSense-2.0-ALPHA-ALPHA-yyyymmdd-time.iso.gz