I have been attempting to setup a new zero 2w as a pwnagotchi, but have been having consistent issues with OTG connection for SSH.
I have successfully gotten my computer to recognize the Pi as an rdnis Ethernet device, however I have consistent issues past this point with any attempt to ping or ssh into the device timing out.
I have up to this point, installed the acer rdnis drivers,
Updated config.txt with dtoverlay=dwc2,dr_mode=peripheral
Removed dwc2 from cmdline.txt This one didn't seem to present a change either way
And was done to hopefully allow dwc2 to load normally with the optional argument
I have additionally tried installing the relative 32 bit version on an older Zero wh as well, and it presents the same issue attempting to connect.
I have tried a number of cables, although currently I am only able to go from USB-C to USB-A, which plugs into the USB-A to micro OTG adapter.
I have a USB-A to USB-A cable on the way, as well as a different OTG adapter to rule out if they are the issue.
I suspect the error is either with windows attempting to connect, or something awful with the number of USB-C protocols not liking being used for OTG.
Any help is appreciated in the meantime.
I have successfully gotten my computer to recognize the Pi as an rdnis Ethernet device, however I have consistent issues past this point with any attempt to ping or ssh into the device timing out.
I have up to this point, installed the acer rdnis drivers,
Updated config.txt with dtoverlay=dwc2,dr_mode=peripheral
Removed dwc2 from cmdline.txt This one didn't seem to present a change either way
And was done to hopefully allow dwc2 to load normally with the optional argument
I have additionally tried installing the relative 32 bit version on an older Zero wh as well, and it presents the same issue attempting to connect.
I have tried a number of cables, although currently I am only able to go from USB-C to USB-A, which plugs into the USB-A to micro OTG adapter.
I have a USB-A to USB-A cable on the way, as well as a different OTG adapter to rule out if they are the issue.
I suspect the error is either with windows attempting to connect, or something awful with the number of USB-C protocols not liking being used for OTG.
Any help is appreciated in the meantime.
Statistics: Posted by LaikaDawg — Fri Jun 21, 2024 4:20 am