Size: 7620
Comment:
|
Size: 7775
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 22: | Line 22: |
In order to go on with this "tutorial" you have to satisfy to some prerequisites. | In order to go on with this "tutorial" you have to satisfy to some prerequisites.[[BR]] |
Line 24: | Line 24: |
a. to be able to access the PC through a PS/2 keyboard; b. to know how to access to the BIOS; c. to search two BIOS options, "USB keyboard support", "PnP managed by OS" or options labeled in some similar way. |
. to be able to access the PC through a PS/2 keyboard;[[BR]] . to know how to access to the BIOS;[[BR]] . to search two BIOS options, "USB keyboard support" or "USB legacy support", "PnP managed by OS" or options labeled in some similar way.[[BR]] |
Line 31: | Line 31: |
To have no interference and to simplify the operations, please, preventively detach any other USB device from the computer. This will also avoid them to be stressed by the probably required repetitive reboot activities. | To have no interference and to simplify operations, please, preventively detach any other USB device from the computer. This will also avoid them to be stressed by the probably required repetitive reboot activities. |
Line 35: | Line 35: |
Hardware issues are often the cause of USB keyboards as other devices' malfunction, so let we check the state of the art. | Hardware issues are often the cause of USB keyboards as other USB devices' malfunction, so let we check the state of the art. |
Line 38: | Line 38: |
This because some USB-HUBs are only partially compatible to the USB standard, so they may interfere with normal messaging between the system and the attached USB devices inducing you, in some cases, to think your USB keyboard is stuck. | This because some low-end USB-HUBs are only partially compatible to the USB standards, so they may interfere with normal messaging between the system and the various attached USB devices wrongly inducing you, in some cases, to think your USB keyboard is stuck. |
Line 42: | Line 42: |
If your USB now works take in account to seriously suspect your USB HUB or another USB device is creating the problem. Check them singularly and place the culprit directly in the trash as it may seriously damage further USB devices if not your PC's USB ports. | If your USB now works, take in account to seriously suspect your USB HUB or another USB device is creating the problem. Check them singularly and place the culprit directly into the trash as it may seriously damage other USB devices if not your PC's USB ports. |
Line 48: | Line 48: |
(Situation 1.) During the POST (Power On Self Test), when the PC is running up for a power-on or a reset, the USB keyboard input is managed by the BIOS routines if it is set up to do so. | (Situation 1.) During the POST (Power On Self Test), when the PC is running up for a power-on or a reset, the USB keyboard input is managed by the BIOS routines, if set up to do so. |
Line 50: | Line 50: |
If not, there is no way the USB keyboard can be recognised and a PS/2 type keyboard is expected connected to its port by default instead. | If not, there is no way the USB keyboard can be recognised and a PS/2 type keyboard is expected to be connected to its port by default instead. |
Line 52: | Line 52: |
As long as your USB keyboard isn't recognised, you aren't able to access the BIOS so you can't do anything else as to connect a PS/2 type keyboard, access the BIOS | As long as your USB keyboard isn't recognised, you aren't able to access the BIOS so you can't do anything else as to connect a PS/2 type keyboard, access the BIOS... |
Line 57: | Line 57: |
by the use of [Del], [F1], [F2], [F9] or whatever key is indicated at the early stages of the start-up process of the PC, | ...by the use of [Del], [F1], [F2], [F9] or whatever key is indicated at the early stages of the start-up process of the PC, |
Line 65: | Line 65: |
and enable the "USB keyboard support" option that can be found in the BIOS. | and enable the "USB keyboard support" or "USB legacy support" option that can be found in the BIOS. |
Line 113: | Line 113: |
. incorrect o.s. setup files for character mode terminal emulation (e.g. the recovery mode in [x]ubuntu); . incorrect Xserver setup files for graphic windowing environment (when the windowing mode is run); . missing, wrong, bugged device drivers; . unsupported USB devices. |
. incorrect o.s. setup files for character mode terminal emulation (e.g. the recovery mode in *ubuntu);[[BR]] . incorrect window server setup files for graphic windowing environment (when the windowing mode is run, e.g. Xwindow in Linux)[[BR]] . missing, wrong, bugged keyboard device drivers;[[BR]] . unsupported USB devices.[[BR]] |
Line 122: | Line 119: |
As stated before this case isn't covered in this how-to. This because the verifications/operations to be made to get the USB keyboard working are so many and depending from e.g. the window manager used, to justify separate how-to documents. | As stated before this case isn't covered in this document. This because the verifications/operations to be made to get the USB keyboard working are so many and depending from e.g. the window manager used, to justify separate documentation. |
ContentsBRTableOfContents |
Introduction
Recurrent posts in the community forums cover problems connected with the installation of USB keyboards. This document shows a simple step-by-step procedure to gain access to this kind of USB devices.
Please notice that this help document covers problems appearing up to, and not included, the operating system's (from now "o.s.") log-in phase. Further explanations regarding USB keyboards problems during and after the log-in phase are strictly related to configuration issues of o.s. installation thus out of the scope to this document.
What we try here, is to ensure that once connected a USB keyboard to a USB port, you are enabled to use it to access the BIOS setup and the bootloader's menu' (be it Grub, LiLo or whatever...) to select and start the required operating system.
Background information
We have to distinguish three specific and chronologically ordered situations where a USB keyboard is used:
- to enter and optimise the BIOS setup;
to select the operating system to boot, by the use of the boot manager (e.g. Grub, LiLo...);
- during and after o.s.' log-in (both in the character terminal as in graphic windowing mode).
Coherently with what we have stated before, only the first two options are covered on this document, therefore some rough indications are given at the end of this document to address the right destination for your further actions.
Prerequisites
In order to go on with this "tutorial" you have to satisfy to some prerequisites.BR It is required:
to be able to access the PC through a PS/2 keyboard;BR
to know how to access to the BIOS;BR
to search two BIOS options, "USB keyboard support" or "USB legacy support", "PnP managed by OS" or options labeled in some similar way.BR
Preparation
Any connection/disconnection of USB devices during the procedures described in this document, has to be made with the PC powered OFF.
To have no interference and to simplify operations, please, preventively detach any other USB device from the computer. This will also avoid them to be stressed by the probably required repetitive reboot activities.
Hardware checkset
Hardware issues are often the cause of USB keyboards as other USB devices' malfunction, so let we check the state of the art.
If you are using an external USB-HUB it is recommended to disconnect it and plug the USB keyboard directly to one of the PC's USB ports.BR This because some low-end USB-HUBs are only partially compatible to the USB standards, so they may interfere with normal messaging between the system and the various attached USB devices wrongly inducing you, in some cases, to think your USB keyboard is stuck. BR Additionally USB-HUBs are the devices at most failure risk due to rough handling, low hardware quality or environmental injuries. So a check will help you avoiding the first problem source you may meet during this ongoing procedure.
If your USB now works, take in account to seriously suspect your USB HUB or another USB device is creating the problem. Check them singularly and place the culprit directly into the trash as it may seriously damage other USB devices if not your PC's USB ports.
If this doesn't help, go on reading the following steps. Don't forget to reset the PC to check any modification made!
Software checkset
(Situation 1.) During the POST (Power On Self Test), when the PC is running up for a power-on or a reset, the USB keyboard input is managed by the BIOS routines, if set up to do so. BR If not, there is no way the USB keyboard can be recognised and a PS/2 type keyboard is expected to be connected to its port by default instead.
As long as your USB keyboard isn't recognised, you aren't able to access the BIOS so you can't do anything else as to connect a PS/2 type keyboard, access the BIOS...
BR attachment:USB-KBRDInstall-POST01.jpg
...by the use of [Del], [F1], [F2], [F9] or whatever key is indicated at the early stages of the start-up process of the PC,
attachment:USBKBRDInstall-BIOS-USBKBDON.jpg
and enable the "USB keyboard support" or "USB legacy support" option that can be found in the BIOS.
BR Save, exit and reset. If, in spite of the precedent set-up, the BIOS continues refusing to recognise the USB keyboard (e.g. you can't go into the BIOS by pressing the correct key on the USB keyboard) you have a second chance to convince it to.
Use the PS/2 keyboard to enter the BIOS again,
attachment:USBKBRDInstall-BIOS-PnPBIOSon.jpg
and look at the "PnP mode" option. PnP is the procedure to set-up extension cards and some on-board' chips connected to the PCI bus. As USB controllers in your computer (both on-board as the eventually added expansion cards) are connected to the PCI bus, they have to be set-up by the BIOS to have the USB keyboard working at the early POST phase.
There are two configuration modes available for PnP:
. the BIOS has to manage the PnP setup; BR . the operating system deals with the PnP setup.
You have to explicitly specify the BIOS has to manage the PnP mode (and not the operating system), to obtain the USB keyboard recognised during this phase.
Verify this and, on change, save, exit the BIOS and reset the PC to control if the USB keyboard is now alive.
BRBR (Situation 2.) You can access the BIOS with your USB keyboard but when Grub's menu' appears on the screen either pressing [Arrow-up] or [Arrow-down] you aren't able to move the selection to one different from the default one.
This means you haven't correctly tested the case 1.!
It must be clear that Grub doesn't manage to load any keyboard device-driver so it expects the BIOS to manage the keyboard correctly.
During this stage Linux hasn't been already loaded so any change to the o.s. will not solve the problem!
You have no choice, go back to Case 1., and work to solve the situation from there.
BRBR (Situation 3.) So you have managed to get the USB keyboard recognised by the BIOS, and in Grub (or LiLo) you are able to select a choice different from the default by the use of the up/down arrows keys.
After a not so long time (we hope), the log-in screen appears but you discover to be unable to write any character into the user/password fields, or if you started from a live CD-R/DVD and you aren't able to write with your keyboard to any application you run from the desktop.
From this point on, problems related to the USB keyboard have to be conducted, in some way, to the Linux operating system configuration issues (and in rare cases to bugs).
In this case, the principal sources of the problem to be searched in are:
incorrect o.s. setup files for character mode terminal emulation (e.g. the recovery mode in *ubuntu);BR
incorrect window server setup files for graphic windowing environment (when the windowing mode is run, e.g. Xwindow in Linux)BR
missing, wrong, bugged keyboard device drivers;BR
unsupported USB devices.BR
As stated before this case isn't covered in this document. This because the verifications/operations to be made to get the USB keyboard working are so many and depending from e.g. the window manager used, to justify separate documentation.
Started 19-06-2008 and supervised by Andreas Troschka |
-##