SDB:Nonfunctioning Keyboard Key After Installation

From openSUSE


Version: 8.2

Contents

Symptom

The key with the characters "<, >, | " no longer works after the installation of SuSE Linux 8.2.

Cause

Due to an incorrectly-set keyboard type for 104 keys, this key has no function.

Solution

There are several approaches for solving this problem:

1. With YaST2 Control Center

Start YaST2 Control Center and select the menu items:

  • Hardware
  • Graphics card and monitor
  • Change...
  • Input devices
  • Keyboard
  • Change Configuration
  • Set the keyboard type to "Standard Keyboard [pc105]" in the drop-down menu.

Now select "Ready", "Finish", "Save", and "Accept". To activate the new settings, the current user must log in and out of the system to reload the X server configuration file.

2. From a Text Console with SaX2

You are logged in as root in a text console (if this is not the case, log in as root with "su"). Make sure the system is in runlevel 3 by executing the command "init 3" in the console. Once the system has confirmed that you are in runlevel 3, enter "sax2".

Select the following menu items:

  • Change configuration
  • Input Devices
  • Keyboard
  • Change configuration
  • Set the keyboard type to "Standard Keyboard [pc105]" in the drop-down menu

Then select "Finish", "Finalize", and "Save". Finally, enter "init 5" in the console. The X server or KDM will now start and the previously-missing key will be now operative.

3. From a Text Console with an Editor

You are logged in as root in a text console (if this is not the case, log in as root with "su"). Make sure you are in runlevel 3 by executing the command "init 3" in the console. Once the system has confirmed that you are in runlevel 3, open the file /etc/X11/XF86Config with an editor of your choice, for example, pico /etc/X11/XF86Config.

Search for Section "InputDevice" and change the line

	Option       "XkbModel" "pc104"

to

Option "XkbModel" "pc105"

Save the changes and quit.

After entering "init 5", the X server will start and the previously-missing key should now work properly.