Can't type encryption password unless my backup drive is connected!
 

Here's a strange one.

I recently did a totally fresh install of Fedora 27, with full encryption. Everything was working fine, at first. Then, I connected a secondary internal SATA hard disk drive, to copy over some backup files. When I removed the secondary backup HDD, the problem started: When I reboot and Fedora prompts me for my encryption password, my USB keyboard is non-responsive and I can't type my password. If I attach a PS/2 keyboard, I can type the password and continue, at which point the USB keyboard becomes responsive once again. The USB keyboard is functional in the BIOS, it is functional at the GRUB prompt, and it is functional once the computer boots. The only time the USB keyboard is non-functional is at the encryption password prompt. If I re-attach the secondary drive to the SATA cable, it restores normal function of the USB keyboard. I don't recall this problem ever happening with previous Fedora releases. I checked /etc/fstab, and there is no reference to this secondary HDD.

To recap: Typing my encryption password with the USB keyboard is only possible when the secondary backup HDD is attached to its SATA cables. Disconnecting this secondary HDD makes the USB keyboard non-responsive at the encryption password prompt. PS/2 keyboard works fine.

Any thoughts?

Strange indeed:-

Go through the dmesg log and see if there are any warnings or errors related to usb. Maybe the log will provide a hint?

That's odd.
The kind of behavior your getting sounds like a bug.

I've never hear of encryption keeping a usb device in an unresponsive state but after thinking on what you have going on it could be that there is a first time for it.

Do you get the same response on a different machine?

FWIW my usb keyboard was unresponsive after a fresh boot and had to reboot 3 times before I could sign in. I ended up purchasing a new keyboard and that solved the issue.

Another thought:-

While the secondary HDD is plugged in (keeping the system busy) it may as a result freeup the usb device somehow.
Maybe it's a dbus issue?

Thanks for your help. Sorry I haven't checked back in a while. The problem is "solved" now since a BIOS update. :)

You're Welcome-

Glad to hear a BIOS update solved the problem.