Code: Select all
cat /etc/os-release
Code: Select all
cat /etc/os-release
Code: Select all
apt-cache policy raspberrypi-kernel
Your kernel version should be the same as mine...IngoKnito wrote: ↑Sun Jul 22, 2018 6:57 amraspberrypi-kernel:
Installed: 1.20180703-1
Candidate: 1.20180703-1
Version table:
*** 1.20180703-1 500
500 http://archive.raspberrypi.org/debian stretch/main armhf Packages
100 /var/lib/dpkg/status
Code: Select all
~ $ apt-cache policy raspberrypi-kernel
raspberrypi-kernel:
Installed: 1.20180703-1
Candidate: 1.20180703-1
Version table:
*** 1.20180703-1 500
500 http://archive.raspberrypi.org/debian stretch/main armhf Packages
100 /var/lib/dpkg/status
Code: Select all
~ $ uname -a
Linux RPi3BP1 4.14.52-v7+ #1123 SMP Wed Jun 27 17:35:49 BST 2018 armv7l GNU/Linux
For those reading this thread it should be emphasized that the problem you are describing occurs with a Pi 1 rather than a Pi 3. While discussing similar problems with the Pi 1 in this thread may seem logical, the root cause of the problem may be different as the hardware has changed quite a bit over the years.
If your results are for the 3b+ then simply post them here, if for anything else, start a new thread.
Everything in the output looks reasonable to me. That and the fact that it was working fine before makes one think this is a 4.14.x kernel regression.