PC keyboard not always detected after reboot

There is a little annoying phenomenon in my brand new PC system with
Windows10Pro.
The PC is a most modern mainboard ASUS Prime z370P-II and Intel I7 9700k.
The keyboard is an unicomp "spacesaver" PC full sized keyboard, a
rebuild of the IBM "loudly klicking" M-model versions. It is a pure USB
keyboard, so I do not use any PS/2 adapters.


Mostly when restarting the PC, the keyboard is properly detected and i
can enter my PIN or password to log into the system.

But frequently when rebooting e.g. after Windows Update, the keyboard IS
NOT DETECTED properly, or at least it fails to respond to any keys, and
NUM-LOCK light will not go on/off when pressing NUMLOCK so i assume the
keyboard gets no power or is not detected.

When this happens, i must pull the keyboard usb plug (the system makes
the usb sound) and re-plug it in (the system makes the sound again) and
then the keyboard works fine.
Stupid ... having to crawl under the table ;-)


Does anyone know of some kind of trick to e.g. re-initialize all USB
ports on startup, or to call some staggered event in scheduler (before
having to log into the user) to force detection of keyboard?

As francly i don't believe that the spacesaver keyboard is broken...


greetings



Roland Schweiger

On Sat, 28 Sep 2019 20:32:40 +0200, Roland Schweiger wrote:

There is a little annoying phenomenon in my brand new PC system with
Windows10Pro.
The PC is a most modern mainboard ASUS Prime z370P-II and Intel I7 9700k.
The keyboard is an unicomp "spacesaver" PC full sized keyboard, a
rebuild of the IBM "loudly klicking" M-model versions. It is a pure USB
keyboard, so I do not use any PS/2 adapters.


Mostly when restarting the PC, the keyboard is properly detected and i
can enter my PIN or password to log into the system.

But frequently when rebooting e.g. after Windows Update, the keyboard IS
NOT DETECTED properly, or at least it fails to respond to any keys, and
NUM-LOCK light will not go on/off when pressing NUMLOCK so i assume the
keyboard gets no power or is not detected.

When this happens, i must pull the keyboard usb plug (the system makes
the usb sound) and re-plug it in (the system makes the sound again) and
then the keyboard works fine.
Stupid ... having to crawl under the table ;-)

Are you using the USB2.0 socket(s) for the keyboard/mouse? They are the
two in the same block as the dual PS/2 socket.

--
Regards - Rodney Pont
The from address exists but is mostly dumped,
please send any emails to the address below
e-mail rpont (at) gmail (dot) com

On 9/28/19 11:32 AM, Roland Schweiger wrote:
There is a little annoying phenomenon in my brand new PC system with
Windows10Pro.
The PC is a most modern mainboard ASUS Prime z370P-II and Intel I7 9700k.
The keyboard is an unicomp "spacesaver" PC full sized keyboard, a
rebuild of the IBM "loudly klicking" M-model versions. It is a pure USB
keyboard, so I do not use any PS/2 adapters.


Mostly when restarting the PC, the keyboard is properly detected and i
can enter my PIN or password to log into the system.

But frequently when rebooting e.g. after Windows Update, the keyboard IS
NOT DETECTED properly, or at least it fails to respond to any keys, and
NUM-LOCK light will not go on/off when pressing NUMLOCK so i assume the
keyboard gets no power or is not detected.

When this happens, i must pull the keyboard usb plug (the system makes
the usb sound) and re-plug it in (the system makes the sound again) and
then the keyboard works fine.
Stupid ... having to crawl under the table ;-)


Does anyone know of some kind of trick to e.g. re-initialize all USB
ports on startup, or to call some staggered event in scheduler (before
having to log into the user) to force detection of keyboard?

As francly i don't believe that the spacesaver keyboard is broken...


greetings



Roland Schweiger

Hi Roland,

Sometimes USB 3 is not compatible with USB 2 keyboards.
Trying moving your keyboard to a USB 2 slot. Usb 2
slots usually have black tangs and usb 3 typically
have blue tangs.

Love Unicomp keyboards!

-T

On Sat, 28 Sep 2019 20:32:40 +0200, Roland Schweiger wrote:

But frequently when rebooting e.g. after Windows Update, the keyboard IS
NOT DETECTED properly, or at least it fails to respond to any keys,

I have a similar problem.

One out of 10 reboots (something like that) for the past six months or so,
won't accept EITHER the keyboard or the mouse.

Win10 Pro.

It doesn't matter if they're plugged in or not, and the equipment, while
old, is standard IBM & Logitech stuff.

I'll keep an eye on this thread, as it ONLY happens in about 10% of the
reboots, and never anytime else.

On Sat, 28 Sep 2019 20:03:57 +0100 (BST), rp wrote:

Are you using the USB2.0 socket(s) for the keyboard/mouse? They are the
two in the same block as the dual PS/2 socket.

Why would that matter?

There are usually LOTS of USB sockets on a desktop, front and back, where
even the monitor has USB sockets.

Yes, there are two on the very bottom of the back of the desktop, which, I
guess, are the ones you're talking about.

But why would it matter for the purpose of booting errors?
I thought the two on the very bottom were simply the slow ones.

Roland Schweiger wrote:

There is a little annoying phenomenon in my brand new PC system with
Windows10Pro.

The PC is a most modern mainboard ASUS Prime z370P-II and Intel I7
9700k. The keyboard is an unicomp "spacesaver" PC full sized
keyboard, a rebuild of the IBM "loudly klicking" M-model versions. It
is a pure USB keyboard, so I do not use any PS/2 adapters.

Mostly when restarting the PC, the keyboard is properly detected and i
can enter my PIN or password to log into the system. But frequently
when rebooting e.g. after Windows Update, the keyboard IS NOT
DETECTED properly, or at least it fails to respond to any keys, and
NUM-LOCK light will not go on/off when pressing NUMLOCK so i assume
the keyboard gets no power or is not detected.

When this happens, i must pull the keyboard usb plug (the system makes
the usb sound) and re-plug it in (the system makes the sound again)
and then the keyboard works fine. Stupid ... having to crawl under
the table ;-)

Does anyone know of some kind of trick to e.g. re-initialize all USB
ports on startup, or to call some staggered event in scheduler
(before having to log into the user) to force detection of keyboard?

- New build. Hear any beeps on a *cold* boot?
- Does the keyboard always work to get into the UEFI settings, and it's
only after loading Windows that the keyboard might be unresponsive?
If so, disable all startup programs and retest.
- Do the LEDs (NumLock, CapsLock, ScrollLock) flash on a cold boot, even
when a cold boot results in an non-working keyboard? As part of a
cold boot, the CPU sends a reset signal to all hardware to put it into
a known or initial starting state. The LED flash tells you the
keyboard got a reset.
- What brand and model of PSU did you install? Wattage/VA rating?
- Go into the BIOS and disable Fast/Quick Boot. Do the same in Win10.
- Check the CSM (Compatibility Support Module) setting. Can be Auto,
Enabled, or Disabled. This hardware setting configures support for
VGA, bootable devices, and add-on device for better compatibility.
CSM is part of the UEFI firmware that provides support for legacy
devices by emulating a BIOS environment. You never identified the
keyboard, so no way anyone else can determine how old it is.
- If you've done any UEFI tweaking, you might want to try resetting to
factory defaults and retest under that config setup.

From the mobo's manual, page 2-12:
Due to the design of the Intel 300 series chipset, all USB devices
connected to the USB 2.0 and USB 3.2 Gen 1 ports are controlled by the
xHCI controller. Some legacy USB devices must update their firmware for
better compatibility.

Again, the keyboard was not identified by brand and model. Unicomp is a
company name, not a model number. Unicomp (https://www.pckeyboard.com/)
is still around, so don't know if you have an old or new keyboard. No
way to know what USB port type it uses (USB 1.x, 2.0, 3.x). How long
have you owned the Unicomp unknown model keyboard? Was it new for your
new build, or something you've been migrating from one build to the
next?

T wrote:
On 9/28/19 11:32 AM, Roland Schweiger wrote:
There is a little annoying phenomenon in my brand new PC system with
Windows10Pro.
The PC is a most modern mainboard ASUS Prime z370P-II and Intel I7 9700k.
The keyboard is an unicomp "spacesaver" PC full sized keyboard, a
rebuild of the IBM "loudly klicking" M-model versions. It is a pure
USB keyboard, so I do not use any PS/2 adapters.


Mostly when restarting the PC, the keyboard is properly detected and i
can enter my PIN or password to log into the system.

But frequently when rebooting e.g. after Windows Update, the keyboard
IS NOT DETECTED properly, or at least it fails to respond to any keys,
and NUM-LOCK light will not go on/off when pressing NUMLOCK so i
assume the keyboard gets no power or is not detected.

When this happens, i must pull the keyboard usb plug (the system makes
the usb sound) and re-plug it in (the system makes the sound again)
and then the keyboard works fine.
Stupid ... having to crawl under the table ;-)


Does anyone know of some kind of trick to e.g. re-initialize all USB
ports on startup, or to call some staggered event in scheduler (before
having to log into the user) to force detection of keyboard?

As francly i don't believe that the spacesaver keyboard is broken...


greetings



Roland Schweiger

Hi Roland,

Sometimes USB 3 is not compatible with USB 2 keyboards.
Trying moving your keyboard to a USB 2 slot. Usb 2
slots usually have black tangs and usb 3 typically
have blue tangs.

Love Unicomp keyboards!

-T

Roland has two "very obvious looking" USB2 connectors
just below the combo PS/2 connector. I'm sure that's
where the keyboard is connected.

His motherboard also has USB2 headers ("USB34", "USB56"),
and using a USB2 header to PCI slot adapter, you could add more
USB2 connectors to the back of the PC if desired. If you buy
a lot of Asus motherboards, you'll usually have a couple
of those adapters kicking around from the year 2005 or so.

His system also has a UEFI setting.

"USB power delivery in Soft Off state(S5)"

and maybe keeping the USB power on would help.

Because his problem is sporadic, that means the chances
a setting is going to help, are pretty slim.

Paul

Paul wrote:

Because his problem is sporadic, that means the chances
a setting is going to help, are pretty slim.

Maybe connect the KB via an externally powered hub?

Andy Burns wrote:
Paul wrote:

Because his problem is sporadic, that means the chances
a setting is going to help, are pretty slim.

Maybe connect the KB via an externally powered hub?

Might work.

Maybe the keyboard is slow coming out of power-on-reset
or something.

Paul

On 9/29/19 1:28 AM, Paul wrote:
Andy Burns wrote:
Paul wrote:

Because his problem is sporadic, that means the chances
a setting is going to help, are pretty slim.

Maybe connect the KB via an externally powered hub?

Might work.

Maybe the keyboard is slow coming out of power-on-reset
or something.

Â*Â* Paul

Gee wiz, exactly how few usb ports does this motherboard have?
No USB 2 only ports?

T wrote:
On 9/29/19 1:28 AM, Paul wrote:
Andy Burns wrote:
Paul wrote:

Because his problem is sporadic, that means the chances
a setting is going to help, are pretty slim.

Maybe connect the KB via an externally powered hub?

Might work.

Maybe the keyboard is slow coming out of power-on-reset
or something.

Paul

Gee wiz, exactly how few usb ports does this motherboard have?
No USB 2 only ports?

It has a total of six USB2 ports.

Two under the PS/2 connector, plus four more as
USB2 headers on the motherboard (two 2x5 connectors).

Paul

Roland wrote:
i must pull the keyboard usb plug (the system makes
the usb sound) and re-plug it in (the system makes the
sound again) and then the keyboard works fine.

Have you installed the proper drivers, for the keyboard ?