Hello @Gerelyn222!
The fact that NetworkManager is missing is concerning, as thatâs the main component to allow you access to the internet. This also makes me wonder if your system is utilizing a different service, especially WPA_Supplicant for WiFi. Itâs clearly youâre getting all these errors due to the lack of internet.
Also, the fact that #4 gave you the âUnreachable Networkâ shows that whatever service other than Network Manager is running (if itâs running), does not connect you at all.
At this point, Iâd recommend you give the ethernet cable a shot and repeat the previous four commands and see what works and what doesnât.
â google.com ping statistics â
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev 24.653/24.968/25.193/0.229 ms
I tried the 1st 2 commands again after this came back hopeful. I received the same results though.
When I was rebooting, I noticed the words NetworkManager scrolling by.
I tried rebooting again so I could stop it and take note of exactly what it was saying. This didnât work. I used the Escape key to try to stop the scrolling.
The last message from the reboot was Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your internet connection or proxy settings.
Hopefully this has some good information in it for you.
Just my 2 cents from years of Raspberry Pi usage. The Raspberry Pi Operating system is by far the most functional OS you can run on the Pi. It is very similar to Ubuntu but Raspberry Pi fits the hardware better, has more available programs and much more community support. Ubuntu is huge but the project to run it on the Raspberry Pi is a tiny faction of that.
Most of the Terminal commands you run in Ubuntu or Mint will be Identical to the Raspberry Pi OS.
Hey @Gerelyn222!
What @Will says is correct. He has more than enough knowledge with the Raspbian OS - while I use my Raspberry Pi 4 with Ubuntu Server.
As far as I see from the capture you sent me, it shows that the ethernet is down on your system. The first thing youâll need to check is the IP of your router. For the sake of expediency, letâs suppose that the address is 192.168.1.1. Open up a terminal and type in - for your Ethernet (provided that it is connected):
sudo ip addr add 192.168.1.100/24 dev eth0
sudo ip link set eth0 up
sudo ip route add default via 192.168.1.1
If the response is as expected, your Pi will gain the 192.168.1.100 IP address. Keep in mind, if your Router - for example - is at the 192.168.2.1 address, then you might want to change the 192.168.1.100/24 to 192.168.2.100/24 and so on. In general, the first three numbers should be identical to your Routerâs address and only the last one to be different (for your Ethernet).
Check to see if you have internet connectivity.
ping -c 3 google.com
If that produces 0% packet loss, youâre good. If you get anything else (100% packet loss or an error), then try the next:
ping -c 3 8.8.8.8
If that produces 0% packet loss, you have Internet, but not name resolution (where names like the domains redirect to IP addresses).
Please let me know what you find, so that we can take it from there. If worse comes to worst, then Willâs recommendation can act as the âDeus Ex Machina!â
Replace the âYOUR_WIFI_SSIDâ with your actual WiFi name and replace the asterisks inside the password quotes.
Again, hit CTRL+O then Enter to save. CTRL+X to exit.
I tried both IP addresses. I received 100% packet loss on both. However, the 192.168.2.1 IP address returned RTNETLINK answers: File exists
I have started over. I reinstalled Raspberry Pi OS using the Raspberry Pi Imager. Everything looks good. My next project is to add an external drive to my Pi.
As always, itâs our pleasure, @Gerelyn222!
Per the external drives, you will not have any trouble. When you get one (or two), just make sure you format them in a Linux filesystem and give them labels. You can do that via the âDisksâ app. Once you do that, let me know and Iâll post some guidance photos to help you get them auto-mounted with their actual names for easier access.