The above explains clearly why it doesn’t work but it doesn’t help you further, so let the machine sit there for 1 minute when this happens and then please read this: How to provide good information
and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information… (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.
A journalctl --system --boot=-1 | tail --lines=50 might be helpful too, although that one might be corrupted by the kernel panic, so it’s a coin- toss whether that’ll give us the information we need.
