Updated test images (2022-04-04-2)

53 views
Skip to first unread message

Chris Burton

unread,
May 15, 2022, 1:35:18 PMMay 15
to ClusterHAT
I've uploaded new test images based on 2022-04-04 Bullseye (32/64-bit) and Buster to https://dist.8086.net/clusterctrl/testing/

This is an update to the 2022-04-04-1 test image, trying to resolve the "NETDEV WATCHDOG: ethpi1 (rndis_host): transmit queue 0 timed out" issue.

The only difference is disabling/removing modemmanager. If you're using the 2022-04-04-1 test images you can disable it by running the following commands.

sudo systemctl disable ModemManager.service
sudo systemctl stop ModemManager.service
sudo apt -y purge modemmanager
sudo apt-mark hold modemmanager

If you haven't used the previous test image please read below about the changes.

When using the Bullseye images please remember you need to set a user/password before booting if you're using it headless otherwise you won't be able to login (the Px images need this too as they can't setup over the serial console).

This can either be done using Raspberry Pi Imager or manually with a userconf.txt file in the boot partition (see https://www.raspberrypi.com/news/raspberry-pi-bullseye-update-april-2022/ ).

The Bullseye usbboot archives also need a userconf.txt. Once the usbboot archive has been extracted you can use something like this to create a password for p1.

cd /var/lib/clusterctrl/nfs/p1
set +o history # Turn off bash history temporarily
# Replace myusername and mypassword with your details
echo "myusername:"$(echo 'mypassword' | openssl passwd -6 -stdin) > boot/userconf.txt
set -o history # Turn history back on again

You can then "touch boot/ssh" to enable SSH if needed and run "usbboot-init 1" as normal and it's ready to power on p1.

It can take 5 minutes or more for a first boot of all images so please be patient!

If you have problems with the images or suggestions, please open a ticket at https://secure.8086.net/billing/submitticket.php?step=2&deptid=1 or create a new thread with details of the image filename, model of Pi you're using, any additional commands you've ran etc. so I can try to replicate the problem.

Chris.
Reply all
Reply to author
Forward
0 new messages