That is based off of this thread: viewtopic.php?t=316528
Unfortunately that guide is A. probably the wrong one, and B. not up to date for Bookworm. Updating is on my to do list but I've not yet got there.
It should work as expected if you use RPiOS legacy (Bullseye) or earlier.
As for the external page you linked to,
- It's from 2018 and does not appear to have been updated for the three major OS revisions that have been released since then.
- It cannot be based on my guide (viewtopic.php?t=316528) as it predates it by several years. Or was that referring to my comments in that thread about the zero2w?
- It advises you use an out of date OS installation method.
- It's the usual poor and incomplete guide you find with a semi random websearch.*
Some further trouble shooting advice (plus see section 6 in the guide I just linked to):
- You have not provided enough information on what you have done and what you are seeing for me to identify the precise nature of the problem.
- If you're running RPiOS Booklworm that has switched to network manager from dhcpcd. Network manager in it's default configuration on RPiOS does not currently cope well with connections without a DHCP server that rely on mDNS/Bonjour/zeroconf. On the gadget interface this usually manifests as the interface not coming up abd having no IP address assigned.
There are workarounds but in order to use them you need a way into the zero2w that does not use the ethernet gadget. For details on several methods see Bookworm vs Bullseye - A Guide section 3 - The website you followed uses a very out of date method of installing the OS image onto your SD card and includes at least one unnecessary step - there is no need to format the card before writng the OS to it.
If you used the method in that article the OS will have stopped during its first boot and be waiting for you to specify a username and password and, possibly, prompting for WiFi details as there is no longer a default user.
Current OS installation instructions can be found here. - You'll need another way to login to the Pi to debug this.
- If the usb0 network interface is present on the Pi, it is not an ethernet gadget problem but rather a network configuration or USB host problem.
- Every third party driver I have tried recently on Windows 10 and 11 has been rejected by Windows as they are unsigned. That includes teh one supplied in the Linux kernel sources and the oft recommended Asus/Acer.** I don't have a "clean" windows 10/11 machine available to test whether mis-identification as a UART is still an issue. It wasn't on the last one I had to reinstall win 10 on a couple of weeks ago.
- RPiOS Legacy is a better choice on the zero2W and zero series. It uses dhcpcd not Network Manager for network configuration which is know to work as expected.
*: But I'm biased as I've written guides that are objectively more complete.
**: I forget which. A forum search will tell you.
Statistics: Posted by thagrol — Wed May 01, 2024 12:06 am
