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.)
Anything in dmesg or syslog?
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.
Our re-engineered Minster Music and Bells system has now been redeployed and
has been working in anger (sort-of) since Monday when WMT re-opened to the
public. There were one or two teething problems which I was able fix by
logging in to the system remotely.
However, I've been
I only just spotted this; it had somehow got marked as 'read' in my email
On Wednesday, 14 April 2021 18:05:27 BST CA Wills wrote:
> Now have the new main PC (NUC B10) working, we are able to print to
> printers (Laser connected on PC by USB, Colour printer via the network
Mail list logo