ThinkWiki - User contributions [en]

Ultrabay

2005-05-05T10:55:21Z

217.93.14.204:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:UltraBay.jpg|UltraBay drives]]
|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;">
=== IBM UltraBay ===
UltraBay is IBM's name for the swapable drive slot. With IBMs words: "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." Introduced back in the times of the 770 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.
Note that the optical drive bay in G series Thinkpads is not an UltraBay in that the drives are fixed and not removable.

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.
</div>
|}
{| border="1" cellspacing="0" cellpadding="2"
|+Overview over UltraBay types and available devices
! UltraBay Type !! featured in !! available drives
|-
| [[Image:Icon20_ultrabay.png]] UltraBay || 365(?), 380(?), 380D(?), 380ED(?), 760, 765 || [[Image:Icon20_floppy.png]] [[Image:Icon20_cdrom.png]]
|-
| [[Image:Icon20_ultrabayii.png]] UltraBay II || 770, 770E, 770ED, 770X, 770Z, SelectaDock III || [[Image:Icon20_floppy.png]] [[Image:Icon20_cdrom.png]] [[Image:Icon20_dvd.png]] [[Image:Icon20_hdd.png]] [[Image:Icon20_battery.png]], ZIP-100, ZIP-250
|-
| [[Image:Icon20_ultrabayfx.png]] UltraBay FX|| 390, 390E, 390X, i1720, i1721 || [[Image:Icon20_floppy.png]] [[Image:Icon20_cdrom.png]] [[Image:Icon20_dvd.png]] [[Image:Icon20_hdd.png]] [[Image:Icon20_cdrw.png]]
|-
| [[Image:Icon20_ultraslimbay.png]] UltraSlimBay || 570, 570E, 600, 600E, 600X || [[Image:Icon20_floppy.png]] [[Image:Icon20_cdrom.png]] [[Image:Icon20_cdrw.png]] [[Image:Icon20_dvd.png]] [[Image:Icon20_hdd.png]] [[Image:Icon20_battery.png]], ZIP-100, ZIP-250, LS-120
|-
| [[Image:Icon20_ultrabay2000.png]] UltraBay 2000 || A20, A21, A22, A30, T20, T21, T22, T23, Dock, Dock II, UltraBase X2|| [[Image:Icon20_floppy.png]] [[Image:Icon20_cdrom.png]] [[Image:Icon20_cdrw.png]] [[Image:Icon20_dvd.png]] [[Image:Icon20_combo.png]] [[Image:Icon20_multiburner.png]] [[Image:Icon20_hdd.png]] [[Image:Icon20_battery.png]], ZIP-100, ZIP-250, LS-120, LS-240
|-
| [[Image:Icon20_ultrabayplus.png]] UltraBay Plus || A30, A30p, A31, A31p, R30, R31, R32, R40, T23, T30, UltraBase X3 || [[Image:Icon20_floppy.png]] [[Image:Icon20_cdrom.png]] [[Image:Icon20_cdrw.png]] [[Image:Icon20_dvd.png]] [[Image:Icon20_combo.png]] [[Image:Icon20_multiburner.png]] [[Image:Icon20_hdd.png]] [[Image:Icon20_battery.png]], ZIP-100, ZIP-250, WorkPad Cradle, Numpad
|-
| [[Image:Icon20_ultrabayslim.png]] UltraBay Slim || T40, T40p, T41, T41p, T42, T42p, T43, T43p, UltraBase X4 || [[Image:Icon20_dvd.png]] [[Image:Icon20_combo.png]] [[Image:Icon20_multiburner.png]] [[Image:Icon20_hdd.png]] [[Image:Icon20_battery.png]]
|-
| [[Image:Icon20_ultrabayenh.png]] UltraBay Enhanced || R50, R50p, R51, R52 || [[Image:Icon20_multiburner.png]] [[Image:Icon20_combo.png]] [[Image:Icon20_dvd.png]] [[Image:Icon20_hdd.png]] [[Image:Icon20_battery.png]]
|-
|}

{| border="1" cellspacing="0" cellpadding="2" style="text-align:center;"
|+Compatibility Matrix (read columns as slots with rows as devices that are compatible)
! Slots<hr />Devices!! [[Image:Icon20_ultrabay.png]]<br />UltraBay<br />  !! [[Image:Icon20_ultrabayii.png]]<br />UltraBay<br />II !! [[Image:Icon20_ultrabayfx.png]]<br />UltraBay<br />FX !! [[Image:Icon20_ultraslimbay.png]]<br />UltraSlimBay<br />  !! [[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
|-
|'''UltraBay''' || yes || Adapter || - || - || - || - || - || -
|-
|'''UltraBay II''' || - || yes || - || - || - || - || - || -
|-
|'''UltraBay FX''' || - || - || yes || - || - || - || - || -
|-
|'''UltraSlimBay''' || - || - || - || yes || - || - || - || -
|-
|'''UltraBay 2000''' || - || - || - || - || yes || yes || - || -
|-
|'''UltraBay Plus''' || - || - || - || - || - || yes || - || -
|-
|'''UltraBay Slim''' || - || - || - || - || Adapter || Adapter || yes || yes
|-
|'''UltraBay Enhanced''' || - || - || - || - || Adapter || Adapter || - || yes
|}

===Mechanical Characteristics===
*UltraBay FX: The combined floppy drive and CD-ROM, DVD or CDRW mechanism found in the 390/390E/390X.
*UltraSlimBay: Frame, rectangle like blending
*UltraBay 2000: Frame, blending has cut out egde on the right
*UltraBay Plus: same as UltraBay 2000, but can take WorkPad cradle and numpad
*UltraBay Slim: notably thinner than UltraBay 2000, cut out right edge in blending
*UltraBay Enhanced: Accepts UltraBay Slim devices

==Linux Support==
The pinout switching is done by the BIOS and hardware, so that it is completely transparent to the operating system.
Hence, all IDE drives are supported by the IDE driver in the linux kernel. SCSI emulation is possible. Floppy drives are supported by the standard floppy driver. ZIP drive support is possible through the ide-disk driver. Batteries are BIOS controlled, anyway.

Hotswapping is supposed to be supported as well, using hdparm to (un)register devices. NOTE: This seems to be broken with 2.6 kernels.
If UltraBay Plus devices are supported is not known.

[[Category:Glossary]] [[Category:i1720]] [[Category:570]] [[Category:570E]] [[Category:600]] [[Category:600E]] [[Category:600X]] [[Category:770]] [[Category:770X]] [[Category:770Z]] [[Category:A20m]] [[Category:A20p]] [[Category:A21m]] [[Category:A21e]] [[Category:A21p]] [[Category:A22m]] [[Category:A22e]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[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]]

ThinkLight

2005-05-05T10:54:16Z

217.93.14.204:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:Thinklight.jpg|ThinkLight]]
|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;">
The ThinkLight is a little LED light integrated into the top edge of the display frame in the A, R, T and X ThinkPad models. It illuminates the ThinkPad's keyboard so that one can type in the dark without using an external light source. The ThinkLight can be controlled via the Fn-PageUp key combination or via ACPI on some of the newer models.
Note that the ThinkLight is not available on the G series ThinkPads.
</div>
|}
==Linux Support==
Controlling the ThinkLight with the keyboard works on all systems since it relies on the BIOS exclusively. Just press Fn-PageUp to toggle its state between on and off.

Support for controlling the light with ACPI is provided by [[ibm-acpi]]. After installing it, a simple
{{cmdroot|echo on > /proc/acpi/ibm/light}}
switches it on and a
{{cmdroot|echo off > /proc/acpi/ibm/light}}
switches it off again.

This allows one to control the light in scripts. Unfortunately, no known ThinkPad comes with a light sensor (yet). ;)

[[Category:Glossary]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R50]] [[Category:R50p]] [[Category:R50e]] [[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]]

Problem with high power drain in ACPI sleep

2005-05-05T10:50:27Z

217.93.14.204:

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

==Problem description==
Several people realised 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).
*One thing to keep in mind, though, is that some models only suffer this problem with certain software. For example, my T40 (2374-94U) has the high power drain issue with the stock Fedora Core 3. If I use one of the more recent kernels from [http://www.sas.upenn.edu/~vbraun/computing/T41/kernel.html Volker Braun's T-41 site], everything (suspend-to-RAM, suspend-to-disk) works just fine and my battery life seems much better than APM. In other words, just because you see this problem with your ThinkPad with your current software does not mean that your ThinkPad will doomed to always be affected. There are similar solutions for Debian-based systems too.

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;" |
* [[:Category:R40 | R40]]
** 2722-5MG
** 2722-B3G
** 2897-GWU
* [[:Category:R50 | R50]]
** 1829-7RG
** 1829-6DM
** 1836-3SU
* [[:Category:R51 | R51]]
** 1829-EHG
** 1836-Q6U
*[[:Category:T23 | T23]]
**2647-???
* [[:Category:T30 | T30]]
** 2366-81A
** 2366-97U
*[[:Category:T40 | T40]]
**2373-MU3
**2373-82U
**2373-92U
**2373-22G
**2373-19G
**2373-A1U
*[[:Category:T40p | T40p]]
**2373-G1U
**2373-G3U
**2373-G3G
**2373-G1G
* [[:Category:T41 | T41]]
**2379-DJU
**2373-9HU
**2373-4FG
**2373-4PG
**2373-2FG
**2373-6U4
**2373-7JU
* [[:Category:T41p | T41p]]
**2373-9FU
* [[:Category:T42 | T42]]
**2378-DUU
**2373-FWG
**[[2373-6ZG]]
* [[:Category:X21 | X21]]
| style="vertical-align:top;background-color:#e9f9e9;" |
*[[:Category:R50p | R50p]]
*[[: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]]
|}

==Affected Operating Systems==

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

==Status==
The cause of the problem is not really clear, yet.

A faulty DSDT might be responsible for the phenomenon. The thinkpad T4x DSDT has a few small bugs, none of which should cause the extra power drain. (Interesting to note: The DSDT from BIOS 3.13 (Nov 04) for the T42p compiles without bugs.)

There is a interesting discussion taking place in the [http://bugme.osdl.org/show_bug.cgi?id=3022 OSDL Bugzilla].

Update: it seems that the most significant difference can be made by properly turning off the video chip.

==Solutions==
===For Thinkpads with Radeon graphic driver===
A 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.

For [[:Category:Fedora Core | Fedora Core]] there's are precompiled patched kernels (2.6.11-rc2 based) available:
*[http://carrot.hep.upenn.edu/~vbraun/kernel-T4x/test/kernel-DANGEROUS-T4x-2.6.11-8.i386.rpm kernel with unconditional patch applied]
*[http://carrot.hep.upenn.edu/~vbraun/kernel-T4x/test/kernel-T4x-2.6.11-8.i386.rpm kernel with conditional patch applied].

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.

{{WARN|This solution enables doing suspend-to-D2 on non-PPC-machines, which is not tested at all and supposed to be the wrong thing to do! Be careful and have a look at the discussion for kernel bug 3022 (see above) before applying the patch.}}

===Other models===
Nothing yet.

[[Category:R40]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:X21]] [[Category:X30]] [[Category:X31]] [[Category:X40]]

Problem with fan noise

2005-05-05T10:44:55Z

217.93.14.204:

Information about the fan noise problem in Thinkpad models from 2003/2004.

==Problem description==

There seem to be two different occurances of the problem (or two different problems).

===acceleration problem:===
The Thinkpad Fan accelerates in regular intervals, making an annoying noise.

===always on problem:===
The Fan is always on, even though the processor is rather cool.

==Affected Models==

===acceleration problem:===
*Thinkpad T40, T40p, T41, T42(?)

===always on problem:===
*Thinkpad T40, T40p, T41, T41p, T42, T42p, T43
*Thinkpad R50, R50p, R51, R52, R32
*Thinkpad X40
*Thinkpad A31p
*Thinkpad 770X

==Affected Operating Systems==

===acceleration problem:===
*Linux, all flavours

===always on problem:===
*Linux, all flavours
*FreeBSD 5.3
*Windows XP
*Windows 2000 pro

==Status==

===acceleration problem:===
IBM released an update to the embedded controller program that seems to at least partially solve this problem:

Version 3.03 - 1RHT70WW
NOTE: This version of Embedded Controller Program will only work with BIOS Version 3.06f (or higher).
* (Fix) Reduced Fan noise in some models.

The update can be found here: http://www-306.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50279

===always on problem:===
The problem is yet unsolved.

IBM made a statement regarding this on their homepage:
http://www-307.ibm.com/pc/support/site.wss/MIGR-56504.html

It seems that it's a feature of centrino - http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2004-September/019737.html
Perhaps it's fixable by adding the fans and temps to the dsdt?

====partial fix:====
When loading [http://ibm-acpi.sourceforge.net/ IBM ThinkPad ACPI Extras v0.11] with experimental switch (modprobe ibm_acpi experimantal=1), it is possible to read and write the status of fan:

'''#cat /proc/acpi/ibm/fan'''
status: enabled
speed: 3580
commands: enable, disable

'''#echo disable > /proc/acpi/ibm/fan'''

'''cat /proc/acpi/ibm/fan'''
status: disabled
speed: 0
commands: enable, disable

But the fan will then '''never''' wake up. So, we need a small script witch is constantly checking the temperature and setting the fan on/off when needed. (deamon? cron job?) If anyone has an idea please post it here.

'''sh script example'''

<pre>
#!/bin/sh

MAXTEMP=50

while [ 1 ];
do
fan=no

for temp in `sed s/temperatures:// < /proc/acpi/ibm/thermal`
do
test $temp -gt $MAXTEMP && fan=yes
done

command='disable'
test "$fan" = "yes" && command='enable'
echo $command > /proc/acpi/ibm/fan

sleep 20
done
</pre>

'''daemon script example'''

<pre>
#! /bin/sh

N=/etc/init.d/fan

set -e

case "$1" in
start)
# make sure privileges don't persist across reboots
if [ -d /var/run/fan ] && [ "x`ls /var/run/fan`" != x ]
then
touch -t 198501010000 /var/run/fan/*
fi
fan.sh & # Script from above
;;
stop|reload|restart|force-reload)
killall fan.sh
echo enable > /proc/acpi/ibm/fan
;;
*)
echo "Usage: $N {start|stop|restart|force-reload}" >&2
exit 1
;;
esac

exit 0
</pre>

==Solutions==

===acceleration problem:===

====Replacing the fan====
Some people reported that they replaced the original fan against one of a similar notebook without the problem has worked for them,
i.e. changing a T41s fan against one from a T41p.

====BIOS upgrade====
You can try upgrading your embedded controller program to version 3.03 or newer.

The update can be found here: http://www-306.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50279

===always on problem:===

It seems like for some people a combination of enabling dynamic frequency scaling and using the most recent radeon drivers (from xorg 6.8.x) with the DynamicClocks option enabled helped lowing the fan rotation and hence making it more quiet.

Also the fglrx driver from ATI is said to show the same effect when used together with dynamic frequency scaling.

On a 770X the fan can be fully controlled through ACPI. Thermal Zone THM5 (possibly the battery/charging circuit, it's definitely warmer when using 5v PCMCIA cards and AC) triggers it to turn on and not ever off by design. Can be solved by a custom DSDT, which also makes use of the variable-speed features of the fan (will release this once I've finished tweaking and testing it).

[[Category:770X]] [[Category:A31p]] [[Category:R32]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X40]] [[Category:X41]]

Problem with DVI throughput

2005-05-05T10:41:57Z

217.93.14.204:

Information about the DVI throughput problem on port replicators and docks with Thinkpads from approximately 2000-2004.

==Problem description==

All Thinkpad port replicators and docking stations support a maximum resolution of 1280x1024 on the replicators/docks DVI port.
Resolutions above are not supported in standard drivers at all and lead to random screen corruption if used with modified or alternative drivers.

Random screen corruption means that approximately 1 out of 5 times you will have a lot ot flickering blue and green pixels (roughly gathered to vertical stripes) on your DVI driven display.

I also discovered the phenomena of an unsharp picture when having automatic picture expansion enabled on my 1600x1200px display. Switching this off recovers the picture quality.

It is not entirely clear so far if the screen corruption problems are a driver or hardware problem.

==Affected Models==

*probably all Thinkpad models produced since the naming scheme change
*all port replicators and docking stations for these models, namely

==Affected Operating Systems==

*Linux, all flavours
*Windows, all flavours

==Status==

IBM knows about this and has included this limitation into the specs of all these docking solutions.

It is possible to run higher resolutions on the DVI port. Linux supports this natively. With Windows you need to install an alternative driver for the ATI graphics card since the IBM driver doesn't support higher resolutions than 1280x1024 on DVI. Also one can do some registry hacking to make the higher resolutions available in the Presentation Manager.

However, on both displays still remains the phenoma of random screen corruption.

==Solutions==

===Linux===

Under Linux, you can in theory make use of higher resolutions. (This is currently limited by the unability of drivers to use the DVI port.) If screen corruption should occur, you can try fixing it by changing from X to the console and back. Doing this often helps.

===Windows===
The solution to the Windows driver problem can be found in patched ATI driver sets like [http://www.dna-drivers.nl/ DNA-ATI] or [http://www.omegadrivers.net OMEGA] drivers.

Also, Dax Kelson posted [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2004-June/018167.html this mail] in the [[mailinglists#Linux-Thinkpad_Mailinglist | Linux-Thinkpad Mailinglist]]. The tool he recommends solves the problem indeed, but introduces the new problem, that you can't use resolutions of 1400x1050 px anymore, since this is a notebook only resolution which is not supported by the standard Catalyst drivers.

The remaining problem with Windows is that IBMs practical Presentation Director utility still doesn't support the higher resolution.
This issue is solvable by doing some manual modifications to Presentation Directors registry entries. If you don't want to tweak your registry you can use multi-res (packaged with the OMEGA drivers) instead of Presentation Director.

If you want to use Presentation Director, follow this procedure:
* Add a profile with VGA output and set it to 1600x1200.
* Then you also add a profile with DVI output and set it to 1280x1024.
* After finishing the wizard you open regedit.
* Look for the Presentation directors key structure (HKEY_CURRENT_USER/Software/IBM/NPdirect/Data/Common/Presentation/Schemes) and
* copy the resolution value from the VGA profile to the DVI profile. (So if your VGA profiles name is VGAprof and the DVI profiles is DVIprof, you copy the Resolution keys value from HKEY_CURRENT_USER/Software/IBM/NPdirect/Data/Common/Presentation Schemes/VGAprof/01 to ....../DVIprof/01.)
* Close regedit (and eventually reboot) and restart Presentation Director.
* You should be have the wanted resolution in the properties of your DVI profile.

[[Category:R40]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]

PreDesktop Area

2005-05-05T10:40:44Z

217.93.14.204:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:hpa.jpg|IBM PreDesktop Area]]
|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;">
=== The PreDesktop Area ===
The Predesktop Area is part of the HPA (generally known as the "Host Protected Area", but called "Hidden Protected Area" by IBM). The HPA is a special area on your harddisk, usually hidden to partitioning tools. It includes all the software and data needed to recover the preloaded state of the ThinkPad. The HPA also includes some diagnostic tools and a (MS Windows only) backup tool.

The Predesktop area was introduced with the R/T/X 40 series of ThinkPads and is present on the preinstalled harddisks of all ThinkPads shipped by IBM since then.
</div>
|}
==General information about the HPA==
The HPA seems to be using [http://www.phoenix.com/en/Products/Trusted+Applications/Phoenix+FirstWare/default.htm Phoenix FirstWare]. FirstWare is (in short) an implementation of two technologies: BEER and PARTIES. (Yes, those names are correct!) BEER (Boot Engineering Extension Record) and PARTIES (Protected Area Run Time Interface Extension Services) are described in [http://www.t13.org/project/d1367r3-PARTIES.pdf this T13 working draft]. There is a more general introduction to PARTIES on the [http://www-1.ibm.com/support/docview.wss?rs=0&uid=psg1MIGR-51248&loc=en_US IBM site].

Basically, what seems to be going on is that the Phoenix BIOS hides the last few gigabytes of the harddisk (that is the HPA) to the OS. Note that this is just a setting in the BIOS and can be disabled. The HPA can be accessed by pressing the [[Access IBM Button]] at boot time. The BIOS will then parse the BEER (128 bytes, situated in the last sector of 512 bytes of the harddisk) and the "Directory of Services" (consisting of directory entries of 64 bytes each, starting in the last sector and spilling over into the previous sectors) to see what part of the HPA should be launched. In (most?) ThinkPads the BEER tells the BIOS to launch the Access IBM Predesktop Area. The system will then actually be booting into a (minimal) DOS which is able to launch a graphical shell (called Phoenix FirstSight). IBM has simply rebranded this graphical shell to the Access IBM Predesktop Area. From this graphical shell one can launch several tools (BIOS Setup Utility, diagnostic tools, recovery tools).

==Three BIOS options==
The BIOS has three settings for the "IBM Predesktop Area" (in the Security category):
*Secure: No user or SW-initiated changes
*Normal: Change allowed; Contents hidden from OS
*Disabled: Not Usable. Visible and Reclaimable

Normal and secure seem to behave identical when using GNU/Linux. Maybe changes are possible in "Normal" mode using an MS Windows application. With "Disabled" you can even remove the HPA.

==Details of the HPA==
Fabrice Bellet describes a [http://bellet.info/laptop/t40.html#the_predesktop_area technique he used] to explore the HPA of his ThinkPad T40, using GNU/Linux tools. This technique is only for the more curious or more careless people. It uses "dd" to copy the sectors on the harddisk containing the HPA from "/dev/hda" to a new file: when using "dd" on "/dev/hda" you are only one small typo away from an unrecoverable disaster!

Here follows a more detailed description of the HPA on a ThinkPad T41 (60 GB harddisk) to contrast his findings.

On this ThinkPad T41 the HPA is 3,4 GB in size. It contains 8 consecutive PSAs (Protected Service Areas). Six of those start with an x86 boot sector.

* The first PSA is 3,2 GB in size. The OEM-ID of the boot sector is: "IBM 7.1". It seems to hold a copy of the preloaded OS and everything needed to generate a bootable DVD-ROM for it, even an El Torito boot image and a boot catalog: see [[Backing up the preloaded OS]].

* The second PSA is exactly 2 MB in size. According to its entry in the Directory of Service it's the "BIOSWORKAREA".

* The third PSA is only 7,4 MB in size. The OEM-ID of the boot sector is: "MSWIN4.1". It seems to be an image of a 1,44 MB bootable floppy disk (with MS DOS) and a directory containig 6 MB of FirstWare tools. It will be launched by the "Recover to factory contents" tool of the Predesktop Area. Those "factory contents" should be the data on the first PSA.

* The fourth PSA is only 1,4 MB in size. The OEM-ID of the boot sector is: "IBM 7.1". It too seems to be an image of a (sort of) 1,44 MB bootable floppy disk. It will be launched by the "Restore your backups" tool of the Predesktop Area.

* The fifth PSA is again 7,4 MB in size. The OEM-ID of the boot sector is: "IBM 7.0". It will be launched by the "Run diagnostics" tool of the Predesktop Area.

* The sixth PSA is also 7,4 MB in size and the OEM-ID of the boot sector also is: "IBM 7.0". It will be launched by the "Create diagnostic disks" tool of the Predesktop Area. It contains a copy of a (sort of) bootable 1,44 MB floppy disk, some tools and compressed copies of the diagnostic disks.

* The seventh PSA is only 1,4 MB in size. The OEM-ID of the boot sector is "PHOENIX". It seems to be a copy of a (sort of) 1.44 MB bootable floppy disk too and only contains a (minimal) DOS and the FirstSight application. Basically, this is the Access IBM Predesktop Area.

* The eigth PSA is 101 MB in size. It doesn't have a boot sector. It contains the FirstWare Reserved Area. That probably is some sort of swap space for the FirstWare system.

==How to remove it==
There's a BIOS setting in my T42p. After disabling the Predesktop Area, it's possible to remove the partition with standard tools. i.e. fdisk, mkfs, ...

==Alternative uses?==
It might be possible to use the FirstWare tools included in the HPA to make the HPA more useful for GNU/Linux purposes. For instance, the copy of the preloaded OS could be replaced with an emergency backup of your GNU/Linux distribution. Maybe the Predesktop area could be even used to boot into a GNU/Linux rescue system. Whether the Phoenix propietary tools really allow alternative uses and whether those tools do not make it too hard to accomplish those cannot yet be said. It seems realistic to assume that the benefits of those alternative uses aren't worth the effort to accomplish them. Still, it might be fun (altough possibly hazardous to your system) to try ...

==Related links==

*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46023 Predesktop Area white paper]
*[http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-46025 Predesktop Aministrator Utility (DOS)]
*[http://webstore.ansi.org/ansidocstore/product.asp?sku=ANSI+INCITS+346-2001 Protected Area Run Time Interface Extension Services (PARTIES) ANSI INCITS 346-2001 ($18)]
*[http://www.phoenix.com/NR/rdonlyres/7465D3CF-B0E3-4F64-9122-47D9C83028D0/0/cme_firstware_wp.pdf Phoenix FirstWare White Paper]
*[http://www.win.tue.nl/~aeb/linux/Large-Disk-11.html Section 11 of the Large Disk HOWTO (Clipped disks)]

__NOTOC__
[[Category:Glossary]] [[Category:R40]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]

Modem Devices

2005-05-05T10:39:43Z

217.93.14.204:

== Internal Thinkpad Modem ==

Linux drivers for the various internal Thinkpad modems.

=== scanModem script ===

To identify your internal modem, it is always a good advice to start with the scanModem script from:
http://linmodems.technion.ac.il/#scanmodem
Grab a current version and have a look at its output.

=== 3com ===

The following cards are known to contain a 3Com modem chip:
*[[3Com 10/100 Ethernet Mini-PCI Adapter with 56K Modem]]

=== Actiontec ===

The following cards contain this chip:
*[[IBM High Rate Wireless LAN Mini-PCI Adapter with Modem]]

=== Agere (T40p) ===
Give the drivers for Agere Softmodems from Smartlink a try:
http://www.smlink.com/main/item.php?ln=en&item_id=84&main_id=32

The following cards contain this chip:
*[[IBM Integrated 56K Modem (MDC-2)]]
*[[IBM Integrated Bluetooth II with 56K Modem (BMDC)]]
*[[IBM High Rate Wireless LAN Mini-PCI Adapter with Modem II]]

=== Conexant (T42p) ===

Although, the Smartlink driver for Agere modems (see above) is able to communicate with the modem via AT commands, it cannot dial out (contradicting reports welcome!).

If your favourite distribution does not include a hsfmodem driver (search for "hsfmodem" or "Conexant"), you can try the one from Linuxant: http://www.linuxant.com/drivers (14k free as in beer, 56k+Fax license 15$, they explain this policy under: http://www.linuxant.com/store/faq.php )

The following cards contain this chip:
*[[IBM Integrated Bluetooth III with 56K Modem (BMDC-2)]]
*[[IBM Integrated Bluetooth IV with 56K Modem (BMDC-3)]]

=== Lucent / Ambit ===
The SmartLink driver may work.

The following cards contain this chip:
*[[Mini-PCI Modem card]]
*[[Modem Daughter Card (MDC)]]
*[[Intel Pro/100 SP Mobile Combo Adapter]]

=== MWave ===
MWave is a DSP (Digital Signal Processor) technology that has been used in certain IBM ThinkPad's for Audio, Modem or a combination of the two.<br>
A Linux MWave Modem driver can be found in kernel 2.4.11 and later, but only supports the PCI based MWave controller (MDSP3780) found in the following machines:
* ThinkPad 600 / 600D / 600E
* ThinkPad 770D / 770ED / 770X / 770Z

In addition to the kernel driver you will need some userland utilities (MWave Manager) that can be found here:
http://sourceforge.net/projects/acpmodem/

SUSE includes the MWave utilities as part of the 'mwavem' RPM.

=== Xircom ===
The following cards contain a Xircom modem chips:
*[[Intel 10/100 Ethernet Mini-PCI Adapter with 56K Modem]]
*[[Xircom 10/100 EtherJet Mini PCI Adapter with 56K Modem]]

[[Category:Drivers]] [[Category:600]] [[Category:600D]] [[Category:600E]] [[Category:770D]] [[Category:770ED]] [[Category:770X]] [[Category:770Z]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[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:TransNote]]

IrDA

2005-05-05T10:39:24Z

217.93.14.204:

== ThinkPad IrDA configuration ==

IrDA can be used to communicate using Infrared to other IrDA compliant devices, such as other Notebooks, PDA's and mobile phones.

All IBM ThinkPads manufactured in the last years have integrated IrDA that can be used in one of two modes, SIR or FIR.
Some very old ThinkPads only support SIR mode, or might not have IrDA support at all.

The purpose of this document is to get the IrDA hardware in your ThinkPad operational, setting up communication to other devices is not covered. However, the external links section can prove useful for this.

=== Serial IR (SIR) ===
SIR is limited to serial datarates up to 115.2Kb/s

==== Linux 2.4 kernel config ====
Edit /etc/modules.conf and add the following lines
alias tty-ldisc-11 irtty
alias char-major-161 ircomm-tty

=== Fast IR (FIR) ===
FIR is the preferred mode of IrDA operation and operates at a bandwidth of 4 Mbps

Main problem here is that the chips FIR mode needs to be activated. On A, G, R, T and X model ThinkPads, the easiest way to activate FIR mode is by entering BIOS setup during boot-up by pressing F1 when prompted.
Then, selecting 'Config' followed by 'Infrared' will allow you to control the IrDA operation. Here you will need to select the option to Enable the infra-red port. Be sure to save the changes, and then Exit.

Note: Changing these BIOS settings do not affect Windows 2000 or XP operating systems, but may cause memory resource issues in older windows versions, or other legacy operating systems.

If changing the BIOS setting is not an option or if the settings cannot be altered, as on some older ThinkPads, the FIR mode can be activated by running Linux OS with one of the following:

* setpnp as part of the old pcmcia-utils source package
* tpctl, but only for some old ThinkPads

If the FIR mode is not activated, attempts to load the nsc-ircc module will result in an error in syslog of "Wrong chip version ff".

=== Very Fast IR (VFIR) ===

Some Thinkpads come with an even faster version of IrDA (VFIR) that operates at 16 Mbps. This may cause some incompatibilities with devices that expect to be able to communicate in FIR mode. You can check your speed by doing the following:

cat /proc/sys/net/irda/max_baud_rate

Additionally, you can revert to regular FIR by doing the following:

echo 4000000 > /proc/sys/net/irda/max_baud_rate

Similarly, you can also set IrDA operation at the conventional serial IR port bandwidth (SIR):

echo 115200 > /proc/sys/net/irda/max_baud_rate

==== Linux 2.4 kernel config ====
Edit /etc/modules.conf and add the following lines

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3
pre-install nsc-ircc setserial /dev/ttyS1 uart none port 0 irq 0

==== Linux 2.6 kernel config ====
Edit /etc/modprobe.conf and add the following lines

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3
install nsc-ircc /bin/setserial /dev/ttyS1 uart none port 0 irq 0; /sbin/modprobe --ignore-install nsc-ircc

=== Some other things you might want to do with IrDA ===

# add fast PPP support:
modprobe irnet

# if needed, limit further the size of the transmit window
echo 1 > /proc/sys/net/irda/max_tx_window

== External links ==
[http://irda.sourceforge.net/ Linux-IrDA Project] (External)

[http://pcmcia-cs.sourceforge.net/ Linux PCMCIA Project] (External)

[http://tpctl.sourceforge.net/ tpctl homepage] (External)

[[Category:Drivers]] [[Category:600]] [[Category:600D]] [[Category:600E]] [[Category:770D]] [[Category:770ED]] [[Category:770X]] [[Category:770Z]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[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]]

How to recover the preloaded OS

2005-05-05T10:38:51Z

217.93.14.204:

Here you can find all kinds of information about the preloaded OS found on recent ThinkPads.

*[[Ordering Recovery CDs]] <tt>(What you should do to get them)</tt>
*[[Recovering from Recovery CDs]] <tt>(useful hints to save you from screaming)</tt>
*[[Backing up the preloaded OS]] <tt>(if you can't get the CDs but still have the preloaded system)</tt>
*[[Recovering without Recovery CDs]] <tt>(what to do if any trace of the Preload is lost)</tt>
*[[PreDesktop Area | The PreDesktop Area]] <tt>(all you should know about it)</tt>

[[Category:R40]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]
[[de:Betriebssystem RÃ¼ckgewinnung]]

How to install ndiswrapper for the Intel 2200bg WLAN adaptor

2005-05-05T10:36:44Z

217.93.14.204:

== Usage of the centrino wlan-adapter 2200BG found in some thinkpads: ==
Find a detailed description here:
http://ndiswrapper.sourceforge.net/wiki/index.php/Intel2200

Note that there is also a [[ipw2200 | linux native open source driver]] available for this card.

[[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]

How to change the BIOS bootsplash screen

2005-05-05T10:31:59Z

217.93.14.204:

== BIOS-Bootsplash ==

This page describes how to replace the standard IBM BIOS Bootsplash (The one with the Thinkpad- and Pentium M-Logo), without access to Microsoft Windows or a floppy drive.

=== Getting the Files ===
You'll need the bios upgrade file from the IBM website.

==== Method 1: Using a Non-Diskette-File and cabextract ====

For ThinkPad R50/p, R51 (1829, 1830, 1831, 1836), T40/p, T41/p, T42/p this file is suitable:
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj28us.exe 1ruj28us.exe]
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj29us.exe 1ruj29us.exe] NEW!
There may be a more recent file on the IBM website.

You need the cabextract tool to extract files from the exe:
apt-get install cabextract

Do this to get the ibm file and extract the disk image from it:
cd /tmp
wget ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj28us.exe
cabextract -F *.IMG 1ruj28us.exe
mv 1RUJ28US.IMG floppy.bin

==== Method 2: Using a Diskette-File and dosemu ====
Another option is to use the "Diskette BIOS file".<br>
For ThinkPad R50/p, R51 (1829, 1830, 1831, 1836), T40/p, T41/p, T42/p this file is suitable:
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj28ud.exe 1ruj28ud.exe]
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/1ruj29ud.exe 1ruj29ud.exe] NEW!

The file is an OS/2 executables and don't run with wine, so you need to install dosemu to run it and create the image.<br>
apt-get install dosemu dosemu-freedos
(for non-debian-users: Get dosemu and freedos somewhere and make it work somehow).

With dosemu, you can run this executable, but this program unfortunately
needs a floppy drive to write to. So use the loopback device, to create a virtual floppy.
dd if=/dev/zero of=/tmp/floppy.bin bs=1024 count=1440
losetup /dev/loop0 /tmp/floppy.bin
Put this block device (<tt>/dev/loop0</tt>) into the dosemu configuration as the floppy disk device.
Now you can run the extractor executable, which makes <tt>/tmp/floppy.bin</tt> the desired floppy image.
dosemu 1ruj27ud.exe
losetup -d /dev/loop0

=== Adding the custom image ===
Mount your floppy.bin as a loopback device.
mkdir /tmp/mnt
mount -o loop,umask=000 /tmp/floppy.bin /tmp/mnt
Create a 16 color 640x480 BMP (4 Bit/pixel) (for example with Gimp) and save it to /tmp/mnt/logo.bmp.
You could use this tux image ([http://www.thinkwiki.org/files/LOGO.BMP logo.bmp], [http://www.thinkwiki.org/files/LOGO.MOD logo.mod]) for example.<br>
Now prepare the image with <tt>prepare.exe</tt> using wine: (This does not work with dosemu!)
wine prepare.exe logo.scr
Now there should be a new <tt>logo.mod</tt> and your <tt>logo.bmp</tt>. If so, you are set, don't forget to unmount your loopback device:
umount /tmp/mnt

=== Fake a floppy ===
Now you need to put the image on a floppy and boot from it. Since recent Thinkpads don't have a
floppy drive, we can use a CD-R (or a CD-RW, actually, for the cheap ones, like me) and burn it with the following command:
mkisofs -b floppy.bin floppy.bin | cdrecord dev=<device> -
(<tt><device></tt> being your cd writer device)

=== The exciting part ===
After this worked, reboot your Thinkpad from the cdrom by pressing F12 while booting
and wait for the IBM tool to start.
Be sure to have your Thinkpad on AC power and say ''Yes'' to the questions the BIOS Upgrade Tool asks.
It will then flash the BIOS, which will take about a minute.

Suddenly the laptop turns itself off with two beeps.
When booting, you'll have your bootsplash picture.

Unfortunately, you won't see it really long, but it's better
than the standard one, so it was worth the action.

Have fun!

[[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]]

Ethernet Controllers

2005-05-05T10:31:11Z

217.93.14.204:

== Internal Ethernet controller ==

A variety of [[Ethernet]] controllers is integrated into almost all models starting with the introduction of the A, T and X series.

The Ethernet controller is located on either a MiniPCI card, Communications Daughter Card (CDC), or integrated on the systemboard.

=== 3COM 10/100 ===
MiniPCI cards featuring this chip:
*[[3Com 10/100 Ethernet Mini-PCI Adapter with 56K Modem]]

=== Intel 10/100 ===
Chipset: Various Intel Mobile Ethernet chips<br>
Driver: e100

The 'e100' driver is the suggested driver, but 'eepro100' should also work.<br>

CDC and MiniPCI cards featuring this chip:
*[[Ethernet Daughter Card (EDC)]]
*[[Intel 10/100 Ethernet Mini-PCI Adapter with 56K Modem]]
*[[Intel Pro/100 SP Mobile Combo Adapter]]
*[[Mini-PCI Ethernet card]]
*[[Xircom 10/100 EtherJet Mini PCI Adapter with 56K Modem]]

In addition, this chip is integrated into select systemboards of the following machines:
* R50, R50p
* T30
* T40, T41p
* X30, X31

=== Intel 10/100/1000 ===
Driver: e1000

This chip is integrated into select systemboards of the following machines:
* R50, R50p
* T40, T40p, T41, T41p, T42, T42p
* X31, X32
* X40

Note: This chip support Auto-MDX, meaning you will never need a crossover ethernet cable.

=== Broadcom 10/100 ===
Chipset: Broadcom BCM5901<br>
Driver: tg3 or bcm5700

This chip is integrated into select systemboards of the following machines:
* G40, G41
* R40e

=== Broadcom 10/100/1000 ===
Chipset: Broadcom BCM5751M<br>
Driver: tg3 or bcm5700

This chip is integrated into select systemboards of the following machines:
* R52
* G41
* T43, T43p
* X41

[[Category:Drivers]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[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:TransNote]]

Embedded Security Subsystem

2005-05-05T10:30:51Z

217.93.14.204:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:ESS.jpg|IBM Embedded Security Subsystem]]
|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;">
=== The Embedded Security Subsystem ===
The Embedded Security Subsystem is nothing but a chip installed on the Thinkpads mainboard that can take care of certain security related tasks conforming to the TCPA standard. It was first introduced among the T23 models and is now under the name Embedded Security Subsystem 2.0 an integral part of most of the modern Thinkpads. The functions of the chip are bound to three main groups:
* public key functions
* trusted boot functions
* initialization and management functions

The purpose of the whole thing is to keep the users sensitive data out of range from software based attacks (like viruses, internet attacks etc.). One way the chip offers to achieve this is by providing storage for keys along with the neccessary functions to handle them within itself, so that a i.e. a private key never has to leave the chip (can't be seen by any piece of software). Besides this there are more complex topics covered by the functionality of the chip. If you want to find out more about it you can find good documents on the [http://www.research.ibm.com/gsal/tcpa/ IBM Research TCPA resources page].
</div>
|}

==Linux Support==
Two linux drivers are available, a [[tpm|classical one]] and a [[tpmdd|newer one]].
Coverage of functionality of the first is unknown so far, the second is part of a bigger project aiming to provide a usable security framework.

David Stafford (one of the developers of the tpm code at IBM) on March 10, 2005 sent me the most recent version of the tpm-kml code. With his permission, I quote his email:

"I am attaching our latest driver and library.
This version is in the process of kernel mailing list review, and
will hopefully be accepted into the official kernel. It works
much better across various 2.6 kernels. Note that this builds
three modules tpm, tpm_atmel, and tpm_nsc. You modprobe the
tpm_atmel (for all current shipping atmel based systems), or
tpm_nsc (for the coming national based systems).

Also note that there is a conflict with the snd-intel8x0
kernel module (they each try to grab the LPC bus). You can
either: load the tpm modules first (such as in initrd or
rc.sysinit, before sound), or recompile the snd-intel8x0, turning
off the MIDI and JOYSTICK support. The latest 2.6.11 version
of snd-intel8x0 also reportedly fixes things."

Compiling this library was easy. Compiling the driver on my 2.6.8-686 (debian testing) laptop failed. But the library works with the driver I compiled from the tpm-2.0 package IBM made available on its pages (see the links below).

Gijs

==Related Links==
*[http://www.pc.ibm.com/us/think/thinkvantagetech/security.html IBMs ThinkVantage<sup>TM</sup> Technologies Embedded Security Subsystem page]
*[http://www.pc.ibm.com/presentations/us/thinkvantage/56/index.html?shortcut=ess& IBMs ThinkVantage<sup>TM</sup> Technologies Flash presentation - Embedded Security Subsystem]
*[http://www.research.ibm.com/gsal/tcpa/ IBM Research TCPA resources page]

[[Category:Glossary]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]]
[[Category:X41]]

Active Protection System

2005-05-05T10:30:29Z

217.93.14.204:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:APS.jpg|IBM Active Protection System]]
|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;">
=== The Active Protection System ===
With the new series of Thinkpads IBM introduced the Active Protection System (APS) in 2003. The APS is a protection system for the Thinkpad's internal harddrive. A sensor inside the Thinkpad recognizes when the notebook is accelerated. A software applet then is triggered to park the harddisk. This way the risk of data loss in case of when the notebook is dropped is significantly reduced since the read/write head of the harddrive is parked and hence can't crash onto the platter when the notebook drops onto the floor.

The whole concept of the technology seems very advanced. For the first part, the hardware sensor is capable of not only recognizing acceleration of the notebook, but also (to a certain degree) of its whole orientation in space, relative to gravity's axis. Furthermore, having the actual control put into software, its functionality is extendable and it gives chance to implement features like the "ignore minor shocks" feature which is present in the Windows based control applet. (This feature prevents the harddrive from parking in case of minor regular shocks such as occur when in a train or car.)
</div>
|}

==Linux Support==
Linux support is so far not available.

Note that this feature definitely depends on software and there is no hardware or BIOS only way of making it work. A statement from IBM clearifies this:
"The APS system will require APS software to be installed on the
computer before it activates the harddrive parking . This means it will
not work on systems preloaded with Linux."

However, IBM made general (unofficial) statements that they are willing to release the specifications of the hardware sensor and its API to the linux community or some developers, but they in fact, never did. Also some linux developers actively tried to contact with IBM about the issue but were unable to make progress.

{| Border="1" Cellspacing="0" Cellpadding="2"
|+The following table is supposed to give us a chance to gather information about the efforts made and how they ended up.
|-
! Date !! User !! effort made !! result
|-
| March 2004 || [[User:Wyrfel|Wyrfel]] || asked IBM representatives at CeBIT 2004 about state of linux support || got promise that specifications will be released, but nothing actually happened
|}

Hi, is it worth to contact ibm in some sort of conserted effort
to get this going?

==Related Links==
*[http://www.pc.ibm.com/presentations/us/thinkvantage/56/index.html?shortcut=aps& IBMs ThinkVantage<sup>TM</sup> Technologies Flash presentation - Active Protection System]

* Quoted from NewScientist.com: The latest Apple PowerBook laptops can be controlled with a gentle shake. Programmer Amit Singh has written code that lets him use the sensor to control software on the computer. The code is published at [http://www.kernelthread.com/software/ams/ www.kernelthread.com/software/ams/].

[[Category:Glossary]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X40]] [[Category:X41]]

Active Protection System

2005-05-05T10:29:28Z

217.93.14.204:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:APS.jpg|IBM Active Protection System]]
|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;">
=== The Active Protection System ===
With the new series of Thinkpads IBM introduced the Active Protection System (APS) in 2003. The APS is a protection system for the Thinkpad's internal harddrive. A sensor inside the Thinkpad recognizes when the notebook is accelerated. A software applet then is triggered to park the harddisk. This way the risk of data loss in case of when the notebook is dropped is significantly reduced since the read/write head of the harddrive is parked and hence can't crash onto the platter when the notebook drops onto the floor.

The whole concept of the technology seems very advanced. For the first part, the hardware sensor is capable of not only recognizing acceleration of the notebook, but also (to a certain degree) of its whole orientation in space, relative to gravity's axis. Furthermore, having the actual control put into software, its functionality is extendable and it gives chance to implement features like the "ignore minor shocks" feature which is present in the Windows based control applet. (This feature prevents the harddrive from parking in case of minor regular shocks such as occur when in a train or car.)
</div>
|}

==Linux Support==
Linux support is so far not available.

Note that this feature definitely depends on software and there is no hardware or BIOS only way of making it work. A statement from IBM clearifies this:
"The APS system will require APS software to be installed on the
computer before it activates the harddrive parking . This means it will
not work on systems preloaded with Linux."

However, IBM made general (unofficial) statements that they are willing to release the specifications of the hardware sensor and its API to the linux community or some developers, but they in fact, never did. Also some linux developers actively tried to contact with IBM about the issue but were unable to make progress.

{| Border="1" Cellspacing="0" Cellpadding="2"
|+The following table is supposed to give us a chance to gather information about the efforts made and how they ended up.
|-
! Date !! User !! effort made !! result
|-
| March 2004 || [[User:Wyrfel|Wyrfel]] || asked IBM representatives at CeBIT 2004 about state of linux support || got promise that specifications will be released, but nothing actually happened
|}

Hi, is it worth to contact ibm in some sort of conserted effort
to get this going?

==Related Links==
*[http://www.pc.ibm.com/presentations/us/thinkvantage/56/index.html?shortcut=aps& IBMs ThinkVantage<sup>TM</sup> Technologies Flash presentation - Active Protection System]

* Quoted from NewScientist.com: The latest Apple PowerBook laptops can be controlled with a gentle shake. Programmer Amit Singh has written code that lets him use the sensor to control software on the computer. The code is published at [http://www.kernelthread.com/software/ams/ www.kernelthread.com/software/ams/].

[[Category:Glossary]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X40]] [[Category:X41]]