However I still can't SSH into it from another machine on the same network. I've enabled SSH and connected it to wifi (which I've confirmed with ifconfig wlan0) and it downloads updates no problem. My ssh attempts simply sit there and do nothing the only error message I have got is from the ping attempts.Įdit: I've now installed Bullseye Lite and am running on the rPi 3 with keyboard and monitor connected no problems there. Has anyone else encountered similar problems with the newer images? Or am I doing something severely stupid that I've overlooked? Apologies for the lack error messages for troubleshooting I honestly haven't got much. But upon setting the default boot behaviour to CLI and rebooting (as I want minimal CPU usage for headless use), the pi stuck on boot sequence and I was no longer able to get anywhere at all. I enabled SSH through the GUI and was then able to SSH in from another machine. ![]() I've tried adding a wpa_supplicant and going wireless as well, but pinging with "ping -c 3 raspberrypi.local" gives an unknown host error.Īfter installing Bullseye and running on my rPi 3, there were no problems with booting into desktop using a monitor, mouse and keyboard. I've tried Bullseye, Bullseye Lite, Buster Lite, and now DietPi and I can't seem to get in through SSH with any of them. ![]() ![]() At first it seemed much easier than it used to be, but I'm finding it impossible to set up a headless pi into which I can SSH over USB (again, I've done this before countless times: flash image, create ssh file, "ssh and voila!). It's been a little while, so I have never used Bullseye or the rPi Imager before. I recently wanted to set up my pi Zero W again in a headless configuration as I usually do. ![]() I say this not to flex, but to illustrate my confusion that I am no longer able to set up a headless pi with SSH over USB. Hi guys, I've been using rPi since rPi B (2011).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |