ThinkWiki - User contributions [en]

Installation instructions for the ThinkPad X61

2010-04-18T14:37:00Z

BruNo: update link to my page

== External sources ==

There are informative Ubuntu forum threads on [http://ubuntuforums.org/showthread.php?t=503233 Feisty] and [http://ubuntuforums.org/showthread.php?t=523022 Gutsy] for the X61.

A very detailed report on the X61 under Ubuntu Gutsy Gibbon is [https://wiki.ubuntu.com/LaptopTestingTeam/ThinkpadX61 here]. The report was written describing Tribe 5, the last prerelease, but describes the release version of Gutsy Gibbon equally well.

* [http://slackwiki.org/ThinkPad_X61s Slackware installation instructions]
* [http://wiki.webvm.net/x61 Debian Lenny installation notes]
* [http://br1.einfach.org/wiki/GentooX61 Installing Gentoo on a Thinkpad X61]

There is also fairly complex [[Installing openSUSE 10.3 on a ThinkPad X61|instalation HOWTO for openSUSE 10.3]] here on ThinkWiki.

* [[Installing Ubuntu 9.10 (Karmic Koala) on a ThinkPad X61]]

[http://www.example.com link title]

== Problems and solutions ==

=== X61 won't boot from the CD-ROM/DVD drive (Solved) ===

Follow these instructions to enable your [http://en.wikipedia.org/wiki/Optical_drive optical drive]:

# Reboot your X61. Press the ThinkVantage button quickly when you see the ThinkPad screen and then press F1 to enter [http://en.wikipedia.org/wiki/BIOS BIOS].
# In BIOS, select Configure -> Serial ATA.
# Now, select Compatibility instead of AHCI.
# Exit BIOS and start your computer normally.

Do this only when booting does not work. This is not always necessary!

=== Suspend/Resume doesn't work out of the box (Solved) ===

Under GNOME, you may find that Suspend/Resume doesn't work out of the box. Fn-F4 does suspend and lid open does resume, but the backlight is off after resume.

To fix this, do the following:

# In the file /boot/grub/menu.lst, find the line beginning with "# kopt=". This is where grub sets the options for your kernel. Append to this line the following: " acpi_sleep=s3_bios". (That is, these words should be preceded by a space separating them from the existing options. Do not remove the initial "#" from the line.)

# Run the command '''update-grub''' as root.

This fix '''is''' needed under Ubuntu 7.04 (Feisty Fawn), but '''is not''' needed under later versions (Gibbon, Hardy, Ibex). It seems likely the difference is due to the GNOME upgrade.

In general the the backlight problem can be solved by suspending with
s2ram -f -a 1
or using vbetool to restore your video state. for hibernate-scripts put into {{path|/etc/hibernate/ram.conf}}

TryMethod sysfs-ram.conf
EnableVbetool yes
VbetoolPost yes

Please see also [http://www.thinkwiki.org/index.php?title=Problem_with_display_remaining_black_after_resume&action=edit&section=13 this link] for adding the s2ram to your acpi scripts.

=== Sound doesn't work (Solved) ===

Sound won't work under the stock ALSA 1.0.14 shipped with Ubuntu Feisty Fawn, but will in later versions including the patched 1.0.14 shipped with Ubuntu Gutsy Gibbon.

Your speakers default to being muted. To fix this, run alsamixer in a terminal window; right-arrow over until the Speaker column is visible, and press the "m" key to toggle it from mute ("MM") to on ("OO").

You may have to go to System->Preferences->Sound->Devices and select PCM to enable your Volume button to work.

The mute button always mutes rather than toggling; you have to undo it by hitting the volume-up button.

=== Known Issues under Ubuntu Feisty Fawn 7.04 ===

# Sound doesn't work under Feisty, but '''does''' under Gutsy/Hardy/Ibex.
# Wireless doesn't work under Feisty, but '''does''' under Gutsy/Hardy. It breaks again under Ibex. No fix yet.
# 2D graphics works fine, but there is no 3D acceleration yet. (3D acceleration works in Hardy/Ibex)
# Fingerprint reader doesn't work yet.

=== Immediate Resume after Suspend ===

If your X61 starts to resume a few seconds after you suspended it to RAM, then you might need to unload the USB modules uhci_hcd and ehci_hcd before going to sleep.

For hibernate-scripts you can put this in {{path|/etc/hibernate/common.conf}}
UnloadModules uhci_hcd ehci_hcd

=== USB ports on right side don't work ===

Can be fixed with a firmware update (from Lenovo); or using [[irqfixup]].

See [http://ubuntuforums.org/showthread.php?t=658065 this thread on ubuntuforums].

=== BIOS/firmware upgrade difficult without UltraBase ===

BIOS upgrades are available from Lenovo online in the form of a bootable CD image. However, USB CD-ROM drivers are not included on the disk, such that external CD-ROM drives will not work with the BIOS upgrade. Due to the lack of internal CD-ROM drive in the X61 series of laptops, this makes upgrading the BIOS difficult without a 32-bit version of Windows (for which there is an executable BIOS upgrade program).

A CD-ROM drive in a Thinkpad UltraBase will be able to boot Lenovo's unmodified ISO and upgrade the BIOS/firmware. Failing this, it is possible to upgrade the X61 BIOS using a bootable USB stick, as per the instructions detailed [http://ubuntuforums.org/showthread.php?t=817897 here].

=== Bluetooth ===

If bluetooth is disabled, just hit Fn-F5.

=== Other (non-)problems ===

The stock drive in the X61 of October 2007 appears not to have the [[Problem_with_hard_drive_clicking|click-of-death]] issue noted on some other ThinkPads. Note, this could potentially change if Lenovo changes drive suppliers.

The X61 is apparently very similar to a T61 internally. You may be able to find helpful tips in the
installation instructions for the [[Installation_instructions_for_the_ThinkPad_T61|Installation instructions for the Thinkpad T61]] for problems that are not solved here.

== Multiple monitors ==

To clone the screen, just plug in a second monitor and hit Fn-F7.

See: [[Xorg RandR 1.2]] and [[Intel Graphics Media Accelerator X3100]] for more details on setting up two monitors.

To keep compiz effects, the largest Virtual screen size you can have currently is 2024 x 2024 (combined size of both monitors). This is apparently a software limitation, and may be extended in future. See [[Xorg RandR 1.2]] for details.

You can change screen setup settings with these GUI apps:
* <code>gnome-display-properties</code> (called "Screen Resolution" in System | Preferences menu)
* <code>grandr</code> (not installed by default. try the command line tool <code>xrandr</code> if grandr doesn't do what you want.)
* <code>gksu displayconfig-gtk</code> (Warning: displayconfig-gtk may mess with your xorg.conf in a bad way. Keep a backup and/or avoid this program!)

[[Category:X61]]

Problems with ACPI suspend-to-ram

2008-03-28T03:12:11Z

BruNo: /* Troubles on suspend */ fix my mistakes

The following glitches may or may not occur in relation to suspending to RAM:

==Troubles on suspend==
;Permissions:If your suspend is failing, and a {{cmdroot|tail /var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions.

;Write error:If {{cmdroot|echo mem > /sys/power/state}} shows "write error: Operation not permitted", verify that CONFIG_HOTPLUG_CPU option is enabled in the kernel. [[Software_Suspend_2|Suspend2]] automatically selects this option.

;Broken sysfs interface:You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} or {{cmdroot|echo mem > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running or if the usb hcd modules are still loaded.

;Immediate Resume after Suspend:If a resume starts a few seconds after suspend a reason might be the USB modules. Unload the modules uhci_hcd and ehci_hcd before you suspend. Users of hibernate-scripts add "UnloadModules uhci_hcd ehci_hcd" to {{path|/etc/hibernate/common.conf}}.

;Hangs on "switching to UP code":You may be using a [[How to make use of Dynamic Frequency Scaling|frequency scaling governor]] such as "conservative" or "ondemand", which sometimes have problems with suspending. Switching to a governor such as "powersave" or "performance" before suspending may solve this problem.

;MySQL daemon running:If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.

;LCD backlight remains on during sleep:When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.

;High power drain during sleep:Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

;Built-in MMC reader:If you have an MMC reader, and the computer hangs when attempting suspend then remove sdhci, mmc_block, and mmc_core modules before suspending.

;Could not power down device <NULL>: error -22:If you have the acpi_cpufreq kernel module loaded, this prevents suspension.

;Immediate Resume, but Suspend "moon" light continues to flash:???

;Hard system lock up:If you are using savagefb, make sure to [[Problem_with_unusable_console|disable the "Console Acceleration" option]] (CONFIG_FB_SAVAGE_ACCEL) in the kernel config. Otherwise, susped-to-RAM may lock up your system such that you must remove the AC adapter and battery to get it to boot again.

==Troubles on resume==
;Blank display on resume:
:When resuming from a suspend-to-ram the display might remain black (on {{X60}}) or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). See [[Problem with display remaining black after resume]] for solutions. See also '''System hang on resume''' on this page - which may be potentially mismatched with this one.

;No mouse cursor on resume:
:When resuming from a suspend-to-ram your X cursor might be invisible(on {{X40}}) when using {{path|/sys/power/state}} directly to suspend, they way to fix this is to rerun the post bios code after returning for suspending.
:{{cmdroot|FGCONSOLE<nowiki>=</nowiki>`fgconsole\`}}
:{{cmdroot|chvt 1 && echo -n mem >/sys/power/state}}
:{{cmdroot|vbetool post && chvt 7 && chvt $FGCONSOLE}}

;Garbage on text consoles on resume:When resuming from suspend-to-ram the text console displays may show garbage instead of actual text. The machine is otherwise still responsive and X displays fine. If all of this is true, then adding the kernel option {{bootparm|acpi_sleep|s3_bios,s3_mode}} in your menu.lst or lilo.conf may solve the problem.

;Broken hardware support after resume:
:*The '''serial port''' of the port replicator might not work after resume.
:*The '''parallel port''' might not work after resume. A possible fix is to unload and reload the parallel port drivers: {{cmdroot|rmmod lp parport_pc parport; modprobe lp}}.
:*Problems with the '''CD-RW/DVD drive''' after wake up from ram have been experienced.
:*There is a known Problem regarding '''battery info''' after suspend to RAM. A [http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/2429.html small patch] exists for kernels 2.6.14/2.6.15.
:*On {{X20}} and {{X21}} (and possibly other) models, the '''sleep LED''' is not reset properly on resume and will keep blinking. If you have the [[ibm-acpi]] kernel module loaded with the {{bootparm|ibm-acpi.experimental|1}} option, you can switch it off on resume by appending the following line to your suspend script: {{cmdroot|echo 7 off > /proc/acpi/ibm/led}}

;Crash on resume:
:*When using '''older ATI proprietary drivers''' a crash on resume can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool]. See the example suspend script [[Problem with display remaining black after resume#Solution for ThinkPads with Intel I830 Chipset]]. This is no longer necessary with recent revisions of the ATI proprietary driver.
:*A crash could also be caused by having '''apic support''' enabled in the kernel config. Try disabling it (in the "Processor type and features" section).
:*On machines with Savage chipsets, the '''savagefb framebuffer driver''' might crash the machine on resume. Make sure it is disabled in your kernel config and use the standard vesafb driver instead.
:*SATA-based laptops utilize the '''libata layer for disk access''' which does not have fully-working power-management support before Linux kernel 2.6.16 (ata_piix) and 2.6.19 (ahci). Suspend to RAM crashes these machines on resume. See the [[Problems with SATA and Linux#Hang on resume from suspend to RAM|relevant section]] on the [[Problems with SATA and Linux]] page.
:*Using [[HDAPS]] as a module causes a crash on resume with the Linux kernel 2.6.19 (possibly even earlier versions). This was observed on a {{X41}}. Try unloading the module before suspending.
:*Gnome-power-manager might be using the wrong backend. If you are able to suspend from the commandline with a certain method, make sure the others are not available so that g-p-m doesn't choose the wrong one. For example, if you suspend with {{cmdroot|echo mem > /sys/power/state}}, make sure '''uswsusp''' and '''hibernate''' are uninstalled.

;System hang on resume:
:When system resumes it hangs right after restarting tasks. Strange thing is, that you may be even able to restart your ThinkPad using {{key|ctrl}}{{key|alt}}{{key|del}}, but if you try to blindly exec a command, it will not work, (eg. touch FILE) so it's not only the problem of videocard. This may be fixed by passing {{bootparm|ec_intr|0}} on kernel cmdline. Affected models: {{T20}}, {{T21}} (at least [[2648-46U]] (T20),[[2647-8AG]] (T21)).
:'''Note:''' ''this is resolved in kernel 2.6.20, there is no need to pass the {{bootparm|ec_intr|0}} bootparam anymore (moreover, you are discouraged to use it) See [http://bugzilla.kernel.org/show_bug.cgi?id=6749 revelant kernel bug report]''
:See also [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/73546 this bug report], I can confirm some strange problems on resume with Bluetooth enabled - my T61 may freeze in a couple of minutes after resuming. This problem is gone as soon as I disable Bluetooth (stop all bluetooth related services and `echo "disable" > /proc/acpi/ibm/bluetooth`).

;Shutdown on resume:
:If your system immediately begins to shut down right after resume, make sure you don't have acpid running with the power button tied to shutdown. The system is simply sensing the power button event and shutting down. This issue has been reported as a bug against the kernel ACPI subsystem, refer to [http://bugzilla.kernel.org/show_bug.cgi?id=6612 kernel.org bugzilla bug #6612].

;Immediate suspend on resume:
:When running GNOME, sometimes gnome-power-manager will put the system back into suspend immediately after resuming. This is caused by a known bug in HAL that causes some ACPI events to be reported incorrectly after a suspend-to-ram. A simple workaround can be found [http://live.gnome.org/GnomePowerManager/Faq?action=recall&rev=28#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].
:Note that suspend being triggered by unrelated ACPI events such as disconnecting the AC adapter may also be fixed by the above method.

;Power Off when suspended laptop is docked
:When T60p is suspended, docking laptop into Advanced Dock immediately turns off laptop and crescent moon sleep indicator LED. Pressing power button initiates cold boot. Also reported by multiple people on thinkpads.com.

;SectorIdNotFound disk errors when laptop is resumed
:The errors look like this:
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=115896900, sector=115896900
Oct 14 17:35:02 cacharro kernel: ide: failed opcode was: unknown

:This happens when you have [[Hidden Protected Area]] (HPA) enabled on the hard drive. There is a [http://bugzilla.kernel.org/show_bug.cgi?id=6840 kernel bug report with an unfinished patch] to fix this. This is not fixed as of kernel 2.16.18.

Problems with ACPI suspend-to-ram

2008-03-28T03:09:30Z

BruNo: /* Troubles on suspend */ add immediate resume after suspend section with info about USB modules

The following glitches may or may not occur in relation to suspending to RAM:

==Troubles on suspend==
;Permissions:If your suspend is failing, and a {{cmdroot|tail /var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions.

;Write error:If {{cmdroot|echo mem > /sys/power/state}} shows "write error: Operation not permitted", verify that CONFIG_HOTPLUG_CPU option is enabled in the kernel. [[Software_Suspend_2|Suspend2]] automatically selects this option.

;Broken sysfs interface:You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} or {{cmdroot|echo mem > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running or if the usb hcd modules are still loaded.

;Immediate Resume after Suspend:If a resume starts a few seconds after suspend a reason might be the USB modules. Unload the modules {{uhci_hcd}} and {{ehci_hcd}} before you suspend. Users of hibernate-scripts add {{UnloadModules uhci_hcd ehci_hcd}} to {{path|/etc/hibernate/common.conf}}.

;Hangs on "switching to UP code":You may be using a [[How to make use of Dynamic Frequency Scaling|frequency scaling governor]] such as "conservative" or "ondemand", which sometimes have problems with suspending. Switching to a governor such as "powersave" or "performance" before suspending may solve this problem.

;MySQL daemon running:If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.

;LCD backlight remains on during sleep:When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.

;High power drain during sleep:Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

;Built-in MMC reader:If you have an MMC reader, and the computer hangs when attempting suspend then remove sdhci, mmc_block, and mmc_core modules before suspending.

;Could not power down device <NULL>: error -22:If you have the acpi_cpufreq kernel module loaded, this prevents suspension.

;Immediate Resume, but Suspend "moon" light continues to flash:???

;Hard system lock up:If you are using savagefb, make sure to [[Problem_with_unusable_console|disable the "Console Acceleration" option]] (CONFIG_FB_SAVAGE_ACCEL) in the kernel config. Otherwise, susped-to-RAM may lock up your system such that you must remove the AC adapter and battery to get it to boot again.

==Troubles on resume==
;Blank display on resume:
:When resuming from a suspend-to-ram the display might remain black (on {{X60}}) or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). See [[Problem with display remaining black after resume]] for solutions. See also '''System hang on resume''' on this page - which may be potentially mismatched with this one.

;No mouse cursor on resume:
:When resuming from a suspend-to-ram your X cursor might be invisible(on {{X40}}) when using {{path|/sys/power/state}} directly to suspend, they way to fix this is to rerun the post bios code after returning for suspending.
:{{cmdroot|FGCONSOLE<nowiki>=</nowiki>`fgconsole\`}}
:{{cmdroot|chvt 1 && echo -n mem >/sys/power/state}}
:{{cmdroot|vbetool post && chvt 7 && chvt $FGCONSOLE}}

;Garbage on text consoles on resume:When resuming from suspend-to-ram the text console displays may show garbage instead of actual text. The machine is otherwise still responsive and X displays fine. If all of this is true, then adding the kernel option {{bootparm|acpi_sleep|s3_bios,s3_mode}} in your menu.lst or lilo.conf may solve the problem.

;Broken hardware support after resume:
:*The '''serial port''' of the port replicator might not work after resume.
:*The '''parallel port''' might not work after resume. A possible fix is to unload and reload the parallel port drivers: {{cmdroot|rmmod lp parport_pc parport; modprobe lp}}.
:*Problems with the '''CD-RW/DVD drive''' after wake up from ram have been experienced.
:*There is a known Problem regarding '''battery info''' after suspend to RAM. A [http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/2429.html small patch] exists for kernels 2.6.14/2.6.15.
:*On {{X20}} and {{X21}} (and possibly other) models, the '''sleep LED''' is not reset properly on resume and will keep blinking. If you have the [[ibm-acpi]] kernel module loaded with the {{bootparm|ibm-acpi.experimental|1}} option, you can switch it off on resume by appending the following line to your suspend script: {{cmdroot|echo 7 off > /proc/acpi/ibm/led}}

;Crash on resume:
:*When using '''older ATI proprietary drivers''' a crash on resume can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool]. See the example suspend script [[Problem with display remaining black after resume#Solution for ThinkPads with Intel I830 Chipset]]. This is no longer necessary with recent revisions of the ATI proprietary driver.
:*A crash could also be caused by having '''apic support''' enabled in the kernel config. Try disabling it (in the "Processor type and features" section).
:*On machines with Savage chipsets, the '''savagefb framebuffer driver''' might crash the machine on resume. Make sure it is disabled in your kernel config and use the standard vesafb driver instead.
:*SATA-based laptops utilize the '''libata layer for disk access''' which does not have fully-working power-management support before Linux kernel 2.6.16 (ata_piix) and 2.6.19 (ahci). Suspend to RAM crashes these machines on resume. See the [[Problems with SATA and Linux#Hang on resume from suspend to RAM|relevant section]] on the [[Problems with SATA and Linux]] page.
:*Using [[HDAPS]] as a module causes a crash on resume with the Linux kernel 2.6.19 (possibly even earlier versions). This was observed on a {{X41}}. Try unloading the module before suspending.
:*Gnome-power-manager might be using the wrong backend. If you are able to suspend from the commandline with a certain method, make sure the others are not available so that g-p-m doesn't choose the wrong one. For example, if you suspend with {{cmdroot|echo mem > /sys/power/state}}, make sure '''uswsusp''' and '''hibernate''' are uninstalled.

;System hang on resume:
:When system resumes it hangs right after restarting tasks. Strange thing is, that you may be even able to restart your ThinkPad using {{key|ctrl}}{{key|alt}}{{key|del}}, but if you try to blindly exec a command, it will not work, (eg. touch FILE) so it's not only the problem of videocard. This may be fixed by passing {{bootparm|ec_intr|0}} on kernel cmdline. Affected models: {{T20}}, {{T21}} (at least [[2648-46U]] (T20),[[2647-8AG]] (T21)).
:'''Note:''' ''this is resolved in kernel 2.6.20, there is no need to pass the {{bootparm|ec_intr|0}} bootparam anymore (moreover, you are discouraged to use it) See [http://bugzilla.kernel.org/show_bug.cgi?id=6749 revelant kernel bug report]''
:See also [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/73546 this bug report], I can confirm some strange problems on resume with Bluetooth enabled - my T61 may freeze in a couple of minutes after resuming. This problem is gone as soon as I disable Bluetooth (stop all bluetooth related services and `echo "disable" > /proc/acpi/ibm/bluetooth`).

;Shutdown on resume:
:If your system immediately begins to shut down right after resume, make sure you don't have acpid running with the power button tied to shutdown. The system is simply sensing the power button event and shutting down. This issue has been reported as a bug against the kernel ACPI subsystem, refer to [http://bugzilla.kernel.org/show_bug.cgi?id=6612 kernel.org bugzilla bug #6612].

;Immediate suspend on resume:
:When running GNOME, sometimes gnome-power-manager will put the system back into suspend immediately after resuming. This is caused by a known bug in HAL that causes some ACPI events to be reported incorrectly after a suspend-to-ram. A simple workaround can be found [http://live.gnome.org/GnomePowerManager/Faq?action=recall&rev=28#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].
:Note that suspend being triggered by unrelated ACPI events such as disconnecting the AC adapter may also be fixed by the above method.

;Power Off when suspended laptop is docked
:When T60p is suspended, docking laptop into Advanced Dock immediately turns off laptop and crescent moon sleep indicator LED. Pressing power button initiates cold boot. Also reported by multiple people on thinkpads.com.

;SectorIdNotFound disk errors when laptop is resumed
:The errors look like this:
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=115896900, sector=115896900
Oct 14 17:35:02 cacharro kernel: ide: failed opcode was: unknown

:This happens when you have [[Hidden Protected Area]] (HPA) enabled on the hard drive. There is a [http://bugzilla.kernel.org/show_bug.cgi?id=6840 kernel bug report with an unfinished patch] to fix this. This is not fixed as of kernel 2.16.18.

Installation instructions for the ThinkPad X61

2008-03-28T03:02:32Z

BruNo: /* Problems and Solutions */ Solution for immediate resume

== External Sources ==

There are informative Ubuntu forum threads on [http://ubuntuforums.org/showthread.php?t=503233 Feisty] and [http://ubuntuforums.org/showthread.php?t=523022 Gutsy] for the X61.

A very detailed report on the X61 under Ubuntu Gutsy Gibbon is [https://wiki.ubuntu.com/LaptopTestingTeam/ThinkpadX61 here]. The report was written describing Tribe 5, the last prerelease, but describes the release version of Gutsy Gibbon equally well.

* [http://slackwiki.org/ThinkPad_X61s Slackware installation instructions]
* [http://wiki.webvm.net/x61 Debian Lenny installation notes]
* [http://br1.einfach.org/GentooX61 Installing Gentoo on a Thinkpad X61]

== Problems and Solutions ==

=== X61 won't boot from the CD-ROM/DVD drive (Solved) ===

Follow these instructions to enable your [http://en.wikipedia.org/wiki/Optical_drive optical drive]:

# Reboot your X61. Press the ThinkVantage button quickly when you see the ThinkPad screen and then press F1 to enter [http://en.wikipedia.org/wiki/BIOS BIOS].
# In BIOS, select Configure -> Serial ATA.
# Now, select Compatibility instead of AHCI.
# Exit BIOS and start your computer normally.

Do this only when booting does not work. This is not always necessary!

=== Suspend/Resume doesn't work out of the box (Solved) ===

Under GNOME, you may find that Suspend/Resume doesn't work out of the box. Fn-F4 does suspend and lid open does resume, but the backlight is off after resume.

To fix this, do the following:

# In the file /boot/grub/menu.lst, find the line beginning with "# kopt=". This is where grub sets the options for your kernel. Append to this line the following: " acpi_sleep=s3_bios". (That is, these words should be preceded by a space separating them from the existing options. Do not remove the initial "#" from the line.)

# Run the command '''update-grub''' as root.

This fix '''is''' needed under Ubuntu 7.04 (Feisty Fawn), but '''is not''' needed under Gutsy Gibbon Tribe 5 or the final release version. It seems likely the difference is due to the GNOME upgrade.

In general the the backlight problem can be solved by suspending with
s2ram -f -a 1
or using vbetool to restore your video state. for hibernate-scripts put into {{path|/etc/hibernate/ram.conf}}

TryMethod sysfs-ram.conf
EnableVbetool yes
VbetoolPost yes

=== Sound doesn't work (Solved) ===

Sound won't work under the stock ALSA 1.0.14 shipped with Ubuntu Feisty Fawn, but will in later versions including the patched 1.0.14 shipped with Ubuntu Gutsy Gibbon.

Your speakers default to being muted. To fix this, run alsamixer in a terminal window; right-arrow over until the Speaker column is visible, and press the "m" key to toggle it from mute ("MM") to on ("OO").

You may have to go to System->Preferences->Sound->Devices and select PCM to enable your Volume button to work.

The mute button always mutes rather than toggling; you have to undo it by hitting the volume-up button.

=== Known Issues under Ubuntu Feisty Fawn 7.04 and Gutsy Gibbon Beta (Tribe 5) ===

# Sound doesn't work under Feisty, but '''does''' under Gutsy Tribe 5 and Gutsy Final.
# Wireless doesn't work under Feisty, but '''does''' under Gutsy Tribe 5 and Gutsy Final.
# 2D graphics works fine, but there is no 3D acceleration yet.
# Fingerprint reader doesn't work yet.

=== Other Notes ===

The stock drive in the X61 of October 2007 appears not to have the [[Problem_with_hard_drive_clicking|click-of-death]] issue noted on some other ThinkPads. Note, this could potentially change if Lenovo changes drive suppliers.

The X61 is apparently very similar to a T61 internally. You may be able to find helpful tips in the
installation instructions for the [[Installation_instructions_for_the_ThinkPad_T61|Installation instructions for the Thinkpad T61]] for problems that are not solved here.

=== Immediate Resume after Suspend ===

If your X61 starts to resume a few seconds after you suspended it to RAM, then you might need to unload the USB modules uhci_hcd and ehci_hcd before going to sleep.

For hibernate-scripts you can put this in {{path|/etc/hibernate/common.conf}}
UnloadModules uhci_hcd ehci_hcd

[[Category:X61]]

Installation instructions for the ThinkPad X61

2008-03-28T02:59:39Z

BruNo: /* Suspend/Resume doesn't work out of the box (Solved) */

Problem with display remaining black after resume

2008-03-22T09:16:54Z

BruNo: /* Affected Models */

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T60p}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}, {{R60}}, {{R61}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}, {{Z60m}}, {{Z61m}}, {{Z61e}}
*ThinkPad {{X60s}}, {{X60}}, {{X61}}, {{X61s}}

==Affected Operating Systems==
*Linux (it's a kernel issue)
*FreeBSD (6.x at least)

==Solutions==
===Quick workaround for R61i, T23, maybe others===
Try pressing CTRL+ALT+F1 to switch to text console. The backlight should come on normally. Press CTRL+ALT+F7 to return to X.

On a T23 using Ubuntu Feisty, pressing Fn+F7 (external/internal display change) once or twice brought the display back. After upgrading to Ubuntu Gutsy it doesn't work anymore, but pressing Fn+F3 (blank screen) and Fn (restore display) works.

===Quick Workaround for R61 (at least 8918-5QG) using NVidia===

Use Vesa driver instead of the proprietary NVidia driver.

=== Solution for ThinkPad Z60t ===

* '''Display controller:''' Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
* '''Distro:''' Fedora release 7 (Moonshine)
* '''Kernel:''' Linux 2.6.22.5-76.fc7

The solution is straight forward - just to add configuration parameter for the default '''pm-utils''' package. Create file <code>/etc/pm/config.d/config</code> and put there one line <code>DISPLAY_QUIRK_S3_BIOS="true"</code>, or execute following command:

echo DISPLAY_QUIRK_S3_BIOS=\"true\" >> /etc/pm/config.d/config

===Semi-Solution for ThinkPad X60 with damaged system after s2ram usage===
It happend when restarting a s2ram-session.

'''Symptom:''' Black screen with blinking "_" sign remaind. (without the ")

'''System status:''' HDD idle, fan running, everything else looks to wait for something to happen.

'''Semi-Solution:''' Booting with DVD-ROM and going through the installations menu,
where you choose "other" and "boot a installed system" (something like that). Gladly it works,
and OpenSuSE 10.1 comes up with 50% "failed" messages! I than shutdown properly, rebooted again
and had 100% "done" again, with no other things affected.

'''Further:''' Repairing with the DVD-ROM crashed massivly(!), so I selected "boot a installed system" as final
solution and it worked!

'''Unknown:''' Maybe the Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM will help,
because X60s and X60 are very familiar. (Not tested so far.)

(If this Problem is not right here, please edit and move.)

===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===
see [[1400x1050 on Intel 915GM]].
===Solution for ThinkPads with ATI graphic chips and Intel 915/945GM ===

Affected models include {{X60s}}, {{R60}} and {{T60}}.

This soluton also applies to T42 with Intel 855 and ATI 9600 M10.

One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this would look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it would look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In [[:Category:OpenSUSE|OpenSUSE]] 10.1 (at least on a T43p), it's necessary to override the default options for s2ram if you're using the newer ATI driver. This can be done putting {{bootparm|SUSPEND2RAM_FORCE|"yes"}} and {{bootparm|SUSPEND2RAM_ACPI_SLEEP|"3"}} in {{path|/etc/powersave/sleep}}.

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves. Also commenting POST_VIDEO may help.

In {{Fedora}}, it may be necessary with the Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}} to comment out the VBE post and restore. (As of FC6 these seem to be pre-commented out.) Also, the laptop, after waking up, may go back to sleep immediately or whenever the AC adapter is disconnected. When this happens, it's caused by a bug in the HAL daemon that incorrectly reports certain ACPI events. This is a known problem and a simple workaround is described [http://live.gnome.org/GnomePowerManager/Faq#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].

{{NOTE|It is possible this method will not work if the laptop is docked. It is also possible that the cited workaround for the HAL daemon bug will not work on some machines. A kludgier workaround in this event is to kill the HAL daemon on suspend. This necessitates the resuscitation of GPM upon resume.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

----

On '''T60 2007-CTO''' (Core2Duo 2Ghz, 2GB Ram, ATI X1400) the screen stayed blank after suspend-to-ram until I set '''vga=0''' in lilo.conf.

Working config:
Linux 2.6.21.5
fglrx 8.37.6
debian etch:
powersaved 0.14.0-5:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core"
hibernate:
SwitchToTextMode yes
lilo.conf:
vga=0

"EnableVbetool yes" and other suggestions didn't work for me.

For suspend-to-disk, don't load fglrx in initrd.

----

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
*For Debian Etch 4.0 on R50e just make following changes to /etc/default/acpi-support:
#SAVE_VBE_STATE=true
#VBESTATE=/var/lib/acpi-support/vbestate
#POST_VIDEO=true
SAVE_VIDEO_PCI_STATE=true

*For a R50e the only thing needed to make suspend to ram work in Ubuntu 6.06 is adding
Option "VBERestore" "yes"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}, and the example script below.

The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

With Ubuntu 6.10 on a [[:Category:R51|R51 (2887-32G)]] I ''just'' (as none of the other tricks above) had to add {{bootparm|fb|false}} to the kernel line in {{path|/etc/grub/menu.lst}} and edit {{path|/etc/defaults/acpi-support}} this way:

SAVE_VBE_STATE=false
POST_VIDEO=false
SAVE_VIDEO_PCI_STATE=true
USE_DPMS=false
DOUBLE_CONSOLE_SWITCH=false

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi
===Solution for ThinkPads with ATI graphic (and possibly other) chips and FreeBSD===

The FreeBSD acpi(4) manpage mentions a tunable parameter, "hw.acpi.reset_video":

hw.acpi.reset_video
Reset the video adapter from real mode during the resume path.
Some systems need this help, others have display problems if it
is enabled. Default is 0 (disabled).

This tunable can be set by adding the following line to your FreeBSD machine's /boot/loader.conf file:

hw.acpi.reset_video="1"

And rebooting your machine. Hopefully, the next time you resume from a suspend, you'll see your video again. This solution doesn't appear to be specific to ATI hardware in any way, so I presume it would be helpful for video chipsets other than ATI, as well.

If this entry doesn't help you, you might consider searching in the [http://lists.freebsd.org/pipermail/freebsd-mobile/ FreeBSD-Mobile email-list archive] for more insight.

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

===Solution using s2ram for Intel 915/945GM===

Just using the "s2ram -f -p" command from the uswsusp package will work from within X, at least on a {{Z61e}}. On {{X60s}} it is enough to issue the "s2ram" command and it works. On {{X61}} "s2ram -f -a 1" can work properly

===Solution using DOUBLE_CONSOLE_SWITCH===

By setting the following in {{path|/etc/default/acpi-support}} the display comes back on {{X61s}} using Intel chipset:

DOUBLE_CONSOLE_SWITCH=true

Fedora 8 doesn't have DOUBLE_CONSOLE_SWITCH, but it works when one does: First, add option "VBERestore" "true" to /etc/X11/xorg.conf

Section "Device"
Identifier "Videocard0"
Driver "intel"
Option "VBERestore" "true"
EndSection

Then suspends with

pm-suspend --quirk-vbemode-restore --quirk-s3-bios

Problem with display remaining black after resume

2008-03-22T09:16:38Z

BruNo: /* Affected Models */ add X61

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T60p}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}, {{R60}}, {{R61}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}, {{Z60m}}, {{Z61m}}, {{Z61e}}
*ThinkPad {{X60s}}, {{X60}}, {{X61}}. {{X61s}}

==Affected Operating Systems==
*Linux (it's a kernel issue)
*FreeBSD (6.x at least)

==Solutions==
===Quick workaround for R61i, T23, maybe others===
Try pressing CTRL+ALT+F1 to switch to text console. The backlight should come on normally. Press CTRL+ALT+F7 to return to X.

On a T23 using Ubuntu Feisty, pressing Fn+F7 (external/internal display change) once or twice brought the display back. After upgrading to Ubuntu Gutsy it doesn't work anymore, but pressing Fn+F3 (blank screen) and Fn (restore display) works.

===Quick Workaround for R61 (at least 8918-5QG) using NVidia===

Use Vesa driver instead of the proprietary NVidia driver.

=== Solution for ThinkPad Z60t ===

* '''Display controller:''' Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
* '''Distro:''' Fedora release 7 (Moonshine)
* '''Kernel:''' Linux 2.6.22.5-76.fc7

The solution is straight forward - just to add configuration parameter for the default '''pm-utils''' package. Create file <code>/etc/pm/config.d/config</code> and put there one line <code>DISPLAY_QUIRK_S3_BIOS="true"</code>, or execute following command:

echo DISPLAY_QUIRK_S3_BIOS=\"true\" >> /etc/pm/config.d/config

===Semi-Solution for ThinkPad X60 with damaged system after s2ram usage===
It happend when restarting a s2ram-session.

'''Symptom:''' Black screen with blinking "_" sign remaind. (without the ")

'''System status:''' HDD idle, fan running, everything else looks to wait for something to happen.

'''Semi-Solution:''' Booting with DVD-ROM and going through the installations menu,
where you choose "other" and "boot a installed system" (something like that). Gladly it works,
and OpenSuSE 10.1 comes up with 50% "failed" messages! I than shutdown properly, rebooted again
and had 100% "done" again, with no other things affected.

'''Further:''' Repairing with the DVD-ROM crashed massivly(!), so I selected "boot a installed system" as final
solution and it worked!

'''Unknown:''' Maybe the Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM will help,
because X60s and X60 are very familiar. (Not tested so far.)

(If this Problem is not right here, please edit and move.)

===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===
see [[1400x1050 on Intel 915GM]].
===Solution for ThinkPads with ATI graphic chips and Intel 915/945GM ===

Affected models include {{X60s}}, {{R60}} and {{T60}}.

This soluton also applies to T42 with Intel 855 and ATI 9600 M10.

One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this would look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it would look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In [[:Category:OpenSUSE|OpenSUSE]] 10.1 (at least on a T43p), it's necessary to override the default options for s2ram if you're using the newer ATI driver. This can be done putting {{bootparm|SUSPEND2RAM_FORCE|"yes"}} and {{bootparm|SUSPEND2RAM_ACPI_SLEEP|"3"}} in {{path|/etc/powersave/sleep}}.

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves. Also commenting POST_VIDEO may help.

In {{Fedora}}, it may be necessary with the Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}} to comment out the VBE post and restore. (As of FC6 these seem to be pre-commented out.) Also, the laptop, after waking up, may go back to sleep immediately or whenever the AC adapter is disconnected. When this happens, it's caused by a bug in the HAL daemon that incorrectly reports certain ACPI events. This is a known problem and a simple workaround is described [http://live.gnome.org/GnomePowerManager/Faq#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].

{{NOTE|It is possible this method will not work if the laptop is docked. It is also possible that the cited workaround for the HAL daemon bug will not work on some machines. A kludgier workaround in this event is to kill the HAL daemon on suspend. This necessitates the resuscitation of GPM upon resume.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

----

On '''T60 2007-CTO''' (Core2Duo 2Ghz, 2GB Ram, ATI X1400) the screen stayed blank after suspend-to-ram until I set '''vga=0''' in lilo.conf.

Working config:
Linux 2.6.21.5
fglrx 8.37.6
debian etch:
powersaved 0.14.0-5:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core"
hibernate:
SwitchToTextMode yes
lilo.conf:
vga=0

"EnableVbetool yes" and other suggestions didn't work for me.

For suspend-to-disk, don't load fglrx in initrd.

----

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
*For Debian Etch 4.0 on R50e just make following changes to /etc/default/acpi-support:
#SAVE_VBE_STATE=true
#VBESTATE=/var/lib/acpi-support/vbestate
#POST_VIDEO=true
SAVE_VIDEO_PCI_STATE=true

*For a R50e the only thing needed to make suspend to ram work in Ubuntu 6.06 is adding
Option "VBERestore" "yes"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}, and the example script below.

The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

With Ubuntu 6.10 on a [[:Category:R51|R51 (2887-32G)]] I ''just'' (as none of the other tricks above) had to add {{bootparm|fb|false}} to the kernel line in {{path|/etc/grub/menu.lst}} and edit {{path|/etc/defaults/acpi-support}} this way:

SAVE_VBE_STATE=false
POST_VIDEO=false
SAVE_VIDEO_PCI_STATE=true
USE_DPMS=false
DOUBLE_CONSOLE_SWITCH=false

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi
===Solution for ThinkPads with ATI graphic (and possibly other) chips and FreeBSD===

The FreeBSD acpi(4) manpage mentions a tunable parameter, "hw.acpi.reset_video":

hw.acpi.reset_video
Reset the video adapter from real mode during the resume path.
Some systems need this help, others have display problems if it
is enabled. Default is 0 (disabled).

This tunable can be set by adding the following line to your FreeBSD machine's /boot/loader.conf file:

hw.acpi.reset_video="1"

And rebooting your machine. Hopefully, the next time you resume from a suspend, you'll see your video again. This solution doesn't appear to be specific to ATI hardware in any way, so I presume it would be helpful for video chipsets other than ATI, as well.

If this entry doesn't help you, you might consider searching in the [http://lists.freebsd.org/pipermail/freebsd-mobile/ FreeBSD-Mobile email-list archive] for more insight.

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

===Solution using s2ram for Intel 915/945GM===

Just using the "s2ram -f -p" command from the uswsusp package will work from within X, at least on a {{Z61e}}. On {{X60s}} it is enough to issue the "s2ram" command and it works. On {{X61}} "s2ram -f -a 1" can work properly

===Solution using DOUBLE_CONSOLE_SWITCH===

By setting the following in {{path|/etc/default/acpi-support}} the display comes back on {{X61s}} using Intel chipset:

DOUBLE_CONSOLE_SWITCH=true

Fedora 8 doesn't have DOUBLE_CONSOLE_SWITCH, but it works when one does: First, add option "VBERestore" "true" to /etc/X11/xorg.conf

Section "Device"
Identifier "Videocard0"
Driver "intel"
Option "VBERestore" "true"
EndSection

Then suspends with

pm-suspend --quirk-vbemode-restore --quirk-s3-bios

Installation instructions for the ThinkPad X61

2008-03-20T13:40:35Z

BruNo:

== External Sources ==

There are informative Ubuntu forum threads on [http://ubuntuforums.org/showthread.php?t=503233 Feisty] and [http://ubuntuforums.org/showthread.php?t=523022 Gutsy] for the X61.

A very detailed report on the X61 under Ubuntu Gutsy Gibbon is [https://wiki.ubuntu.com/LaptopTestingTeam/ThinkpadX61 here]. The report was written describing Tribe 5, the last prerelease, but describes the release version of Gutsy Gibbon equally well.

* [http://slackwiki.org/ThinkPad_X61s Slackware installation instructions]
* [http://wiki.webvm.net/x61 Debian Lenny installation notes]
* [http://br1.einfach.org/GentooX61 Installing Gentoo on a Thinkpad X61]

== Problems and Solutions ==

=== X61 won't boot from the CD-ROM/DVD drive (Solved) ===

Follow these instructions to enable your [http://en.wikipedia.org/wiki/Optical_drive optical drive]:

# Reboot your X61. Press the ThinkVantage button quickly when you see the ThinkPad screen and then press F1 to enter [http://en.wikipedia.org/wiki/BIOS BIOS].
# In BIOS, select Configure -> Serial ATA.
# Now, select Compatibility instead of AHCI.
# Exit BIOS and start your computer normally.

Do this only when booting does not work. This is not always necessary!

=== Suspend/Resume doesn't work out of the box (Solved) ===

Under GNOME, you may find that Suspend/Resume doesn't work out of the box. Fn-F4 does suspend and lid open does resume, but the backlight is off after resume.

To fix this, do the following:

# In the file /boot/grub/menu.lst, find the line beginning with "# kopt=". This is where grub sets the options for your kernel. Append to this line the following: " acpi_sleep=s3_bios". (That is, these words should be preceded by a space separating them from the existing options. Do not remove the initial "#" from the line.)

# Run the command '''update-grub''' as root.

This fix '''is''' needed under Ubuntu 7.04 (Feisty Fawn), but '''is not''' needed under Gutsy Gibbon Tribe 5 or the final release version. It seems likely the difference is due to the GNOME upgrade.

=== Sound doesn't work (Solved) ===

Sound won't work under the stock ALSA 1.0.14 shipped with Ubuntu Feisty Fawn, but will in later versions including the patched 1.0.14 shipped with Ubuntu Gutsy Gibbon.

Your speakers default to being muted. To fix this, run alsamixer in a terminal window; right-arrow over until the Speaker column is visible, and press the "m" key to toggle it from mute ("MM") to on ("OO").

You may have to go to System->Preferences->Sound->Devices and select PCM to enable your Volume button to work.

The mute button always mutes rather than toggling; you have to undo it by hitting the volume-up button.

=== Known Issues under Ubuntu Feisty Fawn 7.04 and Gutsy Gibbon Beta (Tribe 5) ===

# Sound doesn't work under Feisty, but '''does''' under Gutsy Tribe 5 and Gutsy Final.
# Wireless doesn't work under Feisty, but '''does''' under Gutsy Tribe 5 and Gutsy Final.
# 2D graphics works fine, but there is no 3D acceleration yet.
# Fingerprint reader doesn't work yet.

=== Other Notes ===

The stock drive in the X61 of October 2007 appears not to have the [[Problem_with_hard_drive_clicking|click-of-death]] issue noted on some other ThinkPads. Note, this could potentially change if Lenovo changes drive suppliers.

The X61 is apparently very similar to a T61 internally. You may be able to find helpful tips in the
installation instructions for the [[Installation_instructions_for_the_ThinkPad_T61|Installation instructions for the Thinkpad T61]] for problems that are not solved here.

[[Category:X61]]

Installation instructions for the ThinkPad X61

2008-03-20T13:37:45Z

BruNo:

There are informative Ubuntu forum threads on [http://ubuntuforums.org/showthread.php?t=503233 Feisty] and [http://ubuntuforums.org/showthread.php?t=523022 Gutsy] for the X61.

A very detailed report on the X61 under Ubuntu Gutsy Gibbon is [https://wiki.ubuntu.com/LaptopTestingTeam/ThinkpadX61 here]. The report was written describing Tribe 5, the last prerelease, but describes the release version of Gutsy Gibbon equally well.

* [http://slackwiki.org/ThinkPad_X61s Slackware installation instructions]
* [http://wiki.webvm.net/x61 Debian Lenny installation notes]
* [http://br1.einfach.org/GentooX61 Installing Gentoo on a Thinkpad X61]

=== X61 won't boot from the CD-ROM/DVD drive (Solved) ===

Follow these instructions to enable your [http://en.wikipedia.org/wiki/Optical_drive optical drive]:

# Reboot your X61. Press the ThinkVantage button quickly when you see the ThinkPad screen and then press F1 to enter [http://en.wikipedia.org/wiki/BIOS BIOS].
# In BIOS, select Configure -> Serial ATA.
# Now, select Compatibility instead of AHCI.
# Exit BIOS and start your computer normally.

=== Suspend/Resume doesn't work out of the box (Solved) ===

Under GNOME, you may find that Suspend/Resume doesn't work out of the box. Fn-F4 does suspend and lid open does resume, but the backlight is off after resume.

To fix this, do the following:

# In the file /boot/grub/menu.lst, find the line beginning with "# kopt=". This is where grub sets the options for your kernel. Append to this line the following: " acpi_sleep=s3_bios". (That is, these words should be preceded by a space separating them from the existing options. Do not remove the initial "#" from the line.)

# Run the command '''update-grub''' as root.

This fix '''is''' needed under Ubuntu 7.04 (Feisty Fawn), but '''is not''' needed under Gutsy Gibbon Tribe 5 or the final release version. It seems likely the difference is due to the GNOME upgrade.

=== Sound doesn't work (Solved) ===

Sound won't work under the stock ALSA 1.0.14 shipped with Ubuntu Feisty Fawn, but will in later versions including the patched 1.0.14 shipped with Ubuntu Gutsy Gibbon.

Your speakers default to being muted. To fix this, run alsamixer in a terminal window; right-arrow over until the Speaker column is visible, and press the "m" key to toggle it from mute ("MM") to on ("OO").

You may have to go to System->Preferences->Sound->Devices and select PCM to enable your Volume button to work.

The mute button always mutes rather than toggling; you have to undo it by hitting the volume-up button.

=== Known Issues under Ubuntu Feisty Fawn 7.04 and Gutsy Gibbon Beta (Tribe 5) ===

# Sound doesn't work under Feisty, but '''does''' under Gutsy Tribe 5 and Gutsy Final.
# Wireless doesn't work under Feisty, but '''does''' under Gutsy Tribe 5 and Gutsy Final.
# 2D graphics works fine, but there is no 3D acceleration yet.
# Fingerprint reader doesn't work yet.

=== Other Notes ===

The stock drive in the X61 of October 2007 appears not to have the [[Problem_with_hard_drive_clicking|click-of-death]] issue noted on some other ThinkPads. Note, this could potentially change if Lenovo changes drive suppliers.

The X61 is apparently very similar to a T61 internally. You may be able to find helpful tips in the
installation instructions for the [[Installation_instructions_for_the_ThinkPad_T61|Installation instructions for the Thinkpad T61]] for problems that are not solved here.

[[Category:X61]]

Hardware Specifications

2008-03-07T03:06:34Z

BruNo: add link to X61

{{Usage|
*Choose a model name to get a list of all currently available information related to this Model.
*Choose a type-and-model number to get the specs of that specific model.
}}
Here you can learn about specific ThinkPads specifications.

Furthermore, you may
*compare the [[ThinkPad series]] (G, R, T, X, Z),
*get an overview of the [[ThinkPad History]] or
*learn about the name [[ThinkPad]].

==IBM/Lenovos hardware specs==
* '''Lenovo ThinkPads'''
** For current Lenovo ThinkPad G, R, T, X and Z series models look for the official specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tabook.pdf tabook.pdf]
** For withdrawn Lenovo ThinkPads, look at [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/ltwbook.pdf ltwbook.pdf]
* '''Withdrawn IBM ThinkPads'''
** For A, G, T and X series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tawbook.pdf tawbook.pdf]
** For R series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/trwbook.pdf trwbook.pdf]
** For i series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tiwbook.pdf tiwbook.pdf]
** For 200, 300, 500, 600 and 700 series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/twbook.pdf twbook.pdf]<br>
** Or try searching the IBM announcements letters [http://www.ibm.com/news/usalet/ here].

==Available Models==
{| cellspacing="0" cellpadding="5" border="1"
|- style="text-align:left;"
!Numbered!!A series!!G series!!R series!!S series!!T series!!X series!!Z series!!others
|- style="text-align:left;vertical-align:top;"
|
'''[[:Category:240 | ThinkPad 240]]'''

'''[[:Category:240X | ThinkPad 240X]]'''

'''[[:Category:240Z | ThinkPad 240Z]]'''

'''[[:Category:390X | ThinkPad 390X]]'''

'''[[:Category:600 | ThinkPad 600]]'''

'''[[:Category:600E | ThinkPad 600E]]'''

'''[[:Category:600X | ThinkPad 600X]]'''

'''[[:Category:700 | ThinkPad 700]]'''

'''[[:Category:760ED | ThinkPad 760ED]]'''

'''[[:Category:760XD | ThinkPad 760XD]]'''

'''[[:Category:765L | ThinkPad 765L]]'''

'''[[:Category:765D | ThinkPad 765D]]'''

'''[[:Category:770 | ThinkPad 770]]'''

'''[[:Category:770E | ThinkPad 770E]]'''
*[[9548-510]]
*[[9548-51U]]

'''[[:Category:770X | ThinkPad 770X]]'''
*[[9549-7AO]]
'''[[:Category:770Z | ThinkPad 770Z]]'''

||
'''[[:Category:A20m | ThinkPad A20m]]'''

'''[[:Category:A20p | ThinkPad A20p]]'''

'''[[:Category:A21e | ThinkPad A21e]]'''

'''[[:Category:A21m | ThinkPad A21m]]'''

'''[[:Category:A21p | ThinkPad A21p]]'''

'''[[:Category:A22e | ThinkPad A22e]]'''

'''[[:Category:A22m | ThinkPad A22m]]'''

'''[[:Category:A22p | ThinkPad A22p]]'''

'''[[:Category:A30 | ThinkPad A30]]'''

'''[[:Category:A30p | ThinkPad A30p]]'''

'''[[:Category:A31 | ThinkPad A31]]'''

'''[[:Category:A31p | ThinkPad A31p]]'''

||
'''[[:Category:G40 | ThinkPad G40]]'''

'''[[:Category:G41 | ThinkPad G41]]'''

||
'''[[:Category:R30 | ThinkPad R30]]'''

'''[[:Category:R31 | ThinkPad R31]]'''

'''[[:Category:R32 | ThinkPad R32]]'''

'''[[:Category:R40 | ThinkPad R40]]'''
*[[2722-9BM]]
*[[2722-DG1]]
*[[2722-BDG]]

'''[[:Category:R40e | ThinkPad R40e]]'''
*[[1834-9LG]]
*[[1834-J8G]]

'''[[:Category:R50 | ThinkPad R50]]'''
*[[1829-3HU]]

'''[[:Category:R50p | ThinkPad R50p]]'''

'''[[:Category:R50e | ThinkPad R50e]]'''
*[[1834-J8G]]

'''[[:Category:R51 | ThinkPad R51]]'''
*[[1829-K6G]]
*[[1829-L7G]]
*[[1830-DG4]]

'''[[:Category:R52 | ThinkPad R52]]'''
*[[1846-B5G]]
*[[1859-4AU]]

'''[[:Category:R60 | ThinkPad R60]]'''
*[[9456-6FG]]

'''[[:Category:R60e | ThinkPad R60e]]'''
*[[0657-3LG]]

'''[[:Category:R61 | ThinkPad R61]]'''
*[[7422-CTO]]
*[[8918-5QG]]
||
'''[[:Category:S30|ThinkPad S30]]'''

'''[[:Category:S31|ThinkPad S31]]'''
||
'''[[:Category:T20|ThinkPad T20]]'''
*[[2647-44G]]

'''[[:Category:T21|ThinkPad T21]]'''
*[[2647-97G]]

'''[[:Category:T22|ThinkPad T22]]'''

'''[[:Category:T23 | ThinkPad T23]]'''
*[[2647-9RG]]
*[[2647-7G1]]
*[[2647-8QU]]

'''[[:Category:T30 | ThinkPad T30]]'''
*[[2366-52U]]
*[[2366-91U]]
*[[2366-FBG]]
*[[2366-GU1]]
*[[2366-JBG]]
*[[2366-R7G]]

'''[[:Category:T40 | ThinkPad T40]]'''

'''[[:Category:T40p | ThinkPad T40p]]'''
*[[2373-G1U]]

'''[[:Category:T41 | ThinkPad T41]]'''

'''[[:Category:T41p | ThinkPad T41p]]'''
*[[2373-315]]
*[[2373-GGG]]
*[[2373-GHG]]
*[[2374-GGU]]

'''[[:Category:T42 | ThinkPad T42]]'''
*[[2373-6ZG]]
*[[2373-9XU]]
*[[2373-B09]]
*[[2373-CH6]]
*[[2373-F1G]]
*[[2373-F7G]]
*[[2373-FWG]]
*[[2373-M1G]]
*[[2373-VUW]]
*[[2373-WGK]]
*[[2378-FVU]]
*[[2378-RSU]]
*[[2379-DXU]]

'''[[:Category:T42p | ThinkPad T42p]]'''
*[[2373-HTG]]
*[[2373-W6M]]
*[[2373-Y4M]]
*[[2378-DYU]]
*[[2378-KXM]]

'''[[:Category:T43 | Thinkpad T43]]'''
*[[2668-A1U]]
*[[2668-C2U]]
*[[2668-8AG]]
*[[2668-98U]]

'''[[:Category:T43p | Thinkpad T43p]]'''

'''[[:Category:T60 | ThinkPad T60]]'''

'''[[:Category:T60p | ThinkPad T60p]]'''

'''[[:Category:T61 | ThinkPad T61]]'''

'''[[:Category:T61p | ThinkPad T61p]]'''
||
'''[[:Category:X20 | ThinkPad X20]]'''

'''[[:Category:X21 | ThinkPad X21]]'''
*[[2662-66U]]

'''[[:Category:X22 | ThinkPad X22]]'''
*[[2662-95U]]
*[[2662-9BU]]

'''[[:Category:X23 | ThinkPad X23]]'''
*[[2662-EVJ]]

'''[[:Category:X24 | ThinkPad X24]]'''
*[[2662-MQG]]

'''[[:Category:X30 | ThinkPad X30]]'''

'''[[:Category:X31 | ThinkPad X31]]'''

'''[[:Category:X32 | ThinkPad X32]]'''

'''[[:Category:X40 | ThinkPad X40]]'''
*[[2371-AVC]]

'''[[:Category:X41 | ThinkPad X41]]'''

'''[[:Category:X41 Tablet | ThinkPad X41 Tablet]]'''

'''[[:Category:X60 | ThinkPad X60]]'''
*[[1706-BM3]]
*[[1706-BM7]]

'''[[:Category:X60s | ThinkPad X60s]]'''

'''[[:Category:X60_Tablet | ThinkPad X60 Tablet]]'''

'''[[:Category:X61 | ThinkPad X61]]'''

'''[[:Category:X61s | ThinkPad X61s]]'''
* [[7669-27G]]

'''[[:Category:X61_Tablet | ThinkPad X61 Tablet]]'''
* [[7762-95G]]

'''[[:Category:X300 | ThinkPad X300]]'''

||

'''[[:Category:Z60t | ThinkPad Z60t]]'''

'''[[:Category:Z60m | ThinkPad Z60m]]'''

'''[[:Category:Z61e | ThinkPad Z61e]]'''

'''[[:Category:Z61t | ThinkPad Z61t]]'''

'''[[:Category:Z61m | ThinkPad Z61m]]'''

'''[[:Category:Z61p | ThinkPad Z61p]]'''
||
'''[[:Template:I_Series | I Series]]'''
'''[[:Category:PC110 | PC110]]'''
*[[PC110]]

'''[[:Category:TransNote|TransNote]]'''
*[[2675-61G]]

|}

[[Category:Models]]