ThinkWiki - User contributions [en]

How to build your own Ultrabay drive

2006-03-02T09:51:40Z

Bluebrother: /* UltraBay 2000 */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Optical [[UltraBay Devices|UltraBay drives]] like CD-ROM and DVD drives or burners are usually a bit more expensive than their non-IBM counterparts. Additionally more modern technologies are not available for discontinued [[UltraBay]] standards. A solution to this annoyance is to take a standard slim form factor notebook drive and turn it into an UltraBay drive yourself.
{{WARN|No warranty of any kind is given for the correctness of the following instructions. Following them can damage your machine. Proceed at your own risk.}}
{{NOTE|This article is written with UltraBay 2000 drives in mind. But should be appliable for UltraSlimBay and other kinds of UltraBay devices as well. However, see the warning below}}
{{WARN|UltraBay Enhanced (and possibly UltraBay Slim) formfactor uses a proprietary connector which is soldered to the board. No standard drive can be modified to be used in UltraBay Enhanced (Slim?) equiped Thinkpads.}}
|}
==The Basics==
The "big secret" about UltraBay drives is that basically they are just standard slim form factor notebook drives equipped with an UltraBay frame. This frame is just a mechanical addition with an integrated connector adapter.

As curious people found, the inner connector of an UltraBay frame is nothing more than a standard interface for such drives. Hence, it is generally possible to disassemble an old UltraBay drive and attach the frame to a newer or better one.

There are, however, some things to consider...

==The Limitations==
Even though these slim form factor drives seem to have a standard form factor at first look, it turns out that there are marginal mechanical differences. This makes it hard if at all possible to know beforehand if the UltraBay frame from your old drive will perfectly fit onto the new one. The fact is that different UltraBay drives even for the same UltraBay standard have frames with different mechanical characteristics. Small differences can sometimes be adjusted by modifying parts of the frame, but this is of course not the nicest solution.

The most varying part is the Blending, which is usually not compatible even among drives of the same manufacturer. The positions of the eject button, the drive LED, the emergency eject hole and the way the blending is attached to the drive all vary a lot. Do precise research before you buy anything. One solution here is to keep the original blending of the drive, since the UltraBay blending is independent from the rest of the frame. The disadvantage is an optical one: the standard blendings are usually flat whereas the UltraBay blendings usually are a bit thicker at the top and thinner at the bottom. Also, for some UltraBay standards you would have to cut out the lower right edge of the blending, since the standard drive blendings are usually rectangle shaped.

==UltraBay 2000==
The UltraBay 2000 frame consists of four parts: Front bezel, left wing, right wing and the back plate containing the connector interface.

The left and right parts are attached with little screws in holes which are at standardised positions and should usually fit among all drives. However, the actual drives show tiny variations in width, which are leveraged by the left and right parts. Hence these can be a bit thicker or thinner (fractions of 1mm). Putting a somewhat wide frame part onto a somewhat wide drive might result in an UltraBay drive that doesn't fit into the bay at all because it's just a tiny little bit too wide. This can be dealt with e.g. by sanding one of the side frame parts, but it's better if all components fit correctly in the first place. Also, the side frames have hatches fitting into the holes in the back part. Among frames these hatches vary in thickness and length and hence, again, might not fit easily. Again, they can be adjusted by cutting them a bit.

{| border=1 cellspacing=0 cellpadding=2
|+ UltraBay 2000 drives and compatible alternative drives
|-
! UltraBay drive !! IBM Part-Nr. !! actual drive !! compatible drive !! needed steps to make fitting
|-
| [[UltraBay 2000 CD-ROM Drive]] || ... || TEAC CD-224E || ... || ...
|-
| [[UltraBay 2000 8x-3x DVD-ROM Drive]] || 27L3447 || Matsushita SR-8175-M || ... || ...
|-
| [[UltraBay 2000 Ultralight 8x DVD-ROM Drive]] || 08K9648 || Matsushita SR-8176-M || ... || ...
|-
| UltraBay 2000 8x DVD drive || ... || Hitachi GD-S200 || 8x DVD+-RW NEC ND-6650A || [http://markoff.biz/pivot/entry.php?id=856 Commented photo manual]
|-
| UltraBay 2000 6x DVD drive || ... || Toshiba DVD-ROM SD-C2302 || [http://www.liteonamericas.com/us/DVDRW_SOSW833S.htm LiteonIT Slimtype SOSW-833S DVD+-RW] || Judging by the pictures, this Liteon IT drive looks a lot like the NEC one in Markoff's guide above. Notes:

1) It seems it's ''not'' necessary to cut away the lower-right corner of the front bezel, at least on a T23. It'll take a bit more determination than normally to close the drive, but it doesn't look like the bezel is suffering from the bent ([http://www.thinkwiki.org/wiki/Image:Ultrabay2k_replacement_drive_bezel_bend.jpg photo]). Also, it was a bit tricky to get the new drive to actually stay locked in the bay, but once you get it to fit (and don't need to swap drives), it'll stay.

2) Burning DVD-Rs at "maximum speed" produces valid DVD's but with a scary, unstable sound, and the net speed fluctuates between 1 and 2x (also on a T23). Choosing 2x keeps the burn process stable (and noiseless!)

|-
| UltraBay 2000 DVD/CD-RW Combo drive || ... || ... || LG GWA-4040N || [http://www.thinkpad-portal.com/modules/cpg1.2.1_standalone/thumbnails.php?album=45&page=1 Photo documentary]
|-
| [[UltraBay 2000 CD-RW/DVD-ROM Combo IV Drive]] || ... || HL-DT-ST GCC-4240N || NEC ND-6650A || building the drive from scratch was pretty easy and straightforward. I got wing and backplane from ebay. On the front bezel it's necessary to cut away the lower-right corner. It seems to be possible to mount the original front bezel with small mods -- the notches seem to be in the same position.
|-
| [[UltraBay 2000 DVD Multi-Burner]] || 22P7015 || Panasonic UJ-840 || NEC 8X SLIM DVD ND-6650 || Eschewing the Ultrabay 2000 bezel, a small section needs to be cut out of the lower right corner of the original front bezel. This can be removed from the drive for this purpose; the other Ultrabay parts screw directly into the drive which fits without further modifications.
|}

==Links==
* [http://markoff.biz/pivot/entry.php?id=856 Commented photo manual about upgrading an UltraBay 2000 drive] <tt>(DVD-ROM Hitachi GD-S200 -> DVD+-RW NEC ND-6650A in IBM ThinkPad T21)</tt>

Category talk:T60

2006-01-06T19:11:30Z

Bluebrother:

#@)$(*!!!! From the article:

"The T60 improves upon the T43 by offering... a Windows key"

I've always loved IBM for omitting the Windows key on their keyboards - I'm sure most all of us linux users also agree that this is NOT an improvement. I think that Lenovo is deviating from the original visions/spirit of IBM in several regards...

I need to second this. Argl! Lenovo really trashed the good old Thinkpads :( [[User:Bluebrother|Bluebrother]] 20:11, 6 Jan 2006 (CET)

How to configure the TrackPoint

2005-11-19T21:42:10Z

Bluebrother: using the middle mouse button and EmulateWheel

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |The [[Patch to enable advanced trackpoint configuration|kernel trackpoint driver]] is controlled by echoing values to special files. Common configuration options are outlined below.
{{NOTE|
*Starting from 2.6.13 config files for this driver are located in <tt>/sys/devices/platform/i8042/serio0/serio2</tt>. (This document uses the new locations.)
*From 2.6.11 on, they are in <tt>/sys/devices/platform/i8042/serio0</tt>.
*Prior to kernel 2.6.11, these files were located in <tt>/proc/trackpoint</tt>.
*Prior to kernel 2.6.9, these files were not files at all, but were command-line options to the psmouse module. (Note this means you must compile psmouse as a module!) See http://stephen.evanchik.com/node/16.
}}
|}

==General Configuration==
The configuration options are reflected by the files you can find in {{path|/sys/devices/platform/i8042/serio0/serio2}}. See the [[Patch to enable advanced trackpoint configuration|TrackPoint driver page]] for a complete list.
Configuration is done by echoing the appropriate values into these special files.

==Most common Features==
The most common settings are '''Press to Select''', '''sensitivity''', '''speed''' and '''scrolling'''.

===Press to Select===
Press to Select allows you to tap the control stick which will simulate a left click. You can enable this feature by typing the following in to a terminal (you may need to be root):

:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio0/serio2/press_to_select}}

Press to Select should now be enabled. You can disable it in a similar manner:

:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/press_to_select}}

===Sensitivity & Speed===
Adjusting the speed and sensitivity of the TrackPoint requires echoing a value between 0 and 255 into the appropriate file. For example, for a speed of 120 and a sensitivity of 250, type the following into a terminal:

:{{cmdroot|echo -n 120 > /sys/devices/platform/i8042/serio0/serio2/speed}}
:{{cmdroot|echo -n 250 > /sys/devices/platform/i8042/serio0/serio2/sensitivity}}

Feel free to experiment with your settings until you find a combination that is comfortable.

===Scrolling===
====Using a kernel prior to 2.6.11====
The scrolling action is essentially the same as is used in the TrackPoint Windows drivers. To enable this feature, type the following in to a terminal (you may need to be root):

:{{cmdroot|echo -n 1 > /proc/trackpoint/scroll}}

Then press the middle button and push the stick up and down to scroll. Similarly, to disable scrolling:

:{{cmdroot|echo -n 0 > /proc/trackpoint/scroll}}

====Using the X server (kernel 2.6.11+)====
The scroll setting has been removed from the trackpoint driver in kernel versions 2.6.11 and above. Scroll emulation should now be handled in the X server. First do:

:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/middle_btn_disable}}

Then, for versions of Xorg since ~Oct '04, add these lines to your TrackPoint configuration section in {{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"

Now restart X and hold down button 2 and move the mouse to scroll, or just press and release button 2 for a middle click.
Please note that the patch allowing to use button 2 for a middle click is currently (27/09/05) NOT included in most distributions packages of Xorg but will appear with release of 6.9 / 7. You can find an updated version of the package in the Experimental branch of debian or try to build the mouse driver yourself with the information of the [http://www.mail-archive.com/devel@xfree86.org/msg03333.html patch announcement]. I got this working with FC3's 6.8.2 packages.

For older versions of Xorg or for Xfree86 ({{path|/etc/X11/XF86Config}}) try this:

Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

Now restart X and hold down button two and move the mouse for scrolling. To get a middle click, press buttons 1 and 3 simultaneously.

==Soft Transparent Mode==
If you wish to connect a special device to the external PS/2 port, you should consider using "Soft Transparent Mode" so that the TrackPoint controller does not interpret any commands sent to the external PS/2 port. You can enable soft transparent mode by typing the following in to a terminal:

:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio0/serio2/transparent}}

Disabling soft transparent mode is similar:

:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/transparent}}

Madwifi

2005-11-06T23:56:08Z

Bluebrother: /* Related links */

== Multiband Atheros Driver for WiFi ==
Linux driver for 802.11a/b/g universal NIC cards - Cardbus, PCI, or miniPCI - using Atheros chip sets.

The following adapters sold by IBM use the Atheros chips:
* [[IBM Dual-Band 11a/b Wi-Fi Wireless Mini PCI Adapter]]
* [[IBM 11b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
* [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]
* IBM 802.11a Wireless LAN Cardbus Adapter
* IBM 11 a/b/g Wireless Cardbus Adapter

=== Project Homepage ===
http://www.madwifi.org (old page: http://sourceforge.net/projects/madwifi)

=== Packages ===
*daily cvs snapshots: http://madwifi.otaku42.de
*{{Debian}} Packages: http://www.marlow.dk/site.php/tech/madwifi
*{{Debian}} Packages: http://www.users.tpg.com.au/sigm/misc/madwiki.txt
*{{Fedora}} Packages(1): http://rpm.livna.org
*{{Fedora}} Packages(2): http://www.atrpms.net/name/madwifi/

=== CVS ===
:{{cmduser|cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/madwifi co madwifi}}

=== Installation ===

*Make sure that you've got sysctl support and the net/radio enabled (wireless extensions) in your kernel. Install the driver with make & make install
* further more you like to install the wireless tools from [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html wireless tools]. Make sure the versions fit together by
:{{cmduser|iwconfig --version}}

Setting up [[wpa_supplicant]] with wpa-psk.

=== Status ===
in development, usable

=== OpenSource HAL ===
The "official" driver consists of an opensource wrapper with binary HAL (Hardware Abstraction Layer). This HAL is not a binary firmware like with the Intel Wireless chips, but a piece of code that needs to runs in the Linux kernel.
The vendors reasoning behind this is, that since the Atheros chip could be tuned to any frequency, and hence interfere with systems operating in those frequencies, that we simply need to accept this binary module.<br>
Obviously this binary HAL is unacceptable to the Linux kernel developers, and the Atheros driver in this state will never become part of the official kernel.<br>
Some OpenBSD developers facing the same issue, reverse engineered the binary HAL and have produced an OpenSource version. Hopefully a driver based on this might be included with the Linux kernel at some point in time, and picked up by the mainstream distributions.

=== Related links ===
* [http://www.madwifi.org/wiki MadWiFi Wiki]
* [http://team.vantronix.net/ar5k/ OpenSource Atheros HAL]

[[Category:Drivers]]

Madwifi

2005-11-06T23:54:50Z

Bluebrother: point out new project homepage

== Multiband Atheros Driver for WiFi ==
Linux driver for 802.11a/b/g universal NIC cards - Cardbus, PCI, or miniPCI - using Atheros chip sets.

The following adapters sold by IBM use the Atheros chips:
* [[IBM Dual-Band 11a/b Wi-Fi Wireless Mini PCI Adapter]]
* [[IBM 11b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
* [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]
* IBM 802.11a Wireless LAN Cardbus Adapter
* IBM 11 a/b/g Wireless Cardbus Adapter

=== Project Homepage ===
http://www.madwifi.org (old page: http://sourceforge.net/projects/madwifi)

=== Packages ===
*daily cvs snapshots: http://madwifi.otaku42.de
*{{Debian}} Packages: http://www.marlow.dk/site.php/tech/madwifi
*{{Debian}} Packages: http://www.users.tpg.com.au/sigm/misc/madwiki.txt
*{{Fedora}} Packages(1): http://rpm.livna.org
*{{Fedora}} Packages(2): http://www.atrpms.net/name/madwifi/

=== CVS ===
:{{cmduser|cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/madwifi co madwifi}}

=== Installation ===

*Make sure that you've got sysctl support and the net/radio enabled (wireless extensions) in your kernel. Install the driver with make & make install
* further more you like to install the wireless tools from [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html wireless tools]. Make sure the versions fit together by
:{{cmduser|iwconfig --version}}

Setting up [[wpa_supplicant]] with wpa-psk.

=== Status ===
in development, usable

=== OpenSource HAL ===
The "official" driver consists of an opensource wrapper with binary HAL (Hardware Abstraction Layer). This HAL is not a binary firmware like with the Intel Wireless chips, but a piece of code that needs to runs in the Linux kernel.
The vendors reasoning behind this is, that since the Atheros chip could be tuned to any frequency, and hence interfere with systems operating in those frequencies, that we simply need to accept this binary module.<br>
Obviously this binary HAL is unacceptable to the Linux kernel developers, and the Atheros driver in this state will never become part of the official kernel.<br>
Some OpenBSD developers facing the same issue, reverse engineered the binary HAL and have produced an OpenSource version. Hopefully a driver based on this might be included with the Linux kernel at some point in time, and picked up by the mainstream distributions.

=== Related links ===
* [http://madwifi.sourceforge.net/dokuwiki/doku.php MadWiFi Wiki]
* [http://team.vantronix.net/ar5k/ OpenSource Atheros HAL]

[[Category:Drivers]]

Problem with high power drain in ACPI sleep

2005-09-09T17:48:37Z

Bluebrother: custom initrd to Fedora section

Information about the problem of too high power drain in ACPI sleep mode.

==Problem description==
Several people realized that their ThinkPads eat up too much power while suspended to ram via ACPI. Compared to APM suspend to ram the power drain is experienced to be about 10 times as high, 2-5 Watts. This empties the battery within one or two days.

==Affected Models==

*Different symptoms have been reported for different models. In some models the origin of the power drain is obvious ([[Problem with LCD backlight remaining on during ACPI sleep|backlight on during suspend]]), in other models there is no obvious reason.

*On some models/configurations the higher power drain couldn't even be realized or was at least significantly lower.

*The T4x Thinkpad series (T40, T40p, T41, T41p, T42, T42p, T43, T43p) suspends to ram just fine, and there are no components that are obviously left powered up. The [[UltraBay]] and network light is on, but that is the same under windows (but under APM sleep to RAM those lights are OFF).

*This is a driver problem and can be fixed in software. For the T4x series, there is a fix available but it has not yet made its way into the official kernel (as of linux 2.6.12).

The following table gives an overview of the models suffering from the mysterious power drain. To find out about your model, you may use the following [[ACPI sleep power drain test script | script]]. It creates a file <tt>/var/log/battery.log</tt> which will tell you if you are affected or not.

{| border="1" cellspacing="0" cellpadding="2"
|-
! style="vertical-align:top;background-color:#ffcfbc;" | affected models
! style="vertical-align:top;background-color:#cfefcf;" | unaffected models
|-
| style="vertical-align:top;background-color:#fff0e0;" |
* {{R32}}
** 2658-BQG
* {{R40}}
** 2722-5MG
** 2722-B3G
** 2722-CDG
** 2897-GWU
** 2722-6YU
* {{R50}}
** 1829-7RG
** 1829-6DM
** 1836-3SU
* {{R51}}
** 1829-9MG
** 1829-EHG
** 1829-R6G
** 1830-DG4
** 1836-Q6U
* {{T23}}
**2647-???
* {{T30}}
** 2366-81A
** 2366-97U
** 2366-FBU
** 2366-96G
*{{T40}}
**2373-MU3
**2373-82U
**2373-92U
**2373-22G
**2373-19G
**2373-A1U
**2373-42G
*{{T40p}}
**2373-G1U
**2373-G3U
**2373-G3G
**2373-G1G
**2373-G5G
* {{T41}}
**2379-DJU
**2373-9HU
**2373-4FG
**2373-4PG
**2373-1FG
**2373-2FG
**2373-2GG
**2373-6U4
**2373-7JU
**2373-CY0
**2373-TG5
* {{T41p}}
**2373-9FU
* {{T42}}
**2373-C19
**2373-CTO
**2378-DUU
**2373-FWG
**2374-ZEP
**2373-F2G
**[[2373-6ZG]]
* {{X21}}
* {{X32}}
**2884-A3U
| style="vertical-align:top;background-color:#e9f9e9;" |
*[[:Category:R50p | R50p]]
*[[:Category:R52 | R52]]
**1858-6MM
*[[:Category:T41 | T41]]
**2373-GEU
*[[:Category:T41p | T41p]]
**2373-GKG
**2373-GGG
**[[2373-GHG]]
*[[:Category:T42p | T42p]]
**[[2373-HTG]]
**[[2373-W6M]]
**[[2373-GTG]]
**[[2373-GXG]]
**2373-KXM
*[[:Category:T42 | T42]]
**[[2378-FVU]]
**[[2373-WBZ]]
**[[2378-RTU]]
*[[:Category:T43 | T43]]
**[[2668-W12]]
*[[:Category:X40 | X40]]
**2371
*[[:Category:A22m | A22m]]
**2628
|}

==Affected Operating Systems==

*Linux, all flavours.
*Windows, for some models as well (only when using non-IBM drivers).
*FreeBSD (on the A22M)

==Status==
*The cause of the mysterious power drain is the radeon GPU, which requires extra steps to suspend properly. Unfortunately, this fix might break non-Thinkpad machines and therefore is not yet in the official kernel sources.

*The official bugzilla entry for the radeon suspend issue is in the [http://bugme.osdl.org/show_bug.cgi?id=3022 OSDL Bugzilla]. There you can find a patch which will solve the power drain issue.

{{WARN|This solution enables doing suspend-to-D2 on non-PPC-machines, which is not properly documented! Be careful and have a look at the discussion for kernel bug 3022 (see above) before applying the patch. By default, the patch enables the suspend-to-D2 only on machines where it is know to work. This behaviour can be overridden with a module option.}}

*Most certainly, the DSDT is not at fault. (Interesting to note: The DSDT from BIOS 3.13 (Nov 04) for the T42p compiles without bugs.)

*Some additional power savings can be achieved by turning off the wake-on-lan (<tt>ethtool -s eth0 wol d</tt>). The power drain of the wol feature is far smaller than the radeon bug, but can be noticeable.

==Solutions==
===For Thinkpads with Radeon graphic driver===

You must use a patched version of the radeon frame buffer, even if you are only interested in using the X window system. This modified radeon frame buffer then suspends the radeon chip correctly during ACPI sleep. This patch is not yet in the official (kernel.org) kernels.

The patch contains a list of Thinkpads where it is known to work, and by default only activates on these machines. If you think that your computer would profit from the patch as well, you can force it by including the module parameter <tt>radeon_force_sleep=1</tt>.

====Fedora Core 3/4 official kernel====

* Fedora Core 4: Fedora ships a patched radeon frame buffer (radeonfb.ko), but you must enable it yourself. [[:Category:Fedora | Fedora Core 4]] compiles it as a module rather than including it in the kernel, therefore you cannot activate it at boot time without a custom initrd (see below to do so). You must arrange for the module to be loaded before X starts (for example, using an init script).
* Fedora Core 3: this is also true for updated kernels (at least for kernel-2.6.12-1.1376_FC3) but '''not''' for the initially shipped version.

===== radeonfb after bootup =====
If you want to try the radeon frame buffer, you can enable it as follows (assuming you are at the gdm login screen). First, switch to a console (Ctrl-Alt-F1) and log in as root. Stop X:
init 3
Now you can load the module:
modprobe radeonfb radeon_force_sleep=1
Finally, resume X:
init 5

===== radeonfb with customized initrd =====
As an alternative you can build your customized initrd. This is as simple as running
# mkinitrd --with=radeonfb /boot/<name-of-your-new-initrd> `uname -r`
and replacing the initrd in {{path|/boot/grub/grub.conf}} with your new one. You also need to add the kernel command line argument <code>video=radeonfb:radeon_force_sleep=1''</code>

====Fedora Core 3/4 custom kernel====

For [[:Category:Fedora | Fedora Core]] there are precompiled patched kernels [http://www.sas.upenn.edu/~vbraun/computing/T41/kernel.html available]:

*[http://carrot.hep.upenn.edu/~vbraun/kernel-T4x/i386/kernel-T4x-2.6.11.11-26.i386.rpm linux 2.6.11 for Fedora Core 3]

*[http://carrot.hep.upenn.edu/~vbraun/kernel-T4x/i386/kernel-T4x-2.6.12.2-2.i386.rpm linux 2.6.12 for Fedora Core 4]

These kernels contain additional thinkpad-related patches, including software suspend2 and trackpoint support. Suspend to disk and suspend to ram should work with them. If your Thinkpad model is not yet whitelisted in the patch, you might have to enable the radeon fix by including the parameter <tt>video=radeonfb:radeon_force_sleep=1</tt> on the kernel command line.

If you try, please send the result (hang yes/no, battery drain yes/no) with the precise model number (for example, I have a IBM thinkpad T41 2379-DJU) to <tt>vbraun at physics dot upenn dot edu</tt>, it would be nice if your subject line would include "RADEONFB:" to make sure that I do not miss any emails.

====Technical Discussion====

The proposed solution is to remove the CONFIG_PPC_PMAC condition for enabling D2 sleep in drivers/video/aty/radeon_pm.c as discussed in [http://bugme.osdl.org/show_bug.cgi?id=3022 kernel bug 3022]. There you can also find patches doing this. The patches divide into unconditional ones like [http://carrot.hep.upenn.edu/~vbraun/kernel-T4x/test/patch-2.6.11-rc2-radeonfb-D2.patch.bz2 this one for 2.6.11-rc2] and conditional ones. The conditional ones only do D2 on models where it has been reported to work, the unconditional ones force D2 sleep on every model and you might experience hangs on resume with those.

====Other====

It is possible that radeontool from http://fdd.com/software/radeon/ will help some people with this case.
(simply run radeontool light off before suspend and radeontool light on after resume).
radeontool patch for freebsd is here: http://www.init-main.com/radeontool.patch (by Takanori Watanabe).

I am now testing radeontool with my T42 (2373-6ZG)

===For other models without radeon graphics===
Nothing yet.