ThinkWiki - User contributions [en]

Problem with high pitch noises

2008-01-18T12:15:23Z

Mozz: /* Kernel BIOS options */

Information on strange high pitch, low volume noises emitted by ThinkPads.

==Problem description==
Even though ThinkPads are known as very silent notebooks, they tend to emit different, mostly high pitch noises in certain circumstances. The noises are of low volume and hence not realized by everyone or at least tolerated by most people. However, there are those with "bat like ears" that hear them and might be annoyed by that.

==Affected Models==
Noises have been experienced in the following situations:
{| border="1" cellspacing="0" cellpadding="2"
|-
! style="vertical-align:top;background-color:#DDDDDD;" | situation
! style="vertical-align:top;background-color:#DDDDDD;" | noise description
! style="vertical-align:top;background-color:#DDDDDD;" | affected models
|-
| style="vertical-align:top;" |
Plugged into AC / running at high CPU frequency
| style="vertical-align:top;" |
soft crackling, buzzing noise
| style="vertical-align:top;" |
*{{T41}}
**2379-DJU
|-
| style="vertical-align:top;" |
ThinkPad suspended to RAM
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T42p}}
|-
| style="vertical-align:top;" |
ThinkPad connected to power and switched off, with battery fully charged
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T41p}}
**2373-GHG
|-
| style="vertical-align:top;" |
moving windows or just the mouse in xorg
| style="vertical-align:top;" |
strange noise like a rapid series of very short high pitch noises adding to a constant kind of whistling (only as long as the movement goes)
| style="vertical-align:top;" |
*{{A21m}}
**2628
*{{T41p}}
**2373-GHG
*{{T60}}
|-
| style="vertical-align:top;" |
Thinkpad connected to power or working on battery, also when suspended to RAM
| style="vertical-align:top;" |
High pitch noise also when HD is powered down.
| style="vertical-align:top;" |
*{{T23}}
**2647-DG4
*{{X24}}
**2662-MWG
|-
| style="vertical-align:top;" |
Thinkpad connected to power battery charged less than 60%
| style="vertical-align:top;" |
High pitch noise till battery is charged more than 60%.
| style="vertical-align:top;" |
*{{T41p}}
**2373-GEG
|-
| style="vertical-align:top;" |
Constantly, if AC connected
| style="vertical-align:top;" |
High pitched, low volume constant noise.
| style="vertical-align:top;" |
*{{T40}}
**2373-88U
|-
| style="vertical-align:top;" |
When the CPU freq jumps up to 1Ghz or above, or when the laptop is in suspend mode
| style="vertical-align:top;" |
Constant high pitched
| style="vertical-align:top;" |
*{{R50}}
**1829-6DM
|-
| style="vertical-align:top;" |
(May come from harddisk.)
| style="vertical-align:top;" |
continuous, intermittent, low volume, high pitched
| style="vertical-align:top;" |
*{{600X}}
|-
| style="vertical-align:top;" |
ACPI puts the processor into the C3 or C4 power saving states (i.e., the system is idle).
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{X41}}
*{{T43}}
**2686-DGU
*{{T43p}}
*{{T60}}
**2007-72U
*{{T21}}
*{{T20}}
**2648-46U
|-
| style="vertical-align:top;" |
Cpufreqd (or powernowd etc.) slows down the processor, for exemple at the end of an heavy task.
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{T42}}
|-
| style="vertical-align:top;" |
When on battery
| style="vertical-align:top;" |
Noise level varies from inaudible to clearly audible, screeching sound, or sometimes beeping (when wifi is on).
| style="vertical-align:top;" |
*{{A21m}}
**2628
*{{R51}}
**EHG-1829
*{{R52}}
**1858-A11
**1846-B5G
*{{R60}}
**9461-DXG
**9462-77G
**9456-HTG
**9461-DXG
*{{R60e}}
**0657-A9G
**0657-3LG
*{{T43}}
**2686-DGU
**1871-4AG
*{{T60}}
**2007-72U
**1951-24G
**1951-24G
**2007-49G
**2007-FUG
*{{T60p}}
**2007-FBG
*{{T61}}
**7659-12G
*{{x60}}
*{{x31}}
**2673-CBU
*{{Z61m}}
**9450-3HG
**9452-128
**9452-W5Q
*{{Z61t}}
**9440-2QU

|-
| CPU is used much AND laptop is on AC power AND the TFT panel is enabled.
| Screetching high pitch noise, like a million crickets
|
* {{X41}}

|-
| Network is pluged in and networkload is ~100%.
| low volume highfreq. pitch noise from left speaker or cpu.
|
*{{Z60m}}, {{Z60t}}
*{{T40}}
*{{T43}}
**2687-DDU

|-
| Constant, but is louder when Tablet Pen is near screen, on battery power
| high pitch noise, screeching sounds *solved by "Media player paused" (see below) and also by BIOS versions 1.05 and later.
|
*{{X60_Tablet}}
**6366-4DU
|}

==Affected Operating Systems==
All, though Linux appears especially susceptible.

==Possible sources==

* '''CPU activity:''' On some models the noise is triggered by certain CPU power states or activity patterns (as proven [http://www.wisdom.weizmann.ac.il/~tromer/acoustic here]).
* '''Graphics processor:''' In some models from the T2x era, e.g. the {{T23}}, the problem was related to the graphics circuitry and occured especially or only while making use of DirectDraw functions. IBM was able to fix it through a BIOS upgrade.
* '''Hard disk:''' On some ThinkPads the processor and hard disk are adjacent and produce similar noise. For example, in the {{X41}} the sound generated by the hard disk is likely to be loudest at the vent.
* '''Gigabit Ethernet processor:''' In some models (e.g., {{T43}}) high ethernet activity causes a high pitch noise.

* '''Screen brightness:''' on an {{X31}}, a hissing sound is started whenever screen brightness is not full.

==Status==

The problem is highly specific to operating system, model and even individual machines. There is no universal solution, but on most machines one of the following will reduce or eliminate the noise (possibly at some cost in power consumption).

==Solutions for CPU-triggered noise==

===Limit ACPI CPU power states===

By default, the kernel supports up to eight ACPI CPU power saving states (C-states), called C1 through C8 (but the ThinkPad BIOS and hardware often offers (or remaps them to) only C1 to C4). Often only the extreme power saving modes C4 or C3 produce the noise, so the noise can be stopped by instructing the Linux ACPI code to use only lower modes. This has a cost, though: disabling C3 and C4 will make the CPU consume more power, and the battery last sooner.

To forbid the ACPI driver from using C4 (this fixed the problem with on some ThinkPad {{T43}}, {{T43p}} and {{T41}}):
* If the ACPI processor component is compiled as built-in (<tt>CONFIG_ACPI_PROCESSOR=y</tt>):
**Pass the {{bootparm|max_cstate|3}} kernel argument.
* If the ACPI processor component is loaded as a module (<tt>CONFIG_ACPI_PROCESSOR=m</tt> and <tt>processor</tt> shows in the output of {{cmdroot|lsmod}}), do either of:
** Pass the {{bootparm|processor.max_cstate|3}} kernel argument (this does not work in Ubuntu 5.10 with default kernel).
** Add <code>options processor max_cstate=3</code> to {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}}, or {{path|/etc/modprobe.d/...}}, depending on your system) (this does not work in Ubuntu 5.10 with default kernel).
** {{cmdroot|echo 3 > /sys/module/processor/parameters/max_cstate}} (this can be changed in runtime for experimentation). (If may need to be set again upon resume from suspend, e.g., in the wakeup script.)
** (On Ubuntu 5.10, the default kernel uses <code>processor</code> as a module. Unfortunately, the script loading it, {{path|/etc/init.d/acpid}}, ignores the <code>options processor max_cstate=3</code> setting in {{path|/etc/modprobe.d/<my file>}}. As a solution for this specific problem, add the line <code>echo 2 > /sys/module/processor/parameters/max_cstate</code> directly to {{path|/etc/init.d/acpid}}, at the end of the function <code>load_modules()</code>, immediately after the line <code>echo "$PRINTK" > /proc/sys/kernel/printk</code>.)
** On Gentoo: Configure your Thinkpad as described in the [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide]. Then as root create the files {{path|/etc/init.d/limit-sleep-states}} and {{path|/etc/conf.d/limit-sleep-states}} as below. After that just issue the command {{cmdroot|rc-update add limit-sleep-states default}} to limit the sleep states only when running on AC power, or {{cmdroot|rc-update add limit-sleep-states default battery}} to always limit the sleep states.
cat <<EOF > /etc/init.d/limit-sleep-states
#!/sbin/runscript

depend() {
need acpid
}

start() {
ebegin "Limiting CPU sleep state to C${LIMIT_CSTATE}"
echo $LIMIT_CSTATE > /sys/module/processor/parameters/max_cstate
eend $?
}

stop() {
ebegin "Removing CPU sleep state limit"
echo $REMOVE_CSTATE > /sys/module/processor/parameters/max_cstate
eend $?
}
EOF

cat <<EOF > /etc/conf.d/limit-sleep-states
# limit CPU sleep state to the following value (adjust accordingly)
LIMIT_CSTATE=3
# some value which is higher than all available sleep states
REMOVE_CSTATE=8
EOF

To also forbid the C3 state, replace "<tt>3</tt>" with "<tt>2</tt>" above (this fixed the problem on some ThinkPad {{X40}}, {{X41}}, {{X60}}, {{T60}}, {{T61}}, {{Z61t}} and {{R52}}, as well as on {{T20}} where C4 is not supported at all).

Note that these options affect power consumption when the CPU is idle. For example, here is the [[How to measure power consumption|measured power consumption]] on a ThinkPad {{T43}}:
* {{bootparm|processor.max_cstate|4}}: 15160mW (default, noisy)
* {{bootparm|processor.max_cstate|3}}: 15770mW (660mW higher, silent)
* {{bootparm|processor.max_cstate|2}}: 16100mW (2940mW higher, silent)

One can control how often Linux tries to enter the C3 state by using the {{bootparm|processor.bm_history|<bitmask>}} parameter on kernels with a scheduler frequency below 800Hz (and if you have noise problems, you really should not be running the kernel at 1000Hz...). Setting {{bootparm|processor.bm_history|0xFFFFFFFF}} will cause C3 to be entered less often. This will waste more power as the CPU won't do C3 or C4 as often, but at least it doesn't forbid C3 and C4 permanently, unlike {{bootparm|max_cstate|2}}.

See the [http://thinkwiki.org/wiki?title=Talk:Problem_with_high_pitch_noises discussion page] for further information and success reports.

*Jakob Schou Pedersen: Editing the file {{path|/etc/init.d/acpid}} as described above (the last solution) worked on my T43 :-)

===Turn off CPU power saving in the BIOS===

Go into the BIOS and turn off the power saving processor feature that puts it into idle mode. This should be somewhere under Config/Power - look for "CPU Power Management", the default being automatic. Set "CPU Power Management" to "Disabled" (This worked on a ThinkPad {{T43}}, {{T21}}, {{X60s}}, {{T60}} and {{Z61m}}). However, this also affects power consumption when the CPU is idle, it's similar to disabling the C4/C3 ACPI CPU power state. For example, on a Z61m 9450-3HG, a full charged battery with power management enabled in the BIOS provides the notebook with power for about 3.5h, if disabled, the battery-lifetime is only about 2h.

===Disable ACPI CPU power states===

Completely disable CPU ACPI power states. Discussion:

*From Martin Steigerwald: I made the observation that I get at least less high pitch noises on my {{T23}} when I do not use the two ACPI modules "processor" and "thermal" (depends on the first one). I have no clue, why. Anyone with similar experiences?
:Omar Yasin: I've got a {{R52}} and when I load the same ACPIO modules the high pitch noises are not as loud but I can still hear them.
*Kaspar Schleiser: On my {{T23}} the noise is less loud when setting max_cstate to 2, but to completely silence it, I have to set it to "1". Is that the same as removing the "processor"-module? "cat /proc/acpi/battery/BAT0/state" does not show increased power drain.
*Niko Ehrenfeuchter: I'm experiencing the same here on my {{X24}}. Removing the "processor" module also stops the pitch noise, which does ONLY occur when setting the CPU to maximum speed (using cpufreq). On low speed it's completely silent, even having loaded the processor module.

*Rolf Adelsberger: I can confirm this: the high pitch noise is only remarkable (at least with my ears ;-) ) if the processor speed is set to maximum frequency.

*Stefan Baums: My {{X41}} produced a high-pitched crackle from the processor vent on the left. Changing HZ did nothing, and the 'processor' module could not easily be removed from the system (Ubuntu 5.04). What solved the problem for me was adding {{bootparm|idle|halt}} to the boot command line. Unfortunately, this solution only lasts until the first hibernation or suspend - when the computer ({{X41}}) resumes, the high-pitched crackle is back.

* The {{bootparm|idle|halt}} solution combined with setting <code>#define HZ 100</code> in the kernel fixes the problem on a {{T43}}.

* jhatch: {{bootparm|idle|halt}} plus <code>#define HZ 100</code> also worked on my {{T43}}. It still reverts back to noisy after a suspend/resume though. This needs to be fixed...

===Change the timer interrupt frequency===

Change the "HZ" kernel constants to alter the frequency of timer interrupts. Discussion:

{{NOTE|The timer interrupt frequency (HZ) in current Linux kernels is directly tied to the kernel task scheduler. Lower frequencies provide larger time-slices and thus also higher latencies (which may kill latency-sensitive applications like audio processing). 100Hz ended up as the recommended "server" setting (because it increases disk/CPU throughput in a latency-insensitive environment). Higher frequencies are better for latency-sensitive applications, and improve desktop responsivity at the cost of less processor throughput. 1000Hz ended up as the recommended "desktop" setting.}}

*Andreas Karnahl: i've read in several forums it has something to do with the "idle"-state (or "C3") of the processor. There is a frequency called "timer interrupt" (or so mething like that). Since kernel 2.6x it is set to 1000 Hz by default (compared to 100 Hz in Kernel 2.4x). The exact reason i don't know, but it is safe to change this frequency to 100 Hz in kernel 2.6x (by the way, windows up to XP uses 100 Hz by default).<br />Just do the following:<br />
: In {{path|[path to kernel-sources]/include/asm-i386/param.h}} find the line
:: <code>#define HZ 1000</code>
: and change the value of HZ to 100:
:: <code>#define HZ 100</code>
:Then recompile the kernel.<br />After i changed it on my ThinkPad {{A30}} (under SuSE 9.2 and 9.3) and recompiling the kernel the high pitch noise is gone away.

* Omar Yasin: Worked on my {{R52}}, thanks.

* [[User:Thinker|Thinker]]: In modern kernels this constant is in the kernel configuration {{kernelconf|CONFIG_HZ|Processor type and features||Timer Frequency|||||}}.

* [[User:sklnd|sklnd]]: As of 2.6.21, enabling a tickless kernel (CONFIG_NO_HZ) seems to fix the sound issue on the X60. This also has the added benefit of causing the kernel to wake up less, which will improve battery life.

===Prevent idling===

Indirectly avoid power saving states by making sure the CPU is rarely idle:

* Paul RIVIER: Here is a really simple workaround. C3 / C4 states are mainly called when the cpu freq is higher than required, for example if your cpufreqd is lazy to slow down the frequency but quick to raise it. That is why I use powernowd with the builtin "passive" mode, which is lazy for raising frequency, but quick to go back to the lowest. Now I don't hear them as often as before, as I avoid C3/C4 states at high frequency.

* The problem also occurs on my {{X41}} with 2.6.11. Setting up [[How to make use of Dynamic Frequency Scaling|frequency scaling]] with the <code>ondemand</code> governor makes things a lot better, as the processor does not stay with the maximum frequency when in idle mode. It can be still heard sometimes, though.

* On a {{T43}} the noise was gone after dropping cpufreqd and switching to the ondemand governor - maybe because of the high sampling rate? (used the default: 10ms)

===Change the processor voltage===

Reducing the processor voltage (when possible) may decrease or eliminate the noise. On one ThinkPad {{T43}}, [[Pentium M undervolting and underclocking|undervolting the Pentium M processor]] eliminated the high-pitched noise. Compared to the other solutions this has the benefit of lower power consumption, both due to the undervolting itself and because there is no need to forbid high APCI CPU power saving modes.

===Kernel BIOS options===

Adding acpi_sleep=s3_bios and pci=bios as boot parameters significantly reduced the pitch noise on a T61. Seems to be the best solution so far, without losing battery capacity. If ondemand governor is enabled as well, the noise is almost gone.--[[User:Mozz|Mozz]] 13:14, 18 January 2008 (CET)

==Solutions for screen brightness related sounds==

===Disable BIOS brightness control===

The sound starts when on batteries as the BIOS automatically reduces screen brightness. To disable this, simply switch Config>Display>Brightness from
Normal to High. See also [[User:Piccobello/Hissing sound on battery|here]].

==Other solutions==

===Disable UltraBay===
*Naheed Vora: My {{T41}} (2373-268) started to give high pitch noise ocassionally, when I upgraded to 2.6.11 kernel. I tried to unload lot of modules but finally figured out that disabling bay stops the noise. If you have [[ibm-acpi]], do (need a cleaner solution): {{cmduser|echo eject >/proc/acpi/ibm/bay}} .

===Disable IrDA===
*Mike Perry: I was able to cure an intermittent high-pitched whine on both my {{X24}} and {{X40}} by disabling the Infrared port.

===Disable the Linuxant Modem Driver===
*Joern Heissler: I made another experience. I played around with linuxant conexant [[Modem Devices|modem]] drivers. After loading them I got some noise on my {{T42p}}.

===Media Player paused===
*Eilif Muller: On my {{R52}} the high-pitched noises go away if I load XMMS, play something then pause it.
*Jacob: On my {{T43}} DGU it goes away if I open mplayerc.exe and press play then pause it. This is the high-pitched noise that only shows up when I'm on battery.
*butcom: On my {{X60 Tablet}}, this tip works in Windows as well with Media Player Classic or Windows Media Player. Just open either program, start playing any music file and pause it and the screeching noise stops.

''I'd guess that the above tip works as when xmms or similar is running, it is uncompressing compressed audio/video, which is a processor intensive action. Keeping this paused means that the app won't 'let go' of the processor, forcing it to stay up and running, which stops it entering the higher powersave modes.''

===nice yes===

Run the command:
{{cmduser|nice yes > /dev/null}}.

This is a good way to test whether the processor is causing the interference, since it forces the CPU to stay at full power. Of course, this will make your system get warm, and probably turn on the fan, as well as eating power.

===Upgrade BIOS===
On a ThinkPad {{X60s}}, [[BIOS_Upgrade|upgrading the BIOS]] to version 1.06 eliminated the high pitch noise when running on battery.

On a ThinkPad {{R60}}, [[BIOS_Upgrade|upgrading the BIOS]] to version 2.19 eliminated the voice also.

===Disable USB===
On one {{T43}} and one {{X60}}, (partially) disabling USB using {{cmdroot|rmmod uhci_hcd}} significantly reduced the noise. Also, on a {{T60}} this trick worked well, doing ''rmmod/modprobe'' twice wiped the noise permanently.

This is likely a CPU-induced noise case, as disabling USB UHCI will reduce a lot the amount of busmaster activity while the computer is idle, and thus has a direct effect on the need for ACPI C-state transitions from C3/C4 to C2 or lower states in a {{T43}} or {{X60}}.

===Suspend USB===
*Stefan Ott: On my X41, the noise seems to have stopped since I enabled "USB selective suspend/resume and wakeup" (CONFIG_USB_SUSPEND).
*babrodtk: This approach worked with an R60 as well.

Problem with high pitch noises

2008-01-18T12:14:55Z

Mozz: /* Solutions for CPU-triggered noise */

Information on strange high pitch, low volume noises emitted by ThinkPads.

==Problem description==
Even though ThinkPads are known as very silent notebooks, they tend to emit different, mostly high pitch noises in certain circumstances. The noises are of low volume and hence not realized by everyone or at least tolerated by most people. However, there are those with "bat like ears" that hear them and might be annoyed by that.

==Affected Models==
Noises have been experienced in the following situations:
{| border="1" cellspacing="0" cellpadding="2"
|-
! style="vertical-align:top;background-color:#DDDDDD;" | situation
! style="vertical-align:top;background-color:#DDDDDD;" | noise description
! style="vertical-align:top;background-color:#DDDDDD;" | affected models
|-
| style="vertical-align:top;" |
Plugged into AC / running at high CPU frequency
| style="vertical-align:top;" |
soft crackling, buzzing noise
| style="vertical-align:top;" |
*{{T41}}
**2379-DJU
|-
| style="vertical-align:top;" |
ThinkPad suspended to RAM
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T42p}}
|-
| style="vertical-align:top;" |
ThinkPad connected to power and switched off, with battery fully charged
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T41p}}
**2373-GHG
|-
| style="vertical-align:top;" |
moving windows or just the mouse in xorg
| style="vertical-align:top;" |
strange noise like a rapid series of very short high pitch noises adding to a constant kind of whistling (only as long as the movement goes)
| style="vertical-align:top;" |
*{{A21m}}
**2628
*{{T41p}}
**2373-GHG
*{{T60}}
|-
| style="vertical-align:top;" |
Thinkpad connected to power or working on battery, also when suspended to RAM
| style="vertical-align:top;" |
High pitch noise also when HD is powered down.
| style="vertical-align:top;" |
*{{T23}}
**2647-DG4
*{{X24}}
**2662-MWG
|-
| style="vertical-align:top;" |
Thinkpad connected to power battery charged less than 60%
| style="vertical-align:top;" |
High pitch noise till battery is charged more than 60%.
| style="vertical-align:top;" |
*{{T41p}}
**2373-GEG
|-
| style="vertical-align:top;" |
Constantly, if AC connected
| style="vertical-align:top;" |
High pitched, low volume constant noise.
| style="vertical-align:top;" |
*{{T40}}
**2373-88U
|-
| style="vertical-align:top;" |
When the CPU freq jumps up to 1Ghz or above, or when the laptop is in suspend mode
| style="vertical-align:top;" |
Constant high pitched
| style="vertical-align:top;" |
*{{R50}}
**1829-6DM
|-
| style="vertical-align:top;" |
(May come from harddisk.)
| style="vertical-align:top;" |
continuous, intermittent, low volume, high pitched
| style="vertical-align:top;" |
*{{600X}}
|-
| style="vertical-align:top;" |
ACPI puts the processor into the C3 or C4 power saving states (i.e., the system is idle).
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{X41}}
*{{T43}}
**2686-DGU
*{{T43p}}
*{{T60}}
**2007-72U
*{{T21}}
*{{T20}}
**2648-46U
|-
| style="vertical-align:top;" |
Cpufreqd (or powernowd etc.) slows down the processor, for exemple at the end of an heavy task.
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{T42}}
|-
| style="vertical-align:top;" |
When on battery
| style="vertical-align:top;" |
Noise level varies from inaudible to clearly audible, screeching sound, or sometimes beeping (when wifi is on).
| style="vertical-align:top;" |
*{{A21m}}
**2628
*{{R51}}
**EHG-1829
*{{R52}}
**1858-A11
**1846-B5G
*{{R60}}
**9461-DXG
**9462-77G
**9456-HTG
**9461-DXG
*{{R60e}}
**0657-A9G
**0657-3LG
*{{T43}}
**2686-DGU
**1871-4AG
*{{T60}}
**2007-72U
**1951-24G
**1951-24G
**2007-49G
**2007-FUG
*{{T60p}}
**2007-FBG
*{{T61}}
**7659-12G
*{{x60}}
*{{x31}}
**2673-CBU
*{{Z61m}}
**9450-3HG
**9452-128
**9452-W5Q
*{{Z61t}}
**9440-2QU

|-
| CPU is used much AND laptop is on AC power AND the TFT panel is enabled.
| Screetching high pitch noise, like a million crickets
|
* {{X41}}

|-
| Network is pluged in and networkload is ~100%.
| low volume highfreq. pitch noise from left speaker or cpu.
|
*{{Z60m}}, {{Z60t}}
*{{T40}}
*{{T43}}
**2687-DDU

|-
| Constant, but is louder when Tablet Pen is near screen, on battery power
| high pitch noise, screeching sounds *solved by "Media player paused" (see below) and also by BIOS versions 1.05 and later.
|
*{{X60_Tablet}}
**6366-4DU
|}

==Affected Operating Systems==
All, though Linux appears especially susceptible.

==Possible sources==

* '''CPU activity:''' On some models the noise is triggered by certain CPU power states or activity patterns (as proven [http://www.wisdom.weizmann.ac.il/~tromer/acoustic here]).
* '''Graphics processor:''' In some models from the T2x era, e.g. the {{T23}}, the problem was related to the graphics circuitry and occured especially or only while making use of DirectDraw functions. IBM was able to fix it through a BIOS upgrade.
* '''Hard disk:''' On some ThinkPads the processor and hard disk are adjacent and produce similar noise. For example, in the {{X41}} the sound generated by the hard disk is likely to be loudest at the vent.
* '''Gigabit Ethernet processor:''' In some models (e.g., {{T43}}) high ethernet activity causes a high pitch noise.

* '''Screen brightness:''' on an {{X31}}, a hissing sound is started whenever screen brightness is not full.

==Status==

The problem is highly specific to operating system, model and even individual machines. There is no universal solution, but on most machines one of the following will reduce or eliminate the noise (possibly at some cost in power consumption).

==Solutions for CPU-triggered noise==

===Limit ACPI CPU power states===

By default, the kernel supports up to eight ACPI CPU power saving states (C-states), called C1 through C8 (but the ThinkPad BIOS and hardware often offers (or remaps them to) only C1 to C4). Often only the extreme power saving modes C4 or C3 produce the noise, so the noise can be stopped by instructing the Linux ACPI code to use only lower modes. This has a cost, though: disabling C3 and C4 will make the CPU consume more power, and the battery last sooner.

To forbid the ACPI driver from using C4 (this fixed the problem with on some ThinkPad {{T43}}, {{T43p}} and {{T41}}):
* If the ACPI processor component is compiled as built-in (<tt>CONFIG_ACPI_PROCESSOR=y</tt>):
**Pass the {{bootparm|max_cstate|3}} kernel argument.
* If the ACPI processor component is loaded as a module (<tt>CONFIG_ACPI_PROCESSOR=m</tt> and <tt>processor</tt> shows in the output of {{cmdroot|lsmod}}), do either of:
** Pass the {{bootparm|processor.max_cstate|3}} kernel argument (this does not work in Ubuntu 5.10 with default kernel).
** Add <code>options processor max_cstate=3</code> to {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}}, or {{path|/etc/modprobe.d/...}}, depending on your system) (this does not work in Ubuntu 5.10 with default kernel).
** {{cmdroot|echo 3 > /sys/module/processor/parameters/max_cstate}} (this can be changed in runtime for experimentation). (If may need to be set again upon resume from suspend, e.g., in the wakeup script.)
** (On Ubuntu 5.10, the default kernel uses <code>processor</code> as a module. Unfortunately, the script loading it, {{path|/etc/init.d/acpid}}, ignores the <code>options processor max_cstate=3</code> setting in {{path|/etc/modprobe.d/<my file>}}. As a solution for this specific problem, add the line <code>echo 2 > /sys/module/processor/parameters/max_cstate</code> directly to {{path|/etc/init.d/acpid}}, at the end of the function <code>load_modules()</code>, immediately after the line <code>echo "$PRINTK" > /proc/sys/kernel/printk</code>.)
** On Gentoo: Configure your Thinkpad as described in the [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide]. Then as root create the files {{path|/etc/init.d/limit-sleep-states}} and {{path|/etc/conf.d/limit-sleep-states}} as below. After that just issue the command {{cmdroot|rc-update add limit-sleep-states default}} to limit the sleep states only when running on AC power, or {{cmdroot|rc-update add limit-sleep-states default battery}} to always limit the sleep states.
cat <<EOF > /etc/init.d/limit-sleep-states
#!/sbin/runscript

depend() {
need acpid
}

start() {
ebegin "Limiting CPU sleep state to C${LIMIT_CSTATE}"
echo $LIMIT_CSTATE > /sys/module/processor/parameters/max_cstate
eend $?
}

stop() {
ebegin "Removing CPU sleep state limit"
echo $REMOVE_CSTATE > /sys/module/processor/parameters/max_cstate
eend $?
}
EOF

cat <<EOF > /etc/conf.d/limit-sleep-states
# limit CPU sleep state to the following value (adjust accordingly)
LIMIT_CSTATE=3
# some value which is higher than all available sleep states
REMOVE_CSTATE=8
EOF

To also forbid the C3 state, replace "<tt>3</tt>" with "<tt>2</tt>" above (this fixed the problem on some ThinkPad {{X40}}, {{X41}}, {{X60}}, {{T60}}, {{T61}}, {{Z61t}} and {{R52}}, as well as on {{T20}} where C4 is not supported at all).

Note that these options affect power consumption when the CPU is idle. For example, here is the [[How to measure power consumption|measured power consumption]] on a ThinkPad {{T43}}:
* {{bootparm|processor.max_cstate|4}}: 15160mW (default, noisy)
* {{bootparm|processor.max_cstate|3}}: 15770mW (660mW higher, silent)
* {{bootparm|processor.max_cstate|2}}: 16100mW (2940mW higher, silent)

One can control how often Linux tries to enter the C3 state by using the {{bootparm|processor.bm_history|<bitmask>}} parameter on kernels with a scheduler frequency below 800Hz (and if you have noise problems, you really should not be running the kernel at 1000Hz...). Setting {{bootparm|processor.bm_history|0xFFFFFFFF}} will cause C3 to be entered less often. This will waste more power as the CPU won't do C3 or C4 as often, but at least it doesn't forbid C3 and C4 permanently, unlike {{bootparm|max_cstate|2}}.

See the [http://thinkwiki.org/wiki?title=Talk:Problem_with_high_pitch_noises discussion page] for further information and success reports.

*Jakob Schou Pedersen: Editing the file {{path|/etc/init.d/acpid}} as described above (the last solution) worked on my T43 :-)

===Turn off CPU power saving in the BIOS===

Go into the BIOS and turn off the power saving processor feature that puts it into idle mode. This should be somewhere under Config/Power - look for "CPU Power Management", the default being automatic. Set "CPU Power Management" to "Disabled" (This worked on a ThinkPad {{T43}}, {{T21}}, {{X60s}}, {{T60}} and {{Z61m}}). However, this also affects power consumption when the CPU is idle, it's similar to disabling the C4/C3 ACPI CPU power state. For example, on a Z61m 9450-3HG, a full charged battery with power management enabled in the BIOS provides the notebook with power for about 3.5h, if disabled, the battery-lifetime is only about 2h.

===Disable ACPI CPU power states===

Completely disable CPU ACPI power states. Discussion:

*From Martin Steigerwald: I made the observation that I get at least less high pitch noises on my {{T23}} when I do not use the two ACPI modules "processor" and "thermal" (depends on the first one). I have no clue, why. Anyone with similar experiences?
:Omar Yasin: I've got a {{R52}} and when I load the same ACPIO modules the high pitch noises are not as loud but I can still hear them.
*Kaspar Schleiser: On my {{T23}} the noise is less loud when setting max_cstate to 2, but to completely silence it, I have to set it to "1". Is that the same as removing the "processor"-module? "cat /proc/acpi/battery/BAT0/state" does not show increased power drain.
*Niko Ehrenfeuchter: I'm experiencing the same here on my {{X24}}. Removing the "processor" module also stops the pitch noise, which does ONLY occur when setting the CPU to maximum speed (using cpufreq). On low speed it's completely silent, even having loaded the processor module.

*Rolf Adelsberger: I can confirm this: the high pitch noise is only remarkable (at least with my ears ;-) ) if the processor speed is set to maximum frequency.

*Stefan Baums: My {{X41}} produced a high-pitched crackle from the processor vent on the left. Changing HZ did nothing, and the 'processor' module could not easily be removed from the system (Ubuntu 5.04). What solved the problem for me was adding {{bootparm|idle|halt}} to the boot command line. Unfortunately, this solution only lasts until the first hibernation or suspend - when the computer ({{X41}}) resumes, the high-pitched crackle is back.

* The {{bootparm|idle|halt}} solution combined with setting <code>#define HZ 100</code> in the kernel fixes the problem on a {{T43}}.

* jhatch: {{bootparm|idle|halt}} plus <code>#define HZ 100</code> also worked on my {{T43}}. It still reverts back to noisy after a suspend/resume though. This needs to be fixed...

===Change the timer interrupt frequency===

Change the "HZ" kernel constants to alter the frequency of timer interrupts. Discussion:

{{NOTE|The timer interrupt frequency (HZ) in current Linux kernels is directly tied to the kernel task scheduler. Lower frequencies provide larger time-slices and thus also higher latencies (which may kill latency-sensitive applications like audio processing). 100Hz ended up as the recommended "server" setting (because it increases disk/CPU throughput in a latency-insensitive environment). Higher frequencies are better for latency-sensitive applications, and improve desktop responsivity at the cost of less processor throughput. 1000Hz ended up as the recommended "desktop" setting.}}

*Andreas Karnahl: i've read in several forums it has something to do with the "idle"-state (or "C3") of the processor. There is a frequency called "timer interrupt" (or so mething like that). Since kernel 2.6x it is set to 1000 Hz by default (compared to 100 Hz in Kernel 2.4x). The exact reason i don't know, but it is safe to change this frequency to 100 Hz in kernel 2.6x (by the way, windows up to XP uses 100 Hz by default).<br />Just do the following:<br />
: In {{path|[path to kernel-sources]/include/asm-i386/param.h}} find the line
:: <code>#define HZ 1000</code>
: and change the value of HZ to 100:
:: <code>#define HZ 100</code>
:Then recompile the kernel.<br />After i changed it on my ThinkPad {{A30}} (under SuSE 9.2 and 9.3) and recompiling the kernel the high pitch noise is gone away.

* Omar Yasin: Worked on my {{R52}}, thanks.

* [[User:Thinker|Thinker]]: In modern kernels this constant is in the kernel configuration {{kernelconf|CONFIG_HZ|Processor type and features||Timer Frequency|||||}}.

* [[User:sklnd|sklnd]]: As of 2.6.21, enabling a tickless kernel (CONFIG_NO_HZ) seems to fix the sound issue on the X60. This also has the added benefit of causing the kernel to wake up less, which will improve battery life.

===Prevent idling===

Indirectly avoid power saving states by making sure the CPU is rarely idle:

* Paul RIVIER: Here is a really simple workaround. C3 / C4 states are mainly called when the cpu freq is higher than required, for example if your cpufreqd is lazy to slow down the frequency but quick to raise it. That is why I use powernowd with the builtin "passive" mode, which is lazy for raising frequency, but quick to go back to the lowest. Now I don't hear them as often as before, as I avoid C3/C4 states at high frequency.

* The problem also occurs on my {{X41}} with 2.6.11. Setting up [[How to make use of Dynamic Frequency Scaling|frequency scaling]] with the <code>ondemand</code> governor makes things a lot better, as the processor does not stay with the maximum frequency when in idle mode. It can be still heard sometimes, though.

* On a {{T43}} the noise was gone after dropping cpufreqd and switching to the ondemand governor - maybe because of the high sampling rate? (used the default: 10ms)

===Change the processor voltage===

Reducing the processor voltage (when possible) may decrease or eliminate the noise. On one ThinkPad {{T43}}, [[Pentium M undervolting and underclocking|undervolting the Pentium M processor]] eliminated the high-pitched noise. Compared to the other solutions this has the benefit of lower power consumption, both due to the undervolting itself and because there is no need to forbid high APCI CPU power saving modes.

===Kernel BIOS options===

Adding acpi_sleep=s3_bios and pci=bios significantly reduced the pitch noise on a T61. Seems to be the best solution so far, without losing battery capacity. If ondemand governor is enabled as well, the noise is almost gone.--[[User:Mozz|Mozz]] 13:14, 18 January 2008 (CET)

==Solutions for screen brightness related sounds==

===Disable BIOS brightness control===

The sound starts when on batteries as the BIOS automatically reduces screen brightness. To disable this, simply switch Config>Display>Brightness from
Normal to High. See also [[User:Piccobello/Hissing sound on battery|here]].

==Other solutions==

===Disable UltraBay===
*Naheed Vora: My {{T41}} (2373-268) started to give high pitch noise ocassionally, when I upgraded to 2.6.11 kernel. I tried to unload lot of modules but finally figured out that disabling bay stops the noise. If you have [[ibm-acpi]], do (need a cleaner solution): {{cmduser|echo eject >/proc/acpi/ibm/bay}} .

===Disable IrDA===
*Mike Perry: I was able to cure an intermittent high-pitched whine on both my {{X24}} and {{X40}} by disabling the Infrared port.

===Disable the Linuxant Modem Driver===
*Joern Heissler: I made another experience. I played around with linuxant conexant [[Modem Devices|modem]] drivers. After loading them I got some noise on my {{T42p}}.

===Media Player paused===
*Eilif Muller: On my {{R52}} the high-pitched noises go away if I load XMMS, play something then pause it.
*Jacob: On my {{T43}} DGU it goes away if I open mplayerc.exe and press play then pause it. This is the high-pitched noise that only shows up when I'm on battery.
*butcom: On my {{X60 Tablet}}, this tip works in Windows as well with Media Player Classic or Windows Media Player. Just open either program, start playing any music file and pause it and the screeching noise stops.

''I'd guess that the above tip works as when xmms or similar is running, it is uncompressing compressed audio/video, which is a processor intensive action. Keeping this paused means that the app won't 'let go' of the processor, forcing it to stay up and running, which stops it entering the higher powersave modes.''

===nice yes===

Run the command:
{{cmduser|nice yes > /dev/null}}.

This is a good way to test whether the processor is causing the interference, since it forces the CPU to stay at full power. Of course, this will make your system get warm, and probably turn on the fan, as well as eating power.

===Upgrade BIOS===
On a ThinkPad {{X60s}}, [[BIOS_Upgrade|upgrading the BIOS]] to version 1.06 eliminated the high pitch noise when running on battery.

On a ThinkPad {{R60}}, [[BIOS_Upgrade|upgrading the BIOS]] to version 2.19 eliminated the voice also.

===Disable USB===
On one {{T43}} and one {{X60}}, (partially) disabling USB using {{cmdroot|rmmod uhci_hcd}} significantly reduced the noise. Also, on a {{T60}} this trick worked well, doing ''rmmod/modprobe'' twice wiped the noise permanently.

This is likely a CPU-induced noise case, as disabling USB UHCI will reduce a lot the amount of busmaster activity while the computer is idle, and thus has a direct effect on the need for ACPI C-state transitions from C3/C4 to C2 or lower states in a {{T43}} or {{X60}}.

===Suspend USB===
*Stefan Ott: On my X41, the noise seems to have stopped since I enabled "USB selective suspend/resume and wakeup" (CONFIG_USB_SUSPEND).
*babrodtk: This approach worked with an R60 as well.

NVIDIA Quadro NVS 140M

2007-11-27T15:01:57Z

Mozz: /* LCD Backlight Brightness Control on T61/R61 */

__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;">
=== NVIDIA Quadro NVS 140M ===

The NVIDIA Quadro NVS 140M is a mobile video card with a G86 core and either 128 MB or 256 MB graphics memory.

=== Features ===

* Chipset: nVidia Quadro NVS 140M
* PCI ID:
** 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0429 (rev a1) (prog-if 00 [VGA])
*** Subsystem: Lenovo Unknown device 20d8
*** Flags: bus master, fast devsel, latency 0, IRQ 169
*** Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
*** Memory at e0000000 (64-bit, prefetchable) [size=256M]
*** Memory at d4000000 (64-bit, non-prefetchable) [size=32M]
*** I/O ports at 2000 [size=128]
*** Capabilities: [60] Power Management version 2
*** Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
*** Capabilities: [78] Express Endpoint IRQ 0
*** Capabilities: [100] Virtual Channel
*** Capabilities: [128] Power Budgeting
*** Capabilities: [600] Unknown (11)
* PCI Express 16×
* 128 or 256 MB video memory

=== Linux X.Org driver ===

Default X.Org NVidia driver, called "nv" works.

=== NVIDIA proprietary driver ===

Support for Quadro NVS 140M has been introduced in the NVIDIA Linux unified driver version 100.14.09 (released on 8 June 2007). For the latest drivers go to the [http://www.nvidia.com/object/unix.html NVIDIA Unix Drivers page]. Note that NVIDIA proprietary drivers do not work with a Xen virtualized kernel.

==== CUDA ====

Since it has a G86 core, [http://developer.nvidia.com/object/cuda.html NVidia CUDA] works on this video card, even though not being listed in the CUDA manuals. Running very large problems (like the SDK examples) however might fail by running out of the relatively small graphics memory.

=== LCD Backlight Brightness Control on T61/R61 ===

There has been an issue with Brightness Control on T61/R61s. This seems to be fixed with the 169.04 BETA drivers from Nvidia. You can find them i.e. here [http://www.nvidia.com/object/linux_display_ia32_169.04.html 169.04 BETA Driver]. You might also need the latest BIOS ([[BIOS_Upgrade_Downloads]] 1.26) as well as the latest version of [[Ibm-acpi]] (thinkpad-acpi, V0.18).

If the nvidia module is loaded with the argument NVreg_EnableBrightnessControl=1, one can switch to a virtual console, change the lcd brightness level there, and have that level preserved after switching back to the X session. On a {{T61}}, this was tested with the acpi video driver included in the vanilla Linux 2.6.21-6 kernel and on an {{R61}} with {{OpenSUSE}} 10.2.

[[Category:Components]]

NVIDIA Quadro NVS 140M

2007-11-27T15:01:14Z

Mozz:

__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;">
=== NVIDIA Quadro NVS 140M ===

The NVIDIA Quadro NVS 140M is a mobile video card with a G86 core and either 128 MB or 256 MB graphics memory.

=== Features ===

* Chipset: nVidia Quadro NVS 140M
* PCI ID:
** 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0429 (rev a1) (prog-if 00 [VGA])
*** Subsystem: Lenovo Unknown device 20d8
*** Flags: bus master, fast devsel, latency 0, IRQ 169
*** Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
*** Memory at e0000000 (64-bit, prefetchable) [size=256M]
*** Memory at d4000000 (64-bit, non-prefetchable) [size=32M]
*** I/O ports at 2000 [size=128]
*** Capabilities: [60] Power Management version 2
*** Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
*** Capabilities: [78] Express Endpoint IRQ 0
*** Capabilities: [100] Virtual Channel
*** Capabilities: [128] Power Budgeting
*** Capabilities: [600] Unknown (11)
* PCI Express 16×
* 128 or 256 MB video memory

=== Linux X.Org driver ===

Default X.Org NVidia driver, called "nv" works.

=== NVIDIA proprietary driver ===

Support for Quadro NVS 140M has been introduced in the NVIDIA Linux unified driver version 100.14.09 (released on 8 June 2007). For the latest drivers go to the [http://www.nvidia.com/object/unix.html NVIDIA Unix Drivers page]. Note that NVIDIA proprietary drivers do not work with a Xen virtualized kernel.

==== CUDA ====

Since it has a G86 core, [http://developer.nvidia.com/object/cuda.html NVidia CUDA] works on this video card, even though not being listed in the CUDA manuals. Running very large problems (like the SDK examples) however might fail by running out of the relatively small graphics memory.

=== LCD Backlight Brightness Control on T61/R61 ===

There has been an issue with Brightness Control on T61/R61s. This seems to be fixed with the 169.04 BETA driver from Nvidia. You can find them i.e. here [http://www.nvidia.com/object/linux_display_ia32_169.04.html 169.04 BETA Driver]. You might also need the latest BIOS ([[BIOS_Upgrade_Downloads]] 1.26) as well as the latest version of [[Ibm-acpi]] (thinkpad-acpi, V0.18).

If the nvidia module is loaded with the argument NVreg_EnableBrightnessControl=1, one can switch to a virtual console, change the lcd brightness level there, and have that level preserved after switching back to the X session. On a {{T61}}, this was tested with the acpi video driver included in the vanilla Linux 2.6.21-6 kernel and on an {{R61}} with {{OpenSUSE}} 10.2.

[[Category:Components]]

NVIDIA Quadro NVS 140M

2007-11-06T20:24:44Z

Mozz: /* LCD Backlight Brightness Control on T61/R61 */

__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;">
=== NVIDIA Quadro NVS 140M ===

The NVIDIA Quadro NVS 140M is a mobile video card with a G86 core and either 128 MB or 256 MB graphics memory.

=== Features ===

* Chipset: nVidia Quadro NVS 140M
* PCI ID:
** 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0429 (rev a1) (prog-if 00 [VGA])
*** Subsystem: Lenovo Unknown device 20d8
*** Flags: bus master, fast devsel, latency 0, IRQ 169
*** Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
*** Memory at e0000000 (64-bit, prefetchable) [size=256M]
*** Memory at d4000000 (64-bit, non-prefetchable) [size=32M]
*** I/O ports at 2000 [size=128]
*** Capabilities: [60] Power Management version 2
*** Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
*** Capabilities: [78] Express Endpoint IRQ 0
*** Capabilities: [100] Virtual Channel
*** Capabilities: [128] Power Budgeting
*** Capabilities: [600] Unknown (11)
* PCI Express 16×
* 128 or 256 MB video memory

=== Linux X.Org driver ===

Default X.Org NVidia driver, called "nv" works.

=== NVIDIA proprietary driver ===

Support for Quadro NVS 140M has been introduced in the NVIDIA Linux unified driver version 100.14.09 (released on 8 June 2007). For the latest drivers go to the [http://www.nvidia.com/object/unix.html NVIDIA Unix Drivers page]. Note that NVIDIA proprietary drivers do not work with a Xen virtualized kernel.

==== CUDA ====

Since it has a G86 core, [http://developer.nvidia.com/object/cuda.html NVidia CUDA] works on this video card, even though not being listed in the CUDA manuals. Running very large problems (like the SDK examples) however might fail by running out of the relatively small graphics memory.

=== LCD Backlight Brightness Control on T61/R61 ===

To the best of my knowledge, no one has been able to get LCD backlight brightness control to work with this video card on the {{T61}}/{{R61}} when using the proprietary driver. However, brightness control works fine when using the vesa driver, so it seems that the problem lies with the Nvidia driver itself.

{{QUOTE|Mike Kershaw|linux-thinkpad@linux-thinkpad.org|This problem was solved (for me) with the latest IBM bios release,
October 18, bios 1.26, 7KET56WW. In-X brightness works now via the hw
keys and acpi/ibm/brightness.}}

Strangely, if the nvidia module is loaded with the argument NVreg_EnableBrightnessControl=1, one can switch to a virtual console, change the lcd brightness level there, and have that level preserved after switching back to the X session. On a {{T61}}, this was tested with the acpi video driver included in the vanilla Linux 2.6.21-6 kernel and on an {{R61}} with {{OpenSUSE}} 10.2.

[[Category:Components]]

NVIDIA Quadro NVS 140M

2007-11-06T20:24:21Z

Mozz: /* LCD Backlight Brightness Control on T61/R61 */

__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;">
=== NVIDIA Quadro NVS 140M ===

The NVIDIA Quadro NVS 140M is a mobile video card with a G86 core and either 128 MB or 256 MB graphics memory.

=== Features ===

* Chipset: nVidia Quadro NVS 140M
* PCI ID:
** 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0429 (rev a1) (prog-if 00 [VGA])
*** Subsystem: Lenovo Unknown device 20d8
*** Flags: bus master, fast devsel, latency 0, IRQ 169
*** Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
*** Memory at e0000000 (64-bit, prefetchable) [size=256M]
*** Memory at d4000000 (64-bit, non-prefetchable) [size=32M]
*** I/O ports at 2000 [size=128]
*** Capabilities: [60] Power Management version 2
*** Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
*** Capabilities: [78] Express Endpoint IRQ 0
*** Capabilities: [100] Virtual Channel
*** Capabilities: [128] Power Budgeting
*** Capabilities: [600] Unknown (11)
* PCI Express 16×
* 128 or 256 MB video memory

=== Linux X.Org driver ===

Default X.Org NVidia driver, called "nv" works.

=== NVIDIA proprietary driver ===

Support for Quadro NVS 140M has been introduced in the NVIDIA Linux unified driver version 100.14.09 (released on 8 June 2007). For the latest drivers go to the [http://www.nvidia.com/object/unix.html NVIDIA Unix Drivers page]. Note that NVIDIA proprietary drivers do not work with a Xen virtualized kernel.

==== CUDA ====

Since it has a G86 core, [http://developer.nvidia.com/object/cuda.html NVidia CUDA] works on this video card, even though not being listed in the CUDA manuals. Running very large problems (like the SDK examples) however might fail by running out of the relatively small graphics memory.

=== LCD Backlight Brightness Control on T61/R61 ===

To the best of my knowledge, no one has been able to get LCD backlight brightness control to work with this video card on the {{T61}}/{{R61}} when using the proprietary driver. However, brightness control works fine when using the vesa driver, so it seems that the problem lies with the Nvidia driver itself.

{{QUOTE|Mike Kershaw|linux-thinkpad@linux-thinkpad.org|This problem was solved (for me) with the latest IBM bios release,
October 18, bios 1.26, 7KET56WW. In-X brightness works now via the hw
keys and acpi/ibm/brightness.}}

Strangely, if the nvidia module is loaded with the argument NVreg_EnableBrightnessControl=1, one can switch to a virtual console, change the lcd brightness level there, and have that level preserved after switching back to the X session. On a {{T61}}, this was tested with the acpi video driver included in the vanilla Linux 2.6.21-6 kernel and on an {{R61}} with {{OpenSUSE}} 10.2.

[[Category:Components]]

NVIDIA Quadro NVS 140M

2007-11-06T20:22:44Z

Mozz: /* LCD Backlight Brightness Control on T61/R61 */

__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;">
=== NVIDIA Quadro NVS 140M ===

The NVIDIA Quadro NVS 140M is a mobile video card with a G86 core and either 128 MB or 256 MB graphics memory.

=== Features ===

* Chipset: nVidia Quadro NVS 140M
* PCI ID:
** 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0429 (rev a1) (prog-if 00 [VGA])
*** Subsystem: Lenovo Unknown device 20d8
*** Flags: bus master, fast devsel, latency 0, IRQ 169
*** Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
*** Memory at e0000000 (64-bit, prefetchable) [size=256M]
*** Memory at d4000000 (64-bit, non-prefetchable) [size=32M]
*** I/O ports at 2000 [size=128]
*** Capabilities: [60] Power Management version 2
*** Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
*** Capabilities: [78] Express Endpoint IRQ 0
*** Capabilities: [100] Virtual Channel
*** Capabilities: [128] Power Budgeting
*** Capabilities: [600] Unknown (11)
* PCI Express 16×
* 128 or 256 MB video memory

=== Linux X.Org driver ===

Default X.Org NVidia driver, called "nv" works.

=== NVIDIA proprietary driver ===

Support for Quadro NVS 140M has been introduced in the NVIDIA Linux unified driver version 100.14.09 (released on 8 June 2007). For the latest drivers go to the [http://www.nvidia.com/object/unix.html NVIDIA Unix Drivers page]. Note that NVIDIA proprietary drivers do not work with a Xen virtualized kernel.

==== CUDA ====

Since it has a G86 core, [http://developer.nvidia.com/object/cuda.html NVidia CUDA] works on this video card, even though not being listed in the CUDA manuals. Running very large problems (like the SDK examples) however might fail by running out of the relatively small graphics memory.

=== LCD Backlight Brightness Control on T61/R61 ===

To the best of my knowledge, no one has been able to get LCD backlight brightness control to work with this video card on the {{T61}}/{{R61}} when using the proprietary driver. However, brightness control works fine when using the vesa driver, so it seems that the problem lies with the Nvidia driver itself.

Strangely, if the nvidia module is loaded with the argument NVreg_EnableBrightnessControl=1, one can switch to a virtual console, change the lcd brightness level there, and have that level preserved after switching back to the X session. On a {{T61}}, this was tested with the acpi video driver included in the vanilla Linux 2.6.21-6 kernel and on an {{R61}} with {{OpenSUSE}} 10.2.

{{QUOTE|Mike Kershaw|linux-thinkpad@linux-thinkpad.org|This problem was solved (for me) with the latest IBM bios release,
October 18, bios 1.26, 7KET56WW. In-X brightness works now via the hw
keys and acpi/ibm/brightness.}}

[[Category:Components]]

Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61

2007-10-13T14:58:33Z

Mozz: /* Suspend */

On the T61, [[Installing_Ubuntu_7.10_(Gutsy_Gibbon)_Release_Candidate_on_a_ThinkPad_T61|Ubuntu 7.10 (Gutsy Gibbon)]] is recommended instead of 7.04 because video drivers and wifi, among other issues, work by default.
recomended

===My DVD drive/CD burner/DVD burner doesn't work (Solved)===

Follow these instructions to enable your [http://en.wikipedia.org/wiki/Optical_drive optical drive]:<br>
1) Reboot your T61. Press the ThinkVantage button quickly when you see the ThinkPad screen and then press F1 enter [http://en.wikipedia.org/wiki/BIOS BIOS].<br>
2) In BIOS, select Configure -> Serial ATA.<br>
3) Now, select Compatibility instead of AHCI.<br>
4) Exit BIOS and start your computer normally.<br>
5) Go to Places -> Computer, right-click your CD-ROM/DVD/etc. drive, and select Properties. Then, go to Drive -> Settings. Set the mount point to ''cdrom'' (regardless of whether it's a CD-ROM drive, DVD drive, etc.).

----

At first, the Ubuntu Live CD would not start at all, this seems to be a problem with the SATA AHCI driver. I had to go into the BIOS and change the SATA driver from ACHI to compatibility (What is the difference? Am I loosing performance?).

----

After you've installed and booted, try the advice from [[Problems_with_SATA_and_Linux]]. Do this:
'''# echo options libata atapi_enabled=1>/etc/modprobe.d/atapienable && update-initramfs -u'''
Then try turning AHCI back on in the BIOS. On a custom-built 2.6.21.5 kernel, my DVD drive appears as /dev/hda and DMA works.
--[[User:Kc8tbe|Kc8tbe]] 12:45, 1 July 2007 (UTC)

If your DVD drive does not appear, modprobe pata-jmicron and ide-generic.
--[[User:Antikristian|Antikristian]] 01:23, 30 July 2007 (UTC)

===NVIDIA Quadro NVS 140M (Solved)===
After initial issues like those explained above in the SATA Issues, I received the xorg error 'fatal error: no screens found'. I was able to boot into Safe Graphics Mode and run the installer, though I had to move both window manager bars to see enough of the install window to use it.

Alternatively, you can download the drivers via wget in a console. Take care to follow the instructions in
[http://www.nvnews.net/vbulletin/showthread.php?t=72490 the NVidia Forum] and uninstall all the packages wit apt-get remove, as described.
Then run the nvidia installer.

Remember that, after you upgrade the kernel, you also have to re-install the drivers.

After installing the NVIDIA drivers, your laptop may not wake after suspend or hibernation. I followed these instructions to fix it [https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend Ubuntu Community Help].

====Alternative NVIDIA driver installation====
Instead of installing the NVIDIA drivers manually as described above, you can try using [http://www.albertomilone.com/nvidia_scripts1.html Envy]. It automatically installs the latest NVIDIA drivers, and cleans up any previous installations.

=== Intel Graphics Media Accelerator X3100 (Chipset GM965) (Solved)===
After that the CD seemed to boot but the screen was just garbage [http://shadowarts.nonlogic.org/projects/thinkpad/screen_garbage.jpg Picture]. In order to get around that issue I had to go back and download the Alternate CD, which allows you to install in text only mode. From here, the text-only install went okay. Changing the VGA settings on the regular CD worked for me.

When I booted up after the installation, I was still getting the same garbage on the screen. To resolve this I edited my [http://shadowarts.nonlogic.org/projects/thinkpad/xorg.conf xorg.conf] file as shown. I also had to install the latest kernel for Feisty, as the one off of the install disk did have have /dev/agpgart. And I could then use X11. There were still some issues however. The screen seemed somewhat fuzzy. This was a little more challenging of a fix... I found [http://www.spinics.net/lists/xorg/msg25099.html this] mailing list posting, according to it, there was a small glitch in the driver. To fix it:
<pre>
apt-get source xserver-xorg-video-intel
cd xserver-xorg-video-intel-1.9.94/
vim src/i830_lvds.c
Goto line 230 and delete (PFIT_ENABLE | VERT_AUTSCALE ....);, replacing it with 0; then quit vim
dpkg-buildpackage -rfakeroot -uc -b
cd ..
dpkg -i xserver-xorg-video-intel_1.9.94-lubuntu3_amd64.deb (wont be amd64 with a 32-bit install)
</pre>
Now reboot your computer, and it should work. **NOTE: For some reason just restarting X didn't fix it, seems like you must reboot.** At this point you should have a nice, crisp display.

I am still working on aiglx and compiz (switching desktops on a cube doesnt seem to work, though I have some ideas...). There are some issues with OpenGL apps freezing Xorg as well, but the standard 2D desktop works flawlessly.
----
It doesn't seem to be necessary to modify the soruce of xserver-xorg-video-intel anymore, but 3D-acceleration doesn't seem to be stable yet and kdm occasionally needs to be restarted after a login attempt.--[[User:Kc8tbe|Kc8tbe]] 12:49, 1 July 2007 (UTC)

----
I was able to use the normal feisty install disk by changing the SATA setting in BIOS, then change the resolution to 800x600 prior to install, then sudo apt-get update and upgrade, and then sudo apt-get install xserver-xorg-video-intel, then change xorg.conf to match link above and 2D graphics work fine. Jul 18, 2008 - John E
----

It seems that everything works fine when using "apt pinning" and updating the xserver-xorg-video-intel, mesa and other packages to the versions provided by Gutsy. I did the following and the resolution and Compiz Fusion are working fine at the moment. The original source of the steps described below can be found here: [http://techreport.com/forums/viewtopic.php?p=714998#714998]

'''Instructions:'''
* Make a new file /etc/apt/preferences
* In the preferences file, put:
<pre>
Package: *
Pin: release a=feisty
Pin-Priority: 700

Package: *
Pin: release a=gutsy
Pin-Priority: 200
</pre>
* Now, edit your sources.list and copy the main and restricted (and others if you want) repo lines replacing feisty with gutsy:
<pre>
# original
deb http://archive.ubuntu.com/ubuntu feisty main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu feisty main restricted universe multiverse

# your addition
deb http://archive.ubuntu.com/ubuntu gutsy main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu gutsy main restricted universe multiverse
</pre>
* Now run:
<pre>
sudo apt-get update
</pre>
{{HINT|If you get an error while trying to update, it may be because your apt cache is too small. To fix this add the following to your "/etc/apt/apt.conf.d/70debconf":
<pre>
APT::Cache-Limit "118388608";
</pre>--[[User:Thefekete|Thefekete]] 04:14, 19 September 2007 (UTC)}}
*Then Run:
<pre>
sudo apt-get -t gutsy install xserver-xorg-video-intel
sudo apt-get -t gutsy install linux
sudo apt-get -t gutsy install libgl1-mesa-dri
</pre>
* Now reboot.

Probably now you have the weird effect that your GUI is scaled wrong and doesn't fill the full width of the monitor. To fix that, open your xorg.conf and make the following changes:
* Add the following section to your xorg.conf
<pre>
Section "Monitor"
Identifier "TVOutput"
Option "Disable" "true"
EndSection
</pre>
* Then in the "Device" section add the following line:
<pre>
Option "monitor-TV" "TVOutput"
</pre>

That should fix the scaling problem and now everything should work fine.
--[[User:Shuk|Shuk]] 02:26, 10 July 2007 (UTC)

{{HINT|If you experience problems with totem or other gstreamer apps crashing, try this:
<pre>
$ gstreamer-properties
</pre>
* Then under the "Video" tab, change the Output Plugin to "X Window System (No Xv)"
This will run the video through you processor, but won't crash gstreamer. --[[User:Thefekete|Thefekete]] 04:14, 19 September 2007 (UTC)}}

===ThinkFinger===
Ubuntu does not come with a package for thinkfinger. Downloading the most recent source and building it was simple enough: Download most recent version (0.3 at time of writing)
<pre>
sudo apt-get install libpam0g-dev libusb-dev
tar xvzf thinkfinger-0.3.tar.gz
cd thinkfinger-0.3/
./configure --with-securedir=/lib/security --with-birdir=/etc/pam_thinkfinger
make -j5 (hey its dual core!)
sudo make install
sudo ldconfig
</pre>

Configuring it is easy as well, open /etc/pam.d/common-auth:
<pre>
auth sufficient pam_thinkfinger.so
auth required pam_unix.so try_first_pass nullok_secure
</pre>

Create the data directory and set your fingerprint:
<pre>
sudo mkdir /etc/pam_thinkfinger
sudo tf-tool --add-user <username>
</pre>

To get be asked to swipe your finger when logging in or sudoing
<pre>
sudo modprobe uinput
</pre>
To make sure it works after reboot add "uinput" to the list in /etc/modules.

It will all be setup. (I found this somewhere on the web, I wish I could give a source but I'm afraid I cant find it, thank you Anonymous!).

===HDAPS===
This seems to be working fine now, I just follow the step on [[How_to_protect_the_harddisk_through_APS]]. Using hdaps-gl does the inverse of the accelerometer, though it's not really a big deal, the harddrive protection should still work.

Assuming that the (improved) hdaps code bundled with tp_smapi is being used, editing the transform_axis function in tp_smapi-0.32/hdaps.c will allow for the proper operation of the accelerometer. Assuming that the accelerometer is rotated 90 degrees from its proper orientation (as it is with the X61), the following code will suffice:

<pre>
static void transform_axes(int *x, int *y)
{
int temp = *x;
*x = -*y;
*y = temp;
}
</pre>

For those paying attention in linear algebra, this corresponds to a linear transformation that rotates a 2D coordinate system 90 degrees.
--[[User:Mbsullivan|Mbsullivan]] 04:21, 27 August 2007 (UTC)

Instead of editing the code, you can just pass the invert=1 parameter when loading the module; modprobe hdaps invert=1
--[[User:Vegar|Vegar]] 14:40, 17 September 2007 (UTC)

===WiFi===
If you have Intel 4965AGN WiFi card, you have to use ndiswrapper OR use backported kernel from Ubuntu Gutsy (Anybody have howto?) and use following:
http://kuscsik.blogspot.com/2007/06/how-to-install-intel-4965-wireless.html

'''Note:'''
Do not use the latest versions of iwlwifi and mac80211. For me with Gutsy mac80211-8.0.2 and iwlwifi-0.0.42 work with the latest firmware. No further modification needed.

If you have the Atheros card, Ubuntu should automatically install madwifi, which works out of the box
----
Works for me with iwlwifi-4965-ucode-4.44.15, iwlwifi-0.0.34, and mac80211-8.0.1. The catch is, you need to patch your kernel with mac80211, which will fail at compile time with the stock Ubuntu sources. Worked for me with vanilla 2.6.21.5 sources patched for tp_smapi and hdaps protect. Make sure to disable CONFIG_NET_WIRELESS_RTNETLINK in your kernel config.

You can download what you need for for iwlwifi and mac80211 from
http://intellinuxwireless.org .--[[User:Kc8tbe|Kc8tbe]] 13:00, 1 July 2007 (UTC)

Works for me with vanilla kernel v2.6.22.1, ucode 4.44.17, iwlwifi 0.1.2 and mac80211 9.0.2. --[[User:Mbsullivan|Mbsullivan]] 13:40, 24 July 2007 (UTC)

You can also use Kernel 2.6.22.9 and Ubuntu Modules 2.6.22.9 from Gutsy and you will not need to compile anything! Works very well.

===Keyboard/Apostrophe issues (Solved)===
When installing with the alternate CD, Ubuntu asks you if your keyboard as a character that appears to be a quotation mark (this character: "). If you're using a US English keyboard, say no; the character is actually an umlaut. [[User:SteveSims|SteveSims]] 02:15, 19 August 2007 (UTC)

My apostrophe key outputs ´ instead of '. I went to System -> Preferences -> Keyboard and could not figure out how to fix it. [[User:SteveSims|SteveSims]] 21:50, 11 August 2007 (UTC)

:Try switching your keyboard layout to US-Classic, and putting it on the top of the list. After you do that, it works perfectly. --[[User:Adamacious|Adamacious]] 04:29, 13 August 2007 (UTC)

::There is no "US Classic" option. Here's what I have:<br>
[[Image:Keyboard_options.png]]<br>
[[User:SteveSims|SteveSims]] 02:17, 15 August 2007 (UTC)

:::It started working, even though I changed nothing. I'm running it as a Macintosh US English keyboard. [[User:SteveSims|SteveSims]] 17:20, 15 August 2007 (UTC)

::::Sorry Steve, what you had to do (and what you did) is select US English, as in the header in the list. It doesn't look selectable, but it is.--[[User:Adamacious|Adamacious]] 20:02, 22 August 2007 (UTC)

===Audio===
====Fixed in Gutsy====
As of 29 August 2007 and [https://bugs.launchpad.net/bugs/122560 this issue], the 2.6.22-10 kernel in Gutsy Gibbon supports audio out-of-the-box (as well as WiFi and other things). Installing the Gutsy kernel via apt and rebooting fixed audio for me, both speakers and headphones. Remaining issues:

* The mute button mutes audio, but doesn't unmute. Pressing volume up or down does unmute it, but has no effect on volume.
* KMix's system tray volume control has no effect because it thinks it's setting the headphones while both outputs are using the speaker settings, but opening KMix and setting the PCM volume works. --lgarfiel

====Python script fix (slightly easier fix)====
First, you have to download the source for the [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.5.tar.gz latest Linux kernel] (2.6.22-5 as of August 26th, 2007) and compile it, something most users cannot do. However, you won't have to compile ALSA and its modules from source if you do it this way.

1) Download the [http://launchpadlibrarian.net/8899521/t61_audio_hack.py T61 audio hack] from [[Launchpad]]. Move it to a convenient folder (e.g., not your desktop).<br>
2) Go to System -> Preferences -> Sessions -> Startup Programs -> Add.<br>
3) Name it whatever you want. Choose something simple like "Python audio fix."<br>
4) Go to Command, and enter the following (with quotation marks):
<pre>gksudo <nowiki>"[THE FOLDER THAT T61_AUDIO_HACK.PY IS IN]</nowiki>/t61_audio_hack.py"</pre>
For example, on my computer, I put t61_audio_hack.py into the /fixes folder in my home folder, so I entered:
<pre>sksudo "/home/sims/fixes/t61_audio_hack.py"</pre> into the Command textbox.<br>
5) Log out, log back in, and type your password quickly when prompted the second time.

References:
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/122560 Launchpad Bug #122560]
[https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/133105 Launchpad Bug #133105]

====ALSA driver update (hard fix, recommended for advanced users)====

:'''''Note: This section assumes a high level of technical proficiency. Please fix it.'''''
::*<s>At [http://www.alsa-project.org www.asla-project.org], did you download only alsa-driver-1.0.14? That and alsa-lib-1.0.14a?</s>
:::Download alsa-driver, alsa-kernel, alsa-lib, and alsa-utils, according to [http://alsa.opensrc.org/index.php/AlsaCVS http://alsa.opensrc.org/index.php/AlsaCVS]. Other sources, however, say only the driver is necessary. Perhaps alsa-project.org simply recommends the other two?
::*''How'' did you compile it from source? ''How'' did you add the patch?
::*In short, please explain ''how'' you did these things in addition to just telling us ''what'' you did. I´m not trying to be rude but seriously, not all Linux users are programmers ;). Thanks. [[User:SteveSims|SteveSims]] 22:19, 11 August 2007 (UTC)
After upgrading to 1.0.14 I still had no sound, and this took about a week to solved (though it was so sadly obvious though). Just upgrading to alsa 1.0.14 will not be enough, there were a few patches released right after the release that fix the Thinkpad's. The reason I missed this was because it was the same day so the release of 1.0.14!

---------------------------------------------------------------------------
VERY SIMPLE METHOD OF MAKING SOUND WORK
http://forums.fedoraforum.org/showthread.php?t=159516&page=1&pp=15
Just follow the instructions step by step, except for two small things:
When doing "cp ../patch_analog.c alsa-driver-1.0.14/alsa-kernel/pci/hda/" use "cp ../patch_analog.c alsa-kernel/pci/hda/" instead
Also, when you get to the part about modifying the modprobe.conf file, it doesn't exist in ubuntu. Adding "options snd-hda-intel index=0 model=thinkpad" to any file (even one you make yourself) inside etc/modprobe.d should work. I personally added it to the options file, and it works fine.

-credit for the guide goes to ciphermonk, and credit to the small changes needed to make this work on ubuntu go to my friend John.

-hotkeys control mic volume, not speaker volume for some reason. I do not know how to fix this

-this fix should provide sound for both headphones and speakers.

-this edit by fatalchaos
---------------------------------------------------------------------------------------

First make sure these packages are installed (System -> Administration -> Synaptic Package Manager) : automake, autoconfig, cvs, libtool, python-dev, build-essential

Then download the source code to the alsa-driver and apply these patches: (links to the revisions)

* [http://hg.alsa-project.org/alsa-kernel/rev/958b39f3e8dd Fix Oops with AD1984 thinkpad model]
* [http://hg.alsa-project.org/alsa-kernel/rev/47ca87407c84 Fix AD1984 basic model]
* [http://hg.alsa-project.org/alsa-kernel/rev/ca37aeeeb0ea Fix Thinkpad X61/T61 outputs]

'''Please use CVS version of ALSA instead. All of these patches are committed'''. The link to the CVS version of ALSA is dead[http://alsa.opensrc.org/index.php/AlsaCVS].

After doing a make and make install reboot your computer (or rrmmod snd-hda-intel && modprobe snd-hda-intel). And run alsamixer (for me it only works as root atm). If you can´t find alsamixer, you can run it in the terminal (Applications -> Accessories -> Terminal) by entering ''alsamixer''. You will have to play with the settings a bit. Make sure the speaker option is not muted and leave the Internal Mic Boost at 0, other wise you will have a really loud microphone feedback sort of sound constantly.

I had to chmod -R 777 /dev/snd/ to get everything work for now. (THIS IS NOT THE CORRECT WAY TO DO IT, IT WILL NOT STAY BETWEEN REBOOTS!).

Audio playback should then work, audio capture (microphone) doesn't seem to work, but I am probably not going to try and fix it, I don't use the capture so I am not concerned with that at the moment.
'''Update:''' With ALSA CVS, microphone seems to work

If you can't hear the mic boost mic settings. Here are my settings at KMix
Output
Mic - low
Mic Boost - full
Input
Mic boost [enable] - medium
capture [enable] - medium

works great with Skype. Also you can use the 'mic level meter' on KRecord to check the mic

In Gnome, default channel mapped to thinkpad volume buttons is MIC, which is bad. Go to ''System->Preferences->Sound->Default mixer tracks'' to change it

'''Please note''' that internal speakers doesn't work with ALSA CVS. Use the headphone jack. Solution?

----
When starting alsamixer over the terminal I couldn't activate the speakers and only had sound over the headphone. However, I figured out how to easily activate the speakers:
* Right-click on your microphone icon in the top panel.
* (If "Mute" is activated, deactivate it. I had that at the beginning and was confused since in alsa you don't really realize it.)
* Click on "Open Volume Control"
* Change to the tab "Switches" and activate the option for speaker.
That should be enough to make it work.
--[[User:Shuk|Shuk]] 02:51, 11 July 2007 (UTC)

I tried those patches, it didnt work for me. But this python script did: http://www.klabs.be/~fpiat/linux/debian/Etch_on_Thinkpad_T61.html#Sound .. apparently if you make the PC speaker play constantly, you cant hear it but you can then hear sound. Hopefully gutsy will fix this :/ --[[User:Rubin|Rubin]] 07:18, 14 July 2007 (UTC)

==Suspend==
Suspending doesn't work by default. It succesfully suspends, but after resuming, Kernel panic occurs. I didn't test hibernate.
I managed to get suspend to ram to work by using this script:

#!/bin/sh

# if launched through a lid event and lid is open, do nothing
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0

# remove USB 1.1 driver
rmmod uhci_hcd
rmmod ehci_hcd

# sync filesystem and clock
sync
/sbin/hwclock --systohc

# switch to console
FGCONSOLE=`fgconsole`
chvt 6

# go to sleep
sleep 5 && echo -n "mem" > /sys/power/state

# readjust the clock (it might be off a bit after suspend)
/sbin/hwclock --adjust
/sbin/hwclock --hctosys

# reload USB 1.1 driver
modprobe uhci_hcd
modprobe ehci_hcd

# turn on the backlight and switch back to X
chvt $FGCONSOLE

It's very similar to script posted on thinkwiki, but I had to add ehci_hcd to removed modules and remove some radeon stuff (when using Nvidia)

{{HINT| "The problem with this suspend script is, that after resuming, the laptop is incredibly slow. Applications start about 20 seconds, Firefox is lagging." Solution: Use latest nvidia drivers (.19)}}

This X-slow-after-resume is still here (T61p, nVidia Quadro FX 570 M, bleeding edge Gutsy 2.6.22-10-generic kernel). However, I found an official OpenSuSE 10.3 for this problem:
[https://bugzilla.novell.com/show_bug.cgi?id=290385]
--[[User:Lech|Lech]] 21:20, 2 September 2007 (UTC)

When using this script, my USB ports are 'dead' after resume (i.e. nothing connected to it gets any power). I have commented out 'rmmod ehci_hcd' and 'modprobe ehci_hcd' lines, to make the USB ports active after a suspend/resume cycle. (this is using nvidia card)

----
Suspend and hibernate work out-of-the-box for me with the 2.6.21.5 kernel, except that you need to put acpi_sleep=s3_bios in the kernel command line (i.e. at the end of each kernel line in /boot/grub/menu.lst).
--[[User:Kc8tbe|Kc8tbe]] 13:03, 1 July 2007 (UTC)

Hmm, with 2.6.21.5 + acpi_sleep=s3_bios, laptop suspends, but resume fails - machine locks up. This is with nvidia 140. Same result when doing it at console. When I resume, I hear a beep and the machine hangs. Have to hard-reset. Suggestions?

Some things seem to break after suspend for me, like network connections time out randomly, cdrom stops working etc. Running 'sudo /etc/init.d/dbus restart' seems to solve it for the most part.

----
We are having similar discussions in Ubunutu's Launchpad, and we found kind of a solution which rules out any 2D/3D graphics acceleration but allows to suspend/resume, at least on my 3 weeks old T61p and some other recent T6x/R6x models:

With thinkpad_acpi 0.16 (!) patches applied to 2.6.22 kernel, and with VESA driver only, it works perfectly so far for us.

The discussion and some links can be found at:
https://bugs.launchpad.net/ubuntu/+bug/139089
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/129125

I know it's not eye candy not to have satisfying GLX etc., but I consider working suspend/resume much more important than say playing with GoogleEarth.

--[[User:Lech|Lech]] 14:48, 16 September 2007 (UTC)

==Brightness==
Changing brightness doesn't work at all. There are many issues. I tried Gutsy and still the same (even worse)

Not a real solution, but if using the vesa driver, brightness control works. ''--Daniel06'' 11:58, 4 July 2007

doesnt work for me with vesa or intel --[[User:Rubin|Rubin]] 06:19, 14 July 2007 (UTC)

It works fine on mine and I have built-in graphics on my motherboard. [[User:SteveSims|SteveSims]] 02:19, 15 August 2007 (UTC)

=== one idea ===
echo "up" >/proc/acpi/ibm/brightness
...works. as does 'down' and 'level x' where x is 1-7. But how to tie that into the buttons? Seems they are currently using something else in /proc that doesnt exist for us. --[[User:Rubin|Rubin]] 06:19, 14 July 2007 (UTC)

=== yet another idea ===

You can add the Gnome power manager brightness applet to the gnome panel, which gives you a GUI tool to do the job, rather than hardware buttons. I don't know about KDE or other window managers. --[[User:Atoponce|Atoponce]] 13:07 22, Aug 2007

=== Another solution for Brightness, using xbacklight and laptop-mode ===

While the hardware buttons still don't work, I have a solution that will automatically raise and lower the backlight when plugged in or on battery.

First, make sure Gnome isn't trying to set the brightness, by going to System > Preferences > Power Management. In the On Battery Power tab, set "Dim display brightness by" to 0%.

Next, install xbacklight.

sudo apt-get install xbacklight

You can manually set the backlight by using "xbacklight -set <number from 1-100>". Note that by using xbacklight, you can make the backlight go brighter or dimmer than normally allowed by Windows or Ubuntu.

To automate brightness changes, first enable laptop-mode

sudo nano /etc/default/acpi-support

Scroll to the bottom and change ENABLE_LAPTOP_MODE to true

ENABLE_LAPTOP_MODE=true

Set laptop mode to start automatically

sudo update-rc.d laptop-mode multiuser

Edit laptop-mode.conf to automate brightness changes. Scroll down to LCD brightness settings. Modify the section to read as follows:

CONTROL_BRIGHTNESS=1

BATT_BRIGHTNESS_COMMAND="xbacklight -set 20"
LM_AC_BRIGHTNESS_COMMAND="xbacklight -set 100"
NOLM_AC_BRIGHTNESS_COMMAND="xbacklight -set 100"
BRIGHTNESS_OUTPUT="/dev/null"

Note: You can use any value from 1 to 100 after -set, I used 20 and 100 as examples. After this, start the laptop-mode daemon, and test if it works. You may have to restart acpid as well.

sudo /etc/init.d/laptop-mode start
sudo /etc/init.d/acpid restart

==Webcam==
The webcam in T61 is some sort of UVC camera: Found UVC 1.00 device Integrated Camera (17ef:1004). The module loads out of the box. I tested the camera using:
Luvcview: http://mxhaard.free.fr/spca50x/Investigation/uvc/luvcview-20070512.tar.gz
Just compile and run using ./luvcview -f yuv (JPG format doesn't work)

I also tried gqcam and webcam, but both doesn't work (first SEGFAULTs, second prints Invalid argument)

luvcview has a button to take pictures. Place your mouse over the buttons at the bottom of the window, and their function is revealed in the title bar. Unfortunately, the button for avi capture does not seem to work (although it does tell you what the video framerate is, which is helpful).

To capture a video stream, run ./luvcview -f yuv -S
To play back the video stream, run mplayer -demuxer rawvideo -rawvideo fps=7:w=320:h=240:yuy2 stream.raw

==64 bit systems issues==
If you are running 64 bit Ubuntu, you will face some problems with 32 bit only proprietary applications. Most of them can be solved.

===Firefox & Flash===
You can use 32bit version of Firefox (see google), or use http://gwenole.beauchesne.info/projects/nspluginwrapper/ nspluginwrapper] which i prefer:
sudo apt-get install ia32-libs ia32-libs-gtk linux32 lib32asound2 alien
Now download both nspluginwrapper rpms (Plugin + Viewer) and convert them:
sudo alien nspluginwrapper*.rpm
sudo dpkg -i nspluginwrapper*.deb

Download Adobe Flash Player: http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_9_linux.tar.gz
tar -xvzf install_flash_player_9_linux.tar.gz
cd install_flash_player_9_linux
sudo install libflashplayer.so flashplayer.xpt /usr/lib/firefox/plugins
nspluginwrapper -i /usr/lib/firefox/plugins/libflashplayer.so
cd ~/.mozilla/plugins/
sudo install npwrapper.libflashplayer.so /usr/lib/mozilla-firefox/plugins/
This howto is taken from [http://webzine.smehlik.net/64bit-ubuntu-adobe-flash-plugin-pomoci-nspluginwrapper/ Smehlik Webzine (in Czech)]

===Skype===
Download Skype for Ubuntu Feisty
Use this commandlibdbus, libqt4-core, libqt4-gui, libsigc++ to determine missing libraries:
ldd /usr/bin/skype | grep not
It should be these:
libdbus, libqt4-core, libqt4-gui, libsigc++ (2.0 version)
Download them from http://packages.ubuntu.com (32bit versions!)
mkdir testlibs
dpkg-deb --extract <deb file> testlibs
Now copy everything from testlibs to /usr/lib32
cp -r testlibs/usr/lib/* /usr/lib32
Freedom lovers are advised to avoid proprietary systems like Skype, however. Centralized directories and signalling architectures can't be good for your health.

==Bluetooth==
works for me (TM)

==USB==
A short time after the system has booted, I get a message on the console of every window indicating IRQ# 23 has fired but noone is expecting it. After this message, the USB ports on the right side fail to work anymore. It was suggested on a forum that they will work, its just it takes it a long time to discover there is a new device. I looked in /proc and determined that the bluetooth device is using IRQ23, so it may be involved, but there may be sharing so it could be something else. Regardless, there are USB bus problems with the T61 and linux.

==Overall==
I initially had some big problems getting this working, but now its working quite well. The wifi card worked at startup (uses madwifi) and I am happy because I don't seem to need any proprietary software to run this system.

==Discussion==
In case you missed it the discussion page (for questions/responses) is right here: [[Talk: Installing Ubuntu 7.04 (Feisty Fawn) on a ThinkPad T61]]

==References==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].
* Many other suggestions and references can be found in the following ubuntu forum: http://ubuntuforums.org/showthread.php?t=471563

[[Category:Ubuntu 7.04]]
[[Category:T61]]

Installing Ubuntu 7.04 on a ThinkPad T43

2007-09-30T07:55:00Z

Mozz: /* Disk Protection */

__TOC__

==Overview==
Worked right out of the box
* 1400*1050 resolution
* Battery Management
* Ultra Nav (Trackpoint and synaptic touchpad)
* WLAN (Atheros, IBM 11a/b/g Wireless LAN Mini PCI Adapter II)
* Hibernate and Standby (some installs have problems with hibernate)
* Fn keys (switch between monitors untested)
* Audio Keys
* ThinkLight
* ATI 3D Acceleration (Mobility Radeon X300)
* AIGLX / Compiz

Was easy
* Fingerprint reader
* AIGLX / Beryl
* middle key of Ultra Nav (Trackpoint) for scrolling
* Active Protection System (acceleration sensor)
* Forward/Backward keys, Access IBM Key
* Toggle Touchpad on/off

Was very hard
* Active Protection System (hard disk parking needs kernel recompile)

Untested
* Bluetooth (light indicates working)
* Modem
* IrDA
* TV out, VGA out

==Installation==

I just installed Feisty using the graphical installer. {{WARN|Installing grub to the MBR may hurt your Rescue 'n' Recovery Partition!}} If you want to keep you Rescue 'n' Recovery Partition, read [http://gawrysiak.org/corvus/?p=4 this blog entry].
Whatever you do, you should care about Backups etc. yourself. A starting point is given in [[Installing Ubuntu 6.10 on a ThinkPad T43#Installation]]

The only non-free driver that was activated was atheros for wifi access.
For graphics the free ati/radeon driver was activated, the restricted ati alternative fglrx was installed but not enabled. I did not try it.

==Configuration==

===3D Acceleration===

====Compiz====

3D Acceleration and Compiz worked out of the box for me. Just activate it in the system menu under desktop effects. I had some minor issues, but I blame the beta status for that.
To test if 3D Acceleration it works, if you have problems, type

$ glxinfo | grep rendering

The answer should be: "direct rendering: Yes". If it says "No", you don't have 3D acceleration.

====Beryl====

I just installed following packages and started beryl-manager. Everything just works out of the box. If you enable compiz effect in the gnome menu you can even swith between beryl, compiz and metacity (no effects) just using the beryl-manager applet.

sudo apt-get install beryl beryl-core beryl-manager beryl-plugins beryl-plugins-data beryl-settings beryl-settings-bindings

====Problem====

If you have problems watching videos when 3D acceleration is enabled, make sure to use the X11 output format. Follow the instructions in [https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/102290 this bug] to do so.

====Compiz-Fusion====

To try out Compiz-Fusion, i.e. early versions of the merge between beryl and compiz, there are many installation guides available on the net, e.g. in the [http://ubuntuforums.org/showthread.php?t=481314h Ubuntu Forum].

===Active Protection System (acceleration monitor)===

====Acceleration Monitor)====

The T43 has a great system to protect your hard disk, the Active Protection System APS. [[HDAPS]] and [[How to protect the harddisk through APS]] describe how you can use it.

Feisty comes with with the accelerometer installed but not activated. To test it activate the kernel module and use a neat program you find in hdaps-utils

To activate it, type:

{{cmduser|sudo su}}
{{cmdroot|echo "hdaps" >> /etc/modules}}
{{cmdroot|exit}}
{{cmduser|sudo modprobe hdaps}}

For a nice 3D show type:

{{cmduser|sudo apt-get install hdaps-utils}}
{{cmduser|hdaps-gl}}

Now you can evaluate acceleration of your Laptop. Your hard disk unfortunately still is not protected. To achive this, try the next chapter.

====Disk Protection====

{{HINT|This one is a little harder to do and can easily fail. If you want to try it anyway, remember, it might not work. In that case you can always reselect your old kernel in grub when booting. So you'd better not delete the old kernel...}}

You'll probably need the following packages:
{{cmduser|sudo apt-get install build-essential fakeroot kernel-package libncurses5-dev wget bzip2}}

Test your kernel version with {{cmduser|uname -r}}

If you see 2.6.20-15-generic, you can just follow the provided instructions. If you have a different version, adapt this howto to your personal needs. Download the right patch for your kernel version, in my case it was
[http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993 2.6.30 rc], but now (may 2007) there is a newer available:
[http://www.nabble.com/attachment/9047418/0/hdaps_protect-2.6.20.patch.bz2 2.6.20]
You'll find more patches in [[HDAPS#Disk_head_parking]]

Get the kernel sources and patch them:

{{cmduser|sudo su}}
{{cmdroot|cd /linux/src}}
{{cmdroot|apt-get install linux-source}}
{{cmdroot|cd linux-source-2.6.20}}
{{cmdroot|patch -p1 -l < /home/silvan/993-001.bin }}

If you only saw some lines saying "patching line..." and "succeeded...", then everything is fine.
{{HINT|If you do not use restricted drivers you can leave that out. I need them for making my atheros wifi working using madwifi.}}
{{cmdroot|sudo apt-get install linux-restricted-modules-generic linux-restricted-modules-common}}

Take necessary steps for whatever restricted kernel module you want to use, e.g.

For atheros wifi get madwifi-source, I used the one from debian testing, as ubuntu does not povide them: [http://packages.debian.org/testing/net/madwifi-source debian testing madwifi-source]. Install them and unpack the madwifi package in {{path|/usr/src}}.

{{HINT|Go on here if you don't want restricted drivers}}
Now let's build the kernel; if you need help on this look at [http://howtoforge.org/roll_a_kernel_debian_ubuntu_way this] or [http://www.howtoforge.com/kernel_compilation_ubuntu that] howto from howtoforge.

{{cmdroot|make clean}}
{{cmdroot|make oldconfig}}
{{cmdroot|fakeroot make-kpkg clean}}
# fakeroot make-kpkg --append-to-version=.hdapscustom kernel_image --initrd binary

This will probably take a very long time, it took me roughly 1:45 hours on my T43. You have to be patient. If it didn't finish with errors, let's now install the newly built kernel. First check the name of our kernel package, and then install at least the image and the header packages. I just installed all like this:

{{cmdroot|cd /usr/src}}
{{cmdroot|ls -l}}
{{cmdroot|dpkg -i}}
{{cmdroot|dpkg -i linux-headers-2.6.20.3-ubuntu1.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-doc-2.6.20.3-ubuntu1.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb }}
{{cmdroot|dpkg -i linux-image-2.6.20.3-ubuntu1.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_i386.deb}}
{{cmdroot|dpkg -i linux-manual-2.6.20.3-ubuntu1.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb }}
{{cmdroot|dpkg -i linux-source-2.6.20.3-ubuntu1.hdapscustom_2.6.20.3-ubuntu1.hdapscustom-10.00.Custom_all.deb}}

Do the same for all packages that were created for restricted modules. Maybe you have to create them first with something like:

# cmdroot|fakeroot make-kpkg --append-to-version=.hdapscustom --added-modules madwifi modules_image

And let's not forget to leave the super user shell

{{cmdroot|exit}}

Now is the time to reboot and to test if everything went fine ;-) Verify with {{cmduser|uname -a}} if you booted the right kernel. If you want you can decide which kernel should be booted by default in /boot/grub/menu.lst selecting the number of the boot entry in the line after 'default'.

Check the output of

$ dmesg | grep hdaps

In my case the new kernel printed nothing, the old kernel printed:

{{cmdresult|hdaps: IBM ThinkPad T43 detected.}}
{{cmdresult|hdaps: initial latch check good (0x01).}}
{{cmdresult|hdaps: device successfully initialized.}}
{{cmdresult|input: hdaps as /class/input/input4}}
{{cmdresult|hdaps: driver successfully loaded.}}

Next step is to install hdapsd, the daemon, that actually stops the hard disk. Get the latest user space daemon [http://www.zen24593.zen.co.uk/hdaps/ hdapsd]. Compile and install it using

{{cmduser|gcc -o hdapsd hdapsd-*.c}}
{{cmduser|sudo cp hdapsd /usr/local/sbin/}}

Start hdapsd using {{cmduser|hdapsd -d sda -s 15}}

{{HINT|What is the best way to start the userspace daemon automatically at boot time? -- There is an init script available in the hdapsd package from the debian (lenny) repos. Just install the package and replace the /usr/bin/hdapsd with the one you compiled --[[User:Mozz|Mozz]] 07:55, 30 September 2007 (UTC)}}

If you move your Laptop you should now see the console printing messages if the disk is parked or not.
{{HELP|It didn't work for me: hdapsd only starts with sudo. Without it says "open(protect_file): Permission denied". The output of sudo hdapsd is saying parking/un-parking, but with a lot of "open: No such file or directory" in between. Any help is appreciated! Use gcc-3.4 to compile, then it should work.}}

$ dmesg | grep protect

should confirm this. If the output says something like {{cmdresult|unload support NOT reported..}} and {{cmdresult|head park not requested, used standby!..}}, have a look at http://thinkwiki.org/wiki/Problem_with_APS_harddisk_parking and examine if your drive might have problems with the disk protection.

A useful gimmick is the gnome-hdaps-applet showing the current disk protection state in the panel. KDE users look at [http://www.kde-apps.org/content/show.php?content=34134 khdapsmonitor] for an alternative. To install gnome-hdaps-applet, do the following:

{{cmduser|mkdir gnome-hdaps-applet}}
{{cmduser|cd gnome-hdaps-applet}}
{{cmduser|wget http://www.zen24593.zen.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|tar -xzf gnome-hdaps-applet-20060120.tar.gz}}
{{cmduser|sudo apt-get install libpanel-applet2-dev}}
{{cmduser|gcc $(pkg-config --cflags --libs libpanelapplet-2.0) -o gnome-hdaps-applet gnome-hdaps-applet.c}}
{{cmduser|sudo install gnome-hdaps-applet /usr/bin/}}
{{cmduser|sudo mkdir /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp *.png /usr/share/pixmaps/gnome-hdaps-applet/}}
{{cmduser|sudo cp GNOME_HDAPS_StatusApplet.server /usr/lib/bonobo}}
{{HELP|Everything seems to work fine with the patched kernel - unless wifi. Ubuntu doesn't find my wireless device anymore. Probably this is because my Atheros card needs restricted modules. Find more infos on http://madwifi.org/wiki/ on compiling Atheros wifi modules. Maybe the kernel compile goal modules or modules_image could help. Could please someone detail the preferred way to handle this?}}o/servers/}}

Afterwards add the applet to your panel manually. Be sure to see the play/pause sign switching when moving your laptop :-)

{{HELP|The applet always shows the play sign, never the pause sign. I think this the same problem like the hdapsd-sudo problem -- Make sure, it doesn't due to the sensitivity value of ''15'' you specified when starting the daemon (it has to be a value between 0 and 1)}}

More information can be found on [[How to protect the harddisk through APS]] or [[Installing_Ubuntu_6.06_on_a_ThinkPad_T43#Active_Protection_System]] or [http://ubuntuforums.org/showthread.php?t=122863 Howto for edgy].
If you speak italian (unfortuately my level is really, really poor), [http://www.ismprofessional.net/pascucci/documenti/z60t/ar01s05.html Fedora on z60t] might be of use to you. Maybe even somebody would find the time to translate and adopt this fedora howto to english and ubuntu?

===Track Point Middle Key Scrolling===

In my case the track point worked out of the box, but the middle mouse button for scrolling did not. [[How to configure the TrackPoint]] explains how to solve this. The steps you need to follow are in section "Using the X server (kernel 2.6.11+)".
However you don't need to follow the steps in "EmulateWheelTimeout temporarily broken (-> fix for Ubuntu Dapper)" as this is fixed already if you have all your packages up-to-date.

Follow the instructions in the sections "Configure firefox for using trackpoint horizontal scrolling" and "Configure Opera for using trackpoint horizontal scrolling" as well, if you are using one of the two browsers.

If Firefox is scrolling into wrong directions, look at [[Talk:How_to_configure_the_TrackPoint#TrackPoint_scrolling_inverted_in_Firefox]].

===Fingerprint Reader===

[[How to enable the fingerprint reader]] has a good explanation for a very complicated way of activating your fingerprint reader using a restricted driver.

A free alternative to this is available at [http://thinkfinger.sourceforge.net]:
[[How to enable the fingerprint reader with ThinkFinger]] provides more details, also the [https://wiki.ubuntu.com/ThinkFinger Ubuntu wiki] does.

===Special keys ===

If the following standard settings are not enough for you, you'll find more info here: [[How to get special keys to work]]

===={{ibmkey|Access IBM|#495988}} to start application====
The {{ibmkey|Access IBM|#495988}} works out of the box. Just go to your shortcut configuration dialog and choose what action you want to connect with pressing this button, e.g. opening your home folder or the terminal, switching to fullscreen, opening help...

===={{key|CAPS}} to substitute {{key|Win}}/{{key|Super}}====
For using your {{key|CAPS}} key as a replacement for the lacking {{key|Win}}/{{key|Super}} key, add following to your {{path|~/.Xmodmap}}

! No Caps Lock
clear lock
! Caps Lock as Win key
add mod4 = Caps_Lock

To avoid restarting X type {{cmduser|xmodmap ~/.Xmodmap}}

===={{ibmkey|Forward|#494949}}/{{ibmkey|Backward|#494949}} in browsers====

=====Firefox=====
For using the {{ibmkey|Forward|#494949}}/{{ibmkey|Backward|#494949}} Keys in your browser add also these lines to your {{path|~/.Xmodmap}} as at least Firefox gets confused with their original setting as XF86Back/XF86Forward.

! back and forward browser keys
keycode 234 = F19
keycode 233 = F20

For Firefox add these lines to your {{path|/usr/share/firefox/chrome/browser/content/browser/browser.xul}}

<key id="goBackKb3" keycode="VK_F19" command="Browser:Back" />
<key id="goForwardKb3" keycode="VK_F20" command="Browser:Forward" />

directly after these lines:

<key id="goBackKb" keycode="VK_LEFT" command="Browser:Back" modifiers="alt"/>
<key id="goForwardKb" keycode="VK_RIGHT" command="Browser:Forward" modifiers="alt"/>

=====Opera=====
For Opera add these pairs in Tool->Preferences->Advanced->Shortcuts->Keyboard setup->Edit->Browser Window->New
* If you did the Firefox Xmodmap entry: F20-Forward, F19-Back
* If you didn't add the lines: XF86Forward-Forward, XF86Back-Back

=====Konqueror=====
In Konqueror it's working out of the box. But if you did the Xmodmap settings you have to adjust Konqueror, too. Just go to Settings->Configure Shortcuts, look for Back and Forward and set the alternative shortcut in the custom dialog by pressing the respective key. If you are using KDE you'll be probable prefering to do that in the Configuration Center to make these changes visible to all KDE Apps.

===Toggle Touchpad on/off===

Some people like to be able to switch their Touchpad on and off on the fly to avoid touching it during typing or pressing buttons when having the laptop lying on the lap. The following settings make this easily possible.
Add the option "SHMconfig" to your synaptics section in the xorg.conf by typing {{cmduser|sudo gedit /etc/X11/xorg.conf}} and set it to "on":
...
Section "InputDevice"

Driver "synaptics"
...
Option "SHMconfig" "on"

EndSection
...
This makes the synaptics touchpad toggable during runtime. If you prefer the touchpad to be switched off always add following line instead:
Option "TouchpadOff" "1"
To make this setting working we need to restart X. The best choice is to log off your window manager (don't forget to close programs where you might loose data) and press {{key|Ctrl}} + {{key|Alt}} + {{key|Backspace}}.

To switch the touchpad on and off you can use synclient. But if you prefer a program with a nice GUI, try gsynaptics (or ksynaptics if you use KDE):
{{cmduser|sudo apt-get install gsynaptics}}
gsynaptics integrates into your gnome settings menu, ksynaptics in the KDE Control Center. They preety much look the same, ksynaptics seems to just offer one additional setting: to switch your touchpad off automatically when typing. For easier reachability I just added a shortcut to my panel.
To make gnome remember your last settings after a system restart go to your session configuration and add the program gsynaptics-init to the startup programs. I did not try this with KDE, sorry.

Find more information on [[Synaptics TouchPad driver for X]]

===IrDA===

Find information here: [[How to make use of IrDA]]

===VGA out ===

I didn't try it, but it looks easy: [http://help.nceas.ucsb.edu/index.php/Enable_vga_out_on_ATI_Thinkpads How to enable VGA out]

===Swap and Hibernation problem ===

Ubunutu uses unique IDs (UUIDs) to identify partitions. The advantage of this is you do not have to differentiate between sda and hda devices. So if upgrading to modern libata drivers will work without having to rewrite hda devices to sda ones.

However feisty seems to have a problem with this naming method and swap partitions on some installations. Do
{{cmduser|sudo free}} to check if your swap partition is used. If the line with swap it it just returns three times "0", your swap partition is not being used and you are most probably affected by [https://launchpad.net/ubuntu/+bug/66637/ bug 66637]. The problem is that your system generates a new UUID for your swap partition on every reboot. Your old settings in the fstab then cannot be used anymore and your system does not use any swap. Without swap hibernate (suspend to disk) does not work either (standby/suspend to RAM still does).

Follow these instructions to fix this

# determine your swap with {{cmduser|sudo fdisk -l}}. In my case it was /dev/sda2
# do mkswap on your swap partition and record the uuid which this command outputs, e.g. {{cmduser|sudo mkswap /dev/sda2}}
# now use this UUID to put into fstab: Look for the line with the swap partition and replace the old UUID with the new one: {{cmduser|sudo gedit /etc/fstab}}
# add the same UUID intu your resume file: {{cmduser|sudo gedit /etc/initramfs-tools/conf.d/resume}}; the file should only look like this: "RESUME=UUID=<the-swap-partition-uuid>"
# do {{cmduser|update-initramfs -u}}
# update your grub configuration; edit it with {{cmduser|sudo gedit /boot/grub/menu.lst}} and look for the line that says "# defoptions=quiet splash" and change it to "# defoptions=quiet splash resume=<the-swap-partition-uuid>"
# reboot normally. After this test with {{cmduser|sudo free}} or with {{cmduser|swapon -s}} if your swap is now activated
# Now you can test hibernate, too.

Thanks to various people on the bug thread.

===Bluetooth===
I do not need it, so I just switched it off using
:{{cmdroot|echo disable > /proc/acpi/ibm/bluetooth}}

More info on how to use Bluetooth can be found in [[How to setup Bluetooth]],
nice HowTos are available in the [https://help.ubuntu.com/community/BluetoothSetup Ubuntu wiki].

===Bluetooth Mouse and Keyboards===
First identify your wireless mouse or keyboard. Start putting them in pairing mode, and run

:{{cmdroot|sudo hidd --search}}

It should show your device address and hopefully connect it. If does not get connected, or you can't see the address, type:

:{{cmdroot|hcitool scan}}

Then manually connect with:
:{{cmdroot|sudo hidd --connect XX:XX:XX:XX:XX:XX}}
Replacing the XX with your device's address.

If you want the device to be enabled each time you boot, edit your /etc/default/bluetooth (bluez-utils in some distros) with the following:

BLUETOOTH_ENABLED=1

HIDD_ENABLED=1
HIDD_OPTIONS="--master --server"
HIDD_OPTIONS="--connect XX:XX:XX:XX:XX:X --server"

Repeat the --connect line for each device.

More info on how to use Bluetooth can be found in [[How to setup Bluetooth]],
nice HowTos are available in the [https://help.ubuntu.com/community/BluetoothSetup Ubuntu wiki].

==References==
* [[Installing Ubuntu 6.10 on a ThinkPad T43]]

== See also ==
* [[Ubuntu 7.10 on a Thinkpad T43]]

== External links ==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].

Hope this helped :-)
tec

[[Category: T43]] [[Category: Ubuntu 7.04]]

How to protect the harddisk through APS

2007-09-30T07:23:36Z

Mozz: /* Installing hdapsd */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page tells you how to make the [[Active Protection System]] work under Linux to protect your harddrive from damage in case of a notebook drop or other kind of impact while it is running.

Specific instructions for {{Fedora}} can be found [[Installing_Fedora_Core_5_on_a_ThinkPad_X41_Tablet#Harddrive_Active_Protection_System_.28HDAPS.29|here]].

For {{Debian}} (Etch) have a look at [[Installing_Debian_Etch_on_a_ThinkPad_Z60m#Active_Protection_System|this]].

== How APS works in Linux ==
APS in Linux consists of four components on the software side:
* The [[HDAPS]] driver (included in recent kernels). It exports a sysfs interface providing the acceleration values.
* The [http://www.dresco.co.uk/hdaps/ <tt>hdaps_protect</tt>] disk protection kernel patch, which exports a sysfs interface that enables an ide or sata disk to be protected by a userspace process.
* The [http://www.dresco.co.uk/hdaps/ <tt>hdapsd</tt>] disk protection userspace daemon. It monitors the acceleration values through the HDAPS interface and automatically initiates disk protection through the hdaps_protect interface - given that the movement exceeds a user specified threshold.
* Optional: the [http://roy.marples.name/node/269 <tt>khdapsmonitor KDE System Tray applet</tt>] or the [http://www.dresco.co.uk/hdaps/ <tt>gnome-hdaps-applet</tt>]. These applets provide a visual indication of the disk protection status and also a graphical interface for adjusting configuration options for <tt>hdapsd</tt>.
|}

==Installation==
As mentioned above, the hdaps kernel driver found in recent kernels is only responsible for reading the accelerometer data and exporting it through the sysfs interface.

In order to use this information to protect the disk, some additional steps are required.

* Download and build the latest hdaps_protect disk protection kernel patches.
* Enable the drivers in the kernel (requires kernel rebuild).
* Download, build and configure the hdapsd userspace daemon.
* Download and build one of the applets to get a real-time representation of the disk protection status.

===Getting the files===
{| border="1" cellspacing="0" cellpadding="2"
! Latest Sources
|
See [[HDAPS#Disk_head_parking|HDAPS - Disk head parking]]
|-
! {{Debian}}
|
*<tt>hdapsd</tt> package: http://packages.debian.org/unstable/misc/hdapsd
|-
! {{Fedora}}
| see instructions [[Installing_Fedora_Core_5_on_a_ThinkPad_X41_Tablet#Harddrive_Active_Protection_System_.28HDAPS.29|here]]
*kernel RPM packages including <tt>hdaps_protect</tt>: http://www.dresco.co.uk/hdaps/
*kernel RPM packages including <tt>hdaps_protect</tt> and [[Software Suspend 2]]: http://mhensler.de/swsusp/download/yum/development/fc5/ (build 2084_2 and up)
|-
! {{Gentoo}}
|
*<tt>hdapsd</tt>: [http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-laptop/hdapsd available]
*<tt>khdapsmonitor</tt>: [http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-laptop/khdapsmonitor available]
|}

=== Adding kernel support ===
A kernel patch is required for disk head parking and queue freezing.

==== Manually patching and compiling a kernel ====
As root, do:
:{{cmdroot|cd /usr/src/linux}}
:{{cmdroot|patch -p1 < ~/hdaps_protect.20060409.patch}}
:{{cmdroot|make clean}}
:{{cmdroot|make}}
:{{cmdroot|make modules_install}}

=== Installing hdapsd ===
==== Manual compilation from source ====
{{NOTE|1=There has been a new release of hdapsd which doesn't use sysfs anymore and therefore reduces timer interrupts. You need tp_smapi 0.32 for this. See also: http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1040 .}}
* Download the <tt>hdapsd</tt> sources (see above)
* Compile using {{cmdroot|gcc -o hdapsd hdapsd-*.c}}
* Run {{cmdroot|./hdapsd -d sda -s 12 -a}} (replace <tt>sda</tt> with your hard disk device; run {{cmdroot|./hdapsd}} without arguments for help)

==== Gentoo ====
{{NOTE|1=hdapsd was added to the official portage tree on the 26th June 2006.}}
{{Gentoo}} users can try the ebuild attached to [http://bugs.gentoo.org/show_bug.cgi?id=119845 gentoo bug 119845].
*Add hdapsd support in your kernel: device drivers -> hardware monitoring -> ... (you need it as a module if you want to use tp_smapi and hdaps, see [[Tp_smapi]])
*Download the ebuild, use same ebuild date as the kernel-patch.
*Make known the portage an extern ebuild path and add the following line to {{path|/etc/make.conf}}:
PORTDIR_OVERLAY="/usr/local/portage/" (or any other location)
*Create directory {{path|/usr/local/portage}} and {{path|/usr/local/portage/app-laptop/}}
*Copy the downloaded ebuild to {{path|/usr/local/portage/app-laptop}} ({{path|/usr/local/portage/app-laptop/hdapsd}} should now exists)
*Make portage known the new ebuild and creat digist with:
:{{cmdroot|ebuild /usr/local/portage/app-laptop/hdapsd/hdapsd-20060326.ebuild digest}}
*Optional: Copy source file to portage distfiles (if no internet connection is available):
:{{cmdroot|cp hdapsd-20060326.c /usr/portage/distfiles}}
*Accept the x86 keyword for this package: {{cmdroot|echo "app-laptop/hdapsd ~x86" >> /etc/portage/package.keywords}}
*Install hdapsd with: {{cmdroot|emerge hdapsd}}.
*Edit {{path|/etc/conf.d/hdapsd}} (change your harddrive if neccessary: mine is sda, and change the value from 5, 5 is to sensitive, 12 is a good value in my opinion).
*start deamon with: {{cmdroot|/etc/init.d/hdapsd start}}
*Optional: add to default runlevel: {{cmdroot|rc-update add hdapsd default, rc-update add hdapsd battery}}
Write an eMail to abartel[Ã¤d]htwm.de, if you want to get my hdapsd-20060326.ebuild and please upload it.

=== Building an applet ===
====hdaps-gl====
*Make sure you have installed hdaps [and loaded] and ?opengl?
*Download <tt>hdaps-gl-0.0.5</tt> from the web.
*Extract files to {{path|/opt/hdaps-gl}}.
*{{cmdroot|make}}
*Start the applet: {{cmdroot|./hdaps-gl}}

==Troubleshooting==
See the [[Problem with APS harddisk parking]] page for troubleshooting APS issues.
{{NOTE|1=If you use [[tp_smapi]], remember to include the option <tt>HDAPS=1</tt> when [[Tp_smapi#Installation|installing tp_smapi]]. Also, you might need to build the hdaps driver as module.}}

==Further Information==
*Additonal information and support is available through the [[Mailinglists#HDAPS Developers Mailinglist|hdaps-devel]] mailinglist and its archive.

[[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61m]] [[Category:Z61e]] [[Category:Z61m]]

Problem with video output switching

2007-09-03T17:56:15Z

Mozz: /* Affected Models */

==Affected Models==
*ThinkPad {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T61}}
*ThinkPad {{X22}}, {{X23}}, {{X31}}, {{X41}}, {{X60s}}

==Problem Description==
External video output is not working, or it is not possible, using the FN-F7 key, to switch between the LCD and the external monitor in the following way:
LCD --> external Monitor--> both -->LCD
However ''cloning'' is possible for the Intel chipsets, see below.

===Problems with Intel chipsets===
Disabling the internal LCD (e.g. when using an external Monitor) doesn't seem to work reliably.

* For Xorg 7.022 one can clone the LCD display to an external monitor, adding the following lines to the Device section in the xorg.conf file:
Section "Device"
Identifier "Generic Video Card"
Driver "i810"
Option "Clone" "true"
Option "MonitorLayout" "CRT,LFP"
however you can not switch between these screens as described above, once you use FN-F7 the cloned display is lost.

* i810switch doesn't have any effect. After disabling the LCD it is still on (but the status display of i810switch claims that is is switched off).

* The following works with Fedora Core 6 on an {{X60s}} and CentOS 5 on {{X60}}: i810switch 0.6.5 with the patch found on http://thpinfo.com/2006/patches/i810switch_macbook_support.patch can switch between LCD and CRT (and initially CRT is off) (NOTE: The first hunk of this patch does not apply to the source, just remove it, it is unnecessary). This patch makes i810switch recognize the i915 chipset. It should thus be doable to use this with an ACPI event/action to do {{key|Fn}}{{key|F7}} switching. After installing i810switch and its i810rotate script and the missing [[ibm-acpi]] kernel module I did the following to achieve just that:

In /etc/rc.local:
modprobe ibm_acpi
echo enable,0x084c > /proc/acpi/ibm/hotkey

in /etc/acpi/events/videoswitch.conf:
event=ibm/hotkey HKEY 00000080 00001007
action=/etc/acpi/actions/video-rotate.sh

Make sure the event code is correct. If acpid doesn't seem to recognise the event, try to recopy it from acpi log.

in /etc/acpi/actions/video-rotate.sh
#!/bin/bash
exec /usr/sbin/i810rotate

* i855crt works see: http://stefan.desire.ch/howto/x41debian/#graphics for details.

* With [[ibm-acpi]], {{cmdroot|echo lcd_disable >/proc/acpi/ibm/video}} works, but {{cmdroot|echo lcd_enable >/proc/acpi/ibm/video}} doesn't work - so one can't enable it anymore after disabling it. (the strange thing is that when switching to a console with {{key|ctrl}}{{key|alt}}{{key|F1}} the LCD display is used for it, so there must be some way to enable it but I can't find out how to control this in X). I've tried this with version 0.8 and version 0.11 of [[ibm-acpi]].
** {{key|Fn}}{{key|F7}} lets me enable the internal LCD after I disabled it with {{cmdroot|echo lcd_disable >/proc/acpi/ibm/video}} on my X41 but it corrupts the crt out

===Problems with ATI chipsets===
*It is a [http://bugs.freedesktop.org/show_bug.cgi?id=2000 known issue] of xorgs radeon driver that {{key|Fn}}{{key|F7}} doesn't work.

You can force the <tt>radeon</tt> driver to enable both CRT and LCD using <tt>Option "MonitorLayout" "LVDS,CRT"</tt> in the <tt>"Device"</tt> section of {{path|/etc/X11/xorg.conf}}. The analogous option for [[fglrx]] is <tt>Option "ForceMonitors" "lvds,crt1"</tt>

The {{cmdroot|radeontool light off}} and {{cmdroot|radeontool dac off}} commands will disable the LCD and CRT if they're been enabled before in the X server, but the corresponding {{cmdroot|radeontool light on}} and {{cmdroot|radeontool dac on}} will not work if the displays have were not enabled when the X server started. Also note that turing off the CRT using this command will not reduce power consumption, nor allow [[fglrx]] to enable power saving modes.

You might try the following: Hit Ctrl+Alt+F1 to switch to a console, hit Fn+F7 to switch video, hit Alt+F7 to switch back to X.

* Similar problems exist with XFree86 4.3 and its radeon driver

You '''can''' switch the display off after switching to tty1 (STRG+ALT+F1) by
* pressing FN+F7 or
* executing ''echo crt_disable > /proc/acpi/ibm/video'' as root

You '''cannot''' do this under X11. The display is always on under X11. I tried
* ''echo auto_disable > /proc/acpi/ibm/video''
* ''echo crt_disable > /proc/acpi/ibm/video''
* ''echo lcd_disable > /proc/acpi/ibm/video''
* pressing FN+F7

but none of the above had any effect. If you switch the display off, then start X or switch to it, the display
will be activated automatically.

====fglrx-Driver====
Output switching with the Closed-Source ati-driver works: Just use {{cmdroot|aticonfig --query-monitor}} and e.g. {{cmdroot |aticonfig --enable-monitor..."}}. You can use those two commands in a script, and bind them to {{key|Fn}}{{key|F7}}

----

Alternative solution: {{path|fglrx}} 8.28.8 will recognize {{key|Fn}}{{key|F7}} directly, if the key is enabled. This obviates the need for scripts which call aticonfig. To enable the hotkey, issue the command {{cmdroot|echo enable,0xffff >/proc/acpi/ibm/hotkey}}. You'll want to have this run both at boot time, and after resume (on my T43, the hotkey mask is reset on resume). For Ubuntu, I've put a script with the command in both the {{path|/etc/acpi/resume.d}}, and {{path|/etc/acpi/start.d}} directories.

----

Using kubuntu 7.04 with xorg-driver-fglrx 7.1.0-8.34.8+2.6.20.5-16.29, fglrx failed to recognise {{key|Fn}}{{key|F7}}. However the following scripts can be used with acpi. Tested on a T42p.

* /etc/acpi/events/ibmvideobtn
# /etc/acpi/events/ibmvideobtn
# This is called when the user presses the video button.
event=ibm/hotkey HKEY 00000080 00001007
action=/etc/acpi/ibm-video.sh

* /etc/acpi/ibm-video.sh
#!/bin/sh

# ACPI Scripts run as root, but the display will not allow access
# from other users.
# Lookup the X process for :0, find the -auth command line option,
# extract the name of the authority file and use this file
# to gain access to the DISPLAY
export XAUTHORITY=`ps -ef | grep /usr/bin/X | grep :0 | grep -v grep | \
awk -F' -' '{for (i=1; i<=NF; i++) if (substr($i, 0, 4)=="auth") print $i}' \
| awk '{print $2}'`

export DISPLAY=:0

# Query current monitor setup
# Expect output from aticonfig such as:
# Connected monitors: crt1, lvds
# Enabled monitors: crt1
#
current=`aticonfig --query-monitor | tail -1 | awk -F: '{print $2}' | cut -c2-`

# Cycle round to next monitor setup.
# We loop through these settings
# 1. CRT
# 2. LCD
# 3. CRT and LCD
echo Current video: $current

case $current in
crt1)
echo Switching to LCD
aticonfig --enable-monitor=lvds
;;
lvds)
echo Switching to both LCD and CRT
aticonfig --enable-monitor=crt1,lvds
;;
"crt1, lvds")
echo Switching to CRT
aticonfig --enable-monitor=crt1
;;
*)
# Unexpected current monitor, change to internal LCD
echo Unknown current mode, switching to LCD
aticonfig --enable-monitor=lvds
esac

====VESA driver====

I have fixed the problem on my T42 by switching to the generic VESA driver in xorg.conf, and rebooting, as mentioned on the xorg bug page above. None of the other solutions worked.

==Related Links==
*https://bugs.freedesktop.org/show_bug.cgi?id=2000

==Solutions==

====BIOSHotKeys====

Try adding
Option "BiosHotKeys" "on"
to "Device" selection in /etc/xorg.conf. For some reason, this is not the default, and will cause xorg to ignore the BIOS's request to switch modes!
This fixes the problem for an X22, with xorg 6.9.0.

It fixed this problem for a X31 with xorg 7.1.1 too, but as the CRT is the primary display in some Thinkpads (like in the X31), you can not switch back to the LCD (or both) if xorg has started with the CRT only or both mode, because it sets the resolution and or refresrate to high for the LCD.

AD1984

2007-08-07T17:13:58Z

Mozz: /* Linux ALSA driver */

__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;">
=== AD1984 ===
This is a ''Analog Devices'' High-Definition Audio controller

=== Features ===
* Chipset: AD1984
* Interface: HD Audio
</div>
|style="vertical-align:top" |
|}

=== Linux ALSA driver ===
This device isn't supported by current Alsa Driver [http://www.alsa-project.org/alsa-doc/index.php?vendor=vendor-Analog_Devices#matrix] (as of May 25, 2007).

However, Takashi Iwai has added support to this device in Alsa development version [http://hg.alsa-project.org/alsa-kernel/log?rev=AD1984]... Still have to wait to get it included in the Linux Kernel... Note: It is rather trivial too get this working in a standard kernel right now, It is only 3 patches on top of the stock 1.0.14 code:

* [http://hg.alsa-project.org/alsa-kernel/rev/958b39f3e8dd Fix Oops with AD1984 thinkpad model]
* [http://hg.alsa-project.org/alsa-kernel/rev/47ca87407c84 Fix AD1984 basic model]
* [http://hg.alsa-project.org/alsa-kernel/rev/ca37aeeeb0ea Fix Thinkpad X61/T61 outputs]

Alsa-Driver 1.0.14 added some support for this chip, but did not work on my T61; however, using the latest HG/Mercurial makes everything work. I created a Debian package for unstable/sid with the HG alsa that works for me, available at [http://people.debian.org/~jello/alsa-modules-2.6.21-2-686_1.0.15~hg2007070601-1+2.6.21-5_i386.deb]. --[[User:Jello|Jello]] 15:31, 6 July 2007 (UTC)

Works with Kernel 2.6.22 and Alsa 1.0.14a
--[[User:Schlodty|Schlodty]] 12:01, 21 July 2007 (UTC)

Did not get it to work on X61s with either of the above packages. Newer HG packages do support this chip, so alsa 1.0.15 should have full support for this chip. --[[User:hjh|hjh]] 9:09, 27 July 2007 (UTC)

Debian users (both Stable/Etch and Testing) can use the small script [http://www.klabs.be/~fpiat/linux/debian/Lenny_on_Thinkpad_T61/#Sound 1] i wrote to patch and build an alsa module package (with module-assistant). --[[User:Fpiat|Fpiat]] 11:45,04 August 2007 (UTC)

Works with a patched 2.6.22.1 kernel using the 2007/07/20 patch from ftp://ftp.alsa-project.org/pub/kernel-patches/ . Just make sure that you have the PCM channel unmuted and the speaker switch checked. --[[User:Mozz|Mozz]] 17:13, 7 August 2007 (UTC)

=== Trouble shooting ===
{{WARN|It's really necessary to leave the modem enabled in the BIOS or the intel_hda-driver will reutrn azx_get_response timeouts which will lead to a non-working soundchip.
Got that information from a comment from: [http://crypto.riken.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/git-alsa.patch here] --[[User:Gladiac|Gladiac]] 06:12, 24 July 2007 (UTC)}}

=== This chip may be found in ===
* {{R61}}
* {{T61}}
* [[:Category:X61|X61]], [[:Category:X61s|X61s]]

=== Datasheets ===
* [http://www.analog.com/en/prod/0,2877,AD1984,00.html Analog Devices page for the AD1984]

[[Category:Components]]

AD1984

2007-08-07T17:11:42Z

Mozz: /* Linux ALSA driver */

__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;">
=== AD1984 ===
This is a ''Analog Devices'' High-Definition Audio controller

=== Features ===
* Chipset: AD1984
* Interface: HD Audio
</div>
|style="vertical-align:top" |
|}

=== Linux ALSA driver ===
This device isn't supported by current Alsa Driver [http://www.alsa-project.org/alsa-doc/index.php?vendor=vendor-Analog_Devices#matrix] (as of May 25, 2007).

However, Takashi Iwai has added support to this device in Alsa development version [http://hg.alsa-project.org/alsa-kernel/log?rev=AD1984]... Still have to wait to get it included in the Linux Kernel... Note: It is rather trivial too get this working in a standard kernel right now, It is only 3 patches on top of the stock 1.0.14 code:

* [http://hg.alsa-project.org/alsa-kernel/rev/958b39f3e8dd Fix Oops with AD1984 thinkpad model]
* [http://hg.alsa-project.org/alsa-kernel/rev/47ca87407c84 Fix AD1984 basic model]
* [http://hg.alsa-project.org/alsa-kernel/rev/ca37aeeeb0ea Fix Thinkpad X61/T61 outputs]

Alsa-Driver 1.0.14 added some support for this chip, but did not work on my T61; however, using the latest HG/Mercurial makes everything work. I created a Debian package for unstable/sid with the HG alsa that works for me, available at [http://people.debian.org/~jello/alsa-modules-2.6.21-2-686_1.0.15~hg2007070601-1+2.6.21-5_i386.deb]. --[[User:Jello|Jello]] 15:31, 6 July 2007 (UTC)

Works with Kernel 2.6.22 and Alsa 1.0.14a
--[[User:Schlodty|Schlodty]] 12:01, 21 July 2007 (UTC)

Did not get it to work on X61s with either of the above packages. Newer HG packages do support this chip, so alsa 1.0.15 should have full support for this chip. --[[User:hjh|hjh]] 9:09, 27 July 2007 (UTC)

Debian users (both Stable/Etch and Testing) can use the small script [http://www.klabs.be/~fpiat/linux/debian/Lenny_on_Thinkpad_T61/#Sound 1] i wrote to patch and build an alsa module package (with module-assistant). --[[User:Fpiat|Fpiat]] 11:45,04 August 2007 (UTC)

Works with a patched 2.6.22.1 kernel using the 2007/07/20 patch from ftp://ftp.alsa-project.org/pub/kernel-patches/ . Just make sure that you have the PCM channel unmuted and the speaker switch checked.

=== Trouble shooting ===
{{WARN|It's really necessary to leave the modem enabled in the BIOS or the intel_hda-driver will reutrn azx_get_response timeouts which will lead to a non-working soundchip.
Got that information from a comment from: [http://crypto.riken.go.jp/archives/linux/kernel.org/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/git-alsa.patch here] --[[User:Gladiac|Gladiac]] 06:12, 24 July 2007 (UTC)}}

=== This chip may be found in ===
* {{R61}}
* {{T61}}
* [[:Category:X61|X61]], [[:Category:X61s|X61s]]

=== Datasheets ===
* [http://www.analog.com/en/prod/0,2877,AD1984,00.html Analog Devices page for the AD1984]

[[Category:Components]]