Precompiled Image Raspberry pi #746
RACHIT G. SHARMA (2026-07-08 04:56)
· 386 view(s)
· 1 comment(s)
upon burning the precompiled image on the raspi the pivr startup service fails on boot and the id and password of the image is also missing request for documentation.
Simon Orlob (2026-09-01 18:29)
We booted `pivr-260617.img.xz` (64-bit, built 2026-06-17) on a Raspberry Pi 5 from SD. Four things from the image that cover both questions.
## The address is hardcoded
`/etc/NetworkManager/system-connections/eth0-connection.nmconnection`:
[ipv4]
method=manual
address1=192.168.137.2/24
dns=none
No gateway, no DNS, and no preconfigured WiFi profile. On a network that hands out addresses by DHCP the Pi does not appear where you expect it, which looks like a boot failure. avahi is
enabled, so mDNS answers regardless of subnet:
$ getent hosts raspberrypi.local
192.168.137.2 raspberrypi.local
To reach that address from a machine on a different subnet, add a second address on the same wire:
sudo ip addr add 192.168.137.200/24 dev
Note that `/etc/dnsmasq.conf` also runs a DHCP server on `eth0` handing out `192.168.137.50-100`, and answers `apple.com` and `google.com` with the Pi's own address. On a shared network that is a second DHCP server on the broadcast domain.
## Changing eth0 to DHCP
After first boot, `/data/nm` is bind-mounted over `/etc/NetworkManager/system-connections`. The live profile is on partition 3, and the copy in the rootfs is masked. On the Pi:
sudo nmcli connection modify eth0-connection ipv4.method auto ipv4.addresses "" ipv4.gateway ""
sudo reboot
Editing offline from the boot device instead: patch both copies, `root:root` mode 0600 — NetworkManager ignores keyfiles with other ownership or permissions.
## Web control panel
`http:///`, password `0000`, from `/pivr/config/.env`:
CONTROL_PANEL_PW=0000
Confirmed on the running Pi: `POST /form.php` with `job=login&pw=0000` returns `{"success":true}`. (#304 mentions `2017`; this image uses `0000`.) The panel covers device configuration, logs,
first-boot status, timesync and reboot, so day-to-day use needs no Linux login.
## SSH
sshd is enabled and running — `ssh.service` is in `multi-user.target.wants`, port 22 is open, and the server offers `publickey,password`. What is missing is a credential. The `pi` user's password is a yescrypt hash set at build time and is not published in the image; there is no `userconf.txt` on the boot partition and no `firstboot` hook in `cmdline.txt` to process one. `/home/pi` contains only `.bash_logout`, `.bashrc` and `.profile` — no `.ssh` directory.
Mount partition 2 (rootfs, ext4) of the boot device and add a key:
mkdir -p /mnt/rootfs/home/pi/.ssh
cp your_key.pub /mnt/rootfs/home/pi/.ssh/authorized_keys
chown -R 1000:1000 /mnt/rootfs/home/pi/.ssh
chmod 700 /mnt/rootfs/home/pi/.ssh
chmod 600 /mnt/rootfs/home/pi/.ssh/authorized_keys
## The address is hardcoded
`/etc/NetworkManager/system-connections/eth0-connection.nmconnection`:
[ipv4]
method=manual
address1=192.168.137.2/24
dns=none
No gateway, no DNS, and no preconfigured WiFi profile. On a network that hands out addresses by DHCP the Pi does not appear where you expect it, which looks like a boot failure. avahi is
enabled, so mDNS answers regardless of subnet:
$ getent hosts raspberrypi.local
192.168.137.2 raspberrypi.local
To reach that address from a machine on a different subnet, add a second address on the same wire:
sudo ip addr add 192.168.137.200/24 dev
Note that `/etc/dnsmasq.conf` also runs a DHCP server on `eth0` handing out `192.168.137.50-100`, and answers `apple.com` and `google.com` with the Pi's own address. On a shared network that is a second DHCP server on the broadcast domain.
## Changing eth0 to DHCP
After first boot, `/data/nm` is bind-mounted over `/etc/NetworkManager/system-connections`. The live profile is on partition 3, and the copy in the rootfs is masked. On the Pi:
sudo nmcli connection modify eth0-connection ipv4.method auto ipv4.addresses "" ipv4.gateway ""
sudo reboot
Editing offline from the boot device instead: patch both copies, `root:root` mode 0600 — NetworkManager ignores keyfiles with other ownership or permissions.
## Web control panel
`http://
CONTROL_PANEL_PW=0000
Confirmed on the running Pi: `POST /form.php` with `job=login&pw=0000` returns `{"success":true}`. (#304 mentions `2017`; this image uses `0000`.) The panel covers device configuration, logs,
first-boot status, timesync and reboot, so day-to-day use needs no Linux login.
## SSH
sshd is enabled and running — `ssh.service` is in `multi-user.target.wants`, port 22 is open, and the server offers `publickey,password`. What is missing is a credential. The `pi` user's password is a yescrypt hash set at build time and is not published in the image; there is no `userconf.txt` on the boot partition and no `firstboot` hook in `cmdline.txt` to process one. `/home/pi` contains only `.bash_logout`, `.bashrc` and `.profile` — no `.ssh` directory.
Mount partition 2 (rootfs, ext4) of the boot device and add a key:
mkdir -p /mnt/rootfs/home/pi/.ssh
cp your_key.pub /mnt/rootfs/home/pi/.ssh/authorized_keys
chown -R 1000:1000 /mnt/rootfs/home/pi/.ssh
chmod 700 /mnt/rootfs/home/pi/.ssh
chmod 600 /mnt/rootfs/home/pi/.ssh/authorized_keys