@yorickbm Nope "Intel/AMD" x64 only. The only ARM install supported is Netgates own HW. /Bingo

Also please don't forget that skipping multiple versions is always a "bigger" problem/endeavour as just upgrading to the next version. Re-Installing with config-recovery in most cases is the far better alternative then simply updating and updating again. As the Plus devices got ZFS as filesystem relatively late in the game with 21.05, I'd always recommend to everyone that has the ability to be on site with the device to just take the latest stable version (21.05.2 or 22.01 if you're adventurous) and do a fresh install with config-recovery. That is available on the console prior to selecting a new install with either UFS/ZFS. Just let it find & recover the current config (or save it yourself) and do a new install with ZFS of the current CE/Plus release of your choice and afterwards watch it boot up the first time with your configuration intact and your interface setup already in place. Had no problem with that with variuos customers that "skipped a few" updates "because the system was OK and just ran..." you know the kind

Seems that this problem occurred in previous pfSense versions as well. https://forum.netgate.com/topic/106500/package-manager-unable-download-the-list-of-packages-on-new-installation

@netblues I am beginning to think that Kubuntu uses some older packages. I had tried to install a future release, but same issue. I will look at upgrading my qemu/kvm to see if this correct the issue. Or stick with OPNsense. I believe that it is build on hardenedBSD, so maybe that is why I was able to install with the current configuration. Regards

@ericatnetgate Please open a ticket at https://www.netgate.com/tac-support-request to request the current firmware!

@johnnyg_mi said in Installer fails, reboots PC, and repeat: I'm using pfSense-CE-memstick-2.5.2-RELEASE-amd64.img.gz just downloaded today. I flashed it to a USB drive, trying both Rufus AND Etcher, but I still have the same issue. After boot, I see the "Welcome to pfSense" menu and it automatically boots after 3 seconds. It starts to load but then reboots 3-4 seconds later. It simply repeats this cycle, never getting to the installer. I've installed other OSes on the same PC without this issue: CentOS Stream 8, Stream 9, and Debian 11. I have also tried downloading pfSense-CE-2.5.2-RELEASE-amd64.iso and writing/burning that to a DVD, but that has the same problem. Just before the PC reboots, I captured the errors in the attached image. I have also tried to intervene when the "Welcome to pfSense" boot menu appears; I have set "Cons: Video" (shows "Cons: Serial" by default) as well as attempting to boot in Single user mode. I have also used the Boot Options menu to set Safe Mode: On and Verbose: On, but I see the same result.[image: 1644105617095-20220205_184224-resized.jpg] See if this thread might help you out: https://forum.netgate.com/topic/161963/boot-from-install-media-results-in-can-t-find-boot-entropy. Others that have experienced this issue in the past had to change some BIOS settings to get around it. And at least one person I recall reading a post from some time back had to actually update the BIOS in his hardware device.

@pwest all in the config file. :)

@bob233 Something simple that happened to me a while ago. Have you tried pressing the "Scroll lock" key and try again? Sometimes it can happen that because you have the lock activated it does not allow you to press enter. Yes, I know that it is a very old post, I am simply adding the information because it is the first Google search on the subject, and it may help someone.

@steveits everything was connected. WAN, LAN, etc... All IP addresses were properly assigned. Had to manually install packages such as apcupsd, pfblocker, etc... The funny thing is that I did not need to configure them once installed. I guess the config backup had written their configurations in a location that did not get overwritten by the package installs.

@gertjan Guess somehow I missed that. Tried again successfully. Thanks!

Thanks, Problem solved

@fabiensch said in pfSense said 2.4.4 is "on the latest version"...: advise against installing packages on pfSense Packages are perfectly fine, but people get into trouble if they log in to an old version of pfSense and install a package which will by default pull from the current version. One can install packages from the previous version (not any version), just change the version per my sig. I'm just saying your error message sounds like others who have done that. Glad to hear you got it reinstalled and running.

@jimp Works, thank you!

Unclear what happened if you didn't delete it yourself. However with those symptoms you should open a ticket with us to get a recovery image: https://www.netgate.com/tac-support-request Steve

There is some automation there but it's not fully automated. Support work 24/7 though. Just for reference you can install CE on the SG-2440 but you need to use the ADI specific image because of it's serial console setup. So for example this: https://nyifiles.netgate.com/mirror/downloads/pfSense-CE-memstick-ADI-2.5.2-RELEASE-amd64.img.gz But you should run Plus on the SG-2440 if you can anyway. Steve

How to remove wireguard interfaces?

So...after scouring the web.... I found this: https://www.reddit.com/r/PFSENSE/comments/9l5fqo/422_upgrade_boots_up_yet_monitor_stuck_at_booting/ I proceeded to test, and yes, pfSense 2.5.2 does boot in legacy mode on the Zotax CI-323 to install, you are just unable to see it booting as the console output stops after you see the message can't find file '/boot/entropy'. The solution was shown in the above link to be: hit [esc] during initial pfsense boot. At the prompt, type "set kern.vty=sc" hit return At the prompt, type "boot" I was able to see the boot and prompts to install once this was completed. There is likely an issue with a kernel driver, but this solves the problem for now. Once I installed with the updated realtek driver, I my /boot/loader.conf.local config is as follows: kern.vty=sc if_re_load="YES" if_re_name="/boot/modules/if_re.ko" The system is now booting in legacy mode and I have the updated CI-323 driver 1.96_04 installed as a module. The system is stable. For what it's worth, I have used a pfsense Zotac CI-321 for more than 2 years with a recompiled kernel and loaded the updated realtek drivers in the kernel. This box achieves 1Gbps throughput routinely and hasn't been rebooted for months. I run it on AT&T Fiber for basic firewall with NAT. I will be recompiling the FreeBSD kernel to include the updated realtek drivers for the CI-323 as well with hopes of duplicating the performance I get on the CI-321. It's a shame we have to do this. I do agree with you. The Intel NICs are mostly painfree with respect to pfsense functionality. Realtek needs some love to get working properly.