Headless rpi02w not connecting to ssh using disk image from rpi0w

Open
#1,663 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux, raspberry-pi

Research direction

Start by reproducing the boot and network behavior with the disk image on both the Raspberry Pi Zero W and Zero 2 W, then review the Raspberry Pi OS Bullseye and SSH setup details linked in the report. Compare boot and network logs from each device; done means the image connects to Wi-Fi and accepts SSH on the Zero 2 W without breaking the original device.

Written by the indexing model from the issue text.

Description

I have a disk image, created using the steps described here (https://www.raspberrypi.com/documentation/computers/getting-started.html), from a rpi0w. I would like to run this disk image on a rpi02w.

The disk image contains the OS and various software I've put onto the rpi0w. I've validated that this disk image works on other rpi0w units, can connect to wifi, and ssh.

When I try using this disk image in a rpi02w, I see that it is booting (LED lights up and shows activity), but it does not appear on my network.

What I've tried to do:

None of these steps have resulted in seeing the rpi02w on the network or being able to SSH. After each of these steps, I validated that the SD card still worked fine in the rpi0w.

cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"

Please help!

Dominant language
No language data
Stars
5.6k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/firmware

All issues in raspberrypi/firmware

Similar issues

More Embedded & IoT issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.