Comment 5 for bug 1385089

I got logs from good and bad boots under different configurations.

I have a bad boot with all my hacks in place
a bad one with all my hacks disabled and debug logging for plymouth
the same after putting the computer to sleep and waking it up again.
and a good boot strangely this was under default debug configuration

and the i915 stuff is to tune the gpu for better performance and power efficiency, I don't think it had any effect as I still had the problem after removing them.

unfortunate I don't think those logs are gonna be much help, is there a way to get lightdm and x to be more detailed in there logs or to get log entries somewhere when process start and stop, that is when executives are run and when they die in order.

is there a way to get information on the input devices from a command line, I can ssh in after booting so if I could see the state of the keyboard from the system it might shed some light or maybe a way to work around it.

I know if I plug in an external keyboard it works but the internal one doesn't till the computer is put to sleep and woke back up again, I loged in with a usb keyboard once, thought the internal one might start working once the computer was loged in but nope, didn't work.