xmodmap -e “keycode 234 = Super_L”
xmodmap -e “keycode 233 = Super_R”

Userland method (of course you’re using GNOME and FC6):

First method:

Create in $HOME a .Xmodmap file. It must be as such:

! Xmodmap for IBM Thinkpad T30:
! map browser keys to Super (Windows) and Hyper keys
keycode 233 = Hyper_R keycode 234 = Super_L

This file will be automatically read at the next session login (a small dialog box appears for this)

Second method: add some lines or create in $HOME a .Xsession file. It must be an executable file (chmod +x .Xsession) as such:

#!/bin/sh xmodmap -e
“keycode 233 = Hyper_R”
xmodmap -e “keycode 234 = Super_L”

Rootland mode: as root edit the /etc/X11/Xmodmap file and add the following lines at the end of this file :

! Xmodmap for IBM Thinkpad T30:
! map browser keys to Super (Windows) and Hyper key
keycode 233 = Hyper_R keycode 234 = Super_L

restart X, that’s it !

Modes:

Continuous maximum frequency

sudo cpfreq-selector -g performance

Increases the CPU frequency slowly if needed, and then decreases quickly.

sudo cpfreq-selector -g conservative

Increases and decreases the CPU frequency quickly, on-demand

sudo cpfreq-selector -g ondemand

Powersave sais it all

sudo cpfreq-selector -g powersave

I do not recall how the following operates

sudo cpfreq-selector -g userspace

It is also possible to set particular frequencies manually with multipliers such as 10000 or 12000 but I do not think this is necessary given the options above, not to mention far less intrusive.

Changing the permissions of the cpufreq-selector binary by doing a:

$sudo chmod +s /usr/bin/cpufreq-selector

will allow me to left mouse click on the ‘Frequency Monitor’ and select a mode and speed from a drop-down menu. Very convenient.

However, you can set the suid of the cpufreq-selector executable by running the following in the terminal and confirming upon prompt.

$ sudo dpkg-reconfigure gnome-applets

I will not recommend this as It caused me problems with my own setup. In short, my CPU frequency got stuck on 800Mhz (46%). I recommend using the safer ‘Modes’ posted at the start of this post to control how you wish to use your CPU.

Here’s a solution I have come accross:

Open your terminal and enter the following (ensuring you re-enter the single speech marks (’) as the terminal has a special need where this is concerned):

xmodmap -e ‘keycode 22 = Backspace Backspace Terminate_Server’

You may find that this is not a permanent fix and that the next time you start your machine the problem only returns, meaning you will have to make the ‘Shift + Backspace restart‘ fix again. To overcome this, I simply run the command during startup by following the following steps:

Navigate to System > Preferences > Sessions and click the Startup Programs tab.

Click Add and enter:

xmodmap -e ‘keycode 22 = Backspace Backspace Terminate_Server’