@stephenw10 well yes that. Plus ultimately the upgrade from 23.09 to 24.xx killed the OS which bricked the device.

That's a library mismatch. At some point it has pulled in packages from a different version. If that happened at upgrade it's probably not an issue unless it reappears after clearing it. Those errors always show at upgrade but are usually suppressed and would not create a report. Steve

I had the same problem. For me, it was a faulty console cable that caused the exactly same issue. With a different console cable, the problem did not occur.

@MLBiedler prob because the built in one in windows doesn't actually understand that common compression method used all over the planet..

it's sorted now, opened a support ticket and netgate reassigned the token to my new NDI.

@stephenw10 ok cool. thanks for your assistance on this.

@viragomann Thank you very much for your support.

It waits for 3 seconds and shows a countdown: TIM-1.0 WTMI-devel-1.0.0-1115f12 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 1.237V NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(release):ROGUE2-01.00.00.01-cpu1_2G-0-g06b570a8d (Marvell-release-1.3.0) NOTICE: BL1: Built : 14:34:11, Feb 7 2020 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(release):ROGUE2-01.00.00.01-cpu1_2G-0-g06b570a8d (Marvell-release-1.3.0) NOTICE: BL2: Built : 14:34:13, Feb 7 2020 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.5(release):ROGUE2-01.00.00.01-cpu1_2G-0-g06b570a8d (Marvell-release-1.3.0) NOTICE: BL31: Built : 14 U-Boot 2018.03-devel-1.2.0ROGUE2-01.00.00.02+ (Feb 07 2020 - 14:33:22 -0500) Model: Silicom Rogue-2 CPU 1200 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 750 [MHz] DRAM: 3.4 GiB Comphy chip #0: Comphy-0: SGMII1 3.125 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 6 Gbps PCIE-0: Link down MMC: sdhci@d8000: 0 Loading Environment from SPI Flash... mvebu_spi_ofdata_to_platdata: ofdata clock 200000000, frequency 20000000 SF: Detected w25q32bv with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Silicom Rogue-2 Net: eth0: neta@30000, eth1: neta@40000 [PRIME] Hit any key to stop autoboot: 0 Marvell>> Pressing space (or any key) should stop the boot. If it doesn't then perhaps your terminal setup is not sending it correctly. Steve

After a lot of struggle this was my solution; It seems a static ip in the 192.168.1.x range is restricted so I changed the ip address of my isp router to 192.168.13.x. Powered off my pfsense1100 booted with usb (only the righter slot works) and pressed the [y] button a couple of times to prevent autoboot. Then I started the ‘recovery’ instead of ‘install’. And in the recovery I only opened the shell to ping a website and confirmed that my internetconnection was working. Then I typed exit to start with the install. And everything worked instantly. During the install you get at 3 moments the feeling that everything is stuck. Especially during the last stage, -the real install- just wait for like 10 minutes.

Everything is running now. The DNS problems resulting from a misconfigured gateway. Thank's for your help. Johannes

Now I did the following: env ASSUME_ALWAYS_YES=yes pkg-static bootstrap -f After that I went to System Update and it showed that I have a new Version available. Before that it always showed that 2.7.0 is the latest version for PfSense. So I updated from 2.7.0 to the new stable version 2.7.2 After it upgraded and rebooted (it felt like it took much longer than usual) But now it seems to work somehow. The package manager shows items and the crash report does not show up anymore. I think the issue is no more. (I hope)

@stephenw10 No, 2.5.2. I am afraid I am a little behind... not proud of it though...

Ah, then, yes, 2.7.0 is the last version that will see packages there. The dynamic repos will not pass branches to CE in Azure.

I would remove the zeek pkg then upgrade, then re-install it. The setting should remain.

There is only the EoL doc here: https://www.netgate.com/support/product-lifecycle Other than that the release notes include devices that specifically cannot run that version. For example the SG-1000 cannot run 23.01 or newer: https://docs.netgate.com/pfsense/en/latest/releases/23-01.html#errata-known-hardware-issues That's the only specific device to date. The 3100 is EoL and at some point will become difficult/impossible to build for but it still runs 24.08 at this point. Some packages are no available for it as they no longer build.

@stephenw10 Ok that would have probably worked too, I had considered getting one of my older downloads to take care of it. Either way, I'm not complaining or don't mean to. It's a free product first of all and second of all, if netgate owns it then they can do what they want with it and nobody is forcing me to download it. It's like if you own a house you should be able to paint it any color you want :) Personally I would paint it glow-in-the-dark haha.

Make sure the update repo branch is set the 23.05.1 still. At the command line run: pkg-static -d update See what errors are shown. Steve

Check: /usr/local/etc/pkg/repos/pfSense.conf See: https://docs.netgate.com/pfsense/en/latest/recipes/freebsd-pkg-repo.html#installing-packages

Not if that is the case. eMMC has limited writes after which it will not allow further writes. It will fail and depending on the drive controller/firmware may at least fail gracefully to a read-only state. It may not be that. Can you write to it with anything?

No you don't need to add a heatsink. We have never fitted one and don't see issues with heat. Unless maybe you have some drive that runs especially hot or is designed to use a heatsink. I'm not aware of any but someone may have produced one.