Like the title I wrote says, the boot process is permanently staying without proceeding to next step.
What should I do in this situation?
Surely, I used the CLI environment by pressing Ctrl + Alt + F4 (In my case, I use tty4), but I need to use the GUI environment as well.
/var/log/Xorg.0.log may tell more about why GUI is dead.
Ah, then, can I check some reasons why it happened on the CLI (Ctrl + Alt + F4) environment with your suggestion?
A better way is running ssh to access the board as you can send the whole file out and attach it here…
You can use the CLI to check the IP of the board first.
Btw, serial console also allows login even if networking is down (I mention this because if you have Wi-Fi it is often not enabled until after the GUI login). There is also the local console login; if you use CTRL+ALT+F2 through CTRL+ALT+F6 from a GUI, then it goes to the other login session, and those do not use the GUI. If you are not in a GUI, just skip the CTRL and use ALT+F1 through ALT+F6 (ALT+F1 would take you back to the GUI).
ssh is best because it allows you to copy the log file via scp. Serial console is close because it can log a session, and you can just “cat” the log file.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
