Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"boot" is sometimes ambiguous.....to some it mean the entire startup process, but to others is mean only the process leading up to handing control to the kernel.
For something like the GRUB bootloader, I don't think there are any error logs. Once the kernel takes over and runs "init", logs are written to /var/log.
In your case, something around "starting udev" should be in the logs.
Try analyse /var/log/syslog, Xorg.0.log, and /var/log/debug. There, at least whatever failed when kernel took over control it could be inferred easily.
By the way what were the messages when the bad config failed to boot?
We need more info regarding your problem so that we can provide help.
I am booting the system two times. First time with "bad" config and having hang, second time with "good" config to be able to inspect logs.
Do you have a working liveCD?
If I were diagnosing a problem like that, I would want to preserve as much as possible of the hang, rather then have anything overwritten by the next startup. So after the hang, I would boot a liveCD and use that to look at any remains on the hard drive from the startup that failed.
Since it was impossible to find the specific answer, I would like to find the more general answer now: how to determine hardware responsible for hang in Linux?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.