Difference between revisions of "Installing Ubuntu on a ThinkPad T23"

From ThinkWiki
Jump to: navigation, search
(Suspend / Resume: note that suggested fix may cause another problem...)
(Post a tip for fixing sound-after-suspend with Ubuntu on a T23.)
Line 3: Line 3:
 
Things generally work fine, with the following notes
 
Things generally work fine, with the following notes
  
=== Suspend / Resume ===
+
=== Power Management ===
  
After upgrading from Feisty, "suspending" may have problems including a blank screen upon resume, or sound upon resume. Selecting a 2.6.20 kernel instead of the 2.6.22 kernel that comes with Gutsy seems to remedy both of these, but USB-after-suspend may quit working. You can select a different default kernel to boot by editing the /boot/grub/menu.lst file. (Alt-F2 gsudo get /boot/grub/menu.lst). You'll want to update the line that says "default" and change the default number to the correspond to the entry for the 2.6.20 kernel you want to use. Remember to start counting from zero!
+
==== Sound After Suspend ====
  
After you made the change and saved the file. Run update-grub in a terminal. (Alt-F2 update-grub, with "run in terminal box" checked).
+
Sound may not work after a suspend/resume cycle. The problem may be that some volume levels have been muted. To fix that save the following into a script:
 +
 
 +
#!/bin/sh
 +
mixers="Master PCM CD"
 +
for mixer in $mixers ; do
 +
  /usr/bin/amixer -q sset $mixer mute
 +
  /usr/bin/amixer -q sset $mixer unmute
 +
done
 +
 
 +
The script should save to /etc/acpi/resume.d/70-sound-unmute.sh
 +
Make sure the file is executable
 +
 
 +
chmod +x  /etc/acpi/resume.d/70-sound-unmute.sh
 +
 
 +
Now, after a suspend/resume cycle, sound should work automatically!
  
 
=== Dual Monitors ===
 
=== Dual Monitors ===

Revision as of 05:40, 4 December 2007

Ubuntu 7.10 Gutsy Gibbon

Things generally work fine, with the following notes

Power Management

Sound After Suspend

Sound may not work after a suspend/resume cycle. The problem may be that some volume levels have been muted. To fix that save the following into a script:

#!/bin/sh
mixers="Master PCM CD"
for mixer in $mixers ; do
  /usr/bin/amixer -q sset $mixer mute
  /usr/bin/amixer -q sset $mixer unmute
done

The script should save to /etc/acpi/resume.d/70-sound-unmute.sh Make sure the file is executable

chmod +x  /etc/acpi/resume.d/70-sound-unmute.sh

Now, after a suspend/resume cycle, sound should work automatically!

Dual Monitors

Gutsy Gibbon has a new "Screens and Graphics" preferences area. It shows a second monitor possibility. Trying a test does make both the LCD and external screen active as one big gray monitor...but only for the test. Choosing the option to accept the settings does not actually cause monitor-spanning to work, but monitor mirroring does.

CPU Frequency Scaling

CPU Frequency Scaling seems to be working automatically. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

Ubuntu 7.04 Feisty Fawn

Power Management

The chips in T23s have the ability to run at speeds slower than their maximum, in order to save power. To see your current speed level, activate the CPU Frequency Scaling Monitor Applet. Right click on the toolbar and select "add to panel". You can search for "Frequency" to find it.

You can also enable this applet to allow you manually change the speed and scaling policy. To do that, run this in a terminal: "sudo dpkg-reconfigure gnome-applets".

These instructions are also available illustrated with screenshots.

You may also need to add a couple of lines to "/etc/modules" to allow you to be able to change the processor speed and governor. The lines are:

acpi-cpufreq
cpufreq_ondemand

These will now be loaded on at boot time. To activate them immediately:

 sudo modprobe acpi-cpufreq
 sudo modprobe cpufreq_ondemand

Some technical details are explained on the SpeedStep page.

External Resources