| Summary: | USB Keyboard does not work in GRUB if UEFI does not pass through UEFI Shell | ||
|---|---|---|---|
| Product: | [Hardware Platforms] MinnowBoard MAX Firmware | Reporter: | Bill Mills <wmills> |
| Component: | minnowboard-uefi-firmware | Assignee: | chao zhang <chao.b.zhang> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | Medium | CC: | scott.a.garman, warthog9 |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | MinnowBoard | ||
| OS: | x86 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Bill Mills
2014-05-20 13:51:24 UTC
I believe this is due to how the fastboot works. If you boot to SD directly, it probably does not init the USB hardware. You can do this in the GRUB build itself, but we removed that module as it conflicts with the firmware USB driver (artifact is unrecognized key presses reported). In my opinion, the correct solution is to ALWAYS enable the USB driver in the firmware since that is the only way to get a physical keyboard attached to the device. Chao, what are your thoughts? if Usb keyboard is in ConIn variable, it should be connected. If you are using debug tip. You can 1. Type in serial console to dump ConIn variable content using dmpstore command. 2. Try drivers command in shell to list all uefi driver states? 3. Try reconnect -r command to see if usb key board is avaiable after connection MinnowBoard v1 has reached new feature EOL, FW development is done as are new hardware features. If you feel EXCEEDINGLY strongly about an issue please re-open it for discussion but be aware that we are recommending individuals migrate to the MAX platform. |