ArchThis Forum is for the discussion of Arch Linux.
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.
Maybe the system is busy doing something which eat all the CPU during that time. Maybe the logs will tell you what. Else I would (in Slackware) put in /etc/rc.d/rc.local (the last executed script during boot sequence) a command to write an information about processes in a file I would read afterwards.
A regular terminal prompt. You are unable to type, or change the state of caps lock, or num lock or anything keyboard related.
Is there a way to keep everything that is loading in the foreground? It seems like there is something required to load, but the Terminal/X is being loaded before it gets a chance. Can I just change the order, or require all services to fully start before starting to load the next service?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.