After pkg update (2017-02-13) keyboard doesn't work at lightdm prompt
After a clean install of OpenIndiana Hipster 2016.10, I immediately performed
pkg refresh --full then
After reboot, the USB keyboard no longer worked at the lightdm login prompt, although the USB mouse works. Clicking the username and password text boxes works as expected, and the GUI appears to be responsive and working. When I press the
C keys at the lightdm prompt, lightdm disappears and I am dropped to a virtual terminal. A screenshot of the contents of the terminal are attached.
No changes were made to OpenIndiana except for updating it. Nothing was configured or installed except the base system.
This hardware works fine with Ubuntu, Debian, CentOS and other Linux distros. It also works well with FreeBSD 10.4 and 11.0.
This issue happens on both 'bare metal' as well as in a VirtualBox virtual-machine, Version 5.1.14 r112924.Hardware information:
- Intel Core(TM) i5-4590 CPU @ 3.30GHz
- Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
- PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
- Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
- USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
- Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
- PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0)
- SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
- VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670]
- Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Updated by Will B almost 5 years ago
This issue appears to happen when the computer is shut down completely after installation then restarted, and also when the computer is shut down completely then restarted after the first
pkg refresh and
When 'fast reboot' is used instead of shutting down between steps, this problem does not seem to occur.