If you installed a new OS it has a new key.
Any existing connection history on your computer is meaningless. Delete it!
If you create a ~/.ssh/config you can disable StrictHostKeyChecking.
I use the following (on my iMac) to disable ONLY for my local network (for which it is unnecessary). You may get warnings, but get the option to connect.
You already reduced the setup to a minimum to locate the error. That's what I would suggest. But there is still your network environment involved. You can try to use a wired direct device to device connection.
A fresh flashed raspios_lite_armhf will work out of the box with a wired connection. It either request an ip address from a DHCP server, or if not ...
There are really two parts to this question. Can you boot from floppy, and can you put an OS on a floppy.
As to whether you can put an OS on a floppy, yes of course you can. Quite apart from the good old days of MS-DOS 3.1, CP/M, et al, I have written small OS that will run from a floppy, it isn't difficult.
As an intellectual exercise or learning process, ...
Here are the JST connectors I used for my projects, but you will need to crimp them small enough:
Litorange 500PCS 2.54mm 2/3/4/5/6 Pin Housing JST Adapter Cable Connector Socket Male and Female JST-XH Connector Kit with Female Pin Terminal Connector Kit
I just use some breadboard jumpers and snip off one end and leave the female end for the GPIO pins.
The problem might be on Amazon's side. While you connect to the same URL in both cases, you obviously reach different physical servers which Amazon puts behind a load balancer on www.amazon.com. One of such servers has misconfigured certificates, which OpenSSL detects:
SSL certificate problem: unable to get local issuer certificate
That also explains why ...
You ignored the note in /etc/network/interfaces:
Please note that this file is written to be used with dhcpcd
For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'
Please reset it to its default setting without any stanza:
rpi ~$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
# Please note that this file is written ...
The FIRST thing you should do is get rid of the static IP Address. (what you have is wrong, but it just makes it more difficult)
What you have to do is setup Interconnect Connection Sharing on the PC and enable DHCP.
This depends on OS, and is not a Pi Question.
If you do it correctly all you need to do is plugin the Ethernet cable.
Mind you if you have a ...
If it doesn't already exist, create an autostart directory, e.g. mkdir ~/.config/autostart
Copy the .desktop file from /usr/share/applications, e.g. cp /usr/share/applications/barrier.desktop ~/.config/autostart
Check the config file has the correct setup, in my case it was here: ~/.config/Debauchee/Barrier.conf
Reboot pi and wait a few seconds for barrier ...
I have a very strange issue...
Yes - most issues are strange until you know what's behind them. But you ask this question as if you were addressing a group of fortune tellers! That's not what we do here. Learn how to ask a reasonable question - SE explains how to do that.
Unraveling "strange issues" often requires some "pick-and-shovel work&...
This is normal, if you have a new OS, you have a new fingerprint. Just do what it tells you:
ssh-keygen -f "/home/amina/.ssh/known_hosts" -R "192.168.1.31"
After that you can connect again. The warning is to avoid MITM attacks since in that case the signature would be wrong. So never execute that command if you don't know why it changed!
One option is to cut the cable in the middle and attach jumper wires compatible with RPi instead of the connector.
Another option is to modify whatever is at the other end of the cable to use the same pins as the RPi, and then simply use jumper wires to connect the two.
Adaptors are unlikely to exist because you will want to choose to which pins you connect, ...
There are a number of problems that can cause your Pi to be not-recognized.
I will dispense with the hardware connectivity; I assume you that works.
If you do not know the Pi's address, and you have a DHCP server (often as part of you (A)DSL router or cable modem), you can check what new address is being handed-out. Pi's are normally B8:27:EB, DC:A6:32 or E4:...
Not a complete solution because lack of detailed information what you exactly have tried. But here are some clarifications to questions from comments that may help.
As noted in the guide:
But you have to do a complete switch. There is no way to mix up with Debian networking and/or dhcpcd.
In the past I have tried to just disable that services but run into ...
I'm certain the problem is that you use a static ip address. Most questions on this site are about static ip addresses. No, it does not make things simple. On the contrary, it makes things more complicated if you do not understand detailed networking. Please have a look at all the other answers about static ip address.
Answering your points:
Sometimes when ...
There are several options to achieve what you want. It depends on your use case. If you do not need to access the PC from a device on your local network then you can use NAT (Network Address Translation) which makes routing configuration simple. Here is an example How to make Raspberry Pi 4 as “WIFI” -> “Ethernet” adaptor without add any USB component?.
buy a cable. Look into cables for phones which support fast charge at 5V. Check the AWG rating printed on the cable: try getting something with AWG 22 or less. Pick one which is as short as required, not longer.
build a cable. Get a DIY USB cable connector and pick a couple of wires for 5V and GND. I've made such a cable for a Pi 4 using AWG ...
You could maybe try a web interface with flask if your remote device and controller are both connected to wifi - here's some links to help you with that
Intro to flask on raspberry pi
Flask video streaming
Using GPIO with flask
Hope that helps and good luck with your project :)
I would suggest using a Raspberry Pi servo hat if you're just starting out and want to learn how to use servos.
There are a lot of them on the market but I'd go with something from Adafruit as they have a lot of very nice tutorials to go along with their products.
On that page they also link to an article on external ...
SSH has a really cool "jump host" option; basically, it allows you to jump through to another host on the network:
Connect to the target host by first making a ssh connection to the jump host described by destination and then establishing a TCP forwarding to the ultimate destination from there. Multiple jump hops may be ...
Try this from your PC instead:
$ ssh pi@XXX.XX.XXX.XXX
Instead of XXX.XX.XXX.XXX, use one of the IP addresses you got from hostname -I. You might try one, and then the other.
Why 2 addresses?
The answer can be found by entering man hostname... refer to the -I option. Learn to use the system manuals - there is (usually) one for every command.
If you know the IP address or DNS are correct, you can use:
$ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no firstname.lastname@example.org
This can be added to your ssh config, however, not recommended, after confirm the connection is ok, use the 'ssh-keygen' command suggested by ssh.
This may be what you're looking for: SparkFun's Breadboard to JST-ZHR Cable
As a bonus, SparkFun sells the SPS30 with the breakout cable for $47 - about HALF the price it goes for on Digikey (without the breakout cable)
WiFi Direct is not specific to video: you will be running a multimedia protocol such as Miracast on top of it. There are a few projects out there, the most promising being miraclecast, though none of them worked for me (on a Pi 4). Perhaps you will be more lucky with your Pi 3.
Note that the opposite task (sending the video stream to the Pi) seems to be much ...
If you are a decent programmer you can use pigpio waves to generate the signal.
This is a Python example which uses the kind of techniques you will need to use.
Problem solved! The issue was my ethernet cable: even though all LEDs were on, and even though it worked on other computers, changing it made it work. I have no real ideas on why the Raspberry Pi didn't accept it, but still didn't complain about it...
When making the image from scratch, don't forget to enable ssh by creating a file named ssh on the SD before you put it in the pi. While you are at it, add a line to cmdline.txt that says
or similar. ( IP must be within the proper subnet.)
When in a similar situation with other devices that don't have static ip capabilities, sometimes I ...