https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=Vrossum&feedformat=atomThinkWiki - User contributions [en]2024-03-29T08:10:17ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=How_to_control_fan_speed&diff=55828How to control fan speed2014-08-17T12:05:12Z<p>Vrossum: /* Fan Tachometer */ added part on 65335 error.</p>
<hr />
<div>This page discusses methods for controlling the system fan.<br />
<br />
{| width="100%" columns="2"<br />
|style="vertical-align:top;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
<br />
{{WARN|When designing fan-control applets, never ignore a valid thermal sensor.<br />
<br />
Even if it seems to be stuck at a certain temperature, you must take that sensor into account. While it will probably make the fan spin faster than if the sensor was ignored, that's exactly what would happen when the fan is under EC control, and could very well be the reason for the "stuck" value in the first place.<br />
<br />
Always play it safe. If a battery pack seems to want the fan to always run faster, the only safe thing to do is to make it run faster.}}<br />
|}<br />
<br />
==For Linux==<br />
<br />
{{NOTE|Fan control operations are disabled by default for safety reasons.}}<br />
<br />
To enable fan control, the module parameter <tt>fan_control=1</tt> must be given to thinkpad-acpi.<br />
<br />
For example, in Ubuntu 8.04 (Hardy Heron), add the following to {{path|/etc/modprobe.d/options}}: <tt>options thinkpad_acpi fan_control=1</tt><br />
<br />
For Debian Squeeze (testing) create {{path|/etc/modprobe.d/thinkpad_acpi.conf}} with: <tt>options thinkpad_acpi fan_control=1</tt> and install the package <tt>thinkfan</tt><br />
<br />
Having done so, reboot and you can use the following commands to control fan speed:<br />
<br />
{{cmdroot|echo level 0 > /proc/acpi/ibm/fan}} (fan off)<br />
<br />
{{cmdroot|echo level 2 > /proc/acpi/ibm/fan}} (low speed)<br />
<br />
{{cmdroot|echo level 4 > /proc/acpi/ibm/fan}} (medium speed)<br />
<br />
{{cmdroot|echo level 7 > /proc/acpi/ibm/fan}} (maximum speed)<br />
<br />
{{cmdroot|echo level auto > /proc/acpi/ibm/fan}} (automatic - default)<br />
<br />
{{cmdroot|echo level disengaged > /proc/acpi/ibm/fan}} (disengaged)<br />
<br />
If you receive a PERMISSION DENIED error you can use the following command syntax instead as a work-around:<br />
<br />
<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level 0 | sudo tee /proc/acpi/ibm/fan</code> (fan off)<br />
<br />
<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level 2 | sudo tee /proc/acpi/ibm/fan</code> (low speed)<br />
<br />
<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level 4 | sudo tee /proc/acpi/ibm/fan</code> (medium speed)<br />
<br />
<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level 7 | sudo tee /proc/acpi/ibm/fan</code> (maximum speed)<br />
<br />
<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level auto | sudo tee /proc/acpi/ibm/fan</code> (automatic - default)<br />
<br />
<code style="white-space:nowrap;color:#495988;background-color:white;"><nowiki>#</nowiki> echo level disengaged | sudo tee /proc/acpi/ibm/fan</code> (disengaged)<br />
<br />
===Automated control scripts===<br />
<br />
An [[ACPI fan control script#Variable speed control scripts|ACPI fan control script]] can be used to override the firmware's fan algorithm with gentler, quieter version. It monitors the laptop's [[thermal sensors]] and sets the fan speed accordingly, according to customizable thresholds. For the default behavior, simply save {{CodeRef|tp-fancontrol}} as {{path|tp-fancontrol}}, make sure you've loaded [[thinkpad-acpi]] with the "fan_control=1" parameter, and run:<br /><br />
{{cmdroot|./tp-fancontrol}}<br />
<br />
There is an distro independent daemon (http://launchpad.net/tp-fan/tpfand/0.94/+download/tpfand-0.94.tar.gz), written in python. Packages are available for debian based linux systems.<br />
<br />
[http://www.gambitchess.org/moin.py/ThinkPad_Fan_Control A GTK GUI program (packaged for Ubuntu 7.10 and 8.04)] may also help.<br />
<br />
===Automated program - Simple ThinkPad Fan Control===<br />
<br />
'''[https://github.com/Stanko/ThinkPad-Fan-Control GitHub Page]'''<br />
<br />
This is program for controlling fans speed on IBM/Lenovo ThinkPads. It is written<br />
for Linux only. This program is written in C, using GTK GUI.<br />
<br />
You are required to have the Linux kernel with 'thinkpad-acpi' patch.<br />
You must also enable manual control for your fans. For Linux 2.6.22 and above,<br />
you must add 'fan_control=1' as a module parameter to 'thinkpad-acpi'.<br />
For example, in Debian Lenny (and Ubuntu 8.04), you must add the following<br />
to "/etc/modprobe.d/options":<br />
options thinkpad_acpi fan_control=1<br />
<br />
Having done so, reboot. Now you'll be able to use this program easily.<br />
<br />
Here is screenshot:<br />
[[Image:Tpfc.png|none]]<br />
<br />
and direct download (src + i386 32bit binary). Please read README.txt file<br />
included in package. <br />
<br />
'''Download links'''<br />
<br />
'''[https://github.com/Stanko/ThinkPad-Fan-Control GitHub Page]'''<br />
<br />
<br />
'''Direct download:'''<br />
<br />
[[http://www.box.net/shared/phz3foll8oe0501k8s1j tpfc0.5.tar.gz]]<br />
<br />
<br />
----<br />
<br />
I wrote this for my own personal use, and thought that it would be a good idea<br />
to release it to the world, and hope that it will be useful to someone!<br />
Feel free to send comments, bug reports or a thanks to the e-mail above. Although I don't use ThinkPad anymore (so I can't test the program), I still try to respond to all emails I get.<br />
<br />
==For Windows==<br />
<br />
Shimodax's ThinkPad fan control tool offers similar functionality (see [http://forum.thinkpads.com/viewtopic.php?t=17715 forum discussion] at thinkpads.com). Source and binaries are available through the [http://sourceforge.net/projects/tp4xfancontrol "Tp4xFanControl"] project on SourceForge.<br />
<br />
==Hardware specs==<br />
<br />
The following hardware behavior was discovered experimentally by [[User:Thinker|Thinker]] and neither provided by nor confirmed by IBM/Lenovo. The following description may be inaccurate and may vary by model (see list of models above). The terminology probably does not match the one used by IBM/Lenovo engineers.<br />
<br />
{{NOTE|Information on other models is included in the [[thinkpad-acpi]] [[Git]] version.}}<br />
{{NOTE|1=The ThinkPad {{X61s}} and {{X61}} with WWAN have a [http://forum.notebookreview.com/showthread.php?t=141931 second system fan]. It shares the same control register as the main fan (cannot be controlled separately), and exposes a second tachometer.}}<br />
<br />
ACPI DSDT register HFSP (8 bits, offset 0x2F in the <tt>EmbeddedController</tt> address space, accessed through the standard EC interface at IO ports 0x62 and 0x66) is read/writable and has the following meaning:<br />
<br />
Bits 7 6 5 4 3 2 1 0<br />
---------------<br />
Value 1 0 * * * * * * - automatic<br />
* 1 * * * * * * - disengaged<br />
0 0 N N N N N N - manual (0..63; 0=disable fan, 1=min, ..., 7=max)<br />
<br />
Changing modes may not be immediate on all ThinkPads. Later ThinkPad models seem to take at least 5s to start responding to a fan mode change, for example.<br />
<br />
After boot, the HFSP register may not reflect the true state of the EC (on some models it reads 0x07 even though the EC is actually in automatic mode).<br />
<br />
The HFSP register controls both fans at the same time in the X61/X61s.<br />
<br />
=== Fan Tachometer ===<br />
<br />
The embedded controller registers 0x84 (LSB), 0x85 (MSB) are the main fan tachometer, and report fan speed in RPM in everything since the {{A31}} and maybe a little earlier. Not much is know about the tachometer in earlier models, or even whether they had one or not.<br />
<br />
On the X61/X61s, one must select through EC register 0x31 bit 0 which fan the tachometer registers will expose (Firmware 7M). Beware: this is the same register used for brightness control in other models.<br />
<br />
If the speed reported is 65335, then is typically due to a broken fan assembly. <br />
The fan might still be rotating.<br />
This error can be intermittent and can prevent booting (Error 'Fan error')<br />
<br />
=== Automatic mode ===<br />
In ''automatic'' mode, the embedded controller sets the fan speed automatically according to system temperatures and some unknown algorithm.<br />
<br />
Note that the ACPI DSDT may supplement this in some models. The {{X40}}, for example, changes the profile of speeds the automatic mode should use depending on battery status.<br />
<br />
=== Manual mode ===<br />
<br />
In ''manual'' mode, the fan level is forced to the given value and the EC will auto-regulate the fan to maintain at a (roughly) constant RPM, which is model-dependent. Manual speed levels 8-63 yield the same behavior as level 7, and the the ACPI DSDT uses level 7 for the emergency mode it enters upon critical CPU/GPU temperature, so apparently 7 is the real maximum level.<br />
<br />
=== Disengaged (full-speed) mode ===<br />
<br />
In ''disengaged'' mode, the embedded controller does not monitor the fan speed. It "disengages" the closed-loop control function that keeps track of fan speed, and uses an open-loop control function that ramps up the fan to its maximum speed (100% duty-cycle). The end speed is not stable, but it is often much faster than the maximum speed manual and automatic modes would set the fan to.<br />
<br />
Most newer ThinkPads take quite a while (in excess of one minute) to fully enter disengaged mode. Exiting it is much faster. The {{A31}} acts differently, and switches to disengaged mode as fast as it switches to other modes.<br />
<br />
For some reason, the embedded controller may stop updating the tachometer registers while entering or exiting disengaged mode in some ThinkPad firmware versions (hence the EC tachometer registers will not be updated on these models while entering/exiting disengaged mode). Once it arrives at maximum speed, or once it gets back at closed-loop cruise speed, the embedded controller starts updating the tachometer registers again. Later T models such as the {{T43}} have this problem, while the {{A31}} does not.<br />
<br />
{{HINT|Apparently the [[Problem with fan noise|pulsing fan noise]] experienced by some users can be cured by repeatedly running 2-4 seconds of manual control followed by 0.5-1 seconds of disengaged mode. The pulse occurs when the the embedded controller computes the fan speed and adjusts the fan voltage adaptively every few seconds (~4.8sec for the ThinkPad T43); the aforementioned mode switching doesn't give it a chance to do so. Some of the [[ACPI fan control script#Variable speed control scripts|ACPI fan control scripts]] implements this solution.}}<br />
<br />
{{HINT|To force engaged mode using [http://www.staff.uni-marburg.de/~schmitzr/donate.html TPFanControl] for Windows, enter '64' as the value (0-7) for manual mode. This can also be incorporated into smart mode through a custom tpfancontrol.ini}}<br />
<br />
==Supported models==<br />
<br />
The above was successfully tested on the following models:<br />
<br />
* ThinkPad {{A31}}, {{A31p}} (fan levels RPM: 0 = off, 1-2 = ~3280-3380 (!), 3-5 = ~3200, 6-7 = ~3380, "disengaged" = ~4000 (see NOTE above))<br />
* ThinkPad {{R50}} (highest manual level is 3; disengage mode works and reaches much higher RPM)<br />
* ThinkPad {{R50p}} (fan levels RPM: 0 = off, 1-2 = ~3200, 3-5 = ~3500-3600, 6-7 = ~3700-3800, disengaged = ~5300)<br />
* ThinkPad {{R51}} (fan levels RPM: 0 = off, 1-2 = ~3150, 3-5 = ~3350, 6 = ~3750, disengaged = ~5100)<br />
* ThinkPad {{R51e}} (fan levels RPM: 0 = off, 1-2 = ~3300, 3-5 = ~3800, 6 = ~4150, disengaged = ~5100)<br />
* ThinkPad {{R52}} (fan levels RPM: 0 = off, 1-2 = ~3350, 3-5 = ~3650, 6 = ~4250, disengaged = ~5245)<br />
* ThinkPad {{R60}} (fan levels RPM: 0 = off, 1-1 = ~2650, 3-5 = ~3300, 6-7 = ~3950, disengaged = ~4800)<br />
* ThinkPad {{R60e}}<br />
* ThinkPad {{R61i}} (fan levels RPM: 0 = off, 1 = 2689, 2 = 2729, 3 = 3059, 4 = 3047, 5 = 3051, 6 = 3515, 7 = 3468, full-speed/disengaged = 4119~4200)mod.#7650-D7G@+/-2yr.used<br />
* ThinkPad {{T22}}<br />
* ThinkPad {{T23}} <br />
** (low speed = '''~2200''', medium and maximum speed = '''~4800'''; disengaged mode works at '''~5800''')<br />
** (fan levels = ~RPM: 0 = '''0'''; 1,2 = '''~2200'''; 3,4,5,6,7 = '''~4900'''; disengaged,full-speed = '''~6331''')<br />
* ThinkPad {{T30}}<br />
* ThinkPad {{T40}} (fan levels RPM: 1-2 = ~2950, 3-5 = ~3600, 6-7 = ~4050; disengaged = ~5400)<br />
* ThinkPad {{T400}} (fan levels RPM: 1 = ~1886, 2 = ~2800, 3-5 = ~3000, 6-7 = ~3500; disengaged mode works at ~5100)<br />
* ThinkPad {{T41}}, {{T41p}} (fan levels RPM: 1-2 = ~2980, 3-5 = ~3500, 6-7 = ~4050; disengaged mode works at ~5100)<br />
* ThinkPad {{T410i}} (fan levels RPM: 0 = off, 1 = ~1950, 2 = ~3575, 3-4 = ~3700, 5-6 = ~3825, 7 = ~4525; full-speed/disengaged = ~5450; only Linux-tested with tpfc0.5)<br />
* ThinkPad {{T42}}, {{T42p}} (fan levels RPM: 1-2 = ~2900, 3-5 = ~3700, 6-7 = ~4700; disengaged mode works at ~5200)<br />
* ThinkPad {{T43}}, {{T43p}} (fan levels RPM: 1-2 = ~3300, 3-5 = ~4100, 6-7 = ~4700; disengaged mode works at ~6450)<br />
* ThinkPad {{T60}} (fan levels RPM: 1-2 = 3000-3100, 3-5 = ~3600, 6-7 = ~4500; disengaged mode works at ~5500)<br />
* ThinkPad {{T61}} (fan levels RPM: 0 = off, 1-2 = ~2980, 3-5 = ~3330, 6-7 = ~3760; disengaged mode works at ~4500)<br />
* ThinkPad {{W500}} (fan levels RPM: 0=off, 1-2 = 1900, 3-5 = ~3000, 6-7 = ~3500; disengaged mode works at ~5100)<br />
* ThinkPad {{W510}} (fan levels RPM: 0=off, 1 = ~2750, 2 = ~3100, 3-5 = ~3500, 6-7 = ~4000; disengaged mode works at ~4585)<br />
* ThinkPad {{X30}} (level 0 = off, low = ~3900, medium = ~4200, maximum = ~4650, disengaged = ~5900)<br />
* ThinkPad {{X31}} (fan levels RPM: 0 = off, 1-2 = ~2850, 3-5 = ~3450, 6 = ~4050, 7 = ~4150; disengaged mode works at ~4975)<br />
* ThinkPad {{X40}}<br />
* ThinkPad {{X41}}<br />
* ThinkPad {{X41T}}<br />
* ThinkPad {{X60}}<br />
** level 0: 0<br />
** level 1: ~2819<br />
** level 2: ~2850<br />
** level 3: ~3025<br />
** level 4: ~3106<br />
** level 5: ~3108<br />
** level 6: ~3580<br />
** level 7: ~3609~3700<br />
** disengaged: ~4700<br />
* ThinkPad {{X61}} (fan levels RPM: 1-2 = ~3400, 3-5 = ~3800, 6-7 = ~4500, disengaged = ~6700)<br />
* ThinkPad {{X61s}} (fan levels RPM: 0 = off, 1-2 = ~3800, 3-5 = ~4500, 6-7 = ~4800, disengaged = ~4800) (though fancontrol can keep it at 2500rpm...)<br />
* ThinkPad {{X120e}}<br />
* ThinkPad {{X201i}} (fan levels RPM: 0 = off, 1 = ~1900, 4 = ~3400, 7 = ~4200, disengaged = ~6300) <br />
* ThinkPad {{X220}} (fan levels RPM: 0 = off, 1 = ~2000, 2 = ~3000, 3-4 = ~3500, 5-6 = ~3900, 7 = ~4500, full-speed = ~5300, disengaged = ~5300)<br />
* ThinkPad {{Z60t}}, {{Z60m}} (fan levels RPM: 1-2 = ~1700, 3-5 = ~2800, 6-7 = ~3500)<br />
* ThinkPad {{Z61m}}<br />
* Thinkpad {{Z61p}} (fan levels 0-7, auto, disengaged; enable, disable; watchdog (untested))<br />
* Thinkpad {{Edge11}} (fan levels: 0 = off, 1, 2, 3, 7 = full; RPM shown value is around 492 - 503, but should be 1000 - 3000) <br />
Probably other models are supported too (please update this page if you confirm this; maintain some ordering too).<br />
<br />
==Models using a different interface==<br />
<br />
The following models also work, use a different access method which supported (only) via the {{path|/proc/acpi/ibm/fan}} of [[thinkpad-acpi]]. No need for patching.<br />
<br />
* ThinkPad {{600E}}, {{600X}}, {{770E}}, {{770X}} (these use a different fan control interface)<br />
<br />
==Unsupported models==<br />
<br />
* ThinkPad {{560}}, {{560X}} (these models don't have a fan)</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=ThinkPad_X200_UltraBase&diff=53294ThinkPad X200 UltraBase2012-01-09T12:32:05Z<p>Vrossum: /* ThinkPad X200 UltraBase */</p>
<hr />
<div>{| cellspacing="0" cellpadding="2" border="0"<br />
| style="vertical-align:top;" | __TOC__<br />
<br />
[[File:UltraBaseX200.jpg|200px|center]]<br />
| style="vertical-align:top;" | <div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
== ThinkPad X200 UltraBase ==<br />
Here is some basic info about X200 UltraBase: portable dock for the X20x-series ThinkPads, providing extra ports (notably DisplayPort), [[Ultrabay|Ultrabay Slim]] slot and an additional battery slot.<br />
<br />
=== Features ===<br />
* Passthrough ports:<br />
** Gigabit Ethernet (RJ45)<br />
** [[VGA Port|VGA]] (supporting up to 2048x1536 according to Lenovo, tested up to 2048x1152)<br />
** Microphone<br />
** Headphone<br />
** Power supply<br />
* Additional ports:<br />
** 4 USB ports (1 on the right side, 3 on the back)<br />
** [[DisplayPort]] (supporting up to 2560x1600), DP->DVI-adaptor is working (tested with Dell 2007FPb monitor)<br />
* Battery charging connector<br />
* [[Ultrabay|Serial Ultrabay Slim]] which accepts one of these [[Ultrabay_Devices#Serial_Ultrabay_Slim_Devices|Serial Ultrabay Slim devices]]<br />
<br />
===Pros & Cons===<br />
Positives:<br />
* eases up portability of laptop<br />
* provides digital video output<br />
* provides option for optical drive<br />
* allows effective use of second battery<br />
* allows to connect 2 external monitors (one via DisplayPort, second via VGA)<br />
Negatives:<br />
* reduces cooling capabilities a bit (mainly HDD)<br />
* introduces some noise to VGA signal. This is something you should pay attention at when purchasing: we've got many of these ultrabases at my company and some of them introduce only a bit of noise while others much more.<br />
<br />
===DisplayPort support in Linux===<br />
<br />
Kernel support for DisplayPort in intel graphic chips using KMS (Kernel Mode Setting) was added by Keith Packard in version 2.6.31. On the userspace side driver version 2.7 or newer is required to use KMS. In order to activate it you need to pass {{bootparm|modeset|1}} parameter to i915 driver either at boot time or in your initramfs.<br />
<br />
{{NOTE|When passing module parameter at boot time you need to precede it's name by module name followed by a dot so in this case you would need to add {{bootparm|i915.modeset|1}} to your boot command line.}}<br />
<br />
{{HINT|To pass module parameter in initramfs simply add it to your modprobe configuration and update your initramfs with <code>update-initramfs</code> command.}}<br />
<br />
=== Links ===<br />
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-70299 Product Overview]<br />
<br />
===Supported with the following ThinkPads===<br />
* {{X200}}, {{X200s}}, {{X200_Tablet}}<br />
* {{X201}}, {{X201i}}, {{X201s}}, {{X201 Tablet}}</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=DisplayPort&diff=52835DisplayPort2011-08-22T12:24:49Z<p>Vrossum: added x220</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
DisplayPort is a digital video connector, available on select ThinkPads<br />
<br />
</div><br />
|}<br />
<br />
* [[Wikipedia:DisplayPort| Wikipedia article on DisplayPort]]<br />
<br />
==ThinkPads featuring this technology==<br />
* {{L412}}, {{L512}}<br />
* {{R500}}<br />
* {{T400s}}, {{T410}}, {{T410i}}, {{T410s}}, {{T410si}}, {{T420}}, {{T500}}, {{T510}}, {{T510i}}, {{T520}}<br />
* {{W500}}, {{W510}}, {{W520}}, {{W700}}, {{W700ds}}, {{W701}}, {{W701ds}}<br />
* {{X301}},{{X220}}<br />
<br />
==Port Replicators and Docks featuring this technology==<br />
Note, some have multiple Displayports<br />
* [[ThinkPad Mini Dock Series 3]]<br />
* [[ThinkPad Mini Dock Plus Series 3 - 170W]]<br />
* [[ThinkPad Mini Dock Plus Series 3 - 135W]]<br />
* [[ThinkPad Mini Dock Plus Series 3 - 90W]]<br />
* [[X200 UltraBase]]<br />
* [[W700 Mini Dock]]<br />
* [[W700 Mini Dock 2.0]]<br />
<br />
== DVI Pass-through ==<br />
<br />
Certain ThinkPad models have a DisplayPort connection which offers DVI pass-through.<br />
<br />
Check [http://www-307.ibm.com/pc/support/site.wss/MIGR-72148.html ThinkPad Digital Video Interface (DVI) and DVI Pass-Through] for more information, and to see if a specific model and configuration is supported.<br />
<br />
== Audio Support ==<br />
<br />
There are reports that DisplayPort on some (possibly all) current thinkpads does not support audio. While there are adapters to convert DisplayPort to HDMI, the lack of audio makes it impossible to, for example, watch a DVD or Blu-Ray on an HDTV using the DisplayPort. [http://forums.lenovo.com/t5/W-Series-ThinkPad-Laptops/Displayport-to-HDMI-with-audio/td-p/68575 See this thread for more information]<br />
<br />
Audio over DisplayPort when used in conjunction with a DisplayPort to HDMI conversion cable is [http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T410-T510-DisplayPort-features-audio/td-p/191530/page/3 confirmed] to work on W500, T410 and T510 both on integrated and discrete graphics options on Windows systems.<br />
<br />
=== T410s ===<br />
<br />
The T410s supports audio pass-through via DisplayPort on recent Linux systems.<br />
<br />
With the Intel HD Audio modul selected recent linux kernels detect the DisplayPort<br />
audio as a separate output device:<br />
<br />
On 2.6.36-rc1 the following devices can be found in /proc/asound/*<br />
<br />
Codec: Intel IbexPeak HDMI<br />
Device: name="INTEL HDMI 0", type="HDMI", device=3<br />
Device: name="INTEL HDMI 1", type="HDMI", device=7<br />
<br />
If you want to pass Audio via DisplayPort you just have to switch to the Intel HDMI audio output device<br />
for the application in PulseAudio (didn't test with pure ALSA).<br />
<br />
=== W510 ===<br />
<br />
The more recent versions of the W510 with the Quadro FX 880M support audio and video out through DisplayPort. Tested with a DisplayPort to HDMI with Audio converter. Used alsa (no PulseAudio) and mplayer, 2.6.35-ARCH, using mplayer -afm hwdts,hwac3 -ao alsa:noblock:device=hw=1.7 and nvidia driver version 256.53. Had to unmute with alsamixer -c1<br />
<br />
== Problems ==<br />
<br />
=== Twinview using Displayport and DVI broken ===<br />
On my T410 mini-dock series 3, the displayport works unless I try to use it while using the DVI out as well.<br />
DVI+VGA works, but nvidia-settings dies horribly. Tried with 195.* and 260* drivers.<br />
<br />
I am using a displayport -> DVI adapter (displayport++ allows this).<br />
<br />
<b> FIX:</b><br />
Using Nouveau drivers instead of the nvidia binary blob allows my displayport to work in concert with the DVI out of my dock.<br />
This allows dual digital external displays. Attempting to activate the laptop monitor as well leads to problems.<br />
<br />
<b> ANOTHER FIX: </b><br />
Version 275* from the nvidia website allows me to use Displayport and DVI at the same time as well.<br />
<br />
== External Sources ==<br />
* [http://www-307.ibm.com/pc/support/site.wss/MIGR-72148.html ThinkPad Digital Video Interface (DVI) and DVI Pass-Through]<br />
* [http://www-307.ibm.com/pc/support/site.wss/MIGR-70321.html DisplayPort Monitor Cables - Overview]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=DisplayPort&diff=52828DisplayPort2011-08-19T13:03:52Z<p>Vrossum: /* ThinkPads featuring this technology */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
DisplayPort is a digital video connector, available on select ThinkPads<br />
<br />
</div><br />
|}<br />
<br />
* [[Wikipedia:DisplayPort| Wikipedia article on DisplayPort]]<br />
<br />
==ThinkPads featuring this technology==<br />
* {{L412}}, {{L512}}<br />
* {{R500}}<br />
* {{T400s}}, {{T410}}, {{T410i}}, {{T410s}}, {{T410si}}, {{T420}}, {{T500}}, {{T510}}, {{T510i}}, {{T520}}<br />
* {{W500}}, {{W510}}, {{W520}}, {{W700}}, {{W700ds}}, {{W701}}, {{W701ds}}<br />
* {{X301}}<br />
<br />
==Port Replicators and Docks featuring this technology==<br />
Note, some have multiple Displayports<br />
* [[ThinkPad Mini Dock Series 3]]<br />
* [[ThinkPad Mini Dock Plus Series 3 - 170W]]<br />
* [[ThinkPad Mini Dock Plus Series 3 - 135W]]<br />
* [[ThinkPad Mini Dock Plus Series 3 - 90W]]<br />
* [[X200 UltraBase]]<br />
* [[W700 Mini Dock]]<br />
* [[W700 Mini Dock 2.0]]<br />
<br />
== DVI Pass-through ==<br />
<br />
Certain ThinkPad models have a DisplayPort connection which offers DVI pass-through.<br />
<br />
Check [http://www-307.ibm.com/pc/support/site.wss/MIGR-72148.html ThinkPad Digital Video Interface (DVI) and DVI Pass-Through] for more information, and to see if a specific model and configuration is supported.<br />
<br />
== Audio Support ==<br />
<br />
There are reports that DisplayPort on some (possibly all) current thinkpads does not support audio. While there are adapters to convert DisplayPort to HDMI, the lack of audio makes it impossible to, for example, watch a DVD or Blu-Ray on an HDTV using the DisplayPort. [http://forums.lenovo.com/t5/W-Series-ThinkPad-Laptops/Displayport-to-HDMI-with-audio/td-p/68575 See this thread for more information]<br />
<br />
Audio over DisplayPort when used in conjunction with a DisplayPort to HDMI conversion cable is [http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T410-T510-DisplayPort-features-audio/td-p/191530/page/3 confirmed] to work on W500, T410 and T510 both on integrated and discrete graphics options on Windows systems.<br />
<br />
=== T410s ===<br />
<br />
The T410s supports audio pass-through via DisplayPort on recent Linux systems.<br />
<br />
With the Intel HD Audio modul selected recent linux kernels detect the DisplayPort<br />
audio as a separate output device:<br />
<br />
On 2.6.36-rc1 the following devices can be found in /proc/asound/*<br />
<br />
Codec: Intel IbexPeak HDMI<br />
Device: name="INTEL HDMI 0", type="HDMI", device=3<br />
Device: name="INTEL HDMI 1", type="HDMI", device=7<br />
<br />
If you want to pass Audio via DisplayPort you just have to switch to the Intel HDMI audio output device<br />
for the application in PulseAudio (didn't test with pure ALSA).<br />
<br />
=== W510 ===<br />
<br />
The more recent versions of the W510 with the Quadro FX 880M support audio and video out through DisplayPort. Tested with a DisplayPort to HDMI with Audio converter. Used alsa (no PulseAudio) and mplayer, 2.6.35-ARCH, using mplayer -afm hwdts,hwac3 -ao alsa:noblock:device=hw=1.7 and nvidia driver version 256.53. Had to unmute with alsamixer -c1<br />
<br />
== Problems ==<br />
<br />
=== Twinview using Displayport and DVI broken ===<br />
On my T410 mini-dock series 3, the displayport works unless I try to use it while using the DVI out as well.<br />
DVI+VGA works, but nvidia-settings dies horribly. Tried with 195.* and 260* drivers.<br />
<br />
I am using a displayport -> DVI adapter (displayport++ allows this).<br />
<br />
<b> FIX:</b><br />
Using Nouveau drivers instead of the nvidia binary blob allows my displayport to work in concert with the DVI out of my dock.<br />
This allows dual digital external displays. Attempting to activate the laptop monitor as well leads to problems.<br />
<br />
<b> ANOTHER FIX: </b><br />
Version 275* from the nvidia website allows me to use Displayport and DVI at the same time as well.<br />
<br />
== External Sources ==<br />
* [http://www-307.ibm.com/pc/support/site.wss/MIGR-72148.html ThinkPad Digital Video Interface (DVI) and DVI Pass-Through]<br />
* [http://www-307.ibm.com/pc/support/site.wss/MIGR-70321.html DisplayPort Monitor Cables - Overview]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=DisplayPort&diff=52827DisplayPort2011-08-19T13:03:16Z<p>Vrossum: /* Port Replicators and Docks featuring this technology */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
DisplayPort is a digital video connector, available on select ThinkPads<br />
<br />
</div><br />
|}<br />
<br />
* [[Wikipedia:DisplayPort| Wikipedia article on DisplayPort]]<br />
<br />
==ThinkPads featuring this technology==<br />
* {{L412}}, {{L512}}<br />
* {{R500}}<br />
* {{T400s}}, {{T410}}, {{T410i}}, {{T410s}}, {{T410si}}, {{T500}}, {{T510}}, {{T510i}}<br />
* {{W500}}, {{W510}}, {{W520}}, {{W700}}, {{W700ds}}, {{W701}}, {{W701ds}}<br />
* {{X301}}<br />
<br />
==Port Replicators and Docks featuring this technology==<br />
Note, some have multiple Displayports<br />
* [[ThinkPad Mini Dock Series 3]]<br />
* [[ThinkPad Mini Dock Plus Series 3 - 170W]]<br />
* [[ThinkPad Mini Dock Plus Series 3 - 135W]]<br />
* [[ThinkPad Mini Dock Plus Series 3 - 90W]]<br />
* [[X200 UltraBase]]<br />
* [[W700 Mini Dock]]<br />
* [[W700 Mini Dock 2.0]]<br />
<br />
== DVI Pass-through ==<br />
<br />
Certain ThinkPad models have a DisplayPort connection which offers DVI pass-through.<br />
<br />
Check [http://www-307.ibm.com/pc/support/site.wss/MIGR-72148.html ThinkPad Digital Video Interface (DVI) and DVI Pass-Through] for more information, and to see if a specific model and configuration is supported.<br />
<br />
== Audio Support ==<br />
<br />
There are reports that DisplayPort on some (possibly all) current thinkpads does not support audio. While there are adapters to convert DisplayPort to HDMI, the lack of audio makes it impossible to, for example, watch a DVD or Blu-Ray on an HDTV using the DisplayPort. [http://forums.lenovo.com/t5/W-Series-ThinkPad-Laptops/Displayport-to-HDMI-with-audio/td-p/68575 See this thread for more information]<br />
<br />
Audio over DisplayPort when used in conjunction with a DisplayPort to HDMI conversion cable is [http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T410-T510-DisplayPort-features-audio/td-p/191530/page/3 confirmed] to work on W500, T410 and T510 both on integrated and discrete graphics options on Windows systems.<br />
<br />
=== T410s ===<br />
<br />
The T410s supports audio pass-through via DisplayPort on recent Linux systems.<br />
<br />
With the Intel HD Audio modul selected recent linux kernels detect the DisplayPort<br />
audio as a separate output device:<br />
<br />
On 2.6.36-rc1 the following devices can be found in /proc/asound/*<br />
<br />
Codec: Intel IbexPeak HDMI<br />
Device: name="INTEL HDMI 0", type="HDMI", device=3<br />
Device: name="INTEL HDMI 1", type="HDMI", device=7<br />
<br />
If you want to pass Audio via DisplayPort you just have to switch to the Intel HDMI audio output device<br />
for the application in PulseAudio (didn't test with pure ALSA).<br />
<br />
=== W510 ===<br />
<br />
The more recent versions of the W510 with the Quadro FX 880M support audio and video out through DisplayPort. Tested with a DisplayPort to HDMI with Audio converter. Used alsa (no PulseAudio) and mplayer, 2.6.35-ARCH, using mplayer -afm hwdts,hwac3 -ao alsa:noblock:device=hw=1.7 and nvidia driver version 256.53. Had to unmute with alsamixer -c1<br />
<br />
== Problems ==<br />
<br />
=== Twinview using Displayport and DVI broken ===<br />
On my T410 mini-dock series 3, the displayport works unless I try to use it while using the DVI out as well.<br />
DVI+VGA works, but nvidia-settings dies horribly. Tried with 195.* and 260* drivers.<br />
<br />
I am using a displayport -> DVI adapter (displayport++ allows this).<br />
<br />
<b> FIX:</b><br />
Using Nouveau drivers instead of the nvidia binary blob allows my displayport to work in concert with the DVI out of my dock.<br />
This allows dual digital external displays. Attempting to activate the laptop monitor as well leads to problems.<br />
<br />
<b> ANOTHER FIX: </b><br />
Version 275* from the nvidia website allows me to use Displayport and DVI at the same time as well.<br />
<br />
== External Sources ==<br />
* [http://www-307.ibm.com/pc/support/site.wss/MIGR-72148.html ThinkPad Digital Video Interface (DVI) and DVI Pass-Through]<br />
* [http://www-307.ibm.com/pc/support/site.wss/MIGR-70321.html DisplayPort Monitor Cables - Overview]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Maximum_Resolutions&diff=50894Maximum Resolutions2011-03-07T11:29:13Z<p>Vrossum: </p>
<hr />
<div>=== Maximum resolution on external displays ===<br />
<br />
This page list the maximum resolution you can get on an external display.<br />
Annoyingly, the official information is known to be incorrect in some cases.<br />
Please update with your info.<br />
<br />
=== General remarks ===<br />
Output via the analog VGA port is always limited to 2048x1536.<br />
This is a rather square aspect ratio. On modern monitors 1920x1200 is more likely the maximum.<br />
<br />
Higher resolutions require either a dual link [[DVI]] or [[DisplayPort]] adaptor.<br />
In some cases these are present on the laptop, but more often they require docking station.<br />
<br />
=== Known configurations to work and not to work at 2560x1600 ===<br />
<br />
Works: <br />
<br />
T61p with Advanced Mini Dock</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Maximum_Resolutions&diff=50893Maximum Resolutions2011-03-07T11:20:23Z<p>Vrossum: </p>
<hr />
<div>=== Maximum resolution on external displays ===<br />
<br />
This page list the maximum resolution you can get on an external display.<br />
Annoyingly, the official information is known to be incorrect in some cases.<br />
Please update with your info.<br />
<br />
=== General remarks ===<br />
Output via the analog VGA port is always limited to 2048x1536.<br />
This is a rather square aspect ratio. On modern monitors 1900x1200 is more likely the maximum.<br />
<br />
Higher resolutions require either a dual link [[DVI]] or [[DisplayPort]] adaptor.<br />
In some cases these are present on the laptop, but more often they require docking station.<br />
<br />
=== Known configurations to work and not to work at 2560x1600 ===<br />
<br />
Works: <br />
<br />
T61p with Advanced Mini Dock</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Maximum_Resolutions&diff=50892Maximum Resolutions2011-03-07T11:14:43Z<p>Vrossum: â†Created page with '=== Maximum resolution on external displays === This page list the maximum resolution you can get on an external display. Annoyingly, the official information is known to...'</p>
<hr />
<div>=== Maximum resolution on external displays ===<br />
<br />
This page list the maximum resolution you can get on an external display.<br />
Annoyingly, the official information is known to be incorrect in some cases.<br />
Please update with your info.<br />
<br />
=== General remarks ===<br />
Output via the analog VGA port is always limited to 2048x1536.<br />
This is a rather square aspect ratio. On modern monitors 1900x1200 is more likely the maximum.<br />
<br />
Higher resolutions require either a dual link {{DVI}} or {{DisplayPort}} adaptor.<br />
<br />
=== Known configurations to</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Problem_with_hard_drive_clicking&diff=50383Problem with hard drive clicking2011-01-29T22:50:20Z<p>Vrossum: </p>
<hr />
<div>Many users have reported a '''problem with hard drive clicking''', sometimes described as a repeating '''tick tick tick''' type of ticking sound, or a '''faint beep''' at random intervals.<br />
<br />
The click sound is caused by the drive parking its head. There are multiple causes for that, including power management and shock detection (see below). It can also mean that your drive is about to DIE.<br />
Check /var/log/messages for suspicious errors and backup!<br />
<br />
The [[Hitachi Travelstar 5K80]] series, which shipped with many T series Thinkpads, is reported to suffer from this problem in particular. The clicks occur rapidly, and are quiet but noticeable. While in use in a quiet environment, the clicks can be relatively loud and annoying. The clicks seem to happen when the drive is idle and the power has been on for a significant period of time. The clicking is also reported on other vendors' laptop hard drives, and is therefore almost certainly hard drive related rather than laptop chassis related.<br />
<br />
The clicking sound appears to occur only when the drive is idle. Forcing the drive to be busy silences the ticking. Launching programs that access the hard drive, such as searching or defragmenting the drive, helps for a time. Cycling the power on the hard drive, such as through a full power-off reboot of the system, stops the ticking for the moment. <tt>hdparm</tt> can be used to reset the drive without rebooting, or to set the power management settings.<br />
<br />
Others recommend using Hitachi's drive feature tool to increase the acoustic management level.<br />
<br />
=== Possible cause and speculation ===<br />
<br />
Laptop drives (especially Hitachi [[Hitachi Travelstar 5K80]], [[Hitachi Travelstar 5K100]] and SAMSUNG MP0804H) can '''unload heads''' very often, producing a noticeable click. Some ThinkPad BIOSes can be very eager to program the HD Advanced Power Management feature (<tt>hdparm -B</tt>), even when told to always keep the HD in "Maximum Performance mode", and will do so every time AC state changes and when coming out of suspend (be it S3 or S4). Unless you reset the HD's APM mode, it will unload its heads eventually, thus producing the clicks.<br />
<br />
Another possible cause is the drive firmware running a low level '''surface media check''' periodically during idle time.<br />
<br />
It is not known whether the problem is a sign of impending drive failure. The root cause of the problem is not yet known. It is quite likely to be a normal mode of drive operation. The problem is very prevalent.<br />
<br />
Do not confuse this with regular activity. Many daemons poll (config) files every few seconds. Despite files being cached, POSIX compliant filesystems like ext2 or ext3 must update (= write) the last access time. More details and a workaround in [[How to reduce power consumption#Hard_Drives]].<br />
<br />
=== Tracking down the cause of the clicks ===<br />
<br />
Using "'''<tt>smartctl -A</tt>'''" (part of the the <tt>[http://sourceforge.net/apps/trac/smartmontools/wiki smartmontools]</tt> package), it is possible to check if any of the drive's attributes related to platter spin-up/down or head unload are increasing when a click is heard. That can help pinpointing the cause of the clicks.<br />
<br />
A shell script like this may help:<br />
<br />
<pre>#!/bin/bash<br />
lastval=0<br />
while :<br />
do<br />
newval=`smartctl -A /dev/sda | awk '$2=="Load_Cycle_Count" {print $10}'`<br />
if [[ $newval != $lastval ]] # i.e., anything has changed (here: load cycle count only)<br />
then<br />
date<br />
echo $newval<br />
fi<br />
lastval=$newval<br />
sleep 30 # or some other interval<br />
done<br />
</pre><br />
<br />
=== Possible solutions (Linux) ===<br />
<br />
The clicking noise apparently occurs when the drive is parking its heads (and ramping them off the drive surface in the process) after a timeout after the last disk access. Temporary relief has been found by using '''<tt>hdparm</tt>''' to turn off power management for the drive:<br />
<br />
: {{cmdroot|hdparm -B 255 /dev/sda}}<br />
<br />
That should stop the drive from parking the heads except when turning off. You can also try<br />
<br />
: {{cmdroot|hdparm -B 254 /dev/sda}}<br />
<br />
which doesn't turn power management off, but is the least aggressive setting: it will still unload heads, but far less often. (The drives ''are'' prepared to withstand a great number of head unloads: 200,000 unloads are typical, and Hitachi drives tolerate about 600,000 unloads.)<br />
<br />
To make these changes permanent, you have to ensure that the <tt>-B</tt> commands are reissued at every boot, after resuming from disk or RAM, after hotswapping, and ''every time the ThinkPad BIOS might try to override them''. This is done in two steps: changing the default settings when the system boots, and changing the settings when the system resumes after the lid is closed and re-opened.<br />
<br />
==== Start-up settings ====<br />
<br />
On Debian, edit <tt>/etc/hdparm.conf</tt> (as root):<br />
<br />
: {{cmdroot|vi /etc/hdparm.conf}}<br />
<br />
Add the following lines:<br />
<br />
# Change sda to hda if it's a PATA drive<br />
/dev/sda {<br />
apm = 255<br />
}<br />
<br />
Then, to refresh the settings, run<br />
<br />
: {{cmdroot|update-rc.d hdparm defaults}}<br />
<br />
On [http://wiki.archlinux.org/index.php/Laptop#Hard_drive_spin_down_problem Arch Linux], edit <tt>/etc/rc.local</tt> instead and add:<br />
<br />
hdparm -B 254 /dev/sda<br />
<br />
Then reboot the system, and the clicking noise should be gone.<br />
<br />
==== Wake-up settings ====<br />
<br />
The clicking may resume when the lid is closed and re-opened. To fix this, create an executable file named <tt>50_hdparm-pm</tt> in <tt>/etc/pm/sleep.d</tt>:<br />
<br />
: {{cmdroot|vi /etc/pm/sleep.d/50_hdparm-pm}}<br />
<br />
With the following content:<br />
<br />
#!/bin/sh<br />
if [ -n "$1" ] && ([ "$1" = "resume" ] || [ "$1" = "thaw" ]); then<br />
hdparm -B 255 /dev/your-hard-drive > /dev/null<br />
fi<br />
<br />
To make it executable, run:<br />
<br />
: {{cmdroot|chmod +x /etc/pm/sleep.d/50_hdparm-pm}}<br />
<br />
If this does not help, but manually setting <tt>hdparm -B 255 /dev/sda</tt> does, try the script below instead:<br />
<br />
#!/bin/sh<br />
. "${PM_FUNCTIONS}"<br />
case "$1" in<br />
thaw|resume)<br />
sleep 2<br />
hdparm -B 255 /dev/sda<br />
;;<br />
*)<br />
;;<br />
esac<br />
exit $NA<br />
<br />
On [https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695 Ubuntu] 8.10 (Linux Mint 6) on a T42, there seems to be something else setting a lower value in battery mode, which might be coming from the BIOS because it clicks during boot and stops with this in place. Make an executable file named "<tt>99-hdd-spin-fix.sh</tt>" (the important thing is it's starting with "<tt>99</tt>"), containing the following:<br />
<br />
#!/bin/sh<br />
# Use a less aggressive hard disk power management to get rid of<br />
# clicking noise when the drive is parking its heads<br />
hdparm -B 255 /dev/sda<br />
<br />
Then, copy this file to <tt>/etc/acpi/suspend.d/</tt>, <tt>/etc/acpi/resume.d/</tt> and <tt>/etc/acpi/start.d/</tt>. Remember to make the files executable (<tt>chmod +x</tt>).<br />
<br />
The problem seems to be solved on Ubuntu 10.04.<br />
<br />
Otherwise, try to reset the drive with <tt>-w</tt>, but note that this may cause data loss, according to <tt>hdparm</tt>'s man page. When used in the following way to stop the clicking, I have not seen any data loss. YMMV.<br />
<br />
# hdparm /dev/sda<br />
# sync<br />
# sleep 5<br />
# sync<br />
# hdparm -w /dev/sda<br />
<br />
Yet another solution is to install the <tt>laptop-mode-tools</tt> package and edit <tt>/etc/laptop-mode/laptop-mode.conf</tt>, setting <tt>CONTROL_HD_POWERMGMT=1</tt> and ensuring that <tt>hdparm</tt> sets <tt>-B 255</tt>.<br />
<br />
=== Possible solution (Windows) ===<br />
<br />
On a X41T, do BIOS, firmware and IBM updates. Then simply disable the ShockProtection of the hard drive. On a native X41T Windows installation, it solved the problem; one will hear a click only every hour. It seems that the problem is related to an aggressive setting that will try to park the head often to protect the drive, so the problem is not related with power management settings. Perhaps a similar approach also works under Linux. &ndash; WBonX (Hitachi drive)<br />
<br />
=== Specific models ===<br />
<br />
==== Hitachi C4K60 (HTC426060G9AT00) ====<br />
<br />
On a Thinkpad X41 with a has a 60 GB Hitachi C4K60 (HTC426060G9AT00) hard disk that had the clicking problem (even in Windows), the <tt>hdparm</tt> solution above did not work. The problem was indeed caused by the hard disk unloading the heads when idle, and the <tt>Load_Cycle_Count</tt> SMART statistic could be seen increasing when the clicks occurred.<br />
<br />
<tt>hdparm -B</tt> settings did not seem to help, and a check of the hard drive's specs (available in [http://www.hitachigst.com/tech/techlib.nsf/products/Travelstar_C4K60 hitachigst.com]) verified that setting the APM mode off (<tt>hdparm -B 255</tt>) would set it actually to the lowest APM mode (the same as <tt>hdparm -B 254</tt>). In this drive, even the lowest APM mode unloads the heads very aggressively, causing the clicking sounds. Another problem is that the drive is rated only for 600,000 unload/load cycles, which means that the drive will break in at most a couple of years.<br />
<br />
{{NOTE|This observation is only about the specific model (Hitachi C4K60), and is not true for more recent Hitachi drives, which do disable APM with <tt>-B 255</tt>.}}<br />
<br />
==== Samsung MP0804H 80GB ====<br />
<br />
On this drive, the clicking noise can be immediately stopped just by enabling ''automatic offline tests'' using<br />
<br />
: {{cmdroot|smartctl -o on /dev/hda}}<br />
<br />
Even more strange is that SMART wasn't enabled by default, although the drive supports it.<br />
<br />
The drive had already performed 15,539 load cycles (out of 600,000) within only one week.<br />
<br />
Note that enabling SMART (<tt>-s</tt> on) without enabling offline tests &ndash; which is what I did immediately after observing the clicks &ndash; did not solve the problem, but made it quite clear that the drive was badly in need of some care.<br />
<br />
==== Seagate Momentus 7200.1 and 7200.3 ====<br />
<br />
Reported in X61t and X61 (I have a ST9320421AS).<br />
<br />
On these drives, each click does indeed correspond to an increase in SMART attribute 193, "<tt>193 Load_Cycle_Count</tt>", as you can see by doing a<br />
<br />
: {{cmdroot|smartctl -A /dev/sda}}<br />
<br />
before and after a click.<br />
<br />
It seems like the problem is that the default powersaving mode for the drive is one which causes clicking. In fact, executing<br />
<br />
: {{cmdroot|hdparm -B 255 /dev/sda}}<br />
<br />
which is supposed to turn off power management, actually leaves power management ''on'', and is equivalent to<br />
<br />
: {{cmdroot|hdparm -B 128 /dev/sda}}<br />
<br />
as can be seen by comparing the results of<br />
<br />
# hdparm -B 1 /dev/sda; hdparm -I /dev/sda | grep Advanced<br />
# hdparm -B 128 /dev/sda; hdparm -I /dev/sda | grep Advanced<br />
# hdparm -B 254 /dev/sda; hdparm -I /dev/sda | grep Advanced<br />
# hdparm -B 255 /dev/sda; hdparm -I /dev/sda | grep Advanced<br />
<br />
This may or may not be related to something else strange; the drive reports that the advanced power management level is 0x8000 more than what you set it to, presumably leading <tt>hdparm</tt> to report that it is always set to "unknown setting" (since the number should be between 1 and 255). FYI, the results of the above sequence of commands are:<br />
<br />
{{cmdroot|hdparm -B 1 /dev/sda; hdparm -I /dev/sda | grep Advanced}}<br />
<br />
/dev/sda:<br />
setting Advanced Power Management level to 0x01 (1)<br />
Advanced power management level: unknown setting (0x8001)<br />
* Advanced Power Management feature set<br />
<br />
{{cmdroot|hdparm -B 128 /dev/sda; hdparm -I /dev/sda | grep Advanced}}<br />
<br />
/dev/sda:<br />
setting Advanced Power Management level to 0x80 (128)<br />
Advanced power management level: unknown setting (0x8080)<br />
* Advanced Power Management feature set<br />
<br />
{{cmdroot|hdparm -B 254 /dev/sda; hdparm -I /dev/sda | grep Advanced}}<br />
<br />
/dev/sda:<br />
setting Advanced Power Management level to 0xfe (254)<br />
Advanced power management level: unknown setting (0x80fe)<br />
* Advanced Power Management feature set<br />
<br />
{{cmdroot|hdparm -B 255 /dev/sda; hdparm -I /dev/sda | grep Advanced}}<br />
<br />
/dev/sda:<br />
setting Advanced Power Management level to disabled<br />
Advanced power management level: unknown setting (0x8080)<br />
Advanced Power Management feature set<br />
<br />
The workaround seems to be to execute<br />
<br />
: {{cmdroot|hdparm -B 254 /dev/sda}}<br />
<br />
So it seems like the drive is interpreting "<tt>hdparm -B 255 /dev/sda</tt>", which I'm guessing is the default (and which is supposed to be ''not'' powersaving mode) as a request to go into powersaving mode, which causes it to spin down a lot and to and click. And I'm guessing that "<tt>hdparm -B 254 /dev/sda</tt>" actually takes it out of powersaving mode.<br />
<br />
Somewhat annoying, because<br />
<br />
: {{cmdroot|smartctl -A /dev/sda}}<br />
<br />
shows that I have already accumulated a <tt>Load_Cycle_Count</tt> 106680 after owning the laptop for just a few weeks! I'm not sure that I understand this stuff, but if this corresponds to "Load/Unload Cycles" in http://www.seagate.com/docs/pdf/datasheet/disc/ds_momentus7200.pdf, then that's more than 1/6 of the drive's lifetime!<br />
<br />
I can confirm that after having my drive for about 5 days now, the 193 cycle count is already at 3000, and it's steadily increasing. That is really annoying. Unfortunately, changing the powersave mode on my drive (ST9320421AS) only breaks my hibernate capability (the laptop resumes immediately), but it won't stop the clicking; instead it will increase it.<br />
<br />
===== Firmware upgrade =====<br />
<br />
While no firmware update was found direct from IBM/Lenovo, Dell support offers a firmware update for a nearly-identical Seagate drive model. In at least in two cases (model T500, 7200.3; model Z61m 7200.3), the firmware update eliminated the clicking issue. Details available from this <s>[http://forums.seagate.com/stx/board/message?board.id=ata_drives&thread.id=2677&view=by_date_ascending&page=2 Seagate Thread]</s> [http://forums.seagate.com/t5/Momentus-XT-Momentus-and/CLICKING-NOISE-ISSUE-on-Momentus-7200-3-ST9320421AS-320GB/m-p/12498#M78 Seagate Thread] (version that works, maybe they have restructured their forum) or [http://www.thinkwiki.org/wiki/Talk:Problem_with_hard_drive_clicking here] (for ST9160411ASG).<br />
<br />
==== [http://sdd.toshiba.com/main.aspx?Path=HardDrivesOpticalDrives/2.5-inchHardDiskDrives/MK2035GSS/MK2035GSSSpecifications Toshiba MK2035GSS] ====<br />
<br />
The issue happens with "laptop mode" disabled. BIOS is an "AMIBIOS 8.00.14", and the chipset is "Mobile Intel GM965 Express".<br />
<br />
I can solve the problem with the <tt>hdparm</tt> workaround. The lowest value that makes the trick for me is:<br />
<br />
: {{cmdroot|sudo hdparm -B 192 /dev/sda}}<br />
<br />
=== Firmware upgrades ===<br />
<br />
There are two HD firmware upgrades on Lenovo's support website. One is specific to X41's, and will upgrade Hitachi's to Release A0L0 (document [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67238 MIGR-67238], 2007/01/24). The upgrade comes in three forms: diskette, Windows executable and ISO CD-ROM image. IBM's latest posted firmware, A5DA, does not appear to solve the problem.<br />
<br />
A newer upgrade set ([http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-62282 MIGR-62282], 2007/05/02) updates HD firmwares of several brands, including Hitachi. The patch upgrades firmware for HTC4260xxG9AT00 to A0L2 (according to program output, from 00P3A0B5 to 00P3A0L2). The upgrade comes in a large (20 MB) ISO format, or as several diskettes. There is seemingly no Windows executable; upgrading a diskless machine can therefore be problematic (it involves making a DOS-based USB bootable drive).<br />
<br />
The upgrade caused one X41 Tablet HTC426060G9AT00 drive to stop clicking.<br />
<br />
=== Another possible solution ===<br />
<br />
IBM, when notified about this occurrence, may replace the drive with a Fujitsu 5k 80GB hard drive, as to them the sound is indicative of a potential hard drive failure.<br />
<br />
=== Data recovery service ===<br />
<br />
In many cases, a software solution would not solve a problem with a clicking hard drive caused by a defective head disk assembly (HDA) or a firmware issue. Consider using an expert data recovery service such as [http://www.WeRecoverData.com WeRecoverData.com].<br />
<br />
== External links ==<br />
<br />
* Ubuntu reported bugs: [https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695 59695], [https://bugs.launchpad.net/ubuntu/+bug/104535 104535]<br />
* [http://wiki.archlinux.org/index.php/Laptop#Hard_drive_spin_down_problem ArchWiki: Hard drive spin down problem]<br />
* [http://www.hitachigst.com/hdd/support/download.htm Hitachi Global Storage Technologies Downloads] &ndash; the drive feature tool may help with this problem<br />
* [http://forum.thinkpads.com/viewtopic.php?t=7462 Thread on thinkpads.com]<br />
* [http://notebookforums.com/showthread.php?t=46058 Thread on notebookforums.com]<br />
* [http://forums.silentpcreview.com/viewtopic.php?p=143203 Thread on silentpcreview.com]<br />
* [http://forum.thinkpads.com/viewtopic.php?t=15769 Another Thread on thinkpads.com]<br />
* [http://www.tabletpcbuzz.com/forum/topic.asp?TOPIC_ID=28538&whichpage=1 Thread on tabletpcbuzz.com]<br />
* [http://thinkpad-forum.de/forum/viewtopic.php?t=2255 German Thread on thinkpad-forum.de (Containing an interesting remark about a possible problem with the Cache)]<br />
* [http://www.werecoverdata.com WeRecoverData.com]<br />
<br />
[[Category:T40]]<br />
[[Category:T41]]<br />
[[Category:T42]]<br />
[[Category:T43]]<br />
[[Category:T61]]<br />
[[Category:T61p]]<br />
[[Category:X41]]<br />
[[Category:G41]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Intel_Core_2_Duo_(Merom)&diff=50382Intel Core 2 Duo (Merom)2011-01-29T21:58:30Z<p>Vrossum: /* Standard Voltage */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
<br />
The Intel 2 Core is the successor of the [[Intel Core Duo (Yonah)]] processor. Unlike the Yonah, the Merom was designed specifically with mobile applications in mind. The Merom introduced various architectural additions such as EM64T, [[SIMD|SSSE3]] and improved the performance by up to 25 percent. The 667 MHz FSB versions are part of the "Napa" platform, while the 800MHz FSB versions are part of the "Santa Rosa" platform. The chip is also part of the hardware from both the Centrino Duo and Centrino Pro brands. The follow-on to Merom is [[Intel_Core_2_Duo_(Penryn)|Penryn]]<br />
<br />
=Features=<br />
*Dual Core<br />
*EM64T<br />
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_Virtualization_Technology_.28Intel_VT.29 Intel Virtualization Technology ]<br />
*XD-Bit<br />
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]], [[SIMD|SSSE3]] instruction sets<br />
*667 or 800 MHz FSB<br />
*65 nm fabrication process<br />
*4 MB or 2 MB L2-Cache with dynamic cache sizing<br />
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), [[QuickStart and Deeper Sleep|Deeper Sleep]] (C4)<br />
</div><br />
|}<br />
<br />
=Available Types and ThinkPads featuring them=<br />
==Standard Voltage==<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Name || sSpec || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models<br />
|- style="background:#ffdead;"<br />
! !! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !! <br />
|-<br />
| T7800 || || 2600 || 1000 || 4MB || 800 || yes || 1.30 || 0.85-0.9 || 35 || ? || {{T61p}}<br />
|-<br />
| T7700 || || 2400 || 1000 || 4MB || 800 || yes || 1.30 || 0.85-0.9 || 35 || ? || {{R61}}, {{T61}}, {{T61p}}<br />
|-<br />
| T7600 || SL9SD || 2333 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}}, {{T60p}}<br />
|-<br />
| T7500 || || 2200 || 1000 || 4MB || 800 || yes || 1.30 || 0.85-0.9 || 35 || ? || {{R61}}, {{T61}}, {{X61}}<br />
|-<br />
| T7400 || SL9SE || 2166 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}}, {{T60p}}, {{Z61t}}<br />
|-<br />
| T7300 || || 2000 || 800 || 4MB || 800 || yes || 1.30 || 0.85-0.9 || 35 || ? || {{R61}}, {{T61}}, {{X61}}<br />
|-<br />
| T7200 || SL9SF || 2000 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61m}}, {{Z61t}}<br />
|-<br />
| T7100 || || 1800 || 1000 || 2MB || 800 || yes || ? || 0.85-0.9 || 35 || ? || {{R61}}, {{T61}}, {{X61}}<br />
|-<br />
| T5870 || || 2000 || ? || 2MB || 800 || yes || ? || ? || 35 || ? || {{R500}}, {{SL300}}, {{SL400}}, {{SL400c}}, {{SL410}}, {{SL500}}, {{SL500c}}, {{SL510}}<br />
|-<br />
| T5750 || || 2000 || ? || 2MB || 667 || no || 1.30 || 1.0375 || 35 || ? || {{R61i}}<br />
|-<br />
| T5670 || || 1800 || 800 || 2MB || 800 || yes || 1.30 || 0.95 || 35 || ? || {{SL300}}, {{SL400}}, {{SL500}}, {{R500}}<br />
|-<br />
| T5600 || || 1833 || 1000 || 2MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61t}}<br />
|-<br />
| T5550 || || 1833 || ? || 2MB || 667 || no || 1.30 || 1.0375 || 35 || ? || {{R61i}}<br />
|-<br />
| T5500 || || 1667 || 1000 || 2MB || 667 || no || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61m}}, {{Z61t}}<br />
|-<br />
| T5450 || || 1667 || ? || 2MB || 667 || no || 1.30 || 1.0375 || 35 || ? || {{R61i}}<br />
|-<br />
| T5250 || || 1500 || ? || 2MB || 667 || no || 1.30 || 1.0375 || 35 || ? || {{R61i}}<br />
|}<br />
<br />
==Low Voltage==<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models<br />
|- style="background:#ffdead;"<br />
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !! <br />
|-<br />
| L7400 || 1500 || 1000 || 4MB || 667 || yes || 1.2 || 0.85 - 0.9 || 17 || ? || {{X60s}}, {{X60_Tablet}}<br />
|-<br />
| L7500 || 1600 || 800 || 4MB || 800 || yes || 1.1 || 0.85 - 0.9 || 17 || ? || {{X61s}}, {{X61_Tablet}}<br />
|-<br />
| L7700 || 1800 || 800 || 4MB || 800 || yes || 1.1 || 0.85 - 0.9 || 17 || ? || {{X61s}}, {{X61_Tablet}}<br />
|-<br />
| SL7100 || 1200 || 800 || 4MB || 800 || yes || 1.1 || 0.85 - 0.9 || 12 || ? || {{X300}}<br />
|}<br />
<br />
As you can see, the Low-Voltage CPU's work at the same Voltage as the normal CPUs when running in SLFM. With a simple tool (RMClock) you can use those lower voltages at every clock.<br />
Intel gave other voltage-regions for the CPUs:<br />
<br />
''the standard processor that works on a core voltage between 1.075V and 1.175V, the low voltage processors that work between 0.975V and 1.062V and finally the ultra low voltage processors that work between 0.80V and 0.975V.''<br />
<br />
Intel doesn't think of the SLFM. With SLFM and a little bit luck, you're T-CPU can be thriftier than a LV-CPU but has more power.<br />
With RMClock every T-CPU is thriftier than a LV-CPU, because you have the same voltage but a higher max-clock, so the sleep-states can be longer.<br />
<br />
=Thermal Specifications=<br />
The maximum temperature for safe operation is 100°C.<br />
<br />
The catastrophic thermal protection temperature is 125°C.<br />
<br />
Idle temperature is typically around 30-50°C.<br />
<br />
Temperature at full utilisation is around 60-70°C.<br />
<br />
These latter two values will of course depend largely on cooling systems and available airflow.<br />
<br />
=Compiler optimisation flags=<br />
==GCC==<br />
In addition to the architecture independent <code>-O[0123s]</code> option hierarchy, architecture dependent optimisations are controlled by the <code>-march=<cpu-type></code> and <code>-mtune=<cpu-type></code> options. The <cpu-type> argument (not surprisingly) describes the type of cpu for which to optimise the compiled code. The <code>-mtune</code> option will generate code that is optimised for the given cpu type which will nevertheless run on cpu types other than the optimisation target. On the other hand, <code>-march</code> will attempt to optimise more aggressively at the expense of reducing portability to other cpu types. Optimisations implied by <code>-mtune</code> are a subset of <code>-march</code> optimisations, and thus it is only necessary to specify <code>-march</code> if the the maximum level of optimisation is desired.<br />
<br />
With version of gcc before 4.3, 32-bit code should be compiled with the "prescott" as the cpu-type argument to <code>-march</code> or <code>-mtune</code> whereas 64-bit code should use the "nocona" argument. Gcc 4.3 however introduces "core2" as a valid argument to the <code>-mtune</code> and <code>-march</code> options which should be used. Alternatively, as of gcc 4.2, the "native" argument is supported. This will automatically determine the cpu-type on which compilation is taking place and apply optimisations specific to that cpu.<br />
<br />
==Intel==<br />
For the [http://www.spec.org/cpu2006/ SPEC CPU 2006 benchmarks], Intel used the shorthand <code>-fast</code>, which translates into <code>-O3 -ipo -static -no-prec-div -xP</code>. However, the compiler also provides the flag <code>-xT</code>, which activates the optimization for Core 2 Duo and SSSE3 (instead of SSE3 only with <code>-xP</code>).<br />
<br />
=Microcode=<br />
Much like software products, bugs, errata or ways to improve upon operation are often found in CPU's after they have reached the market. In some cases, the necessary changes can be applied by the end user without any change to the underlying hardware in the form of microcode updates downloadable from the manufacturer. Intel offers these microcode updates for download on their [http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=2676&DwnldID=14303&lang=eng website]. <br />
<br />
Provided the availability of the <tt>microcode</tt> and <tt>firmware</tt> kernel modules (which are enabled in the stock kernels of most distributions) and a suitable user space tool such as [http://urbanmyth.org/microcode/ microcode_ctl], one can install the updated microcode into their processors at runtime. The microcode update is volatile however, meaning that it disappears upon reboot. While this reduces the risk of applying such an update to essentially 0, it does mean that it must be applied on each boot.<br />
==Debian==<br />
You can install the microcode.ctl package which will take care of everything (including downloading the microcode itself) for you. Just run<br />
{{cmdroot|aptitude install microcode.ctl}}. This package includes an init script which will run at boot to load the microcode into the processor. This script also contains a line which will remove the <tt>microcode</tt> kernel module once the operation is complete and it is no longer needed, however it is strangely commented out by default. If you want to keep your loaded modules (used memory) to a minimum, you can edit {{path|/etc/init.d/microcode.ctl}} and uncomment the line<br />
<pre><br />
[ -x /sbin/modprobe ] && /sbin/modprobe -r microcode > /dev/null 2> /dev/null<br />
</pre><br />
==Gentoo==<br />
The <tt>microcode-ctl</tt> utility can be installed as follows: {{cmdroot|emerge microcode-ctl}}. This will create an init script <tt>/etc/init.d/microcode_ctl</tt>, but will not automatically set it to run on startup; to do so, run {{cmdroot|rc-update add microcode_ctl boot}}. Also, this will install an old copy of the microcode to <tt>/etc/microcode.dat</tt>; to update it, download a new copy from the link above and replace this file.<br />
<br />
=Note on Hyper-Threading=<br />
Note that as opposed to Pentium 4/NetBurst, current Core 2 do not support hyper-threading, and therefore there is usually no option in the BIOS to activate it. Refer to Intel's [http://www.intel.com/products/ht/hyperthreading_more.htm Hyper-Threading Technology] for a list of hyper-threading capable CPU.<br />
<br />
=See also=<br />
*[[Intel Core Solo (Yonah)]]<br />
*[[Intel Core Duo (Yonah)]]<br />
*[[Intel Core 2 Duo (Penryn)]]<br />
<br />
== External Links ==<br />
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]<br />
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]<br />
<br />
[[Category:Components]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Full_Disk_Encryption_(FDE)&diff=49699Full Disk Encryption (FDE)2010-10-04T08:18:45Z<p>Vrossum: /* Disadvantages */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== Full Disk Encryption ===<br />
Lenovo's 'Full Disk Encryption' (FDE) is a technology incorporated into some of Seagate's FDE-ready hard disks. It provides encryption of all of the contents of the hard disk.<br />
<br />
<br />
=== Features ===<br />
* Multi platform (Linux, Windows).<br />
* Protects the whole disk (including FAT partition...)<br />
* No performance impact.<br />
* Compatible with TPM<br />
* AES (the chip which performs AES encryption has been [http://www.seagate.com/ww/v/index.jsp?locale=en-US&name=null&vgnextoid=ade81f7095904110VgnVCM100000f5ee0a0aRCRD certified] by [http://csrc.nist.gov/cryptval/aes/aesval.html NIST] )<br />
* Wiping the disk (for disposal...) takes just a second.<br />
<br />
<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:momentus5400_3_fde_sm_106x106.gif|FDE Hard disk Photo, credits: seagate.com]]<br />
|}<br />
<br />
=== Using Seagate FDE ===<br />
Using FDE as as easy as setting up the hard disk password (from BIOS). You can choose to have just a user password, or both a user and a master password.<br />
You can export the key to an external storage, for password recovery (you need the password !!)<br />
<br />
N.B.: The [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-69621 Lenovo FAQ on FDE] specifically states that on the T60 & T61, there is no means of backing up or exporting the key, but that the drive may be used in another system (it is evidently not tied to a motherboard [http://en.wikipedia.org/wiki/Full_disk_encryption#Full_disk_encryption_and_Trusted_Platform_Module Trusted Platform Module]).<br />
<br />
==== Lost password ====<br />
Three possibilities :<br />
* Use the master password to change the user key.<br />
* Recover the password using the previously exported key. (See note from Lenovo FAQ, above.)<br />
* Reset the encryption key (which causes the hard disk to be instantly "wiped", and resets the "hard disk password").<br />
<br />
==== Wipe the disk ====<br />
Wiping the disk is as easy as reseting the encryption key from the BIOS..<br />
<br />
==== TPM ====<br />
It should be possible to use TPM (with fingerprint readers...) not tested yet.<br />
* T61 with TPM & fingerprints, FDE password works with a configured fingerprint but you must use windows based software to program the imprint. By keeping a small windows partition, I am able to boot linux with a fingerprint, fingerprint passes the TPM power-on password AND the FDE disk 1 password, which is separate.<br />
<br />
==== Disadvantages ====<br />
FDE is only safe when the computer is off or hibernated.<br />
When the computer is stolen while it is on or suspended, a restart which boots from a USB stick will reveal your data.<br />
The problem is that these warm restarts will not ask for the HD password, nor the power-on-password for that matter.<br />
This can be seen as a security risk.<br />
<br />
Dm-crypt solutions are better in this respect as they will prompt for a password on any reboot.<br />
<br />
Another disadvantage is that the disk can not be read if it is put in a USB enclosure.<br />
Again, dm-crypt does allow to mount encrypted partitions from a USB disk (password protected, of course), which is useful when upgrading disks, or when using disks across computers.<br />
<br />
=== Software alternatives ===<br />
<br />
It is possible to get similar security, at a very slight performance impact, by using appropriate software-based full disk encryption solutions. For example, under Linux, you can use <tt>dm-crypt</tt> to encrypt the whole disk (including swap and root partitions) except for a bootloader. Numerous tutorials are available on the Internet.<br />
<br />
=== Links ===<br />
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-69621 Lenovo Full Disk Encryption Hard Disk Drive Frequently Asked Questions]<br />
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=TPAD-SIMS Thinkpad Bios simulator] (R61/T61 not available yet, unfortunately)<br />
* [http://www.seagate.com/www/en-us/products/laptops/momentus/momentus_5400_fde.2/ Seagate MoMentuS 5400 FDe.2]<br />
* [http://en.wikipedia.org/wiki/Full_disk_encryption Wikipedia - Full disk encryption] (why FDE ??)<br />
* [http://www.xml-dev.com/pipermail/fde/ Full-Disk-Encryption Mailing list]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Full_Disk_Encryption_(FDE)&diff=49698Full Disk Encryption (FDE)2010-10-04T08:18:27Z<p>Vrossum: /* Disadvantages */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== Full Disk Encryption ===<br />
Lenovo's 'Full Disk Encryption' (FDE) is a technology incorporated into some of Seagate's FDE-ready hard disks. It provides encryption of all of the contents of the hard disk.<br />
<br />
<br />
=== Features ===<br />
* Multi platform (Linux, Windows).<br />
* Protects the whole disk (including FAT partition...)<br />
* No performance impact.<br />
* Compatible with TPM<br />
* AES (the chip which performs AES encryption has been [http://www.seagate.com/ww/v/index.jsp?locale=en-US&name=null&vgnextoid=ade81f7095904110VgnVCM100000f5ee0a0aRCRD certified] by [http://csrc.nist.gov/cryptval/aes/aesval.html NIST] )<br />
* Wiping the disk (for disposal...) takes just a second.<br />
<br />
<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:momentus5400_3_fde_sm_106x106.gif|FDE Hard disk Photo, credits: seagate.com]]<br />
|}<br />
<br />
=== Using Seagate FDE ===<br />
Using FDE as as easy as setting up the hard disk password (from BIOS). You can choose to have just a user password, or both a user and a master password.<br />
You can export the key to an external storage, for password recovery (you need the password !!)<br />
<br />
N.B.: The [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-69621 Lenovo FAQ on FDE] specifically states that on the T60 & T61, there is no means of backing up or exporting the key, but that the drive may be used in another system (it is evidently not tied to a motherboard [http://en.wikipedia.org/wiki/Full_disk_encryption#Full_disk_encryption_and_Trusted_Platform_Module Trusted Platform Module]).<br />
<br />
==== Lost password ====<br />
Three possibilities :<br />
* Use the master password to change the user key.<br />
* Recover the password using the previously exported key. (See note from Lenovo FAQ, above.)<br />
* Reset the encryption key (which causes the hard disk to be instantly "wiped", and resets the "hard disk password").<br />
<br />
==== Wipe the disk ====<br />
Wiping the disk is as easy as reseting the encryption key from the BIOS..<br />
<br />
==== TPM ====<br />
It should be possible to use TPM (with fingerprint readers...) not tested yet.<br />
* T61 with TPM & fingerprints, FDE password works with a configured fingerprint but you must use windows based software to program the imprint. By keeping a small windows partition, I am able to boot linux with a fingerprint, fingerprint passes the TPM power-on password AND the FDE disk 1 password, which is separate.<br />
<br />
==== Disadvantages ====<br />
FDE is only safe when the computer is off or hibernated.<br />
When the computer is stolen while it is on or suspended, a restart which boots from a USB stick will reveal your data.<br />
The problem is that these warm restarts will not ask for the HD password, nor the power-on-password for that matter.<br />
This can be seen as a security risk.<br />
<br />
Dm-crypt solutions are better in this respect as they will prompt for a password on any reboot.<br />
<br />
Another disadvantage is that the disk can not be read if it is put in a USB enclosure.<br />
Again, dm-crypt does allow to mount encrypted partitions from a USB disk (password protected, of course), which is useful when upgrading disks.<br />
<br />
=== Software alternatives ===<br />
<br />
It is possible to get similar security, at a very slight performance impact, by using appropriate software-based full disk encryption solutions. For example, under Linux, you can use <tt>dm-crypt</tt> to encrypt the whole disk (including swap and root partitions) except for a bootloader. Numerous tutorials are available on the Internet.<br />
<br />
=== Links ===<br />
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-69621 Lenovo Full Disk Encryption Hard Disk Drive Frequently Asked Questions]<br />
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=TPAD-SIMS Thinkpad Bios simulator] (R61/T61 not available yet, unfortunately)<br />
* [http://www.seagate.com/www/en-us/products/laptops/momentus/momentus_5400_fde.2/ Seagate MoMentuS 5400 FDe.2]<br />
* [http://en.wikipedia.org/wiki/Full_disk_encryption Wikipedia - Full disk encryption] (why FDE ??)<br />
* [http://www.xml-dev.com/pipermail/fde/ Full-Disk-Encryption Mailing list]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Full_Disk_Encryption_(FDE)&diff=49640Full Disk Encryption (FDE)2010-09-22T09:48:51Z<p>Vrossum: /* Disadvantages */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== Full Disk Encryption ===<br />
Lenovo's 'Full Disk Encryption' (FDE) is a technology incorporated into some of Seagate's FDE-ready hard disks. It provides encryption of all of the contents of the hard disk.<br />
<br />
<br />
=== Features ===<br />
* Multi platform (Linux, Windows).<br />
* Protects the whole disk (including FAT partition...)<br />
* No performance impact.<br />
* Compatible with TPM<br />
* AES (the chip which performs AES encryption has been [http://www.seagate.com/ww/v/index.jsp?locale=en-US&name=null&vgnextoid=ade81f7095904110VgnVCM100000f5ee0a0aRCRD certified] by [http://csrc.nist.gov/cryptval/aes/aesval.html NIST] )<br />
* Wiping the disk (for disposal...) takes just a second.<br />
<br />
<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:momentus5400_3_fde_sm_106x106.gif|FDE Hard disk Photo, credits: seagate.com]]<br />
|}<br />
<br />
=== Using Seagate FDE ===<br />
Using FDE as as easy as setting up the hard disk password (from BIOS). You can choose to have just a user password, or both a user and a master password.<br />
You can export the key to an external storage, for password recovery (you need the password !!)<br />
<br />
N.B.: The [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-69621 Lenovo FAQ on FDE] specifically states that on the T60 & T61, there is no means of backing up or exporting the key, but that the drive may be used in another system (it is evidently not tied to a motherboard [http://en.wikipedia.org/wiki/Full_disk_encryption#Full_disk_encryption_and_Trusted_Platform_Module Trusted Platform Module]).<br />
<br />
==== Lost password ====<br />
Three possibilities :<br />
* Use the master password to change the user key.<br />
* Recover the password using the previously exported key. (See note from Lenovo FAQ, above.)<br />
* Reset the encryption key (which causes the hard disk to be instantly "wiped", and resets the "hard disk password").<br />
<br />
==== Wipe the disk ====<br />
Wiping the disk is as easy as reseting the encryption key from the BIOS..<br />
<br />
==== TPM ====<br />
It should be possible to use TPM (with fingerprint readers...) not tested yet.<br />
* T61 with TPM & fingerprints, FDE password works with a configured fingerprint but you must use windows based software to program the imprint. By keeping a small windows partition, I am able to boot linux with a fingerprint, fingerprint passes the TPM power-on password AND the FDE disk 1 password, which is separate.<br />
<br />
==== Disadvantages ====<br />
FDE is only safe when the computer is off or hibernated.<br />
When the computer is stolen while it is on or suspended, a restart which boots from a USB stick will reveal your data.<br />
The problem is that these warm restarts will not ask for the HD password, nor the power-on-password for that matter.<br />
This can be seen as a security risk.<br />
<br />
dm-crypt solutions are better in this respect as they will prompt for a password on the reboot.<br />
<br />
Another disadvantage is that the disk can not be read if it is put in a USB enclosure.<br />
Again, dm-crypt does allow to mount encrypted partitions from a USB disk (password protected, of course), which is useful when upgrading disks.<br />
<br />
=== Software alternatives ===<br />
<br />
It is possible to get similar security, at a very slight performance impact, by using appropriate software-based full disk encryption solutions. For example, under Linux, you can use <tt>dm-crypt</tt> to encrypt the whole disk (including swap and root partitions) except for a bootloader. Numerous tutorials are available on the Internet.<br />
<br />
=== Links ===<br />
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-69621 Lenovo Full Disk Encryption Hard Disk Drive Frequently Asked Questions]<br />
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=TPAD-SIMS Thinkpad Bios simulator] (R61/T61 not available yet, unfortunately)<br />
* [http://www.seagate.com/www/en-us/products/laptops/momentus/momentus_5400_fde.2/ Seagate MoMentuS 5400 FDe.2]<br />
* [http://en.wikipedia.org/wiki/Full_disk_encryption Wikipedia - Full disk encryption] (why FDE ??)<br />
* [http://www.xml-dev.com/pipermail/fde/ Full-Disk-Encryption Mailing list]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Full_Disk_Encryption_(FDE)&diff=49639Full Disk Encryption (FDE)2010-09-21T21:50:58Z<p>Vrossum: /* added section on disadvangages */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== Full Disk Encryption ===<br />
Lenovo's 'Full Disk Encryption' (FDE) is a technology incorporated into some of Seagate's FDE-ready hard disks. It provides encryption of all of the contents of the hard disk.<br />
<br />
<br />
=== Features ===<br />
* Multi platform (Linux, Windows).<br />
* Protects the whole disk (including FAT partition...)<br />
* No performance impact.<br />
* Compatible with TPM<br />
* AES (the chip which performs AES encryption has been [http://www.seagate.com/ww/v/index.jsp?locale=en-US&name=null&vgnextoid=ade81f7095904110VgnVCM100000f5ee0a0aRCRD certified] by [http://csrc.nist.gov/cryptval/aes/aesval.html NIST] )<br />
* Wiping the disk (for disposal...) takes just a second.<br />
<br />
<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:momentus5400_3_fde_sm_106x106.gif|FDE Hard disk Photo, credits: seagate.com]]<br />
|}<br />
<br />
=== Using Seagate FDE ===<br />
Using FDE as as easy as setting up the hard disk password (from BIOS). You can choose to have just a user password, or both a user and a master password.<br />
You can export the key to an external storage, for password recovery (you need the password !!)<br />
<br />
N.B.: The [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-69621 Lenovo FAQ on FDE] specifically states that on the T60 & T61, there is no means of backing up or exporting the key, but that the drive may be used in another system (it is evidently not tied to a motherboard [http://en.wikipedia.org/wiki/Full_disk_encryption#Full_disk_encryption_and_Trusted_Platform_Module Trusted Platform Module]).<br />
<br />
==== Lost password ====<br />
Three possibilities :<br />
* Use the master password to change the user key.<br />
* Recover the password using the previously exported key. (See note from Lenovo FAQ, above.)<br />
* Reset the encryption key (which causes the hard disk to be instantly "wiped", and resets the "hard disk password").<br />
<br />
==== Wipe the disk ====<br />
Wiping the disk is as easy as reseting the encryption key from the BIOS..<br />
<br />
==== TPM ====<br />
It should be possible to use TPM (with fingerprint readers...) not tested yet.<br />
* T61 with TPM & fingerprints, FDE password works with a configured fingerprint but you must use windows based software to program the imprint. By keeping a small windows partition, I am able to boot linux with a fingerprint, fingerprint passes the TPM power-on password AND the FDE disk 1 password, which is separate.<br />
<br />
==== Disadvantages ====<br />
FDE is only safe when the computer is off or hibernated.<br />
When the computer is stolen while it is on or suspended, a restart which boots from a USB stick will reveal your data.<br />
The problem is that these warm restarts will not ask for the HD password, nor the power-on-password for that matter.<br />
This can be seen as a security risk.<br />
<br />
dm-crypt solutions are better in this respect as they will prompt for a password on the reboot.<br />
<br />
=== Software alternatives ===<br />
<br />
It is possible to get similar security, at a very slight performance impact, by using appropriate software-based full disk encryption solutions. For example, under Linux, you can use <tt>dm-crypt</tt> to encrypt the whole disk (including swap and root partitions) except for a bootloader. Numerous tutorials are available on the Internet.<br />
<br />
=== Links ===<br />
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-69621 Lenovo Full Disk Encryption Hard Disk Drive Frequently Asked Questions]<br />
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=TPAD-SIMS Thinkpad Bios simulator] (R61/T61 not available yet, unfortunately)<br />
* [http://www.seagate.com/www/en-us/products/laptops/momentus/momentus_5400_fde.2/ Seagate MoMentuS 5400 FDe.2]<br />
* [http://en.wikipedia.org/wiki/Full_disk_encryption Wikipedia - Full disk encryption] (why FDE ??)<br />
* [http://www.xml-dev.com/pipermail/fde/ Full-Disk-Encryption Mailing list]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Using_16V_powersupplies_for_new_20_V_laptops&diff=43617Using 16V powersupplies for new 20 V laptops2009-07-07T22:07:25Z<p>Vrossum: â†Created page with 'If you are using a 20V IBM/LEnovo laptop (T60 series for example) and your powersupply is broken, don't worry. Your computer will run and charge batteries using old 16V p...'</p>
<hr />
<div>If you are using a 20V IBM/LEnovo laptop (T60 series for example) and your powersupply is broken,<br />
don't worry.<br />
<br />
Your computer will run and charge batteries using old 16V powersupplies.<br />
Of course the plug is not compatible, but you can fix that easily.</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Hardware_Modifications&diff=43616Hardware Modifications2009-07-07T22:05:00Z<p>Vrossum: /* Hardware hacks */</p>
<hr />
<div>This page is dedicated to your Hardware modifications and stories about strange or clever uses of ThinkPads.<br />
<br />
==Hardware hacks==<br />
* [[Harddrive Upgrade|Upgrade your hard drive]]<br />
* [[CPU upgrade]]<br />
* [[How to build your own UltraBay drive]]<br />
* [[How to build your own UltraBay Plus device]]<br />
* [[How to build your own UltraPort device]]<br />
* [[How to build a T43 southbridge cooler]]<br />
* [[Unofficial maximum memory specs]]<br />
* [[Compact Flash boot drive]]<br />
* [[Installing a QXGA display in a R/T60 or 61]]<br />
* [[Using 16V powersupplies for new 20 V laptops]]<br />
<br />
==Undocumented software control of hardware==<br />
*[[Pentium M undervolting and underclocking]]<br />
*[[How to control fan speed]]<br />
<br />
==External Sources==<br />
*[http://www.stud.uni-hannover.de/~przemy/en_ibm760xd.html ThinkPad 760XD do-it-yourself-page]<br />
*[http://repair4laptop.org/disassembly_ibm.html How to Upgrade, Repair, Disassemble a Lenovo (former IBM) ThinkPad Laptop or Notebook] - links to illustrated (often) HOWTOs for old and new ThinkPad models.<br />
*[http://members.at.infoseek.co.jp/monkung/tp_cup/tp_cup.htm ThinkPad overclocking by photo for different older models (japanese)]<br />
*[http://www.ibmmania.com/submenu3-tp.htm IBM Mania's Application pages] <tt>(Korean, but with pictures)</tt><br />
*[http://forum.thinkpads.com/viewtopic.php?t=20958 T43p Embedded Controller Internals]<br />
*[http://linuxfocus.org/~guido/gentoo-tpt43p/cooling/ Enhancing cooling for the T43/p]<br />
*[http://forum.thinkpads.com/viewtopic.php?t=69539 Hardware fix for the T43/p fan noise]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Problem_with_display_remaining_black_after_resume&diff=42157Problem with display remaining black after resume2009-03-16T12:54:00Z<p>Vrossum: /* Solution for nvidia-drivers-180* series */</p>
<hr />
<div>There has been a problem encountered where the display stays black on resuming from suspend.<br />
<br />
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}}.<br />
<br />
==Affected Models==<br />
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T60p}}, {{T61p}}<br />
*Thinkpad {{T23}}<br />
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}<br />
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}, {{R60}}, {{R61}}<br />
*ThinkPad {{A30p}}<br />
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)<br />
*ThinkPad {{Z60t}}, {{Z60m}}, {{Z61m}}, {{Z61e}}<br />
*ThinkPad {{X60s}}, {{X60}}, {{X61}}, {{X61s}}, {{X200}}<br />
<br />
==Affected Operating Systems==<br />
*Linux (it's a kernel issue)<br />
*FreeBSD (6.x at least)<br />
<br />
==Solutions==<br />
===Quick workaround for R61i, T23, maybe others===<br />
Try pressing CTRL+ALT+F1 to switch to text console. The backlight should come on normally. Press CTRL+ALT+F7 to return to X.<br />
<br />
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.<br />
<br />
===Quick Workaround for R61 (at least 8918-5QG) using NVidia===<br />
<br />
Use Vesa driver instead of the proprietary NVidia driver.<br />
<br />
===Pseudo-solution for R61===<br />
On an R61 running Fedora Core 9, the nv driver fails to turn the backlight on after resuming from a suspend to RAM. I fixed this by using the proprietary NVIDIA Linux drivers (v177.82).<br />
<br />
=== Solution for ThinkPad Z60t ===<br />
<br />
* '''Display controller:''' Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)<br />
* '''Distro:''' Fedora release 7 (Moonshine)<br />
* '''Kernel:''' Linux 2.6.22.5-76.fc7<br />
<br />
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:<br />
<br />
echo DISPLAY_QUIRK_S3_BIOS=\"true\" >> /etc/pm/config.d/config<br />
<br />
===Semi-Solution for ThinkPad X60 with damaged system after s2ram usage===<br />
It happend when restarting a s2ram-session.<br />
<br />
'''Symptom:''' Black screen with blinking "_" sign remaind. (without the ")<br />
<br />
'''System status:''' HDD idle, fan running, everything else looks to wait for something to happen.<br />
<br />
'''Semi-Solution:''' Booting with DVD-ROM and going through the installations menu,<br />
where you choose "other" and "boot a installed system" (something like that). Gladly it works,<br />
and OpenSuSE 10.1 comes up with 50% "failed" messages! I than shutdown properly, rebooted again<br />
and had 100% "done" again, with no other things affected.<br />
<br />
'''Further:''' Repairing with the DVD-ROM crashed massivly(!), so I selected "boot a installed system" as final<br />
solution and it worked!<br />
<br />
'''Unknown:''' Maybe the Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM will help,<br />
because X60s and X60 are very familiar. (Not tested so far.)<br />
<br />
(If this Problem is not right here, please edit and move.)<br />
<br />
===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===<br />
see [[1400x1050 on Intel 915GM]].<br />
===Solution for ThinkPads with ATI graphic chips and Intel 915/945GM ===<br />
<br />
Affected models include {{X60s}}, {{X200s}}, {{R60}} and {{T60}}.<br />
<br />
This soluton also applies to T42 with Intel 855 and ATI 9600 M10.<br />
<br />
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.<br />
<br />
For grub this would look like this:<br />
<br />
title Linux, kernel 2.6.11-1-686<br />
root (hd0,0)<br />
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios<br />
initrd /boot/initrd.img-2.6.11-1-686<br />
savedefault<br />
boot<br />
<br />
For lilo it would look like this:<br />
<br />
image=/boot/vmlinuz<br />
append="acpi_sleep=s3_bios"<br />
<br />
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:<br />
<br />
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}}.<br />
<br />
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. <br />
<br />
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].<br />
<br />
{{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.}}<br />
<br />
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}}).<br />
<br />
<br />
----<br />
<br />
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.<br />
<br />
Working config:<br />
Linux 2.6.21.5<br />
fglrx 8.37.6<br />
debian etch:<br />
powersaved 0.14.0-5:<br />
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core"<br />
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core" <br />
hibernate:<br />
SwitchToTextMode yes<br />
lilo.conf:<br />
vga=0<br />
<br />
"EnableVbetool yes" and other suggestions didn't work for me.<br />
<br />
For suspend-to-disk, don't load fglrx in initrd.<br />
<br />
----<br />
<br />
On '''T60-20076RG''' (Core2Duo 2GHz, ATI X1400) with {{OpenSUSE}} 11.1 and fglrx 8-12 the following had to be done to get suspend to RAM always resume:<br />
* Add {{bootparm|S2RAM_QUIRKS_SOURCE|"s2ram"}} to file {{path|/etc/pm/config.d/config}}<br />
* Create an executable script {{path|/etc/pm/sleep.d/00text}} containing:<br />
#!/bin/bash<br />
<br />
case "$1" in<br />
hibernate|suspend)<br />
/bin/chvt 1<br />
;;<br />
thaw|resume)<br />
/bin/chvt 7<br />
;;<br />
esac<br />
<br />
There seems to be a bug ([https://bugzilla.novell.com/show_bug.cgi?id=463434 Novell bugzilla]) which makes it impossible for s2ram to switch to text console while suspending through pm-suspend. The script above forces console change. Along with setting s2ram as quirks source (which makes it correctly set acpi_bios before suspend - to s3_bios,s3_mode<br />
for T60 2007*) this can make resume work flawlessly despite using vesafb.<br />
<br />
===Solution for ThinkPads with Intel Extreme Graphics 2===<br />
{{NOTE|<br />
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.}}<br />
<br />
The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.<br />
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.<br />
*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.<br />
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.<br />
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.<br />
*For Debian Etch 4.0 on R50e just make following changes to /etc/default/acpi-support:<br />
#SAVE_VBE_STATE=true<br />
#VBESTATE=/var/lib/acpi-support/vbestate<br />
#POST_VIDEO=true<br />
SAVE_VIDEO_PCI_STATE=true<br />
<br />
*For a R50e the only thing needed to make suspend to ram work in Ubuntu 6.06 is adding<br />
Option "VBERestore" "yes"<br />
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}, and the example script below.<br />
<br />
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.<br />
<br />
#!/bin/bash<br />
<br />
# change to console 1<br />
FGCONSOLE=`fgconsole`<br />
chvt 6<br />
<br />
# safe video state<br />
cat /proc/bus/pci/00/02.0 > /tmp/video_state<br />
<br />
# sync filesystem<br />
sync<br />
<br />
# sync hardware clock with system time<br />
hwclock --systohc<br />
<br />
# go to sleep<br />
echo -n 3 > /proc/acpi/sleep<br />
<br />
# waking up<br />
# restore system clock<br />
hwclock --hctosys<br />
<br />
# restore video state<br />
cat /tmp/video_state > /proc/bus/pci/00/02.0<br />
<br />
# change back to X<br />
chvt $FGCONSOLE<br />
<br />
# clean up behind us<br />
rm /tmp/video_state<br />
<br />
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:<br />
<br />
SAVE_VBE_STATE=false<br />
POST_VIDEO=false<br />
SAVE_VIDEO_PCI_STATE=true<br />
USE_DPMS=false<br />
DOUBLE_CONSOLE_SWITCH=false<br />
<br />
===Solution for ThinkPads with Intel I830 Chipset===<br />
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.<br />
*this works with vesafb and also with intelfb frambuffer support.<br />
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.<br />
<br />
#!/bin/bash<br />
<br />
FGCONSOLE=`fgconsole`<br />
chvt 8<br />
sync<br />
hwclock --systohc<br />
<br />
echo -n "mem" > /sys/power/state<br />
<br />
hwclock --hctosys<br />
vbetool post<br />
<br />
if [ "$FGCONSOLE" -ge "7" ] ; then<br />
chvt $FGCONSOLE<br />
else<br />
chvt 7<br />
chvt $FGCONSOLE<br />
fi<br />
===Solution for ThinkPads with ATI graphic (and possibly other) chips and FreeBSD===<br />
<br />
The FreeBSD acpi(4) manpage mentions a tunable parameter, "hw.acpi.reset_video":<br />
<br />
hw.acpi.reset_video<br />
Reset the video adapter from real mode during the resume path.<br />
Some systems need this help, others have display problems if it<br />
is enabled. Default is 0 (disabled).<br />
<br />
This tunable can be set by adding the following line to your FreeBSD machine's /boot/loader.conf file:<br />
<br />
hw.acpi.reset_video="1"<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
{{footnotes|<br />
#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]].<br />
}}<br />
<br />
===Solution using s2ram for Intel 915/945GM===<br />
<br />
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. Best idea seems to be to put this into the corresponding acpi script:<br />
<br />
% cat /etc/acpi/sleep.sh <br />
#!/bin/sh<br />
test -f /usr/share/acpi-support/power-funcs || exit 0<br />
test -f /usr/sbin/s2ram || exit 0<br />
rmmod usb_storage<br />
rmmod uhci_hcd<br />
rmmod ehci_hcd<br />
/usr/sbin/s2ram -f -a 1 -m<br />
modprobe uhci_hcd<br />
modprobe ehci_hcd<br />
modprobe usb_storage<br />
<br />
Source: [http://d.hatena.ne.jp/conceal-rs/20080309/1205083315 http://d.hatena.ne.jp/conceal-rs/20080309/1205083315]<br />
Works on my X61.<br />
<br />
===Solution using DOUBLE_CONSOLE_SWITCH===<br />
<br />
By setting the following in {{path|/etc/default/acpi-support}} the display comes back on {{X61s}} using Intel chipset:<br />
<br />
DOUBLE_CONSOLE_SWITCH=true<br />
<br />
Fedora 8 doesn't have DOUBLE_CONSOLE_SWITCH, but it works when one does: First, add option "VBERestore" "true" to /etc/X11/xorg.conf<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "intel"<br />
Option "VBERestore" "true" <br />
EndSection<br />
<br />
Then suspends with<br />
<br />
pm-suspend --quirk-vbemode-restore --quirk-s3-bios<br />
<br />
===Solution for nvidia-drivers-180* series===<br />
<br />
The proprietary NVidia drivers of the 180 series introduce several problems with suspend to ram:<br />
<br />
* Situation 1: Suspend from console, '''no''' X-Server running:<br/><br />
You need to use vbetool to save and restore the vbestate.<br />
When using hibernate-script, this can be done by setting the following config variables:<br />
EnableVbetool yes<br />
RestoreVbeStateFrom /var/lib/vbetool/vbestate<br />
VbetoolPost yes<br />
<br />
You may need to run <code>mkdir -p /var/lib/vbetool && vbetool vbestate save > /var/lib/vbetool/vbestate</code> first.<br />
<br />
* Situation 2: Suspend from running X-Server:<br/><br />
You '''cannot''' use vbetool or any other quirks, since it seems to confuse the nvidia X driver. That means you should enter S3 simply by doing <code>echo mem > /sys/power/state</code>.<br />
<br />
If you have your hotkeys handled by acpid, you might differentiate those two cases by checking for a running X process in your hotkey handler (i.e. <code>/etc/acpid/default.sh</code>):<br />
pgrep -x X > /dev/null \ # checks for running process with name "X"<br />
&& echo mem > /sys/power/state # if found, do plain S3 suspend<br />
|| hibernate-ram # otherwise, run quirked script<br />
<br />
Furthermore, it seems to be a good idea to use the 180 series with a 2.6.28* kernel.<br />
<br />
It has been reported that acpi_sleep=S3_bios should be used instead of acpi_sleep=S3_mode<br />
as a boot option.<br />
<br />
See, http://www.nvnews.net/vbulletin/showthread.php?t=123303&highlight=suspend&page=6<br />
<br />
<br />
It might also help to put <code>blacklist intel_agp </code><br />
in <code>/etc/modprobe.d/blacklist<br />
<br />
Finally, it seems to depend on precise model nr.<br />
See<br />
https://bugs.launchpad.net/ubuntu/+bug/235284<br />
for a discussion and patch.</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Problem_with_display_remaining_black_after_resume&diff=40871Problem with display remaining black after resume2009-01-26T15:10:37Z<p>Vrossum: /* Solution for nvidia-drivers-180* series */</p>
<hr />
<div>There has been a problem encountered where the display stays black on resuming from suspend.<br />
<br />
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}}.<br />
<br />
==Affected Models==<br />
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T60p}}, {{T61p}}<br />
*Thinkpad {{T23}}<br />
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}<br />
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}, {{R60}}, {{R61}}<br />
*ThinkPad {{A30p}}<br />
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)<br />
*ThinkPad {{Z60t}}, {{Z60m}}, {{Z61m}}, {{Z61e}}<br />
*ThinkPad {{X60s}}, {{X60}}, {{X61}}, {{X61s}}, {{X200}}<br />
<br />
==Affected Operating Systems==<br />
*Linux (it's a kernel issue)<br />
*FreeBSD (6.x at least)<br />
<br />
==Solutions==<br />
===Quick workaround for R61i, T23, maybe others===<br />
Try pressing CTRL+ALT+F1 to switch to text console. The backlight should come on normally. Press CTRL+ALT+F7 to return to X.<br />
<br />
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.<br />
<br />
===Quick Workaround for R61 (at least 8918-5QG) using NVidia===<br />
<br />
Use Vesa driver instead of the proprietary NVidia driver.<br />
<br />
===Pseudo-solution for R61===<br />
On an R61 running Fedora Core 9, the nv driver fails to turn the backlight on after resuming from a suspend to RAM. I fixed this by using the proprietary NVIDIA Linux drivers (v177.82).<br />
<br />
=== Solution for ThinkPad Z60t ===<br />
<br />
* '''Display controller:''' Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)<br />
* '''Distro:''' Fedora release 7 (Moonshine)<br />
* '''Kernel:''' Linux 2.6.22.5-76.fc7<br />
<br />
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:<br />
<br />
echo DISPLAY_QUIRK_S3_BIOS=\"true\" >> /etc/pm/config.d/config<br />
<br />
===Semi-Solution for ThinkPad X60 with damaged system after s2ram usage===<br />
It happend when restarting a s2ram-session.<br />
<br />
'''Symptom:''' Black screen with blinking "_" sign remaind. (without the ")<br />
<br />
'''System status:''' HDD idle, fan running, everything else looks to wait for something to happen.<br />
<br />
'''Semi-Solution:''' Booting with DVD-ROM and going through the installations menu,<br />
where you choose "other" and "boot a installed system" (something like that). Gladly it works,<br />
and OpenSuSE 10.1 comes up with 50% "failed" messages! I than shutdown properly, rebooted again<br />
and had 100% "done" again, with no other things affected.<br />
<br />
'''Further:''' Repairing with the DVD-ROM crashed massivly(!), so I selected "boot a installed system" as final<br />
solution and it worked!<br />
<br />
'''Unknown:''' Maybe the Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM will help,<br />
because X60s and X60 are very familiar. (Not tested so far.)<br />
<br />
(If this Problem is not right here, please edit and move.)<br />
<br />
===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===<br />
see [[1400x1050 on Intel 915GM]].<br />
===Solution for ThinkPads with ATI graphic chips and Intel 915/945GM ===<br />
<br />
Affected models include {{X60s}}, {{X200s}}, {{R60}} and {{T60}}.<br />
<br />
This soluton also applies to T42 with Intel 855 and ATI 9600 M10.<br />
<br />
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.<br />
<br />
For grub this would look like this:<br />
<br />
title Linux, kernel 2.6.11-1-686<br />
root (hd0,0)<br />
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios<br />
initrd /boot/initrd.img-2.6.11-1-686<br />
savedefault<br />
boot<br />
<br />
For lilo it would look like this:<br />
<br />
image=/boot/vmlinuz<br />
append="acpi_sleep=s3_bios"<br />
<br />
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:<br />
<br />
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}}.<br />
<br />
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. <br />
<br />
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].<br />
<br />
{{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.}}<br />
<br />
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}}).<br />
<br />
<br />
----<br />
<br />
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.<br />
<br />
Working config:<br />
Linux 2.6.21.5<br />
fglrx 8.37.6<br />
debian etch:<br />
powersaved 0.14.0-5:<br />
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core"<br />
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core" <br />
hibernate:<br />
SwitchToTextMode yes<br />
lilo.conf:<br />
vga=0<br />
<br />
"EnableVbetool yes" and other suggestions didn't work for me.<br />
<br />
For suspend-to-disk, don't load fglrx in initrd.<br />
<br />
----<br />
<br />
On '''T60-20076RG''' (Core2Duo 2GHz, ATI X1400) with {{OpenSUSE}} 11.1 and fglrx 8-12 the following had to be done to get suspend to RAM always resume:<br />
* Add {{bootparm|S2RAM_QUIRKS_SOURCE|"s2ram"}} to file {{path|/etc/pm/config.d/config}}<br />
* Create an executable script {{path|/etc/pm/sleep.d/00text}} containing:<br />
#!/bin/bash<br />
<br />
case "$1" in<br />
hibernate|suspend)<br />
/bin/chvt 1<br />
;;<br />
thaw|resume)<br />
/bin/chvt 7<br />
;;<br />
esac<br />
<br />
There seems to be a bug ([https://bugzilla.novell.com/show_bug.cgi?id=463434 Novell bugzilla]) which makes it impossible for s2ram to switch to text console while suspending through pm-suspend. The script above forces console change. Along with setting s2ram as quirks source (which makes it correctly set acpi_bios before suspend - to s3_bios,s3_mode<br />
for T60 2007*) this can make resume work flawlessly despite using vesafb.<br />
<br />
===Solution for ThinkPads with Intel Extreme Graphics 2===<br />
{{NOTE|<br />
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.}}<br />
<br />
The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.<br />
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.<br />
*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.<br />
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.<br />
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.<br />
*For Debian Etch 4.0 on R50e just make following changes to /etc/default/acpi-support:<br />
#SAVE_VBE_STATE=true<br />
#VBESTATE=/var/lib/acpi-support/vbestate<br />
#POST_VIDEO=true<br />
SAVE_VIDEO_PCI_STATE=true<br />
<br />
*For a R50e the only thing needed to make suspend to ram work in Ubuntu 6.06 is adding<br />
Option "VBERestore" "yes"<br />
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}, and the example script below.<br />
<br />
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.<br />
<br />
#!/bin/bash<br />
<br />
# change to console 1<br />
FGCONSOLE=`fgconsole`<br />
chvt 6<br />
<br />
# safe video state<br />
cat /proc/bus/pci/00/02.0 > /tmp/video_state<br />
<br />
# sync filesystem<br />
sync<br />
<br />
# sync hardware clock with system time<br />
hwclock --systohc<br />
<br />
# go to sleep<br />
echo -n 3 > /proc/acpi/sleep<br />
<br />
# waking up<br />
# restore system clock<br />
hwclock --hctosys<br />
<br />
# restore video state<br />
cat /tmp/video_state > /proc/bus/pci/00/02.0<br />
<br />
# change back to X<br />
chvt $FGCONSOLE<br />
<br />
# clean up behind us<br />
rm /tmp/video_state<br />
<br />
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:<br />
<br />
SAVE_VBE_STATE=false<br />
POST_VIDEO=false<br />
SAVE_VIDEO_PCI_STATE=true<br />
USE_DPMS=false<br />
DOUBLE_CONSOLE_SWITCH=false<br />
<br />
===Solution for ThinkPads with Intel I830 Chipset===<br />
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.<br />
*this works with vesafb and also with intelfb frambuffer support.<br />
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.<br />
<br />
#!/bin/bash<br />
<br />
FGCONSOLE=`fgconsole`<br />
chvt 8<br />
sync<br />
hwclock --systohc<br />
<br />
echo -n "mem" > /sys/power/state<br />
<br />
hwclock --hctosys<br />
vbetool post<br />
<br />
if [ "$FGCONSOLE" -ge "7" ] ; then<br />
chvt $FGCONSOLE<br />
else<br />
chvt 7<br />
chvt $FGCONSOLE<br />
fi<br />
===Solution for ThinkPads with ATI graphic (and possibly other) chips and FreeBSD===<br />
<br />
The FreeBSD acpi(4) manpage mentions a tunable parameter, "hw.acpi.reset_video":<br />
<br />
hw.acpi.reset_video<br />
Reset the video adapter from real mode during the resume path.<br />
Some systems need this help, others have display problems if it<br />
is enabled. Default is 0 (disabled).<br />
<br />
This tunable can be set by adding the following line to your FreeBSD machine's /boot/loader.conf file:<br />
<br />
hw.acpi.reset_video="1"<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
{{footnotes|<br />
#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]].<br />
}}<br />
<br />
===Solution using s2ram for Intel 915/945GM===<br />
<br />
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. Best idea seems to be to put this into the corresponding acpi script:<br />
<br />
% cat /etc/acpi/sleep.sh <br />
#!/bin/sh<br />
test -f /usr/share/acpi-support/power-funcs || exit 0<br />
test -f /usr/sbin/s2ram || exit 0<br />
rmmod usb_storage<br />
rmmod uhci_hcd<br />
rmmod ehci_hcd<br />
/usr/sbin/s2ram -f -a 1 -m<br />
modprobe uhci_hcd<br />
modprobe ehci_hcd<br />
modprobe usb_storage<br />
<br />
Source: [http://d.hatena.ne.jp/conceal-rs/20080309/1205083315 http://d.hatena.ne.jp/conceal-rs/20080309/1205083315]<br />
Works on my X61.<br />
<br />
===Solution using DOUBLE_CONSOLE_SWITCH===<br />
<br />
By setting the following in {{path|/etc/default/acpi-support}} the display comes back on {{X61s}} using Intel chipset:<br />
<br />
DOUBLE_CONSOLE_SWITCH=true<br />
<br />
Fedora 8 doesn't have DOUBLE_CONSOLE_SWITCH, but it works when one does: First, add option "VBERestore" "true" to /etc/X11/xorg.conf<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "intel"<br />
Option "VBERestore" "true" <br />
EndSection<br />
<br />
Then suspends with<br />
<br />
pm-suspend --quirk-vbemode-restore --quirk-s3-bios<br />
<br />
===Solution for nvidia-drivers-180* series===<br />
<br />
The proprietary NVidia drivers of the 180 series introduce several problems with suspend to ram:<br />
<br />
* Situation 1: Suspend from console, '''no''' X-Server running:<br/><br />
You need to use vbetool to save and restore the vbestate.<br />
When using hibernate-script, this can be done by setting the following config variables:<br />
EnableVbetool yes<br />
RestoreVbeStateFrom /var/lib/vbetool/vbestate<br />
VbetoolPost yes<br />
<br />
You may need to run <code>mkdir -p /var/lib/vbetool && vbetool vbestate save > /var/lib/vbetool/vbestate</code> first.<br />
<br />
* Situation 2: Suspend from running X-Server:<br/><br />
You '''cannot''' use vbetool or any other quirks, since it seems to confuse the nvidia X driver. That means you should enter S3 simply by doing <code>echo mem > /sys/power/state</code>.<br />
<br />
If you have your hotkeys handled by acpid, you might differentiate those two cases by checking for a running X process in your hotkey handler (i.e. <code>/etc/acpid/default.sh</code>):<br />
pgrep -x X > /dev/null \ # checks for running process with name "X"<br />
&& echo mem > /sys/power/state # if found, do plain S3 suspend<br />
|| hibernate-ram # otherwise, run quirked script<br />
<br />
Furthermore, it seems to be a good idea to use the 180 series with a 2.6.28* kernel.<br />
<br />
It has been reported that acpi_sleep=S3_bios should be used instead of acpi_sleep=S3_mode<br />
as a boot option.<br />
<br />
See, http://www.nvnews.net/vbulletin/showthread.php?t=123303&highlight=suspend&page=6<br />
<br />
<br />
It might also help to put <code>blacklist intel_agp </code><br />
in <code>/etc/modprobe.d/blacklist</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=ThinkPad_X6_UltraBase&diff=40844ThinkPad X6 UltraBase2009-01-22T13:16:17Z<p>Vrossum: /* UltraBase X6 under Linux (newer style) */</p>
<hr />
<div>{| cellspacing="0" cellpadding="2" border="0"<br />
| style="vertical-align:top;" | __TOC__<br />
[[image:UltraBaseX6.gif|UltraBase X6]]<br />
| style="vertical-align:top;" | <div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
== Lenovo UltraBase X6 ==<br />
The IBM UltraBase X6 is a portable dock for the 6-series ThinkPads providing extra ports as well as a bay for an optical drive and a set of stereo speakers. Containing a full featured [[UltraBay|UltraBay Slim]] slot, it provides flexibility in drive choice as well as the option of a secondary battery for extended working time on the road.<br />
<br />
=== Features ===<br />
* Passthrough ports:<br />
** Ethernet (RJ45)<br />
** Modem (RJ11)<br />
** USB (four ports)<br />
** [[VGA Port|VGA]]<br />
** [[Serial Port|Serial (DB9-M)]]<br />
** [[Parallel Port|Parallel (DB25-F)]]<br />
** Microphone<br />
** Headphone<br />
* Ultrabay Slim<br />
* Stereo speakers<br />
* Kensington security hole<br />
<br />
===Pros & Cons===<br />
* Positives: Expansion capability, portable<br />
* Negatives: makes the ThinkPad quite thick<br />
* Compatibility: {{X60}}, {{X60s}}, {{X61}}, {{X61s}}<br />
* Warranty: Three Years<br />
</div><br />
|}<br />
<br />
==UltraBay Slim==<br />
The UltraBay Slim slot in this dock is a full featured one and supports hot swapping with all UltraBay Slim drives. You can also feed it with the UltraBay Slim battery pack to extend the overall battery life time.<br />
<br />
== UltraBase X6 under Linux (older style) ==<br />
The docking stations are (at least in openSUSE) supported by the [http://en.opensuse.org/Dockutils Dockutils] project. The dockutils are formed by a set of simple bash scripts that handle docking and undocking of the computer. When the user chooses to undock the laptop, it does some system calls and when properly configured, it could disconnect the DVD drive in UltraBase or internal display resolution.<br />
<br />
Overally, the UltraBase works pretty same way as under Windows (it only has more configuration possibilites), the user only needs to press key on the dock to undock the PC. Docking is handled automatically.<br />
<br />
The following code has been tested on {{OpenSUSE}} 10.3 (Linux 2.6.22) with ThinkPad X61 but should work on all dockable ThinkPads with recent kernel and the required software installed.<br />
<br />
=== Dockutils hook ===<br />
In order to have the docking handled automatically, we need to create a hook in Dockutils directory({{path|/usr/lib/dockutils}}). We will put our hook in {{path|hooks/thinkpad/}} directory.<br />
<br />
{{cmdroot|cat /usr/lib/dockutils/hooks/thinkpad/70x61}}<br />
<pre>#!/bin/bash<br />
# dock/undock script for Thinkpad X61<br />
<br />
export DISPLAY=:0<br />
<br />
if [ "$1" = "dock" ]; then<br />
echo "X61 dock"<br />
# non-present dvd drive workaround, not required in newer distros<br />
/bin/rescan-scsi-bus.sh --hosts=1 --channels=0 --ids=0 --luns=0 --forceremove &<br />
<br />
# set external display resolution & dpi<br />
/usr/bin/xrandr --output VGA --auto<br />
/usr/bin/xrandr --screen 0 -s 1920x1200<br />
/usr/bin/xrandr --screen 0 --dpi 96x96<br />
<br />
elif [ "$1" = "undock" ]; then<br />
echo "X61 undock"<br />
<br />
# turn external display off, internal on and set res<br />
/usr/bin/xrandr --screen 0 -s 1024x768<br />
/usr/bin/xrandr --output LVDS --auto<br />
/usr/bin/xrandr --output VGA --off<br />
/usr/bin/xrandr --screen 0 --dpi 96x96<br />
fi</pre><br />
{{NOTE|If you don't use external display, remove the <code>/usr/bin/xrandr</code> lines from the script}}<br />
The {{cmdroot|xhost +local:root}} command has to be in {{path|/etc/X11/xinit/xinitrc.d/<script name>}} to get <code>xrandr</code> working from the root account.<br />
<br />
=== ACPI event handlers ===<br />
You can always run the Dockutils using {{cmdroot|docker dock}} or {{cmdroot|docker undock}} command, but this is not comfortable. We will use the ACPI subsystem to bind {{key|Fn}}{{key|F8}}, {{key|Fn}}{{key|F9}} keys and blue button on the docking station to the Dockutils. This could be performed using the following code:<br />
<br />
{{cmdroot|cat /etc/acpi/events/dock}}<br />
<pre>event=(ibm/dock GDCK 00000000 00000003|ibm/hotkey HKEY 00000080 00001008)<br />
action=/usr/sbin/docker dock</pre><br />
and <br />
<br />
{{cmdroot|cat /etc/acpi/events/undock}}<br />
<pre>event=(ibm/dock GDCK 00000003 00000001|ibm/hotkey HKEY 00000080 00001009)<br />
action=/usr/sbin/docker undock</pre><br />
Now, you should be able to undock your PC using the keyboard keys and the dock button.<br />
{{NOTE|[[Thinkpad-acpi|thinkpad_acpi]] and <code>acpid</code> must be installed and running for this to work}}<br />
<br />
== UltraBase X6 under Linux (newer style) ==<br />
Since in recent distributions (like openSUSE 11.1), there is no generated ACPI event for undocking the notebook (Alt+F9 still works the same), you need to use udev in order to be able detect the undocking event. You can use the same ACPI hook as in the "older style" docking setting but you need to put this code into your udev rules:<br />
<br />
{{cmdroot|cat /etc/udev/rules.d/10-docking.rules}}<br />
<pre>ENV{EVENT}=="undock", KERNEL=="dock.0", SUBSYSTEM=="platform", RUN+="/usr/lib/dockutils/hooks/thinkpad/70x61 undock"<br />
ENV{EVENT}=="dock", KERNEL=="dock.0", SUBSYSTEM=="platform", RUN+="/usr/lib/dockutils/hooks/thinkpad/70x61 dock"</pre><br />
After this change, the notebook will change it's resolution automatically after you remove it from the UltraBase.</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=ThinkPad_X6_UltraBase&diff=40843ThinkPad X6 UltraBase2009-01-22T13:10:53Z<p>Vrossum: wrong file name 10-docking -> 10-docking.rules</p>
<hr />
<div>{| cellspacing="0" cellpadding="2" border="0"<br />
| style="vertical-align:top;" | __TOC__<br />
[[image:UltraBaseX6.gif|UltraBase X6]]<br />
| style="vertical-align:top;" | <div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
== Lenovo UltraBase X6 ==<br />
The IBM UltraBase X6 is a portable dock for the 6-series ThinkPads providing extra ports as well as a bay for an optical drive and a set of stereo speakers. Containing a full featured [[UltraBay|UltraBay Slim]] slot, it provides flexibility in drive choice as well as the option of a secondary battery for extended working time on the road.<br />
<br />
=== Features ===<br />
* Passthrough ports:<br />
** Ethernet (RJ45)<br />
** Modem (RJ11)<br />
** USB (four ports)<br />
** [[VGA Port|VGA]]<br />
** [[Serial Port|Serial (DB9-M)]]<br />
** [[Parallel Port|Parallel (DB25-F)]]<br />
** Microphone<br />
** Headphone<br />
* Ultrabay Slim<br />
* Stereo speakers<br />
* Kensington security hole<br />
<br />
===Pros & Cons===<br />
* Positives: Expansion capability, portable<br />
* Negatives: makes the ThinkPad quite thick<br />
* Compatibility: {{X60}}, {{X60s}}, {{X61}}, {{X61s}}<br />
* Warranty: Three Years<br />
</div><br />
|}<br />
<br />
==UltraBay Slim==<br />
The UltraBay Slim slot in this dock is a full featured one and supports hot swapping with all UltraBay Slim drives. You can also feed it with the UltraBay Slim battery pack to extend the overall battery life time.<br />
<br />
== UltraBase X6 under Linux (older style) ==<br />
The docking stations are (at least in openSUSE) supported by the [http://en.opensuse.org/Dockutils Dockutils] project. The dockutils are formed by a set of simple bash scripts that handle docking and undocking of the computer. When the user chooses to undock the laptop, it does some system calls and when properly configured, it could disconnect the DVD drive in UltraBase or internal display resolution.<br />
<br />
Overally, the UltraBase works pretty same way as under Windows (it only has more configuration possibilites), the user only needs to press key on the dock to undock the PC. Docking is handled automatically.<br />
<br />
The following code has been tested on {{OpenSUSE}} 10.3 (Linux 2.6.22) with ThinkPad X61 but should work on all dockable ThinkPads with recent kernel and the required software installed.<br />
<br />
=== Dockutils hook ===<br />
In order to have the docking handled automatically, we need to create a hook in Dockutils directory({{path|/usr/lib/dockutils}}). We will put our hook in {{path|hooks/thinkpad/}} directory.<br />
<br />
{{cmdroot|cat /usr/lib/dockutils/hooks/thinkpad/70x61}}<br />
<pre>#!/bin/bash<br />
# dock/undock script for Thinkpad X61<br />
<br />
export DISPLAY=:0<br />
<br />
if [ "$1" = "dock" ]; then<br />
echo "X61 dock"<br />
# non-present dvd drive workaround, not required in newer distros<br />
/bin/rescan-scsi-bus.sh --hosts=1 --channels=0 --ids=0 --luns=0 --forceremove &<br />
<br />
# set external display resolution & dpi<br />
/usr/bin/xrandr --output VGA --auto<br />
/usr/bin/xrandr --screen 0 -s 1920x1200<br />
/usr/bin/xrandr --screen 0 --dpi 96x96<br />
<br />
elif [ "$1" = "undock" ]; then<br />
echo "X61 undock"<br />
<br />
# turn external display off, internal on and set res<br />
/usr/bin/xrandr --screen 0 -s 1024x768<br />
/usr/bin/xrandr --output LVDS --auto<br />
/usr/bin/xrandr --output VGA --off<br />
/usr/bin/xrandr --screen 0 --dpi 96x96<br />
fi</pre><br />
{{NOTE|If you don't use external display, remove the <code>/usr/bin/xrandr</code> lines from the script}}<br />
The {{cmdroot|xhost +local:root}} command has to be in {{path|/etc/X11/xinit/xinitrc.d/<script name>}} to get <code>xrandr</code> working from the root account.<br />
<br />
=== ACPI event handlers ===<br />
You can always run the Dockutils using {{cmdroot|docker dock}} or {{cmdroot|docker undock}} command, but this is not comfortable. We will use the ACPI subsystem to bind {{key|Fn}}{{key|F8}}, {{key|Fn}}{{key|F9}} keys and blue button on the docking station to the Dockutils. This could be performed using the following code:<br />
<br />
{{cmdroot|cat /etc/acpi/events/dock}}<br />
<pre>event=(ibm/dock GDCK 00000000 00000003|ibm/hotkey HKEY 00000080 00001008)<br />
action=/usr/sbin/docker dock</pre><br />
and <br />
<br />
{{cmdroot|cat /etc/acpi/events/undock}}<br />
<pre>event=(ibm/dock GDCK 00000003 00000001|ibm/hotkey HKEY 00000080 00001009)<br />
action=/usr/sbin/docker undock</pre><br />
Now, you should be able to undock your PC using the keyboard keys and the dock button.<br />
{{NOTE|[[Thinkpad-acpi|thinkpad_acpi]] and <code>acpid</code> must be installed and running for this to work}}<br />
<br />
== UltraBase X6 under Linux (newer style) ==<br />
Since in recent distributions (like openSUSE 11.1), there is no generated ACPI event for undocking the notebook (Alt+F9 still works the same), you need to use udev in order to be able detect the undocking event. You can use the same ACPI hook as in the "older style" docking setting but you need to put this code into your udev rules:<br />
<br />
{{cmdroot|cat /etc/udev/rules.d/10-docking.rules}}<br />
<pre>ENV{EVENT}=="undock", KERNEL=="dock.0", SUBSYSTEM=="platform", RUN+="/usr/lib/dockutils/hooks/thinkpad/70x61 undock"<br />
ENV{EVENT}=="dock", KERNEL=="dock.0", SUBSYSTEM=="platform", RUN+="/usr/lib/dockutils/hooks/thinkpad/70x61 dock"</pre><br />
After this change, the notebook will change it's resolution automatically after you remove it from the UltraBase.<br />
<br />
<br />
(Has anyone tested this?)</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Problem_with_display_remaining_black_after_resume&diff=40836Problem with display remaining black after resume2009-01-21T21:53:05Z<p>Vrossum: Added blacklist for intel_agp</p>
<hr />
<div>There has been a problem encountered where the display stays black on resuming from suspend.<br />
<br />
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}}.<br />
<br />
==Affected Models==<br />
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T60p}}, {{T61p}}<br />
*Thinkpad {{T23}}<br />
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}<br />
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}, {{R60}}, {{R61}}<br />
*ThinkPad {{A30p}}<br />
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)<br />
*ThinkPad {{Z60t}}, {{Z60m}}, {{Z61m}}, {{Z61e}}<br />
*ThinkPad {{X60s}}, {{X60}}, {{X61}}, {{X61s}}, {{X200}}<br />
<br />
==Affected Operating Systems==<br />
*Linux (it's a kernel issue)<br />
*FreeBSD (6.x at least)<br />
<br />
==Solutions==<br />
===Quick workaround for R61i, T23, maybe others===<br />
Try pressing CTRL+ALT+F1 to switch to text console. The backlight should come on normally. Press CTRL+ALT+F7 to return to X.<br />
<br />
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.<br />
<br />
===Quick Workaround for R61 (at least 8918-5QG) using NVidia===<br />
<br />
Use Vesa driver instead of the proprietary NVidia driver.<br />
<br />
===Pseudo-solution for R61===<br />
On an R61 running Fedora Core 9, the nv driver fails to turn the backlight on after resuming from a suspend to RAM. I fixed this by using the proprietary NVIDIA Linux drivers (v177.82).<br />
<br />
=== Solution for ThinkPad Z60t ===<br />
<br />
* '''Display controller:''' Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)<br />
* '''Distro:''' Fedora release 7 (Moonshine)<br />
* '''Kernel:''' Linux 2.6.22.5-76.fc7<br />
<br />
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:<br />
<br />
echo DISPLAY_QUIRK_S3_BIOS=\"true\" >> /etc/pm/config.d/config<br />
<br />
===Semi-Solution for ThinkPad X60 with damaged system after s2ram usage===<br />
It happend when restarting a s2ram-session.<br />
<br />
'''Symptom:''' Black screen with blinking "_" sign remaind. (without the ")<br />
<br />
'''System status:''' HDD idle, fan running, everything else looks to wait for something to happen.<br />
<br />
'''Semi-Solution:''' Booting with DVD-ROM and going through the installations menu,<br />
where you choose "other" and "boot a installed system" (something like that). Gladly it works,<br />
and OpenSuSE 10.1 comes up with 50% "failed" messages! I than shutdown properly, rebooted again<br />
and had 100% "done" again, with no other things affected.<br />
<br />
'''Further:''' Repairing with the DVD-ROM crashed massivly(!), so I selected "boot a installed system" as final<br />
solution and it worked!<br />
<br />
'''Unknown:''' Maybe the Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM will help,<br />
because X60s and X60 are very familiar. (Not tested so far.)<br />
<br />
(If this Problem is not right here, please edit and move.)<br />
<br />
===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===<br />
see [[1400x1050 on Intel 915GM]].<br />
===Solution for ThinkPads with ATI graphic chips and Intel 915/945GM ===<br />
<br />
Affected models include {{X60s}}, {{X200s}}, {{R60}} and {{T60}}.<br />
<br />
This soluton also applies to T42 with Intel 855 and ATI 9600 M10.<br />
<br />
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.<br />
<br />
For grub this would look like this:<br />
<br />
title Linux, kernel 2.6.11-1-686<br />
root (hd0,0)<br />
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios<br />
initrd /boot/initrd.img-2.6.11-1-686<br />
savedefault<br />
boot<br />
<br />
For lilo it would look like this:<br />
<br />
image=/boot/vmlinuz<br />
append="acpi_sleep=s3_bios"<br />
<br />
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:<br />
<br />
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}}.<br />
<br />
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. <br />
<br />
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].<br />
<br />
{{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.}}<br />
<br />
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}}).<br />
<br />
<br />
----<br />
<br />
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.<br />
<br />
Working config:<br />
Linux 2.6.21.5<br />
fglrx 8.37.6<br />
debian etch:<br />
powersaved 0.14.0-5:<br />
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core"<br />
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core" <br />
hibernate:<br />
SwitchToTextMode yes<br />
lilo.conf:<br />
vga=0<br />
<br />
"EnableVbetool yes" and other suggestions didn't work for me.<br />
<br />
For suspend-to-disk, don't load fglrx in initrd.<br />
<br />
----<br />
<br />
On '''T60-20076RG''' (Core2Duo 2GHz, ATI X1400) with {{OpenSUSE}} 11.1 and fglrx 8-12 the following had to be done to get suspend to RAM always resume:<br />
* Add {{bootparm|S2RAM_QUIRKS_SOURCE|"s2ram"}} to file {{path|/etc/pm/config.d/config}}<br />
* Create an executable script {{path|/etc/pm/sleep.d/00text}} containing:<br />
#!/bin/bash<br />
<br />
case "$1" in<br />
hibernate|suspend)<br />
/bin/chvt 1<br />
;;<br />
thaw|resume)<br />
/bin/chvt 7<br />
;;<br />
esac<br />
<br />
There seems to be a bug ([https://bugzilla.novell.com/show_bug.cgi?id=463434 Novell bugzilla]) which makes it impossible for s2ram to switch to text console while suspending through pm-suspend. The script above forces console change. Along with setting s2ram as quirks source (which makes it correctly set acpi_bios before suspend - to s3_bios,s3_mode<br />
for T60 2007*) this can make resume work flawlessly despite using vesafb.<br />
<br />
===Solution for ThinkPads with Intel Extreme Graphics 2===<br />
{{NOTE|<br />
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.}}<br />
<br />
The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.<br />
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.<br />
*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.<br />
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.<br />
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.<br />
*For Debian Etch 4.0 on R50e just make following changes to /etc/default/acpi-support:<br />
#SAVE_VBE_STATE=true<br />
#VBESTATE=/var/lib/acpi-support/vbestate<br />
#POST_VIDEO=true<br />
SAVE_VIDEO_PCI_STATE=true<br />
<br />
*For a R50e the only thing needed to make suspend to ram work in Ubuntu 6.06 is adding<br />
Option "VBERestore" "yes"<br />
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}, and the example script below.<br />
<br />
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.<br />
<br />
#!/bin/bash<br />
<br />
# change to console 1<br />
FGCONSOLE=`fgconsole`<br />
chvt 6<br />
<br />
# safe video state<br />
cat /proc/bus/pci/00/02.0 > /tmp/video_state<br />
<br />
# sync filesystem<br />
sync<br />
<br />
# sync hardware clock with system time<br />
hwclock --systohc<br />
<br />
# go to sleep<br />
echo -n 3 > /proc/acpi/sleep<br />
<br />
# waking up<br />
# restore system clock<br />
hwclock --hctosys<br />
<br />
# restore video state<br />
cat /tmp/video_state > /proc/bus/pci/00/02.0<br />
<br />
# change back to X<br />
chvt $FGCONSOLE<br />
<br />
# clean up behind us<br />
rm /tmp/video_state<br />
<br />
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:<br />
<br />
SAVE_VBE_STATE=false<br />
POST_VIDEO=false<br />
SAVE_VIDEO_PCI_STATE=true<br />
USE_DPMS=false<br />
DOUBLE_CONSOLE_SWITCH=false<br />
<br />
===Solution for ThinkPads with Intel I830 Chipset===<br />
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.<br />
*this works with vesafb and also with intelfb frambuffer support.<br />
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.<br />
<br />
#!/bin/bash<br />
<br />
FGCONSOLE=`fgconsole`<br />
chvt 8<br />
sync<br />
hwclock --systohc<br />
<br />
echo -n "mem" > /sys/power/state<br />
<br />
hwclock --hctosys<br />
vbetool post<br />
<br />
if [ "$FGCONSOLE" -ge "7" ] ; then<br />
chvt $FGCONSOLE<br />
else<br />
chvt 7<br />
chvt $FGCONSOLE<br />
fi<br />
===Solution for ThinkPads with ATI graphic (and possibly other) chips and FreeBSD===<br />
<br />
The FreeBSD acpi(4) manpage mentions a tunable parameter, "hw.acpi.reset_video":<br />
<br />
hw.acpi.reset_video<br />
Reset the video adapter from real mode during the resume path.<br />
Some systems need this help, others have display problems if it<br />
is enabled. Default is 0 (disabled).<br />
<br />
This tunable can be set by adding the following line to your FreeBSD machine's /boot/loader.conf file:<br />
<br />
hw.acpi.reset_video="1"<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
{{footnotes|<br />
#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]].<br />
}}<br />
<br />
===Solution using s2ram for Intel 915/945GM===<br />
<br />
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. Best idea seems to be to put this into the corresponding acpi script:<br />
<br />
% cat /etc/acpi/sleep.sh <br />
#!/bin/sh<br />
test -f /usr/share/acpi-support/power-funcs || exit 0<br />
test -f /usr/sbin/s2ram || exit 0<br />
rmmod usb_storage<br />
rmmod uhci_hcd<br />
rmmod ehci_hcd<br />
/usr/sbin/s2ram -f -a 1 -m<br />
modprobe uhci_hcd<br />
modprobe ehci_hcd<br />
modprobe usb_storage<br />
<br />
Source: [http://d.hatena.ne.jp/conceal-rs/20080309/1205083315 http://d.hatena.ne.jp/conceal-rs/20080309/1205083315]<br />
Works on my X61.<br />
<br />
===Solution using DOUBLE_CONSOLE_SWITCH===<br />
<br />
By setting the following in {{path|/etc/default/acpi-support}} the display comes back on {{X61s}} using Intel chipset:<br />
<br />
DOUBLE_CONSOLE_SWITCH=true<br />
<br />
Fedora 8 doesn't have DOUBLE_CONSOLE_SWITCH, but it works when one does: First, add option "VBERestore" "true" to /etc/X11/xorg.conf<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "intel"<br />
Option "VBERestore" "true" <br />
EndSection<br />
<br />
Then suspends with<br />
<br />
pm-suspend --quirk-vbemode-restore --quirk-s3-bios<br />
<br />
===Solution for nvidia-drivers-180* series===<br />
<br />
The proprietary NVidia drivers of the 180 series introduce several problems with suspend to ram:<br />
<br />
* Situation 1: Suspend from console, '''no''' X-Server running:<br/><br />
You need to use vbetool to save and restore the vbestate.<br />
When using hibernate-script, this can be done by setting the following config variables:<br />
EnableVbetool yes<br />
RestoreVbeStateFrom /var/lib/vbetool/vbestate<br />
VbetoolPost yes<br />
<br />
You may need to run <code>mkdir -p /var/lib/vbetool && vbetool vbestate save > /var/lib/vbetool/vbestate</code> first.<br />
<br />
* Situation 2: Suspend from running X-Server:<br/><br />
You '''cannot''' use vbetool or any other quirks, since it seems to confuse the nvidia X driver. That means you should enter S3 simply by doing <code>echo mem > /sys/power/state</code>.<br />
<br />
If you have your hotkeys handled by acpid, you might differentiate those two cases by checking for a running X process in your hotkey handler (i.e. <code>/etc/acpid/default.sh</code>):<br />
pgrep -x X > /dev/null \ # checks for running process with name "X"<br />
&& echo mem > /sys/power/state # if found, do plain S3 suspend<br />
|| hibernate-ram # otherwise, run quirked script<br />
<br />
Furthermore, it seems to be a good idea to use the 180 series with a 2.6.28* kernel.<br />
<br />
<br />
It might also help to put <code>blacklist intel_agp </code><br />
in <code>/etc/modprobe.d/blacklist</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Tools&diff=40468Tools2009-01-04T17:41:02Z<p>Vrossum: /* Graphics */</p>
<hr />
<div>Information on Tools helping you to get along with your ThinkPad.<br />
<br />
==Input==<br />
*[[tpb]] <tt>(ThinkPad buttons)</tt><br />
*[http://rsim.cs.uiuc.edu/~sachs/tp-scroll/ tp-scroll] <tt>(Use trackpoint and middle button to scroll vertically. You may also use the built-in EmulateWheel option in both XFree86 and XOrg.)</tt><br />
*[http://tpctl.sourceforge.net/configure-trackpoint.html configure-trackpoint] <tt>(GUI TrackPoint configuration tool for the TrackPoint driver for 2.6 linux kernel)</tt><br />
*[http://www.slac.stanford.edu/~strauman/pers/tp4utils/ Linux Trackpoint Utilities] <tt>(An earlier trackpoint configuration tool)</tt><br />
<br />
==Graphics==<br />
*[[radeontool]] <tt>(Tool for enabling/disabling background light and external video)</tt><br />
*[[atitvout]] <tt>(Tool to control TV out)</tt><br />
*[[rovclock]] <tt>(Tool to under/overclock Radeon cards)</tt><br />
*[[s3switch]] <tt>(Tool to change the output devices and format for Savage cards)</tt><br />
*[http://gsynaptics.sourceforge.jp/ gsynaptics] <tt>(Tool to control synaptics touchpad on some thinkpads)</tt><br />
*[http://willem.engen.nl/projects/disper/ disper] <tt> (Tool to switch displays quickly for Nvidia cards)</tt><br />
<br />
==Power Management==<br />
*[[apmd]] <tt>(APM event daemon and tools)</tt><br />
*[[tpctl]] and configure-thinkpad <tt>(ThinkPad configuration programs that are compatible with APM)</tt><br />
*[[acpid]] <tt>(ACPI event daemon)</tt><br />
*[http://sourceforge.net/projects/acpitool/ acpitool]<tt> (displays acpi information and can be used to set sleep mode)</tt><br />
*[[tphdisk]] <tt>(Tool to create a hibernation file, an alternative to the [[Software Suspend 2]] kernel patch)</tt><br />
*[[laptop-mode-tools]] <tt>(laptop-mode configuration scripts)</tt><br />
*[[KThinkBat]] <tt>(KDE-Kicker applet to show the battery fuel state)</tt><br />
<br />
==Networking==<br />
*[[ifplugd]] <tt>(Daemon to reconfigure your network settings on cable (un)plugging)</tt><br />
*[[waproamd]] <tt>(Daemon for Wireless roaming with automatic WEP key handling)</tt><br />
*[[Wpa_supplicant]] <tt>(waproamd's successor, can handle WPA)</tt><br />
*[[ifmetric]] <tt>(Tool to help set different route metrics for WLAN/cable connections, to be used in conjunction with ifplugd and waproamd)</tt><br />
<br />
==Troubleshooting==<br />
Below are the Tools recommended / used by IBM service reps <br />
*[http://www.memtest86.com memtest86] for testing suspect memory<br />
*[http://www.hitachigst.com/hdd/support/download.htm#DFT Drive Fitness Test] for testing suspected faulty hdd maintained and developed by Hitachi.<br />
<br />
==Movies==<br />
Installing / Adding / Removing Hardware from your thinkpad / Lenovo product?<br />
<br />
*[http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=Tpad-MOVIES Thinkpad Movies]<br />
*[http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=tctr-MOVIES Thinkcentre Movies] (New desktops)<br />
*[http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=netv-MOVIES Netvista Movies] (Older Desktops)</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Rovclock&diff=37284Rovclock2008-04-08T09:58:15Z<p>Vrossum: /* Minimum stable and default clockrates */</p>
<hr />
<div>==General==<br />
Rovclock is a utility to control frequency rates of your Radeon card.<br />
<br />
It is very helpful for underclocking the Radeon chip in order to save power when running on batteries. Also, by underclocking it is possible to prevent the fan from running.<br />
<br />
It can also be used to gain performance by overclocking.<br />
<br />
{{NOTE|While this utility complements the [[How to make use of Graphics Chips Power Management features|DynamicClocks]] option of the X.org <tt>radeon</tt> driver, it is not compatible with the power saving mode of the [[fglrx]] driver. Setting power saving mode using both [[fglrx]] and [[rovclock]] results in an unusably slow desktop.}}<br />
<br />
==Features==<br />
Used to under-/overclock Radeon gfx-cards.<br />
* Controls GPU core frequency<br />
* Controls gfx-memory frequency<br />
<br />
== Project Homepage / Availability ==<br />
* Homepage: http://www.hasw.net/linux/<br />
<br />
==Usage==<br />
*Set the core frequency (-c) to 100 Mhz and the memory frequency (-m) to 120 Mhz.<br />
:{{cmduser|sudo rovclock -c 100 -m 120}}<br />
*Get current frequencies among other information (-i).<br />
:{{cmduser|sudo rovclock -i}}<br />
<br />
==Minimum stable and default clockrates==<br />
* {{A30p}} with Radeon 7000<br />
** LCD: No lower core limit, 90MHz mem (basic use) / 125MHz mem (no artifacts with glxgears)<br />
* {{T42}} with Radeon 7500 <br />
** NOTE: Setting the memory under 100Mhz may hang your card.<br />
** LCD: 100MHz core, 120MHz memory.<br />
** Using DVI output on Port replicator: 100Mhz core, 180MHz memory.<br />
* {{T42}} with Radeon 9600<br />
** LCD: Core: 54.0 MHz, Mem: 60.75 MHz<br />
* {{T42p}} Firegl T2 (9600), fglrx driver, 1600x1200 LCD<br />
** Default: 317.25/202.50<br />
** Core: 81 Mhz, Mem: 67.5 Mhz<br />
* {{T43}} with [[ATI Mobility Radeon X300]]:<br />
** 100MHz core, 120Mz memory (see more [[ATI Mobility Radeon X300|here]])<br />
* {{X24}} with [[ATI Mobility Radeon 7000]]<br />
** Core: 95 Mhz Mem: 90-95 Mhz (mem 90 gave me distorted pictures)<br />
* {{X31}} with [[ATI Mobility Radeon 7000]]<br />
** Default: 144/144<br />
** 90MHz core, 100Mz memory (90/90 is giving distorted picture)<br />
* {{X32}} with [[ATI Mobility Radeon 7000]]<br />
** 90MHz core, 90Mz memory<br />
* {{R50p}} with FireGL Mobility T2:<br />
** 1600x1200 LCD: Core: 100 MHz Mem: 120Mz<br />
* {{R51}} with FireGL 9000<br />
** Core: 40 Mhz Mem: 100 Mhz (2d only, reducing memory further causes some artifacts and doesn't visibly reduce temps.)<br />
<br />
== See also ==<br />
*[[How to make use of Graphics Chips Power Management features]] using the <tt>DynamicClocks</tt> option of the <tt>radeon</tt> driver<br />
*[http://forums.gentoo.org/viewtopic-t-343029.html Gentoo forum discussion]<br />
*[[Radeontool]]<br />
<br />
[[Category:Tools]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Rovclock&diff=37188Rovclock2008-03-28T15:34:01Z<p>Vrossum: /* Minimum stable clockrates */</p>
<hr />
<div>==General==<br />
Rovclock is a utility to control frequency rates of your Radeon card.<br />
<br />
It is very helpful for underclocking the Radeon chip in order to save power when running on batteries. Also, by underclocking it is possible to prevent the fan from running.<br />
<br />
It can also be used to gain performance by overclocking.<br />
<br />
{{NOTE|While this utility complements the [[How to make use of Graphics Chips Power Management features|DynamicClocks]] option of the X.org <tt>radeon</tt> driver, it is not compatible with the power saving mode of the [[fglrx]] driver. Setting power saving mode using both [[fglrx]] and [[rovclock]] results in an unusably slow desktop.}}<br />
<br />
==Features==<br />
Used to under-/overclock Radeon gfx-cards.<br />
* Controls GPU core frequency<br />
* Controls gfx-memory frequency<br />
<br />
== Project Homepage / Availability ==<br />
* Homepage: http://www.hasw.net/linux/<br />
<br />
==Usage==<br />
*Set the core frequency (-c) to 100 Mhz and the memory frequency (-m) to 120 Mhz.<br />
:{{cmduser|sudo rovclock -c 100 -m 120}}<br />
*Get current frequencies among other information (-i).<br />
:{{cmduser|sudo rovclock -i}}<br />
<br />
==Minimum stable and default clockrates==<br />
* {{A30p}} with Radeon 7000<br />
** LCD: No lower core limit, 90MHz mem (basic use) / 125MHz mem (no artifacts with glxgears)<br />
* {{T42}} with Radeon 7500 <br />
** NOTE: Setting the memory under 100Mhz may hang your card.<br />
** LCD: 100MHz core, 120MHz memory.<br />
** Using DVI output on Port replicator: 100Mhz core, 180MHz memory.<br />
* {{T42}} with Radeon 9600<br />
** LCD: Core: 54.0 MHz, Mem: 60.75 MHz<br />
* {{T42p}} Firegl T2 (9600), fglrx driver<br />
** 1600x1200 LCD: Core: 81 Mhz, Mem: 67.5 Mhz<br />
* {{T43}} with [[ATI Mobility Radeon X300]]:<br />
** 100MHz core, 120Mz memory (see more [[ATI Mobility Radeon X300|here]])<br />
* {{X24}} with [[ATI Mobility Radeon 7000]]<br />
** Core: 95 Mhz Mem: 90-95 Mhz (mem 90 gave me distorted pictures)<br />
* {{X31}} with [[ATI Mobility Radeon 7000]]<br />
** Default: 144/144<br />
** 90MHz core, 100Mz memory (90/90 is giving distorted picture)<br />
* {{X32}} with [[ATI Mobility Radeon 7000]]<br />
** 90MHz core, 90Mz memory<br />
* {{R50p}} with FireGL Mobility T2:<br />
** 1600x1200 LCD: Core: 100 MHz Mem: 120Mz<br />
* {{R51}} with FireGL 9000<br />
** Core: 40 Mhz Mem: 100 Mhz (2d only, reducing memory further causes some artifacts and doesn't visibly reduce temps.)<br />
<br />
== See also ==<br />
*[[How to make use of Graphics Chips Power Management features]] using the <tt>DynamicClocks</tt> option of the <tt>radeon</tt> driver<br />
*[http://forums.gentoo.org/viewtopic-t-343029.html Gentoo forum discussion]<br />
*[[Radeontool]]<br />
<br />
[[Category:Tools]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Talk:Embedded_Security_Subsystem&diff=36851Talk:Embedded Security Subsystem2008-03-05T12:40:42Z<p>Vrossum: </p>
<hr />
<div>Q: Good or Bad?<br />
<br />
Someone said: This Security Chip is a hardware trojan. True or false?<br />
<br />
== hmmm. depends. but the fear is big, that it is trojan... ==<br />
<br />
Hello,<br />
<br />
I would say it depends, how TCPA/'Fritz'-Chip is used. But the fear of the critics and (cyber) civil rights people are, that the industry wants to control the use of digital media like MP3, DVD, etc. to prevent copying - even if you own it.<br />
<br />
There is also a fear, that there are hidden channels in this black box type of hardware, because hidden channels where found in so many black box type of hardware for years now. What is transmitted over these hidden channels?<br />
<br />
The recent modifications by the TCG because of the critic and the resulting pressure are a good beginning. We, the consumers and users, have to go an with our demands, with our critic and we have to look carefully, what TCG and the others are doing here.<br />
<br />
Why? Because it will affect all of us sooner or later in using our MP3- or DVD-Players or e.g. -Software on our computers etc. And you can think also about your mobile cellular phones, digital cameras and so on. Digital content, digital media is more and more widespread.<br />
<br />
And this is where Digital Rights Management (DRM) comes into the game. DRM is feared to be a trade barrier for a free market, a barrier to future historians, etc.<br />
<br />
Trusted Computing is not bad by meaning, but it is bad (or 'lousy'?), how the industry is implementing it. They could do better, right?<br />
<br />
--[[User:Pitsche|Pitsche]] 12:19, 4 Jul 2005 (CEST)<br />
<br />
== ESS page may have errors... ==<br />
<br />
Hi, The ESS 1.0 section claims that its based on TCG 1.1 specs, but I cannot find anything to support that. The ESS 2.0 systems I have all have v1.1 TPMs in them, but I don't have an ESS 1.0 system. As far as I know, the ESS 1.0 does not implement any TCG specification.<br />
<br />
Also, the ESS 2.0 does not provide a TCG 1.2 TPM. No currently shipping IBM platforms contain 1.2 TPMs. I thought I'd mention this stuff somewhere before just changing the wiki with no discussion.<br />
<br />
Thanks<br />
----<br />
Thanks. You could have just changed it and leave a note with pointers to your sources. I also wondered about the fact that IBM says nothing about TCG in ESS 1.0, but i didn't find any more detailed information. Did you? And if so, where?<br />
<br />
[[User:Wyrfel|Wyrfel]] 19:59, 12 Jul 2005 (CEST)<br />
----<br />
Yeah, I am seeing less and less on ESS 1.0 on www.ibm.com, which is my source for this stuff. If I come across anything concrete, I'll post it.<br />
<br />
== X60, X60s and T60 with TCG 1.2-compliant Atmel chip ==<br />
<br />
Lenovo's "Personal Systems Reference" on Thinkpad Notebooks version 301, January 2006 states that Thinkpads X60, X60 and T60 are equipped with a "Trusted Platform Module / Atmel chip / TCG 1.2-compliant".<br />
<br />
Could this be the Atmel AT97SC3203? <br />
Can anyone confirm this?<br />
<br />
What about linux support for this chip?<br />
<br />
Update: In the same document I found "LPC bus (PC87382 Super I/O, Atmel® 97SC3203)" in the architecture section.<br />
----<br />
I believe that TCG 1.2 includes an API for software communication with the chips, so the drivers should be chip independent. Not sure, though.<br />
<br />
[[User:Wyrfel|Wyrfel]] 12:34, 19 January 2006 (CET)<br />
----<br />
<br />
== TPM removal??? ==<br />
<br />
So, according to the photo in the article, the TPM chip is on a removable daughter card. With the chip removed, will the PC still operate as a normal (non TPM-enabled) PC?<br />
<br />
Answer: Yes, it is true the TPM chip is 97SC3203. But the TP won't work w/o it. It will give the security chip tamper error. Anyway, the chip internal ROM can be read in the same way as the PC8394T-VJG ROM.<br />
<br />
<br />
== But what's its use ? ==<br />
<br />
Despite all the info, it is still unclear what this system is good for.<br />
What is the typical scenario for using it? How does it compare to just plain encryption of you HD?<br />
<br />
Thanks.</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Problem_with_video_related_system_lockup_II&diff=36224Problem with video related system lockup II2008-01-26T12:16:58Z<p>Vrossum: added r50p as affected</p>
<hr />
<div>Thinkpads with the ATI 9600 video chip used in R50p, T42 and T42p can cause lock-ups.<br />
<br />
This happens after about two years of use.<br />
<br />
==Symptoms==<br />
Screen goes blank, requires hard reboot (power off-on) to get screen display. On boot may give one long, two short beeps POST code. Screen goes blank when laptop flexed, eg adjusting lid angle, squeezing around ultranav trackpad area, twisting, pressing on palmrest. POST code or screen blanking more prevalent after warm-up. Problem gets worse over time. Problem repeatable from first boot (bios) screen with tpad partially disassembled - hdd, ultrabay, extra ram, wifi removed, kb, palm rest removed, but connected. See http://www.technotaste.com/blog/thinkpad-t42-ati-radeon-9600-driver-and-the-blue-screen-of-death-bsod<br />
and<br />
http://forum.thinkpads.com/viewtopic.php?t=33952<br />
for discussions of many similar symptoms.<br />
<br />
== Diagnosis ==<br />
Bad or broken solder joint on graphics chip. The chip is a ball grid array (BGA) package mounted to the system board. The problem is likely caused by an intermittent connection to the system board due to one or more bad or broken solder joints connecting the BGA to the system board. Thermal and/or mechanical movement breaks the connection, crashing the chip, yielding a blank screen or the BSOD.<br />
<br />
==Solutions==<br />
* Replace system board. <br />
* Reflow the solder on the graphics chip: Remove the system board, take it to a board house that can reflow the BGA package, reassemble, cross fingers, test. There are a number of videos showing the process on YouTube. One of them: http://www.youtube.com/watch?v=vR8L3B3eDr0<br />
* Place a supplement between the GPU Disipator and the keyboard metal, this will push the gpu to the systemboard, forcing a better contact. I placed about eight post-it's bended at the half. So far, so good. it works for me (eMaringolo). See it here: http://www.flickr.com/photos/emaringolo/373874916/<br />
<br />
== See Also==<br />
[[Problem with garbled screen]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Talk:Intel_Pentium_M_(Dothan)&diff=36191Talk:Intel Pentium M (Dothan)2008-01-23T16:22:13Z<p>Vrossum: compiler options</p>
<hr />
<div>Why advice '-Os' as compiler option?<br />
Isn't -O3 better?</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Talk:Lt_hotswap&diff=35809Talk:Lt hotswap2008-01-11T15:25:26Z<p>Vrossum: â†Created page with 'I get a compilation error, even after applying the suggested changes: /usr/local/src/lt_hotswap-0.3.6/lt_hotswap.c: In function ‘lths_scan_ide’: /usr/local/src/lt_hot...'</p>
<hr />
<div>I get a compilation error, even after applying the suggested changes:<br />
<br />
/usr/local/src/lt_hotswap-0.3.6/lt_hotswap.c: In function ‘lths_scan_ide’:<br />
/usr/local/src/lt_hotswap-0.3.6/lt_hotswap.c:460: error: implicit declaration of function ‘ide_setup_dma’<br />
<br />
Anyone?</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=How_to_configure_acpid&diff=35498How to configure acpid2008-01-05T14:32:09Z<p>Vrossum: </p>
<hr />
<div>__TOC__<br />
==Introduction==<br />
Basically, [[acpid]] just executes scripts residing in {{path|/etc/acpi/actions}}. Which script to launch at which event is configured in several files in {{path|/etc/acpi/events}}. All actions are documented in {{path|/var/log/acpid}}.<br />
<br />
==Sources of Information==<br />
*{{cmduser|man acpid}} holds detailed information on how to configure acpid.<br />
*The [[ibm-acpi]] package includes example scripts in the {{path|config}} folder inside the tarball. They are a good starting point to adjust them to your needs.<br />
*You also might want to have a look at the [[Configs#ACPI | ACPI section of the Configs page]] or the [[:Category:Scripts|Scripts]] repository.<br />
*And you can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].<br />
<br />
==Example: go to sleep on lid close==<br />
To make the ThinkPad go to sleep when you close the lid, you need to add<br />
an event handler for the lid event and an action script that takes care<br />
of going to sleep and resuming.<br />
<br />
===Event Script===<br />
The event script needs to be created within {{path|/etc/acpi/events}} and can have any name you like.<br />
In this case we call it lid because it will trigger the lid event. Do {{cmdroot|vi /etc/acpi/events/lid}} and make it look like this:<br />
event=button/lid<br />
action=/etc/acpi/actions/sleep.sh %e<br />
<br />
The "event" line is a regular expression specifying the events we're<br />
interested in. You can determine what the event strings are from looking at<br />
{{path|/var/log/acpid}} after trying to suspend, close the lid, etc. .<br />
You can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].<br />
<br />
The "action" line is the command to be executed when these events are<br />
dispatched. In this example we call the {{path|sleep.sh}} script residing in {{path|/etc/acpi/actions}} and pass the event description text using the %e placeholder.<br />
<br />
For the script you can use the <tt>hibernate</tt> script of [http://www.tuxonice.net/ Tux On Ice] (it is independent of the [[ www.suspend2.net | suspend-to-disk]] functionality), or any of many examples available on the web, such as the one below.<br />
<br />
{{NOTE|To make your changes take effect after adding or modifying the events files you must do a <tt>kill -SIGHUP `pidof acpid`</tt>}}<br />
<br />
===Action Script===<br />
Our example {{path|/etc/acpi/actions/sleep.sh}} script looks as follows:<br />
<br />
#!/bin/sh<br />
<br />
# if launched through a lid event and lid is open, do nothing<br />
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0<br />
<br />
# remove USB 1.1 driver<br />
rmmod uhci_hcd<br />
<br />
# sync filesystem and clock<br />
sync<br />
/sbin/hwclock --systohc<br />
<br />
# switch to console<br />
FGCONSOLE=`fgconsole`<br />
chvt 6<br />
/usr/sbin/radeontool light off<br />
<br />
# go to sleep<br />
sleep 5 && echo -n "mem" > /sys/power/state<br />
<br />
# readjust the clock (it might be off a bit after suspend)<br />
/sbin/hwclock --adjust<br />
/sbin/hwclock --hctosys<br />
<br />
# reload USB 1.1 driver<br />
modprobe uhci_hcd<br />
<br />
# turn on the backlight and switch back to X<br />
radeontool light on<br />
chvt $FGCONSOLE<br />
<br />
{{NOTE|This parts of this script are now part of some distributions, like Debian Etch and you probably don't need to add this script. Look into /etc/acpi/lid.sh, for example.}}<br />
<br />
====Explanations====<br />
*The lid generates an event for both opening and closing thus requiring that we check its state and only act if it's closed.<br />
*There have been problems encountered with the USB devices not working properly after a resume from suspend. To circumvent those we remove the USB driver prior to suspend and reload it afterwards.<br />
*Note that the {{cmdroot|echo -n "mem" > /sys/power/state}} line does not return until we are revived. So there is only one event generated and there is no need to check the state of anything.<br />
*The console switching code in this script is a special solution for [[Problem with LCD backlight remaining on during ACPI sleep|a problem where the backlight doesn't switch off]] on the {{T30}} and some other models. Before going to sleep, these models switch to console mode which causes the backlight to come back on. So we preemptively switch to console mode and turn off the backlight using [[radeontool]] before going to sleep.<br />
<br />
==Screen blanking script==<br />
<br />
You might want to be able to switch of the screen using Fn-f3.<br />
This is not completely straightforward.<br />
You will first need to give permission to the script to muck around with your screen<br />
<br />
xhost +local:root <br />
<br />
/etc/acpi/events/sleepbtn <br />
contains<br />
event=(button[ /]sleep|ibm/hotkey HKEY 00000080 00001004)<br />
action=/etc/acpi/sleepbtn.sh<br />
<br />
And /etc/acpi/sleepbtn.sh is <br />
<br />
#!/bin/bash<br />
<br />
# simple script to turn the display on or off #<br />
# By Mahram Z.Foadi #<br />
# Oct 22 2005 # <br />
# thank you linuxquestions.org #<br />
# # <br />
# the following lines must be present in your "/etc/acpi/events/" files. Some #<br />
# systems already have a file called sample.conf in the mentioned directory #<br />
# rename it to something more meaningful (i.e. acpid.conf) and these lines to #<br />
# the end of it (you don't HAVE to rename it, you can even create a new file #<br />
# and call it /etc/acpi/events/lid.conf with the 2 lines in it. If you intend #<br />
# to put this file anywhere other than /sbin/lidevent, make sure you make the #<br />
# proper changes in the "action" line below. For example if you are going to #<br />
# save this script as /usr/bin/mylid.sh then the action line should be: #<br />
# action=/usr/bin/mylid.sh #<br />
# be sure both files are executable, writable, and owned by root ONLY because #<br />
# the acpid daemon is most likely running as root in your system #<br />
# #<br />
# ---- insert the two lines below in /etc/acpi/events/acpid.conf ---- #<br />
# event=button/lid.* #<br />
# action=/sbin/lidevent #<br />
#-----------------------------------------------------------------------------#<br />
<br />
# default display on current host<br />
DISPLAY=:0.0<br />
<br />
# find out if DPMS is enabled<br />
STATUS=`xset -display $DISPLAY -q | grep -e 'DPMS is'`<br />
<br />
# enable DPMS if disabled<br />
if [ "$STATUS" == " DPMS is Disabled" ]<br />
then<br />
echo "Enabling DPMS ..."<br />
xset -display $DISPLAY +dpms<br />
fi<br />
<br />
# find out if monitor is on<br />
STATUS=`xset -display $DISPLAY -q | grep 'Monitor'`<br />
<br />
if [ "$STATUS" == " Monitor is On" ]<br />
then<br />
echo "[`date`] Turning display OFF"<br />
xset -display $DISPLAY dpms force off<br />
else<br />
echo "[`date`] Turning display ON" # shows up in log<br />
xset -display $DISPLAY dpms force on # turn monitor on<br />
xset -display $DISPLAY s activate # un-blank monitor<br />
fi<br />
<br />
#clean up<br />
unset STATUS<br />
<br />
# comment this line out if you're manually running this script from a shell (put a # in front of it)<br />
unset DISPLAY<br />
<br />
exit 0<br />
<br />
An alternative is to call radeontool (if you have a radeon videocard only of course)<br />
<br />
<br />
==Switch external display==<br />
Again make sure that <br />
xhost +local:root <br />
<br />
With the newer versions of X, display switching can be done with xrandr.<br />
Create the script /etc/acpi/switchdisplay.sh<br />
#!/bin/csh<br />
/usr/bin/xrandr --output VGA-0 --auto<br />
<br />
And /etc/acpi/events/displaybtn<br />
event=ibm/hotkey HKEY 00000080 00001007<br />
action=/etc/acpi/switchdisplay.sh<br />
<br />
==Troubleshooting==<br />
*If something doesn't work, your first action should be a {{cmdroot|tail /var/log/acpid}}. It will tell you a lot about what is going on. If it has "Permission denied" errors, check the permissions of your {{path|/etc/acpi/actions}} scripts (especially make sure that the executable bit is set). Also check the permissions for other involved files like i.e. device nodes.<br />
*For further problems look at the [[Problems with ACPI suspend-to-ram|Problems with ACPI suspend-to-ram page]].<br />
<br />
<br />
<br />
[[Category:770X]] [[Category:770Z]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:Z60t]] [[Category:Z60m]] [[Category:TransNote]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=How_to_configure_acpid&diff=35497How to configure acpid2008-01-05T14:28:56Z<p>Vrossum: /* Troubleshooting */</p>
<hr />
<div>__TOC__<br />
==Introduction==<br />
Basically, [[acpid]] just executes scripts residing in {{path|/etc/acpi/actions}}. Which script to launch at which event is configured in several files in {{path|/etc/acpi/events}}. All actions are documented in {{path|/var/log/acpid}}.<br />
<br />
==Sources of Information==<br />
*{{cmduser|man acpid}} holds detailed information on how to configure acpid.<br />
*The [[ibm-acpi]] package includes example scripts in the {{path|config}} folder inside the tarball. They are a good starting point to adjust them to your needs.<br />
*You also might want to have a look at the [[Configs#ACPI | ACPI section of the Configs page]] or the [[:Category:Scripts|Scripts]] repository.<br />
*And you can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].<br />
<br />
==Example: go to sleep on lid close==<br />
To make the ThinkPad go to sleep when you close the lid, you need to add<br />
an event handler for the lid event and an action script that takes care<br />
of going to sleep and resuming.<br />
<br />
===Event Script===<br />
The event script needs to be created within {{path|/etc/acpi/events}} and can have any name you like.<br />
In this case we call it lid because it will trigger the lid event. Do {{cmdroot|vi /etc/acpi/events/lid}} and make it look like this:<br />
event=button/lid<br />
action=/etc/acpi/actions/sleep.sh %e<br />
<br />
The "event" line is a regular expression specifying the events we're<br />
interested in. You can determine what the event strings are from looking at<br />
{{path|/var/log/acpid}} after trying to suspend, close the lid, etc. .<br />
You can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].<br />
<br />
The "action" line is the command to be executed when these events are<br />
dispatched. In this example we call the {{path|sleep.sh}} script residing in {{path|/etc/acpi/actions}} and pass the event description text using the %e placeholder.<br />
<br />
For the script you can use the <tt>hibernate</tt> script of [http://www.tuxonice.net/ Tux On Ice] (it is independent of the [[ www.suspend2.net | suspend-to-disk]] functionality), or any of many examples available on the web, such as the one below.<br />
<br />
{{NOTE|To make your changes take effect after adding or modifying the events files you must do a <tt>kill -SIGHUP `pidof acpid`</tt>}}<br />
<br />
===Action Script===<br />
Our example {{path|/etc/acpi/actions/sleep.sh}} script looks as follows:<br />
<br />
#!/bin/sh<br />
<br />
# if launched through a lid event and lid is open, do nothing<br />
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0<br />
<br />
# remove USB 1.1 driver<br />
rmmod uhci_hcd<br />
<br />
# sync filesystem and clock<br />
sync<br />
/sbin/hwclock --systohc<br />
<br />
# switch to console<br />
FGCONSOLE=`fgconsole`<br />
chvt 6<br />
/usr/sbin/radeontool light off<br />
<br />
# go to sleep<br />
sleep 5 && echo -n "mem" > /sys/power/state<br />
<br />
# readjust the clock (it might be off a bit after suspend)<br />
/sbin/hwclock --adjust<br />
/sbin/hwclock --hctosys<br />
<br />
# reload USB 1.1 driver<br />
modprobe uhci_hcd<br />
<br />
# turn on the backlight and switch back to X<br />
radeontool light on<br />
chvt $FGCONSOLE<br />
<br />
{{NOTE|This parts of this script are now part of some distributions, like Debian Etch and you probably don't need to add this script. Look into /etc/acpi/lid.sh, for example.}}<br />
<br />
====Explanations====<br />
*The lid generates an event for both opening and closing thus requiring that we check its state and only act if it's closed.<br />
*There have been problems encountered with the USB devices not working properly after a resume from suspend. To circumvent those we remove the USB driver prior to suspend and reload it afterwards.<br />
*Note that the {{cmdroot|echo -n "mem" > /sys/power/state}} line does not return until we are revived. So there is only one event generated and there is no need to check the state of anything.<br />
*The console switching code in this script is a special solution for [[Problem with LCD backlight remaining on during ACPI sleep|a problem where the backlight doesn't switch off]] on the {{T30}} and some other models. Before going to sleep, these models switch to console mode which causes the backlight to come back on. So we preemptively switch to console mode and turn off the backlight using [[radeontool]] before going to sleep.<br />
<br />
==Screen blanking script==<br />
<br />
You might want to be able to switch of the screen using Fn-f3.<br />
This is not completely straightforward.<br />
You will first need to give permission to the script to muck around with your screen<br />
<br />
xhost +local:root <br />
<br />
/etc/acpi/events/sleepbtn <br />
contains<br />
event=(button[ /]sleep|ibm/hotkey HKEY 00000080 00001004)<br />
action=/etc/acpi/sleepbtn.sh<br />
<br />
And /etc/acpi/sleepbtn.sh is <br />
<br />
#!/bin/bash<br />
<br />
# simple script to turn the display on or off #<br />
# By Mahram Z.Foadi #<br />
# Oct 22 2005 # <br />
# thank you linuxquestions.org #<br />
# # <br />
# the following lines must be present in your "/etc/acpi/events/" files. Some #<br />
# systems already have a file called sample.conf in the mentioned directory #<br />
# rename it to something more meaningful (i.e. acpid.conf) and these lines to #<br />
# the end of it (you don't HAVE to rename it, you can even create a new file #<br />
# and call it /etc/acpi/events/lid.conf with the 2 lines in it. If you intend #<br />
# to put this file anywhere other than /sbin/lidevent, make sure you make the #<br />
# proper changes in the "action" line below. For example if you are going to #<br />
# save this script as /usr/bin/mylid.sh then the action line should be: #<br />
# action=/usr/bin/mylid.sh #<br />
# be sure both files are executable, writable, and owned by root ONLY because #<br />
# the acpid daemon is most likely running as root in your system #<br />
# #<br />
# ---- insert the two lines below in /etc/acpi/events/acpid.conf ---- #<br />
# event=button/lid.* #<br />
# action=/sbin/lidevent #<br />
#-----------------------------------------------------------------------------#<br />
<br />
# default display on current host<br />
DISPLAY=:0.0<br />
<br />
# find out if DPMS is enabled<br />
STATUS=`xset -display $DISPLAY -q | grep -e 'DPMS is'`<br />
<br />
# enable DPMS if disabled<br />
if [ "$STATUS" == " DPMS is Disabled" ]<br />
then<br />
echo "Enabling DPMS ..."<br />
xset -display $DISPLAY +dpms<br />
fi<br />
<br />
# find out if monitor is on<br />
STATUS=`xset -display $DISPLAY -q | grep 'Monitor'`<br />
<br />
if [ "$STATUS" == " Monitor is On" ]<br />
then<br />
echo "[`date`] Turning display OFF"<br />
xset -display $DISPLAY dpms force off<br />
else<br />
echo "[`date`] Turning display ON" # shows up in log<br />
xset -display $DISPLAY dpms force on # turn monitor on<br />
xset -display $DISPLAY s activate # un-blank monitor<br />
fi<br />
<br />
#clean up<br />
unset STATUS<br />
<br />
# comment this line out if you're manually running this script from a shell (put a # in front of it)<br />
unset DISPLAY<br />
<br />
exit 0<br />
<br />
An alternative is to call radeontool (if you have a radeon videocard only of course)<br />
<br />
<br />
==Switch external display==<br />
Again make sure that <br />
<br />
With the newer versions of X, display switching can be done with xrandr.<br />
<br />
<br />
<br />
==Troubleshooting==<br />
*If something doesn't work, your first action should be a {{cmdroot|tail /var/log/acpid}}. It will tell you a lot about what is going on. If it has "Permission denied" errors, check the permissions of your {{path|/etc/acpi/actions}} scripts (especially make sure that the executable bit is set). Also check the permissions for other involved files like i.e. device nodes.<br />
*For further problems look at the [[Problems with ACPI suspend-to-ram|Problems with ACPI suspend-to-ram page]].<br />
<br />
<br />
<br />
[[Category:770X]] [[Category:770Z]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:Z60t]] [[Category:Z60m]] [[Category:TransNote]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Talk:Ultrabay_Slim_Multi-Burner_Drive&diff=35264Talk:Ultrabay Slim Multi-Burner Drive2007-12-22T11:58:01Z<p>Vrossum: â†Created page with 'I had already 2 drives of this type fail on me. Anybody else similar experiences?'</p>
<hr />
<div>I had already 2 drives of this type fail on me.<br />
Anybody else similar experiences?</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Ultrabay&diff=35253Ultrabay2007-12-21T13:15:09Z<p>Vrossum: /* Unofficially compatible */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:UltraBay.jpg|UltraBay drives]] __NOTOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== IBM UltraBay ===<br />
UltraBay{{footnote|1}} is IBM's name for the swapable drive slot. With IBMs words: <blockquote>"The ThinkPad UltraBay, also standard with the system, is an intelligent bay that switches its pinout signals to allow the installation of standard and optional features in what would normally be just the FDD bay."</blockquote> Introduced back in the times of the 750 ThinkPads, this technology has gone through redesigns with almost every new generation of ThinkPad models, possibly leading to some confusion that is hopefully cleared up here. The following table gives an overview of the different UltraBay types, in which models they occurred and what drives are available for them.<br />
Note that the optical drive bay in G series ThinkPads is not an UltraBay in that the drives are fixed and not removable.<br />
<br />
On the media side different UltraBays relate to the form factor of the drives they accept, e.g early A, T and X series models can accept UltraBay devices up to 12.5mm in thickness, whereas current T and X series machines are limited to devices no more than 9.5mm thick.<br />
</div><br />
|}<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|+Overview over UltraBay types and available devices<br />
! width=140px|UltraBay Type !! featured in !! available drives (see [[UltraBay Devices]] for details)<br />
<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay || {{355}}, {{355C}}, {{355Cs}}, {{360}}, {{360C}}, {{360Cs}}, {{360P}}, {{360CE}}, {{360CSE}}, {{360PE}}, {{370C}}, {{750}}, {{750C}}, {{750Cs}}, {{750P}}, {{755C}}, {{755CE}}, {{755Cs}}, {{755CSE}}, {{755CV}}, {{755CX}}, {{760C}}, {{760L}}, {{760E}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay Thick|| {{755CD}}, {{755CDV}}, {{760CD}}, {{760E}}, {{760ED}}, {{760EL}}, {{760ELD}}, {{760LD}}, {{760XD}}, {{760XL}}, {{765D}}, {{765L}}, [[SelectaDock I]], [[SelectaDock II]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabayii.png]] UltraBay II || {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}, [[SelectaDock III]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayfx.png]] UltraBay FX|| {{390}}, {{390E}}, {{390X}}, {{i1720}}, {{i1721}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultraslimbay.png]] UltraslimBay || {{600}}, {{600E}}, {{600X}}, [[UltraBase]], [[Portable Drive Bay]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabay2000.png]] UltraBay 2000 || {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{T20}}, {{T21}}, {{T22}}, {{T23}}, [[ThinkPad Dock|Dock]], [[ThinkPad Dock II|Dock II]], [[UltraBase X2]], [[Portable Drive Bay 2000]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayplus.png]] UltraBay Plus || {{A30}}, {{A30p}}, {{A31}}, {{A31p}}, {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{T23}}, {{T30}}, [[UltraBase X3]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], WorkPad Cradle, Numpad<br />
|-<br />
| [[Image:Icon20_ultrabayslim.png]] UltraBay Slim || {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T60p}}, {{T61}}, {{T61p}}, {{Z60t}}, [[UltraBase X4]], [[ThinkPad X4 Dock]], [[UltraBase X6]], [[X6 Tablet UltraBase]] || [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], Serial/Parallel Port Adapter (T60/T60p)<br />
|-<br />
| [[Image:Icon20_ultrabayenh.png]] UltraBay Enhanced || {{R50}}, {{R50e}}, {{R50p}}, {{R51}}, {{R52}}, {{R60}}, {{Z60m}}, {{Z61m}}, [[ ThinkPad Advanced Dock]]|| [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
|}<br />
<br />
{| border="1" cellspacing="0" cellpadding="2" style="text-align:center;"<br />
|+Compatibility Matrix (read columns as slots with rows as devices that are compatible)<br />
! Slots<hr />Devices!! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />&nbsp; !! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />Thick !! [[Image:Icon20_ultrabayii.png]]<br />UltraBay<br />II !! [[Image:Icon20_ultrabayfx.png]]<br />UltraBay<br />FX !! [[Image:Icon20_ultraslimbay.png]]<br />UltraslimBay<br />&nbsp; !! [[Image:Icon20_ultrabay2000.png]]<br />UltraBay<br />2000 !! [[Image:Icon20_ultrabayplus.png]]<br />UltraBay<br />Plus !! [[Image:Icon20_ultrabayslim.png]]<br />UltraBay<br />Slim !! [[Image:Icon20_ultrabayenh.png]]<br />UltraBay<br />Enhanced<br />
|-<br />
|'''UltraBay''' || yes || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay Thick''' || - || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay II''' || - || - || yes || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay FX''' || - || - || - || yes || - || - || - || - || -<br />
|-<br />
|'''UltraslimBay''' || - || - || - || - || yes || - || - || - || -<br />
|-<br />
|'''UltraBay 2000''' || - || - || - || - || - || yes || yes || - || -<br />
|-<br />
|'''UltraBay Plus''' || - || - || - || - || - || - || yes || - || -<br />
|-<br />
|'''UltraBay Slim''' || - || - || - || - || - || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || yes || yes<br />
|-<br />
|'''UltraBay Enhanced''' || - || - || - || - || - || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || - || yes<br />
|}<br />
<br />
===Characteristics===<br />
*UltraBay: no hot swapping<br />
*UltraBay Thick: thicker version of UltraBay to support CD-ROM drive<br />
*UltraBay II: supports hot swapping, blending has cut out edge on the right<br />
*UltraBay FX: the combined [[floppy]] drive and CD-ROM, DVD or CDRW mechanism found in the {{390}}/{{390E}}/{{390X}}<br />
*UltraSlimBay: supports hot swapping; frame, rectangle like blending<br />
*UltraBay 2000: supports hot swapping; frame, blending has cut-out edge on the right<br />
*UltraBay Plus: same as UltraBay 2000, but can take the [[UltraBay Plus Device Carrier]] which in turn can hold the [[UltraBay Plus c500 Cradle]] or the [[UltraBay Plus Numeric Keypad]]<br />
*UltraBay Slim: supports hot swapping; notably thinner than the UltraBay 2000, cut-out right edge in blending<br />
*UltraBay Enhanced: supports hot swapping; slightly thicker than UltraBay Slim, but accepts UltraBay Slim devices<br />
<br />
==Linux Support==<br />
The pinout switching is done by the BIOS and hardware, so that it is completely transparent to the operating system.<br />
*Floppy drives are supported by the standard floppy driver.<br />
*ZIP drive support is possible through the ide-disk driver.<br />
*IDE hard disks and optical drives are supported by the <tt>ide-disk</tt> or <tt>ata_piix</tt> driver in the linux kernel. SCSI emulation via <tt>ide-scsi</tt> is possible. <br />
*Batteries are automatically handled by the hardware, but can be controlled further by using [[tp_smapi]].<br />
*UltraBay Plus devices should be handled by the USB subsystem, but if the actual devices are is not known.<br />
<br />
===Unofficially compatible===<br />
A CDRW/DVD-ROM Superdrive (scavenged from a Mac iBook) will fit in an Ultrabay 2000. The original face won't fit in the bay, leaving a bare metal front. When the drive spins up, it blows a lot of air out. Maybe that's an anti-dust measure?<br />
<br />
In general, Ultrabay 2000 CD drives have a standard connector, and can therefore be replaced by most other 12.7 mm drives. You might have to do some cutting of the plastic face plate.<br />
<br />
The Ultrabay Slim CD drives however, have a proprietary connector. You can not replace them with any 9.5 mm CD drive.<br />
<br />
===Hotswapping===<br />
See also [[How to hotswap UltraBay devices]].<br />
<br />
==External Sources==<br />
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50366 IBMs page on using a second hard drive adapter in the Ultrabay 2000 slot under Linux]<br />
<br />
{{footnotes|<br />
#IBM originally used the spelling UltraBay with a capital B and later switched to Ultrabay with a lower b. We are sticking with the capital B here.<br />
}}<br />
<br />
[[Category:Glossary]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Ultrabay&diff=35252Ultrabay2007-12-21T13:14:18Z<p>Vrossum: /* Unofficially compatible */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:UltraBay.jpg|UltraBay drives]] __NOTOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== IBM UltraBay ===<br />
UltraBay{{footnote|1}} is IBM's name for the swapable drive slot. With IBMs words: <blockquote>"The ThinkPad UltraBay, also standard with the system, is an intelligent bay that switches its pinout signals to allow the installation of standard and optional features in what would normally be just the FDD bay."</blockquote> Introduced back in the times of the 750 ThinkPads, this technology has gone through redesigns with almost every new generation of ThinkPad models, possibly leading to some confusion that is hopefully cleared up here. The following table gives an overview of the different UltraBay types, in which models they occurred and what drives are available for them.<br />
Note that the optical drive bay in G series ThinkPads is not an UltraBay in that the drives are fixed and not removable.<br />
<br />
On the media side different UltraBays relate to the form factor of the drives they accept, e.g early A, T and X series models can accept UltraBay devices up to 12.5mm in thickness, whereas current T and X series machines are limited to devices no more than 9.5mm thick.<br />
</div><br />
|}<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|+Overview over UltraBay types and available devices<br />
! width=140px|UltraBay Type !! featured in !! available drives (see [[UltraBay Devices]] for details)<br />
<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay || {{355}}, {{355C}}, {{355Cs}}, {{360}}, {{360C}}, {{360Cs}}, {{360P}}, {{360CE}}, {{360CSE}}, {{360PE}}, {{370C}}, {{750}}, {{750C}}, {{750Cs}}, {{750P}}, {{755C}}, {{755CE}}, {{755Cs}}, {{755CSE}}, {{755CV}}, {{755CX}}, {{760C}}, {{760L}}, {{760E}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabay.png]] UltraBay Thick|| {{755CD}}, {{755CDV}}, {{760CD}}, {{760E}}, {{760ED}}, {{760EL}}, {{760ELD}}, {{760LD}}, {{760XD}}, {{760XL}}, {{765D}}, {{765L}}, [[SelectaDock I]], [[SelectaDock II]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], 2.88 MB diskette, PCMCIA Cartridge, IBM Wireless Modem ARDIS, IBM Wireless Modem<br />
|-<br />
| [[Image:Icon20_ultrabayii.png]] UltraBay II || {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}, [[SelectaDock III]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayfx.png]] UltraBay FX|| {{390}}, {{390E}}, {{390X}}, {{i1720}}, {{i1721}} || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultraslimbay.png]] UltraslimBay || {{600}}, {{600E}}, {{600X}}, [[UltraBase]], [[Portable Drive Bay]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabay2000.png]] UltraBay 2000 || {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{T20}}, {{T21}}, {{T22}}, {{T23}}, [[ThinkPad Dock|Dock]], [[ThinkPad Dock II|Dock II]], [[UltraBase X2]], [[Portable Drive Bay 2000]]|| [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
| [[Image:Icon20_ultrabayplus.png]] UltraBay Plus || {{A30}}, {{A30p}}, {{A31}}, {{A31p}}, {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{T23}}, {{T30}}, [[UltraBase X3]] || [[Image:Icon20_floppy.png|Floppy Drive]] [[Image:Icon20_ls120.png|SuperDisk LS-120 Drive]] [[Image:Icon20_ls240.png|SuperDisk LS-240 Drive]] [[Image:Icon20_zip100.png|100MB Zip Drive]] [[Image:Icon20_zip250.png|250MB Zip Drive]] [[Image:Icon20_cdrom.png|CD-ROM Drive]] [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_cdrw.png|CD-RW Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], WorkPad Cradle, Numpad<br />
|-<br />
| [[Image:Icon20_ultrabayslim.png]] UltraBay Slim || {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T60p}}, {{T61}}, {{T61p}}, {{Z60t}}, [[UltraBase X4]], [[ThinkPad X4 Dock]], [[UltraBase X6]], [[X6 Tablet UltraBase]] || [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]], Serial/Parallel Port Adapter (T60/T60p)<br />
|-<br />
| [[Image:Icon20_ultrabayenh.png]] UltraBay Enhanced || {{R50}}, {{R50e}}, {{R50p}}, {{R51}}, {{R52}}, {{R60}}, {{Z60m}}, {{Z61m}}, [[ ThinkPad Advanced Dock]]|| [[Image:Icon20_dvd.png|DVD-ROM Drive]] [[Image:Icon20_combo.png|CD-RW/DVD-ROM Combo Drive]] [[Image:Icon20_multiburner.png|DVD Multi-Burner Drive]] [[Image:Icon20_hdd.png|Harddisk Drive Adapter]] [[Image:Icon20_battery.png|Battery]]<br />
|-<br />
|}<br />
<br />
{| border="1" cellspacing="0" cellpadding="2" style="text-align:center;"<br />
|+Compatibility Matrix (read columns as slots with rows as devices that are compatible)<br />
! Slots<hr />Devices!! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />&nbsp; !! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />Thick !! [[Image:Icon20_ultrabayii.png]]<br />UltraBay<br />II !! [[Image:Icon20_ultrabayfx.png]]<br />UltraBay<br />FX !! [[Image:Icon20_ultraslimbay.png]]<br />UltraslimBay<br />&nbsp; !! [[Image:Icon20_ultrabay2000.png]]<br />UltraBay<br />2000 !! [[Image:Icon20_ultrabayplus.png]]<br />UltraBay<br />Plus !! [[Image:Icon20_ultrabayslim.png]]<br />UltraBay<br />Slim !! [[Image:Icon20_ultrabayenh.png]]<br />UltraBay<br />Enhanced<br />
|-<br />
|'''UltraBay''' || yes || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay Thick''' || - || yes || [[Ultrabay Drive Adapter for Ultrabay II|Adapter]] || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay II''' || - || - || yes || - || - || - || - || - || -<br />
|-<br />
|'''UltraBay FX''' || - || - || - || yes || - || - || - || - || -<br />
|-<br />
|'''UltraslimBay''' || - || - || - || - || yes || - || - || - || -<br />
|-<br />
|'''UltraBay 2000''' || - || - || - || - || - || yes || yes || - || -<br />
|-<br />
|'''UltraBay Plus''' || - || - || - || - || - || - || yes || - || -<br />
|-<br />
|'''UltraBay Slim''' || - || - || - || - || - || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Slim Drive Adapter for Ultrabay 2000|Adapter]] || yes || yes<br />
|-<br />
|'''UltraBay Enhanced''' || - || - || - || - || - || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || [[Ultrabay Enhanced Drive Adapter for Ultrabay 2000|Adapter]] || - || yes<br />
|}<br />
<br />
===Characteristics===<br />
*UltraBay: no hot swapping<br />
*UltraBay Thick: thicker version of UltraBay to support CD-ROM drive<br />
*UltraBay II: supports hot swapping, blending has cut out edge on the right<br />
*UltraBay FX: the combined [[floppy]] drive and CD-ROM, DVD or CDRW mechanism found in the {{390}}/{{390E}}/{{390X}}<br />
*UltraSlimBay: supports hot swapping; frame, rectangle like blending<br />
*UltraBay 2000: supports hot swapping; frame, blending has cut-out edge on the right<br />
*UltraBay Plus: same as UltraBay 2000, but can take the [[UltraBay Plus Device Carrier]] which in turn can hold the [[UltraBay Plus c500 Cradle]] or the [[UltraBay Plus Numeric Keypad]]<br />
*UltraBay Slim: supports hot swapping; notably thinner than the UltraBay 2000, cut-out right edge in blending<br />
*UltraBay Enhanced: supports hot swapping; slightly thicker than UltraBay Slim, but accepts UltraBay Slim devices<br />
<br />
==Linux Support==<br />
The pinout switching is done by the BIOS and hardware, so that it is completely transparent to the operating system.<br />
*Floppy drives are supported by the standard floppy driver.<br />
*ZIP drive support is possible through the ide-disk driver.<br />
*IDE hard disks and optical drives are supported by the <tt>ide-disk</tt> or <tt>ata_piix</tt> driver in the linux kernel. SCSI emulation via <tt>ide-scsi</tt> is possible. <br />
*Batteries are automatically handled by the hardware, but can be controlled further by using [[tp_smapi]].<br />
*UltraBay Plus devices should be handled by the USB subsystem, but if the actual devices are is not known.<br />
<br />
===Unofficially compatible===<br />
A CDRW/DVD-ROM Superdrive (scavenged from a Mac iBook) will fit in an Ultrabay 2000. The original face won't fit in the bay, leaving a bare metal front. When the drive spins up, it blows a lot of air out. Maybe that's an anti-dust measure?<br />
<br />
In general, Ultrabay 2000 CD drives have a standard connector, and can therefore be replaced by most other 12.7 mm drives. You might have to do some cutting of the plastic face plate.<br />
<br />
The Ultraslim CD drives however, have a proprietary connector. You can not replace them with any 9.5 mm CD drive.<br />
<br />
===Hotswapping===<br />
See also [[How to hotswap UltraBay devices]].<br />
<br />
==External Sources==<br />
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50366 IBMs page on using a second hard drive adapter in the Ultrabay 2000 slot under Linux]<br />
<br />
{{footnotes|<br />
#IBM originally used the spelling UltraBay with a capital B and later switched to Ultrabay with a lower b. We are sticking with the capital B here.<br />
}}<br />
<br />
[[Category:Glossary]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=ThinkPad_X3_UltraBase&diff=34568ThinkPad X3 UltraBase2007-11-15T08:58:38Z<p>Vrossum: /* UltraBay Plus , not more than one battery */</p>
<hr />
<div>{| cellspacing="0" cellpadding="2" border="0"<br />
| style="vertical-align:top;" | __TOC__<br />
[[image:UltraBaseX3.gif|UltraBase X3]]<br />
| style="vertical-align:top;" | <div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
== IBM UltraBase X3 ==<br />
The IBM UltraBase X3 is a portable dock for the X30, X31 and X32 ThinkPads providing extra ports as well as a bay for an optical drive and a set of stereo speakers. Containing a full featured [[UltraBay|UltraBay Plus]] slot, it provides flexibility in drive choice as well as the option of a secondary battery for extended working time on the road. The Ultrabase X3 also features a battery slot on the underside that accepts the same battery as your X30 Series ThinkPad. The UltraBase X3 doesn't provide a second docking port as the original [[UltraBase]] did, hence you can't dock the UltraBase to any of the other docking solutions.<br />
<br />
=== Features ===<br />
* Passthrough ports:<br />
** Ethernet (RJ45)<br />
** Modem (RJ11)<br />
** USB<br />
** [[VGA Port|VGA]]<br />
** [[Serial Port|Serial (DB9-M)]]<br />
** [[Parallel Port|Parallel (DB25-F)]]<br />
** [[PS/2 Port|Combined PS/2 Mouse + Keyboard]]<br />
* [[UltraBay|Ultrabay Plus]]<br />
* Stereo speakers<br />
* Kensington security hole<br />
* Battery Slot (For Second X30 Series Battery)<br />
<br />
===Pros & Cons===<br />
* Positives: Expansion capability, portable<br />
* Negatives: makes the ThinkPad quite thick, no extra docking port<br />
* Compatibility: {{X30}}, {{X31}}, {{X32}}<br />
* Warranty: Three Years<br />
</div><br />
|}<br />
<br />
==UltraBay Plus==<br />
The [[UltraBay|UltraBay Plus]] slot in this dock is a full featured one and supports hot swapping with all UltraBay Plus and UltraBay 2000 drives. You can also feed it with the UltraBay Plus battery pack to extend the overall battery life time. However, you can not use the additional battery slot on the Ultrabase if you use the UltraBay Plus battery pack (a plastic pen prevents you).<br />
<br />
== Linux(-kernel) support ==<br />
<br />
In general, see [[How_to_hotswap_the_UltraBase]] and [[How_to_hotswap_UltraBay_devices]].<br />
<br />
This can be problematic under Debian, as the default kernel (2.6.18) do not support the IBM docks by default, as the IBM_DOCK and DOCK methods are not compatible. This is not a problem with 2.6.22 for some reason. Under 2.6.18, you need to recompile the Linux kernel with CONFIG_ACPI_IBM_DOCK enabled, and CONFIG_ACPI_DOCK disabled. You also need to hook a few scripts into the acpi events system.<br />
<br />
ibm-dock.sh:<br />
#!/bin/sh<br />
<br />
# acknowledge docking with the dockstation<br />
echo dock > /proc/acpi/ibm/dock<br />
<br />
ibm-undock.sh:<br />
#!/bin/sh<br />
<br />
# prepare the laptop for undocking with the dockstation<br />
<br />
echo undock > /proc/acpi/ibm/dock<br />
<br />
events/ibm-dock:<br />
<br />
event=ibm/dock GDCK 00000000 00000003<br />
action=/etc/acpi/ibm-dock.sh<br />
<br />
events/ibm-undock:<br />
<br />
event=ibm/dock GDCK 00000003 00000001<br />
action=/etc/acpi/ibm-undock.sh<br />
<br />
2.6.22-rc2 actually works without a flaw, without the above modifications, provided that the "bay" and "dock" modules are loaded at boot time.</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=34520Fglrx2007-11-13T17:03:42Z<p>Vrossum: New driver does not support (all?) figregl cards</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
== ATI fglrx driver ==<br />
This is a proprietary Linux binary-only driver for ATI graphic chips with support for 3D acceleration.<br />
<br />
Also see [[R300|opensource driver]] with 3D support<br />
|}<br />
<br />
==Availability / Project Homepage==<br />
Home page: http://ati.amd.com/support/drivers/linux/linux-radeon.html<br />
<br />
== Packages ==<br />
The ATI drivers have explicit permission for repackaging and redistribution of the Linux drivers. Many distributions are supported within the installer, and many more repackaged by external developers. Please visit the [http://wiki.cchtml.com/index.php/Category:Distributions Distribution Page at the Unofficial ATI driver Wiki]<br />
<br />
*{{Debian}}<br />
** These packages have been added to Debian unstable as <tt>fglrx-driver</tt>, so you can now apt-get them and use module-assistant to install.<br />
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, let it build Debian packages and proceed as usual. There's a [http://jroller.com/page/erAck?entry=lot_day_6_2_fglrx detailed description] available.<br />
** [http://wiki.cchtml.com/index.php/Debian_Installation_Guide Debian Howto]<br />
*{{SUSE}} packages: http://www.suse.de/~sndirsch/ati-installer-HOWTO.html<br />
*{{Gentoo}} {{cmdroot|emerge ati-drivers}}<br />
*{{Fedora}} 4 packages: http://rpm.livna.org<br />
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}<br />
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]<br />
*{{Fedora}} 5 packages: http://rpm.livna.org<br />
** For stock Fedora kernels: {{cmdroot|yum install xorg-x11-drv-fglrx}}<br />
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]<br />
*{{Fedora}} 7 packages: http://rpm.livna.org<br />
** The newest version of the driver (8.39.4) is supposed to work with Fedora 7, and is available from Livna.<br />
*{{Arch Linux}}<br />
:{{cmdroot|pacman -S ati-fglrx}} (kernel module for 2.6.15-ARCH)<br />
:{{cmdroot|pacman -S ati-fglrx-archck}} (kernel module for 2.6.15-archck)<br />
:{{cmdroot|pacman -S ati-fglrx-utils}} (xorg7 stuff and tools)<br />
*{{Ubuntu}}<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide Dapper Drake Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Breezy_Installation_Guide Breezy Badger Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Edgy_Installation_Guide Edgy Eft Howto]<br />
**[http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Feisty Fawn Howto]<br />
<br />
== Building for Xorg 7.0==<br />
To compile fglrx versions <= 8.24.8 for Xorg 7.0.0, fake Xorg 6.9.0 by <br />
:{{cmdroot|1=export X_VERSION=x690; sh ati-driver-installer-8.24.8-x86.run}}<br />
Next, move the various resulting libraries and modules from /usr/X11R6 to /usr/lib/xorg<br />
<br />
In {{path|/usr/src/ATI}} additional sources are installed for fireglcontrol and fgl_glxgears<br />
<br />
== Status ==<br />
Current version: 8.42.3 (23rd September 2007).<br />
Major changes:<br />
* 8.42.3: Composite support added enabling AIGLX and Beryl/Compiz on the desktop. Support for (most?) FireGl cards dropped (should be restored in upcoming versions)<br />
* 8.41.7: increased OpenGL performance on some Radeon Cards, size/position TV-out adjustments work for Radeon X1900 or higher, X crash when connecting external DFP display fixed <br />
* 8.40.4: some new TV out control options in CCC, another (non-exciting) maintenance release (see [http://www.phoronix.com/scan.php?page=article&item=804&num=1 Phoronix])<br />
* 8.39.4: kernel 2.6.22 support, TexturedVideo fix, aticonfig segfault fix (see 8.38.7 hotfix), to get rid of the "AMD Testing use only" logo, use [http://www.phoronix.com/forums/showpost.php?p=10641&postcount=44 this] workaround.<br />
* 8.38.7: hotfix release for "Using aticonfig --initial segfaults destroying xorg.conf file when run in X with Vesa driver.", search for "737-28261" on the ATI website.<br />
* 8.38.6: RedHat Enterprise Linux 5 support, Xserver crashes on moving video window between two monitors fixed, corruption when playing multiple vodeps with textured video fixed<br />
* 8.37.6: Xorg Server 1.3 support, CCC 1.0, crash when logging off from X fixed, Xv cropping bug fixed<br />
* 8.36.5: Kernel 2.6.20 support, CCC Beta 0.9 with localization<br />
* 8.35.5: Beta AMD Catalyst Control Center, X-Server termination from console does not result in a blank screen. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.35.5|fglrx patches section]]).<br />
* 8.34.8: Radeon Xpress 1250 support, X-Video on x86_64 fix, hibernation mode fix. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.34.8|fglrx patches section]]).<br />
* 8.33.6: X.Org 7.2 support, kernel 2.6.19 support, some fixes in the installer, 2 more bugfixes. Resume from suspend works if you make sure you have set "VbetoolPost no" and "EnableVbetool no" in your suspend to ram hibernate conf (/etc/hibernate/ram.conf on ubuntu/debian).<br />
* 8.32.5: support for X1650, X.Org 7.2 RC2 support, bugfixes. Suspend-to-ram is broken with specific cards, *no* 2.6.19 support (see [[Problems_with_fglrx#fglrx_8.32.5|fglrx patches section]]).<br />
* 8.31.5: no new features, only bugfixes. Of note, for some users, this version breaks suspend-to-ram and suspend-to-disk.<br />
* 8.30.3: no new features, only bugfixes<br />
* 8.29.6: Linux 2.6.18 support, dropped support for Radeon 8500/9000/9100/9200/9250 (both, mobile and normal versions)<br />
* 8.28.8: Display Switching Support for ThinkPads, ATI Pairmode support, Retaining display device state between restarts, Support for Radeon Xpress 1200, 1250, and 1300<br />
* 8.27.10: X.org 7.1 support, Fedora Core package support<br />
* 8.26.18: support for dynamically attached DFPs and Thermal Event Power Management (both via daemon), minor bug fixes<br />
* 8.25.18: Xorg 7.0 support, FireGLâ„¢V5xxx/V7xxx support, Dynamic Display Management, fixed a lot of critical bugs.<br />
* 8.24.8: support for X1300, X1400, X1600, X1800 (generic and mobility) and 3D accelerated video playback on Avivo<br />
* 8.23.7: support for X850 and X800, OpenGL 2.0 Enhancement, FSAA for some chips<br />
* 8.22.5: added kernel 2.6.15 support -- patch no longer required<br />
* 8.21.7: initial OpenGL 2.0 support<br />
* 8.20.8: fixed resume issues, fixed compile problems with kernels 2.6.13 and 2.6.14<br />
* 8.19.10: has added suspend / resume and dynamic GPU power management support. Using vbetool no longer required.<br />
<br />
== Known problems and solutions ==<br />
See [[Problems with fglrx]].<br />
== User experience ==<br />
=== Speed ===<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
Compared to the old drivers, approximately 40% speed gain have been noticed with fglrx. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (via {{key|ctrl}}{{key|alt}}{{key|plus}}, {{key|ctrl}}{{key|alt}}{{key|minus}}), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using the open source radeon driver: 1200 FPS for glxgears{{footnote|1}}!<br />
<br />
However the situation seems to be changing significantly as time goes on. With recent x11-drm-20060608 driver (gentoo) and thinkpad t42 (ati 9600) the speed is confirmed as 1900fps and stable. As of October 2007 there is dramatic improvement in the open source 3d drivers in speed and stability.<br />
<br />
=== 3D acceleration ===<br />
<br />
According to [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] you need these options:<br />
<br />
Section "Module"<br />
...<br />
Load "GLcore"<br />
Load "glx"<br />
Load "dri"<br />
...<br />
EndSection<br />
<br />
# Of course you need to activate the driver<br />
Section "Device"<br />
...<br />
Driver "fglrx"<br />
EndSection<br />
<br />
Don't forget to load the module <tt>fglrx</tt> (<tt>modprobe fglrx</tt>). Under Debian the module can be placed in <tt>/etc/modules</tt>.<br />
<br />
With fglrx drivers prior to 8.42.3 will need to disable composite to enable 3D DRI acceleration. To do this, add an extra Extensions section (if necessary) containing:<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable" #make DRI work with fglrx.<br />
EndSection<br />
<br />
If you are unsure whether you have DRI running, issue <tt>glxinfo | grep -i direct</tt> after disabling composite. Note, this <br />
<br />
{{NOTE|1=Video overlay acceleration may be disabled when 3D acceleration is enabled. The following comment from the xorg.conf file bundled with the fglrx driver indicates that:<br />
# === OpenGL Overlay ===<br />
# Note: When OpenGL Overlay is enabled, Video Overlay<br />
# will be disabled automatically<br />
Option "OpenGLOverlay" "1"<br />
However, you can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. This has nothing to do with the acceleration of 2D drawing primitives. Further, your mileage on performance may vary depending on what card you have. The open source drivers don't support newer cards, while the ATI drivers don't support older cards.<br />
<br />
You may be able to preserve VideoOverlay acceleration if you explicitly remove the OpenGLOverlay using:<br />
<br />
Option "VideoOverlay" "True" and Option "OpenGLOverlay" "False". See [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] for detail.}}<br />
<br />
=== Power saving ===<br />
Power saving is much better than with the <tt>radeon</tt> driver, but doesn't work in dual-screen configuration (see [[How to make use of Graphics Chips Power Management features]]).<br />
<br />
=== Suspending with fglrx ===<br />
<br />
On a ThinkPad T42 with Kernel 2.6.19 with Software Suspend 2 and R60 with Kernel 2.6.18-suspend2-r1 (Gentoo) , the following addition to <tt>/etc/hibernate/suspend2.conf</tt> is required:<br />
<br />
# For fglrx<br />
ProcSetting extra_pages_allowance 20000<br />
<br />
=== Display Switching (Dynamic Display Management) ===<br />
<br />
Version 8.25.18 introduces a new feature: Dynamic Display Management. It allows display switching on-the-fly.<br />
<br />
To list all connected and enabled monitors:<br />
:{{cmdroot|1=aticonfig --query-monitor}}<br />
<br />
To switch displays:<br />
:{{cmdroot|1=aticonfig --enable-monitor=STRING,STRING}}, where STRING can be: none, lvds, crt1, crt2, tv, tdms1, tdms2<br />
<br />
Only 2 displays can be enabled at the same time. Any displays that are not on the list will be disabled.<br />
<br />
The '''Catalyst Control Center''', which comes with the driver (at least from Livna in Fedora Core 6) can be used to do this switching. It also does various other kinds of display managements. However, the version that comes with 8.39.4 doesn't seem to handle switching into Big Desktop mode, does anyone know how to get this to work? The control center also complains a lot about rebooting, but rebooting doesn't seem to be required. Does anyone have decent documentation for the control center?<br />
<br />
== Useful links == <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www.rage3d.com/content/articles/atilinuxhowto/ ATI Radeon Linux How-To]<br />
* [http://www.rage3d.com/board/forumdisplay.php?f=61&daysprune=30&order=asc&sort=title Rage3D Linux Discussion Forum]<br />
* [http://www.driverheaven.net/forumdisplay.php?f=103 Radeon Driver Forum at Driverheaven]<br />
* [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html Gentoo ATI Radeon FAQ]<br />
* [http://forums.gentoo.org/viewtopic-t-374745-highlight-t42+ati+dri.html Gentoo T42 ATI. DRI + xorg driver]<br />
* [http://ati.cchtml.com/ Unofficial community ATI bugzilla] - tracks bugs in the driver. Might be monitored by ATI ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]).<br />
<br />
== ThinkPads that may be supported ==<br />
Supported chips, as found in select IBM ThinkPads:<br />
{{NOTE|fglrx version 8.29.6 discontinued support for Radeon 9200 and earlier.}}<br />
* [[ATI Mobility FireGL 9000]]<br />
** {{T40p}}<br />
* [[ATI Mobility FireGL T2]]<br />
** {{R50p}}<br />
** {{T41p}}, {{T42p}}<br />
* [[ATI Mobility FireGL V3200]]<br />
** {{T43p}}<br />
* [[ATI Mobility Radeon 9000]]<br />
** {{R50}}, {{R51}}<br />
** {{T40}}, {{T41}}, {{T42}}<br />
* [[ATI Mobility Radeon 9600]]<br />
** {{T42}}<br />
* [[ATI Mobility Radeon X300]]<br />
** {{R52}}<br />
** {{T43}}<br />
** {{Z60m}}<br />
* [[ATI Mobility Radeon Xpress 200M]]<br />
** {{R51e}}<br />
* [[ATI Mobility Radeon X600]]<br />
** {{Z60m}}<br />
* [[ATI Mobility Radeon X1400]]<br />
** {{T60}}, {{R60}}, {{Z61m}}<br />
* [[ATI Mobility FireGL V5200]]<br />
** {{T60p}}, {{Z61p}}<br />
<br />
== ThinkPads that are NOT supported by fglrx==<br />
Unsupported chips, as found in select IBM ThinkPads:<br />
* [[ATI Mobility Radeon 7500]]<br />
** {{R40}}<br />
** {{T30}}<br />
** {{T42}}<br />
<br />
{{footnotes|<br />
#Note that glxgears isn't a benchmark tool, it's so simple that its FPS values is without any meaning... you can only compare glxgears using the same drivers/machine, if you change any of then you can have higher/lower values and in real life programs/games happen to have the opposite effects. Think in terms of a car engines rpms: higher rpms in the same car usually means a faster car, change anything and it's meaningless, ie: gears, truck, wheel size, etc. make it useless.<br />
}}<br />
[[Category:Drivers]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=How_to_configure_acpid&diff=28881How to configure acpid2007-03-23T14:04:23Z<p>Vrossum: /* Troubleshooting */</p>
<hr />
<div>__TOC__<br />
==Introduction==<br />
Basically, [[acpid]] just executes scripts residing in {{path|/etc/acpi/actions}}. Which script to launch at which event is configured in several files in {{path|/etc/acpi/events}}. All actions are documented in {{path|/var/log/acpid}}.<br />
<br />
==Sources of Information==<br />
*{{cmduser|man acpid}} holds detailed information on how to configure acpid.<br />
*The [[ibm-acpi]] package includes example scripts in the {{path|config}} folder inside the tarball. They are a good starting point to adjust them to your needs.<br />
*You also might want to have a look at the [[Configs#ACPI | ACPI section of the Configs page]] or the [[:Category:Scripts|Scripts]] repository.<br />
*And you can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].<br />
<br />
==Example: go to sleep on lid close==<br />
To make the ThinkPad go to sleep when you close the lid, you need to add<br />
an event handler for the lid event and an action script that takes care<br />
of going to sleep and resuming.<br />
<br />
===Event Script===<br />
The event script needs to be created within {{path|/etc/acpi/events}} and can have any name you like.<br />
In this case we call it lid because it will trigger the lid event. Do {{cmdroot|vi /etc/acpi/events/lid}} and make it look like this:<br />
event=button/lid<br />
action=/etc/acpi/actions/sleep.sh %e<br />
<br />
The "event" line is a regular expression specifying the events we're<br />
interested in. You can determine what the event strings are from looking at<br />
{{path|/var/log/acpid}} after trying to suspend, close the lid, etc. .<br />
You can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].<br />
<br />
The "action" line is the command to be executed when these events are<br />
dispatched. In this example we call the {{path|sleep.sh}} script residing in {{path|/etc/acpi/actions}} and pass the event description text using the %e placeholder.<br />
<br />
For the script you can use the <tt>hibernate</tt> script of [http://www.suspend2.net/ Software Suspend 2] (it is independent of the [[Software Suspend 2|suspend-to-disk]] functionality), or any of many examples available on the web, such as the one below.<br />
<br />
{{NOTE|To make your changes take effect after adding or modifying the events files you must do a <tt>kill -SIGHUP `pidof acpid`</tt>}}<br />
<br />
===Action Script===<br />
Our example {{path|/etc/acpi/actions/sleep.sh}} script looks as follows:<br />
<br />
#!/bin/sh<br />
<br />
# if launched through a lid event and lid is open, do nothing<br />
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0<br />
<br />
# remove USB 1.1 driver<br />
rmmod uhci_hcd<br />
<br />
# sync filesystem and clock<br />
sync<br />
/sbin/hwclock --systohc<br />
<br />
# switch to console<br />
FGCONSOLE=`fgconsole`<br />
chvt 6<br />
/usr/sbin/radeontool light off<br />
<br />
# go to sleep<br />
sleep 5 && echo -n "mem" > /sys/power/state<br />
<br />
# readjust the clock (it might be off a bit after suspend)<br />
/sbin/hwclock --adjust<br />
/sbin/hwclock --hctosys<br />
<br />
# reload USB 1.1 driver<br />
modprobe uhci_hcd<br />
<br />
# turn on the backlight and switch back to X<br />
radeontool light on<br />
chvt $FGCONSOLE<br />
<br />
{{NOTE|This parts of this script are now part of some distributions, like Debian Etch and you probably don't need to add this script. Look into /etc/acpi/lid.sh, for example.}}<br />
<br />
====Explanations====<br />
*The lid generates an event for both opening and closing thus requiring that we check its state and only act if it's closed.<br />
*There have been problems encountered with the USB devices not working properly after a resume from suspend. To circumvent those we remove the USB driver prior to suspend and reload it afterwards.<br />
*Note that the {{cmdroot|echo -n "mem" > /sys/power/state}} line does not return until we are revived. So there is only one event generated and there is no need to check the state of anything.<br />
*The console switching code in this script is a special solution for [[Problem with LCD backlight remaining on during ACPI sleep|a problem where the backlight doesn't switch off]] on the {{T30}} and some other models. Before going to sleep, these models switch to console mode which causes the backlight to come back on. So we preemptively switch to console mode and turn off the backlight using [[radeontool]] before going to sleep.<br />
<br />
==Screen blanking script==<br />
<br />
You might want to be able to switch of the screen using Fn-f3.<br />
This is not completely straightforward.<br />
You will first need to give permission to the script to muck around with your screen<br />
<br />
xhost +local:root <br />
<br />
/etc/acpi/events/sleepbtn <br />
contains<br />
event=(button[ /]sleep|ibm/hotkey HKEY 00000080 00001004)<br />
action=/etc/acpi/sleepbtn.sh<br />
<br />
And /etc/acpi/sleepbtn.sh is <br />
<br />
#!/bin/bash<br />
<br />
# simple script to turn the display on or off #<br />
# By Mahram Z.Foadi #<br />
# Oct 22 2005 # <br />
# thank you linuxquestions.org #<br />
# # <br />
# the following lines must be present in your "/etc/acpi/events/" files. Some #<br />
# systems already have a file called sample.conf in the mentioned directory #<br />
# rename it to something more meaningful (i.e. acpid.conf) and these lines to #<br />
# the end of it (you don't HAVE to rename it, you can even create a new file #<br />
# and call it /etc/acpi/events/lid.conf with the 2 lines in it. If you intend #<br />
# to put this file anywhere other than /sbin/lidevent, make sure you make the #<br />
# proper changes in the "action" line below. For example if you are going to #<br />
# save this script as /usr/bin/mylid.sh then the action line should be: #<br />
# action=/usr/bin/mylid.sh #<br />
# be sure both files are executable, writable, and owned by root ONLY because #<br />
# the acpid daemon is most likely running as root in your system #<br />
# #<br />
# ---- insert the two lines below in /etc/acpi/events/acpid.conf ---- #<br />
# event=button/lid.* #<br />
# action=/sbin/lidevent #<br />
#-----------------------------------------------------------------------------#<br />
<br />
# default display on current host<br />
DISPLAY=:0.0<br />
<br />
# find out if DPMS is enabled<br />
STATUS=`xset -display $DISPLAY -q | grep -e 'DPMS is'`<br />
<br />
# enable DPMS if disabled<br />
if [ "$STATUS" == " DPMS is Disabled" ]<br />
then<br />
echo "Enabling DPMS ..."<br />
xset -display $DISPLAY +dpms<br />
fi<br />
<br />
# find out if monitor is on<br />
STATUS=`xset -display $DISPLAY -q | grep 'Monitor'`<br />
<br />
if [ "$STATUS" == " Monitor is On" ]<br />
then<br />
echo "[`date`] Turning display OFF"<br />
xset -display $DISPLAY dpms force off<br />
else<br />
echo "[`date`] Turning display ON" # shows up in log<br />
xset -display $DISPLAY dpms force on # turn monitor on<br />
xset -display $DISPLAY s activate # un-blank monitor<br />
fi<br />
<br />
#clean up<br />
unset STATUS<br />
<br />
# comment this line out if you're manually running this script from a shell (put a # in front of it)<br />
unset DISPLAY<br />
<br />
exit 0<br />
<br />
An alternative is to call radeontool (if you have a radeon videocard only of course)<br />
<br />
<br />
==Troubleshooting==<br />
*If something doesn't work, your first action should be a {{cmdroot|tail /var/log/acpid}}. It will tell you a lot about what is going on. If it has "Permission denied" errors, check the permissions of your {{path|/etc/acpi/actions}} scripts (especially make sure that the executable bit is set). Also check the permissions for other involved files like i.e. device nodes.<br />
*For further problems look at the [[Problems with ACPI suspend-to-ram|Problems with ACPI suspend-to-ram page]].<br />
<br />
<br />
[[Category:770X]] [[Category:770Z]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:Z60t]] [[Category:Z60m]] [[Category:TransNote]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=R300&diff=27591R3002007-01-10T14:35:21Z<p>Vrossum: /* Packages */</p>
<hr />
<div>== Status ==<br />
<br />
The latest CVS version (see [[#Experimental stand-alone installation|Experimental stand-alone installation]]) provides good performance, but is not stable (e.g., it [https://bugs.freedesktop.org/show_bug.cgi?id=6991 hangs on some applications]). <br />
<br />
== R300 drivers with DRI support ==<br />
In post-2.6.13 development kernels (and also 2.6.13-mm3), DRM support for the [http://r300.sourceforge.net/ R300] chips from ATI has been included. Together with a bleeding-edge version of [http://www.mesa3d.org/ Mesa] (at least 6.3.2), this will allow 3D acceleration support for systems having a chip like this without the need for the ATI binary only driver ([[Fglrx]]). The latest beta releases of [http://www.x.org/ X.Org] for 6.9/7.0 already have Mesa 6.3.2, but building the R300 DRI drivers is disabled by default.<br />
<br />
== Kernel configuration ==<br />
You need to build AGP support with<br />
# CONFIG_AGP=y<br />
# CONFIG_AGP_INTEL=y #for a ThinkPad T41p<br />
and the Radeon DRM support with <br />
# CONFIG_DRM=y<br />
# CONFIG_DRM_RADEON=y<br />
Alternatively, can also build modules instead of including the code into the kernel. The modules will then be automatically loaded when X starts up.<br />
<br />
If everything works well, the device /dev/dri/card0 should show up.<br />
<br />
== Mesa ==<br />
If your distribution does not offer binary packages of the current Mesa development packages, you need to build them yourself. It might also be possible that the DRI driver is included in your X.Org packages, just look out for a file like {{path|/usr/X11R6/lib/modules/dri/r300_dri.so}}.<br />
<br />
== X configuration ==<br />
You will need to load the dri and GLcore extensions with<br />
# Section "Module"<br />
# ...<br />
# module "dri"<br />
# module "GLcore"<br />
# ...<br />
# EndSection<br />
Note: In Xorg 7.0 you don't need to load GLCore manually anmore<br />
<br />
My radeon configuration looks like this<br />
# Section "Device"<br />
# Identifier "firegl"<br />
# Driver "radeon"<br />
# BusID "PCI:1:0:0"<br />
# ....<br />
# Option "AGPFastWrite" "off" # "on" freezes my laptop<br />
# Option "AGPMode" "4" # this value depends on your hardware, this one is for a T41p<br />
# Option "DynamicClocks" "on"<br />
# Option "ColorTiling" "on"<br />
# EndSection<br />
<br />
X will silently ignore if DRI cannot be activated for your card, so you should check yor X logfile. Just search for DRI and/or DRM. Afterwards, you might want to do the usual glxinfo/glxgears magic.<br />
<br />
== Packages ==<br />
*{{Debian}} Packages: http://packages.debian.org/libgl1-mesa-dri<br />
*{{Gentoo}}:<br />
:Emerge the latest Xorg (7.1). The opensource driver is in cvs since version 7.0<br />
:Enable agp suuport in a kernel:<br />
::Device Drivers ---><br />
:::Character devices ---><br />
::::<M> /dev/agpgart (AGP Support)<br />
::::<M> Intel 440LX/BX/GX, I8xx and E7x05 chipset support<br />
:Add the following two lines to {{path|/etc/modules.autoload.d/kernel-2.6}}:<br />
agpgart<br />
intel-agp<br />
:or compile as a kernel.<br />
:To enable 3D support, emerge latest x11-base/x11-drm<br />
echo "x11-base/x11-drm" >> /etc/portage/package.keywords<br />
emerge x11-base/x11-drm<br />
*{{Fedora}} 5<br />
The development repository has a stable implementation.<br />
To install do<br />
:yum --enablerepo=development update 'xorg*' 'libX*'<br />
<br />
== Experimental stand-alone installation ==<br />
If you want to test the latest r300 driver and X server without touching your main X tree, see [[How to compile an experimental X server]].<br />
<br />
== Performance ==<br />
With 2.6.14-rc1 + Mesa 6.3.2, glxgears (the dubious Linux 3D benchmark) gives ~2200 FPS on my ThinkPad T41p with a FireGL Mobility T2 and a 1.7GHz Pentium M, 1GB RAM.<br />
<br />
There is to note that the Color-depth has great effect on this value.<br />
on my R50p with 24Bit I get about 2k fps, with 16Bit i get about 1k-1.5k fps<br />
<br />
With 2.6.15 + Mesa 6.3.2, glxgears gives ~1480 FPS on a ThinkPad T43 with a Radeon Mobility X300 and a 1.86GHz Pentium M, 512MB RAM, when AGPMode=8, EnablePageFlip=on, AGPFastWrite=on and RenderAccel=on. Adding AccelMethod=EXA reduces to 700 FPS but makes the Composite Extension be usable.<br />
<br />
glxgear output:<br />
9607 frames in 5.0 seconds = 1921.285 FPS<br />
9574 frames in 5.0 seconds = 1914.716 FPS<br />
9510 frames in 5.0 seconds = 1901.832 FPS<br />
9643 frames in 5.0 seconds = 1928.568 FPS<br />
9676 frames in 5.0 seconds = 1934.910 FPS<br />
9553 frames in 5.0 seconds = 1910.021 FPS<br />
<br />
== Troubleshooting ==<br />
* Useful thread about two possible gotchas in Ubuntu Dapper: http://www.ubuntuforums.org/showthread.php?t=110008&page=5 (in short: mv /usr/X11R6/lib/modules/dri /usr/X11R6/lib/modules/dri.old;ln -s /usr/lib/dri /usr/X11R6/lib/modules/dri;apt-get remove --purge xorg-driver-fglrx)<br />
<br />
== Useful links ==<br />
* [http://dri.freedesktop.org/wiki/R300_20Portal R300 Portal on the DRI Wiki] - benchmarks, sample configs and other tips<br />
* [http://r300.sourceforge.net The original R300 development page]<br />
* [http://www.mesa3d.org Mesa 3D graphics library]<br />
* [http://wiki.x.org/wiki/ChangesSince68 Rough changelog for X.Org 6.9]<br />
<br />
== ThinkPads that may be supported ==<br />
Supported chips, as found in select IBM ThinkPads (please add your own ones!):<br />
* [[ATI Mobility Radeon 9600]]<br />
** {{T42}}<br />
* [[ATI Mobility FireGL T2]]<br />
** {{R50p}}<br />
** {{T41p}}, {{T42p}}<br />
* [[ATI Mobility Radeon X300]]<br />
** {{R52}}<br />
** {{T43}}<br />
** {{Z60m}}<br />
* [[ATI Mobility FireGL M24 1T]]<br />
** {{T43p}}</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=R300&diff=24604R3002006-09-11T16:53:16Z<p>Vrossum: /* Packages */</p>
<hr />
<div>== Status ==<br />
<br />
The latest CVS version (see [[#Experimental stand-alone installation|Experimental stand-alone installation]]) provides good performance, but is not stable (e.g., it [https://bugs.freedesktop.org/show_bug.cgi?id=6991 hangs on some applications]). <br />
<br />
== R300 drivers with DRI support ==<br />
In post-2.6.13 development kernels (and also 2.6.13-mm3), DRM support for the [http://r300.sourceforge.net/ R300] chips from ATI has been included. Together with a bleeding-edge version of [http://www.mesa3d.org/ Mesa] (at least 6.3.2), this will allow 3D acceleration support for systems having a chip like this without the need for the ATI binary only driver ([[Fglrx]]). The latest beta releases of [http://www.x.org/ X.Org] for 6.9/7.0 already have Mesa 6.3.2, but building the R300 DRI drivers is disabled by default.<br />
<br />
== Kernel configuration ==<br />
You need to build AGP support with<br />
# CONFIG_AGP=y<br />
# CONFIG_AGP_INTEL=y #for a ThinkPad T41p<br />
and the Radeon DRM support with <br />
# CONFIG_DRM=y<br />
# CONFIG_DRM_RADEON=y<br />
Alternatively, can also build modules instead of including the code into the kernel. The modules will then be automatically loaded when X starts up.<br />
<br />
If everything works well, the device /dev/dri/card0 should show up.<br />
<br />
== Mesa ==<br />
If your distribution does not offer binary packages of the current Mesa development packages, you need to build them yourself. It might also be possible that the DRI driver is included in your X.Org packages, just look out for a file like {{path|/usr/X11R6/lib/modules/dri/r300_dri.so}}.<br />
<br />
== X configuration ==<br />
You will need to load the dri and GLcore extensions with<br />
# Section "Module"<br />
# ...<br />
# module "dri"<br />
# module "GLcore"<br />
# ...<br />
# EndSection<br />
Note: In Xorg 7.0 you don't need to load GLCore manually anmore<br />
<br />
My radeon configuration looks like this<br />
# Section "Device"<br />
# Identifier "firegl"<br />
# Driver "radeon"<br />
# BusID "PCI:1:0:0"<br />
# ....<br />
# Option "AGPFastWrite" "off" # "on" freezes my laptop<br />
# Option "AGPMode" "4" # this value depends on your hardware, this one is for a T41p<br />
# Option "DynamicClocks" "on"<br />
# Option "ColorTiling" "on"<br />
# EndSection<br />
<br />
X will silently ignore if DRI cannot be activated for your card, so you should check yor X logfile. Just search for DRI and/or DRM. Afterwards, you might want to do the usual glxinfo/glxgears magic.<br />
<br />
== Packages ==<br />
*{{Debian}} Packages: http://packages.debian.org/libgl1-mesa-dri<br />
*{{Gentoo}}:<br />
:Emerge the latest Xorg (7.1). The opensource driver is in cvs since version 7.0<br />
:Enable agp suuport in a kernel:<br />
::Device Drivers ---><br />
:::Character devices ---><br />
::::<M> /dev/agpgart (AGP Support)<br />
::::<M> Intel 440LX/BX/GX, I8xx and E7x05 chipset support<br />
:Add the following two lines to {{path|/etc/modules.autoload.d/kernel-2.6}}:<br />
agpgart<br />
intel-agp<br />
:or compile as a kernel.<br />
:To enable 3D support, emerge latest x11-base/x11-drm<br />
echo "x11-base/x11-drm" >> /etc/portage/package.keywords<br />
emerge x11-base/x11-drm<br />
*{{Fedora}}<br />
The development repository has a stable implementation.<br />
To install do<br />
:yum --enablerepo=development update 'xorg*' 'libX*'<br />
<br />
== Experimental stand-alone installation ==<br />
If you want to test the latest r300 driver and X server without touching your main X tree, see [[How to compile an experimental X server]].<br />
<br />
== Performance ==<br />
With 2.6.14-rc1 + Mesa 6.3.2, glxgears (the dubious Linux 3D benchmark) gives ~2200 FPS on my ThinkPad T41p with a FireGL Mobility T2 and a 1.7GHz Pentium M, 1GB RAM.<br />
<br />
There is to note that the Color-depth has great effect on this value.<br />
on my R50p with 24Bit I get about 2k fps, with 16Bit i get about 1k-1.5k fps<br />
<br />
With 2.6.15 + Mesa 6.3.2, glxgears gives ~1480 FPS on a ThinkPad T43 with a Radeon Mobility X300 and a 1.86GHz Pentium M, 512MB RAM, when AGPMode=8, EnablePageFlip=on, AGPFastWrite=on and RenderAccel=on. Adding AccelMethod=EXA reduces to 700 FPS but makes the Composite Extension be usable.<br />
<br />
glxgear output:<br />
9607 frames in 5.0 seconds = 1921.285 FPS<br />
9574 frames in 5.0 seconds = 1914.716 FPS<br />
9510 frames in 5.0 seconds = 1901.832 FPS<br />
9643 frames in 5.0 seconds = 1928.568 FPS<br />
9676 frames in 5.0 seconds = 1934.910 FPS<br />
9553 frames in 5.0 seconds = 1910.021 FPS<br />
<br />
== Troubleshooting ==<br />
* Useful thread about two possible gotchas in Ubuntu Dapper: http://www.ubuntuforums.org/showthread.php?t=110008&page=5 (in short: mv /usr/X11R6/lib/modules/dri /usr/X11R6/lib/modules/dri.old;ln -s /usr/lib/dri /usr/X11R6/lib/modules/dri;apt-get remove --purge xorg-driver-fglrx)<br />
<br />
== Useful links ==<br />
* [http://r300.sourceforge.net The original R300 development page]<br />
* [http://www.mesa3d.org Mesa 3D graphics library]<br />
* [http://wiki.x.org/wiki/ChangesSince68 Rough changelog for X.Org 6.9]<br />
<br />
== ThinkPads that may be supported ==<br />
Supported chips, as found in select IBM ThinkPads (please add your own ones!):<br />
* [[ATI Mobility Radeon 9600]]<br />
** {{T42}}<br />
* [[ATI Mobility FireGL T2]]<br />
** {{R50p}}<br />
** {{T41p}}, {{T42p}}<br />
* [[ATI Mobility Radeon X300]]<br />
** {{R52}}<br />
** {{T43}}<br />
** {{Z60m}}<br />
* [[ATI Mobility FireGL M24 1T]]<br />
** {{T43p}}</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Additional_options_for_the_radeon_driver&diff=24409Additional options for the radeon driver2006-08-30T20:52:29Z<p>Vrossum: /* External Monitors */</p>
<hr />
<div>Options for the radeon driver are documented on the radeon(4x) man page.<br />
<br />
==External Monitors==<br />
<br />
First of all, suppose you want to plug in your laptop into a projector occasionally, but you<br />
don't want to restart X when you do so.<br />
The easiest thing is to not use any of the CRT2 options and use <br />
<br />
Option "MonitorLayout" "LVDS,NONE"<br />
<br />
The vga port will carry the same signal as the laptop display<br />
(at least on my T42p). If the projector does not support the resolution, you can change it using xrandr.<br />
<br />
===Using Xinerama===<br />
<br />
You can use '''MergedFB''' to provide dualhead '''Xinerama'''-like setups. MergedFB's pseudo-Xinerama is not Xorg server's Xinerama. You don't have to enable Xorg server's Xinerama to use MergedFB's pseudo-Xinerama. However, applications compiled with Xinerama support (Gentoo users USE="xinerama") can interpret pseudo-Xinerama hints, for example, to maximize to a single monitor instead of spanning two monitors.<br />
<br />
The following (partial) '''Xorg''' config will make the Radeon card use '''1024x768''' on the internal lcd display and '''1280x1024''' on the external ('''Note''': only one screen/monitor section is needed (it controls the setup of the internal monitor) even though we have two displays):<br />
'''N.B.:''' Modes used in the ''MetaModes'' also have to be present in the ''screen'' modes section.<br />
<br />
Section "Device"<br />
Identifier "ATI"<br />
Driver "radeon"<br />
'''# accelration'''<br />
Option "AGPMode" "4"<br />
Option "EnablePageFlip" "on"<br />
Option "RenderAccel" "on"<br />
'''# enable (partial) PowerPlay features'''<br />
Option "DynamicClocks" "on"<br />
'''# use bios hot keys on thinkpad (aka fn+f7)'''<br />
Option "BIOSHotkeys" "on"<br />
'''# enable radeon specific xinerama'''<br />
Option "MergedFB" "true"<br />
Option "CRT2Position" "RightOf"<br />
Option "CRT2Hsync" "50-75"<br />
Option "CRT2VRefresh" "30-82"<br />
Option "MetaModes" "1024x768-1280x1024"<br />
Option "MergedNonRectangular" "true"<br />
BusID "PCI:1:0:0"<br />
EndSection<br />
Section "Monitor"<br />
Identifier "InternalLCD"<br />
Option "DPMS"<br />
EndSection<br />
Section "Screen"<br />
Identifier "Default Screen"<br />
Device "ATI"<br />
Monitor "InternalLCD"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Depth 24<br />
Modes "1024x768"<br />
EndSubSection<br />
EndSection<br />
<br />
Note: The '''CRT2''' directives always applies for the external monitore regardless of type (LCD, CRT...). The option '''MergedNonRectangular''' is needed to force the screens into two different sizes.<br />
<br />
===External Monitors and Docking Stations/Port Replicators===<br />
I seems that '''Xorg''' incorectly discovers the external displays when connected to a docking station/port replicator - the only solution to this problem (at least that I know of) is to start the laptop (and boot all the way into X) prior to inserting it in the dock.<br />
<br />
It also happens that if you are attempting to use the mergedFB trick to<br />
do dual head with out a docking station, you have to start X on the laptop<br />
LCD first, then plug a monitor into the VGA port. If the external monitor<br />
is already plugged in, the internal LCD will be blank.<br />
<br />
===External Monitors and FireGL Boards with x.org 7===<br />
x.org release 7, the modular release, broke mergedfb mode with FireGL boards (t4xp systems). Dual screen displays hard locked the machine in certain cases. This is fixed in x.org cvs. Fedora Core 5 (and possibly other distros using x.org 7) can get a new version of radeon_drv.so [http://www.marcuswatkins.net/firegl_xorg7_fedora.html here].<br />
<br />
==AGP speed==<br />
<br />
By default, the open source radeon driver forces 1x AGP speed. Quote from the developers:<br />
<br />
tuning to the highest speed possible has caused hangs on some boxes, with no<br />
discernable pattern, so we default to 'slow but safe' whilst giving the option<br />
to go fast if the user wants to try it.<br />
<br />
<br />
Higher speeds can be enabled by adding '''Option "AGPMode" "X"''' (where X is a number) in the '''Device''' section in {{path|/etc/X11/xorg.conf}}.<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "radeon"<br />
VendorName "IBM Thinkpad"<br />
BoardName "ATIdd Mobility FireGL 7800"<br />
'''Option "AGPMode" "4"'''<br />
EndSection<br />
<br />
<br />
With this option enabled (set to 4x speed), the X11 server should print ({{path|/var/log/Xorg.0.log}}):<br />
<br />
(**) RADEON(0): Option "AGPMode" "4"<br />
(**) RADEON(0): Using AGP 4x mode<br />
<br />
<br />
==AGP Fast Writes==<br />
<br />
By default, the open source radeon driver disables AGP Fast Writes. Fast Writes can be enabled by adding '''Option "AGPFastWrite" "yes"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}.<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "radeon"<br />
VendorName "IBM Thinkpad"<br />
BoardName "ATI Mobility FireGL 7800"<br />
'''Option "AGPFastWrite" "yes"'''<br />
EndSection<br />
<br />
<br />
==Dynamic Clock scaling==<br />
<br />
Please see:<br />
<br />
*[[How to make use of Graphics Chips Power Management features]] <tt>(save even more battery power)</tt><br />
*[https://bugs.freedesktop.org/show_bug.cgi?id=2187 Xorg bug] <tt>DynamicClocks may hang your machine</tt><br />
<br />
==Color Tiling==<br />
<br />
ColorTiling is supposed to be enabled by default. But, it looks like setting it explicitely to "on" increases the FPS in glxgears.<br />
<br />
Option "ColorTiling" "on"<br />
<br />
==Acceleration Architecture==<br />
<br />
By default, the XAA architecture is used. EXA is newer and supposed to have better performance. It looks like it reduces the FPS in glxgears (maybe because it disables Page Flip) but makes the Composite extension be fast.<br />
<br />
Option "AccelMethod" "EXA"<br />
<br />
==Page Flip==<br />
<br />
Page Flip increases performance but is not always supported. It will be disabled if the EXA architecture is used.<br />
<br />
Option "EnablePageFlip" "on"<br />
<br />
==Video overlay==<br />
<br />
When the video overlay is used (e.g., by most video players) in dual-screen configuration, the content will be shown only on one head (LCD or CRT) and the other will display a blank rectangle. To control which head displays the video, use the following:<br />
<br />
Option "OverlayOnCRTC2" "on"<br />
<br />
To switch on the fly, use these commands:<br />
<br />
:{{cmd|xvattr -a XV_SWITCHCRT -v 0|}} &nbsp; (LCD)<br />
:{{cmd|xvattr -a XV_SWITCHCRT -v 1|}} &nbsp; (CRT)<br />
<br />
{{HINT|You can configure [[acpid]] to execute these commands automatically when the lid is opened or closed.}}<br />
<br />
== Related Links ==<br />
*[http://www.x.org/X11R6.8.2/doc/radeon.4.html xorg 6.8.2 Radeon manual page]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Category:T42p&diff=24355Category:T42p2006-08-26T14:02:27Z<p>Vrossum: /* Standard Features */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top" |<br />
[[image:ThinkPadT40.jpg|ThinkPad T42p]]<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== ThinkPad T42p ===<br />
This pages gives an overview of all ThinkPad T42p related topics.<br />
<br />
Machine Type: 2373, 2374, 2378<br />
==== Standard Features ====<br />
* [[Intel Pentium M (Dothan)]] 1.7, 1.8, 2.0 or 2.1GHz CPU<br />
* [[ATI Mobility FireGL T2]] with 128MB<br />
** 14.1" TFT display with 1400x1050 resolution<br />
** 15.0" TFT display with 1600x1200 resolution<br />
* 512MB or 1GB [[PC2700]] memory standard<br />
* 60 or 80GB HDD<br />
* [[AD1981B]] AC'97 Audio controller<br />
* Intel 10/100/1000 Ethernet<br />
* [[UltraBay|UltraBay Slim]] with one of the following:<br />
** DVD-ROM/CD-RW Combo<br />
** DVD-RW<br />
* [[CDC slot]] with one of the following:<br />
** [[IBM Integrated 56K Modem (MDC-2)]]<br />
** [[IBM Integrated Bluetooth III with 56K Modem (BMDC-2)]]<br />
* [[MiniPCI slot]] with one of the following:<br />
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]<br />
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]<br />
** [[Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter]]<br />
** [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]]<br />
** [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]]<br />
* (2) Type II [[CardBus slot|CardBus slots]] or (1) type III<br />
* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]<br />
* [[Active Protection System|IBM Active Protection System]]<br />
* [[Integrated Fingerprint Reader]] on select systems<br />
</div><br />
|}<br />
<br />
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/13n6243.pdf ThinkPad T40/p, T41/p, T42, T42p - Hardware Maintenance Manual (April 2004)] (5,391,719 Bytes)<br />
<br />
[[Category:T Series]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Problem_with_red_tinted_display&diff=24255Problem with red tinted display2006-08-17T17:00:19Z<p>Vrossum: /* Affected Models */</p>
<hr />
<div>Information about the problem of red tinted display corners in T23 ThinkPads.<br />
<br />
==Problem description==<br />
If your screen is developing a red tint on the bottom left and/or right corners, this is the sign of a dying LCD and it will slowly spread to the whole screen.<br />
<br />
The red tint is strongest when the screen is first switched on and it will fade away with the time your ThinkPad is running.<br />
<br />
==Affected Models==<br />
*ThinkPad {{A31p}} (2653-H4U and similar with high resolution displays)<br />
*ThinkPad {{T21}} {{T23}} (with high resolution (SXGA) displays)<br />
<br />
==Affected Operating Systems==<br />
*all<br />
<br />
==Status==<br />
It is not clear which component (screen/backlight/inverter) exactly is responsible for this.<br />
<br />
==Solutions==<br />
You can have IBM fix the problem if your ThinkPad is still in warranty.<br />
Or:<br />
Change the fluorescent backlight, which has deceased. The phosporous layer of cold tube has a high spectrum in red, with the other spectra joining in after a few seconds, resulting in white color. this usually happens with aged tubes.<br />
The tube is different sizes in different models. It can be ordered from some supply stores, but not from IBM or Lenovo.<br />
<br />
The problem can also be caused by a bad power inverter. The inverter converts the low-voltage DC electricity from the battery to high-voltage AC to drive the fluorescent tube. The inverter failure is often a cause of the red tint in the 600 series ThinkPads. The inverter can commonly be purchased cheaply and is much quicker to replace than the [http://www.bosstar.com/ CCFL] (cold cathode fluorescent lamp).</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Problem_with_red_tinted_display&diff=24254Problem with red tinted display2006-08-17T17:00:03Z<p>Vrossum: /* Affected Models */</p>
<hr />
<div>Information about the problem of red tinted display corners in T23 ThinkPads.<br />
<br />
==Problem description==<br />
If your screen is developing a red tint on the bottom left and/or right corners, this is the sign of a dying LCD and it will slowly spread to the whole screen.<br />
<br />
The red tint is strongest when the screen is first switched on and it will fade away with the time your ThinkPad is running.<br />
<br />
==Affected Models==<br />
*ThinkPad {{A31p}} (2653-H4U and similar with high resolution displays)<br />
*ThinkPad {{T21, T23}} (with high resolution (SXGA) displays)<br />
<br />
==Affected Operating Systems==<br />
*all<br />
<br />
==Status==<br />
It is not clear which component (screen/backlight/inverter) exactly is responsible for this.<br />
<br />
==Solutions==<br />
You can have IBM fix the problem if your ThinkPad is still in warranty.<br />
Or:<br />
Change the fluorescent backlight, which has deceased. The phosporous layer of cold tube has a high spectrum in red, with the other spectra joining in after a few seconds, resulting in white color. this usually happens with aged tubes.<br />
The tube is different sizes in different models. It can be ordered from some supply stores, but not from IBM or Lenovo.<br />
<br />
The problem can also be caused by a bad power inverter. The inverter converts the low-voltage DC electricity from the battery to high-voltage AC to drive the fluorescent tube. The inverter failure is often a cause of the red tint in the 600 series ThinkPads. The inverter can commonly be purchased cheaply and is much quicker to replace than the [http://www.bosstar.com/ CCFL] (cold cathode fluorescent lamp).</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=How_to_copy_a_Linux_installation&diff=24089How to copy a Linux installation2006-08-12T23:43:08Z<p>Vrossum: /* Using dd to make a 1:1 copy */</p>
<hr />
<div>== Using dd to make a 1:1 copy ==<br />
<br />
=== Advantages ===<br />
<br />
When dd is used to create the copy, it is copied at a sector by sector level. This means that in many circumstances, the new version will have it's boot sector set up and everthing. In situations where you are making a complete copy of the disk, even things like the IBM tools and your windows partition will be saved.<br />
<br />
=== Disadvantages ===<br />
<br />
Because dd copies sector by sector it copies everything, including sectors that aren't allocated. This makes it a longer process. To update the backup copy, it must perform the whole process again, rather than simply updating the things that have changed.<br />
<br />
=== Case 1: The Linux installation is on a separate Harddisk ===<br />
<br />
This method works if you can put wo drives in your laptop.<br />
Best to boot from a boot disk, so that the contents of the disks are not changed during the cloning.<br />
<br />
dd if=/dev/hd[a,b,c,..] of=/dev/hd[a,b,c,..] bs=2M<br />
<br />
Part of Sourcedrive : if=/dev/hd[a,b,c,..] the Letter "a" for the first Harddrive, b for the second, ....<br />
<br />
Part of Destinationdrive : of=/dev/hd[a,b,c,..] the Letter "a" for the first Harddrive, b for the second, ....<br />
<br />
=== Case 2: The Linux installation is on a Partition ===<br />
<br />
(e.g. hda1 is the Partition with the Linux installation and hdb1 is the Destinationdrive)<br />
<br />
dd if=/dev/hda1 of=/dev/hdb1 bs=2M<br />
<br />
=== Case 3: Copying whole disk ===<br />
<br />
Case 1 assumes you can put two drives in your laptop.<br />
The method here can be used when you have access to a networked computer with a lot of space. Or, when you have an external 3.5 HD.<br />
(If you have a 2.5 external USB drive you can use [[Harddrive_Upgrade]])<br />
<br />
1) Boot from a CD, such as R.I.P.<br />
<br />
2a) dd if=/dev/hda bs=65536 conv=noerror,sync |gzip -c| ssh somewhere-with-disk<br />
<br />
Or, with external drive, mount it on /mnt/usb<br />
<br />
2b) dd if=/dev/hda bs=65536 conv=noerror,sync |gzip -c > /mnt/usb/big_file<br />
<br />
The gzip will cause a compression of the image file, hope for about 2:1 compression, but prepare for worse!<br />
<br />
3)Replace your old drive with new drive, and boot again from the CD.<br />
Restore with:<br />
<br />
4a) ssh somewhere-with-disk cat rawdisk.img|gzip -dc|dd of=/dev/hda bs=65536<br />
<br />
Or, for the external drive<br />
<br />
4b) cat /mnt/usb/big_file |gzip -dc|dd of=/dev/hda bs=65536<br />
<br />
You can change the partition information after the restore with tools such as parted.<br />
Note, on very old drives this method might fail when the drives are not fully identical, as the geometries needed to be equal. <br />
However, there is no risk of data loss, just re-insert the old drive and try another method.<br />
<br />
== Using tar to make a copy of the filesystem ==<br />
<br />
=== Advantages ===<br />
* able to restore it to another filesystem<br />
* compression<br />
* burn splitted backups on dvd<br />
* incremental backups<br />
<br />
=== Disadvantages ===</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Problem_with_video_related_system_lockup_II&diff=24013Problem with video related system lockup II2006-08-06T17:32:47Z<p>Vrossum: </p>
<hr />
<div>Also Thinkpads with the ATI 9600 video chip used in T42 and T42p can cause lock-ups.<br />
<br />
This happens after about two years of use.<br />
<br />
According to http://www.technotaste.com/blog/thinkpad-t42-ati-radeon-9600-driver-and-the-blue-screen-of-death-bsod/<br />
this problem is thermal and is caused by the GPU coming off the MB.<br />
<br />
Solution: replace motherboard.<br />
Or, remove the keyboard to provide extra cooling :)</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Known_Problems&diff=24011Known Problems2006-08-06T17:21:43Z<p>Vrossum: /* Display Problems */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
Information on known problems with certain ThinkPad models.<br />
|}<br />
==Display Problems==<br />
*[[Problem with unusable console | Console unusable]] <tt>(models with savage video chipset: T2x, A22e)</tt><br />
*[[Problem with Pixel Error | Dead pixels on TFT displays]] <tt>(all models)</tt><br />
*[[Problem with DVI throughput | DVI throughput on port replicators and docks]] <tt>(models from 2000-2004)</tt><br />
*[[Problems with fglrx | fglrx problems]] <tt>(ATI Radeon models)</tt><br />
*[[Problem with garbled screen | Garbled Screen]] <tt>(T40, T41, T42, R40, A30, A31, A31p)</tt><br />
*[[Problem with broken inverter | Inverter broken]] <tt>(all models)</tt><br />
*[[Problem with key and trackpoint markings on the display | Key and Trackpoint markings on display]]<br />
*[https://bugs.freedesktop.org/show_bug.cgi?id=2187 Radeon 7500 "DynamicClocks" randomly hangs] <tt>(TP T4x, Xorg-X11 bug report)</tt><br />
*[[Problem with red display shadow | Red shadow on display]] <tt>(TP T41p)</tt><br />
*[[Problem with red tinted display | Red tinted display]] <tt>(TP 23)</tt><br />
*[[Problem with black X | Unmovable square black X in X]] <tt>(TP T2x)</tt><br />
*[[Problem with video related system lockup | System Lockups related to video adapter]] <tt>(TP T2x)</tt><br />
*[[Problem with video related system lockup II | System Lockups related to video adapter T42]] <tt>(TP T42, T42p)</tt><br />
*[[Problem with ati driver in xorg 6.9.x | System lockup soon after starting xorg 6.9.x ]] <tt>(TP T4x)</tt><br />
*[[Problem with video output switching | Video output switching]]<br />
<br />
==Harddisk Drive related Problems==<br />
*[[Problem with APS harddisk parking|APS harddisk parking]] <tt>(models featuring APS)</tt><br />
*[[Problem with too large harddrive|BIOS hangs with harddrive sized over 8G]] <tt>(560)</tt><br />
*[[Problem with hard drive clicking | Clicking Hard Drive]] <tt>(models with Hitachi's 5k80 hard drive)</tt><br />
*[[Problem with non-ThinkPad hard disks|Non-ThinkPad hard disks]] <tt>(T43, X41, R52)</tt><br />
*[[Problems with SATA and Linux|SATA and Linux]] <tt>(T43, X41, R52, Z60)</tt><br />
<br />
==Network Problems==<br />
*[[Problem with 3Com 10/100 Ethernet card not being recognized|3Com 10/100 Ethernet card not recognized]] <tt>(models with that card)</tt><br />
*[[Problem with unauthorized MiniPCI network card|"Unauthorized" MiniPCI Wireless Network card error (Error 1802)]] <tt>(Recent TPs)</tt><br />
*[[Cisco Aironet Wireless 802.11b]] fails to work with certain firmware versions<br />
*[[Problem with error 01C9 - More than one Ethernet devices | Error 01C9: More than one Ethernet Devices are found (Atheros WLAN MiniPCI)]] <tt>(T30, A31p, R40 and others)</tt><br />
*[[Problem with e1000: EEPROM Checksum Is Not Valid]] <tt>(T60, X60, may be others)</tt><br />
<br />
==Power Management, AC-adapter or Battery Problems==<br />
*[[Problem with ThinkPad 600 batteries | 600 series Battery dying prematurely]] <tt>(TP 600/E/X)</tt><br />
*[[Damage in 56W AC-Adapter, plastic housing melted |AC-Adapter damaged, plastic housing melted]] <tt>(240, 390, i and s models)</tt><br />
*[[Problems with ACPI suspend-to-ram|ACPI suspend-to-ram]] <tt>(ACPI sleep troubles)</tt><br />
**[[Problem with display remaining black after resume|Blank display after resume]] <tt>(various models)</tt><br />
**[[Problem with high power drain in ACPI sleep | High power drain in ACPI sleep]] <tt>(various models)</tt><br />
**[[Problem with LCD backlight remaining on during ACPI sleep | LCD backlight remaining on during ACPI sleep]] <tt>(various models)</tt><br />
*[[Problem with fan noise | Fan noise]] <tt>(TP T4x/p, TP R5x/p)</tt><br />
*[[Problem with checking battery status | Checking battery status causes mouse to jerk around]] <tt>(R31)</tt><br />
*[[Battery drains despite seemingly being charged]] <tt>(A/C adapter issues)</tt><br />
*[[High-pitch noise from AC-Adapter]] <tt>(T60/p)</tt><br />
<br />
==Sound Problems==<br />
*[[Problem with broken sound on ThinkPad 600 | Broken sound on ThinkPad 600/E]] <tt>(TP 600/E/X, 770Z)</tt><br />
*[[Problem with audio jacks | Audio jacks not working properly]] <tt>(TP T43)</tt><br />
*[[Problem with audio clipping|Audio clipping]] <tt>(TP T43)</tt><br />
<br />
==Misc Problems==<br />
*[[Problem with Bending / Twisting|Casing malformed by bending/twising]] <tt>(X41)</tt><br />
*[[Problem with Dock USB Ports | Dock USB Ports]] <tt>(T30)</tt><br />
*[[Problem with high pitch noises | High pitch noises]] <tt>(several models)</tt><br />
*[[Problem with lm-sensors | lm_sensors kills ThinkPads]] <tt>(TP 570E, 770X/Z, 600E/X, 240, X20)</tt><br />
*[[Problem with USB 2.0 | USB 2.0 problems]] <tt>(T40)</tt><br />
<br />
[[de:Bekannte_Probleme]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Known_Problems&diff=24010Known Problems2006-08-06T17:21:04Z<p>Vrossum: /* Display Problems */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
Information on known problems with certain ThinkPad models.<br />
|}<br />
==Display Problems==<br />
*[[Problem with unusable console | Console unusable]] <tt>(models with savage video chipset: T2x, A22e)</tt><br />
*[[Problem with Pixel Error | Dead pixels on TFT displays]] <tt>(all models)</tt><br />
*[[Problem with DVI throughput | DVI throughput on port replicators and docks]] <tt>(models from 2000-2004)</tt><br />
*[[Problems with fglrx | fglrx problems]] <tt>(ATI Radeon models)</tt><br />
*[[Problem with garbled screen | Garbled Screen]] <tt>(T40, T41, T42, R40, A30, A31, A31p)</tt><br />
*[[Problem with broken inverter | Inverter broken]] <tt>(all models)</tt><br />
*[[Problem with key and trackpoint markings on the display | Key and Trackpoint markings on display]]<br />
*[https://bugs.freedesktop.org/show_bug.cgi?id=2187 Radeon 7500 "DynamicClocks" randomly hangs] <tt>(TP T4x, Xorg-X11 bug report)</tt><br />
*[[Problem with red display shadow | Red shadow on display]] <tt>(TP T41p)</tt><br />
*[[Problem with red tinted display | Red tinted display]] <tt>(TP 23)</tt><br />
*[[Problem with black X | Unmovable square black X in X]] <tt>(TP T2x)</tt><br />
*[[Problem with video related system lockup | System Lockups related to video adapter]] <tt>(TP T2x)</tt><br />
*[[Problem with video related system lockup | System Lockups related to video adapter T42]] <tt>(TP T42, T42p)</tt><br />
*[[Problem with ati driver in xorg 6.9.x | System lockup soon after starting xorg 6.9.x ]] <tt>(TP T4x)</tt><br />
*[[Problem with video output switching | Video output switching]]<br />
<br />
==Harddisk Drive related Problems==<br />
*[[Problem with APS harddisk parking|APS harddisk parking]] <tt>(models featuring APS)</tt><br />
*[[Problem with too large harddrive|BIOS hangs with harddrive sized over 8G]] <tt>(560)</tt><br />
*[[Problem with hard drive clicking | Clicking Hard Drive]] <tt>(models with Hitachi's 5k80 hard drive)</tt><br />
*[[Problem with non-ThinkPad hard disks|Non-ThinkPad hard disks]] <tt>(T43, X41, R52)</tt><br />
*[[Problems with SATA and Linux|SATA and Linux]] <tt>(T43, X41, R52, Z60)</tt><br />
<br />
==Network Problems==<br />
*[[Problem with 3Com 10/100 Ethernet card not being recognized|3Com 10/100 Ethernet card not recognized]] <tt>(models with that card)</tt><br />
*[[Problem with unauthorized MiniPCI network card|"Unauthorized" MiniPCI Wireless Network card error (Error 1802)]] <tt>(Recent TPs)</tt><br />
*[[Cisco Aironet Wireless 802.11b]] fails to work with certain firmware versions<br />
*[[Problem with error 01C9 - More than one Ethernet devices | Error 01C9: More than one Ethernet Devices are found (Atheros WLAN MiniPCI)]] <tt>(T30, A31p, R40 and others)</tt><br />
*[[Problem with e1000: EEPROM Checksum Is Not Valid]] <tt>(T60, X60, may be others)</tt><br />
<br />
==Power Management, AC-adapter or Battery Problems==<br />
*[[Problem with ThinkPad 600 batteries | 600 series Battery dying prematurely]] <tt>(TP 600/E/X)</tt><br />
*[[Damage in 56W AC-Adapter, plastic housing melted |AC-Adapter damaged, plastic housing melted]] <tt>(240, 390, i and s models)</tt><br />
*[[Problems with ACPI suspend-to-ram|ACPI suspend-to-ram]] <tt>(ACPI sleep troubles)</tt><br />
**[[Problem with display remaining black after resume|Blank display after resume]] <tt>(various models)</tt><br />
**[[Problem with high power drain in ACPI sleep | High power drain in ACPI sleep]] <tt>(various models)</tt><br />
**[[Problem with LCD backlight remaining on during ACPI sleep | LCD backlight remaining on during ACPI sleep]] <tt>(various models)</tt><br />
*[[Problem with fan noise | Fan noise]] <tt>(TP T4x/p, TP R5x/p)</tt><br />
*[[Problem with checking battery status | Checking battery status causes mouse to jerk around]] <tt>(R31)</tt><br />
*[[Battery drains despite seemingly being charged]] <tt>(A/C adapter issues)</tt><br />
*[[High-pitch noise from AC-Adapter]] <tt>(T60/p)</tt><br />
<br />
==Sound Problems==<br />
*[[Problem with broken sound on ThinkPad 600 | Broken sound on ThinkPad 600/E]] <tt>(TP 600/E/X, 770Z)</tt><br />
*[[Problem with audio jacks | Audio jacks not working properly]] <tt>(TP T43)</tt><br />
*[[Problem with audio clipping|Audio clipping]] <tt>(TP T43)</tt><br />
<br />
==Misc Problems==<br />
*[[Problem with Bending / Twisting|Casing malformed by bending/twising]] <tt>(X41)</tt><br />
*[[Problem with Dock USB Ports | Dock USB Ports]] <tt>(T30)</tt><br />
*[[Problem with high pitch noises | High pitch noises]] <tt>(several models)</tt><br />
*[[Problem with lm-sensors | lm_sensors kills ThinkPads]] <tt>(TP 570E, 770X/Z, 600E/X, 240, X20)</tt><br />
*[[Problem with USB 2.0 | USB 2.0 problems]] <tt>(T40)</tt><br />
<br />
[[de:Bekannte_Probleme]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Known_Problems&diff=24009Known Problems2006-08-06T17:19:53Z<p>Vrossum: /* Display Problems */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
Information on known problems with certain ThinkPad models.<br />
|}<br />
==Display Problems==<br />
*[[Problem with unusable console | Console unusable]] <tt>(models with savage video chipset: T2x, A22e)</tt><br />
*[[Problem with Pixel Error | Dead pixels on TFT displays]] <tt>(all models)</tt><br />
*[[Problem with DVI throughput | DVI throughput on port replicators and docks]] <tt>(models from 2000-2004)</tt><br />
*[[Problems with fglrx | fglrx problems]] <tt>(ATI Radeon models)</tt><br />
*[[Problem with garbled screen | Garbled Screen]] <tt>(T40, T41, T42, R40, A30, A31, A31p)</tt><br />
*[[Problem with broken inverter | Inverter broken]] <tt>(all models)</tt><br />
*[[Problem with key and trackpoint markings on the display | Key and Trackpoint markings on display]]<br />
*[https://bugs.freedesktop.org/show_bug.cgi?id=2187 Radeon 7500 "DynamicClocks" randomly hangs] <tt>(TP T4x, Xorg-X11 bug report)</tt><br />
*[[Problem with red display shadow | Red shadow on display]] <tt>(TP T41p)</tt><br />
*[[Problem with red tinted display | Red tinted display]] <tt>(TP 23)</tt><br />
*[[Problem with black X | Unmovable square black X in X]] <tt>(TP T2x)</tt><br />
*[[Problem with video related system lockup | System Lockups related to video adapter]] <tt>(TP T2x)</tt><br />
*[[Problem with video related system lockup | System Lockups related to video adapter]] <tt>(TP T42, T42p)</tt><br />
*[[Problem with ati driver in xorg 6.9.x | System lockup soon after starting xorg 6.9.x ]] <tt>(TP T4x)</tt><br />
*[[Problem with video output switching | Video output switching]]<br />
<br />
==Harddisk Drive related Problems==<br />
*[[Problem with APS harddisk parking|APS harddisk parking]] <tt>(models featuring APS)</tt><br />
*[[Problem with too large harddrive|BIOS hangs with harddrive sized over 8G]] <tt>(560)</tt><br />
*[[Problem with hard drive clicking | Clicking Hard Drive]] <tt>(models with Hitachi's 5k80 hard drive)</tt><br />
*[[Problem with non-ThinkPad hard disks|Non-ThinkPad hard disks]] <tt>(T43, X41, R52)</tt><br />
*[[Problems with SATA and Linux|SATA and Linux]] <tt>(T43, X41, R52, Z60)</tt><br />
<br />
==Network Problems==<br />
*[[Problem with 3Com 10/100 Ethernet card not being recognized|3Com 10/100 Ethernet card not recognized]] <tt>(models with that card)</tt><br />
*[[Problem with unauthorized MiniPCI network card|"Unauthorized" MiniPCI Wireless Network card error (Error 1802)]] <tt>(Recent TPs)</tt><br />
*[[Cisco Aironet Wireless 802.11b]] fails to work with certain firmware versions<br />
*[[Problem with error 01C9 - More than one Ethernet devices | Error 01C9: More than one Ethernet Devices are found (Atheros WLAN MiniPCI)]] <tt>(T30, A31p, R40 and others)</tt><br />
*[[Problem with e1000: EEPROM Checksum Is Not Valid]] <tt>(T60, X60, may be others)</tt><br />
<br />
==Power Management, AC-adapter or Battery Problems==<br />
*[[Problem with ThinkPad 600 batteries | 600 series Battery dying prematurely]] <tt>(TP 600/E/X)</tt><br />
*[[Damage in 56W AC-Adapter, plastic housing melted |AC-Adapter damaged, plastic housing melted]] <tt>(240, 390, i and s models)</tt><br />
*[[Problems with ACPI suspend-to-ram|ACPI suspend-to-ram]] <tt>(ACPI sleep troubles)</tt><br />
**[[Problem with display remaining black after resume|Blank display after resume]] <tt>(various models)</tt><br />
**[[Problem with high power drain in ACPI sleep | High power drain in ACPI sleep]] <tt>(various models)</tt><br />
**[[Problem with LCD backlight remaining on during ACPI sleep | LCD backlight remaining on during ACPI sleep]] <tt>(various models)</tt><br />
*[[Problem with fan noise | Fan noise]] <tt>(TP T4x/p, TP R5x/p)</tt><br />
*[[Problem with checking battery status | Checking battery status causes mouse to jerk around]] <tt>(R31)</tt><br />
*[[Battery drains despite seemingly being charged]] <tt>(A/C adapter issues)</tt><br />
*[[High-pitch noise from AC-Adapter]] <tt>(T60/p)</tt><br />
<br />
==Sound Problems==<br />
*[[Problem with broken sound on ThinkPad 600 | Broken sound on ThinkPad 600/E]] <tt>(TP 600/E/X, 770Z)</tt><br />
*[[Problem with audio jacks | Audio jacks not working properly]] <tt>(TP T43)</tt><br />
*[[Problem with audio clipping|Audio clipping]] <tt>(TP T43)</tt><br />
<br />
==Misc Problems==<br />
*[[Problem with Bending / Twisting|Casing malformed by bending/twising]] <tt>(X41)</tt><br />
*[[Problem with Dock USB Ports | Dock USB Ports]] <tt>(T30)</tt><br />
*[[Problem with high pitch noises | High pitch noises]] <tt>(several models)</tt><br />
*[[Problem with lm-sensors | lm_sensors kills ThinkPads]] <tt>(TP 570E, 770X/Z, 600E/X, 240, X20)</tt><br />
*[[Problem with USB 2.0 | USB 2.0 problems]] <tt>(T40)</tt><br />
<br />
[[de:Bekannte_Probleme]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=21757Fglrx2006-04-18T14:47:54Z<p>Vrossum: /* Building for Xorg 7.0 */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
== ATI fglrx driver ==<br />
This is a binary-only driver for ATI graphic chips with support for 3D acceleration.<br />
|}<br />
<br />
==Availability / Project Homepage==<br />
Home page: https://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&folderID=356<br />
<br />
== Packages ==<br />
The ATI drivers have explicit permission for repackaging and redistribution of the Linux drivers. Many distributions are supported within the installer, and many more repackaged by external developers. Please visit the [http://wiki.cchtml.com/index.php/Category:Distributions Distribution Page at the Unofficial ATI driver Wiki]<br />
<br />
*{{Debian}} packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html<br />
** These packages have been added to Debian unstable as <tt>fglrx-driver</tt>, so you can now apt-get them and use module-assistant to install.<br />
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, let it build Debian packages and proceed as usual. There's a [http://jroller.com/page/erAck?entry=lot_day_6_2_fglrx detailed description] available.<br />
*{{SUSE}} packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/<br />
*{{Gentoo}} {{cmdroot|emerge x11-drivers/ati-drivers}}<br />
*{{Fedora}} packages: http://rpm.livna.org<br />
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}<br />
** Creating and installing a custom RPM for a custom-compiled kernel on {{Fedora}}:<br />
::{{cmdroot|yum install ati-fglrx}}<br />
::{{cmdroot|1=VER=8.20.8.1-0.lvn.1.4 # copy version string from output of above command}}<br />
::{{cmdroot|wget http://rpm.livna.org/fedora/4/i386/SRPMS.lvn/ati-fglrx-$VER.src.rpm}}<br />
::{{cmdroot|rpmbuild --rebuild --target $(uname -m) --define "ksrc /lib/modules/$(uname -r)/build" --without userland ati-fglrx-$VER.src.rpm}}<br />
::{{cmdroot|rpm -Uvh --replacepkgs /usr/src/redhat/RPMS/$(uname -m)/kernel-module-fglrx-$(uname -r)-$VER.$(uname -m).rpm}}<br />
*{{Arch Linux}}<br />
:{{cmdroot|pacman -S ati-fglrx}} (kernel module for 2.6.15-ARCH)<br />
:{{cmdroot|pacman -S ati-fglrx-archck}} (kernel module for 2.6.15-archck)<br />
:{{cmdroot|pacman -S ati-fglrx-utils}} (xorg7 stuff and tools)<br />
<br />
== Building for Xorg 7.0==<br />
To compile for Xorg 7.0.0, fake Xorg 6.9.0 by <br />
:{{cmdroot|1=export X_VERSION=x690; sh ati-driver-installer-8.24.8-x86.run}}<br />
Next, one needs to move the various resulting libraries and modules from /usr/X11R6 to /usr/lib/xorg<br />
<br />
In {{path|/usr/src/ATI}} additional sources are installed for fireglcontrol and fgl_glxgears<br />
<br />
== Status ==<br />
Current version: 8.24.8 (13th April 2006)<br />
<br />
Major changes:<br />
* 8.24.8: support for X1300, X1400, X1600, X1800 (generic and mobility) and 3D accelerated video playback on Avivo<br />
* 8.23.7: support for X850 and X800, OpenGL 2.0 Enhancement, FSAA for some chips<br />
* 8.22.5: added kernel 2.6.15 support -- patch no longer required<br />
* 8.21.7: initial OpenGL 2.0 support<br />
* 8.20.8: fixed resume issues, fixed compile problems with kernels 2.6.13 and 2.6.14<br />
* 8.19.10: has added suspend / resume and dynamic GPU power management support. Using vbetool is no longer required (tested and successful with T43p).<br />
<br />
== Known problems and solutions ==<br />
See [[Problems with fglrx]].<br />
== User experience ==<br />
=== Speed ===<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
Compared to the old drivers, approximately 40% speed gain have been noticed with fglrx. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (via {{key|ctrl}}{{key|alt}}{{key|plus}}, {{key|ctrl}}{{key|alt}}{{key|minus}}), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using the open source radeon driver: 1200 FPS for glxgears{{footnote|1}}!<br />
{{NOTE|1=Video overlay acceleration may be disabled when 3D acceleration is enabled. The following comment from the xorg.conf file bundled with the fglrx driver indicates that:<br />
# === OpenGL Overlay ===<br />
# Note: When OpenGL Overlay is enabled, Video Overlay<br />
# will be disabled automatically<br />
Option "OpenGLOverlay" "1"<br />
However, you can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. This has nothing to do with the acceleration of 2D drawing primitives. Further, your mileage on performance may vary depending on what card you have. The open source drivers don't support newer cards, while the ATI drivers don't support older cards.}}<br />
<br />
=== Power saving ===<br />
Power saving is much better than with the <tt>radeon</tt> driver, but doesn't work in dual-screen configuration (see [[How to make use of Graphics Chips Power Management features]]).<br />
<br />
== Useful links == <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www.rage3d.com/content/articles/atilinuxhowto/ ATI Radeon Linux How-To]<br />
* [http://www.rage3d.com/board/forumdisplay.php?f=61&daysprune=30&order=asc&sort=title Rage3D Linux Discussion Forum]<br />
* [http://www.driverheaven.net/forumdisplay.php?f=103 Radeon Driver Forum at Driverheaven]<br />
* [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html Gentoo ATI Radeon FAQ]<br />
* [http://forums.gentoo.org/viewtopic-t-374745-highlight-t42+ati+dri.html Gentoo T42 ATI. DRI + xorg driver]<br />
* [http://ati.cchtml.com/ Unofficial community ATI bugzilla] - tracks bugs in the driver. Might be monitored by ATI ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]).<br />
* [http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide Installing Version 8.24.8 in Ubuntu] for X1*00 support.<br />
<br />
== ThinkPads that may be supported ==<br />
Supported chips, as found in select IBM ThinkPads:<br />
* [[ATI Mobility FireGL 9000]]<br />
** {{T40p}}<br />
* [[ATI Mobility FireGL T2]]<br />
** {{R50p}}<br />
** {{T41p}}, {{T42p}}<br />
* [[ATI Mobility FireGL V3200]]<br />
** {{T43p}}<br />
* [[ATI Mobility Radeon 9000]]<br />
** {{R50}}, {{R51}}<br />
** {{T40}}, {{T41}}, {{T42}}<br />
* [[ATI Mobility Radeon 9600]]<br />
** {{T42}}<br />
* [[ATI Mobility Radeon X300]]<br />
** {{R52}}<br />
** {{T43}}<br />
** {{Z60m}}<br />
* [[ATI Mobility Radeon Xpress 200M]]<br />
** {{R51e}}<br />
* [[ATI Mobility Radeon X600]]<br />
** {{Z60m}}<br />
{{footnotes|<br />
#Note that glxgears isn't a benchmark tool, it's so simple that its FPS values is without any meaning... you can only compare glxgears using the same drivers/machine, if you change any of then you can have higher/lower values and in real life programs/games happen to have the opposite effects. Think in terms of a car engines rpms: higher rpms in the same car usually means a faster car, change anything and it's meaningless, ie: gears, truck, wheel size, etc. make it useless.<br />
}}<br />
[[Category:Drivers]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=21584Fglrx2006-04-13T09:59:59Z<p>Vrossum: /* Packages */</p>
<hr />
<div>== ATI fglrx driver ==<br />
This is a binary-only driver which supports 3D acceleration.<br />
<br />
Home page: https://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&folderID=356<br />
<br />
== Status ==<br />
Current version: 8.24.8 (13th April 2006)<br />
<br />
Major changes:<br />
* 8.24.8: unclear<br />
* 8.23.7: support for X850 and X800, OpenGL 2.0 Enhancement, FSAA for some chips<br />
* 8.22.5: added kernel 2.6.15 support -- patch no longer required<br />
* 8.21.7: initial OpenGL 2.0 support<br />
* 8.20.8: fixed resume issues, fixed compile problems with kernels 2.6.13 and 2.6.14<br />
* 8.19.10: has added suspend / resume and dynamic GPU power management support. Using vbetool is no longer required (tested and successful with T43p).<br />
<br />
== Known problems and solutions ==<br />
See [[Problems with fglrx]].<br />
<br />
== Build from ATI source ==<br />
To compile for Xorg 7.0.0, fake Xorg 6.9.0 by <br />
# export X_VERSION=x690; sh ati-driver-installer-8.24.8-x86.run<br />
<br />
In /usr/src/ATI additional sources are installed for fireglcontrol and fgl_glxgears<br />
<br />
<br />
== Packages ==<br />
The ATI drivers have explicit permission for repackaging and redistribution of the Linux drivers. Many distributions are supported within the installer, and many more repackaged by external developers. Please visit the [http://wiki.cchtml.com/index.php/Category:Distributions Distribution Page at the Unofficial ATI driver Wiki]<br />
<br />
*{{Debian}} packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html<br />
** These packages have been added to Debian unstable as "fglrx-driver", so you can now apt-get them and use module-assistant to install (currently v8.20.8-1).<br />
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, currently v8.22.5, let it build Debian packages and proceed as usual. There's a [http://jroller.com/page/erAck?entry=lot_day_6_2_fglrx detailed description] available.<br />
*{{SUSE}} packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/<br />
*{{Gentoo}} {{cmdroot|emerge x11-drivers/ati-drivers}}<br />
*{{Fedora}} packages: http://rpm.livna.org<br />
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}<br />
** Creating and installing a custom RPM for a custom-compiled kernel on {{Fedora}}:<br />
# yum install ati-fglrx<br />
# VER=8.20.8.1-0.lvn.1.4 # copy version string from output of above command<br />
# wget http://rpm.livna.org/fedora/4/i386/SRPMS.lvn/ati-fglrx-$VER.src.rpm<br />
# rpmbuild --rebuild --target $(uname -m) --define "ksrc /lib/modules/$(uname -r)/build" --without userland ati-fglrx-$VER.src.rpm<br />
# rpm -Uvh --replacepkgs /usr/src/redhat/RPMS/$(uname -m)/kernel-module-fglrx-$(uname -r)-$VER.$(uname -m).rpm<br />
*{{Arch Linux}}<br />
** {{cmdroot|pacman -S ati-fglrx}} (kernel module for 2.6.15-ARCH)<br />
** {{cmdroot|pacman -S ati-fglrx-archck}} (kernel module for 2.6.15-archck)<br />
** {{cmdroot|pacman -S ati-fglrx-utils}} (xorg7 stuff and tools)<br />
<br />
== User experience ==<br />
=== Speed ===<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
- On the old drivers, I've noticed appx 40% speed gain with ATI fglrx vs open source drivers. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (ctrl-alt-plus, ctrl-alt-minus), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using "radeon" or "ati" in xorg.conf. 1200FPS glxgears! (''note that glxgears isnt a benchmark tool, its so simple that its value is without any meaning... you can only compare glxgears using the same drivers/machine, if you change any of then you can have higher/lower values and in real life programs/games happend the opposite. Think in the car engine rpm, higher rpm in the same car usually its a faster car, change anything and its meaningless. ie: gears, truck, wheel size, etc make it useless'')<br />
<br />
NOTE: 2D acceleration may be disabled when 3D acceleration is enabled. This comes from the Xorg.conf file the fglrx driver provides<br />
# === OpenGL Overlay ===<br />
# Note: When OpenGL Overlay is enabled, Video Overlay<br />
# will be disabled automatically<br />
Option "OpenGLOverlay" "1"<br />
<br />
Just a note to the above. The 2D acceleration for that option refers to video overlay. You can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. It has nothing to do with 2D drawing primitives. Further, your mileage on performance may vary depending on what card you have. The open-source drivers don't support newer cards, while the ATI drivers don't support older cards.<br />
<br />
=== Power saving ===<br />
Power saving is much better than with the <tt>radeon</tt> driver, but doesn't work in dual-screen configuration (see [[How to make use of Graphics Chips Power Management features]]).<br />
<br />
== Useful links == <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www.rage3d.com/content/articles/atilinuxhowto/ ATI Radeon Linux How-To]<br />
* [http://www.rage3d.com/board/forumdisplay.php?f=61&daysprune=30&order=asc&sort=title Rage3D Linux Discussion Forum]<br />
* [http://www.driverheaven.net/forumdisplay.php?f=103 Radeon Driver Forum at Driverheaven]<br />
* [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html Gentoo ATI Radeon FAQ]<br />
* [http://forums.gentoo.org/viewtopic-t-374745-highlight-t42+ati+dri.html Gentoo T42 ATI. DRI + xorg driver]<br />
* [http://ati.cchtml.com/ Unofficial community ATI bugzilla] - tracks bugs in the driver. Might be monitored by ATI ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]).<br />
<br />
== ThinkPads that may be supported ==<br />
Supported chips, as found in select IBM ThinkPads:<br />
* [[ATI Mobility FireGL 9000]]<br />
** {{T40p}}<br />
* [[ATI Mobility FireGL T2]]<br />
** {{R50p}}<br />
** {{T41p}}, {{T42p}}<br />
* [[ATI Mobility FireGL V3200]]<br />
** {{T43p}}<br />
* [[ATI Mobility Radeon 9000]]<br />
** {{R50}}, {{R51}}<br />
** {{T40}}, {{T41}}, {{T42}}<br />
* [[ATI Mobility Radeon 9600]]<br />
** {{T42}}<br />
* [[ATI Mobility Radeon X300]]<br />
** {{R52}}<br />
** {{T43}}<br />
** {{Z60m}}<br />
* [[ATI Mobility Radeon Xpress 200M]]<br />
** {{R51e}}<br />
* [[ATI Mobility Radeon X600]]<br />
** {{Z60m}}<br />
<br />
[[Category:Drivers]]</div>Vrossumhttps://www.thinkwiki.org/w/index.php?title=Fglrx&diff=21582Fglrx2006-04-13T09:51:40Z<p>Vrossum: /* Status */</p>
<hr />
<div>== ATI fglrx driver ==<br />
This is a binary-only driver which supports 3D acceleration.<br />
<br />
Home page: https://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&folderID=356<br />
<br />
== Status ==<br />
Current version: 8.24.8 (13th April 2006)<br />
<br />
Major changes:<br />
* 8.24.8: unclear<br />
* 8.23.7: support for X850 and X800, OpenGL 2.0 Enhancement, FSAA for some chips<br />
* 8.22.5: added kernel 2.6.15 support -- patch no longer required<br />
* 8.21.7: initial OpenGL 2.0 support<br />
* 8.20.8: fixed resume issues, fixed compile problems with kernels 2.6.13 and 2.6.14<br />
* 8.19.10: has added suspend / resume and dynamic GPU power management support. Using vbetool is no longer required (tested and successful with T43p).<br />
<br />
== Known problems and solutions ==<br />
See [[Problems with fglrx]].<br />
<br />
== Packages ==<br />
The ATI drivers have explicit permission for repackaging and redistribution of the Linux drivers. Many distributions are supported within the installer, and many more repackaged by external developers. Please visit the [http://wiki.cchtml.com/index.php/Category:Distributions Distribution Page at the Unofficial ATI driver Wiki]<br />
<br />
*{{Debian}} packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html<br />
** These packages have been added to Debian unstable as "fglrx-driver", so you can now apt-get them and use module-assistant to install (currently v8.20.8-1).<br />
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, currently v8.22.5, let it build Debian packages and proceed as usual. There's a [http://jroller.com/page/erAck?entry=lot_day_6_2_fglrx detailed description] available.<br />
*{{SUSE}} packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/<br />
*{{Gentoo}} {{cmdroot|emerge x11-drivers/ati-drivers}}<br />
*{{Fedora}} packages: http://rpm.livna.org<br />
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}<br />
** Creating and installing a custom RPM for a custom-compiled kernel on {{Fedora}}:<br />
# yum install ati-fglrx<br />
# VER=8.20.8.1-0.lvn.1.4 # copy version string from output of above command<br />
# wget http://rpm.livna.org/fedora/4/i386/SRPMS.lvn/ati-fglrx-$VER.src.rpm<br />
# rpmbuild --rebuild --target $(uname -m) --define "ksrc /lib/modules/$(uname -r)/build" --without userland ati-fglrx-$VER.src.rpm<br />
# rpm -Uvh --replacepkgs /usr/src/redhat/RPMS/$(uname -m)/kernel-module-fglrx-$(uname -r)-$VER.$(uname -m).rpm<br />
*{{Arch Linux}}<br />
** {{cmdroot|pacman -S ati-fglrx}} (kernel module for 2.6.15-ARCH)<br />
** {{cmdroot|pacman -S ati-fglrx-archck}} (kernel module for 2.6.15-archck)<br />
** {{cmdroot|pacman -S ati-fglrx-utils}} (xorg7 stuff and tools)<br />
== User experience ==<br />
=== Speed ===<br />
How much is the speed gain versus the opensource drivers?<br />
<br />
- On the old drivers, I've noticed appx 40% speed gain with ATI fglrx vs open source drivers. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (ctrl-alt-plus, ctrl-alt-minus), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using "radeon" or "ati" in xorg.conf. 1200FPS glxgears! (''note that glxgears isnt a benchmark tool, its so simple that its value is without any meaning... you can only compare glxgears using the same drivers/machine, if you change any of then you can have higher/lower values and in real life programs/games happend the opposite. Think in the car engine rpm, higher rpm in the same car usually its a faster car, change anything and its meaningless. ie: gears, truck, wheel size, etc make it useless'')<br />
<br />
NOTE: 2D acceleration may be disabled when 3D acceleration is enabled. This comes from the Xorg.conf file the fglrx driver provides<br />
# === OpenGL Overlay ===<br />
# Note: When OpenGL Overlay is enabled, Video Overlay<br />
# will be disabled automatically<br />
Option "OpenGLOverlay" "1"<br />
<br />
Just a note to the above. The 2D acceleration for that option refers to video overlay. You can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. It has nothing to do with 2D drawing primitives. Further, your mileage on performance may vary depending on what card you have. The open-source drivers don't support newer cards, while the ATI drivers don't support older cards.<br />
<br />
=== Power saving ===<br />
Power saving is much better than with the <tt>radeon</tt> driver, but doesn't work in dual-screen configuration (see [[How to make use of Graphics Chips Power Management features]]).<br />
<br />
== Useful links == <br />
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]<br />
* [http://www.rage3d.com/content/articles/atilinuxhowto/ ATI Radeon Linux How-To]<br />
* [http://www.rage3d.com/board/forumdisplay.php?f=61&daysprune=30&order=asc&sort=title Rage3D Linux Discussion Forum]<br />
* [http://www.driverheaven.net/forumdisplay.php?f=103 Radeon Driver Forum at Driverheaven]<br />
* [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html Gentoo ATI Radeon FAQ]<br />
* [http://forums.gentoo.org/viewtopic-t-374745-highlight-t42+ati+dri.html Gentoo T42 ATI. DRI + xorg driver]<br />
* [http://ati.cchtml.com/ Unofficial community ATI bugzilla] - tracks bugs in the driver. Might be monitored by ATI ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]).<br />
<br />
== ThinkPads that may be supported ==<br />
Supported chips, as found in select IBM ThinkPads:<br />
* [[ATI Mobility FireGL 9000]]<br />
** {{T40p}}<br />
* [[ATI Mobility FireGL T2]]<br />
** {{R50p}}<br />
** {{T41p}}, {{T42p}}<br />
* [[ATI Mobility FireGL V3200]]<br />
** {{T43p}}<br />
* [[ATI Mobility Radeon 9000]]<br />
** {{R50}}, {{R51}}<br />
** {{T40}}, {{T41}}, {{T42}}<br />
* [[ATI Mobility Radeon 9600]]<br />
** {{T42}}<br />
* [[ATI Mobility Radeon X300]]<br />
** {{R52}}<br />
** {{T43}}<br />
** {{Z60m}}<br />
* [[ATI Mobility Radeon Xpress 200M]]<br />
** {{R51e}}<br />
* [[ATI Mobility Radeon X600]]<br />
** {{Z60m}}<br />
<br />
[[Category:Drivers]]</div>Vrossum