Eventually managed to connect to my old Raspberry Pi 1B. Not entirely sure which thing fixed the problem but I created a ssh file with no file extension, as a text file, as Shabaz described (who knew you could do such a thing? And why would you want to? I've never needed to do it before in 37 years of computing) which didn't resolve the problem by itself. But I then went to my local WiFi hub/router thingy and noticed that there was nothing listed as being plugged into the Ethernet. I then realised that perhaps plugging the Pi into my laptop was actually making a connection to my local network Ethernet. So I plugged the Ethernet cable directly into my WiFi hub and there is was, listed as raspberrypi. There were many shouts of great rejoicing at this point and I was tempted to stop on this great high.
It makes sense to plug directly into the hub when you think about it but when you don't know what you are doing it is not at all obvious.
It wasn't showing the IP address though so I tried pinging raspberrypi.local as suggested, nothing. So I thought I'll just ping raspberrypi as that is the name listed on the hub and there it was, now called raspberrypi.home with an IP address of 192.168.1.151. Marvellous. So I put this IP address into Putty and contact was made!
There was some message about the servers host key not being cached in the registry, no idea what that means, so I just went with Yes. Failed again. Great disappointment. Maybe it timed out, I'll give it another try. That worked without asking about server keys and whatever and I was able to login and get going.
Hooray, Hooray, Hooray. Who needs keyboards and displays, or HDMI cables! Whoppee !!!!!!!
I'm going to for a lie down now. All I have to do now is to figure out how to turn it all off. Maybe I'll just leave it al connected and logged in for the moment.
Dubbie


Top Comments