ThinkWiki - User contributions [en]

Installing Debian 3.1 (Sarge) on a ThinkPad T43

2005-10-08T08:58:24Z

Thinc: spelling

__TOC__

This is how I slapped {{Debian}}/Sarge onto my shiny new {{T43}}, which seems quite a nice machine all in all. It's a very new type, being based on the Sonoma platform with PCI Express, SATA and other happy things. Does Intel marketing really call Sonoma a "platform"? Oh well.

==Installation==
===Repartitioning/Resizing the Windows Partition===

This is only necessary if you want to keep your Windows installation for dual booting. I kept mine just so I could update the BIOS more easily in case it becomes necessary.

I was able to boot Knoppix 3.7, '''but only with the 2.4 kernel'''. Then resizing the existing 70-odd GB NTFS partition presented no problems at all, but it was rather slow (no DMA mode) due to the ICH6 IDE/SATA controller not being recognized properly. Use ntfsresize, or if you don't trust your knowledge of this rather powerful and potentially confusing tool, try QtParted. Both are available in Knoppix' K menu. Don't be worried if nothing happens while you resize your partition, it took more than an hour on mine.

To repeat myself: You '''cannot''' boot Knoppix (at least up to 3.7) using the 2.6 kernel. Use 2.4.

===The big switcharoo: /dev/hda becomes /dev/sda===

When initially installing Sarge from the rc3 Debian Installer images, the installation disc's 2.4 kernel saw the hard drive as /dev/hda. Since the ICH6 controller doesn't support DMA that way, transfers are extremely slow. Therefore I started by installing a base system with a compiler so I could build my own kernel. After building my kernel with options to support ICH6 ({{kernelconf|CONFIG_SCSI_ATA_PIIX|<*>|Intel PIIX/ICH SATA support|SCSI low level drivers|SCSI device support|Device Drivers|}}), the drive is seen through libata's SCSI emulation as {{path|/dev/sda}}, though.

To change that, you can boot to 2.4, edit {{path|/etc/fstab}} and {{path|/boot/grub/menu.lst}} (or your preferred bootloader's configuration file). Replace all occurences of "hda" with "sda" and reboot to your new 2.6 kernel. If things go wrong and your 2.6 doesn't boot properly, use the Debian installer CD as rescue system and change your fstab and bootloader configuration back to hda, then retry with new kernel options. I will post my working .config as soon as I figure out how to upload non-image files here :)

I suppose the Debian installer might at some time switch to a kernel that supports ICH6 natively, removing the need for this procedure.

(2005-07-02) Debian Stable 3.1 (sarge) still has this problem.

(2005-09-20) To date the problem has NOT been fixed!

==Hardware==
===CPU and frequency scaling===
2.6.11.7's <tt>CONFIG_X86_SPEEDSTEP_CENTRINO</tt> (speedstep-centrino.ko) and <tt>CONFIG_X86_ACPI_CPUFREQ</tt> (acpi-cpufreq.ko) '''both''' seem to work to scale the CPU frequency. Which of the two gets you more battery life and a less noisy CPU fan has yet to be determined. I noticed the CPU fan is rather loud and active a lot. Not something you'd expect for a laptop this expensive. On the other hand, the whole system is pretty brand new and perhaps future kernels will allow for a quieter machine.

===Network===
The network card identifies to lspci as "Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express" and works with the tg3 module, both on kernel 2.4 and 2.6. I didn't find anyhting special here. Haven't tested it on an actual gigabit network, though, so nothing to benchmark with.

===Bluetooth===
Seems to work under 2.6.11.7. Make sure to enable RFCOMM in your kernel, and you will also need support for ibm-acpi. then:

apt-get install bluez-utils
echo "enable" > /proc/acpi/ibm/bluetooth
/etc/init.d/bluez-utils start

And you can try using "hcitool scan" to scan for nearby devices. My Sony Ericsson T630 was found immediately and I could back up its contens using MultiSync.

==Buttons==
{|
|[[ThinkLight]]
|{{key|Fn}}{{key|PgUp}}
|Just worked (can also be toggled through [[ibm-acpi|ibm-acpi's]] {{path|/proc/acpi/ibm/light}})
|-
|Display brightness +
|{{key|Fn}}{{key|Home}}
|Just worked (no software necessary)
|-
|Display brightness -
|{{key|Fn}}{{key|End}}
|Just worked (no software necessary)
|-
|Backlight off
|{{key|Fn}}{{key|F3}}
|Supported with [[ibm-acpi]], [[acpid]] and [[radeontool]]
|}

===Backlight off===
I turned this into something more like a backlight toggle by using this script as {{path|/etc/acpid/backlight.sh}} for acpid:

<pre>
<nowiki>
#!/bin/bash

RADEONTOOL='/usr/local/sbin/radeontool'

status=`$RADEONTOOL light`;

if [[ "$status" = "The radeon backlight looks on" ]] ; then
$RADEONTOOL light off
elif [[ "$status" = "The radeon backlight looks off" ]] ; then
$RADEONTOOL light on
fi
</nowiki>
</pre>

You must first grab radeontool and copy it to {{path|/usr/local/sbin}} for this to work, of course. The script itself was stolen from someone else (whose name I forgot -- sorry!) and modified to work with the current version of radeontool.

My {{path|/etc/acpid/events/backlight}} looks like this:

event=ibm/hotkey.*1003
action=/etc/acpi/backlight.sh

==Various Information==
===lspci Output===

To have all the hardware show up with its proper name, I had to get a new pci.ids file from the [http://pciids.sourceforge.net/ Linux PCI ID Repostiory] and copy it to {{path|/usr/share/misc/pci.ids}}. I believe newer distributions and kernels won't need that file anymore.

0000:00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
0000:00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03)
0000:00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
0000:00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 03)
0000:00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
0000:00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
0000:00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
0000:00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
0000:00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
0000:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
0000:00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)\
AC'97 Audio Controller (rev 03)
0000:00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
0000:00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
0000:00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
0000:00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Radeon Mobility M300]
0000:02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express (rev 11)
0000:04:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 8d)
0000:04:02.0 Network controller: Intel Corporation: Unknown device 4224 (rev 05)

Things are up and running, WLAN and all, and I will update this article with the details once I have the time :)

'''... To be continued ...'''

==Complaints==
It appears to me that even when the CPU is clocked down to 800 MHz, the CPU fan is very noisy and blows practically non-stop at the same speed. Does anyone else think this simply shouldn't be the case with a laptop this pricy? I've seen some that cost half as much, have a comparable processor and aren't as noisy. Is this simply a symptom of e.g. the graphics card's frequency scaling not being supported yet? I'd love some discussion about this.

I use a script (started from a an rc.d script as a daemon) to check the temperatures and turn the fan on or off depending on the temperature:

<pre>
#!/bin/sh

MAXTEMP=55

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>

----

Seems like a solution, thanks :)
''Author of the script''
It's not really a solution, merely a temporary fix. The ideal solution would be to find out how to control the fan speed. At low speed the fan is not noisy ==> work for ibm_acpi!

I cannot see {{path|/proc/acpi/ibm/fan}} yet, perhaps it's because {{path|/etc/init.d/acpid}} tries to load any and all available acpi modules when the system boots, so a module is already filling places that ibm_acpi wants to take. I'll reconfigure it so it leaves out "fan" and "thermal" and see if ibm_acpi can then grab those two.

It appears that wasn't the problem, but that the ibm-acpi that ships with 2.6.11.7 doesn't have the experimental fan adjustment support. I downloaded the latest available version and will try with that.

It works when using the downloaded ibm-acpi and when that's loaded with the "experimental=1" option.

All of this info is available on a separate page in this wiki, I'll link to it and add some text in the "CPU" section about fan noise.

IBM 11a/b/g Wireless LAN Mini PCI Adapter II

2005-08-23T22:01:34Z

Thinc: /* Features */ added AR521x

__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;">
=== IBM 11a/b/g Wireless LAN Mini PCI Adapter II ===
This is a Mini-PCI WiFi Adapter that is installed in a Mini-PCI slot.
=== Features ===
* Chipset: Atheros AR5004X or AR521x
* IEEE Standards: 802.11a, 802.11b, 802.11g
* PCI ID: 168c:1014
</div>
|style="vertical-align:top" |
[[image:mini-pci-wifi-card.gif|Mini-PCI WiFi Adapter]]
|}

=== IBM Partnumbers ===
'''Ambit parts'''<br>
IBM Option PN (WW): 73P4301<br>
IBM Option PN (Philippines, Singapore, Indonesia, Taiwan, China): 73P4302<br>
IBM Option PN (Japan): 73P4303<br>
IBM FRU PN (WW): 93P4262<br>
IBM FRU PN (Philippines, Singapore, Indonesia, Taiwan, China): 93P4264<br>
IBM FRU PN (Japan): 93P4266<br>

'''Bartlett parts'''<br>
IBM FRU PN (US): 27K9944<br>
IBM FRU PN (EU): 27K9946<br>
IBM FRU PN (Japan): 27K9948<br>
IBM FRU PN (Taiwan): 27K9999<br>

=== Also known (in IBM literature) as.... ===
* 802.11a/b/g Ambit wireless Card
* 802.11a/b/g Bartlett Wireless Card

=== Linux WiFi driver ===
This is an Atheros chip and works with the [[Madwifi]] driver "out of the box".

Make sure that your kernel supports "CONFIG_SECURITY_CAPABILITIES", or you might get some message from the Atheros hal that it does not support all features.

=== ThinkPad's this card may be found in ===
* {{R51}}, {{R52}}
* {{T42p}},{{T43}}, {{T43p}}
* {{X32}}
* {{X40}}, {{X41}}

=== Related Links ===
*Specifications: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57210 MIGR-57210]
*Users Guide: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57217 MIGR-57217]
*Service Parts: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-57214 MIGR-57214]

[[Category:Components]]

Category:T43

2005-08-18T07:04:34Z

Thinc: added link to mentioned forums.thinkpads.com thread

{| 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;">
=== ThinkPad T43 ===
This pages gives an overview of all ThinkPad T43 related topics.
==== Features ====
* [[Intel Pentium M (Dothan)]] 1.6, 1.73, 1.86 or 2.0GHz CPU
* One of the following graphics adapters:
** [[Intel Graphics Media Accelerator 900]]
** [[ATI Mobility Radeon X300]] with 64MB
* One of the following displays:
** 14.1" TFT display with 1024x768 resolution
** 14.1" TFT display with 1400x1050 resolution
** 15.0" TFT display with 1024x768 resolution
** 15.0" TFT display with 1400x1050 resolution
* 256 or 512MB memory standard
* 40, 60 or 80GB HDD{{footnote|1}}{{footnote|2}}
* [[AD1981B|AD1981B AC'97 Audio controller]]
* [[Ethernet Controllers|Broadcom 10/100/1000 Ethernet]]
* [[UltraBay|UltraBay Slim]] with one of the following:
** DVD-ROM
** DVD-ROM/CD-RW Combo
** DVDÂ±RW
* CDC slot with one of the following:
** [[IBM Integrated 56K Modem (MDC-2)]]
** [[IBM Integrated Bluetooth IV with 56K Modem (BMDC-3)]]
* MiniPCI slot with one of the following:
** none (empty)
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
** [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]]
** [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]]
* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]
* [[Active Protection System|IBM Active Protection System]]
* [[Integrated Fingerprint Reader]] on select systems
* [[UltraNav]] (TrackPoint / Touchpad combo)
</div>
|style="vertical-align:top" |
[[Image:ThinkpadT43P.JPG|ThinkPad T43]]
|}
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/27r0949.pdf ThinkPad T43 - Hardware Maintenance Manual (for 1XXX series T43s) (February 2005)] (4,461,520 Bytes)
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/27r0700.pdf ThinkPad T43/p - Hardware Maintenance Manual (for 2XXX series T43s) (January 2005)] (4,534,423 Bytes)

{{footnotes|
#Those who have taken apart their T43s or replaced the hard drives noted that the HD is not physically SATA, even though it is supported under Linux as SATA. [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-April/025535.html ref] The T43 hardware maintenance manual describes the hard drive as IDE and not SATA.
#Word to the wise: the T43 uses a SATA->PATA converter and PATA drives. Unfortunately, the drive's firmware is modified by IBM for performance and stability reasons. In general, you can install a non-IBM branded HD as the primary drive, but it will give a warning at boot time. See [http://forum.thinkpads.com/viewtopic.php?t<nowiki>=</nowiki>11059 Firmware Problems with Seagate 100g Drive on T43]

[[Category:Models]]

Category:T43

2005-08-18T06:30:28Z

Thinc: added link to mentioned forums.thinkpads.com thread

{| 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;">
=== ThinkPad T43 ===
This pages gives an overview of all ThinkPad T43 related topics.
==== Features ====
* [[Intel Pentium M (Dothan)]] 1.6, 1.73, 1.86 or 2.0GHz CPU
* One of the following graphics adapters:
** [[Intel Graphics Media Accelerator 900]]
** [[ATI Mobility Radeon X300]] with 64MB
* One of the following displays:
** 14.1" TFT display with 1024x768 resolution
** 14.1" TFT display with 1400x1050 resolution
** 15.0" TFT display with 1024x768 resolution
** 15.0" TFT display with 1400x1050 resolution
* 256 or 512MB memory standard
* 40, 60 or 80GB HDD{{footnote|1}}{{footnote|2}}
* [[AD1981B|AD1981B AC'97 Audio controller]]
* [[Ethernet Controllers|Broadcom 10/100/1000 Ethernet]]
* [[UltraBay|UltraBay Slim]] with one of the following:
** DVD-ROM
** DVD-ROM/CD-RW Combo
** DVDÂ±RW
* CDC slot with one of the following:
** [[IBM Integrated 56K Modem (MDC-2)]]
** [[IBM Integrated Bluetooth IV with 56K Modem (BMDC-3)]]
* MiniPCI slot with one of the following:
** none (empty)
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
** [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]]
** [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]]
* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]
* [[Active Protection System|IBM Active Protection System]]
* [[Integrated Fingerprint Reader]] on select systems
* [[UltraNav]] (TrackPoint / Touchpad combo)
</div>
|style="vertical-align:top" |
[[Image:ThinkpadT43P.JPG|ThinkPad T43]]
|}
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/27r0949.pdf ThinkPad T43 - Hardware Maintenance Manual (for 1XXX series T43s) (February 2005)] (4,461,520 Bytes)
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/27r0700.pdf ThinkPad T43/p - Hardware Maintenance Manual (for 2XXX series T43s) (January 2005)] (4,534,423 Bytes)

{{footnotes|
#Those who have taken apart their T43s or replaced the hard drives noted that the HD is not physically SATA, even though it is supported under Linux as SATA. [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-April/025535.html ref] The T43 hardware maintenance manual describes the hard drive as IDE and not SATA.
#Word to the wise: the T43 uses a SATA->PATA converter and PATA drives. Unfortunately, the drive's firmware is modified by IBM for performance and stability reasons. In general, you can install a non-IBM branded HD as the primary drive, but it will give a warning at boot time. See [http://forum.thinkpads.com/viewtopic.php?t=11059 Firmware Problems with Seagate 100g Drive on T43] at http://forums.thinkpads.com
}}

[[Category:Models]]

Category:T43

2005-08-16T07:07:47Z

Thinc: /* Features */ clarified information about nonibm hard drives

{| 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;">
=== ThinkPad T43 ===
This pages gives an overview of all ThinkPad T43 related topics.
==== Features ====
* [[Intel Pentium M (Dothan)]] 1.6, 1.73, 1.86 or 2.0GHz CPU
* One of the following graphics adapters:
** [[Intel Graphics Media Accelerator 900]]
** [[ATI Mobility Radeon X300]] with 64MB
* One of the following displays:
** 14.1" TFT display with 1024x768 resolution
** 14.1" TFT display with 1400x1050 resolution
** 15.0" TFT display with 1024x768 resolution
** 15.0" TFT display with 1400x1050 resolution
* 256 or 512MB memory standard
* 40, 60 or 80GB HDD{{footnote|1}}
* [[AD1981B|AD1981B AC'97 Audio controller]]
* [[Ethernet Controllers|Broadcom 10/100/1000 Ethernet]]
* [[UltraBay|UltraBay Slim]] with one of the following:
** DVD-ROM
** DVD-ROM/CD-RW Combo
** DVDÂ±RW
* CDC slot with one of the following:
** [[IBM Integrated 56K Modem (MDC-2)]]
** [[IBM Integrated Bluetooth IV with 56K Modem (BMDC-3)]]
* MiniPCI slot with one of the following:
** none (empty)
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
** [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]]
** [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]]
* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]
* IBM Active Protection System
* [[Integrated Fingerprint Reader]] on select systems
* [[UltraNav]] (TrackPoint / Touchpad combo)
</div>
|style="vertical-align:top" |
[[Image:ThinkpadT43P.JPG|ThinkPad T43]]
|}
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/27r0949.pdf ThinkPad T43 - Hardware Maintenance Manual (for 1XXX series T43s) (February 2005)] (4,461,520 Bytes)
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/27r0700.pdf ThinkPad T43/p - Hardware Maintenance Manual (for 2XXX series T43s) (January 2005)] (4,534,423 Bytes)

{{footnotes|
#Those who have taken apart their T43s or replaced the hard drives noted that the HD is not physically SATA, even though it is supported under Linux as SATA. [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-April/025535.html ref] The T43 hardware maintenance manual describes the hard drive as IDE and not SATA.
#Word to the wise: the T43 uses a SATA->PATA converter and PATA drives. Unfortunately, the drive's firmware is modified by IBM for performance and stability reasons. In general, you can install a non-IBM branded HD as the primary drive, but it will give a warning at boot time. See "Firmware Problems with Seagate 100g Drive on T43" at forums.thinkpad.com
}}

[[Category:Models]]

How to make use of Dynamic Frequency Scaling

2005-07-23T20:21:15Z

Thinc: /* Using Frequency Scaling Governors */ gouvernour->governor

==General==
Linux supports Dynamic Frequency Scaling for ThinkPads with mobile Pentium III, Pentium 4 and Pentium M processors.

===Configuring the Kernel===
====2.4 Kernels====
There were various frequency scaling implementations in the 2.4 series of kernels. They all were preliminary and a standard was rised with the introduction of the sysfs filesystem in 2.6 kernels. It is recommended to use a 2.6 kernel, if possible.

====2.6 Kernels====
You need to enable the cpu frequency scaling for your kernel (usually your distros kernel will have this enabled):
CONFIG_CPU_FREQ=y

You need to enable governors, if not already done in your distros default kernel:
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y

Since 2.6.10 there is the ondemand governor that does cpu frequency scaling in kernel so you dont need userspace programs like powernowd etc.
It can be enabled with:
CONFIG_CPU_FREQ_GOV_ONDEMAND=y

==Using the Sys Interface==

The files in {{path|/sys/devices/system/cpu/cpu0/cpufreq/}} provide information and a means of controlling the frequency scaling subsystem.
Seed values are given in Khz. You need to be root to access the /sys filesystem.

Your max speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}
:{{cmdresult|700000}}
Your min speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}
:{{cmdresult|500000}}
You can write to {{path|/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}} to change the current speed.
:{{cmdroot|echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 697.252}}
:{{cmdroot|echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 976.152}}

==Using Frequency Scaling Governors==
You can compile the scaling gouvernours into your kernel or compile it as module. You'll find the gouvernors with 'make menuconfig' here:
: <code>Power managemant options (ACPI, APM) ---></code>
:: <code>CPU Frequency scaling ---></code>

After booting the new kernel you can get a list of available governors with (as root):
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors}}
:{{cmdresult|conservative ondemand powersave userspace performance}}

A Short Overview over the available governors:
:;ondemand
::This driver is a dynamic cpufreq policy governor. It changes frequency based on the processor load.
:;conservative
::New since 2.6.12. Similar to ''ondemand''. Optimized for battery powered environments and AMD64.
:;powersave
::Like the name says, your battery would choose this one ;). It sets the Frequency always to the lowest available.
:;userspace
::You have to choose this one, if a [[#Using Frequency Scaling Daemons|frequency scaling daemon]] should manage your CPU frequency or you want to do it manually.
:;performance
::This governor sets your Frequency always to the highest available.

Now we set our governor:
What is our current governor?
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|userspace}}
Set new governor and watch if it has changed
:{{cmdroot|echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|conservative}}

Congrats! Your governor is active.

You may set the governor in your rc.local, to make it used on every boot.

Debian has no rc.local, so read [http://www.debian.org/doc/FAQ/ch-customizing.en.html#s-custombootscripts this] and [http://www.debian.org/doc/FAQ/ch-customizing.en.html#s-booting this]

==Using Frequency Scaling Daemons==
{{NOTE|It is recommended to use the ondemand frequency scaling governor, available in kernels from 2.6.10. See [[#Using Frequency Scaling Governors|above]]. If you do this you do not need a frequency scaling daemon}}

Don't forget to enable the userspace governor to have a userspace daemon do the frequency scaling. If it is built as module, load it as <tt>cpufreq-userspace</tt>.

There are plenty of userspace frequency scaling daemons available:

*[[How to configure cpufreqd | cpufreqd]]
*[[How to configure cpudynd | cpudynd]]
*[[How to configure speedfreqd | speedfreqd]]
*[[How to configure powersaved | powersaved]]
*[[How to configure powernowd | powernowd]]
*[[How to use cpufrequtils | cpufrequtils]]

==Troubleshooting==
*If you have a Coppermine-piix-smi based Thinkpads like from the A2x, X2x and T2x series you need to enable the <tt>speedstep-ich</tt> driver in the kernel and load it if it's built as module. You might want to look at [[How to get SpeedStep working on Coppermine-piix4-smi based Thinkpads | this page]].

*If you have a p4-class celeron based Thinkpad like the R40e you might want to look at [[How to get SpeedStep working on P4-class-Celeron based Thinkpads | this page]]

[[Category:570E]] [[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category: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:X41 Tablet]]

How to make use of Dynamic Frequency Scaling

2005-07-23T20:20:27Z

Thinc: /* Using Frequency Scaling Governors */ powersafe->powersave

==General==
Linux supports Dynamic Frequency Scaling for ThinkPads with mobile Pentium III, Pentium 4 and Pentium M processors.

===Configuring the Kernel===
====2.4 Kernels====
There were various frequency scaling implementations in the 2.4 series of kernels. They all were preliminary and a standard was rised with the introduction of the sysfs filesystem in 2.6 kernels. It is recommended to use a 2.6 kernel, if possible.

====2.6 Kernels====
You need to enable the cpu frequency scaling for your kernel (usually your distros kernel will have this enabled):
CONFIG_CPU_FREQ=y

You need to enable governors, if not already done in your distros default kernel:
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y

Since 2.6.10 there is the ondemand governor that does cpu frequency scaling in kernel so you dont need userspace programs like powernowd etc.
It can be enabled with:
CONFIG_CPU_FREQ_GOV_ONDEMAND=y

==Using the Sys Interface==

The files in {{path|/sys/devices/system/cpu/cpu0/cpufreq/}} provide information and a means of controlling the frequency scaling subsystem.
Seed values are given in Khz. You need to be root to access the /sys filesystem.

Your max speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}
:{{cmdresult|700000}}
Your min speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}
:{{cmdresult|500000}}
You can write to {{path|/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}} to change the current speed.
:{{cmdroot|echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 697.252}}
:{{cmdroot|echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 976.152}}

==Using Frequency Scaling Governors==
You can compile the scaling gouvernours into your kernel or compile it as module. You'll find the gouvernors with 'make menuconfig' here:
: <code>Power managemant options (ACPI, APM) ---></code>
:: <code>CPU Frequency scaling ---></code>

After booting the new kernel you can get a list of available governors with (as root):
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors}}
:{{cmdresult|conservative ondemand powersave userspace performance}}

A Short Overview over the available governors:
:;ondemand
::This driver is a dynamic cpufreq policy governor. It changes frequency based on the processor load.
:;conservative
::New since 2.6.12. Similar to ''ondemand''. Optimized for battery powered environments and AMD64.
:;powersave
::Like the name says, your battery would choose this one ;). It sets the Frequency always to the lowest available.
:;userspace
::You have to choose this one, if a [[#Using Frequency Scaling Daemons|frequency scaling daemon]] should manage your CPU frequency or you want to do it manually.
:;performance
::This gouvernour sets your Frequency always to the highest available.

Now we set our governor:
What is our current governor?
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|userspace}}
Set new governor and watch if it has changed
:{{cmdroot|echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|conservative}}

Congrats! Your governor is active.

You may set the governor in your rc.local, to make it used on every boot.

Debian has no rc.local, so read [http://www.debian.org/doc/FAQ/ch-customizing.en.html#s-custombootscripts this] and [http://www.debian.org/doc/FAQ/ch-customizing.en.html#s-booting this]

==Using Frequency Scaling Daemons==
{{NOTE|It is recommended to use the ondemand frequency scaling governor, available in kernels from 2.6.10. See [[#Using Frequency Scaling Governors|above]]. If you do this you do not need a frequency scaling daemon}}

Don't forget to enable the userspace governor to have a userspace daemon do the frequency scaling. If it is built as module, load it as <tt>cpufreq-userspace</tt>.

There are plenty of userspace frequency scaling daemons available:

*[[How to configure cpufreqd | cpufreqd]]
*[[How to configure cpudynd | cpudynd]]
*[[How to configure speedfreqd | speedfreqd]]
*[[How to configure powersaved | powersaved]]
*[[How to configure powernowd | powernowd]]
*[[How to use cpufrequtils | cpufrequtils]]

==Troubleshooting==
*If you have a Coppermine-piix-smi based Thinkpads like from the A2x, X2x and T2x series you need to enable the <tt>speedstep-ich</tt> driver in the kernel and load it if it's built as module. You might want to look at [[How to get SpeedStep working on Coppermine-piix4-smi based Thinkpads | this page]].

*If you have a p4-class celeron based Thinkpad like the R40e you might want to look at [[How to get SpeedStep working on P4-class-Celeron based Thinkpads | this page]]

[[Category:570E]] [[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category: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:X41 Tablet]]

How to make use of Dynamic Frequency Scaling

2005-07-23T19:46:10Z

Thinc: /* Using Frequency Scaling Governors */ debian has no rc.local, links to debian docs for how to enable something similar

==General==
Linux supports Dynamic Frequency Scaling for ThinkPads with mobile Pentium III, Pentium 4 and Pentium M processors.

===Configuring the Kernel===
====2.4 Kernels====
There were various frequency scaling implementations in the 2.4 series of kernels. They all were preliminary and a standard was rised with the introduction of the sysfs filesystem in 2.6 kernels. It is recommended to use a 2.6 kernel, if possible.

====2.6 Kernels====
You need to enable the cpu frequency scaling for your kernel (usually your distros kernel will have this enabled):
CONFIG_CPU_FREQ=y

You need to enable governors, if not already done in your distros default kernel:
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y

Since 2.6.10 there is the ondemand governor that does cpu frequency scaling in kernel so you dont need userspace programs like powernowd etc.
It can be enabled with:
CONFIG_CPU_FREQ_GOV_ONDEMAND=y

==Using the Sys Interface==

The files in {{path|/sys/devices/system/cpu/cpu0/cpufreq/}} provide information and a means of controlling the frequency scaling subsystem.
Seed values are given in Khz. You need to be root to access the /sys filesystem.

Your max speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}
:{{cmdresult|700000}}
Your min speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}
:{{cmdresult|500000}}
You can write to {{path|/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}} to change the current speed.
:{{cmdroot|echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 697.252}}
:{{cmdroot|echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 976.152}}

==Using Frequency Scaling Governors==
You can compile the scaling gouvernours into your kernel or compile it as module. You'll find the gouvernors with 'make menuconfig' here:
: <code>Power managemant options (ACPI, APM) ---></code>
:: <code>CPU Frequency scaling ---></code>

After booting the new kernel you can get a list of available governors with (as root):
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors}}
:{{cmdresult|conservative ondemand powersave userspace performance}}

A Short Overview over the available governors:
:;ondemand
::This driver is a dynamic cpufreq policy governor. It changes frequency based on the processor load.
:;conservative
::New since 2.6.12. Similar to ''ondemand''. Optimized for battery powered environments and AMD64.
:;powersafe
::Like the name says, your battery would choose this one ;). It sets the Frequency always to the lowest available.
:;userspace
::You have to choose this one, if a [[#Using Frequency Scaling Daemons|frequency scaling daemon]] should manage your CPU frequency or you want to do it manually.
:;performance
::This gouvernour sets your Frequency always to the highest available.

Now we set our governor:
What is our current governor?
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|userspace}}
Set new governor and watch if it has changed
:{{cmdroot|echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|conservative}}

Congrats! Your governor is active.

You may set the governor in your rc.local, to make it used on every boot.

Debian has no rc.local, so read [http://www.debian.org/doc/FAQ/ch-customizing.en.html#s-custombootscripts this] and [http://www.debian.org/doc/FAQ/ch-customizing.en.html#s-booting this]

==Using Frequency Scaling Daemons==
{{NOTE|It is recommended to use the ondemand frequency scaling governor, available in kernels from 2.6.10. See [[#Using Frequency Scaling Governors|above]]. If you do this you do not need a frequency scaling daemon}}

Don't forget to enable the userspace governor to have a userspace daemon do the frequency scaling. If it is built as module, load it as <tt>cpufreq-userspace</tt>.

There are plenty of userspace frequency scaling daemons available:

*[[How to configure cpufreqd | cpufreqd]]
*[[How to configure cpudynd | cpudynd]]
*[[How to configure speedfreqd | speedfreqd]]
*[[How to configure powersaved | powersaved]]
*[[How to configure powernowd | powernowd]]
*[[How to use cpufrequtils | cpufrequtils]]

==Troubleshooting==
*If you have a Coppermine-piix-smi based Thinkpads like from the A2x, X2x and T2x series you need to enable the <tt>speedstep-ich</tt> driver in the kernel and load it if it's built as module. You might want to look at [[How to get SpeedStep working on Coppermine-piix4-smi based Thinkpads | this page]].

*If you have a p4-class celeron based Thinkpad like the R40e you might want to look at [[How to get SpeedStep working on P4-class-Celeron based Thinkpads | this page]]

[[Category:570E]] [[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category: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:X41 Tablet]]

How to make use of Dynamic Frequency Scaling

2005-07-23T19:39:41Z

Thinc: /* Using Frequency Scaling Daemons */ note about not needing daemon when using ondemand

==General==
Linux supports Dynamic Frequency Scaling for ThinkPads with mobile Pentium III, Pentium 4 and Pentium M processors.

===Configuring the Kernel===
====2.4 Kernels====
There were various frequency scaling implementations in the 2.4 series of kernels. They all were preliminary and a standard was rised with the introduction of the sysfs filesystem in 2.6 kernels. It is recommended to use a 2.6 kernel, if possible.

====2.6 Kernels====
You need to enable the cpu frequency scaling for your kernel (usually your distros kernel will have this enabled):
CONFIG_CPU_FREQ=y

You need to enable governors, if not already done in your distros default kernel:
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y

Since 2.6.10 there is the ondemand governor that does cpu frequency scaling in kernel so you dont need userspace programs like powernowd etc.
It can be enabled with:
CONFIG_CPU_FREQ_GOV_ONDEMAND=y

==Using the Sys Interface==

The files in {{path|/sys/devices/system/cpu/cpu0/cpufreq/}} provide information and a means of controlling the frequency scaling subsystem.
Seed values are given in Khz. You need to be root to access the /sys filesystem.

Your max speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}
:{{cmdresult|700000}}
Your min speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}
:{{cmdresult|500000}}
You can write to {{path|/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}} to change the current speed.
:{{cmdroot|echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 697.252}}
:{{cmdroot|echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 976.152}}

==Using Frequency Scaling Governors==
You can compile the scaling gouvernours into your kernel or compile it as module. You'll find the gouvernors with 'make menuconfig' here:
: <code>Power managemant options (ACPI, APM) ---></code>
:: <code>CPU Frequency scaling ---></code>

After booting the new kernel you can get a list of available governors with (as root):
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors}}
:{{cmdresult|conservative ondemand powersave userspace performance}}

A Short Overview over the available governors:
:;ondemand
::This driver is a dynamic cpufreq policy governor. It changes frequency based on the processor load.
:;conservative
::New since 2.6.12. Similar to ''ondemand''. Optimized for battery powered environments and AMD64.
:;powersafe
::Like the name says, your battery would choose this one ;). It sets the Frequency always to the lowest available.
:;userspace
::You have to choose this one, if a [[#Using Frequency Scaling Daemons|frequency scaling daemon]] should manage your CPU frequency or you want to do it manually.
:;performance
::This gouvernour sets your Frequency always to the highest available.

Now we set our governor:
What is our current governor?
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|userspace}}
Set new governor and watch if it has changed
:{{cmdroot|echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|conservative}}

Congrats! Your governor is active.

You may set the governor in your rc.local, to make it used on every boot.

==Using Frequency Scaling Daemons==
{{NOTE|It is recommended to use the ondemand frequency scaling governor, available in kernels from 2.6.10. See [[#Using Frequency Scaling Governors|above]]. If you do this you do not need a frequency scaling daemon}}

Don't forget to enable the userspace governor to have a userspace daemon do the frequency scaling. If it is built as module, load it as <tt>cpufreq-userspace</tt>.

There are plenty of userspace frequency scaling daemons available:

*[[How to configure cpufreqd | cpufreqd]]
*[[How to configure cpudynd | cpudynd]]
*[[How to configure speedfreqd | speedfreqd]]
*[[How to configure powersaved | powersaved]]
*[[How to configure powernowd | powernowd]]
*[[How to use cpufrequtils | cpufrequtils]]

==Troubleshooting==
*If you have a Coppermine-piix-smi based Thinkpads like from the A2x, X2x and T2x series you need to enable the <tt>speedstep-ich</tt> driver in the kernel and load it if it's built as module. You might want to look at [[How to get SpeedStep working on Coppermine-piix4-smi based Thinkpads | this page]].

*If you have a p4-class celeron based Thinkpad like the R40e you might want to look at [[How to get SpeedStep working on P4-class-Celeron based Thinkpads | this page]]

[[Category:570E]] [[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category: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:X41 Tablet]]

How to make use of Graphics Chips Power Management features

2005-07-23T19:28:27Z

Thinc: note about how to use DynamicClocks

==Power Saving With A Framebuffer Console==
In order to use the dynamic GPU clock-scaling similar to what X.org has, you need to use the radeonfb kernel module. You'll need to enable the '''CONFIG_FB_RADEON''' in your kernel configuration. If setup correctly you should see something like the following in your kernel log:
radeonfb: Dynamic Clock Power Management enabled

==DynamicClocks in the Radeon Xorg driver==
The xorg X server has support for a power saving feature from ATI called PowerPlay. Xorg calls this feature DynamicClocks. It can be enabled in the server by adding '''Option "DynamicClocks" "on"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}

Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "IBM Thinkpad"
BoardName "ATI Radeon Mobility M9"
'''Option "DynamicClocks" "on"'''
EndSection

With this option enabled, the X11 server should print ({{path|/var/log/Xorg.0.log}}):

(**) RADEON(0): Option "DynamicClocks" "on"
(II) RADEON(0): Dynamic Clock Scaling Enabled

[http://www.ati.com/products/pdf/powerplaywp2.pdf Marketing information from ATI]

==How to use it==

After enabling it, my first question was how do I control it? After reading about it, the answer is: you don't have to, it manages the power consumption for you.\

==x.org on Debian==
Because debian doesn't have X.org yet - [http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 Installing a non-intrusive X.org server on Debian].

'''Update:''' X.org has made it into Debian. See: [http://packages.debian.org/unstable/x11/xserver-xorg]

There are also sarge backports available [http://www.backports.org/ here] or [http://people.debian.org/~nobse/xorg-x11/ here].

deb http://people.debian.org/~nobse/xorg-x11/ sarge main

[[Category:G40]] [[Category:G41]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]]

How to make use of Graphics Chips Power Management features

2005-07-23T18:52:54Z

Thinc: /* x.org on Debian */ note about xorg backport

==Power Saving With A Framebuffer Console==
In order to use the dynamic GPU clock-scaling similar to what X.org has, you need to use the radeonfb kernel module. You'll need to enable the '''CONFIG_FB_RADEON''' in your kernel configuration. If setup correctly you should see something like the following in your kernel log:
radeonfb: Dynamic Clock Power Management enabled

==DynamicClocks in the Radeon Xorg driver==
The xorg X server has support for a power saving feature from ATI called PowerPlay. Xorg calls this feature DynamicClocks. It can be enabled in the server by adding '''Option "DynamicClocks" "on"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}

Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "IBM Thinkpad"
BoardName "ATI Radeon Mobility M9"
'''Option "DynamicClocks" "on"'''
EndSection

With this option enabled, the X11 server should print ({{path|/var/log/Xorg.0.log}}):

(**) RADEON(0): Option "DynamicClocks" "on"
(II) RADEON(0): Dynamic Clock Scaling Enabled

http://www.ati.com/products/pdf/powerplaywp2.pdf

==x.org on Debian==
Because debian doesn't have X.org yet - [http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 Installing a non-intrusive X.org server on Debian].

'''Update:''' X.org has made it into Debian. See: [http://packages.debian.org/unstable/x11/xserver-xorg]

There are also sarge backports available [http://www.backports.org/ here] or [http://people.debian.org/~nobse/xorg-x11/ here].

deb http://people.debian.org/~nobse/xorg-x11/ sarge main

[[Category:G40]] [[Category:G41]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]]

IBM 11a/b/g Wireless LAN Mini PCI Adapter

2005-07-22T06:03:52Z

Thinc: also found in t43

__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;">
=== IBM 11a/b/g Wireless LAN Mini PCI Adapter ===
This is a Mini-PCI WiFi Adapter that is installed in a Mini-PCI slot.

=== Features ===
* Chipset: Atheros AR5001X+
* IEEE Standards: 802.11a, 802.11b, 802.11g
* PCI ID: 168c:1014<br>
</div>
|style="vertical-align:top" |
[[image:mini-pci-wifi-card.gif|Mini-PCI WiFi Adapter]]
|}
=== IBM Partnumbers ===
IBM Option PN (WW): 31P9701<br>
IBM Option PN (Japan): 31P9702<br>
IBM FRU PN (WW): 91P7301, 39T0071<br>
IBM FRU PN (Japan): 91P7303, 93P3599<br>

=== Also known (in IBM literature) as.... ===
* 802.11a\b\g wireless card
* 11A/B/G Wireless LAN Mini PCI Adapter

=== Linux WiFi driver ===
The [[Madwifi]] driver works with this adapter.

=== ThinkPad's this card may be found in ===
* {{G40}}, {{G41}}
* {{R50}}, {{R50p}}, {{R51}}
* {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}
* {{X31}}
* {{X40}}

=== Related Links ===
*Specifications: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-52623 MIGR-52623]
*Users Guide: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-52650 MIGR-52650]
*Service Parts: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-52626 MIGR-52626]

[[Category:Components]]

Installing Debian 3.1 (Sarge) on a ThinkPad T43p

2005-07-20T06:16:47Z

Thinc: add note about pci.ids still being necessary

__TOC__

This is how I installad Debian / Sarge on my new T43p.

==Installation==
I also got a new 100 GB HDS disk, so I swapped out the 60 GB model an plug in my new 100 GB.
When I booted the Sarge Installdisks with the 2.6 Kernel, Linux was not able to recognize the HD.

Then I booted with the old 2.4 Kernel, installed sarge, get a fresh kernel from kernel.org.
After compilation and replacing hda through sda, the T43p boot into 2.6.

==Hardware==
===CPU and frequency scaling===
First you have to activate ACPI and Speedsteep in your Kernel:

<pre>
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_IBM=y
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_ACPI_CPUFREQ=y
CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
CONFIG_X86_ACPI_CPUFREQ_PROC_INTF=y

CONFIG_X86_SPEEDSTEP_CENTRINO=y
CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
CONFIG_X86_SPEEDSTEP_ICH=y
CONFIG_X86_SPEEDSTEP_LIB=y
CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK=y
</pre>

apt-get install acpid powernowd

you can test your current cpu frequenc with the following comand:
echo `cat /proc/cpuinfo | grep "^cpu MHz" | cut -d":" -f2` MHZ

===Network===
Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express (rev 11)
Works with the tg3 module

===Bluetooth===
Nothing special here. Working without any problem.

===Sound===
Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controlle<br>
With ALSA snd_intel8x0 working without any problem.

===Graphics Adapter===
ATI Technologies Inc M24 1T [FireGL M24 GL] (rev 80)

It is a [[ATI Mobility FireGL V3200]] with 128MB

I used the debian packages from [[http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html]] version 8.14.13-2
and followed the instructions on that page.

Nothing special here. (XFree 4.3.0.dfsg)

===Mouse===
I use one external USB Logitech Trackball and both internal, the Touchpad and the Trackpoint.
In my XF86Config-4 are 3 mice.

<pre>
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/psaux"
Option "Protocol" "PS/2"
EndSection

Section "InputDevice"
Identifier "Configured Mouse_II"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/psaux"
Option "Protocol" "PS/2"
EndSection

Section "InputDevice"
Identifier "Generic Mouse"
Driver "mouse"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
EndSection
</pre>

==Buttons==
{|
|ThinkLight
|Fn + PgUp
|Just worked (can also be toggled through ibm-acpi's /proc/acpi/ibm/light)
|-
|Display brightness up
|Fn + Home
|Just worked (no software necessary)
|-
|Display brightness down
|Fn + End
|Just worked (no software necessary)
|}

KDE Konfigurationtool for the Buttons:
apt-get install kmilo

==Various Information==
===lspci Output===

To have all the hardware show up with its proper name, I had to get a new pci.ids file from the [http://pciids.sourceforge.net/ Linux PCI ID Repostiory] and copy it to /usr/share/misc/pci.ids. I believe newer distributions and kernels won't need that file anymore. -- 2005-07-19 (kernel 2.6.12.2) still need it.
<pre>
0000:00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
0000:00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03)
0000:00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
0000:00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 03)
0000:00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
0000:00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
0000:00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
0000:00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
0000:00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
0000:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
0000:00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
0000:00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
0000:00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
0000:00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
0000:00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc M24 1T [FireGL M24 GL] (rev 80)
0000:02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M Gigabit Ethernet PCI Express (rev 11)
0000:04:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 8d)
0000:04:02.0 Network controller: Intel Corporation: Unknown device 4224 (rev 05)
</pre>

[[Category:Debian]] [[Category:T43p]]

BIOS Upgrade

2005-07-05T07:58:01Z

Thinc: /* The Non Diskette Updater */ removed false info about earlier version of the bios.

__TOC__
----

==Before You Begin==

This page is meant to describe ways to update the BIOS on a Thinkpad that only runs Linux for users that don't have ready access to Windows (if you have Windows on your thinkpad you can just boot into it and follow instructions on the IBM website). Updating the BIOS in Linux (with few exceptions) '''is not officially supported''' by IBM. However there are work arounds.

{{WARN|By following any of the instructions here you are accepting the '''very real risk''' of turning your thinkpad into a big expensive paper weight, as a firmware update gone wrong can create unfixable problems.

'''Proceed at your own risk!'''

It is also '''important''' to understand that all newer thinkpads have 2 seperate firmwares, the BIOS and the Control Program. A specific version of the Control Program will only work with specific versions of the BIOS. If you go through the readme's on the IBM site they'll cleary state that '''you must''' update the Control Program first, then imediately update the BIOS. Otherwise you risk turning your thinkpad into a very nice paper weight.}}

==BIOS Upgrade Paths==

For every firmware (either BIOS or Control Program) update on the IBM site there are two different firmware update programs provided.

===The Diskette Updater===

This installer appears to be a 16bit dos program which asks you to accept a license agreement. It will run in Windows, DOS, OS/2, or [http://dosemu.sf.net Dosemu] perfectly, but requires a real floppy disk attached via a real floppy control. The USB Floppy Drive to the new Thinkpads doesn't count.

===The Non Diskette Updater===

'''Warning: Though I've used this process on 1 version of .exe files found on ibm.com website this doesn't mean it will work for all of them. Use at your own risk'''

This installer appears to be a 32bit windows exe which is designed for updating the BIOS directly from a running Windows OS. It turns out that the .exe is really a wrapper license program arround windows .cab files (this information is in [[How_to_change_the_BIOS_bootsplash_screen|BIOS-Bootsplash]]). If you install the Linux program '''cabextract''' you can expand these files directly. Run the following:

cabextract FILENAME.exe

You will get 8 files in the current directory. One of them will be FILENAME.img. You can test that this is really a floppy image by running:

mkdir mntfloppy
mount -o loop FILENAME.img mntfloppy
ls -la mntfloppy

If the results of ls -la look like a dos floppy, and no read errors were displayed, you have a pretty good chance that the floppy image is usable. Again, proceed at your own risk.

==Updating from within Windows==

If you have windows on your machine... you probably never found this page anyway as you wouldn't need it. ;) However updating the BIOS from Windows is very easy, and the supported way to do it by IBM. Simply follow the IBM instructions, as described on the respective BIOS upgrade page on the IBM site.

Note that in one case ([[APM setup on a type 2379 Thinkpad T40]]) it was not possible to upgrade the BIOS from Windows XP; a downgrade to Windows 98 was required to successfully run the BIOS upgrade app. The symptoms in this case were that, once the files had been extracted to the hard disk, and the machine was to reboot into the upgrade app, it would beep and hang just before reboot, requiring a power cycle. Once the power was cycled, it would simply reboot back into XP without performing any BIOS upgrade actions. So even if you have Windows, you may still need to use the info on this page.

==Downloads==

{| border="1" cellspacing="0" cellpadding="2"
| rowspan="3"| '''Models'''
| colspan="2"| '''Non-Diskette'''
| colspan="3"| '''Diskette'''
|-
| rowspan="2"| '''BIOS'''
| rowspan="2"| '''Embedded Controller Program'''
| colspan="2"| '''BIOS'''
| rowspan="2"| '''Embedded Controller Program'''
|-
| '''Windows'''
| '''Linux'''
|-
| {{390}}
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-427MCG 5.62]
|
|
|-
| {{390E}}
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-46AKPY 1.55]
|
|
|-
| {{390X}}
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4C5UP9 0.55]
|
|
|-
| {{560X}}
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-3QYK7L 1.15]
|
|
|-
| {{560Z}}
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-3YTKKV 1.07]
|
|
|-
| {{570}}
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-47JS5Z 1.16]
|
|
|-
| {{570E}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4HT3RD 1.07]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4HA2BF 1.07]
|
|
|-
| {{600}}
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-3VRJPK 1.22]
|
|
|-
| {{600E}} (2645 selected models, 2646)
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-46HLKQ 1.16]
|
|
|-
| {{600E}} (2645: 55x, 56x, 57x, 58x, A5x, A6x, Bxx [except for BAU], JJ1, JJ2, RRA)
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-43DNQ5 1.15]
|
|
|-
| {{600X}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4HVUYL 1.11]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4FYS2U 1.11]
|
|
|-
| {{770}}, {{770E}}, {{770ED}}
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-3P2MCB 1.34]
|
|
|-
| {{770X}}
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-42QLVU 1.10]
|
|
|-
| {{770Z}}
|
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-47F3VA 1.05]
|
|
|-
| {{A20m}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4MNN8Z 1.13]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4JWNTQ 1.13]
|
|
|-
| {{A20p}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4MNN8Y 1.11]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4JWNTR 1.11]
|
|
|-
| {{A21e}} (2165)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4UNQKX 1.07]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4UNRRF 1.07]
|
|
|-
| {{A21e}} (2628)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KLU 1.13]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KLV 1.13]
|
|
|-
| {{A21m}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4PJMXK 1.09]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KM4 1.09]
|
|
|-
| {{A21p}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KM3 1.11]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4PJN8X 1.11]
|
|
|-
| {{A22e}} Celeron
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4UNQKX 1.07]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4UNRRF 1.07]
|
|
|-
| {{A22e}} Pentium
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4XQKLK 1.05]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4XQL7B 1.05]
|
|
|-
| {{A22m}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KM4 1.09]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4PJMXK 1.09]
|
|
|-
| {{A22m}} (2628-Sxx)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4VXS2T 1.05]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4VXRG4 1.05]
|
|
|-
| {{A22p}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KM3 1.11]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4PJN8X 1.11]
|
|
|-
| {{A30}}, {{A30p}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39863 1.18]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-40846 1.07]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39861 1.18]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-40847 1.07]
|-
| {{A31}}, {{A31p}} (Bios 1G*)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42654 1.10]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45771 1.04]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42660 1.10]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45900 1.05]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45770 1.04]
|-
| {{A31}}, {{A31p}} (Bios 1N*)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44450 1.08]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45662 1.04]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44451 1.08]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45898 1.02]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45663 1.04]
|-
| {{G40}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50672 1.17]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50673 1.17]
|
|
|-
| {{G41}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-58127 1.06]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-58129 1.06]
|
|
|-
| {{R30}}
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-40216 1.38]
|
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-40217 1.38]
|
|
|-
| {{R31}}
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-41378 3.11]
|
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-41535 3.11]
|
|
|-
| {{R32}}
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-43571 2.15]
|
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-43572 2.15]
|
|
|-
| {{R40}} (2681, 2682, 2683, 2896, 2898, 2899)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46055 1.23]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46143 1.13]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46061 1.23]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46144 1.13]
|-
| {{R40}} (2722, 2723, 2724, 2897)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50320 1.29]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46143 1.14]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50321 1.29]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46144 1.14]
|-
| {{R40e}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50302 1.33]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50344 1.04]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50301 1.33]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50343 1.04]
|-
| {{R50}}, {{R50p}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50273 3.16]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50279 3.04]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50275 3.16]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50277 3.04]
|-
| {{R50e}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55000 2.02]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54996 1.04]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55001 2.02]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54997 1.04]
|-
| {{R51}} (1829, 1830, 1831, 1836)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50273 3.16]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50279 3.04]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50275 3.16]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50277 3.04]
|-
| {{R51}} (2883, 2887, 2888, 2889, 2894, 2895)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55003 1.21]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54996 1.04]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55004 1.21]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54997 1.04]
|-
| {{R52}} (1846, 1847, 1848, 1849, 1850, 1870)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59221 1.04]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59184 1.02]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59220 1.04]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59183 1.02]
|-
| {{R52}} (1858, 1859, 1860, 1861, 1862, 1863)
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59379 1.01]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59439 1.01]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59380 1.01]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59440 1.01]
|-
| {{T20}}
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4MNN8X 1.22]
|
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4JWNJC 1.22]
|
|
|-
| {{T21}}
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4Q2KM5 1.16]
|
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4PJN8Y 1.16]
|
|
|-
| {{T22}}
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4VWPPU 1.12]
|
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4VWP54 1.12]
|
|
|-
| {{T23}}
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-39366 1.18]
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-40022 1.06a]
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-39362 1.18]
|
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-40021 1.06a]
|-
| {{T30}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42694 2.08]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42711 1.06]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42720 2.08]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45745 2.02]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42725 1.06]
|-
| {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50273 3.16]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50279 3.04]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50275 3.16]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50277 3.04]
|-
| {{T43}}, {{T43p}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59096 1.05]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59120 1.03]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59097 1.05]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59121 1.03]
|-
| {{TransNote}}
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4UDSMK 1.02]
|
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4UDRRF 1.02]
|
|
|-
| {{X20}}, {{X21}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4P52BM 2.25]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4VQNTP 1.36]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4P52BL 2.25]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4PBMCT 1.36]
|-
| {{X22}}, {{X23}}, {{X24}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39672 1.32]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39806 1.30]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39665 1.32]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39808 1.30]
|-
| {{X30}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44135 1.07]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44152 1.04]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44131 1.07]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44149 1.04]
|-
| {{X31}}, {{X32}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50298 3.00d]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53480 1.07b]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50308 3.00d]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53479 1.07b]
|-
| {{X40}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53881 1.65]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53882 1.56]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53883 1.65]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53885 1.56]
|-
| {{X41}}
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59206 1.16]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59208 1.00]
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59205 1.16]
|
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59207 1.00]

|}

==Updating via Floppy==

If you were able to create the boot floppy per the Diskette update method, and you have a Floppy with your Thinkpad, the update should be simple.

==Updating via CD/DVD Drive==

The whole thing gets more complicated if you neither have Windows nor a floppy drive installed. This is what this page is intended to describe.

Be aware that IBM officially does '''not''' support this! The official statement to my support request was:

<blockquote style="background: white; border: 1px solid black; padding: 1em;">
<pre><nowiki>
I'm afraid we only support the options listed on our web page and no you
can't burn a CD/DVD, however you can try to use an external USB FDD
(floppy) drive. The experts recommend a IBM USB FDD, however they have also
tested it with a Sony USB FDD drive.

In order to make sure the drive is recognised you can boot up the FDD with
a bootable dos diskette for w98
</nowiki></pre>
</blockquote>

But it seems to be possible as Mathias Dalheimer describes this [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html here].

Another indication that it should work is that IBM uses PHLASH16.EXE (at least on T4x/p systems) to flash the BIOS into the chip. The same tool is used by [http://www.samsungpc.com/gb/support/p35/bios/bios-instructions.html other vendors] to flash the BIOS from bootable CD-ROMs.
{{WARN|Do '''not''' use the [http://syslinux.zytor.com/ SYSLINUX] image-loader [http://syslinux.zytor.com/memdisk.php MEMDISK] to boot the images! Some flash tools crash in that situation!}}

Some interesting but very technical information about the used flash tool can be found [http://www.paul.sladen.org/thinkpad-r31/wifi-card-pci-ids.html here].

===Creating a Floppy Image===

If you have created a boot floppy on another machine, you need to create an image file of that floppy. This can be easily done in linux by running a command line:

dd bs=2x80x18b if=/dev/fd0 of=/tmp/floppy.img

You should verify this floppy.img as explained above.

===Creating a Bootable CD from a Floppy Image===

Once you have your floppy image, either from imaging a real floppy, or from extracting them via the cabextract method above, you need to make a boot CD out of it.

The eltorito bootable CD standard is a wonderful thing. What this means is that a bootable cd can be made with a bootable floppy in such as way that the CD believes that it is a 2.88 MB floppy drive. This allows you to replace a boot floppy by a boot CD in nearly all situations.

It is very easy to create such a bootable CD ISO image in Linux using the mkisofs tool. To do this run a command as follows:

mkisofs -b bootfloppy.img -o bootcd.iso bootfloppy.img

Note: You don't strictly need the last ''bootfloppy.img'', however some versions of mkisofs get confused about why you would want to create an iso with no contents, and thus won't let you. You don't actually care about the contents of the CD, you only care that the '''-b''' boot image is applied to the CD. For more info on this read the '''mkisofs man page'''.

You can now burn the bootcd.iso in your favorite cd burning program.

To get an overview which models have been tested with this version, here is a list:

===Does work:===
{|
| '''Model''' || '''Tested by'''
|-
| {{R31}} || [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html Mathias Dalheimer]
|-
| {{R40}} || Matthew Lambie, http://lambie.org
|-
| {{R50}} (1836-3SU) || jlbartos <jlbartos at hotmail dot com>
|-
| {{R51}} (1829) || Robert Uhl <rob dot uhl at gmx dot de>
|-
| {{R51}} (2887) || Ingo van Lil <inguin at gmx dot de>
|-
| {{T40}} || Sean Dague, http://dague.net
|-
| {{T40}} || Justin Mason, http://jmason.org
|-
| {{T41}} || Lev Givon (Bios 3.15 / EC 3.04) <lev at columbia dot edu>
|-
| {{T40p}} || Lukas KrÃ¤henbÃ¼hl, ismo at pop dot agri dot ch
|-
| {{T40p}} || Thomas Achtemichuk, tom at tomchuk dot com. BIOS 3.15 flashed fine with cabextract/CD method
|-
| {{T41p}} || Nils Newman, work great. (Version: Bios 3.14 / Embedded Controller 3.04)
|-
| {{T42p}} || Robert Schiele <rschiele@uni-mannheim.de>, Joern Heissler <joern@heissler.de>
|-
| {{T43}} || Tom Heady <tom-thinkwiki.org@punch.net>
|-
| {{X20}} || Neil Caunt <retardis at gmail dot com>
|-
| {{X40}} || Robbie Stone <robbie@serendipity.cx>
|-
| {{T20}} || Franz Hassels <fhassel at suse dot com>
|-
| {{T43}} (2668)|| Carsten SÃ¶hrens <casoe@gmx.de> (Version: Bios 1.05 / Embedded Controller 1.03)
|}

===Does not work:===
{|
| '''Model''' || '''Tested by'''
|}

Please note that testing this is '''at your own risk'''!!!

==Updating with Network Boot Image==

BIOS, Embedded Controller (EC), CD/DVD and Harddisk firmware disks can be booted
over the network with [http://syslinux.zytor.com/pxe.php PXELINUX] as part of the [http://syslinux.zytor.com/ SYSLINUX] package.

This requires that you have a DHCP and tftp server configured and setup properly on
your network, and is probably not for the faint of heart.

Make sure the firmware bootdisk is in linux 'dd' format, as the self-extracting .exe disks
from the IBM website cannot be booted directly as such.

This worked on the {{R31}}, {{X22}}, {{T21}}, {{T30}} and {{T41p}} with various firmware updates.

==Rentry Check List==

(With appologies to Ed Nisley)

The following is important to remember:
# You must update '''both''' the Control Program and the BIOS at the same time
# You must find versions of the Control Program and BIOS that are compatible. Not all of them are, so follow the readmes on the IBM website carefully to determine which are.
# You must update the Control Program '''before''' you update the BIOS
# All of these instructions are provided with '''no warranty'''. A bios update gone wrong for any reason can '''completely destroy''' your Thinkpad.

Wireless Network Adapters

2005-07-05T07:45:15Z

Thinc: /* "Unauthorized" MiniPCI network card */ added note about t43

This document covers IBM integrated (MiniPCI), Cardbus and PC Card (PCMCIA) Wi-Fi devices.

= Finding out which adapter you have =
For MiniPCI or Cardbus adapters run the command:
lspci -n | grep "Class 0200"
And compare the PCI IDS with the ones below.

Note: This will also return the PCI IDS of any Ethernet adapters, as Ethernet adapters and Wireless adapters share the same PCI Class ID.

= MiniPCI adapters =
== Atheros ==
*[[IBM Dual-Band 11a/b Wi-Fi Wireless Mini PCI Adapter]] <tt>(PCI-ID: 168c:0012)</tt>
*[[IBM 11b/g Wireless LAN Mini PCI Adapter]] <tt>(PCI-ID: 168c:0013)</tt>
*[[IBM 11a/b/g Wireless LAN Mini PCI Adapter]] <tt>(PCI-ID: 168c:1014)</tt>
*[[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]] <tt>(PCI-ID: 168c:1014)</tt>
== Cisco ==
*[[Cisco Aironet Wireless 802.11b]] <tt>(PCI-ID: 14b9:a504)</tt>
== Intel ==
*[[Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter]] <tt>(PCI-ID: 8086:1043)</tt>
*[[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] <tt>(PCI-ID: 8086:4220)</tt>
*[[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]] <tt>(PCI-ID: 8086:4224)</tt>
== Prism ==
*[[IBM High Rate Wireless LAN Mini-PCI Adapter with Modem]] <tt>(PCI-ID: 1260:3873)</tt>
*[[IBM High Rate Wireless LAN Mini-PCI Adapter with Modem II]] <tt>(PCI-ID: 1260:3873)</tt>
*[[IBM High Rate Wireless LAN Mini-PCI Adapter III]]

== "Unauthorized" MiniPCI network card ==
Although the MiniPCI slot is an industry standard and can accept any MiniPCI adapter, the IBM BIOS is set to only allow you to boot with an 'authorized' adapter installed. Attempts to install an unsupported card will result in the following message:

1802: Unauthorized network card is plugged in - Power off and remove the miniPCI network card.

This is because the cards ID(s) (what ''lspci'' uses) are checked against a [[Wikipedia:Whitelist|whitelist]] in the BIOS. IBM's reasoning for this is that the combination of MiniPCI card and the integrated antenna in the ThinkPad needs to be certified by the US FCC (Federal Communications Committee).

Several people say that it is not necessary to switch off the computer after receiving the error message. It seems to be possible to press F1 to enter the BIOS and deactivate the WLAN card. -- This does not work on my t43.

There is a tool in the internet called "no-1802". It is used to set a certain bit in the CMOS memory which overrides the whitelist. This does not work on my t43.

Additional Information about "Unauthorised" MiniPCI adapters can be found at: http://www.srcf.ucam.org/~mjg59/thinkpad/

Also see [http://www.paul.sladen.org/thinkpad-r31/wifi-card-pci-ids.html Paul Sladens and Matthew Garretts detailed page on IBM BIOS hacking].

= Cardbus adapters =
Cardbus is a 32bits bus that runs at 33MHz, and is in many ways simular to the PCI bus. In fact under Linux Cardbus adapters are handled by the PCI subsystem.<br>
You can differentiate a PC Card adapter from a Cardbus adapter as the later has a gold coloured grounding strip
== IBM 11 a/b/g Wireless Cardbus Adapter ==
Chipset: Atheros<br>
Driver: [[madwifi]]<br>
Supported wireless modes: 802.11a, 802.11b, 802.11g

Specifications: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51855 MIGR-51855]<br>
Users Guide: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51959 MIGE-51855]<br>
Service Parts: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51874 MIGR-51874]

== IBM 802.11a Wireless LAN Cardbus Adapter ==
Chipset: Atheros<br>
Driver: [[madwifi]]<br>
Supported wireless modes: 802.11a

Specifications: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42209 MIGR-42209]<br>
Users Guide: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42233 MIGR-42233]<br>
Service Parts: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42231 MIGR-42231]

= PC Card (PCMCIA) adapters =
PC Card or PCMCIA (Personal Computer Memory Card International Association) as it used to be called, is an 8 or 16bits bus limited to 8MHz, in many ways simular to the old ISA bus and not suitable for highspeed devices.
== Cisco Aironet 350 802.11b wireless PC card with 128bit ==
Chipset: Cisco<br>
Driver: airo_cs<br>
Supported wireless modes: 802.11b
== IBM High Rate Wireless LAN PC Card ==
Chipset: Prism 2.5<br>
Drivers: [[orinoco|orinoco_pci]] or [[hostap]]<br>
Supported wireless modes: 802.11b