Hi @Shore,
Obviously something happened. Where I don’t know. But I suspect we can check the logs and find out why it’s not working. To do so, enter a chroot environment and from there inspect the logs:
How to chroot
-
Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.
-
Write/copy/
ddthe ISO to a USB thumb drive. -
When done, boot with the above mentioned USB thumb drive into the live environment.
-
Once booted, open a terminal and enter the following command to enter the
chrootenvironment:
manjaro-chroot -a
- If you have more than one Linux installation, select the correct one to use from the list provided.
When done, you should now be in the chroot environment.
But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.
Once successfully logged into the ch root environment, we need to find the logs. To do so, follow below inside the chroot environment:
Finding errors for boot
journalctl --priority=warning..err --no-pager --boot=-1
Where:
- The
--priority=warning..errargument limits the output to warnings and errors only; - and the
--no-pagerformats the output nicely for use here, on the forum; - the
--boot=-1argument limits the output to log messages from the previous boot. This can be adjusted to-2for the boot before that,-3to the boot before that, and so on and so forth.
Feel free to provide the logs if you cannot find the problem.