|
Lines 207-213
Link Here
|
| 207 |
.Nm |
207 |
.Nm |
| 208 |
driver will attempt to reset the pointing device during the boot process. |
208 |
driver will attempt to reset the pointing device during the boot process. |
| 209 |
It sometimes takes a long while before the device will respond after |
209 |
It sometimes takes a long while before the device will respond after |
| 210 |
reset. |
210 |
reset. The driver will wait KBD_RESETDELAY msec for the aux device attached to the keyboard controller hosting the PS/2 port to respond per reset attempt. It will make KDB_MAXWAIT reset attempts before failing. |
|
|
211 |
The default for KBD_RESETDELAY of about 200 is enough for most direcly connected pointing devices. If you are using a device such as a KVM |
| 212 |
to share a mouse and perhaps keyboard and montior among more than one system box, or if your pointing |
| 213 |
device takes longer than the default to reset, then the driver will not load even though bootup indications indicate the ps/2 pointing device is present. In these cases putting |
| 214 |
.Pp |
| 215 |
.Cd "options KBD_RESETDELAY=401" |
| 216 |
.Pp |
| 217 |
in a custom kernel configuration has been helpful. Later versions may make this a tunable system setting to avoid the need to compile a custom kernel. |
| 211 |
These options control how long the driver should wait before |
218 |
These options control how long the driver should wait before |
| 212 |
it eventually gives up waiting. |
219 |
it eventually gives up waiting. |
| 213 |
The driver will wait |
220 |
The driver will wait |
|
Lines 740-746
Link Here
|
| 740 |
The second line shows the result of the keyboard controller's |
747 |
The second line shows the result of the keyboard controller's |
| 741 |
test on the auxiliary port interface, with zero indicating |
748 |
test on the auxiliary port interface, with zero indicating |
| 742 |
no error; note that some controllers report no error even if |
749 |
no error; note that some controllers report no error even if |
| 743 |
the port does not exist in the system, however. |
750 |
the port does not exist in the system, however. If the driver doesn't load but you think the hardware |
|
|
751 |
is working, read the information about the KBD_RESETDELAY option above. |
| 744 |
.Pp |
752 |
.Pp |
| 745 |
The third through fifth lines show the reset status of the pointing device. |
753 |
The third through fifth lines show the reset status of the pointing device. |
| 746 |
The functioning device should return the sequence of FA AA <ID>. |
754 |
The functioning device should return the sequence of FA AA <ID>. |