If it's a USB CD-ROM, check the port it's in. If it's a USB 3.0 port, try a USB 2.0 port instead. A USB memstick would be faster/easier than a CD anyhow though

Many thanks Steve, just saw this, no, I hadn't cleared the CHS settings, I'll try again this aft if I get chance. I did set all to Auto for the drive, assuming it would rescan the disk afresh, but if it still holds that config, that would prevent boot. I'll report back with results.

Yep ^ that. You don't need to open the .img file. Once you've removed it from the gzip (.gz) you write the .img file to the USB drive. Steve

Many thanks :)

Do a fresh install, restore config backup.

I should had mention that before but I don't use transparent squid proxy. I do have a transparent setup for Dansguardian, which is on a different subnet. This is the order I did my install a month ago… squid, squidguard... got them running... then added dansguardian into the mix I have squid listening on my lan and loopback...  dansguardian is listening on my lan and upstreams to squid via 127.0.0.1 here is the nat I use for dansguardian KIDSNET TCP * * * 80 (HTTP) 127.0.0.1 8080 Dansguardian Transparent Proxy Re-Direct

Hello, I've reinstalled all over again, but first using my old installation I made two backups, one with and one without packages. I've followed the instructions given here, I've restored only the no packages backup and now I don't have orphan package configurations. But the main problem persists, "Unable to communicate with http://packages.pfsense.org. Please verify DNS and interface configuration, and that pfSense has functional Internet connectivity", so I cannot view or install any packages… I have checked it out almost everything, from the console everything seems to work fine, dns resolves OK when pinging even to packages.pfsense.org  (attached img) Thank you in advance for any advice or suggestions you may have...  

Could it be because Im trying to install 1.5 on an SSD drive?

Exactly. Not a software bug but a documentation issue. Steve

your not getting it… the paths to perl in the lightsquid package needs to be corrected.. it has nothing to do with the squid package. if the workaround isn't working for you, post a bounty and see if someone will fix it sooner then later

I'm running the 64 bit version in a vmware esx 5.5 environment.  The reason I suspect it being a problem with carp is due to the number of  interfaces that I have in Carp.  I do not use limiters at all.  I am running 3 WAN connections all with carp.  Other than that I have some basic rules and vpn connections. Andy

Excellent.  :) Use /boot/loader.conf.local for custom loader tweaks like that. It won't be overwritten by a firmware update for example. Though this almost certainly won't be an issue in 2.2.1. gpioapu is an addition in pfSense, it's not included in FreeBSD. Normally that value will be set by the BIOS to return the motherboard model for example. The driver looks to see if it's running on the APU but for some reason it seems there's a condition in which it loads anyway. Seemingly this includes when no value is able to be obtained for variable. Your board is almost certainly too old to have any smbios features so it's returning 'null' when queried. Edit: Looks like that box produced about the same time smbios was introduced but for whatever reason it doesn't have it. I was just running a test to see if that worked but the box I have to do it is so slow you beat me to it! Good to see that works anyway. Steve

Hi, Is there any solution? I want to use havp on pfSense 2.2.

Ok, here is what i did. I created "warning.mydomain.net" in the vHosts package and copied squid_clwarn.php to "/usr/local/vhosts/warning.mydomain.net" I also added "warning.mydomain.net" to the DNS Resolver Host Overrides. In squidclamav.conf i changed to: redirect http://warning.mydomain.net/squid_clwarn.php No more certificate warnings! What about the other stuff from my logs i was asking about? And what someone share his Clamav settings for performance?

Just for the record: I wasn't able to fix this problem with an "online" pfsense. To fix the problem, I had to reinstall the whole system. Don't forget to backup your configuration settings.

@kejianshi: Are you also mixing and matching oil and brake fluid in your car?  Don't do that either. That analogy may be a little extreme.  ;) Closer to running 10w30 oil and topping it up with 5w10. You shouldn't do it but it's unlikely to cause a problem. If it does though your dealer just going to turn around and say 'well we said use this oil and you didn't so no replacement engine for you!'. I have run dissimilar memory modules successfully many times however I couldn't recommend it for a production environment. Steve

I got it. Thanks & Regards amitaussie

Hmm, long while since I've used 2.0! I assume it doesn't say underneath the graph then? From your state-table size and number of mbufs it looks like a small ammount. You can grep for it in the boot log from the command line like so: [2.2-RELEASE][root@pfsense.fire.box]/root: cat /var/log/dmesg.boot | grep memory real memory  = 1072627712 (1022 MB) avail memory = 1015791616 (968 MB) agp0: aperture size is 256M, detected 764k stolen memory You can probably also run that from Diagnostics > Command Prompt. Steve