One of the very common riddle in linux community, a frequently asked one, is when a user stuck on boot after loading GRUB2.
Take a deep breath don’t be panic, even when you have kernel panic, you need to calm down. Most of the time it is just something happened in init process, sometimes it is just a display driver or else e.g. mount time, so what you need is to have a more verbose error message. All you need to do is, removing the quiet option in GRUB2.
Please Click for higher resolution.
You can remove the quiet option in GRUB2 in either way.
Temporary, by pressing e-key when booting in GRUB, and edit the entry.
Change the grub.cfg in /boot/grub/, using Live CD/DVD/USB. It will be wiped to default when you update grub later. You can also edit grub.cfg from other partition in multiboot environment.
Well, it doesn’t solve your boot problem, but at least you have a chance to investigate, what is going on in your boot process. Especially, what service issue, that might block your system.
Furthermore you should also check the log, related the service issue. e.g. XOrg when it come to display driver problem.
This is just my 2 Cents
Thank you for reading
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016