On 14/11/2023 11:08, Ralph Corderoy wrote:
That's surprising. Did it look like an orderly shutdown or did the
power just cut?  My only guess at a cause is overheating though I'd
normally expect that to just cause the CPU to be throttled in speed.
Is this a laptop on a hot lap or something with adequate cooling?
I think that it simply ran out of memory after maxing out the CPU cores for a minute or two.  It shut down fairly normally, in that the machine stayed alive throughout the process, but presumably was unable to safely close all files owing to lack of resources to do it with.  This is my desktop.
Is that ‘normally’ because the system has shut itself down before?
When I said normally, I meant when I had shut it down by holding the power button in for > 7 seconds.  This time it shut down before I got round to doing it.
Has the machine booted such that it understands there is a wired network
interface, i.e. it has loaded the drivers?  ‘ip l’ should like the known
network ‘links’, i.e. interfaces.  ‘ip a’ will show any addresses
assigned to them.
Well it did until I stupidly uninstalled the network-manager package ;-(
A wired network interface can be configured at the command line but that
may be a bit long winded.
https://wiki.archlinux.org/title/Network_configuration
If I can find the repository that contains the network-manager package, I can download it onto a USB stick and install it manually on the broken machine.

--
Terry Coles


--
 Next meeting: Online, Jitsi, Tuesday, 2023-12-05 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

Reply via email to