Fedora IOT 33 aarch64 on Raspberry Pi

mpphill2 · November 24, 2020, 2:09am

Hi all,

I recently purchased a Raspberry Pi 4 (only the 2GB RAM) with the intentions of using it as a pi-hole. I decided to try and use the aarch64 image since the model 4 is supposed to be capable of 64-bit. I ran the command below to install it on the SD card:

sudo arm-image-installer --image=Fedora-IoT-33-20201102.0.aarch64.raw.xz --target=rpi4 --media=/dev/mmcblk0 --resizefs

It wrote to the SD card successfully but when I try to boot the Pi - nothing. Am I doing something wrong here or any thoughts on troubleshoot? I did connect it to my Sharp TV but I’ve connected other computers to it just fine. Should I just use the ARMv7 image? Thanks!

mattdm · November 24, 2020, 4:10pm

I believe it should work, but it’s possible there’s a problem with the video output. I’d try the 32-bit version as a first diagnostic step.

coremodule · November 25, 2020, 2:13pm

I have had problems in the past with having the micro HDMI cable plugged into the wrong port since the RPi4 has dual video out. You could try moving the cable to the other port and see if you get any output.

mmorrell2016 · November 26, 2020, 6:41pm

Things you can try for debug.

make sure firmware on pi is up to date.
you should see the four raspberry display and uboot countdown timeout when you power up the pi.
Try a different SD card
I have F33-IoT 64bit running on my RPI4 no problems.

mpphill2 · November 28, 2020, 10:54pm

I just plugged it into a normal monitor and it came up great! Is there a default user because it put me at a login prompt but I had not set up a user or password. Couldn’t log in. I’m reflashing the SD card again just to see if I missed something.

ETA: Ah, I see that reading is fundamental. I hadn’t seen read the section “Setting up the device with Zezere” because I didn’t think it applied to me. Looks like it was part of the process. Hope rewriting the image isn’t too bad on the SD card lol.

I’m excited to get this up and going! I hope the pi-hole container plays nice with podman!

mpphill2 · November 28, 2020, 11:11pm

Can someone help elaborate on how I’m supposed to log into this? I made some SSH keys and followed the guide but I don’t understand when it says open a terminal and SSH in through the root. I haven’t set up an IP address yet? I try logging into the device locally with root and the password I set up. What am I missing?

mpphill2 · November 28, 2020, 11:24pm

Okay I got. I feel like an imposter, I’m a network engineer by day so I should have figured it out sooner.

Once you copy over the public key you have to go to the router and compare the MAC address of the Pi to those in the DHCP lease table. Once you have the IP address you just point your SSH to that with the private key you set up.

ssh root@192.168.0.31 -i /var/home/matthew/Downloads/ssh

mpphill2 · November 29, 2020, 12:30am

Alright, I’m so close but I’m running into one error when I try to pull and then run the container. It needs port 53 open but when I try to specify the port in the podman run command it says it is already in use. How can I troubleshoot this?

I am specifically trying to use the podman run command equivalent to the docker run command found here:

github.com

pi-hole/docker-pi-hole/blob/master/docker_run.sh

#!/bin/bash

# https://github.com/pi-hole/docker-pi-hole/blob/master/README.md

PIHOLE_BASE="${PIHOLE_BASE:-$(pwd)}"
[[ -d "$PIHOLE_BASE" ]] || mkdir -p "$PIHOLE_BASE" || { echo "Couldn't create storage directory: $PIHOLE_BASE"; exit 1; }

# Note: ServerIP should be replaced with your external ip.
docker run -d \
    --name pihole \
    -p 53:53/tcp -p 53:53/udp \
    -p 80:80 \
    -p 443:443 \
    -e TZ="America/Chicago" \
    -v "${PIHOLE_BASE}/etc-pihole/:/etc/pihole/" \
    -v "${PIHOLE_BASE}/etc-dnsmasq.d/:/etc/dnsmasq.d/" \
    --dns=127.0.0.1 --dns=1.1.1.1 \
    --restart=unless-stopped \
    --hostname pi.hole \
    -e VIRTUAL_HOST="pi.hole" \

This file has been truncated. show original

mpphill2 · November 29, 2020, 2:23am

Solution was to stop the systemd-resolved service. I just tried using the DNS address locally and it is now working whereas it wasn’t if I left off the port 53 from the podman run command.

I’m about to set up my router to point to it as the DNS address automatically, fingers crossed.

ETA: My old Spectrum router doesn’t have the option. No matter, it works great just setting the DNS locally on each device. I am also about to move soon and will buy my own router for the new place.

Fedora 33 IOT aarch64 + Pi-hole via podman works great! I am very happy with this solution.

mmorrell2016 · November 30, 2020, 2:37am

Hi mpphill2. Your experience was almost exactly the same as mine the first time I set up Fedora-IoT. BTW, if you don’t want to use the Zerere service to provision ssh keys, check out some the command line options when running the arm-image-installer. As for the Pi-Hole setup, if you uncomment the line for DNSStubListener=no in /etc/systemd/resolved.conf, then you don’t need to stop/disable the systemd-resolved service. This will just disable the stub listener that is using port 53.