Hello,
There doesn’t seem to be a location to post questions about compiling images for deployment, so here I am. If the thread needs to be moved per Admin, cool, but hopefully we can position this so we can collectively use my work.
I have a Raspberry Pi 4B. I initially downloaded the latest ARM image, burned it with Rufus 3.10, put it in the Pi, and booted it. Nothing!! No HDMI video. I initially thought that my video card may be bad in the Pi, so I moved on. I grabbed a copy of Raspbiian and burned it using the exact same method. I popped in the SDCard to the R-Pi4B and booted it… Holy crap… There was video, so I immediately came to the conclusion that the image wasn’t compiled for R-Pi4B. Upon further research, it seems that the last compiled image was supported only for RP3B ish… It hadn’t made it to 4B yet and apparently nobody has built an image for running IPFire on an R-Pi4B yet.
Well, I need to get it to work, so I pulled down the entire branch of sourcecode for IPFire 2.x, and followed the instruction set from:
https://wiki.ipfire.org/devel/ipfire-2-x/build-howto
This was built ontop of the latest release of Functional and Bootable Raspbiian OS right on the same Raspberry Pi4B, pulled and installed, in the past couple of days. So all of the PreReqs were installed, and instruction set followed. Heck, there are only 3 real simple steps minus burning it. How hard can that be?
I didn’t get a single errors, and it built a smooth image. The story continues…
(Before someone replies and says, “Why don’t you run it on an old PC?” Well, its because I don’t want to. Thought I would get that out of the way up front. I want a rinky-dink little Pi4B running it, or I wouldn’t be going through all this trouble. LOL)
This built an image file and an MD5 File. Cool Right?
MD5 = 91e19177f508de3c13f89e05e3177886 ipfire-2.25.2gb-ext4.armv5tel-full-core144.img.xz
I again, went through the same procedure as before, using Rufus to burn the image created in the screenshot to the SDCard, but again, just like before… It doesn’t show any video. Frustrating huh?
Wiring is the microHDMI to full HDMI cable, and the Power Cord.
Also, editing is another issue to bring up. I found that there were articles eluding to editing the following in case the HDMI doesn’t show anything on the monitor. Did that as well, and the video won’t “hit a lick”. I finally reached a point where I thought I would just hoppity hop on here and see if anyone else ever tried this, had any success, or know of why on earth a simple build won’t boot. I am sure I am not the only one who’s run into this.
Here are the files as it sits right now, located on the burned SD card for Boot, so I can install IPFire 2.x
uEnv.txt
KVER=4.14.173
DTBSUNXI=sun8i-h3-nanopi-r1.dtb
root_dev=UUID=9abe2fbb-6f8a-44f4-a171-ded550343847
SERIAL-CONSOLE=OFF
Further Notes in Bold Below:
config.txt
###############################################################################
Raspberry Pi - Videocore configuration file
###############################################################################
###############################################################################
GPU Memory Settings (16,32,64 … )
###############################################################################
gpu_mem=16
###############################################################################
hdmi/video options
###############################################################################
Set this if monitor was not detected at reboot.
hdmi_force_hotplug=1 ------This Was commented out. I Un-Commented and left at 1
hdmi_drive: 0 auto, 1 DVI (no Sound), 2 HDMI (Sound)
hdmi_drive=2 ------This Was commented out. I Un-Commented and moved from 0 to 2
sdtv_mode: 0 NTSC, 1 NTSC (JP), 3 PAL, 4 PAL (Brazil)
#sdtv_mode=2
sdtv_ascpect: 0 4:3, 1 14:9, 2 16:9
sdtv_aspect=0 ------This Was commented out. I Un-Commented and left default at 0
overscan
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
###############################################################################
Turbo Mode (cpufreq) Settings …
default clocks are arm=700, core=250 and sdram=400
###############################################################################
underclock at idle
#arm_freq_min=500
#sdram_freq_min=250
use following paramters to overclock at load
#arm_freq=900
#core_freq=450
#sdram_freq=450
higher clock than 900Mhz most need over voltage. Use with care.
#over_voltage=3
################################################################################
end
################################################################################
If someone would care to review, I would appreciate it, if someone else has an R-Pi4B or can give me an idea of direction. For all I know, there may be a file that needs edited in the IPFire2.x sourcecode before I fire off the build. Documentation is scattered around, so difficult to follow at best right now.
Thanks…
