Judging by the name we just helped you get this going again in a support ticket. To help others in a similar situation, it turns out that in this case it appears to have been your USB cable that didn't work correctly, which caused the COM port to not appear in your workstation.

Any chance of upgrading it to something a little more current so that you're not chasing old bugs?

You are better off on 2.2.3. The 2.2.3 snapshots at this point (From yesterday afternoon forward) are much more stable than 2.2.2 in just about every way except the official blessing of being a release.

Hi When Navigating in the GUI, in general when applying any change after creating a rule it takes to much time, I have no special configuration, nat and port forwarding, I just started configuring it. PFSense 2.2.2 AMD 2 core at 2.5 4GB Ram 32 GB USB

Sounds like failed upgrade with screwed permissions and without reboot. Reboot the box and reapply the upgrade.

@almabes: Yes.  Just make sure you plug it in the correct slot. i see what you mean as i see three slots.  the adi "component  layout internal connections" shows which one is mSata. thanks!

It's NIC cards that matter more than the processor.  You want Intel gigabit NICs.  The little APU they sell at the pfSense store has a 1Ghz cpu, and craptastic realtek NICs.  I have one on my 100Mb comcast connection, and it works just fine.

Look, on any recent SSD, you can write hundreds of TBs of data and it will still be well alive and kicking. That's a usage that's never gonna happen with /tmp or /var on pfSense…

you can, but don't do it. pc's are horrible switches

My apologies: I should have read more carefully. I just jumped down to the "Disable Write Caching" section. I think I have documentation fatigue today. Yes, hint.ata.0.mode=PIO4 works in place of hw.ata.ata_dma=0 and, it boots fine. Thank you. Andrew

I'll just point out that your WAN side rules are similarly flawed. Your NAT rules to allow IPSec traffic to a server at 192.168.0.9 will not pass the required UDP traffic. Steve

Not sure what you were doing with tinycore in the original post, but you didn't end up with nano on it as it wouldn't be mounting adaX. Just write the SD card from another machine and move it over to the APU. https://doc.pfsense.org/index.php/Writing_Disk_Images

https://doc.pfsense.org/index.php/Writing_Disk_Images

Ah, thanks! I did not have a entry like that in the backup. But after som try-and-errors (thank god for snapshots!!!) i figured out to go to "System->Advanced->Serial Communications->Change to VGA" on the 2.1.5 system, save the configuration and take a backup again adds the following to the XML: <system><serialspeed>9600</serialspeed> <primaryconsole>video</primaryconsole></system> Now it boots fine after restoring config :)