https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=Ylai&feedformat=atomThinkWiki - User contributions [en]2024-03-28T21:45:22ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=Intel_Core_2_Duo_(Merom)&diff=36104Intel Core 2 Duo (Merom)2008-01-19T10:37:07Z<p>Ylai: /* Note on Hyperthreading */ sp</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
===Intel Core 2 Duo ===<br />
The Intel 2 Core is the successor of the [[Intel Core Duo (Yonah)]] processor. Even if the name seems like a second version, the Core 2 Duo is "only" a mobile version of the desktop processor with the same name and not designed for mobile applications in the first place like its predecessor. The architecture is changed in many ways, which introduced EM64T, [[SIMD|SSSE3]] and improved the performance by up to 25 percent. The 667 MHz FSB versions are part of the "Napa"- and the 800MHz FSB versions of the "Santa Rosa"-platform. It is part of the hardware from both the Centrino Duo and Centrino Pro brands.<br />
<br />
===Features===<br />
*Dual Core<br />
*EM64T<br />
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_VT_.28IVT.29 Intel Virtualization Technology]<br />
*XD-Bit<br />
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]], [[SIMD|SSSE3]] instruction sets<br />
*667 or 800 MHz FSB<br />
*65 nm fabrication process<br />
*4 MB or 2 MB L2-Cache with dynamic cache sizing<br />
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), [[QuickStart and Deeper Sleep|Deeper Sleep]] (C4)<br />
</div><br />
|}<br />
<br />
==Available Types and ThinkPads featuring them==<br />
===Standard Voltage===<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models<br />
|- style="background:#ffdead;"<br />
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !! <br />
|-<br />
| T7800 || 2600 || 1000 || 4MB || 800 || yes || 1.30 || ? || 35 || ? || {{T61p}}<br />
|-<br />
| T7700 || 2400 || 1000 || 4MB || 800 || yes || 1.30 || ? || 35 || ? || {{R61}}, {{T61}}<br />
|-<br />
| T7600 || 2333 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}}, {{T60p}}<br />
|-<br />
| T7500 || 2200 || 1000 || 4MB || 800 || yes || 1.30 || ? || 35 || ? || {{R61}}, {{T61}}, {{X61}}<br />
|-<br />
| T7400 || 2166 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}}, {{Z61t}}<br />
|-<br />
| T7300 || 2000 || 1000 || 4MB || 800 || yes || 1.30 || 0.95 || 35 || ? || {{R61}}, {{T61}}, {{X61}}<br />
|-<br />
| T7200 || 2000 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61m}}, {{Z61t}}<br />
|-<br />
| T7100 || 1800 || 1000 || 2MB || 800 || yes || ? || ? || 35 || ? || {{R61}}, {{T61}}<br />
|-<br />
| T5600 || 1833 || 1000 || 2MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61t}}<br />
|-<br />
| T5500 || 1666 || 1000 || 2MB || 667 || no || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61m}}, {{Z61t}}<br />
|}<br />
<br />
===Low Voltage===<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models<br />
|- style="background:#ffdead;"<br />
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !! <br />
|-<br />
| L7400 || 1500 || 1000 || 4MB || 667 || yes || 1.2 || 0.9 || 17 || ? || {{X60s}}, {{X60_Tablet}}<br />
|-<br />
| L7500 || 1600 || 800 || 4MB || 800 || yes || 1.1 || 0.9 || 17 || ? || {{X61s}}, {{X61_Tablet}}<br />
|-<br />
| L7700 || 1800 || 800 || 4MB || 800 || yes || 1.1 || 0.9 || 17 || ? || {{X61s}}, {{X61_Tablet}}<br />
|}<br />
<br />
==Thermal Specifications==<br />
The maximum temperature for safe operation is 100°C.<br />
<br />
The catastrophic thermal protection temperature is 125°C.<br />
<br />
==GCC Optimization Flags==<br />
<br />
==Intel Compiler Optimization Flags==<br />
For the [http://www.spec.org/cpu2006/ SPEC CPU 2006 benchmarks], Intel used the shorthand <code>-fast</code>, which translates into <code>-O3 -ipo -static -no-prec-div -xP</code>. However, the compiler also provides the flag <code>-xT</code>, which activates the optimization for Core 2 Duo and SSSE3 (instead of SSE3 only with <code>-xP</code>).<br />
<br />
==Note on Hyper-Threading==<br />
Note that as opposed to Pentium 4/NetBurst, current Core 2 do not support hyper-threading, and therefore there is usually no option in the BIOS to activate it. Refer to Intel's [http://www.intel.com/products/ht/hyperthreading_more.htm Hyper-Threading Technology] for a list of hyper-threading capable CPU.<br />
<br />
==See also==<br />
[[Intel_Core_Solo_(Yonah)|Intel Core Solo (Yonah)]]<br />
<br />
[[Intel Core Duo (Yonah)]]<br />
<br />
==Links==<br />
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]<br />
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]<br />
[[Category:Components]]</div>Ylaihttps://www.thinkwiki.org/w/index.php?title=Intel_Core_2_Duo_(Merom)&diff=36103Intel Core 2 Duo (Merom)2008-01-19T10:36:23Z<p>Ylai: /* Intel Compiler Optimization Flags */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
===Intel Core 2 Duo ===<br />
The Intel 2 Core is the successor of the [[Intel Core Duo (Yonah)]] processor. Even if the name seems like a second version, the Core 2 Duo is "only" a mobile version of the desktop processor with the same name and not designed for mobile applications in the first place like its predecessor. The architecture is changed in many ways, which introduced EM64T, [[SIMD|SSSE3]] and improved the performance by up to 25 percent. The 667 MHz FSB versions are part of the "Napa"- and the 800MHz FSB versions of the "Santa Rosa"-platform. It is part of the hardware from both the Centrino Duo and Centrino Pro brands.<br />
<br />
===Features===<br />
*Dual Core<br />
*EM64T<br />
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_VT_.28IVT.29 Intel Virtualization Technology]<br />
*XD-Bit<br />
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]], [[SIMD|SSSE3]] instruction sets<br />
*667 or 800 MHz FSB<br />
*65 nm fabrication process<br />
*4 MB or 2 MB L2-Cache with dynamic cache sizing<br />
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), [[QuickStart and Deeper Sleep|Deeper Sleep]] (C4)<br />
</div><br />
|}<br />
<br />
==Available Types and ThinkPads featuring them==<br />
===Standard Voltage===<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models<br />
|- style="background:#ffdead;"<br />
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !! <br />
|-<br />
| T7800 || 2600 || 1000 || 4MB || 800 || yes || 1.30 || ? || 35 || ? || {{T61p}}<br />
|-<br />
| T7700 || 2400 || 1000 || 4MB || 800 || yes || 1.30 || ? || 35 || ? || {{R61}}, {{T61}}<br />
|-<br />
| T7600 || 2333 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}}, {{T60p}}<br />
|-<br />
| T7500 || 2200 || 1000 || 4MB || 800 || yes || 1.30 || ? || 35 || ? || {{R61}}, {{T61}}, {{X61}}<br />
|-<br />
| T7400 || 2166 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}}, {{Z61t}}<br />
|-<br />
| T7300 || 2000 || 1000 || 4MB || 800 || yes || 1.30 || 0.95 || 35 || ? || {{R61}}, {{T61}}, {{X61}}<br />
|-<br />
| T7200 || 2000 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61m}}, {{Z61t}}<br />
|-<br />
| T7100 || 1800 || 1000 || 2MB || 800 || yes || ? || ? || 35 || ? || {{R61}}, {{T61}}<br />
|-<br />
| T5600 || 1833 || 1000 || 2MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61t}}<br />
|-<br />
| T5500 || 1666 || 1000 || 2MB || 667 || no || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61m}}, {{Z61t}}<br />
|}<br />
<br />
===Low Voltage===<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models<br />
|- style="background:#ffdead;"<br />
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !! <br />
|-<br />
| L7400 || 1500 || 1000 || 4MB || 667 || yes || 1.2 || 0.9 || 17 || ? || {{X60s}}, {{X60_Tablet}}<br />
|-<br />
| L7500 || 1600 || 800 || 4MB || 800 || yes || 1.1 || 0.9 || 17 || ? || {{X61s}}, {{X61_Tablet}}<br />
|-<br />
| L7700 || 1800 || 800 || 4MB || 800 || yes || 1.1 || 0.9 || 17 || ? || {{X61s}}, {{X61_Tablet}}<br />
|}<br />
<br />
==Thermal Specifications==<br />
The maximum temperature for safe operation is 100°C.<br />
<br />
The catastrophic thermal protection temperature is 125°C.<br />
<br />
==GCC Optimization Flags==<br />
<br />
==Intel Compiler Optimization Flags==<br />
For the [http://www.spec.org/cpu2006/ SPEC CPU 2006 benchmarks], Intel used the shorthand <code>-fast</code>, which translates into <code>-O3 -ipo -static -no-prec-div -xP</code>. However, the compiler also provides the flag <code>-xT</code>, which activates the optimization for Core 2 Duo and SSSE3 (instead of SSE3 only with <code>-xP</code>).<br />
<br />
==Note on Hyperthreading==<br />
Note that as opposed to Pentium 4/NetBurst, current Core 2 do not support hyper-threading, and therefore there is usually no option in the BIOS to activate it. Refer to Intel's [http://www.intel.com/products/ht/hyperthreading_more.htm Hyper-Threading Technology] for a list of hyper-threading capable CPU.<br />
<br />
==See also==<br />
[[Intel_Core_Solo_(Yonah)|Intel Core Solo (Yonah)]]<br />
<br />
[[Intel Core Duo (Yonah)]]<br />
<br />
==Links==<br />
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]<br />
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]<br />
[[Category:Components]]</div>Ylaihttps://www.thinkwiki.org/w/index.php?title=Intel_Core_2_Duo_(Merom)&diff=36102Intel Core 2 Duo (Merom)2008-01-19T10:33:51Z<p>Ylai: Intel Compiler, HT</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
===Intel Core 2 Duo ===<br />
The Intel 2 Core is the successor of the [[Intel Core Duo (Yonah)]] processor. Even if the name seems like a second version, the Core 2 Duo is "only" a mobile version of the desktop processor with the same name and not designed for mobile applications in the first place like its predecessor. The architecture is changed in many ways, which introduced EM64T, [[SIMD|SSSE3]] and improved the performance by up to 25 percent. The 667 MHz FSB versions are part of the "Napa"- and the 800MHz FSB versions of the "Santa Rosa"-platform. It is part of the hardware from both the Centrino Duo and Centrino Pro brands.<br />
<br />
===Features===<br />
*Dual Core<br />
*EM64T<br />
*[http://en.wikipedia.org/wiki/Vanderpool#Intel_VT_.28IVT.29 Intel Virtualization Technology]<br />
*XD-Bit<br />
*[[SIMD|MMX]], [[SIMD|SSE]], [[SIMD|SSE2]], [[SIMD|SSE3]], [[SIMD|SSSE3]] instruction sets<br />
*667 or 800 MHz FSB<br />
*65 nm fabrication process<br />
*4 MB or 2 MB L2-Cache with dynamic cache sizing<br />
*[[SpeedStep|Enhanced Intel SpeedStep (EIST)]], power states: normal (C0), AutoHALT/MWAIT (C1), Stop Grant (C2), Deep Sleep (C3), [[QuickStart and Deeper Sleep|Deeper Sleep]] (C4)<br />
</div><br />
|}<br />
<br />
==Available Types and ThinkPads featuring them==<br />
===Standard Voltage===<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models<br />
|- style="background:#ffdead;"<br />
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !! <br />
|-<br />
| T7800 || 2600 || 1000 || 4MB || 800 || yes || 1.30 || ? || 35 || ? || {{T61p}}<br />
|-<br />
| T7700 || 2400 || 1000 || 4MB || 800 || yes || 1.30 || ? || 35 || ? || {{R61}}, {{T61}}<br />
|-<br />
| T7600 || 2333 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}}, {{T60p}}<br />
|-<br />
| T7500 || 2200 || 1000 || 4MB || 800 || yes || 1.30 || ? || 35 || ? || {{R61}}, {{T61}}, {{X61}}<br />
|-<br />
| T7400 || 2166 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{T60}}, {{Z61t}}<br />
|-<br />
| T7300 || 2000 || 1000 || 4MB || 800 || yes || 1.30 || 0.95 || 35 || ? || {{R61}}, {{T61}}, {{X61}}<br />
|-<br />
| T7200 || 2000 || 1000 || 4MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61m}}, {{Z61t}}<br />
|-<br />
| T7100 || 1800 || 1000 || 2MB || 800 || yes || ? || ? || 35 || ? || {{R61}}, {{T61}}<br />
|-<br />
| T5600 || 1833 || 1000 || 2MB || 667 || yes || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61t}}<br />
|-<br />
| T5500 || 1666 || 1000 || 2MB || 667 || no || 1.30 || 0.95 || 34 || 20 || {{R60}}, {{T60}}, {{X60}}, {{Z61m}}, {{Z61t}}<br />
|}<br />
<br />
===Low Voltage===<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Nr. || colspan=2 | Frequency (MHz) || L2 Cache || FSB (MHz)|| VT || colspan=2 | core Voltage (V) || colspan=2 | TDP (W) || ThinkPad Models<br />
|- style="background:#ffdead;"<br />
! !!max. !! min. !! !! !! !! high !! low !! high freq !! low freq !! <br />
|-<br />
| L7400 || 1500 || 1000 || 4MB || 667 || yes || 1.2 || 0.9 || 17 || ? || {{X60s}}, {{X60_Tablet}}<br />
|-<br />
| L7500 || 1600 || 800 || 4MB || 800 || yes || 1.1 || 0.9 || 17 || ? || {{X61s}}, {{X61_Tablet}}<br />
|-<br />
| L7700 || 1800 || 800 || 4MB || 800 || yes || 1.1 || 0.9 || 17 || ? || {{X61s}}, {{X61_Tablet}}<br />
|}<br />
<br />
==Thermal Specifications==<br />
The maximum temperature for safe operation is 100°C.<br />
<br />
The catastrophic thermal protection temperature is 125°C.<br />
<br />
==GCC Optimization Flags==<br />
<br />
==Intel Compiler Optimization Flags==<br />
For the [http://www.spec.org/cpu2006/ SPEC CPU 2006 benchmarks], Intel used the shorthand <code>-fast</code>, which translates into <code>-O3 -ipo -static -no-prec-div -xP</code>. However, the compiler also provide <code>-xT</code>, which activates optimization for Core 2 Duo and SSSE3 (instead of SSE3 only with <code>-xP</code>).<br />
<br />
==Note on Hyperthreading==<br />
Note that as opposed to Pentium 4/NetBurst, current Core 2 do not support hyper-threading, and therefore there is usually no option in the BIOS to activate it. Refer to Intel's [http://www.intel.com/products/ht/hyperthreading_more.htm Hyper-Threading Technology] for a list of hyper-threading capable CPU.<br />
<br />
==See also==<br />
[[Intel_Core_Solo_(Yonah)|Intel Core Solo (Yonah)]]<br />
<br />
[[Intel Core Duo (Yonah)]]<br />
<br />
==Links==<br />
*[http://www.intel.com/products/processor_number/chart/core2duo.htm Intel - Processor Numbers and Features]<br />
*[http://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Mobile_processors Wikipedia - Intel Core 2 mobile microprocessors]<br />
[[Category:Components]]</div>Ylaihttps://www.thinkwiki.org/w/index.php?title=NVIDIA_Quadro_NVS_140M&diff=31391NVIDIA Quadro NVS 140M2007-07-19T22:32:13Z<p>Ylai: /* CUDA */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== NVIDIA Quadro NVS 140M ===<br />
<br />
The NVIDIA Quadro NVS 140M is a mobile video card with a G86 core and either 128 MB or 256 MB graphics memory.<br />
<br />
=== Features ===<br />
<br />
* Chipset: nVidia Quadro NVS 140M<br />
* PCI ID:<br />
** 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0429 (rev a1) (prog-if 00 [VGA])<br />
*** Subsystem: Lenovo Unknown device 20d8<br />
*** Flags: bus master, fast devsel, latency 0, IRQ 169<br />
*** Memory at d6000000 (32-bit, non-prefetchable) [size=16M]<br />
*** Memory at e0000000 (64-bit, prefetchable) [size=256M]<br />
*** Memory at d4000000 (64-bit, non-prefetchable) [size=32M]<br />
*** I/O ports at 2000 [size=128]<br />
*** Capabilities: [60] Power Management version 2<br />
*** Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-<br />
*** Capabilities: [78] Express Endpoint IRQ 0<br />
*** Capabilities: [100] Virtual Channel<br />
*** Capabilities: [128] Power Budgeting<br />
*** Capabilities: [600] Unknown (11)<br />
* PCI Express 16&times;<br />
* 128 or 256 MB video memory<br />
<br />
=== Linux X.Org driver ===<br />
<br />
Default X.Org NVidia driver, called "nv" works.<br />
<br />
=== NVIDIA proprietary driver ===<br />
<br />
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.<br />
<br />
==== CUDA ====<br />
<br />
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.<br />
<br />
=== LCD Backlight Brightness Control on T61 ===<br />
<br />
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}} 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. <br />
<br />
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. This was tested with the acpi video driver included in the vanilla Linux 2.6.21-6 kernel.<br />
<br />
[[Category:Components]]</div>Ylaihttps://www.thinkwiki.org/w/index.php?title=NVIDIA_Quadro_NVS_140M&diff=31383NVIDIA Quadro NVS 140M2007-07-19T19:06:26Z<p>Ylai: cat, PCI ID</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== NVIDIA Quadro NVS 140M ===<br />
<br />
The NVIDIA Quadro NVS 140M is a mobile video card with a G86 core and either 128 MB or 256 MB graphics memory.<br />
<br />
=== Features ===<br />
<br />
* Chipset: nVidia Quadro NVS 140M<br />
* PCI ID:<br />
** 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0429 (rev a1) (prog-if 00 [VGA])<br />
*** Subsystem: Lenovo Unknown device 20d8<br />
*** Flags: bus master, fast devsel, latency 0, IRQ 169<br />
*** Memory at d6000000 (32-bit, non-prefetchable) [size=16M]<br />
*** Memory at e0000000 (64-bit, prefetchable) [size=256M]<br />
*** Memory at d4000000 (64-bit, non-prefetchable) [size=32M]<br />
*** I/O ports at 2000 [size=128]<br />
*** Capabilities: [60] Power Management version 2<br />
*** Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-<br />
*** Capabilities: [78] Express Endpoint IRQ 0<br />
*** Capabilities: [100] Virtual Channel<br />
*** Capabilities: [128] Power Budgeting<br />
*** Capabilities: [600] Unknown (11)<br />
* PCI Express 16&times;<br />
* 128 or 256 MB video memory<br />
<br />
=== Linux X.Org driver ===<br />
<br />
Default X.Org NVidia driver, called "nv" works.<br />
<br />
=== NVIDIA proprietary driver ===<br />
<br />
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.<br />
<br />
==== CUDA ====<br />
<br />
Since it has a G86 core, [http://developer.nvidia.com/object/cuda.html NVidia CUDA] works on this video card, even though it is not listed in the CUDA manuals. Running very large problems (like the SDK samples) however might fail because of running out of the small graphics memory.<br />
<br />
=== LCD Backlight Brightness Control on T61 ===<br />
<br />
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}} 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. <br />
<br />
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. This was tested with the acpi video driver included in the vanilla Linux 2.6.21-6 kernel.<br />
<br />
[[Category:Components]]</div>Ylaihttps://www.thinkwiki.org/w/index.php?title=NVIDIA_Quadro_NVS_140M&diff=31382NVIDIA Quadro NVS 140M2007-07-19T18:52:03Z<p>Ylai: cat</p>
<hr />
<div>The Quadro NVS 140M is a mobile video card with a G86 core and either 128 MB or 256 MB graphics memory.<br />
<br />
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.<br />
<br />
Since it has a G86 core, [http://developer.nvidia.com/object/cuda.html NVIDIA CUDA] works on this video card, even though it is not listed in the CUDA manuals. Running very large problems (like the SDK samples) however might fail because of running out of the small graphics memory.<br />
<br />
== LCD Backlight Brightness Control on T61 ==<br />
<br />
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}} 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. <br />
<br />
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. This was tested with the acpi video driver included in the vanilla Linux 2.6.21-6 kernel.<br />
<br />
[[Category:Components]]</div>Ylaihttps://www.thinkwiki.org/w/index.php?title=NVIDIA_Quadro_NVS_140M&diff=31381NVIDIA Quadro NVS 140M2007-07-19T18:46:28Z<p>Ylai: rephrase the first part, CUDA</p>
<hr />
<div>The Quadro NVS 140M is a mobile video card with a G86 core and either 128 MB or 256 MB graphics memory.<br />
<br />
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.<br />
<br />
Since it has a G86 core, [http://developer.nvidia.com/object/cuda.html NVIDIA CUDA] works on this video card, even though it is not listed in the CUDA manuals. Running very large problems (like the SDK samples) however might fail because of running out of the small graphics memory.<br />
<br />
== LCD Backlight Brightness Control on T61 ==<br />
<br />
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}} 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. <br />
<br />
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. This was tested with the acpi video driver included in the vanilla Linux 2.6.21-6 kernel.</div>Ylaihttps://www.thinkwiki.org/w/index.php?title=AD1984&diff=31311AD19842007-07-15T11:32:06Z<p>Ylai: /* Linux ALSA driver */ patches</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== AD1984 ===<br />
This is a ''Analog Devices'' High-Definition Audio controller<br />
<br />
=== Features ===<br />
* Chipset: AD1984<br />
* Interface: HD Audio <br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
<br />
=== Linux ALSA driver ===<br />
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).<br />
<br />
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:<br />
<br />
* [http://hg.alsa-project.org/alsa-kernel/rev/958b39f3e8dd Fix Oops with AD1984 thinkpad model]<br />
* [http://hg.alsa-project.org/alsa-kernel/rev/47ca87407c84 Fix AD1984 basic model]<br />
* [http://hg.alsa-project.org/alsa-kernel/rev/ca37aeeeb0ea Fix Thinkpad X61/T61 outputs]<br />
<br />
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)<br />
<br />
=== This chip may be found in ===<br />
* {{R61}}<br />
* {{T61}}<br />
<br />
=== Datasheets ===<br />
* [http://www.analog.com/en/prod/0,2877,AD1984,00.html Analog Devices page for the AD1984]<br />
<br />
[[Category:Components]]</div>Ylaihttps://www.thinkwiki.org/w/index.php?title=Rescue_and_Recovery&diff=31310Rescue and Recovery2007-07-15T11:23:43Z<p>Ylai: /* Newer versions of Rescue and Recovery */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | __NOTOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
===Rescue and Recovery===<br />
Rescue and Recovery version 3.0 consists of a bootable partition containing various system recovery tools, including full recovery of the preinstalled Windows XP partition. It can be activated by pressing the {{ibmkey|ThinkPad|#494949}}, {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkVantage|#495988}} [[ThinkPad Button|Button]] during system boot. It contains a FAT filesystem (labeled "IBM_SERVICE"), and has partition type 0x12 ("Compaq diagnostics" in <tt>fdisk</tt>).<br />
<br />
As opposed to a [[Hidden Protected Area|Hidden Protected Area]] Recovery partitions are ordinary partitions, accessible through the partition table. As they are ordinary partitions they are accessible by ordinary partitioning tools. They should be dealt with carefully.<br />
<br />
Rescue and Recovery is a Windows specific feature. If you intend to recover into Windows when you have an issue, it is important to follow the warnings here carefully. If you intend to run another operating system exclusively and never return to Windows, removing this partition is safe. If you remove it, you can still reinstall windows at a later time, provided you have created a Recovery set of discs (1CD + 1DVD or 5CDs required). Booting from the Recovery CD will restore the system to the factory state including the recovery partition.<br />
</div><br />
|}<br />
<br />
==Proper MBR==<br />
{{WARN|Only tinker with the MBR and the Rescue and Recovery partition if you know what you're doing. Mistakes can leave the system unbootable and can make it very difficult to retrieve the data on the harddisk.}}<br />
<br />
Consideration 6 of the Readme states:<br />
<blockquote>"The Master Boot Record (MBR) must be configured properly for the Rescue and Recovery application to function properly. When possible, the Rescue and Recovery application attempts to ensure the proper configuration of the MBR. This can only occur if the Rescue and Recovery application is installed after other applications that requires the MBR."</blockquote><br />
<br />
Apparently, the MBR is not "configured properly" if LILO or GRUB have written it. The following is the case:<br />
*The default bootloader seems to ignore the active bit and always boots the first partition instead<br />
*The default bootloader contains code to catch a press of the appropriate button during bootup and launch the Rescue and Recovery application in that case<br />
*Before launching the Rescue and Recovery application at system boot, the default bootloader changes the partition type of the Rescue and Recovery partiton to 0x0b, otherwise it changes it to 0x12 (to hide it from Windows)<br />
*The Rescue and Recovery application assumes that the first partition contains Windows<br />
*When booting from the Rescue and Recovery partition, it needs to have its type set (either by Thinkvantage or by GRUB) to 0x0b (FAT32) for the default bootloader to launch the Rescue and Recovery application.<br />
<br />
Since neither LILO nor GRUB catch the press of the button (an undocumented mechanism anyway) it is not possible to launch the Rescue and Recovery application by pressing the appropriate button during system boot, once LILO or GRUB have altered the MBR for their boot procedure.<br />
<br />
IBM provides a program to manage the Rescue and Recovery bootloader. It is located in {{path|C:\Program Files\IBM ThinkVantage\Common\BMGR}} or {{path|C:\Program Files\Common Files\Lenovo\BMGR}}. It can select the partition to boot, and also allows for rewriting the MBR if it was written by another bootloader. More information is needed about this program.<br />
<br />
Some information here, but it may be slightly out of date:<br />
http://www.redbooks.ibm.com/abstracts/SG247107.html<br />
<br />
===MBR written by GRUB===<br />
If the MBR was written by GRUB you can still use GRUB to launch the Rescue and Recovery application. However if you leave the type of the Rescue and Recovery partition to 0x12 (Compaq diagnostics), this will result in an error message "c000021a, Fatal System Error" if you try to launch it. To avoid that and to make sure the recovery partition always is of the right type, add a line to change the partition type to 0x0b to the Rescue and Recovery partition's entry in your {{path|/boot/grub/menu.lst}}. Assuming your Rescue and Recovery partition is the second partition, it could look like this: Please note that there are people who report that this didn't work, for example it didn't work on a {{Z61m}} 9450-3HG.<br />
<br />
title IBM Rescue and Recovery<br />
root (hd0,1)<br />
'''parttype (hd0,1) 0x0b'''<br />
'''unhide (hd0,1)'''<br />
chainloader +1<br />
<br />
Also add an <tt>unhide</tt> line here because we are going to hide the Rescue and Recovery partition on every boot of Windows, so we need to unhide it, when the recovery partition is booted. This is because if we don't hide the partition when booting Windows, it would be visible and accessable there and that's not what we want. So, assuming that Windows is on the first partition, the Windows entry could now look like this:<br />
title Windows<br />
root (hd0,0)<br />
'''hide (hd0,1)'''<br />
chainloader +1<br />
<br />
===GRUB in a partition's boot sector===<br />
A way to have your Access IBM button still functional on bootup, is to create a separate {{path|/boot}} partition, install GRUB to that partition and make it active. This will leave the MBR untouched.<br />
{{NOTE|If the above finding is true that the MBR ignores the active bit, that partition has to be the first one. In most recent Linux distributions it is not easy to create /boot as first partition and shrink the Windows partition. In that case the Windows bootloader can be used to boot Windows and Linux, also preserving the Rescue and Recovery functionality. See below.}}<br />
*In the BIOS, set the IBM Predesktop Area to 'Secure'.<br />
*Boot your Linux distribution's installation CD.<br />
*Follow the instructions and go through the regular installation process.<br />
*Create a '''primary partition''' for /boot (the other stuff can go into the extended partitions) and when the time comes to install GRUB, make sure you install it into the boot sector of the boot partition.<br />
*Set this boot partition as active.<br />
<br />
===Using the Windows Bootloader to Boot Linux===<br />
The NTLDR Windows bootloader can be configured to boot Linux in addition to Windows. The master boot record (MBR) is unchanged, so the ThinkVantage Rescue and Recovery system boot functionality is preserved. This clever procedure was [http://gawrysiak.org/corvus/?p=4 originally applied] to Ubuntu Dapper Drake, and is generalized here.<br />
<br />
1. Boot Windows and make product recovery disks. You will see this step repeated throught this wiki for good reason. The recovery disks can refresh your hard disk to its original factory state, getting you out of the trouble you might make in the next step.<br />
<br />
2. Shrink the Windows NTFS partition to the size you like. You will need a bootable CD that is capable of resizing NTFS partitions. I have done this before with Knoppix, but this time I used Partition Magic (US$70).<br />
<br />
Leave the Rescue and Recovery partition (~5GB) at the end of the disk. Other authors claim that it ''must not'' be moved. I did move it, and it works fine. Still, in retrospect I agree that the end of the disk is the best place for your Rescue and Recovery partition.<br />
<br />
3. Reboot. Push the {{ibmkey|ThinkVantage|#495988}} button during system boot, and verify that Rescue and Recovery still runs. Reboot into Windows to verify that the partition resize was successful.<br />
<br />
4. Begin your Linux installation. Linux will see the Windows NTFS partition as /dev/sda1, and the Rescue and Recovery FAT32 partition as /dev/sda2. When the Linux installer asks you about GRUB, do not install GRUB in the MBR. Instead, install GRUB in the /boot partition (most likely /dev/sda3).<br />
<br />
5. After the Linux installation is finished, reboot with a bootable Linux live CD. The "rescue mode" of your Linux installation CD #1 should work fine for this. Usually you start the rescue mode with the command,<br />
<br />
linux rescue<br />
<br />
Start the network if you plan to use FTP in step 7.<br />
<br />
6. After you get a shell prompt, become root if necessary, and then write the first sector of the /boot partition (probably /dev/sda3) to a file using the dd command:<br />
<br />
sudo -i # If necessary<br />
cd /mnt/sysimage/boot # Or wherever your live CD mounts the /boot partition<br />
dd if=/dev/sda3 of=grub.img bs=512 count=1<br />
<br />
The resulting grub.img file should be 512 bytes long.<br />
<br />
7. Transfer the grub.img file somewhere where you can read it from Windows. You can use removable media like a USB flash drive, or even FTP.<br />
<br />
8. Reboot into Windows. Copy the grub.img file to c:\grub.img.<br />
<br />
9. Make a backup copy of the c:\boot.ini NTLDR control file. c:\boot.ini is read-only and hidden, so you will have to tell Windows to show hidden files, and turn off the read-only property on c:\boot.ini.<br />
<br />
10. Edit c:\boot.ini. Append the line,<br />
<br />
c:\grub.img="Linux GRUB Bootloader"<br />
<br />
So that Linux will boot by default, you may also want to change the default OS to c:\grub.img, and reduce the timeout to 5 seconds or so. For reference, here is my c:\boot.ini file for Windows XP:<br />
<br />
[boot loader]<br />
timeout=5<br />
default=c:\grub.img<br />
[operating systems]<br />
c:\grub.img="Linux GRUB Bootloader"<br />
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional" /noexecute=optin /fastdetec<br />
<br />
11. Reboot. Now the Windows boot menu should offer you a choice of "Linux GRUB Bootloader" or Windows XP. Choose "Linux GRUB Bootloader", and you will be taken to the GRUB boot menu, where you can select Linux, or even go back to the Windows boot menu.<br />
<br />
12. When you need Rescue and Recovery, push the {{ibmkey|ThinkVantage|#495988}} button upon system boot. Since you have touched neither the MBR nor the Rescue and Recovery partition, Rescue and Recovery will work exactly the same as it did before you installed Linux.<br />
<br />
==Newer versions of Rescue and Recovery==<br />
<br />
Rescue and Recovery version 4 is installed on T61.<br />
<br />
The partition type is 0x27. By factory default, the R&R partition is the first partition on the disk. The filesystem used is NTFS. The preloaded Windows appear as the second partition, with the active bit set.<br />
<br />
R&R version 4 bootloader seems to honor the active bit in the partition table. To install Linux while maintaining the R&R functionality is therefore rather straightforward:<br />
<br />
* Shrink the second Windows partition &ndash; or remove it if not needed<br />
* Add partitions for Linux (or other operating systems)<br />
* Install GRUB on a partition boot sector<br />
* Remove the active bit from the Windows partition and activate the boot partition with GRUB<br />
<br />
==Older versions of Rescue and Recovery==<br />
Some Thinkpads (e.g., T23 and T30) do not come with a Recovery CD, but also do not support the [[Hidden Protected Area]]. These ThinkPads have an older version of Rescue and Recovery preloaded on the hard disk to implement the factory recovery function. Most of the comments above also apply to the older versions, with the following differences:<br />
*The recovery partition type is 0x1c, hidden FAT32, LBA-mapped (or 0xc when unhidden).<br />
*The boot manager program is in {{path|C:\IBMTOOLS\RECOVERY}} and only runs in a 16-bit DOS environment<br />
{{Fixme|name of this boot manager needed}}<br />
*The IBM Predesktop area runs atop of Windows 98 (command-line) instead of WinPE<br />
<br />
==External Sources==<br />
* IBM page on [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4Q2QAK ThinkVantage Rescue and Recovery].<br />
* [ftp://ftp.software.ibm.com/pc/pccbbs/thinkvantage_en/tvtrnr3_1027en.txt Rescue and Recovery Readme]<br />
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-46088 IBM page about accessing the Recovery Partition if Linux has been installed and the F11 button no longer works]<br />
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-54483 IBM Rescue and Recovery repair diskette]<br />
<br />
==Models featuring this technology==<br />
* ThinkPad {{T23}}, {{T30}} (R&R 2.0)<br />
* ThinkPad {{T42}}<br />
* ThinkPad {{T43}}, {{T43p}}<br />
* ThinkPad {{T60}}, {{T60p}}<br />
* ThinkPad {{R52}}<br />
* ThinkPad {{Z60m}}<br />
* Thinkpad {{Z61m}}<br />
<br />
[[Category:Glossary]]</div>Ylai