5 Commits

Author SHA1 Message Date
Cyril Brulebois
c1be115a2f Avoid 3 known debconf prompts during deployment.
Even if those prompts and the associated answers are already documented
in “Beginner guide - How to setup a PiRogue”, it's a bit annoying to
have to go through them every time a new PiRogue is set up.

Let's pick the right answers (moving away from the default every time),
and mark those questions as seen (i.e. asked and answered):

 - Save current IPv4 rules?                           Yes → No
 - Save current IPv6 rules?                           Yes → No
 - Should non-superusers be able to capture packets?  No → Yes

Link: https://github.com/PiRogueToolSuite/pirogue-images/issues/3
2024-07-28 21:28:10 +02:00
Cyril Brulebois
132ce6a1a5 Deploy and clean rpi-resizerootfs hook and script.
Another way could be to install the Raspberry Pi kernel first, compare
the contents of the initramfses for the Debian and the Raspberry Pi
kernels, and fix the missing files in the latter. Duplicating hook and
script seems a little more straightforward.
2024-07-20 18:38:39 +02:00
Cyril Brulebois
d586813d5f Preconfigure raspi-firmware to avoid cma=64M on the kernel cmdline. 2024-07-20 18:37:05 +02:00
Cyril Brulebois
e14d454156 Install required packages for the Pi 5.
We need a specific linux-image package to boot the Pi 5 at all, plus a
newer version of firmware-brcm80211 to ensure the wlan0 interface shows
up.
2024-07-20 18:37:02 +02:00
Cyril Brulebois
d9fb46386f Boostrap a Pi 5 recipe.
For the time being, let's keep both Pi 3/Pi 4 and Pi 5 recipes separate,
making it easy to modify the latter freely. Later on, it will probably
make sense to have a common section.
2024-07-20 14:36:03 +02:00