https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=Floffe&feedformat=atomThinkWiki - User contributions [en]2024-03-29T08:03:09ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=User_talk:Tonko&diff=50035User talk:Tonko2010-11-15T15:48:11Z<p>Floffe: </p>
<hr />
<div>Hei, great work! If you have fitting pictures for the 755CD/CDV feel free to upload and change them. Concerning the 701 and 755 i'll check. Thx. [[User:Wyrfel|Wyrfel]] 10:20, 17 Mar 2005 (CET)<br />
----<br />
== Thinkpad ACPI ==<br />
<br />
Are you sure that thinkpad_acpi is removed from the kernel? it's still loaded in my 2.6.31-14 kernel...<br />
<br />
?? thinkpad_acpi is certainly not removed from the kernel. ibm_acpi is though, or rather has been renamed to thinkpad_acpi. Having said that some of the functionality thinkpad_acpi used to provide (bays and docks) has been recently stripped from the driver, and is now the responsibility of the generic ACPI bay and dock drivers. Also on newer thinkpads (T60 and such), thinkpad_acpi is no longer used for backlight, which instead is now handled by the generic acpi video driver. --[[User:Tonko|Tonko]] 08:48, 18 November 2009 (UTC)<br />
<br />
== UltraBase ==<br />
<br />
Hi Tonko,<br />
<br />
You posted that the UltraBase has an UltraSlimBay. I don't think there IS such a thing as an UltraBase. Certainly all of the X series UltraBase (X2, X3 and X4) do NOT have an UltraSlimBay. They are already on the chart.<br />
<br />
Can you give a reference or part number to the UltraBase, please? [[User:Whizkid|Whizkid]] 14:22, 25 May 2005 (CEST)<br />
<br />
Hei Wizkid,<br />
<br />
(sorry for interfering ;-) ). The (original) UltraBase is the same kind of media slide but for the ThinkPad 570. That's why it didn't have an X, because the X originates from X series and the numbers with it to designate the generation of X series the according UltraBase fits. I owned one of these once, so believe me, they exist an they feature an UltraSlimBay. ;-)Wyrfel.<br />
----<br />
<br />
We should create an [[UltraBase]] page, but I never had one, and am too busy right now to dig it up the details. Finding specs on these old options is getting difficult. Tonko<br />
<br />
----<br />
Just did that. I found some data in my old eBay announcement that i created when i sold the notebook. [[User:Wyrfel|Wyrfel]] 02:06, 26 May 2005 (CEST)<br />
----<br />
<br />
Hei,<br />
<br />
as you have realized we sysoped you some days ago. We did this to give you the ability to delete and move pages etc. . If you would send [[User:akw|akw]] your email address, he will create a forward address for you on the thinkwiki domain.<br />
<br />
Thanks once more for all your great responsible work.<br />
[[User:Wyrfel|Wyrfel]] 03:26, 17 Aug 2005 (CEST)<br />
----<br />
<br />
<br />
== Rovclock ==<br />
Hey, what's up with removing my info on lowest clockspeeds on the radeon 9500Pro? I'm sure people that find this wiki page might be interested at what speeds they can underclock their radeon in a desktop. maybe it's a media center that needs to be quiet and cool, maybe it's a desktop in a country that doesn't have enormous amounts of electricity at no charge like american's do. Either let people put all additional info on, or make the page read only.<br />
<br />
----<br />
This is "ThinkWiki", a Wiki for Linux on ThinkPads, not a Wiki for desktop machines<br />
<br />
--[[User:Tonko|Tonko]] 02:39, 3 Nov 2005 (CET)<br />
<br />
== Full Dock ==<br />
<br />
Hello,<br />
<br />
referring to the changes you made to the [[ThinkPad_Dock]] page. I heard that the DVI pass-through works at least on the X3* models as well. If you are not absolutely certain the models you listed are the only ones supporting DVI output through the dock I kindly request you to change the wording.<br />
<br />
--[[User:Rolf|Rolf]] 18:09, 13 Nov 2005 (CET)<br />
----<br />
Do you actually have evidence of that?<br />
<br />
The X30 most likely will not support DVI, as it has an Integrated graphics controller in the Intel Southbridge, the X31 and X32 have the ATI Radeon 7000 chip, and might perhaps be possible of DVI. But I have never seen anywhere stated that they can.<br />
<br />
So unless you can point to some IBM documentation that they can, or have personal experience with one of the X30 models that confirms that they can do DVI pass-through, I think we should leave it as is. I don't want someone to buy an X32 based on us saying it can do DVI pass-through when it cannot.<br />
<br />
--[[User:Tonko|Tonko]] 19:14, 13 Nov 2005 (CET)<br />
<br />
== Question about "nsc-ircc, Wrong chip version ff" ==<br />
<br />
Tonko,<br />
<br />
On the [[How to make use of IrDA]] page there is mention of a "Wrong chip version ff" error that is caused "if the FIR mode is not activated" when you attempt "to load the nsc-ircc module". It is also briefly discussed on the associated talk page.<br />
<br />
I'm running Ubuntu Dapper Drake on a Z60m, and whenever I suspend to RAM, just before the screen goes dark, a console appears that shows this error several times (once per time I've suspended since last reboot). Corresponding entries also appear in my system log. So, I am experiencing this problem, but it isn't clear to me exactly how to fix it. I'm assuming I need to activate FIR mode before loading the nsc-ircc module, but I have no idea how to do this (or exactly what this means).<br />
<br />
Can you point me in the right direction?<br />
<br />
Thanks,<br />
<br />
--[[User:Chiron|Chiron]] 18:41, 27 July 2006 (CEST)<br />
<br />
Chiron,<br />
<br />
Sorry for taking a while to respond. I have been away for a bit and started a new job and such...<br />
<br />
I do not have a 60 series machine, but it does sound like the chip is not getting initialized properly upon resume.<br />
<br />
You might be able to resolve this issue by simply upgrading to the latest 2.6 kernel from kernel.org, as that includes fixes for enabling the chip (without hacks), and also to re-activate the chip in FIR mode after a suspend.<br />
<br />
--[[User:Tonko|Tonko]] 14:16, 25 August 2006 (CEST)<br />
<br />
== Thinkpad W510 Graphics Cards ==<br />
<br />
Hi, Tonko. I have a W510 and it has a Quadro FX 880M. Furthermore, the lenovo product documentation ( http://www.lenovo.com/psref/pdf/tabook.pdf ) lists this graphics card. Where are you seeing that it's supposed to have a NVS 5100M?<br />
<br />
Maybe you know something I don't, but in the interest of time (and at risk of possible rudeness), I'm going to change the wiki page back. I will make a clearer comment this time. (P.s., is this really how users on this wiki talk to each other?)<br />
<br />
--[[User:Quinxex|Quinxex]]<br />
<br />
== SSD ==<br />
<br />
SSD = Solid State '''Drive'''<br />
<br />
SSD = Solid State '''Disk'''<br />
<br />
HDD = Hard Disk Drive<br />
<br />
<br />
== Spam report ==<br />
[[User:Edotowiza]] seems to be a spambot. [[User:Floffe|Floffe]] 15:48, 15 November 2010 (UTC)</div>Floffehttps://www.thinkwiki.org/w/index.php?title=Swsusp&diff=50033Swsusp2010-11-15T15:20:54Z<p>Floffe: Reverting spam "Under construction" message</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 />
===Software Suspend - swsusp===<br />
Software Suspend (<tt>swsusp</tt>) is a suspend-to-disk implementation included in the 2.6 kernel series. See [[Software Suspend 2]] for an alternative implementation, which has some advantages.<br />
<br />
Note that swsusp is not needed for suspend-to-RAM functionality.<br />
|}<br />
<br />
==Kernel configuration==<br />
To enable software suspend change your kernel config as follows:<br />
:{{kernelconf|CONFIG_PM|<*>|Power management support|Power management options|||}}<br />
:{{kernelconf|CONFIG_SOFTWARE_SUSPEND|<*>|Software Suspend|Power management options|||}}<br />
:{{kernelconf|CONFIG_PM_STD_PARTITION|[/dev/resume_partition]|Default resume partition|Power management options|||}}<br />
<tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.) <br />
<br />
You can override the default resume partition anytime by giving {{bootparm|resume|/dev/resume_partition}} as kernel boot parameter.<br />
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - losing all data that was unsaved at suspend time), you can give the {{bootparm|noresume|}} kernel boot parameter.<br />
<br />
{{NOTE|For some people suspending did not work if <tt>resume_partition</tt> was specified in the kernel config. In such case specify the resume partition as a kernel parameter instead.}}<br />
<br />
{{NOTE|When using Debian Etch or Sid, you need to use <tt>initramfs-tools</tt> as yaird is currently (2006-05-18) not supporting swsusp. See [http://wiki.debian.org/InitrdReplacementOptions the Debian Wiki] for more details.}}<br />
<br />
==Suspending==<br />
To suspend you can either do a simple {{cmdroot|echo disk > /sys/power/state}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}. As the {{path|/proc/acpi/sleep}} interface becomes deprecated in newer kernels you should NOT use the old {{cmdroot|echo -n 4 > /proc/acpi/sleep}} anymore.<br />
<br />
Ideally, you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend:<br />
*any running mysql server<br />
*the linuxant driver may require to be stopped as well ({{cmdroot|dldrstop}} does the trick).<br />
<br />
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.<br />
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).<br />
<br />
If the sound output is silent after resume, the following commands might help to get sound to work again without reloading any modules:<br />
amixer set Master mute >/dev/null 2>&1<br />
amixer set PCM mute >/dev/null 2>&1<br />
amixer set Master unmute >/dev/null 2>&1<br />
amixer set PCM unmute >/dev/null 2>&1<br />
<br />
==S5 vs. S4 state==<br />
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.<br />
<br />
<br />
==Model-specific Status==<br />
<br />
{| align="center" cellpadding="2" width="100%" style="border:1px; background:grey;"<br />
! style="background:#efefef;"| Thinkpad Model <br />
! style="background:#efefef;"| Type <br />
! style="background:#efefef;"| Operating System <br />
! style="background:#efefef;"| Kernel Version<br />
! style="background:#efefef;"| swsusp works<br />
! style="background:#efefef;"| Note<br />
|- style="background: white;"<br />
<br />
|- style="background: white; color:black;"<br />
|{{X60}}<br />
| 1706-BM7<br />
| [Own Distro]<br />
| 2.6.20<br />
! style ="color:green;"| yes<br />
|<br />
|- style="background: white; color:black;"<br />
<br />
|- style="background: white; color:black;"<br />
|{{X60s}}<br />
| 1702-55G <br />
| Arch Linux<br />
| 2.6.20<br />
! style ="color:green;"| yes<br />
|<br />
|- style="background: white; color:black;"<br />
<br />
|- style="background: white; color:black;"<br />
|{{X60s}}<br />
| 1702-5FG <br />
| [[:Category:Debian|Debian Etch]]<br />
| 2.6.18 with [[User:Profilek | Forest Zhao's AHCI patches]]<br />
! style ="color:green;"| yes<br />
| <br />
|- style="background: white; color:black;"<br />
<br />
|- style="background: white; color:black;"<br />
|{{X60s}}<br />
| 1702-5FG <br />
| [[:Category:Debian|Debian Etch]]<br />
| 2.6.19.2<br />
! style ="color:green;"| yes<br />
| <br />
|- style="background: white; color:black;"<br />
<br />
|- style="background: white; color:black;"<br />
|{{X31}}<br />
| 2672-BCO <br />
| [[:Category:Debian|Debian Etch]]<br />
| 2.6.20.1<br />
! style ="color:green;"| yes<br />
| <br />
|- style="background: white; color:black;"<br />
<br />
|- style="background: white; color:black;"<br />
|{{X32}}<br />
| 2673 <br />
| [[:Category:Debian|Debian Lenny]]<br />
| 2.6.26<br />
! style ="color:green;"| yes<br />
| <br />
|- style="background: white; color:black;"<br />
<br />
|{{R52}}<br />
| 18299MG<br />
| [[:Category:Debian|Debian Sarge]]<br />
| 2.6.17.9<br />
! style ="color:green;"| yes<br />
| <br />
|- style="background: white; color:black;"<br />
<br />
|{{T30}}<br />
| 2366<br />
| [[:Category:Slackware|Slackware 12 ]]<br />
| 2.6.24.3<br />
! style ="color:green;"| yes<br />
| <br />
|- style="background: white; color:black;"<br />
<br />
|{{T43}}<br />
| 2668-74G<br />
| [[:Category:Fedora|Fedora Core 6]]<br />
| 2.6.19<br />
! style ="color:green;"| yes<br />
| <br />
<br />
|- style="background: white; color:black;"<br />
|{{T43}}<br />
| 2668-74G<br />
| [[:Category:Gentoo|Gentoo]]<br />
| 2.6.20.7<br />
! style ="color:green;"| yes<br />
| <br />
<br />
|- style="background: white; color:black;"<br />
|{{T60}}<br />
| 1953-E7U<br />
| [[:Category:Slackware|Slackware 11]]<br />
| 2.6.20<br />
! style="color:green;" | yes<br />
| <br />
|- style="background: white; color:black;"<br />
<br />
|- style="background: white; color:black;"<br />
|{{X40}}<br />
| 2386-H6G<br />
| [[:Category:Ubuntu|Ubuntu]]<br />
| 2.6.20<br />
! style="color:green;" | yes<br />
| <br />
|- style="background: white; color:black;"</div>Floffehttps://www.thinkwiki.org/w/index.php?title=Parallel_Port&diff=50032Parallel Port2010-11-15T15:20:29Z<p>Floffe: Reverting spam "Under construction" message</p>
<hr />
<div>{| width="100%"<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
Most ThinkPads have a Female DB-25 Parallel Port, for ThinkPads produced from 1995 on they are IEEE1284 compliant.<br />
<br />
The latest ThinkPads no longer have a physical parallel port, but still have the logic integrated, all that is required is to attach the ThinkPad to a supported Dock or Port Replicator with a parallel port.<br />
</div><br />
|}<br />
<br />
* [[Wikipedia:Parallel port| Wikipedia article on Parallel Port]]<br />
* [[Wikipedia:IEEE 1284| Wikipedia article on IEEE 1284]]<br />
__NOTOC__<br />
<br />
==Models featuring this Technology==<br />
*ThinkPad {{220}}<br />
*ThinkPad {{350}}, {{350C}}<br />
*ThinkPad {{355}}, {{355C}}, {{355Cs}}<br />
*ThinkPad {{360}}, {{360Cs}}, {{360C}}, {{360P}}, {{360PE}}<br />
*ThinkPad {{550BJ}}<br />
*ThinkPad {{710T}}<br />
<br />
'''EPP'''<br />
*ThinkPad {{300}}<br />
*ThinkPad {{345C}}, {{345CS}}<br />
*ThinkPad {{360CSE}}, {{360CE}}<br />
*ThinkPad {{370C}}<br />
*ThinkPad {{500}}<br />
*ThinkPad {{510Cs}}<br />
*ThinkPad {{750}}, {{750Cs}}, {{750C}}, {{750P}}<br />
*ThinkPad {{755C}}, {{755Cs}}<br />
<br />
'''EPP & ECP'''<br />
*ThinkPad {{755CSE}}, {{755CE}}<br />
<br />
'''DMA'''<br />
*ThinkPad {{700}}, {{700C}}<br />
*ThinkPad {{720}}, {{720C}}<br />
<br />
'''IEEE1284 compatible'''<br />
*ThinkPad {{240}}, {{240X}}<br />
*ThinkPad {{310}}, {{310D}}, {{310E}}, {{310ED}}<br />
*ThinkPad {{365CS}}, {{365C}}, {{365CSD}}, {{365CD}}, {{365E}}, {{365ED}}, {{365X}}, {{365XD}}<br />
*ThinkPad {{380}}, {{380D}}, {{380E}}, {{380ED}}, {{380XD}}, {{380Z}}<br />
*ThinkPad {{385D}}, {{385ED}}, {{385XD}}<br />
*ThinkPad {{390}}, {{390E}}, {{390X}}<br />
*ThinkPad {{560}}, {{560E}}, {{560X}}, {{560Z}}<br />
*ThinkPad {{570}}, {{570E}}<br />
*ThinkPad {{600}}, {{600E}}, {{600X}}<br />
*ThinkPad {{701C}}, {{701CS}} <tt>(non-DMA)</tt><br />
*ThinkPad {{755CX}}, {{755CV}}, {{755CD}}, {{755CDV}}<br />
*ThinkPad {{760C}}, {{760CD}}, {{760EL}}, {{760ELD}}, {{760E}}, {{760ED}}, {{760L}}, {{760LD}}, {{760XL}}, {{760XD}}<br />
*ThinkPad {{765L}}, {{765D}}<br />
*ThinkPad {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}<br />
*ThinkPad {{820}}, {{850}}, {{860}}<br />
*ThinkPad {{A Series}}<br />
*ThinkPad {{I Series}}<br />
*ThinkPad {{G40}}, {{G41}}<br />
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{R40e}}, {{R50}}, {{R50e}}, {{R50p}}, {{R51}}, {{R51e}}, {{R52}}<br />
*ThinkPad {{T20}}, {{T21}}, {{T22}}, {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}<br />
<br />
==Docks and Port Replicators featuring this Technology==<br />
{{NOTE|These devices only feature pass-through functionality, the actual Parallel port logic needs to reside in the ThinkPad for the port to work}}<br />
* [[ThinkPad Port Replicator]]<br />
* [[ThinkPad Port Replicator II]]<br />
* [[ThinkPad Dock]]<br />
* [[ThinkPad Dock II]]<br />
* [[ThinkPad Advanced Dock]]<br />
* [[ThinkPad Advanced Mini Dock]]<br />
* [[ThinkPad Mini-Dock]]<br />
* [[ThinkPad X4 Dock]]<br />
* [[UltraBase X2]]<br />
* [[UltraBase X3]]<br />
* [[UltraBase X4]]<br />
* [[UltraBase X6]]<br />
* [[X6 Tablet UltraBase]]<br />
* [[ThinkPad 365 Port Replicator]]<br />
* [[ThinkPad 365X Port Replicator]]<br />
* [[ThinkPad 380/385 Port Replicator]]<br />
* [[ThinkPad 560 Port Replicator]]<br />
* [[ThinkPad Enhanced Port Replicator]]<br />
* [[ThinkPad Port Replicator with Advanced EtherJet]]<br />
* [[SelectaBase Model I]]<br />
* [[SelectaBase 600]]<br />
* [[SelectaBase 770]]<br />
* [[ThinkPad MultiPort II]]<br />
* [[ThinkPad Dock I (3545)]]<br />
* [[ThinkPad Dock II (3546)]]<br />
* [[ThinkPad Port Replicator Model 1]]<br />
* [[ThinkPad Port Replicator Model 2]]</div>Floffehttps://www.thinkwiki.org/w/index.php?title=CX20585&diff=50031CX205852010-11-15T15:20:11Z<p>Floffe: Reverting spam "Under construction" message</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 />
<br />
This is a Conexant High-Definition Audio 1.0 codec<br />
<br />
== Features ==<br />
* Chipset: CX20585<br />
* Interface: HD Audio 1.0<br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
== Linux ALSA driver ==<br />
This codec is supported by the current Linux kernels<br />
<br />
Note that the Internal microphone will give static, which for some ThinkPads (T410) is fixed with kernel 2.6.34.2 or for others (X201) with kernel 2.6.35.<br />
<br />
Alternatively the patch can be located [https://patchwork.kernel.org/patch/92496/ here].<br />
<br />
== ThinkPads this chip may be found in ==<br />
* {{T400s}}, {{T410}}, {{T410i}}, {{T410s}}, {{T410si}}, {{T510}}, {{T510i}}<br />
* {{W510}}, {{W701}}, {{W701ds}}<br />
* {{X201}}, {{X201i}}, {{X201s}}, {{X201 Tablet}}<br />
<br />
== Datasheets ==<br />
* ...<br />
<br />
[[Category:Components]]</div>Floffehttps://www.thinkwiki.org/w/index.php?title=How_to_save_memory&diff=50030How to save memory2010-11-15T15:19:36Z<p>Floffe: Reverting spam "Under construction" message</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |This page is meant as a collection of information on how to save memory to make Linux work reasonable on older systems with limited amount of RAM.<br />
<br />
Most distributions nowadays don't take much care about it anymore, so there are a lot of things you can do to save memory. To get a smoothly working Linux environment on a low memory machine you will need to consciously choose a lot of aspects of your system, most importantly the graphical environment, desktop environment and applications. This page provides detailed information about these various optimization possibilities.<br />
|}<br />
<br />
==Alternative graphical environments==<br />
{{Todo|...}}<br />
<br />
==Streamlining the desktop environment==<br />
The common desktop environments GNOME and KDE are focused more on features, integration, and beauty rather than on saving resources. Understandable, but running Linux on an older ThinkPad with limited RAM requires a focus on limiting resource usage. The good thing about Linux is that a lot of things stay adjustable and customizable. So lets see what we can do about desktops.<br />
<br />
One of the most important things is to decide for one graphical widget library and stick with that when you are choosing your desktop environment and applications. Having several toolkits in use means more libraries being loaded and hence more memory being used by those. Possibilities are:<br />
* [http://www.fltk.org/ FLTK]<br />
* [http://www.fox-toolkit.org/ FOX toolkit]<br />
* [http://www.gnustep.org GNUstep toolkit]<br />
* [http://www.gtk.org/ GTK] (not recommended, use GTK 2 if possible)<br />
* [http://www.gtk.org/ GTK 2]<br />
* [http://www.lesstif.org/ Lesstif] / [http://www.openmotif.org/ OpenMotif]<br />
* [http://www.trolltech.com/products/qt/index.html QT]<br />
* [http://www.windowmaker.org/development-wings.html WINGs] (kind of a lightweight GNUstep toolkit, provided by the WindowMaker developers)<br />
* [http://www.x.org/ X Toolkit]<br />
<br />
Of those, at current state, there are enough applications for the X Toolkit, GTK, GTK 2 and QT to provide you with a solution for every task you should want.<br />
<br />
===GNOME===<br />
It's like with humans, the worst feature is in most cases also the best one. For GNOME it is probably the many little parts it consists of. Makes it hard to install, but enables one to customize the installation. So, the first thing you should do to streamline GNOME is not to launch it. Sound stupid? Well, lets have a look.<br />
<br />
GNOME is basically a set of libraries built around the GTK+ libs and extending its functionality. Add some nice little applications, a session manager, a panel, beautiful icons, and some other stuff and you have GNOME as you know it. Reversing those additions is what you can do to use GNOME applications on a machine that this desktop environment would normally take your nerves on.<br />
<br />
The GNOME panel, the session manager, the desktop manager and the window manager are all parts of GNOME that eat a lot of memory for something that others can do in a maybe little less beautiful but much more resource saving way.<br />
So first off configure your login manager not to launch gnome-session at login. If you are using GDM this is quite straight forward, you just need to add a different session script, launching your favorite window manager. See the list below and pick one, lets say i.e. WindowMaker. WindowMaker uses a desktop menu, a dock and a notification area to provide you with an organized way of launching applications and iconfying running ones. So we don't need a panel anymore. Also, think if you really need icons on your desktop. If you do, think about using something like ROX filer instead of nautilus for that. In any case, tell nautilus not to manage the desktop by default by unchecking the according setting within gconf-editor. To keep GNOME applications happy we would need to have gconf and gnome-settings-manager running at every session start. One way to do this is to either include them in your new session script. They both need to be running to make GNOME applications realize their settings properly.<br />
<br />
===KDE===<br />
{{Todo|...}}<br />
<br />
===Alternative Desktop Environments===<br />
First of all, it is important to notice that GNOME and KDE are not the only Desktop Environments around.<br />
Other complete (featuring most of: window management, session management, desktop management, file management and panel) desktop environments are:<br />
* [http://xfce.org/ XFCE] <tt>uses GTK 2</tt><br />
* [http://rox.sourceforge.net ROX Desktop]<br />
* [http://ede.sourceforge.net Equinox Desktop Environment] <tt>uses eFLTK, a modified version of FLTK</tt><br />
* [http://www.nongnu.org/antiright/ AntiRight Desktop Environment] <tt>uses LessTif / OpenMotif</tt><br />
* [http://foxdesktop.sourceforge.net/ FOX Desktop Environment] <tt>uses FOX Toolkit</tt><br />
* [http://www.gnustep.org/ GNUstep] <tt>provides it's own toolkit</tt><br />
* [[http://www.lxde.org/ LXDE, the Lightweight X11 Desktop Environment]] <tt>uses GTK-2</tt><br />
<br />
But also, some Window Managers exceed the task of managing windows towards providing a functional workbench. See below for a list.<br />
<br />
===Building your own Desktop===<br />
<br />
====Window Manager====<br />
If you want to build your own customized desktop, a good start is choosing the window manager of your liking. A list of window managers is at [http://xwinman.org].<br />
<br />
Here's a list of some of them:<br />
*including basic Desktop Environment functionality<br />
**the [[Wikipedia:NextStep|NextStep]] alike ones<br />
***[http://www.windowmaker.org/ WindowMaker] <tt>(probably the most widespread NextStep like WM)</tt><br />
***[http://www.afterstep.org/ AfterStep] <tt>(another one of those)</tt><br />
**the Blackbox-like ones<br />
***[http://blackboxwm.sourceforge.net/ BlackBox]<br />
***[http://fluxbox.sourceforge.net/ FluxBox] <tt>(tabbed windows, lighweight)</tt><br />
***[http://www.icculus.org/openbox/ OpenBox] <tt>(written from scratch to be fully ICCCM and EWMH compliant, fast and light-weight)</tt><br />
**others<br />
***[http://www.icewm.org/ IceWM] <tt>(lightweight, widespread)</tt><br />
***[http://enlightenment.sourceforge.net/ Enlightenment] <tt>(lots of features and eye candy)</tt><br />
***[http://www.pekwm.org PekWM] <tt>(kind of a one man show, but feature rich and extremely customizable)</tt><br />
*pure WindowManagers <br />
**[http://golem.sourceforge.net/ Golem]<br />
**[http://home.earthlink.net/~lab1701/larswm/ LarsWM] <tt>(unique tiling Window Manager)</tt><br />
**[http://www.nongnu.org/ratpoison/ ratpoison] <tt>(modeled after gnu screen)</tt><br />
**[http://fvwm.org/ fvwm] <tt>(small but powerful)</tt><br />
**[http://www.jfc.org.uk/software/lwm.html lwm] <tt>(very small, and fast)</tt><br />
**[http://www.all-day-breakfast.com/wm2/ wm2] <tt>really small Window Manager</tt><br />
**[http://www.all-day-breakfast.com/wmx/ wmx] <tt>slightly more featureful version of wm2</tt><br />
**[http://wmii.suckless.org wmii] <tt>keyboard driven approach, very small, dynamic window managing</tt><br />
**[http://dwm.suckless.org dwm] <tt>keyboard-only driven approach, yet smaller than wmii, dynamic window managing</tt><br />
<br />
====Taskbar/Panel====<br />
Another thing that especially users coming to Linux from the Windows world would probably like is a Panel or Taskbar.<br />
<br />
Here's a collection of independant low resource panels:<br />
*[http://www.chatjunkies.org/fspanel/ F***ing Small Panel] <tt>(doesn't use any toolkit)</tt><br />
*[http://freshmeat.net/projects/hpanel/ HPanel] <tt>(doesn't use any toolkit)</tt><br />
*[http://fbpanel.sourceforge.net/ fbpanel] <tt>(depends on GTK 2)</tt><br />
*[http://jodrell.net/projects/perlpanel Perl Panel] <tt>(depends on GTK 2, gnomevfs, perl)</tt><br />
*[http://www.gkrellm.net/ GKrellM] <tt>(depends on GTK 2, flexible plugin based skinable vertical panel)</tt><br />
<br />
Furthermore most of the windowmanagers allow you to have something like a panel/taskbar configured, and system tray applications like [http://stalonetray.sourceforge.net/ stalonetray] supply support for persistent applications (i.e. those that on quit do not quit but minimize to a tray icon) like Skype.<br />
<br />
====Desktop Pinboard====<br />
Then, the next thing you might be looking for is how to get icons onto your desktop. Usually this is done by the file manager who displays the content of a special directory as icons on the desktop. See the File Manager section to follow this approach.<br />
<br />
However, you might decide for a really lightwight file manager which doesn't offer this feature. In that case all hope is not lost, for there are also special programs specialized in desktop icon management. Such are:<br />
* [http://idesk.sourceforge.net/ iDesk] <tt>(recent versions need imlib2 only)</tt><br />
<br />
====File Manager====<br />
File Managers are the fourth really important compontent of a desktop environment. There are plenty out their ranging from resource hugs to really lightweight and slim ones.<br />
<br />
File Managers come with three distinct general user interface approaches: the two pane gui, the spacial and the browser gui. The browser gui is the one the Windows Explorer starting from Windows 2000 uses as well as earlier versions of Nautilus. The spacial view is the one known from Windows 95 and more recent versions of Nautilus. The two pane view is know to many from Norten Commander, Directory Opus or your favorite FTP client.<br />
<br />
The following list provides an overview.<br />
*FLTK<br />
** [http://www.oksid.ch/flfm/ Fast Light File Manager] <tt>(spacial gui)</tt><br />
* FOX toolkit<br />
** [http://roland65.free.fr/xfe/ X File Explorer] <tt>(browser and two pane gui)</tt><br />
*GTK<br />
** [http://www.kaisersite.de/dfm/ Desktop File Manager] <tt>(spacial gui, incl. desktop icon management)</tt><br />
** [http://www.uwyn.com/projects/fm/ FM] <tt>(spacial, MAC OS 9 like gui)</tt><br />
** [http://radekc.regnet.cz/ Seksi Commander] <tt>(two pane gui)</tt><br />
*GTK 2<br />
** [http://rox.sourceforge.net/ ROX Filer] <tt>(highly productive spacial gui, incl. panel and desktop icon management)</tt><br />
** [http://blog.perldude.de/projects/filer/ Filer] <tt>(browser and two pane gui, requires Perl)</tt><br />
** [http://xffm.sourceforge.net/ XFFM] <tt>(browser and spacial gui, requires some XFCE libs)</tt><br />
** [http://logicaldesktop.sourceforge.net/ Logical Desktop] <tt>(browser gui, actually a very special approach)</tt><br />
** [http://tuxcmd.sourceforge.net/ Tux Commander] <tt>(two pane gui)</tt><br />
** [http://www.nongnu.org/gcmd/index.html Gnome Commander] <tt>(two pane gui)</tt><br />
** [http://emelfm2.net/emelFM2/ emelFM2] <tt>(two pane gui with full customizable menu and toolbar, the best for power users)</tt><br />
** [http://thunar.xfce.org/index.xhtml Thunar] <tt>(requires some XFCE libs)</tt><br />
** [http://pcmanfm.sourceforge.net/ PCMan File Manager] <tt>(An extremly fast and lightweight file manager which features tabbed browsing and user-friendly interface. Requires GTK+ version 2.8.x)</tt><br />
* OpenMotif<br />
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xplore/xplore.php Xplore] <tt>(browser gui with productive 4 pane concept)</tt><br />
* QT 2<br />
** [http://www.hi-net.cz/blaza/bfcommander/en/index.html BF-Commander] <tt>(two pane gui)</tt><br />
*Qt3<br />
** [http://www.beesoft.org/download_bsc.html Beesoft Commander] <tt> (fast & easy two panel file manager, like Norton Commander)</tt><br />
* Tcl/Tk<br />
** [http://users.tkk.fi/~mkivinie/X-Files/ X-Files] <tt>(two pane gui)</tt><br />
*X Toolkit<br />
** [http://www.musikwissenschaft.uni-mainz.de/~ag/xfm/ X File Manager] <tt>(spacial gui)</tt><br />
** [http://www.boomerangsworld.de/worker/ Worker] <tt>(two pane gui, highly productive and configurable)</tt><br />
** [http://xnc.dubna.su/ X Northern Captain] <tt>(interesting flexible two pane gui)</tt><br />
*3D Filemanagers<br />
** [http://www.determinate.net/webdata/seg/tdfsb.html TDFSB] <tt>(3D gui, the most impressing 3D file browser so far)</tt><br />
** [http://www.forchheimer.se/bfm/ Brutal File Manager] <tt>(3D gui more for fun than productivity)</tt><br />
** [http://turma.sourceforge.net/software/3dfile/ 3DFile] <tt>(3D gui)</tt><br />
** [http://orbis.sourceforge.net/ Orbis] <tt>(3D gui)</tt><br />
<br />
==Choosing applications==<br />
===Web Browser===<br />
This is highly dependent on the way you use your browser, it's often worth it to try out all and just track general<br />
memory usage. Remember that <tt>top</tt> and <tt>ps</tt> don't report correct memory usage, track totals only.<br />
<br />
====Firefox====<br />
Firefox is graphical web browser. One can install features like AdBlock and FlashClicktoplay which will decrease memory and<br />
processor usage by hiding Flash and Java -adverts.<br />
<br />
====Opera====<br />
Opera is graphical web browser. You can easily enable/disable plug-ins and java (press F12) and decrease memory usage.<br />
Opera uses QT as toolkit, so you may shave off some Mbytes off memory usage by using dynamically linked version if you use KDE.<br />
<br />
====Konqueror====<br />
Konqueror is graphical web browser. It's integrated with KDE and has several advanced features (esp. ca. KDE 3.5).<br />
You may save some megabytes by using it instead of other browsers when using KDE.<br />
It's not necessarily heavy even when used without running KDE.<br />
<br />
====Dillo====<br />
Dillo is minimalistic and very small graphical web browser. <br />
<br />
====Elinks/Lynx====<br />
elinks/lynx are both text mode web browsers. <tt>elinks</tt> handles tables and formatting much nicer than <tt>lynx</tt>.<br />
Both go very easy on memory footprint.<br />
<br />
{{Todo|...}}<br />
<br />
==Disabling unneeded system deamons==<br />
Another thing you can do to improve performance is to get rid of unneaded system daemons launched from your init scripts. Disable them by using the according configuration interface of your distro or by deleting links in the according runlevel directories (usually in <code>/etc/rc.d/</code>).<br />
<br />
Daemons you usually don't need:<br />
* httpd <tt>(Apache web server)</tt><br />
* mysqld <tt>(MySQL database server)</tt><br />
* smbd <tt>(SMB windows filesharing server)</tt><br />
* pppd <tt>(PPP server for connections through modems and serial lines)</tt><br />
<br />
==Adjusting filesystems==<br />
You can also try to optimize memory usage by making sure that you have as little as possible of your filesystem residing in RAM. To do this make sure that the following mount points are set to reside on your harddisk in {{path|/etc/fstab}}. {{Todo|how?}}<br />
* /dev (not possible if you use udev)<br />
* /tmp<br />
<br />
Also make sure that you mount filesystems with extensive usage with noatime parameter (mount -o remount,ro /...), which disabled access time writes every time you access some file. Note that many incremental backups needs atime to work, such backups will then behave like full backup everytime. This depends on backup systems.<br />
<br />
==Other tips==<br />
===Disk space===<br />
When using Debian/Ubuntu/other derivative, use <tt>aptitude</tt> as package manager, and use it as soon as possible. Use it and only it to install and remove packages.<br />
<br />
One of its most useful features is that it tracks packages you install and marks packages installed via dependency as such, so when you remove a package that is no longer used, or package updates and doesn't use a library anymore, that dependency will get uninstalled.<br />
<br />
You can mark packages installed as automatically installed by hitting 'M' (uppercase m), it will be marked for deinstallation if it's not longer required.<br />
<br />
You could also install <tt>localepurge</tt>, which will remove all unneeded locales and localized manpages for packages you install.<br />
<br />
===System clock===<br />
<tt>ntpd</tt> can occupy around 4MB of memory, which is a substantial proportion of many older systems' total. [http://chrony.sunsite.dk/ <tt>chrony</tt>] is a pair of programs that replace the standard <tt>ntp</tt> and require much less memory.</div>Floffehttps://www.thinkwiki.org/w/index.php?title=Hard_disk_drives&diff=50029Hard disk drives2010-11-15T15:19:15Z<p>Floffe: Reverting spam "Under construction" message</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 />
IBM sold its HDD manufacturing to Hitachi, who continued to use the Travelstar name for notebook drives.<br />
|}<br />
<br />
==IBM/Hitachi harddisk naming scheme==<br />
Hitachi harddisk names (on modern drives) are a set of letters and numbers that in fact tell a lot about the specifications of the drive. The designation follows the pattern:<br />
<br />
{| style="text-align:center;"<br />
| style="background-color:#eeeeee;" | H<br />
| style="background-color:#eeeeee;" | T<br />
| style="background-color:#eeeeee;" | S<br />
| style="background-color:#eeeeee;" | 72<br />
| style="background-color:#eeeeee;" | 60<br />
| style="background-color:#eeeeee;" | 60<br />
| style="background-color:#eeeeee;" | M<br />
| style="background-color:#eeeeee;" | 9<br />
| style="background-color:#eeeeee;" | AT<br />
| style="background-color:#eeeeee;" | 00<br />
|-<br />
| style="background-color:#dddddd;" | H<br />
| style="background-color:#dddddd;" | [t]<br />
| style="background-color:#dddddd;" | [T]<br />
| style="background-color:#dddddd;" | [rr]<br />
| style="background-color:#dddddd;" | [SS]<br />
| style="background-color:#dddddd;" | [ss]<br />
| style="background-color:#dddddd;" | [g]<br />
| style="background-color:#dddddd;" | [h]<br />
| style="background-color:#dddddd;" | [ii]<br />
| style="background-color:#dddddd;" | [??]<br />
|}<br />
<br />
*the H is for Hitachi<br />
*[t] is a single letter designating the drive type, like<br />
** T = Travelstar<br />
** D = Deskstar<br />
** E = Endurastar<br />
*[T] - S for Standard (vs A for Auto for example) - I don't know what this mean :)<br />
*[rr] is the first two digits of speed in RPM, i.e. 54 for 5400 RPM.<br />
*[SS] maximum disk size in model line.<br />
*[ss] is two digits giving the size in GB. 100gig drives have a 10 here.<br />
*[g] generation code<br />
*[h] is the drives height in full millimeters, first digit, i.e. 9 for 9.5mm or some code for desktop: i.e. L - 1-inch form-factor.<br />
*[ii] is a two digit code for the drives interface, like this:<br />
**AT = IDE/ATA<br />
**SA = IDE/SATA<br />
**CE = IDE/ZIF<br />
**CF = Compact Flash<br />
**L3 = SCSI/Ultra320<br />
**LF = FC-AL<br />
*two numerical digits are following, might be some kind of revision, might be something else. Upd: for DeskStar 1st is buffer size (2 - 2MB 8 - 8MB) and 2nd is reserved.<br />
<br />
==Available drives from IBM or Lenovo==<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
! colspan=7 style="text-align:center;background:#efefef;" |<br />
=== 2.5" 9.5mm SATA ===<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models<br />
|-<br />
| 40GB || 5400 || || 39T2621 || Hitachi || ||<br />
|-<br />
| 40GB || 5400 || || 39T2629 || Toshiba || ||<br />
|-<br />
| 40GB || 5400 || || 39T2637 || Fujitsu || ||<br />
|-<br />
| 60GB || 5400 || 40Y8723 || 39T2623 || Hitachi || ||<br />
|-<br />
| 60GB || 5400 || 40Y8723 || 39T2631 || Toshiba || ||<br />
|-<br />
| 60GB || 5400 || || 39T2639 || Fujitsu || MHV2060B|| {{R60e}}<br />
|-<br />
| 60GB || 5400 || || 39T2703 || Hitachi || HTS541060G9SA00 || {{R60e}}<br />
|-<br />
| 60GB || 7200 || 41N3012 || 39T2645 || || ||<br />
|-<br />
| 80GB || 5400 || || 39T2625 || Hitachi || HTS541680J9SA00 || {{X61_Tablet}}<br />
|-<br />
| 80GB || 5400 || || 39T2633 || Toshiba || ||<br />
|-<br />
| 80GB || 5400 || || 39T2641 || Fujitsu || ||<br />
|-<br />
| 80GB || 5400 || 39T2602 || 39T2705 || Hitachi || HTS541080G9SA00 || {{X60_Tablet}}<br />
|-<br />
| 100GB || 5400 || 40Y8721 || 39T2627 || Hitachi || ||<br />
|-<br />
| 100GB || 5400 || 40Y8721 || 39T2635 || Toshiba || ||<br />
|-<br />
| 100GB || 5400 || || 39T2643 || Fujitsu || ||<br />
|-<br />
| 100GB || 7200 || 41N3013 || 39T2649 || Hitachi || ||<br />
|-<br />
| 100GB || 7200 || 42T1021 || 42T1403 || Hitachi || HTS721010G9SA00 || {{T60}}<br />
|-<br />
| 100GB || 7200 || || 27R2345 || Hitachi || ||<br />
|-<br />
| 100GB || 7200 || || 27R2346 || Seagate || ||<br />
|-<br />
| 120GB || 5400 || || || Seagate || ST9120822AS || {{X61s}}<br />
|-<br />
| 120GB || 5400 || 39T2764 || 39T2785 || Fujitsu || [http://www.fujitsu.com/us/services/computing/storage/hdd/mobile/mhv2120bh-sata.html MHV2120BH] || {{X60s}}<br />
|-<br />
| 120GB || 5400 || 42T1030 || 42T1417 || Hitachi || [http://www.hitachigst.com/hdd/support/5k160/5k160.htm HTS541612J9SA00] || {{X60s}} (replacement drive)<br />
|-<br />
! colspan=7 style="text-align:center;background:#efefef;" |<br />
<br />
=== 2.5" 9.5mm PATA ===<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models<br />
|-<br />
| 6GB || 4200 || 05K9237 || 05K9227 || SSD || ||<br />
|-<br />
| 6GB || 4200 || 05K9237 || 05K9228 || Hitachi || ||<br />
|-<br />
| 10GB || 4200 || 08K9510 || 08K9508 || SSD || ||<br />
|-<br />
| 10GB || 4200 || 08K9510 || 08K9531 || Hitachi || ||<br />
|-<br />
| 12GB || 4200 || 05K9238 || 05K9229 || SSD || || <br />
|-<br />
| 12GB || 4200 || 05K9238 || 05K9230 || Hitachi || || <br />
|-<br />
| 15GB || 4200 || 08K9588 || 08K9587 || Hitachi || ||<br />
|-<br />
| 15GB || 4200 || 08K9588 || 08K9585 || STD || ||<br />
|-<br />
| 20GB || 4200 || || 08K9533 || Hitachi || || <br />
|-<br />
| 20GB || || || 92P6375 || Hitachi || || <br />
|-<br />
| 20GB || 4200 || 27L3439 || 27L3441, 08K9548 || || ||<br />
|-<br />
| 20GB || || || 27L3427 || SSD || || <br />
|-<br />
| 20GB || || || 27L4075 || SSD || || <br />
|-<br />
| 20GB || 4200 || 08K9686 || 27L4286 || STD || ||<br />
|-<br />
| 20GB || 4200 || 08K9686 || 27L4385 || Fujitsu || ||<br />
|-<br />
| 20GB || 4200 || 08K9686 || 92P6327 || STD || ||<br />
|-<br />
| 20GB || 4200 || || 92P6019 || Fujitsu || MHS2020AT || {{G40}}, {{G41}}<br />
|-<br />
| 20GB || 4200 || || 92P6094 || Fujitsu || MHT2020AT || {{G40}}, {{G41}}<br />
|-<br />
| 20GB || 4200 || || 92P6017 || Hitachi || DK23EA-20 || {{G40}}, {{G41}}<br />
|-<br />
| 20GB || 4200 || || 92P6086 || Hitachi || IC25N020ATMR04 || {{G40}}, {{G41}}<br />
|-<br />
| 20GB || || 07N4382 || 22L0072 || IBM || DJSA-220 || {{X20}}<br />
|-<br />
| 30GB || || 08K9593 || 08K9590 || || ||<br />
|-<br />
| 30GB || || 08K9593 || 08K9592 || Hitachi || ||<br />
|-<br />
| 30GB || || || 08K9660 || Hitachi || ||<br />
|-<br />
| 30GB || || || 08K9656 || Diabo || ||<br />
|-<br />
| 30GB || || || 08K9564 || SSD || ||<br />
|-<br />
| 30GB || || || 27L4291 || || ||<br />
|-<br />
| 30GB || || || 92P6330 || STD || ||<br />
|-<br />
| 30GB || || 08K1088 || 92P6330 || Hitachi || IC25N030ATCS04-0 ||<br />
|-<br />
| 30GB || 4200 || || 92P6088 || Hitachi || IC25N030ATMR04 || {{G40}}, {{G41}}<br />
|-<br />
| 30GB || 4200 || || 92P6096 || Fujitsu || MHT2030AT || {{G40}}, {{G41}}<br />
|-<br />
| 40GB || 4200 || || 08K9683 || STD || ||<br />
|-<br />
| 40GB || 4200 || || 08K9767 || Hitachi || ||<br />
|-<br />
| 40GB || 4200 || || 92P6023 || Fujitsu || MHS2040T || {{G40}}, {{G41}}<br />
|-<br />
| 40GB || 4200 || || 92P6098 || Fujitsu || MHT2040AT || {{G40}}, {{G41}}<br />
|-<br />
| 40GB || 4200 || || 92P6021 || Hitachi || DK23EA-40 || {{G40}}, {{G41}}<br />
|-<br />
| 40GB || 4200 || || 92P6090 || Hitachi || IC25N040ATMR04 || {{G40}}, {{G41}}<br />
|-<br />
| 40GB || 4200 || || 92P6119 || Moraga || B || {{G40}}, {{G41}}<br />
|-<br />
| 40GB || 4200 || || 92P6121 || Toshiba || Proteus || {{G40}}, {{G41}}<br />
|-<br />
| 40GB || 4200 || 08K9832 || 92P6332 || Hitachi || IC25N040ATMR04-0 ||<br />
|-<br />
| 40GB || 5400 || || 08K9758 || Toshiba || || {{T30}}<br />
|-<br />
| 40GB || 5400 || || 27L4384 || STD || ||<br />
|-<br />
| 40GB || 5400 || 08K9687 || 08K9599 || || ||<br />
|-<br />
| 40GB || 5400 || 08K9816 || 92P6342 || STD || ||<br />
|-<br />
| 40GB || 5400 || 08K9816 || 13N6801 || || ||<br />
|-<br />
| 40GB || 5400 || 08K9816 || 08K9834 || Hitachi || || {{T30}}<br />
|-<br />
| 40GB || 5400 || 08K9816 || 92P6545 || Hitachi || HTS548040M9AT00 ||<br />
|-<br />
| 60GB || 4200 || || 08K9833 || Hitachi || || {{T30}}<br />
|-<br />
| 60GB || 4200 || || 92P6092 || Hitachi || IC25N060ATMR04 || {{G40}}, {{G41}}<br />
|-<br />
| 60GB || 4200 || || 92P6122 || Moraga || C || {{G40}}, {{G41}}<br />
|-<br />
| 60GB || 4200 || 13N6706 || 13N6707 || Hitachi || IC25N060ATMR04-0 || {{R51}}<br />
|-<br />
| 60GB || 5400 || 08K9688 || 08K9700 || || ||<br />
|-<br />
| 60GB || 5400 || 08K9688 || 92P6340 || STD || ||<br />
|-<br />
| 60GB || 5400 || 73P3357 || 13N6893 || || ||<br />
|-<br />
| 60GB || 5400 || || 92P6547 || Hitachi || HTS548060M9AT00 ||<br />
|-<br />
| 60GB || 7200 || || 13N6807 || Hitachi || HTS726060M9AT00 ([[Hitachi Travelstar 7K60|Travelstar 7K60]]) || {{T41p}}, {{T42p}}, {{T43}}, {{T43p}}<br />
|-<br />
| 60GB || 7200 || || 92P6551 || Hitachi || HTS726060M9AT00 ([[Hitachi Travelstar 7K60|Travelstar 7K60]]) ||<br />
|-<br />
| 60GB || 7200 || || 08K0889 || Hitachi || HTE726060M9AT00 ([[Hitachi Travelstar 7K60|Travelstar 7K60]]) || {{R50}}<br />
|-<br />
| 60GB || 7200 || 13N6799 || 13N6807 || Hitachi || HTS726060M9AT00 || {{T41}}<br />
|-<br />
| 80GB || 4200 || 08K9869 || 08K9863 || || ||<br />
|-<br />
| 80GB || 4200 || || 92P6123 || Moraga || B || {{G40}}, {{G41}}<br />
|-<br />
| 80GB || 5400 || 13N6798 || 13N6805 || Hitachi || HTS548080M9AT00 || {{T41p}}, {{T42p}}, {{T43p}}<br />
|-<br />
| 80GB || 5400 || 09N4273 || 92P6549 || Hitachi || HTS548080M9AT00 ||<br />
|-<br />
| 80GB || 7200 || || 39T2583 || Hitachi || ||<br />
|-<br />
| 100GB || 5400 || 40Y8716 || 39T2555 || Fujitsu || ||<br />
|-<br />
| 100GB || 5400 || 40Y8716 || 39T2559 || Toshiba || ||<br />
|-<br />
| 100GB || 7200 || || 39T2585 || Hitachi || ||<br />
|-<br />
| 250GB || 5400 || || || Samsung || HM250JI || {{X60s}}<br />
|-<br />
! colspan=7 style="text-align:center;background:#efefef;" |<br />
<br />
=== 2.5" 12.5mm PATA ===<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models<br />
|-<br />
| 18GB || 4200 || 05K9239 || 05K9231 || || ||<br />
|-<br />
| 32GB || 5400 || 08K9511 || 08K9509 || SSD || || <br />
|-<br />
| 48GB || 5400 || 08K9600 || 08K9599 || || || <br />
|-<br />
| 48GB || 5400 || 08K9600 || 92P6338 || STD || || <br />
|-<br />
! colspan=7 style="text-align:center;background:#efefef;" |<br />
<br />
=== 1.8" 9.5mm PATA ===<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models<br />
|-<br />
| 2GB/4GB/8GB || SSD || || || Transcend || TS2GIFD18/TS4GIFD18/TS8GIFD18 || {{X40}}, {{X41}}, {{X41T}}<br />
|-<br />
| 20GB || 4200 || || 92P6083 || Hitachi || DK14FA-20 || {{X40}}, {{X41}}, {{X41T}}<br />
|-<br />
| 20GB || 4200 || || 39T2541 || Hitachi || HTC426020G7AT00 || {{X40}}, {{X41}}, {{X41T}}<br />
|-<br />
| 30GB || 4200 || || 92P6140 || Hitachi || || {{X40}}, {{X41}}, {{X41T}}<br />
|-<br />
| 30GB || 4200 || || 39T2543 || Hitachi || || {{X40}}, {{X41}}, {{X41T}}<br />
|-<br />
| 30GB || 4200 || || 39T2747 || Toshiba || || {{X60s}}<br />
|-<br />
| 40GB || 4200 || || 92P6085 || Hitachi || DK13FA-40 || {{X40}}, {{X41}}, {{X41T}}<br />
|-<br />
| 40GB || 4200 || || 39T2545 || Hitachi || HTC426040G9AT00 || {{X40}}, {{X41}}, {{X41T}}<br />
|-<br />
| 40GB || 4200 || || 39T2749 || Toshiba || || {{X60s}}<br />
|-<br />
| 60GB || 4200 || 73P3358 || 39T2547 || Hitachi || HTC426060G9AT00 || {{X40}}, {{X41}}, {{X41T}}<br />
|-<br />
| 60GB || 4200 || || 39T2751 || Toshiba || || {{X60s}}<br />
|-<br />
! colspan=7 style="text-align:center;background:#efefef;" |<br />
<br />
=== 2.5" PATA (770 series)===<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models<br />
|-<br />
| 5.1GB || || 11J8947 || 12J0449(Box) 83H7102(Disk) || IBM || DADA-25120 || {{770}}, {{770E}}, {{770ED}}<br />
|-<br />
| 8.1GB || 4900 || 02K0517 || 02K0514 || IBM || DYLA-28100 || {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}<br />
|-<br />
| 14.1GB || || 02K0526 || 02K0525 || || || {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}<br />
|-<br />
! colspan=7 style="text-align:center;background:#efefef;" |<br />
<br />
=== 2.5" PATA (380,385,560,570,600 series)===<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models<br />
|-<br />
| 1.08GB || || 46H4208 || || || ||<br />
|-<br />
| 2.1GB || || 73H9797 || || || ||<br />
|-<br />
| 2.1GB || || 45H8783 || || || ||<br />
|-<br />
| 3.2GB || || 02K0487 || || || ||<br />
|-<br />
| 4.0GB || || 02K0501 || || || ||<br />
|-<br />
| 4.0GB || || 03L5659 || 22L0024 || IBM || DKLA-24090 || {{390E}}<br />
|-<br />
| 4.0GB || || 05K8871 || || || ||<br />
|-<br />
| 4.32GB || 4200 || 25L2744 || || IBM || DKLA-24320 || {{380Z}}<br />
|-<br />
| 5.1GB || || 02K0506 || || || ||<br />
|-<br />
| 6.0GB || || 05K9199 || || || ||<br />
|-<br />
| 6.4GB || || 02K0518 || || || ||<br />
|-<br />
| 10GB || || 36L9293 || || || ||<br />
|-<br />
| 12GB || || 05K9200 || || || ||<br />
|-<br />
| 18GB || || 37L2993 || || || ||<br />
|-<br />
! colspan=7 style="text-align:center;background:#efefef;" |<br />
=== 2.5" SCSI-2 (PowerPC ThinkPads)===<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
!Capacity!!RPM!!PartNr.!!FRU!!Manufacturer!!Model!!ThinkPad Models<br />
|-<br />
| 540MB || || 30H1388 || || || || {{820}}, {{850}}, {{860}}<br />
|-<br />
| 810MB || || 30H1392 || || || || {{820}}, {{850}}, {{860}}<br />
|-<br />
| 1.2GB || || 30H1467 || || || || {{820}}, {{850}}, {{860}}<br />
|}<br />
[[Category:Components]]</div>Floffehttps://www.thinkwiki.org/w/index.php?title=Talk:Tpb&diff=50028Talk:Tpb2010-11-15T15:18:29Z<p>Floffe: Reverting spam "Under construction" message</p>
<hr />
<div>"''Note that on some systems the "nvram" module will need to be loaded before tpb will work, as tpb needs to write to this device. If you run tpb in user-space, you will need write permissions (and, possibly, read); it is probably best to simply add users to a "nvram" group.''"<br />
<br />
Indeed, it may be much easier to get tpb to work properly if you add your user to the nvram group.<br />
<br />
LeJo<br />
<br />
== Possible to use hotkey-setup instead? ==<br />
<br />
Hi, I want to configure the "Access IBM" button on my T40 to open a console / xterm when I press it. However, in Ubuntu 7.04, when I do an <code>aptitude install tpb</code>, it tells me that "<code>hotkey-setup: Conflicts: tpb</code>". So I would like to use hotkey-setup only if I can, especially since I see [http://ubuntuforums.org/showthread.php?t=469740 reports] of other people trying to install tpb together with hotkey-setup and messing up their other keys that were handled correctly by hotkey-setup before. Has anyone got the "Access IBM" key bound to a command using only hotkey-setup, and if so could you maybe share what you did? -- All the best, [[User:Nickj|Nickj]] 05:31, 2 September 2007 (UTC)<br />
<br />
As per [http://ubuntuforums.org/showthread.php?t=207514 this thread] I have just managed to get my "Access IBM" Button working without tpb. I just installed xbindkeys, created a very small file .xbindkeysrc with just the following 2 lines<br />
"gnome-terminal"<br />
m:0x0 + c:159<br />
and added xbindkeys under System -> Preferences -> Sessions -> Startup Programs. The key code in the second line was given by <code>xbindkeys --key</code> when I pressed the button. --[[User:Hepta sean|Hepta sean]] 01:33, 12 September 2007 (UTC)<br />
<br />
I added a longer version of this under [[ThinkPad_Button#Using_xbindkeys_on_Ubuntu|ThinkPad_Button]]. --[[User:Hepta sean|Hepta sean]] 02:59, 12 September 2007 (UTC)</div>Floffehttps://www.thinkwiki.org/w/index.php?title=Colour_profile&diff=50027Colour profile2010-11-15T15:17:52Z<p>Floffe: Undo spam "Under construction" message</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 />
Linux distributions are starting to get support for Colour profiles with gnome-color-manager which is planned to be part of Fedora 13 [https://fedoraproject.org/wiki/Features/ColorManagement].<br />
<br />
IBM and Lenovo have been providing colour profile packages for years, unfortunately they are stuck away in Windows .exe files, with no easy to read mapping of ThinkPad model to ICM file. These instructions will tell you how to unpack the archive and locate the correct ICM file for your ThinkPad.<br />
{{Todo|simplify the procedure for finding the right colour profile to load}}<br />
|}<br />
<br />
==Unpacking the EXE==<br />
Download the Windows EXE file for your model. There are three methods of unpacking it.<br />
# Use a windows machine<br />
# Use wine<br />
# Use cabextract<br />
<br />
The last one is by far the easiest, and will extract the files to your current directory.<br />
==== cabextract on newer ThinkPads ====<br />
{{NOTE|With the latest archive (79oi20ww.exe), Lenovo switched to a different format that neither cabextract nor unzip is able to unpack. As such your now forced to resort to Wine or a (virtual) windows machine.}}<br />
<br />
==== cabextract on older ThinkPads====<br />
Files and directories will be created in the current working directory. You can use the files in any of the directories created, they are all the same.<br />
<br />
$ cabextract 1yoi04ww.exe <br />
Extracting cabinet: 1yoi04ww.exe<br />
extracting WIN98/IBMTPFLX.ICM<br />
extracting WIN98/IBMTPLCD.CAT<br />
extracting WIN98/IBMTPLCD.ICM<br />
extracting WIN98/IBMTPLCD.INF<br />
extracting WIN2000/IBMTPFLX.ICM<br />
extracting WIN2000/IBMTPLCD.CAT<br />
extracting WIN2000/IBMTPLCD.ICM<br />
extracting WIN2000/IBMTPLCD.INF<br />
extracting WINME/IBMTPFLX.ICM<br />
extracting WINME/IBMTPLCD.CAT<br />
extracting WINME/IBMTPLCD.ICM<br />
extracting WINME/IBMTPLCD.INF<br />
extracting WINXP/IBMTPFLX.ICM<br />
extracting WINXP/IBMTPLCD.CAT<br />
extracting WINXP/IBMTPLCD.ICM<br />
extracting WINXP/IBMTPLCD.INF<br />
<br />
==== Using wine====<br />
If you use wine instead to unpack the "ThinkPad Monitor INF File" .exe file. The profiles for newer ThinkPads will be located in {{path|~/.wine/drive_c/DRIVERS/WIN/MONITOR/}}.<br />
<br />
For older ThinkPads a bunch of OS directories will be created in {{path|~/.wine/drive_c/DRIVERS/WIN/MONITOR}}. It does not matter which OS directory you use, the ICM files are all the same.<br />
<br />
==Finding your colour profile==<br />
{{NOTE|These instructions assume you have a newer model ThinkPad. If you have an older model ThinkPad you need to use IBMTPLCD.INF instead.}}<br />
After unpacking the windows EXE you should find a bunch of ICM files and a INF file with a mapping of the LCD vendor to colour profile. <br />
<br />
But first you need to know which LCD you have. Unfortunately xrandr does not provide the EISA vendor information, but monitor-edid from the monitor-edid RPM (on Fedora) does. On ubuntu, you can install read-edid ("sudo aptitude install read-edid") and then run "sudo get-edid | parse-edid", the identifier information will have to be transposed ("LEN:3140" -> LEN4031).<br />
<br />
$ monitor-edid<br />
EISA ID: LEN4022<br />
Screen size: 28.6 cm x 21.4 cm (14.06 inches, aspect ratio 4/3 = 1.34)<br />
Gamma: 2.2<br />
Digital signal<br />
<br />
# Monitor preferred modeline (60.0 Hz vsync, 64.0 kHz hsync, ratio 4/3, 124 dpi)<br />
ModeLine "1400x1050" 108 1400 1448 1560 1688 1050 1051 1054 1066 -hsync -vsync<br />
<br />
# Monitor preferred modeline (50.0 Hz vsync, 53.3 kHz hsync, ratio 4/3, 124 dpi)<br />
ModeLine "1400x1050" 89.97 1400 1448 1560 1688 1050 1051 1054 1066 -hsync -vsync<br />
<br />
As you can see from the above, I have a '''LEN4022'''. If I then look at the INF file<br />
$ grep -i LEN4022 TPLCD.INF<br />
%TPSXGAP% = TPLCDSXGAP.Install, Monitor\LEN4022 ; 14" SXGA+ TFT 1400x1050<br />
%TPSXGAP% = TPLCDSXGAP.Install.NTx86, Monitor\LEN4022 ; 14" SXGA+ TFT 1400x1050<br />
%TPSXGAP% = TPLCDSXGAP.Install, Monitor\LEN4022 ; 14" SXGA+ TFT 1400x1050<br />
<br />
You will see this maps to '''TPLCDSXGAP'''<br />
<br />
We now need to find what colour profile that maps to.<br />
$ grep -A 2 \\[TPLCDSXGAP.Install] TPLCD.INF<br />
[TPLCDSXGAP.Install] ; SXGA+ 1400x1050<br />
DelReg=DEL_CURRENT_REG<br />
AddReg=1400, DPMS, ICM<br />
<br />
As you can see on the last line, it refers to a '''ICM''' colour profile. Now to finally find out which file we need to use<br />
$ grep -A 1 \\[ICM] TPLCD.INF<br />
[ICM]<br />
HKR,,ICMProfile,0,"TPLCD.icm"<br />
<br />
As you can see above the ICM colour profile, maps to the '''TPLCD.icm''' file (the actual filename will be all upper-case), so that is the file I need to load in gnome-color-manager for my ThinkPad LCD.<br />
{{NOTE|Even though I need to use TPLCD.ICM for my ThinkPad does not mean the outcome will be the same for your ThinkPad. Please run through the steps to determine what file you need to use}}<br />
<br />
== Recent ThinkPads==<br />
Download [http://www-307.ibm.com/pc/support/site.wss/MIGR-62923.html "ThinkPad Monitor INF File"]<br />
<br />
===Supported ThinkPads===<br />
* L410, {{L412}}, L510, {{L512}}<br />
* {{Edge 13"}}, {{Edge 14"}}, {{Edge 15"}},<br />
* {{R60}}, {{R60e}}, {{R61}}, {{R61e}}, {{R61i}}<br />
* {{R400}}, {{R500}}<br />
* {{SL300}}, {{SL400}}, {{SL400c}}, {{SL410}}, {{SL500}}, {{SL500c}}, {{SL510}}<br />
* {{T60}}, {{T60p}}, {{T61}}, {{T61p}}<br />
* {{T400}}, {{T400s}}, {{T410}}, {{T410i}}, {{T410s}}, {{T410si}}, {{T500}}, {{T510}}, {{T510i}}<br />
* {{W500}}, {{W510}}, {{W700}}, {{W700ds}}, {{W701}}, {{W701ds}}<br />
* {{X60}}, {{X60s}}, {{X60 Tablet}}, {{X61}}, {{X61s}}, {{X61 Tablet}}<br />
* {{X100e}}, {{X200}}, {{X200s}}, {{X200 Tablet}}, {{X201}}, {{X201i}}, {{X201s}}, {{X201 Tablet}}, {{X300}}, {{X301}}<br />
* {{Z61e}}, {{Z61m}}, {{Z61p}}, {{Z61t}}<br />
* {{Reserve Edition}}<br />
<br />
== Older ThinkPads==<br />
Download [http://www-307.ibm.com/pc/support/site.wss/MIGR-44320.html "ThinkPad Monitor File"]<br />
<br />
===Supported ThinkPads===<br />
* {{240}}, {{240X}}, {{240Z}}<br />
* {{390}}, {{390E}}, {{390X}}<br />
* {{570}}, {{570E}}<br />
* {{600}}, {{600E}}, {{600X}}<br />
* {{770E}}, {{770ED}}, {{770X}}, {{770Z}}<br />
* {{i1200}}, {{i1300}}<br />
* i Series 1400, Type 2621, 2651<br />
* {{i1720}}, {{i1721}}, i1781<br />
* {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}<br />
* {{A30}}, {{A30p}}, {{A31}}, {{A31p}}<br />
* {{G40}}, {{G41}}<br />
* {{R30}}, {{R31}}<br />
* {{R40}}, {{R40e}}<br />
* {{R50}}, {{R50e}}, {{R50p}}, {{R51}}, {{R52}}<br />
* {{s31}}<br />
* {{T20}}, {{T21}}, {{T22}}, {{T23}}<br />
* {{T30}}<br />
* {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}<br />
* {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}<br />
* {{X30}}, {{X31}}, {{X32}}<br />
* {{X40}}, {{X41}}, {{X41 Tablet}}<br />
* {{TransNote}}</div>Floffehttps://www.thinkwiki.org/w/index.php?title=Ipw2200&diff=50026Ipw22002010-11-15T15:17:20Z<p>Floffe: Undo spam "Under construction" message</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 />
<br />
The '''Ipw2200''' is the Linux driver for the [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] and [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]] found in [[Centrino]] laptops. This driver only works on 2.6.x kernels (2.6.4 or newer).<br />
<br />
Starting with kernels 2.6.14 the driver is included in kernel.<br />
<br />
{{NOTE|Make sure you have installed the firmware! The ipw2200 documentation will tell you where to find these firmware files and where to install those.}}<br />
<br />
Included in mainline Linux kernels, tracking the SourceForge version with about 6 months delay.<br />
<br />
== Packages ==<br />
*{{Fedora}} Packages(1): Fedora Core includes the ipw2200-drivers in FC3 (with updates) and FC4. You still need to grab the firmware from http://rpm.livna.org/<br />
*{{Fedora}} Packages(2): http://www.atrpms.net/name/ipw2200/ <br />
*{{Mandriva}}: The ipw2200 driver modules are included in the stock kernel package; the firmware is included in the commercial distribution or available from http://plf.zarb.org/.<br />
*{{Gentoo}}: The driver is in the portage tree: emerge net-wireless/ipw2200 and net-wireless/ipw2200-firmware<br />
*{{Debian}} Sarge includes the source code for the modules in package ipw2200-source (http://packages.debian.org/ipw2200-source). You additionally need to download firmware manually.<br />
*{{Debian}} Etch includes a version of the modules in its kernel or for a later version install package ipw2200-modules-2.6-486 or ipw2200-modules-2.6-686 or ipw2200-modules-2.6-686-bigmem or ipw2200-modules-2.6-k7 or ipw2200-modules-2.6-amd64; or the source code for them in ipw2200-source (http://packages.debian.org/ipw2200-source) to compile one yourself. You additionally need to download firmware manually.<br />
<br />
== Status ==<br />
In development, usable, WEP 128bit encryption works, WPA and WPA2 work with drivers >= 1.0.2 using [[wpa_supplicant]], monitor/rfmon is supported as with version >= 1.0.6. Generally works well, but some users experience problems (especially with firmware restarts and with WPA functionality using [[wpa_supplicant]]). Passing the <tt>hwcrypto=0</tt> module parameter improves reliability for many users.<br />
<br />
The ipw2200 driver up to version 1.0.6 (in combination with some newer kernels) had a problem getting DHCP leases (it turned out to be a bug in the broadcasting code). Version 1.0.7 seems to have fixed this.<br />
<br />
Older ipw2200 driver versions shipped by many distributions have been reported to freeze a T43 after several minutes of intensive communication. Installing version 1.1.2 of the driver solved the problem.<br />
<br />
Latest stable versions:<br />
* ipw2200 driver: 1.2.0<br />
* firmware: 3.0<br />
* ieee80211 stack: 1.2.15<br />
<br />
Latest development versions:<br />
* ipw2200 driver: 1.2.2<br />
* firmware: 3.1<br />
* ieee80211 stack: 1.2.18<br />
<br />
Mainline kernels contain older (but mostly functional) versions of ipw2200 and ieee80211, and still require the addition of the [http://ipw2200.sourceforge.net/firmware.php firmware] files. To get the latest versions you need to separately install the [http://ipw2200.sourceforge.net/downloads.php ipw2200] module and [http://ieee80211.sourceforge.net/downloads.php ieee80211] stack.<br />
<br />
==Installation==<br />
=== Source Code ===<br />
Download the latest [http://ieee80211.sourceforge.net/downloads.php ieee80211] stack and install it:<br />
:{{cmdroot|tar xzvf ieee80211-1.2.15.tgz}}<br />
:{{cmdroot|cd ieee80211-1.2.15}}<br />
:{{cmdroot|make}}<br />
:{{cmdroot|make install}}<br />
<br />
Download the latest [http://ipw2200.sourceforge.net/downloads.php ipw2200] module and install it:<br />
:{{cmdroot|tar xzvf ipw2200-1.2.0.tgz}}<br />
:{{cmdroot|cd ipw2200-1.2.0}}<br />
:{{cmdroot|make}}<br />
:{{cmdroot|make install}}<br />
<br />
Download the matching [http://ipw2200.sourceforge.net/firmware.php firmware] and install it:<br />
:{{cmdroot|tar xzvf ipw2200-fw-3.1.tgz -C /lib/firmware}}<br />
<br />
=== Debian Sarge ===<br />
{{cmdroot|apt-get install ipw2200-source}}<br />
<br />
{{cmdroot|module-assistant -t build ipw2200-source}}<br />
<br />
[is this how module-assistant works in Sarge?]<br />
<br />
=== Debian Etch ===<br />
<br />
The kernel includes a version but if you want a more recent version install the module ipw2200-modules-2.6-486 or ipw2200-modules-2.6-686 or ipw2200-modules-2.6-686-bigmem or ipw2200-modules-2.6-k7 or ipw2200-modules-2.6-amd64 depending on your architecture.<br />
<br />
The firmware is not distributed with Debian due to licensing reasons, download the matching version 3.0 [http://ipw2200.sourceforge.net/firmware.php firmware] and install it:<br />
<br />
:{{cmdroot|tar -xvf ipw2200-fw-3.1.tgz -C /lib/firmware}}<br />
<br />
:{{cmdroot|mv /lib/firmware/ipw2200-fw-3.1/* /lib/firmware}}<br />
<br />
=== Debian Unstable ===<br />
Install ieee80211-source:<br />
:{{cmdroot|apt-get install ieee80211-source}}<br />
:{{cmdroot|module-assistant -t build ieee80211-source}}<br />
<br />
The kernel includes a version but if you want a more recent version install the module ipw2200-modules-2.6-486 or ipw2200-modules-2.6-686 or ipw2200-modules-2.6-686-bigmem or ipw2200-modules-2.6-k7 or ipw2200-modules-2.6-amd64 depending on your architecture.<br />
<br />
There is a bug in the {{Debian}} package (last checked: Dec 30th 2005) that prevents from linking to <tt>ieee80211</tt> modules using module-assistant. In case it is not fixed in your version, fall back to the regular source installation procedure described above.<br />
<br />
The firmware is not distributed with Debian due to licensing reasons, download the matching [http://ipw2200.sourceforge.net/firmware.php firmware] and install it:<br />
<br />
:{{cmdroot|tar xzvf ipw2200-fw-2.4.tgz -C /usr/lib/hotplug/firmware}}<br />
<br />
see /etc/hotplug/firmware.agent for details on configured firmware locations<br />
<br />
Make sure that your firmware files are not in a subdirectory (dmesg will give you warnings after any modprobe when firmware can't be loaded)<br />
<br />
=== Fedora Core ===<br />
Installation on Fedora Core 5 works out of the box provided you install the ipw2200-firmware package. However, certain parts of the install process may not set up the wireless networking in a friendly manner using GNOME system tray icons and other tools. Bill Moss has written some excellent HowTo articles, including using VPNC to connect to a remote Cisco IPSec network.<br />
<br />
* [http://www.ces.clemson.edu/linux/fc2-ipw2200.shtml Fedora Core 5 and the IPW2200 Wireless Driver]<br />
* [http://www.ces.clemson.edu/linux/nm.shtml Fedora Core 5 NetworkManager, NetworkManager-vpnc and Wireless Driver IPW2200]<br />
<br />
== Testing the driver ==<br />
:{{cmdroot|modprobe ipw2200}}<br />
:{{cmdroot|iwconfig}}<br />
<br />
{{cmdroot|dmesg}} output might look similar to this:<br />
ieee80211: 802.11 data/management/control stack, 1.1.6<br />
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com><br />
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.8<br />
ipw2200: Copyright(c) 2003-2005 Intel Corporation<br />
ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection<br />
<br />
NB: To make the wifi LED work on the thinkpad, pass the option {{bootparm|led|1}} to the kernel while loading the module. eg. {{cmdroot|1=modprobe ipw2200 led=1}}. This can also be accomplished by adding that option to the file where your distribution looks for modprobe options so that it becomes automatic.<br />
<br />
In debian this can be done by putting a file named after the module in /etc/modutils with the options in it<br />
<br />
here we might run a cmd like this<br />
<br />
:{{cmdroot|1=echo options ipw2200 led=1 > /etc/modutils/ipw2200 }}<br />
<br />
then we must run update-modules to remake /etc/module.conf<br />
<br />
:{{cmdroot|update-modules}}<br />
<br />
== WPA support ==<br />
<br />
Use [[wpa_supplicant]] with the <tt>-Dwext</tt> argument (not <tt>-Dipw</tt>), and pass the <tt>hwcrypto=0</tt> argument to the <tt>ipw2200</tt> module.<br />
<br />
There are some very detailed instructions with working sample configurations on the following link:<br />
[http://www.bughost.org/ipw/wpa_howto.txt ipw2200 WPA instruction]<br />
<br />
== Power Management ==<br />
The ipw2200 driver has power management capabilities, which comes in handy while operating on battery. <br />
<br />
To enable reduced power consumption mode, issue: <br />
:{{cmdroot|iwpriv wlan0 set_power 7}}<br />
where <tt>wlan0</tt> is the name of your interface. This will reduce idle power consumption by 1-2 Watts compared to no power management. To return to the "normal" operation mode, you can issue:<br />
:{{cmdroot|iwpriv wlan0 set_power 6}}.<br />
<br />
In order to check current settings, you can issue:<br />
:{{cmdroot|iwpriv wlan0 get_power}}.<br />
<br />
More information on these option is available in the {{path|README.ipw3945}} file in the <tt>ipw3945</tt> package ({{path|README.ipw2200}} seems to be rather sketchy about the details of power management). You may want to turn power management on/off on demand in an ACPI script that catches battery/AC events, so that this happens automatically.<br />
<br />
Note that there have been [http://www.bughost.org/bugzilla/show_bug.cgi?id=1074 reports] that some versions of ipw2200 react with a firmware error to power management commands. This [http://www.bughost.org/bugzilla/attachment.cgi?id=1024 patch] could alleviate the problem.<br />
<br />
*To disable the radio (and further reduce power consumption) when the card is not in use, issue:<br />
:{{cmdroot|echo 1 > /sys/bus/pci/drivers/ipw2200/*/rf_kill}}<br />
*To enable the radio, issue:<br />
:{{cmdroot|echo 0 > /sys/bus/pci/drivers/ipw2200/*/rf_kill}}<br />
*To make the radio off by default after boot, add <br />
options ipw2200 disable=1<br />
to your {{path|/etc/modprobe.conf}} or equivalent (on kubuntu 6.10 {{path|/etc/modprobe.d/options}}).<br />
<br />
See {{path|README.ipw2200}} in the <tt>ipw2200</tt> package for details and other options.<br />
<br />
== Changing the enabled channels ==<br />
Permitted WiFi channels vary with geography due to regulation. The EEPROM in this chip contains a country code (programmed by the hardware manufacturer), and the driver converts this to a channel list and enforces it.<br />
<br />
If you carry your laptop to a different regulatory region, you may need to change the list of permitted channels according to local regulations. There are two ways to accomplish this:<br />
<br />
===Patching the ipw2200 driver===<br />
You can alter the ipw2200 driver sourcecode to hard-code the country code instead of reading it from EEPROM. For example, this will allow all 14 channels (perfect for those special occasions in international water):<br />
<pre><br />
--- ipw2200.c.orig<br />
+++ ipw2200.c<br />
@@ -11344,7 +11344,7 @@ static int ipw_up(struct ipw_priv *priv)<br />
memcpy(priv->net_dev->dev_addr, priv->mac_addr, ETH_ALEN);<br />
<br />
for (j = 0; j < ARRAY_SIZE(ipw_geos); j++) {<br />
- if (!memcmp(&priv->eeprom[EEPROM_COUNTRY_CODE],<br />
+ if (!memcmp("ZZR",<br />
ipw_geos[j].name, 3))<br />
break;<br />
}<br />
</pre><br />
<br />
For the list of codes and their meaning, see the "<tt>ipw_geos</tt>" table in the [http://lxr.free-electrons.com/source/drivers/net/wireless/ipw2x00/ipw2200.c#10382 ipw2200.c sourcecode].<br />
<br />
===Patching the EEPROM===<br />
<br />
Alternatively, you can change the country code in the EEPROM once and for all, and then use the standard ipw2200 driver.<br />
<br />
See this guide:<br />
* [http://saftware.de/#ipw2200 Patching the EEPROM].<br />
<br />
Instead of the <tt>hd</tt> program mentioned there, you can use the more common <tt>od</tt> program:<br />
echo -n ZZD | od -t x1<br />
0000000 5a 5a 44<br />
0000003<br />
<br />
{{WARN|If this procedure goes wrong, you may ruin your wireless card.}}<br />
<br />
== Additional Comments ==<br />
Your kernel may include an old version of the ipw2200 driver. It is recommended to use the latest version.<br />
<br />
Make sure you also install the firmware version needed by the driver version you use. You can find the firmware [http://ipw2200.sourceforge.net/firmware.php here]. To install it, decompress the <tt>.tgz</tt> file into {{path|/usr/lib/hotplug/firmware}} or {{path|/lib/firmware}} depending on your disto.<br />
<br />
The driver doesn't appear to support the MII interface, so any tools like automatic network configuration managers (i.e. whereami) that rely on mii-tool do not work.<br />
<br />
See incompatibility with some Access Points described on [[Intel_PRO/Wireless_2200BG_Mini-PCI_Adapter#Problems|this other page]]<br />
<br />
== External links ==<br />
* [http://ipw2200.sourceforge.net/ Official website]<br />
<br />
[[Category:Drivers]]</div>Floffehttps://www.thinkwiki.org/w/index.php?title=User_talk:Edotowiza&diff=50025User talk:Edotowiza2010-11-15T15:16:43Z<p>Floffe: â†Created page with 'Seems to be a spambot. Reverting contributions ~~~~'</p>
<hr />
<div>Seems to be a spambot. Reverting contributions [[User:Floffe|Floffe]] 15:16, 15 November 2010 (UTC)</div>Floffehttps://www.thinkwiki.org/w/index.php?title=Intel_Mobile_Pentium_MMX&diff=50024Intel Mobile Pentium MMX2010-11-15T15:14:19Z<p>Floffe: Undo spam "Under construction" message</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 Pentium MMX ===<br />
<br />
===Features===<br />
*133-266 MHz tact<br />
*60/66 MHz FSB<br />
*4.5 Million Transistors<br />
*0.35&micro;m or 0.25&micro;m fabrication process<br />
*1.8-2.45 VCore<br />
*2x 16KB L1-Cache<br />
*256KB or 512KB backside L2-Cache<br />
*APIC<br />
*[[SIMD|MMX]] instruction set<br />
</div><br />
|}<br />
<br />
==Available Types and ThinkPads featuring them==<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Model/Freq. (MHz) !! L2 Cache (KB) !! FSB (MHz) !! VCore (V) !! ThinkPad Models<br />
|- style="background:#efefef;"<br />
! colspan=5 | Pentium MMX Mobile<br />
|-<br />
| 300 || 512 || 66 || ... || {{I1411}}, {{I1451}}<br />
|-<br />
| 266 || 512 || 66 || 2.0 || {{235}}, {{380XD}}, {{385XD}}, {{I1410}}, {{I1450}}<br />
|-<br />
| 233 || 512 || 66 || 1.8 || {{380XD}}, {{385XD}}, {{390}}, {{560X}}, {{600}}, {{770}}<br />
|-<br />
| 200 || 512 || 66 || 1.8 || {{560X}}, {{770}}<br />
|-<br />
| 166 || 512 || 66 || 1.8 || <br />
|- style="background:#efefef;"<br />
! colspan=5 | Pentium MMX<br />
|-<br />
| 233 || 256 || 66 || 2.45 || {{560X}}<br />
|-<br />
| 200 || 256 || 66 || 2.45 || {{560X}}<br />
|-<br />
| 166 || 256 || 66 || 2.45 || {{310E}}, {{310ED}}, {{380ED}}, {{385ED}}, {{560E}}, {{760XD}}, {{760XL}}, {{765D}}, {{765L}}<br />
|-<br />
| 150 || 256 || 60 || 2.45 || {{310E}}, {{380D}}, {{380E}}, {{385D}}, {{535E}}, {{560E}}<br />
|-<br />
| 133 || 256 || 66 || 2.45 || {{310E}}, {{310ED}}<br />
|}<br />
<br />
==Thermal Specifications==<br />
<br />
==GCC Optimization Flags==<br />
<br />
<br />
[[Category:Components]]</div>Floffehttps://www.thinkwiki.org/w/index.php?title=User:Duff&diff=50023User:Duff2010-11-15T15:13:57Z<p>Floffe: Undo spam "Under construction" message</p>
<hr />
<div>I love ThinkPads.<br />
<br />
The second laptop I ever owned was a used ThinkPad {{365XD}} which was given to me in 2003. It ran Windows 98, and served me for almost a year before it met it's fate falling three feet to a concrete floor.<br />
<br />
It would be another two years before I owned another ThinkPad, this time a {{R40}} purchased off eBay. Unfortunately, it died just a year or so later, from what seemed to be failure of the system board or graphics chip.<br />
<br />
I recently obtained a collection of older ThinkPads.<br />
<br />
''quantity - model''<br />
<br />
'''Working and/or Minor Issues'''<br />
<br />
1 - {{365XD}}<br /><br />
3 - {{380XD}}<br /><br />
2 - {{380ED}}<br /><br />
1 - {{380Z}}<br /><br />
1 - {{770}}<br /><br />
1 - {{560}}<br />
<br />
'''Not Working'''<br />
<br />
1 - {{600E}}<br /><br />
1 - {{600X}}<br /><br />
2 - Uncertain Models (P2/Celeron Era)<br />
<br />
'''Unknown - No Power Adapter'''<br />
<br />
1 - {{760L}}<br /><br />
1 - {{755CE}}<br /><br />
1 - {{360Cs}}</div>Floffehttps://www.thinkwiki.org/w/index.php?title=Ipw&diff=50022Ipw2010-11-15T15:13:33Z<p>Floffe: Undo spam "Under construction" message</p>
<hr />
<div>The Intel PRO/Wireless ('''IPW''') cards are Intel's WiFi hardware for the [[Centrino]] platforms. The cards come in various formats (mini-PCI, mini-PCIe), and capabilities (802.11b, 802.11b/g, 802.11a/b/g, 802.11a/g/n...).<br />
<br />
The cards have built-in RISC CPUs (used as MAC processors) and a firmware that does all of the stuff that the USA FCC regulations won't allow a vendor to distribute in a way the user could easily modify and run). This makes them Linux-friendly since it allows the vendor to publish GPL drivers without risking any issues with the FCC.<br />
<br />
The driver provided support for a series of Intel wireless cards:<br />
* [[ipw2100]] for the [[Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter]]<br />
* [[ipw2200]] for the [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] and [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]]<br />
* [[ipw3945]] for the [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]<br />
* [[ipw4965]] for the [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter]]<br />
<br />
== See also ==<br />
* [[Iwlwifi]]<br />
<br />
[[Category: Drivers]]</div>Floffehttps://www.thinkwiki.org/w/index.php?title=Ipw2100&diff=50021Ipw21002010-11-15T15:13:12Z<p>Floffe: Undo spam "Under construction" message</p>
<hr />
<div>The '''Ipw2100''' is the Linux driver for the [[Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter]] found in [[Centrino]] laptops.<br />
<br />
== Packages ==<br />
*{{Fedora}} Packages(1): Fedora Core includes the ipw2100-drivers in FC3 (with updates) and FC4. You still need to grab the firmware from http://rpm.livna.org/<br />
*{{Fedora}} Packages(2): http://www.atrpms.net/name/ipw2100/<br />
*{{Mandriva}}: The ipw2100 driver modules are included in the stock kernel package; the firmware is included in the commercial distribution or available from http://plf.zarb.org/<br />
*{{Debian}} Sarge includes the source code for the modules in package ipw2100-source (http://packages.debian.org/ipw2100-source). You additionally need to download firmware manually.<br />
*{{Debian}} Etch includes a version of the modules in its kernel or for a later version install package ipw2100-modules-2.6-486, ipw2100-modules-2.6-686, ipw2100-modules-2.6-686-bigmem, ipw2100-modules-2.6-k7 and ipw2100-modules-2.6-amd64 or the source code for them in ipw2100-source (http://packages.debian.org/ipw2100-source). You additionally need to download firmware manually.<br />
<br />
== Status ==<br />
* Works, but not reliable in recent kernels up to 2.6.33. Random crashes of the firmware, see [https://bugzilla.redhat.com/show_bug.cgi?id=149968],[http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1743].<br />
* In development but usable. Version 1.0.5 works quite well with kernel 2.6.10.<br />
* Works very well with kernel 2.6.16-9. Only firmware needs to be copied to the appropriate directory and everything works out-of-box.<br />
<br />
==Installation==<br />
<br />
=== Debian Sarge ===<br />
{{cmdroot|apt-get install ipw2100-source}}<br />
<br />
{{cmdroot|module-assistant -t build ipw2100-source}}<br />
<br />
[is this how module-assistant works in Sarge?]<br />
<br />
=== Debian Etch ===<br />
The kernel includes a version but if you want a more recent version install the module ipw2100-modules-2.6-486 or ipw2100-modules-2.6-686 or ipw2100-modules-2.6-686-bigmem or ipw2100-modules-2.6-k7 or ipw2100-modules-2.6-amd64 depending on your architecture.<br />
<br />
The firmware is not distributed with Debian due to licensing reasons, download the matching version 1.3 [http://ipw2100.sourceforge.net/firmware.php firmware] and install it:<br />
<br />
:{{cmdroot|tar -xvf ipw2100-fw-1.3.tgz -C /lib/firmware}}<br />
<br />
:{{cmdroot|mv /lib/firmware/ipw2100-fw-1.3/* /lib/firmware}}<br />
<br />
=== Debian Unstable ===<br />
Install ieee80211-source:<br />
:{{cmdroot|apt-get install ieee80211-source}}<br />
:{{cmdroot|module-assistant -t build ieee80211-source}}<br />
<br />
The kernel includes a version but if you want a more recent version install the module ipw2100-modules-2.6-486 or ipw2100-modules-2.6-686 or ipw2100-modules-2.6-686-bigmem or ipw2100-modules-2.6-k7 or ipw2100-modules-2.6-amd64 depending on your architecture.<br />
<br />
The firmware is not distributed with Debian due to licensing reasons, download the matching version ?.? [http://ipw2100.sourceforge.net/firmware.php firmware] and install it:<br />
<br />
:{{cmdroot|tar -xvf ipw2100-fw-?.?.tgz -C /lib/firmware}}<br />
<br />
:{{cmdroot|mv /lib/firmware/ipw2100-fw-?.?/* /lib/firmware}}<br />
<br />
=== Additional Comments ===<br />
Make sure to try the newest version. You will need to install the loadable binary firmware provided on http://ipw2100.sourceforge.net/firmware.php as required by the driver.<br />
<br />
To install the firmware, decompress the <tt>.tgz</tt> in <tt>/lib/firmware</tt><br />
<br />
To turn off the radio on boot-up load ipw2100 with option disable=1, i.e. {{cmdroot|1=modprobe ipw2100 disable=1}}.<br />
<br />
== External links ==<br />
* [http://ipw2100.sourceforge.net/ Official website]<br />
* [http://ipw2100.sourceforge.net/faq.php Official website FAQ]<br />
<br />
[[Category:Drivers]]</div>Floffehttps://www.thinkwiki.org/w/index.php?title=Laptop-mode&diff=50020Laptop-mode2010-11-15T15:12:51Z<p>Floffe: Undo spam "Under construction" message</p>
<hr />
<div>An often overlooked feature in 2.4.23+ and 2.6.6+ Linux kernels is the laptop-mode. It may be activated by writing a "5" into {{path|/proc/sys/vm/laptop_mode}}. Laptop-mode, when configured correctly, can make the kernel buffer disk activities for quite a long time and keep the harddisk spun down for most of the time to save power.<br />
<br />
There is also a set of userland tools made to automatically manage all aspects of laptop-mode configuration according to the actual mode of operation (ac/battery-status). It is called [[laptop-mode-tools]] and you can install it in debian via apt-get or download it from [http://www.xs4all.nl/~bsamwel/laptop_mode/tools here].<br />
<br />
Almost anything you need to know about laptop-mode can be read in your Linux kernel documentation at /usr/src/linux/Documentation/laptop-mode.txt<br><br />
If you can not find this file on your laptop, then go and get yourself the latest kernel sources.<br />
<br />
{{NOTE|The use of Laptop-mode and laptop-mode-tools is not recommended in SuSE Linux. The supplied <tt>powersaved</tt> already takes care of everything regarding power saving}}<br />
{{NOTE| Laptop-mode is disabled by default on Ubuntu 6.10 and later. See [http://samwel.tk/laptop_mode/packages/ubuntu here] for more details}}. <br />
<br />
<br />
=== Keeping the disk in the stand-by state ===<br />
<br />
Laptop-mode is only effective if one avoids spinning up the disk for frivoulous reasons. What will spin a disk up is dependent on the HD firmware, but unfortunately most will spin up on just about every command. To add insult to injury, ATA/SATA pass-through commands are not logged through the {{path|/proc/sys/vm/block_dump}} facility, and thus invisible to tools like '''lm-profiler'''.<br />
<br />
{{HINT|The '''lm-profiler''' tool from laptop-mode-tools can be used to list all processes doing normal disk access.}}<br />
<br />
In systems where the HD spins up too easily, the "'''hddtemp'''" daemon will wake up the disk every minute, and must thus be disabled for power management to be effective. The "'''smartd'''" daemon is also an offender, but fortunately its default configuration issues commands to the HDs only every 30 minutes.<br />
<br />
{{HINT|smartd can be configured to never issue commands to the disk if it is in the sleep or standby states, through the use of option "'''-n standby,q'''". The "''',q'''" is needed to supress syslog messages.}}<br />
<br />
=== Hard drive noise using laptop-mode ===<br />
<br />
The use of laptop-mode can cause a recurrence of the bug https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695 known to affect Ubuntu distributions, which causes the spindle of the hard drive to be parked too frequently. This is caused by laptop-mode setting the Advanced Power Management feature of the hard drive in /etc/laptop-mode/laptop-mode.conf. <br />
<br />
Ubuntu is not completely at fault, as the hard drive manufacturer should set an appropriate graduation between hard drive longevity and power saving using a value between 1 and 255. (more information can be found in the hdparm manual page under the -B flag).<br />
<br />
Values up to 127 can cause unacceptable noise and wear of a hard drive (for more information on Load_Cycle_Counts and hard drive wear, see above bug report). An acceptable balance can be found using hdparm:<br />
<br />
sudo hdparm -B 254 /dev/sdX<br />
<br />
This value can then be entered into /etc/laptop-mode/laptop-mode.conf, first ensuring laptop-mode is set to control hdparm...<br />
<br />
CONTROL_HD_POWERMGMT=1<br />
<br />
...then by changing the default values:<br />
<br />
BATT_HD_POWERMGMT=254<br />
LM_AC_HD_POWERMGMT=254<br />
NOLM_AC_HD_POWERMGMT=254<br />
<br />
<br />
[[Category:Glossary]]</div>Floffehttps://www.thinkwiki.org/w/index.php?title=CDC_slot&diff=50019CDC slot2010-11-15T15:11:57Z<p>Floffe: Undo revision 50001 by Edotowiza (Talk)</p>
<hr />
<div>{| width="100%"<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
The CDC (Communications Daughter Card) slot is an internal expansion slot found in modern ThinkPads.<br />
<br />
It is not meant for customer upgrades.<br><br />
Different CDC slots exist for different functions and different form-factor cards, so you cannot just install any CDC adapter into a CDC slot.<br />
<br />
The types of CDC cards you can use in your system is dependent on the BIOS. If you insert a Bluetooth IV with 56K Modem from an R52 system (for instance) and place it into an R51 system which only had the Modem Daughter Card, the system refuses to boot up and displays Invalid Daughter Card.<br />
<br />
* [http://en.wikipedia.org/wiki/Mobile_Daughter_Card Wikipedia article on CDC]<br />
</div><br />
|}<br />
__NOTOC__<br />
<br />
=== CDC Adapters ===<br />
* [[Ethernet Daughter Card (EDC)]]<br />
* [[Bluetooth Daughter Card (BDC)]]<br />
* [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2)]]<br />
* [[ThinkPad Bluetooth with Enhanced Data Rate (BDC-2.1)]]<br />
* [[Modem Daughter Card (MDC)]]<br />
* [[ThinkPad 56K Modem (MDC-1.5)]]<br />
* [[IBM Integrated 56K Modem (MDC-2)]]<br />
* [[ThinkPad Modem (MDC-3.0, 56kbps HDA)]]<br />
* [[IBM Integrated Bluetooth II with 56K Modem (BMDC)]]<br />
* [[IBM Integrated Bluetooth III with 56K Modem (BMDC-2)]]<br />
* [[IBM Integrated Bluetooth IV with 56K Modem (BMDC-3)]]<br />
<br />
{{gallery_start}}<br />
<br />
{{thumb|T43-2686-DGU-CDC.jpg|CDC in a ThinkPad T43-2686}}<br />
{{thumb|dscf0118.png|analog modem 56k at cdc}}<br />
{{thumb|dscf0119.png||rear cover that houses the cdc at x41}}<br />
{{gallery_end}}<br />
<br />
=== Linux support ===<br />
The different cards appear as either PCI, AC97 or USB devices.<br />
<br />
=== Models featuring this Technology ===<br />
* ThinkPad {{A30}}, {{A30p}}, {{A31}}, {{A31p}}<br />
* ThinkPad {{Edge Series}}<br />
* ThinkPad {{G Series}}<br />
* ThinkPad {{R Series}}<br />
* ThinkPad {{S30}}, {{S31}}<br />
* ThinkPad {{SL Series}}<br />
* ThinkPad {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T60p}}, {{T61}}, {{T61p}}, {{T400}}, {{T400s}}, {{T410}}, {{T410i}}, {{T410s}}, {{T410si}}, {{T500}}, {{T510}}, {{T510i}}<br />
* ThinkPad {{W Series}}<br />
* ThinkPad {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}}, {{X41T}}, {{X60}}, {{X60s}}, {{X60 Tablet}}, {{X61}}, {{X61s}}, {{X61 Tablet}}, {{X200}}, {{X200s}}, {{X201}}, {{X201i}}, {{X201s}}, {{X201 Tablet}}, {{X300}}, {{X301}}<br />
* ThinkPad {{Z Series}}<br />
<br />
[[Category:Components]]</div>Floffehttps://www.thinkwiki.org/w/index.php?title=PC2100&diff=50017PC21002010-11-15T14:53:33Z<p>Floffe: Undo revision 50006 by Edotowiza (Talk)</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 />
=== PC2100 ===<br />
This is DDR (Double Data Rate) memory in 200-pin SO-DIMM form-factor.<br><br />
PC2100 memory is also called DDR266<br />
<br />
</div><br />
|style="vertical-align:top" |<br />
[[image:so-dimm.jpg|SO-DIMM]]<br />
|}<br />
<br />
=== Available memory types from IBM or Lenovo ===<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! Partnumber !! FRU !! Description<br />
|-<br />
| 10K0028 || 10K0029 || 128MB PC2100 DDR-SDRAM CL2.5 SO-DIMM<br />
|-<br />
| 10K0030 || 10K0031 || 256MB PC2100 DDR-SDRAM CL2.5 SO-DIMM<br />
|-<br />
| 10K0032 || 10K0033 || 512MB PC2100 DDR-SDRAM CL2.5 SO-DIMM<br />
|-<br />
| 10K0034 || 10K0035 || 1GB PC2100 DDR-SDRAM CL2.5 SO-DIMM{{Footnote|1}}<br />
|}<br />
<br />
{{NOTE|As PC2100 memory is getting increasingly difficult to aquire, [[PC2700]] memory can be used instead. Using PC2700 memory will not increase system performance, as it will be run at only PC2100 speed.}}<br />
<br />
=== ThinkPads that support this technology ===<br />
{| border=1 cellspacing=0 cellpadding=2<br />
|- style="background:#ffdead;white-space:nowrap;"<br />
! ThinkPad Models !! Soldered<br>on systemboard !! DIMM<br>Slot 1 !! DIMM<br>Slot 2 !! Official<br>Max-Memory !! Unofficial<br>Max-Memory{{Footnote|2}}<br />
|-<br />
| {{A31}}, {{A31p}} || || Occupied || Empty || 1GB{{Footnote|3}} || 2GB{{Footnote|4}} {{Footnote|5}} {{Footnote|7}}<br />
|-<br />
| {{G40}} || || Occupied || Empty || 1GB{{Footnote|3}} || Unknown<br />
|-<br />
| {{R32}} || || Occupied || Empty || 1GB{{Footnote|3}} || 2GB{{Footnote|4}} {{Footnote|5}} {{Footnote|7}}<br />
|-<br />
| {{R40}} - Celeron or Pentium 4-M || || Occupied || Empty || 1GB{{Footnote|3}} || Unknown<br />
|-<br />
| {{R40}} - Pentium M || || Occupied || Empty || 2GB{{Footnote|4}} || Unknown<br />
|-<br />
| {{R40e}} || || Occupied || Empty || 1GB{{Footnote|3}} || Unknown<br />
|-<br />
| {{T30}} || || Occupied || Empty || 1GB{{Footnote|3}} || 2GB{{Footnote|4}} {{Footnote|5}} {{Footnote|7}}<br />
|-<br />
| {{T40}}, {{T40p}} || || Occupied || Empty || 2GB{{Footnote|4}} || 2GB{{Footnote|4}} {{Footnote|6}} {{Footnote|7}}<br />
|-<br />
| {{X31}} || || Occupied || Empty || 2GB{{Footnote|4}} || 2GB{{Footnote|4}} {{Footnote|6}} {{Footnote|7}}<br />
|}<br />
{{Footnotes|<br />
# Only supported with R40 (Pentium M models), T40, T40p and X31<br />
# See [[Unofficial_maximum_memory_specs]]<br />
# Based on 2x 512MB DIMMs, might require removal of original base memory<br />
# Based on 2x 1GB DIMMs, requires removal of original base memory<br />
# DDR SO-DIMM modules exist at a maximum of 1GB. You cannot physically install more than 1 GB per slot.<br />
# DDR SO-DIMM modules exist at a maximum of 1GB. You cannot physically install more RAM than the official specs state.<br />
# Chipset is limited to 2GB.}}<br />
[[Category:Components]]</div>Floffehttps://www.thinkwiki.org/w/index.php?title=IdeaPad_S12&diff=50016IdeaPad S122010-11-15T14:53:22Z<p>Floffe: Undo revision 50015 by Edotowiza (Talk)</p>
<hr />
<div>I got an IdeaPad S12 for Christmas! I'm going to install Ubuntu Karmic on it. This page will record my adventures.<br />
<br />
== Installer ==<br />
<br />
The IdeaPad S12 has a Nano processor by VIA. It's a 64-bit, x86 compatible processor, so you can either install 32-bit x86 or 64-bit x86. Since 64-bit is still flaky I went for 32-bit.<br />
<br />
== Graphics ==<br />
<br />
The default installer for Ubuntu Karmic (including both the Netbook Remix and normal versions) don't contain the correct drivers for the VIA Chrome9 HC3 IGP. You'll know if this is happening to you because the kernel will boot (you'll get to stare at a pretty Ubuntu icon for several minutes), and then the screen will either go blank and have a blinking cursor, or because the screen will start flashing through colors such as red, green, blue, grey as if it were going through a factory test. I also saw a root prompt shortly before graphics attempted to kick in. You should be able to get a terminal using control-alt-fX.<br />
<br />
There is a PPA with updated drivers that worked for me. To install it, get a terminal (using control-alt-f1) and then:<br />
<br />
add-apt-repository ppa:xorg-edgers<br />
aptitude update<br />
aptitude full-upgrade<br />
<br />
I did not have to custom compile the drivers myself.<br />
<br />
== Wireless ==<br />
<br />
Wireless did not work by default, Ubuntu offers you a choice of Broadcom restricted drivers (according to [http://ubuntuforums.org/showthread.php?t=948475 this thread] the STA driver is higher performance), so make sure you have ethernet and go install it.<br />
<br />
== Webcam ==<br />
<br />
Works out of the box.<br />
<br />
{{Template:S12}}</div>Floffe