Also forgot to ask. How much does RAM size impact IPFire?
If you are referring to a IPFire backup you should be fine.
Read through this Wiki article about migration:
I’ve done this a few times and it all works A-OK. You need to run through setup. See the first paragraph in above Wiki.
I don’t know the real answer to this. To me the more options and add-ons you have the more RAM you’ll need.
If you are thinking to double the RAM and suddenly IPS/IDS will start working better I doubt that will help IPS/IDS. The RPi4B is just not powerful enough.
I think the minimum recommended RAM size is 2 GB. But someone else should really answer this question.
If you are just using IPFire as a firewall with no additional options like Web Proxy or IPS turned on then the minimum is 512MB with the recommended being 1GB. However if you turn on IPS them you really need something like 4GB but also with active network adaptors that can do their own processing for throughput combined with firmware that spreads the network load to the adaptors across all available cores in the cpu.
The lack of the latter two items is the usual reason people end up having big reductions in throughput rate when IPS is turned on.
https://wiki.ipfire.org/hardware/requirements
https://wiki.ipfire.org/configuration/firewall/ips/performance-considerations
Thank you. I’m not really having any issues with basic firewalling with a Pi 3b+. I’m interested in enabling IPS, but if a Pi 4b isn’t going to manage that then maybe I’m better off just leaving things as-is.
On a whim, I decided to grab a Pi 4B+ and see how things work. Unfortunately, I’m not having any luck on first boot. I’m using a serial console and I am caught in an infinite U-Boot loop. Does anyone have any suggestions on what might be going on here?
Thanks,
Craig
Please share the link to the file you use. I can give it a try on my RPI.
UPDATE: Tried the latest and found the same
U-Boot 2021.07 (Aug 09 2021 - 09:19:51 +0000) RPi4 - IPFire.org
DRAM: 7.9 GiB
RPI 4 Model B (0xd03114)
MMC: mmcnr@7e300000: 1, emmc2@7e340000: 0
Loading Environment from FAT... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: eth0: ethernet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: probe failed, error -110
No working controllers found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2451 bytes read in 13 ms (183.6 KiB/s)
## Executing script at 02400000
114 bytes read in 6 ms (18.6 KiB/s)
Load uEnv.txt...
...
Set console to ttyAMA0,115200n8
"Synchronous Abort" handler, esr 0x96000004
elr: 00000000000a51b0 lr : 00000000000a51ec (reloc)
elr: 000000003e3761b0 lr : 000000003e3761ec
x0 : 000000003df5e880 x1 : 4e184e174e164e15
x2 : 000000003df4cd90 x3 : 0000000000000016
x4 : 000000003df4ce50 x5 : 4e244e234e224e21
x6 : 0000000000000016 x7 : 000000003e3d2b38
x8 : 000000003df64870 x9 : 0000000000000008
x10: 0000000000000001 x11: 0000000000000006
x12: 000000000000205e x13: 0000000000000001
x14: 0000000000080000 x15: 000000003df40e90
x16: 000000003e380190 x17: 68897ef610278cee
x18: 000000003df4cd90 x19: 0000000000000000
x20: 0000000000000006 x21: 0000000000000006
x22: 0000000000000000 x23: 000000003df3eb48
x24: 000000003e3bafe0 x25: 000000003df648c0
x26: 0000000000304000 x27: 000000003dfe8ac0
x28: 0000000000005400 x29: 000000003df3eac0
Code: 54000061 d2800000 d65f03c0 f9400401 (b9400821)
Resetting CPU ...
resetting ...
U-Boot 2021.07 (Aug 09 2021 - 09:19:51 +0000) RPi4 - IPFire.org
DRAM: 7.9 GiB
RPI 4 Model B (0xd03114)
MMC: mmcnr@7e300000: 1, emmc2@7e340000: 0
Loading Environment from FAT... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: eth0: ethernet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: probe failed, error -110
No working controllers found
Hit any key to stop autoboot: 1
I think the kernel is not loading at the right place or the kernel file itself it not working.
Can you try an older image ? Coz I am off to sleep now.
UPDATE:
Raspberry Pi 4 Model B
RPi4 is supported since IPFire-2.27 core159 aarch64.
So this seem to be the first image.
I grabbed the flash image for aarch64 based on this thread. That is what is flashed to the SD card and showing the errors. I appreciate any input or suggestions.
1 Like
I should add that I also just grabbed a recent raspian image that I’m going to try just to validate I don’t have some kind of hardware issue.
Thanks for the updates. I guess at this point, I need to wait for more direction on this front. Happy to try other builds, but not sure I know how to do much more with this image.
This appears to be related to firmware ordering and such. Image does not start on Raspberry Pi 4 8Gb · Issue #22 · lueschem/edi-pi · GitHub talks more about this, although I don’t really know enough about the functionality to determine next steps.
If I connect a monitor, I’m able to get further in the boot sequence. It gets to the point where it says that it is loading the kernel and then hangs at that point. It does look like the issues referenced in those issues I linked to are related. In the end, this device needs to be headless since it is normally nowhere near a monitor.
I will add that I was able to cleanly boot a recent RaspiOS image without issues, so thankfully this is not a hardware issue.
I will keep poking at this as I have time. If anyone has any suggestions or things that I should try, I’m happy to do that.
This is the filename of the image I downloaded and installed:
ipfire-2.27.2gb-ext4.aarch64-full-core159.img.xz
I grabbed it from this page:
https://www.ipfire.org/download
I am assuming you are getting these errors BEFORE you get to the IPFire setup. But I am having trouble figuring out where in the boot sequence you are seeing the issue. Can you take a few pictures?
I’m going to load up a new SD Card and image and record some video with my iPhone. Maybe we can figure out where things go sideways!
If you read back a bit, this may be due to me trying to set this all up without a monitor attached using the serial console. I’m not even getting the kernel loaded, so nowhere near IPFire setup. Do you have a monitor and keyboard connected?
Yes - keyboard & monitor attached. No serial console for me.
When you setup the keyboard & monitor did you change the settings in the config files?
Note - The ARM flash image is configured for serial console at default
• If using HDMI & USB Keyboard: edit theuENV.txtfile and changeSERIAL-CONSOLE=ONtoOFF
• If using the serial console: edit theconfig.txtfile and addenable_uart=1to the end
I haven’t had time to try any other combinations or configurations yet
My final update for the moment because I’ve run out of ideas of what else to try. I switched to HDMI/Keyboard and disabled serial per the instructions. I could see that the kernel started to boot, but then settled into a loop showing:
invalid bus width
error -22 whilst initialising SD Card
I reflashed the image to the SD Card, but that didn’t make any difference. It doesn’t appear that U-Boot is not very happy with my hardware for some reason.
Craig
Serial Console
I tried with the serial console and I got an error like above in Post 11 and Post 12.
It may be a bug so I opened report 12680.
HDMI/Keyboard
For me HDMI/Keyboard works A-OK.
- Do you get the same above errors with HDMI/Keyboard?
- Or something different?
Like four IPFire logos on a mostly blank screen?
EDIT: back to Serial Console for a moment.
The text (issue) in Post 11 & Post 12 are slightly different from my text. Your has this error: Bus xhci_pci: probe failed, error -110 but I don’t see that error. Odd!
U-Boot 2021.07 (Aug 09 2021 - 09:19:51 +0000) RPi4 - IPFire.
U-Boot 2021.07 (Aug 09 2021 - 09:19:51 +0000) RPi4 - IPFire.org
DRAM: 998 MiB
RPI 4 Model B (0xa03111)
MMC: mmcnr@7e300000: 1, emmc2@7e340000: 0
Loading Environment from FAT... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: eth0: ethernet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
Port not available.
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
"Synchronous Abort" handler, esr 0x96000044
elr: 000000000009df64 lr : 000000000009e4c8 (reloc)
elr: 000000003e36ef64 lr : 000000003e36f4c8
x0 : 000000003df5e800 x1 : 6f6f625f726f665f
x2 : 7665645f6e006900 x3 : 000000003e3d27d8
x4 : 000000003df5e860 x5 : 000000000000005d
x6 : 000000003e3d27e8 x7 : 0000000000000010
x8 : fffffffffffffff0 x9 : 0000000000000008
x10: 00000000ffffffd0 x11: 000000000000000a
x12: 000000000001869f x13: 000000003df40da8
x14: 000000003df40eb0 x15: 0000000000000002
x16: 000000003e37119c x17: 0cc49240c2e78984
x18: 000000003df4cd90 x19: 0000000000000060
x20: 000000003e3d2218 x21: 0000000000000030
x22: 000000000000000b x23: 000000003e3d2218
x24: 0000000000000001 x25: 0000000000000060
x26: 000000003df56660 x27: 000000003e3c6aab
x28: 000000000000003b x29: 000000003df3fef0
Code: b2400021 f9000481 f9400c01 f8410c02 (f9000c41)
Resetting CPU ...
resetting ...
Serial Console
I tried with the serial console and I got an error like above in Post 11 and Post 12.
It may be a bug so I opened report 12680.
Thanks, I wasn’t sure how to open a ticket. I just went ahead and added some comments.
For me HDMI/Keyboard works A-OK.
Do you get the same above errors with HDMI/Keyboard? Or something different?Like four IPFire logos on a mostly blank screen?
Different behavior. I get past the four logos. And then it goes into a spin as I mentioned in my last comment.
Is anything plugged into USB besides a keyboard?
FYI - I found a Dell keyboard that would not allow me to boot. For fun you may want to try some other keyboard…