@doktornotor: Seems like you need better hardware. It's the C2758 model, it sounds weird, is not it?

Hi and thanks James. I reinstalled the firmware using the downloaded link you supplied. All good. I did lose all my configs and certificates I had created in the last 2 months (recovery of them didn't work), but i had a backup from December which got me partly back on track. Kind regards and thankfully it's not become faulty with the update. Andy

upgrade to 2.3.3_1 doesn't reboot? and powered off and on doesn't come back on… same device. similar if you ask me... probably the actions taken after are why we are at a different stage. in any case - my issue has been resolved by support

Thank you, that was the problem. I have it up and running.

Is this a request for help? Just a complaint? Share a few more details and I'm sure others would be willing to try and help troubleshoot the problem.

Nothing changed in the drivers, or even most of the OS. It is highly unlikely the problem was related to the update, and might have been from the reboot. That said, the configuration format of both 2.3.3 and 2.3.3-p1 is the same. Backup the configuration, reinstall from a 2.3.3 install disk, then restore the configuration. I'd use that as a last resort since it's likely a red herring and not the true source of the problem. Before doing that, I'd try the usual things like swapping cables and trying different switch ports, etc.

@mscher: The pfSense 2.1.1 did not work too. Yesterday I tested the pfSense 2.2 and it booted, but it is a alpha version. Then, does anyone have a solution for network adapter be recognized in pfSense 2.1.4? Were you ever able to get it working with the hp 331flr? I'm having the some problems. But I'm doing it on a mineitx, amd cpu. The lights on the adapter won't even blink when I have an Ethernet cable pluged in And if I try to boot with the adapter installed it won't even post it just keeps on rebooting.

start here: https://doc.pfsense.org/index.php/Interface_Bridges

The .img file is a disk image that is written to the USB memstick using dd, win32disk imager, rufus, etc. The filesystem format is UFS which few other operating systems can read, aside from FreeBSD. The fact that you can't see any files on there does not mean there is a problem. Try to boot from the USB memstick. If the hardware supports booting from USB and FreeBSD will run on that hardware, then it should work. There was at least one other person who managed to get it to work on similar hardware, but that might be a different model: https://forum.pfsense.org/index.php?topic=116910.0

That went into the right direction. I had defined the LDAP server by FQDN. But during testing, there was also a problem with DNS lookups, so the server was not found. Instead defining it by IP address solved the problem. There had been some more challenges to take (WAN connections didn't come up right away…), but the process of exchanging hardware finally worked. What a relief!

Thanks for this guide it really helped. I did run into a snag though on 2.3.3: If you follow the posted guide pkg install icu will install icu-58.2,1. This will then throw an error when you try to run murmurd. Unable to load library icui18n "Cannot load library icui18n: (Shared object "icui18n" not found, required by "murmurd")" To resolve this I issued: pkg remove icu Then added the icu package 55 as per rest of guide: pkg add http://pkg.freebsd.org/FreeBSD:10:i386/release_3/All/icu-55.1.txz I also had to re-add all the QT dependancies as listed above because the removal of icu also removed QT. Of course if you add icu-55 first there is no need to remove anything and the guide is still good. Hope this saves someone some time. I love Mumble and wish it could be a native package  :P ***For the observant; I added this to an i386 architecture. So be careful when copy-pasting!

Follow on from the above. By adjusting the "start date" on the rrd_summary package I've found that the large data "error" occurs all on one day - the day I was assembling the pc with the new LAN card.  Starting the present month after that date shows sensible figures. Most probably I've caused some file or data corruption, perhaps with the backup file which at one point I restored.  My assumption now is that the display will self correct at the month end - and the "problem" is self inflicted.  Oops. J

YES! That was it. Thanks so much!

Install an older version that will boot on that box (e.g. 2.1.x) and then upgrade.