Hello everyone,
Our system has a “black box” keyboard controller in between the keyboard
controller in the super i/o and the ps/2 keyboard. The ps/2 keyboard works
fine in POST and DOS. But when we boot Windows 2000, the i8042prt.sys
driver is loaded but stopped. As a result, the ps/2 keyboard no longer
works. We hooked up the kernel debugger and found that we get the
following error message:
“Mapper: No keyboard match found”
Does anyone know what Windows 2000 is looking for? What is Windows 2000
trying to match? Is it the keyboard ID?
Can someone explain how this keyboard detection works and suggest how I can
get the debugger to spit out more detailed messages?
Thanks.
Sammy Hui
Software Engineer
RadiSys Corporation
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
It means the keyboard ID that the system got from the firmware (stored under
the HKLM\Hardware\Desciption key)doesn’t match with system known IDs. The
IDs that system can recognize is given in the keyboard.inf file.
;
; This section is used during startup by the Windows NT Plug&Play Manager to
; simulate enumeration of the keyboard based on information retrieved from
; ARC firmware/NTDETECT.
;
XT_83KEY = *PNP0300
PCAT_86KEY = *PNP0301
PCXT_84KEY = *PNP0302
XT_84KEY = *PNP0302
101-KEY = *PNP0303
OLI_83KEY = *PNP0304
ATT_301 = *PNP0304
OLI_102KEY = *PNP0305
OLI_86KEY = *PNP0306
OLI_A101_102KEY = *PNP0309
ATT_302 = *PNP030a
PCAT_ENHANCED = *PNP030b
What is your firmware reporting?
-----Original Message-----
From: xxxxx@radisys.com [mailto:xxxxx@radisys.com]
Sent: Friday, February 09, 2001 9:45 AM
To: NT Developers Interest List
Subject: [ntdev] Mapper: No keyboard match found
Hello everyone,
Our system has a “black box” keyboard controller in between the keyboard
controller in the super i/o and the ps/2 keyboard. The ps/2 keyboard works
fine in POST and DOS. But when we boot Windows 2000, the i8042prt.sys
driver is loaded but stopped. As a result, the ps/2 keyboard no longer
works. We hooked up the kernel debugger and found that we get the
following error message:
“Mapper: No keyboard match found”
Does anyone know what Windows 2000 is looking for? What is Windows 2000
trying to match? Is it the keyboard ID?
Can someone explain how this keyboard detection works and suggest how I can
get the debugger to spit out more detailed messages?
Thanks.
Sammy Hui
Software Engineer
RadiSys Corporation
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Eliyas,
During the OS selection screen (boot.ini) if I let it timeout without
pressing a key, this is what I get in the registry…
HKEY_LOCAL_MACHINE/HARDWARE/DESCRIPTION/System/MultifunctionAdapter/5/KeyboardController/0/KeyboardPeripheral/0/Identifier
= UNKNOWN_KEYBOARD.
In this case, the PS/2 keyboard does NOT work because the i8042prt.sys
driver doesn’t get loaded.
If I press a key on the PS/2 keyboard during the OS selection screen, this
is what I get in the registry…
HKEY_LOCAL_MACHINE/HARDWARE/DESCRIPTION/System/MultifunctionAdapter/5/KeyboardController/0/KeyboardPeripheral/0/Identifier
= PCAT_ENHANCED.
In this case, the PS/2 keyboard DOES work.
It seems that one of our keyboard controllers/keyboards is getting into a
weird state (which goes away when I press key). What is Windows 2000
looking for? It can’t be the PNP0xxx value, because the BIOS is returning
PNP0303 whether or not I press a key. I checked this using a PNP status
utility. Does Windows 2000 run some kind of test or look for some keyboard
controller status bits to determine if a keyboard is out there?
Thanks.
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com