Raspbian Stretch (all 3 versions) works on ALL model Pi, have published checksums, and is maintained - at least until superseded by Buster (and for some time after).
NOTE There is no such thing as a Pi 1.
The initial releases were Raspberry Pi Model A & Model B.
There was a Raspberry Pi Model B Rev 2 and later releases increased memory to 512MB
I have ...
I wanted to update this with what I found to work in case any lost and weary Googlers are running into this issue.
Thanks to @Ingo for the link references metrics. I had no luck in adjusting the metric values for each connection, although this is due to my limited understanding of how internet connections work under the hood. After some other searching, ...
You can switch ttys from the command line using
sudo chvt 55
This is handy when you run out of Fn keys.
To create a new virtual terminal and run something on it, use openvt - for example
sudo openvt -c 55 bash
Have a look at man openvt for more details.
Full disclosure: I don't have access to a Pi connected to a monitor at the moment, so this is tested ...
You are using an experimental kernel and presumably firmware, probably from running rpi-update. There are outstanding issues with the 4.19 kernel.
"In normal circumstances there is NEVER a need to run rpi-update as it always gets you to the leading edge firmware and kernel and because that may be a testing version it could leave your RPi unbootable". ...
You can't have been using a "3B+ … for about 2 years" because it was only released just over a year ago.
The /etc/network/interfaces file you are using is obsolete, and would never have worked properly, even in Jessie.
Stretch (which was released in August 2017) uses different networking.
The 3B+ only works with firmware introduced in Stretch.
See How to ...
I suggest to install protobuf in raspberrypi 3 b+ from the default repository. With:
rpi ~$ apt list *protobuf*
you will find some packages supporting protocol buffers. Just install what you want, for example:
rpi ~$ sudo apt install python3-protobuf
You will also find the protobuf compiler if you need it. Installing from the repository has the big ...
A few things you can try to narrow down the problem:
Use ping <IP_ADDRESS> from another computer on the same network to see if your Pi is network reachable (as suggested in the comments already). Be aware that this will send ICMP packets so just make sure that your network hardware/security software will allow these to pass; if not you'll get false ...
Surprising (to me anyway) answer to the problem ... the brand of the SD card is the issue. I was using 'Binful' cards. These appear to work in every other respect on RPis and phones. I just got some SanDisk cards, and now both the RPi copier and Win32DiskImager works fine. I had tried a 3 new Binful cards, all with the same (poor) results. The SanDisk ...
I do not understand why you can't execute lxterminal. On Raspbian Stretch, not using the Light version, it is installed by default.
Anyway, if you are missing it you can just install it with:
rpi ~$ sudo apt install lxterminal
Are there any logs that I can check to debug this further?
The procedure below may interfere or be interfered with by the system networking daemon, whatever it currently is (I've lost track of this on Raspbian as have my own way of doing things). Anyway:
sudo wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlan0 -d
This will run in the ...
This is a description of a typical issue with routing. I don't know if it is your problem but it is very likely. I don't know what network managing environment do you use but many of them define default routes to each interface by default. The RasPi can use only one default route to the next gateway, means where to send packets with unknown destination. That ...
You drop the file custom-configuration.txt to the boot directory on the SD Card when it is attached to your computer. After booting the SD Card in a Raspberry Pi you should find this file with:
rpi ~$ sudo ls -l /boot/custom-configuration.txt
-rwxr-xr-x 1 root root 0 Apr 29 20:39 /boot/custom-configuration.txt
The only reason I can figure why the file ...
The good news is that the all the data in your home directory is almost certainly still there.
DO NOT reformat the SD Card - it will be readable in any Linux OS (including Raspbian).
Take this as a lesson to backup your data before updating.
I downloaded both version with release date 2019-04-08. Without doing an upgrade and without Internet connection, I then ran the command sudo apt list --installed.
I saved the results in a text file and then diffed the files. The differences are:
A solution to the problem is given below. Wanted to share my solution to this problem as I see many people are experiencing it with few solutions that actually work, short of formatting and a clean install.
One solution presented here suggested to expand the file system using:
sudo raspi-config then Advance Options > Expand Filesystem
Another user cited ...