On Saturday, 17 April 2021 12:58:23 BST Hamish McIntyre-Bhatty wrote:
> Anything in dmesg or syslog?
Nothing useful. I rebooted twice this morning; each time after making a
change to the Python code. (A reboot is the safest way of ensuring everything
starts off the same as at powerup.)
At 0817 I can see the usb0 interface connecting to the assigned (static) IP
address in syslog, but not anything about the second reboot a few minutes
later after I had realised that a typo was preventing the Python code from
running. The next time it occurs is at 0919 when the power cycle took effect.
I did nothing between the reboot that locked the system and the power cycle
(other than panic a bit of course).
> I have had issues like this with Pis before, but there should be a fix
> in the latest kernel for this - maybe try installing updates or use
> rpi-update for new kernel if it persists? My issue was with more
> standard RJ45 networking, but may still apply.
I ran apt update / upgrade just before the system was physically deployed
about two weeks ago.
I remember getting into some trouble some time ago when using rpi-update.
Here is what RaspberryPi.org say:
'rpi-update is a command line application that will update your Raspberry Pi
OS kernel and VideoCore firmware to the latest pre-release versions. WARNING:
Pre-release versions of software are not guaranteed to work. You should not
use rpi-update on any system unless recommended to do so by a Raspberry Pi
engineer'
That would definitely be a last resort.
--
Terry Coles
--
Next meeting: Online, Jitsi, Tuesday, 2021-05-04 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
