ThinkWiki - User contributions [en]

2373-F7G

2006-06-20T18:12:12Z

Gq: /* Storage */

= IBM ThinkPad T42 2373-F7G Specifications =

== CPU ==
{|
|Processor Manufacturer || Intel
|-
|Processor Class || (Pentium M - Dothan 90nm)
|-
|Processor Name || Intel Pentium M 745
|-
|Processor Speed || 1.80 GHz
|-
|Processor FSB Speed || 400 MHz
|-
|L2 Cache Size || 2 MB
|}
== Memory ==
{|
|Installed Memory || 512 MB (1 SO-DIMM)
|-
|Maximum Memory || 2 GB (2 SO-DIMM)
|-
|Memory Technology || DDR SDRAM
|-
|Memory Speed || 333 MHz
|}
== Storage ==
{|
|Hard Drive Model || Hitachi HTS548080M9AT00
|-
|Hard Drive Capacity || 80 GB
|-
|Hard Drive Rotation Speed || 5400 RPM
|-
|Included Drives || DVD Multi-Burner (Matshita UJ-812) or DVD Multi-Burner Plus (Matshita UJ-822S)
|}

== Display and Graphics ==
{|
|Display Size || 15 inch
|-
|Display Type || Flexview (IPS)
|-
|Display Resolution || SXGA+ (1400x1050)
|-
|Graphics Processor || ATI Mobility Radeon 9600
|-
|Graphics Memory || 64 MB
|-
|Graphics Interface || AGP 4x
|}

== Battery ==
{|
|Battery Model || 6 cell
|-
|Battery Capacity || 47520 mWh (10.8V, 4.4 AH)
|-
|Battery Type || Lithium ion
|}

== Communications and Networking ==
{|
|Bluetooth || Yes
|-
|Modem Speed || 56 Kbps
|-
|Network LAN || Intel PRO/1000 MT
|-
|Network WLAN || Intel PRO/Wireless 2200BG MiniPCI card
|}

== Software ==
{|
|Shipped Operating System || Microsoft Windows XP Professional
|}

== Connectors ==
{|
|Interface Provided ||Parallel Port, S-Video, VGA, Phone line, Headphone, Microphone, Ethernet 10Base-T/100Base-TX/1000Base-T
|-
|Connectors ||2 x Hi-Speed USB - 4 pin USB Type A, 1 x parallel - IEEE 1284 (EPP/ECP) - 25 pin D-Sub (DB-25), 1 x display / video - VGA - 15 pin HD D-Sub (HD-15), 1 x infrared - IrDA, 1 x modem - phone line - RJ-11, 1 x network - Ethernet 10Base-T/100Base-TX/1000Base-T - RJ-45, 1 x display / video - S-video output - 4 pin mini-DIN, 1 x docking / port replicator, 1 x microphone - input - mini-phone mono 3.5 mm , 1 x audio - line-out/headphones - mini-phone stereo 3.5 mm
|}

== General Product Info ==
{|
|Input Devices || Keyboard, Touchpad, TrackPoint, Fingerprint sensor
|-
|Included Sound Card || Analog Devices Soundmax
|-
|Built-in Microphone || Yes
|-
|Weight || 2.6939 kg
|-
|Manufacturer Part No. || 2373F7G
|-
|Dimension || 31mm x 329mm x 268mm (HxWxD)
|}

[[Category:T42]]

Problem with high power drain in ACPI sleep

2006-03-31T14:11:21Z

Gq: /* Affected Models */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
==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==
{| border="1" cellspacing="0" cellpadding="2" style="float:right;margin-left:20px;"
|-
! 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-3GG
** 2722-5MG
** 2722-B3G
** 2722-CDG
** 2897-GWU
** 2722-6YU
** 2722-CDG
* {{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-19G
**2373-22G
**2373-42G
**2373-75G
**2373-82U
**2373-92U
**2373-A1U
**2373-MU3
*{{T40p}}
**2373-G1U
**2373-G3U
**2373-G3G
**2373-G1G
**2373-G5G
* {{T41}}
**2379-DJU
**2373-3KG
**2373-9HU
**2373-4FG
**2373-4PG
**2373-1FG
**2373-2FG
**2373-2GG
**2373-6U4
**2373-7JU
**2373-CY0
**2373-TG5
**2373-3HM
**2373-4GU
* {{T41p}}
**2373-9FU
* {{T42}}
**2373-C19
**2373-CTO
**2378-DTU
**2378-DUU
**2378-XXE
**2373-FWG
**2374-ZEP
**2373-F2G
**2373-VUW
**[[2373-6ZG]]
* {{X21}}
**2662-BSG
* {{X32}}
**2884-A3U
| style="vertical-align:top;background-color:#e9f9e9;" |
*[[:Category:A22m | A22m]]
**2628
*[[:Category:A31 | A31]]
**2652-D5G
*[[:Category:R50p | R50p]]
*[[:Category:R52 | R52]]
**1858-6MM
*[[:Category:T41 | T41]]
**2373-GEU
*[[:Category:T41p | T41p]]
**2373-GKG
**2373-GGG
**[[2373-GHG]]
*[[:Category:T42 | T42]]
**[[2373-M1G]]
**[[2373-WBZ]]
**[[2373-F7G]]
**[[2378-DXU]]
**[[2378-FVU]]
**[[2378-RTU]]
**[[2378-RRU]]
*[[:Category:T42p | T42p]]
**[[2373-HTG]]
**[[2373-W6M]]
**[[2373-GTG]]
**[[2373-GXG]]
**2373-KXM
*[[:Category:T43 | T43]]
**[[2668-W12]]
*[[:Category:T43p | T43p]]
**[[2668-G2G]]
*[[:Category:X40 | X40]]
**2371
|}
*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 and other Radeon based models suspend 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). For these models the higher power drain is caused by a driver problem and can be fixed in software. This fix has not yet made its way into the official kernel (as of linux 2.6.12).

The table on the right 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 {{path|/var/log/battery.log}} which will tell you if you are affected or not.

==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 known 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 ({{cmdroot|ethtool -s eth0 wol d}}). The power drain of the wol feature is far smaller than the radeon bug, but can be noticeable.

==Solutions==
===For ThinkPads with Radeon graphic chips===
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 [http://bugme.osdl.org/attachment.cgi?id=6444&action=view 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 {{bootparm|radeon_force_sleep|1}}. If it doesn't work this can result in system hangs.

====Technical Background====
The patch removes the CONFIG_PPC_PMAC condition for enabling D2 sleep in {{path|drivers/video/aty/radeon_pm.c}} as discussed in [http://bugme.osdl.org/show_bug.cgi?id=3022 kernel bug 3022].

====Fedora Core====
* Fedora Core 4: Fedora ships a patched radeon frame buffer (radeonfb.ko), but you must enable it yourself. {{Fedora}} compiles it as a module rather than including it in the kernel, therefore you cannot activate it at boot time without a custom initrd. 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.

There are precompiled patched kernels [http://www.sas.upenn.edu/~vbraun/computing/T41/kernel.html available] as well, that do not need an initrd modification:
*[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 Suspend 2]] 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 {{bootparm|video|2=radeonfb:radeon_force_sleep=1}} on the kernel command line.

If you try, please send the result (hang yes/no, battery drain yes/no) with the precise model number (i.e. 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.

=====testing radeonfb without changing initrd=====
If you want to try the radeon frame buffer, you can enable it as follows:
*First, switch to a console ({{key|Ctrl}}{{key|Alt}}{{key|F1}}) and log in as root.
*Stop X: {{cmdroot|init 3}}
*Now you can load the module: {{cmdroot|1=modprobe radeonfb radeon_force_sleep=1}}
*Finally, resume X: {{cmdroot|init 5}}

=====including radeonfb into your initrd=====
As an alternative you can build your customized initrd. This is as simple as running
:{{cmdroot|1=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 {{bootparm|video|2=radeonfb:radeon_force_sleep=1}}.

====Gentoo====
After installing the patch on {{Gentoo}} (it works fine with gentoo-sources: {{cmdroot|cd /usr/src/linux/drivers/video/aty}}, and execute {{cmdroot|patch -p4 <patchname>}}, then recompile the kernel), one needs to add {{bootparm|video|radeonfb:force_sleep}} to the kernel parameters.

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

===For models without radeon graphics===
The Problem seems to be solved when you use the [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] to turn the LCD off before suspending ...
:{{cmdroot|vbetool dpms off}}
and turning it on afterwards again...
:{{cmdroot|vbetool dpms on}}
You have to change to a normal console before turning the LCD off.
Additionally you have to deactivate the Wake-On-Lan feature like mentioned above ...
:{{cmdroot|ethtool -s eth0 wol d}}
With these commands used together the "testing script" reports no high power drain while suspending.

Hard disk drives

2006-03-04T22:19:39Z

Gq: /* IBM/Hitachi harddisk naming scheme */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
IBM sold its HDD manufacturing to Hitachi, who continued to use the Travelstar name for notebook drives.
|}

==IBM/Hitachi harddisk naming scheme==
Hitachi harddisk names (on modern drives) are a set of letters and numbers that in fact tell a lot about the specifications of the drive. The designation follows the pattern:

{| style="text-align:center;"
| style="background-color:#eeeeee;" | H
| style="background-color:#eeeeee;" | T
| style="background-color:#eeeeee;" | S
| style="background-color:#eeeeee;" | 72
| style="background-color:#eeeeee;" | 60
| style="background-color:#eeeeee;" | 60
| style="background-color:#eeeeee;" | M
| style="background-color:#eeeeee;" | 9
| style="background-color:#eeeeee;" | AT
| style="background-color:#eeeeee;" | 00
|-
| style="background-color:#dddddd;" | H
| style="background-color:#dddddd;" | [t]
| style="background-color:#dddddd;" | [T]
| style="background-color:#dddddd;" | [rr]
| style="background-color:#dddddd;" | [SS]
| style="background-color:#dddddd;" | [ss]
| style="background-color:#dddddd;" | [g]
| style="background-color:#dddddd;" | [h]
| style="background-color:#dddddd;" | [ii]
| style="background-color:#dddddd;" | [??]
|}

*the H is for Hitachi
*[t] is a single letter designating the drive type, like
** T = Travelstar
** D = Deskstar
** E = Endurastar
*[T] - S for Standard (vs A for Auto for example) - I don't know what this mean :)
*[rr] is the first two digits of speed in RPM, i.e. 54 for 5400 RPM.
*[SS] maximum disk size in model line.
*[ss] is two digits giving the size in GB. 100gig drives have a 10 here.
*[g] generation code
*[h] is the drives height in full millimeters, first digit, i.e. 9 for 9.5mm or some code for desktop: i.e. L - 1-inch form-factor.
*[ii] is a two digit code for the drives interface, like this:
**AT = IDE/ATA
**SA = IDE/SATA
**CE = IDE/ZIF
**CF = Compact Flash
**L3 = SCSI/Ultra320
**LF = FC-AL
*two numerical digits are following, might be some kind of revision, might be something else. Upd: for DeskStar 1st is buffer size (2 - 2MB 8 - 8MB) and 2nd is reserved.

==Available drives from IBM or Lenovo==
{| border="1" cellspacing="0" cellpadding="2"
|-
! colspan=7 style="text-align:center;background:#efefef;" |
=== 2.5" 9.5mm SATA ===
|- style="background:#ffdead;white-space:nowrap;"
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models
|-
| 40GB || 5400 || || 39T2621 || Hitachi || ||
|-
| 40GB || 5400 || || 39T2629 || Toshiba || ||
|-
| 40GB || 5400 || || 39T2637 || Fujitsu || ||
|-
| 60GB || 5400 || 40Y8723 || 39T2623 || Hitachi || ||
|-
| 60GB || 5400 || 40Y8723 || 39T2631 || Toshiba || ||
|-
| 60GB || 5400 || || 39T2639 || Fujitsu || ||
|-
| 80GB || 5400 || || 39T2625 || Hitachi || ||
|-
| 80GB || 5400 || || 39T2633 || Toshiba || ||
|-
| 80GB || 5400 || || 39T2641 || Fujitsu || ||
|-
| 100GB || 5400 || 40Y8721 || 39T2627 || Hitachi || ||
|-
| 100GB || 5400 || 40Y8721 || 39T2635 || Toshiba || ||
|-
| 100GB || 5400 || || 39T2643 || Fujitsu || ||
|-
| 60GB || 7200 || 41N3012 || 39T2645 || || ||
|-
| 100GB || 7200 || 41N3013 || 39T2649 || Hitachi || ||
|-
| 100GB || 7200 || || 27R2345 || Hitachi || ||
|-
| 100GB || 7200 || || 27R2346 || Seagate || ||
|-
! colspan=7 style="text-align:center;background:#efefef;" |

=== 2.5" 9.5mm PATA ===
|- style="background:#ffdead;white-space:nowrap;"
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models
|-
| 6GB || 4200 || 05K9237 || 05K9227 || SSD || ||
|-
| 6GB || 4200 || 05K9237 || 05K9228 || Hitachi || ||
|-
| 10GB || 4200 || 08K9510 || 08K9508 || SSD || ||
|-
| 10GB || 4200 || 08K9510 || 08K9531 || Hitachi || ||
|-
| 12GB || 4200 || 05K9238 || 05K9229 || SSD || ||
|-
| 12GB || 4200 || 05K9238 || 05K9230 || Hitachi || ||
|-
| 15GB || 4200 || 08K9588 || 08K9587 || Hitachi || ||
|-
| 15GB || 4200 || 08K9588 || 08K9585 || STD || ||
|-
| 20GB || 4200 || || 08K9533 || Hitachi || ||
|-
| 20GB || || || 92P6375 || Hitachi || ||
|-
| 20GB || 4200 || 27L3439 || 27L3441, 08K9548 || || ||
|-
| 20GB || || || 27L3427 || SSD || ||
|-
| 20GB || || || 27L4075 || SSD || ||
|-
| 20GB || 4200 || 08K9686 || 27L4286 || STD || ||
|-
| 20GB || 4200 || 08K9686 || 27L4385 || Fujitsu || ||
|-
| 20GB || 4200 || 08K9686 || 92P6327 || STD || ||
|-
| 20GB || 4200 || || 92P6019 || Fujitsu || MHS2020AT || {{G40}}, {{G41}}
|-
| 20GB || 4200 || || 92P6094 || Fujitsu || MHT2020AT || {{G40}}, {{G41}}
|-
| 20GB || 4200 || || 92P6017 || Hitachi || DK23EA-20 || {{G40}}, {{G41}}
|-
| 20GB || 4200 || || 92P6086 || Hitachi || IC25N020ATMR04 || {{G40}}, {{G41}}
|-
| 30GB || || 08K9593 || 08K9590 || || ||
|-
| 30GB || || 08K9593 || 08K9592 || Hitachi || ||
|-
| 30GB || || || 08K9660 || Hitachi || ||
|-
| 30GB || || || 08K9656 || Diabo || ||
|-
| 30GB || || || 08K9564 || SSD || ||
|-
| 30GB || || || 27L4291 || || ||
|-
| 30GB || || || 92P6330 || STD || ||
|-
| 30GB || 4200 || || 92P6088 || Hitachi || IC25N030ATMR04 || {{G40}}, {{G41}}
|-
| 30GB || 4200 || || 92P6096 || Fujitsu || MHT2030AT || {{G40}}, {{G41}}
|-
| 40GB || 4200 || || 08K9683 || STD || ||
|-
| 40GB || 4200 || || 08K9767 || Hitachi || ||
|-
| 40GB || 4200 || || 92P6023 || Fujitsu || MHS2040T || {{G40}}, {{G41}}
|-
| 40GB || 4200 || || 92P6098 || Fujitsu || MHT2040AT || {{G40}}, {{G41}}
|-
| 40GB || 4200 || || 92P6021 || Hitachi || DK23EA-40 || {{G40}}, {{G41}}
|-
| 40GB || 4200 || || 92P6090 || Hitachi || IC25N040ATMR04 || {{G40}}, {{G41}}
|-
| 40GB || 4200 || || 92P6119 || Moraga || B || {{G40}}, {{G41}}
|-
| 40GB || 4200 || || 92P6121 || Toshiba || Proteus || {{G40}}, {{G41}}
|-
| 40GB || 5400 || || 08K9758 || Toshiba || || {{T30}}
|-
| 40GB || 5400 || || 27L4384 || STD || ||
|-
| 40GB || 5400 || 08K9687 || 08K9599 || || ||
|-
| 40GB || 5400 || 08K9816 || 92P6342 || STD || ||
|-
| 40GB || 5400 || 08K9816 || 13N6801 || || ||
|-
| 40GB || 5400 || 08K9816 || 08K9834 || Hitachi || || {{T30}}
|-
| 40GB || 5400 || 08K9816 || 92P6545 || Hitachi || HTS548040M9AT00 ||
|-
| 60GB || 4200 || || 08K9833 || Hitachi || || {{T30}}
|-
| 60GB || 4200 || || 92P6092 || Hitachi || IC25N060ATMR04 || {{G40}}, {{G41}}
|-
| 60GB || 4200 || || 92P6122 || Moraga || C || {{G40}}, {{G41}}
|-
| 60GB || 4200 || 13N6706 || 13N6707 || Hitachi || IC25N060ATMR04-0 || {{R51}}
|-
| 60GB || 5400 || 08K9688 || 08K9700 || || ||
|-
| 60GB || 5400 || 08K9688 || 92P6340 || STD || ||
|-
| 60GB || 5400 || 73P3357 || 13N6893 || || ||
|-
| 60GB || 5400 || || 92P6547 || Hitachi || HTS548060M9AT00 ||
|-
| 60GB || 7200 || || 13N6807 || Hitachi || HTS726060M9AT00 || {{T41p}}, {{T42p}}, {{T43}}, {{T43p}}
|-
| 60GB || 7200 || || 92P6551 || Hitachi || HTS726060M9AT00 ||
|-
| 80GB || 4200 || 08K9869 || 08K9863 || || ||
|-
| 80GB || 4200 || || 92P6123 || Moraga || B || {{G40}}, {{G41}}
|-
| 80GB || 5400 || 13N6798 || 13N6805 || Hitachi || HTS548080M9AT00 || {{T41p}}, {{T42p}}, {{T43p}}
|-
| 80GB || 5400 || 09N4273 || 92P6549 || Hitachi || HTS548080M9AT00 ||
|-
| 80GB || 7200 || || 39T2583 || Hitachi || ||
|-
| 100GB || 5400 || 40Y8716 || 39T2555 || Fujitsu || ||
|-
| 100GB || 5400 || 40Y8716 || 39T2559 || Toshiba || ||
|-
| 100GB || 7200 || || 39T2585 || Hitachi || ||
|-
! colspan=7 style="text-align:center;background:#efefef;" |

=== 2.5" 12.5mm PATA ===
|- style="background:#ffdead;white-space:nowrap;"
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models
|-
| 18GB || 4200 || 05K9239 || 05K9231 || || ||
|-
| 32GB || 5400 || 08K9511 || 08K9509 || SSD || ||
|-
| 48GB || 5400 || 08K9600 || 08K9599 || || ||
|-
| 48GB || 5400 || 08K9600 || 92P6338 || STD || ||
|-
! colspan=7 style="text-align:center;background:#efefef;" |

=== 1.8" 9.5mm PATA ===
|- style="background:#ffdead;white-space:nowrap;"
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models
|-
| 20GB || 4200 || || 92P6083 || Hitachi || DK14FA-20 || {{X40}}, {{X41}}, {{X41T}}
|-
| 20GB || 4200 || || 39T2541 || Hitachi || HTC426020G7AT00 || {{X40}}, {{X41}}, {{X41T}}
|-
| 30GB || 4200 || || 92P6140 || Hitachi || || {{X40}}, {{X41}}, {{X41T}}
|-
| 30GB || 4200 || || 39T2543 || Hitachi || || {{X40}}, {{X41}}, {{X41T}}
|-
| 30GB || 4200 || || 39T2747 || Toshiba || || {{X60s}}
|-
| 40GB || 4200 || || 92P6085 || Hitachi || DK13FA-40 || {{X40}}, {{X41}}, {{X41T}}
|-
| 40GB || 4200 || || 39T2545 || Hitachi || || {{X40}}, {{X41}}, {{X41T}}
|-
| 40GB || 4200 || || 39T2749 || Toshiba || || {{X60s}}
|-
| 60GB || 4200 || 73P3358 || 39T2547 || Hitachi || || {{X40}}, {{X41}}, {{X41T}}
|-
| 60GB || 4200 || || 39T2751 || Toshiba || || {{X60s}}
|-
! colspan=7 style="text-align:center;background:#efefef;" |

=== 2.5" PATA (770 series)===
|- style="background:#ffdead;white-space:nowrap;"
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models
|-
| 5.1GB || || 11J8947 || 12J0449 || || || {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}
|-
| 8.1GB || || 02K0517 || 02K0514 || || || {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}
|-
| 14.1GB || || 02K0526 || 02K0525 || || || {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}
|-
! colspan=7 style="text-align:center;background:#efefef;" |

=== 2.5" PATA (380,385,560,570,600 series)===
|- style="background:#ffdead;white-space:nowrap;"
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models
|-
| 1.08GB || || 46H4208 || || || ||
|-
| 2.1GB || || 73H9797 || || || ||
|-
| 2.1GB || || 45H8783 || || || ||
|-
| 3.2GB || || 02K0487 || || || ||
|-
| 4.0GB || || 02K0501 || || || ||
|-
| 4.0GB || || 05K8871 || || || ||
|-
| 5.1GB || || 02K0506 || || || ||
|-
| 6.0GB || || 05K9199 || || || ||
|-
| 6.4GB || || 02K0518 || || || ||
|-
| 10GB || || 36L9293 || || || ||
|-
| 12GB || || 05K9200 || || || ||
|-
| 18GB || || 37L2993 || || || ||
|-
! colspan=7 style="text-align:center;background:#efefef;" |
=== 2.5" SCSI-2 (PowerPC ThinkPads)===
|- style="background:#ffdead;white-space:nowrap;"
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models
|-
| 540MB || || 30H1388 || || || || {{820}}, {{850}}, {{860}}
|-
| 810MB || || 30H1392 || || || || {{820}}, {{850}}, {{860}}
|-
| 1.2GB || || 30H1467 || || || || {{820}}, {{850}}, {{860}}
|}
[[Category:Components]]

How to save memory

2006-03-04T22:00:00Z

Gq: /* Disk space */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |This page is meant as a collection of information on how to save memory to make Linux work reasonable on older system with limited amount of RAM.

Most distributions nowadays don't take much care about it anymore, so there are a lot of things you can do to save memory. To get a smoothly working linux environment on a low memory machine you will need to conciously choose a lot of aspects of your system, most importantly the graphical environment, desktop environment and applications. This page provides detailed information about these various optimization possibilities.
|}

==Alternative graphical environments==
{{Todo|...}}

==Streamlining the desktop environment==
The common Desktop environments GNOME and KDE are, in their modern state, focused more on features, integration, and beauty rather than on resource saving. Understandable, but running Linux on an older ThinkPad with limited RAM requires conscious and sensitive resource usage more than anything else. The good thing about Linux is that a lot of things stay adjustable and customizable. So lets see what we can do about desktops.

One of the most important things is to decide for one graphical widget library and stick with that when you are choosing your desktop environment and applications. Having several toolkits in use means more libraries being loaded and hence more memory being used by those. Possibilities are:
* [http://www.fltk.org/ FLTK]
* [http://www.fox-toolkit.org/ FOX toolkit]
* [http://www.gnustep.org GNUstep toolkit]
* [http://www.gtk.org/ GTK] <tt>(not recommended, use GTK 2 if possible)</tt>
* [http://www.gtk.org/ GTK 2]
* [http://www.lesstif.org/ Lesstif] / [http://www.openmotif.org/ OpenMotif]
* [http://www.trolltech.com/products/qt/index.html QT]
* [http://www.windowmaker.org/development-wings.html WINGs] <tt>(kind of a lightweight GNUstep toolkit, provided by the WindowMaker developers)</tt>
* [http://www.x.org/ X Toolkit]

Of those, at current state, there are enough applications for the X Toolkit, GTK, GTK 2 and QT to provide you with a solution for every task you should want.

===GNOME===
It's like with humans, the worst feature is in most cases also the best one. For GNOME it is probably the many little parts it consists of. Makes it hard to install, but enables one to customize the installation. So, the first thing you should do to streamline GNOME is not to launch it. Sound stupid? Well, lets have a look.

GNOME is basically a set of libraries built around the GTK+ libs and extending its functionality. Add some nice little applications, a session manager, a panel, beautiful icons, and some other stuff and you have GNOME as you know it. Reversing those additions is what you can do to use GNOME applications on a machine that this desktop environment would normally take your nerves on.

The GNOME panel, the session manager, the desktop manager and the window manager are all parts of GNOME that eat a lot of memory for something that others can do in a maybe little less beautiful but much more resource saving way.
So first off configure your login manager not to launch gnome-session at login. If you are using GDM this is quite straight forward, you just need to add a different session script, launching your favorite window manager. See the list below and pick one, lets say i.e. WindowMaker. WindowMaker uses a desktop menu, a dock and a notification area to provide you with an organized way of launching applications and iconfying running ones. So we don't need a panel anymore. Also, think if you really need icons on your desktop. If you do, think about using something like ROX filer instead of nautilus for that. In any case, tell nautilus not to manage the desktop by default by unchecking the according setting within gconf-editor. To keep GNOME applications happy we would need to have gconf and gnome-settings-manager running at every session start. One way to do this is to either include them in your new session script. They both need to be running to make GNOME applications realize their settings properly.

===KDE===
{{Todo|...}}

===Alternative Desktop Environments===
First of all, it is important to notice that GNOME and KDE are not the only Desktop Environments around.
Other complete (featuring most of: window management, session management, desktop management, file management and panel) desktop environments are:
*[http://xfce.org/ XFCE] <tt>uses GTK 2</tt>
*[http://ede.sourceforge.net Equinox Desktop Environment] <tt>uses eFLTK, a modified version of FLTK</tt>
*[http://www.nongnu.org/antiright/ AntiRight Desktop Environment] <tt>uses LessTif / OpenMotif</tt>
*[http://foxdesktop.sourceforge.net/ FOX Desktop Environment] <tt>uses FOX Toolkit</tt>
*[http://www.gnustep.org/ GNUstep] <tt>provides it's own toolkit</tt>

But also, some Window Managers exceed the task of managing windows towards providing a functional workbench. See below for a list.

===Building your own Desktop===

====Window Manager====
If you want to build your own customized desktop, a good start is choosing the window manager of your liking.

Here's a list of some of them:
*including basic Desktop Environment functionality
**the [[Wikipedia:NextStep|NextStep]] alike ones
***[http://www.windowmaker.org/ WindowMaker] <tt>(probably the most widespread NextStep like WM)</tt>
***[http://www.afterstep.org/ AfterStep] <tt>(another one of those)</tt>
***[http://blackboxwm.sourceforge.net/ BlackBox]
***[http://fluxbox.sourceforge.net/ FluxBox] <tt>(tabbed windows, lighweight)</tt>
**others
***[http://www.icewm.org/ IceWM] <tt>(lightweight, widespread)</tt>
***[http://enlightenment.sourceforge.net/ Enlightenment] <tt>(lots of features and eye candy)</tt>
***[http://www.pekwm.org PekWM] <tt>(kind of a one man show, but feature rich and extremely customizable)</tt>
*pure WindowManagers
**[http://golem.sourceforge.net/ Golem]
**[http://home.earthlink.net/~lab1701/larswm/ LarsWM] <tt>(unique tiling Window Manager)</tt>
**[http://www.nongnu.org/ratpoison/ ratpoison] <tt>(modeled after gnu screen)</tt>
**[http://fvwm.org/ fvwm] <tt>(small but powerful)</tt>
**[http://www.all-day-breakfast.com/wm2/ wm2] <tt>really small Window Manager</tt>
**[http://www.all-day-breakfast.com/wmx/ wmx] <tt>slightly more featureful version of wm2</tt>

====Taskbar/Panel====
Another thing that especially users coming to Linux from the Windows world would probably like is a Panel or Taskbar.

Here's a collection of independant low resource panels:
*[http://www.chatjunkies.org/fspanel/ F***ing Small Panel] <tt>(doesn't use any toolkit)</tt>
*[http://freshmeat.net/projects/hpanel/ HPanel] <tt>(doesn't use any toolkit)</tt>
*[http://fbpanel.sourceforge.net/ fbpanel] <tt>(depends on GTK 2)</tt>
*[http://jodrell.net/projects/perlpanel Perl Panel] <tt>(depends on GTK 2, gnomevfs, perl)</tt>
*[http://www.gkrellm.net/ GKrellM] <tt>(depends on GTK 2, flexible plugin based skinable vertical panel)</tt>

====Desktop Pinboard====
Then, the next thing you might be looking for is how to get icons onto your desktop. Usually this is done by the file manager who displays the content of a special directory as icons on the desktop. See the File Manager section to follow this approach.

However, you might decide for a really lightwight file manager which doesn't offer this feature. In that case all hope is not lost, for there are also special programs specialized in desktop icon management. Such are:
* [http://idesk.sourceforge.net/ iDesk] <tt>(recent versions need imlib2 only)</tt>

====File Manager====
File Managers are the fourth really important compontent of a desktop environment. There are plenty out their ranging from resource hugs to really lightweight and slim ones.

File Managers come with three distinct general user interface approaches: the two pane gui, the spacial and the browser gui. The browser gui is the one the Windows Explorer starting from Windows 2000 uses as well as earlier versions of Nautilus. The spacial view is the one known from Windows 95 and more recent versions of Nautilus. The two pane view is know to many from Norten Commander, Directory Opus or your favorite FTP client.

The following list provides an overview.
*FLTK
** [http://www.oksid.ch/flfm/ Fast Light File Manager] <tt>(spacial gui)</tt>
* FOX toolkit
** [http://roland65.free.fr/xfe/ X File Explorer] <tt>(browser and two pane gui)</tt>
*GTK
** [http://www.kaisersite.de/dfm/ Desktop File Manager] <tt>(spacial gui, incl. desktop icon management)</tt>
** [http://www.uwyn.com/projects/fm/ FM] <tt>(spacial, MAC OS 9 like gui)</tt>
** [http://radekc.regnet.cz/ Seksi Commander] <tt>(two pane gui)</tt>
*GTK 2
** [http://rox.sourceforge.net/ ROX Filer] <tt>(highly productive spacial gui, incl. panel and desktop icon
management)</tt>
** [http://blog.perldude.de/projects/filer/ Filer] <tt>(browser and two pane gui, requires Perl)</tt>
** [http://xffm.sourceforge.net/ XFFM] <tt>(browser and spacial gui, requires some XFCE libs)</tt>
** [http://logicaldesktop.sourceforge.net/ Logical Desktop] <tt>(browser gui, actually a very special approach)</tt>
** [http://tuxcmd.sourceforge.net/ Tux Commander] <tt>(two pane gui)</tt>
** [http://emelfm2.net/emelFM2/ emelFM2] <tt>(two pane gui with full customizable menu and toolbar, the best for power users)</tt>
** [http://thunar.xfce.org/index.xhtml Thunar] <tt>(requires some XFCE libs)</tt>
* OpenMotif
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xplore/xplore.php Xplore] <tt>(browser gui with productive 4 pane concept)</tt>
* QT 2
** [http://www.hi-net.cz/blaza/bfcommander/en/index.html BF-Commander] <tt>(two pane gui)</tt>
*Qt3
** [http://www.beesoft.org/download_bsc.html Beesoft Commander] <tt> (fast & easy two panel file manager, like Norton Commander)</tt>
* Tcl/Tk
** [http://users.tkk.fi/~mkivinie/X-Files/ X-Files] <tt>(two pane gui)</tt>
*X Toolkit
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xfm/ X File Manager] <tt>(spacial gui)</tt>
** [http://www.boomerangsworld.de/worker/ Worker] <tt>(two pane gui, highly productive and configurable)</tt>
** [http://xnc.dubna.su/ X Northern Captain] <tt>(interesting flexible two pane gui)</tt>
*3D Filemanagers
** [http://www.determinate.net/webdata/seg/tdfsb.html TDFSB] <tt>(3D gui, the most impressing 3D file browser so far)</tt>
** [http://www.forchheimer.se/bfm/ Brutal File Manager] <tt>(3D gui more for fun than productivity)</tt>
** [http://turma.sourceforge.net/software/3dfile/ 3DFile] <tt>(3D gui)</tt>
** [http://orbis.sourceforge.net/ Orbis] <tt>(3D gui)</tt>

==Choosing applications==
===Web Browser===
This is highly dependend on the way you use your browser, it's often worth it to try out all and just track general
memory usage. Remember that <tt>top</tt> and <tt>ps</tt> don't report correct memory usage, track totals only.

====Firefox====
Firefox is graphical web browser. One can install features like AdBlock and FlashClicktoplay which will decrease memory and
processor usage by hiding Flash and Java -adverts.

====Opera====
Opera is graphical web browser. You can easily enable/disable plug-ins and java (press F12) and decrease memory usage.
Opera uses QT as toolkit, so you may shave off some Mbytes off memory usage by using dynamically linked version if you use KDE.

====Konqueror====
Konqueror is graphical web browser. It's integrated with KDE and has several advanced features (esp. ca. KDE 3.5).
You may save some megabytes by using it instead of other browsers when using KDE.
It's not necessarily heavy even when used without running KDE.

====Dillo====
Dillo is minimalistic and very small graphical web browser.

====Elinks/Lynx====
elinks/lynx are both text mode web browsers. <tt>elinks</tt> handles tables and formatting much nicer than <tt>lynx</tt>.
Both go very easy on memory footprint.

{{Todo|...}}

==Disabling unneeded system deamons==
Another thing you can do to improve performance is to get rid of unneaded system daemons launched from your init scripts. Disable them by using the according configuration interface of your distro or by deleting links in the according runlevel directories (usually in <code>/etc/rc.d/</code>).

Daemons you usually don't need:
* httpd <tt>(Apache web server)</tt>
* mysqld <tt>(MySQL database server)</tt>
* smbd <tt>(SMB windows filesharing server)</tt>
* pppd <tt>(PPP server for connections through modems and serial lines)</tt>

==Adjusting filesystems==
You can also try to optimize memory usage by making sure that you have as little as possible of your filesystem residing in RAM. To do this make sure that the following mount points are set to reside on your harddisk in {{path|/etc/fstab}}.
* /dev (not possible if you use udev)
* /tmp

==Other tips==
===Disk space===
When using Debian/Ubuntu/other derivative, use <tt>aptitude</tt> as package manager, and use it as soon as possible. Use it and only it to install and remove packages.

One of it's most usefull features is that it tracks packages you install and marks packages installed via dependency as such, so when you remove a package that is no longer used, or package updates and doesn't use a library anymore, that dependency will get uninstalled.

You can mark packages installed as automatically installed by hitting 'M' (uppercase m), it will be marked for deinstallation if it's not longer required.

You could also install localepurge wich will remove all unneded locales and localized manpages for packages you install.

Problem with display remaining black after resume

2006-03-04T20:18:45Z

Gq: /* Solution for ThinkPads with ATI graphic chips */

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

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

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43p}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)

==Affected Operating Systems==
*Linux (it's a kernel issue)

==Solutions==
===Solution for ThinkPads with ATI graphic chips===
The Solution is to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this can look like this:
title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it can look like this:

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

Additionally, in {{Ubuntu}} or {{Kubuntu}} it might be necessary modify {{path|/etc/default/acpi-support}}. Check to make sure that ACPI_SLEEP and SAVE_VBE_STATE are both uncommented and set to true. (If you are using this trick with Intel graphics chips, as suggested below, make sure that nothing with respect to VBE state is done--don't repost the video, don't save the VBE state.)

Otherwise see the example script below.

Another one solution will be to use vbetool. If you are using Debian with hibernate package just uncomment "EnableVbetool yes" in /etc/hibernate/hibernate.conf (or /etc/hibernate/ram.conf)

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

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

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

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

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

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

# waking up
# restore system clock
hwclock --hctosys

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

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

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

Ultrabay Slim DVD Multi-Burner III

2006-03-04T12:04:37Z

Gq: /* Actual Drives */

__NOTOC__
{| width="100%"
|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;">
=== UltraBay Slim Super Multi-Burner Drive ===
This is an DVD Writer for the Ultrabay Slim.

=== Features ===
* Read capabilities
** CD-ROM (24x)
** DVD-ROM (8x)
* Write capabilities
** CD-R (24x)
** CD-RW (16x)
** DVD-R (8x)
** DVD-R DL (2x)
** DVD-RW (4x)
** DVD-RAM (3x)
** DVD+R (8x)
** DVD+R DL (2.4x)
** DVD+RW (4x)

</div>
|style="vertical-align:top" |
[[image:UltraBay Slim Optical Drive.gif|UltraBay Slim Optical Drive]]
|}

*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-62441 IBMs product overview page for this drive]

==== Actual Drives ====
* ?? (may be [http://www.panasonic.com/industrial/computer/storage/optical/models/UJ846B.htm Matshita UJ-846-B])

=== IBM Partnumbers ===
* Order PN: 40Y8623 (flat bezel), 40Y8622 (curved bezel)
* FRU PN: 39T2677 (flat bezel)

=== Linux Support ===
If connected at boot time, the drive is {{path|/dev/hdc}}.

=== Supported with ===
*ThinkPad {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T60p}}
*ThinkPad {{Z60t}}
*[[UltraBase X4]], [[ThinkPad X4 Dock]], [[UltraBase X6]]

[[Category:Components]]