Keyboard not responding during boot process

szboardstretcher · 11-07-2012, 11:02 AM

Arch boots very fast on my computer, but I cannot type for 10+ seconds after it reaches a login prompt.

Any ideas on how to fix Arch so I can type immediately?

(I had this problem on OpenSuse years ago, don't remember what i did to fix it)

Didier Spaier · 11-08-2012, 09:59 PM

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.

szboardstretcher · 11-09-2012, 08:57 AM

I had considered this already. But there is no information relevent in the dmesg output.

I found a program called "bootchart" that claims to give insight into the boot process and what is going on.

Aside from this, do you think it could be the order of linux modules being loaded? Like maybe the keyboard or keyboard subsystem is being loaded last?

Thanks so much for your reply.

SilentSam · 11-09-2012, 01:49 PM

Which login prompt are you speaking of? If it's a DM's login screen, check /var/log/Xorg.0.log instead of dmesg.

szboardstretcher · 11-14-2012, 10:45 AM

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?

Its just annoying more than anything.

Thanks

SilentSam · 11-14-2012, 03:51 PM

I could write a really lengthy reply, but since someone has done it much better than I, check the Arch Wiki Boot Debug Entry