ThinkWiki - User contributions [en]

List of DMI IDs

2006-07-24T15:57:38Z

Spiney: /* DMI ID database */ add t43p 2668-g2g

This page maintains a database of [http://en.wikipedia.org/wiki/Desktop_Management_Interface DMI] information which can be used to identify ThinkPad models. It is intended as an aid for driver development.

==DMI ID database==

{| border="1" cellspacing="0" cellpadding="2"
|-
! Model
! <tt>system- manufa cturer</tt>
! <tt>system- product-name</tt>
! <tt>system- version</tt>
! <tt>baseboard- manufa cturer</tt>
! <tt>baseboard- product-name</tt>
! <tt>baseboard- version</tt>
! <tt>chassis- manufa cturer</tt>
! <tt>chassis- version</tt>
! <tt>bios- vendor</tt>
! <tt>bios- version</tt>
! <tt>bios- release- date</tt>
! Embedded controller
! Notes
|-
! colspan=14 style="text-align:center;background:#efefef;" | A series
|-
| {{A22p}} 2629-USG
|| IBM || 2629USG || Not Available || IBM || 2629USG || Not Available || IBM || Not Available || IBM || KYET36WW (1.09a) || 10/17/2002
|| ''unknown'' ||
|-
! colspan=14 style="text-align:center;background:#efefef;" | R series
|-
| {{R52}} 1846-AQG
|| IBM || 1846AQG || ThinkPad H || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[76HT14WW-1.04 ]-</nowiki> || Note the weird system-version
|-
| {{R52}} 1846-AQG
|| IBM || 1846AQG || ThinkPad R52 || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET65WW (1.25 ) || 05/18/2006|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki> ||
|-
| {{R51}} 1829-9MG
|| IBM || 18299MG || ThinkPad R51 || IBM || 18299MG || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/ 27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" | T series
|-
| {{T40}} 2378-D2U
|| IBM || 2378D2U || ThinkPad T40 || IBM || 2378D2U || Not Available || IBM || Not Available || IBM || 1RETC2WW (3.03 ) || 04/07/2004
|| <nowiki></nowiki> ||
|-
| {{T41}} 23732FG
|| IBM || 23732FG || ThinkPad T41 || IBM || 23732FG || Not Available || IBM || Not Available || IBM || 1RET84WW (2.11 ) || 10/30/2003
|| <nowiki></nowiki> ||
|-
| {{T42p}} 2373GYG
|| IBM || 2373GYG || ThinkPad T42p || IBM || 2373GYG || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki> ||
|-
| {{T43}} 2686-DGU
|| IBM || 2686DGU || ThinkPad T43 || IBM || 2686DGU || Not Available || IBM || Not Available || IBM || 1YET62WW (1.27 ) || 05/18/2006
|| String 1: IBM ThinkPad Embedded Controller -[1YHT29WW-1.06 ]- ||
|-
| {{T43p}} 2668-G2G
|| IBM || 2668G2G || ThinkPad T43p || IBM || 2668G2G || Not Available || IBM || Not Available || IBM || 1YET47WW (1.08 ) || 06/09/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki> ||
|-
| {{T60}} 2007-49G
|| LENOVO || 200749G || ThinkPad T60 || LENOVO || 200749G || Not Available || LENOVO || Not Available || LENOVO || 79ET62WW (1.07 ) || 06/12/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[79HT45WW-1.04 ]-</nowiki> ||
|-
| {{T60p}} 2007-83U
|| LENOVO || 200783U || ThinkPad T60p || LENOVO || 200783U || Not Available || LENOVO || Not Available || LENOVO || 79ET60WW (1.05a) || 04/18/2006 || <nowiki> String 1: IBM ThinkPad Embedded Controller -[79HT43WW-1.02 ]-</nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" | X series
|-
| {{X60}} 1709-47U
|| LENOVO || 170947U || ThinkPad X60 || LENOVO || 170947U || Not Available || LENOVO || Not Available || LENOVO || 7BET44WW (1.04 ) || 03/13/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[7BHT29WW-1.02 ]-</nowiki> ||
|-
| {{X60s}} 1702-55G
|| LENOVO || 170255G || ThinkPad X60s || LENOVO || 170255G || Not Available || LENOVO || Not Available || LENOVO || 7BET44WW (1.04 ) || 03/13/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[7BHT29WW-1.02 ]-</nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" | Z series
|-
| {{Z61m}} 9453-A11
|| LENOVO || 9453A11 || ThinkPad Z61m || LENOVO || 9453A11 || Not Available || LENOVO || Not Available || LENOVO || 7FET48WW (1.08 ) || 05/26/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[7FHT21WW-1.03 ]-</nowiki> ||
|-
| {{Z60t}} 2511-FEU
|| IBM || 2511FEU || ThinkPad Z60t || IBM || 2511FEU || Not Available || IBM || Not Available || IBM || 77ET42WW (1.05 ) || 11/19/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[77HT28WW-1.02 ]-</nowiki> ||

|}

==Adding entries==

Edit the [[#DMI_ID_database|DMI ID database]] section above. Identify your series (or add a new one), and add an entry of the following form:
:<tt>!-</tt>
:<tt>| </tt>description of your model
:data line 1
:data line 2

where the two data lines are genereated by the following <tt>bash</tt> command:

<pre>
for X in system-{manufacturer,product-name,version} \
baseboard-{manufacturer,product-name,version} \
chassis-{manufacturer,version} bios-{vendor,version,release-date}; do \
echo -n "|| `sudo /usr/sbin/dmidecode -s $X` "; done; echo; \
echo "|| <nowiki><nowiki>`sudo /usr/sbin/dmidecode | grep -i 'embedded controller'`</nowiki></nowiki> ||"
</pre>

==Software using ThinkPad DMI IDs==
* [[HDAPS]] driver whitelist
* [[tp_smapi]] driver whitelist

Template:Industry News

2006-04-12T17:45:44Z

Spiney:

12.04.2006 New [[fglrx]] driver version 8.24.8 released

09.03.2006 New [[fglrx]] driver version 8.23.7 released

10.02.2006 New [[fglrx]] driver version 8.22.5 released

28.01.2006 Lenovo and others have [http://www.pc.ibm.com/us/thinkpad/tseries/workstation.html first mention] of [[:Category:T60p|T60p]] models.

19.01.2006 New [[fglrx]] driver version 8.21.7 released

14.01.2006 A bit old news: [http://www.businessweek.com/technology/content/dec2005/tc20051221_376268.htm?campaign_id=rss_tech Lenovo hires new CEO from Dell].

05.01.2006 Lenovo [http://www.pc.ibm.com/ww/thinkpad/x-t.html?re=home_primary_us announces] the next step in X and T series: [[:Category:X60|X60]], [[:Category:X60s|X60s]] and [[:Category:T60|T60]].

Template:ThinkWiki News

2006-03-15T07:00:18Z

Spiney: removed fglrx, it's in the "industry watch" news already

24.02.2006: ThinkWiki has been upgraded to MediaWiki 1.5.6

21.02.2006: The new [[lt_hotswap]] kernel module enables hot-swapping of drives with full DMA support.

17.02.2006: ThinkWiki has been upgraded to MySQL 5.0.16, PHP/5.1.2 and Apache 2.0.55 for better performance.

11.02.2006: The [http://mmc.drzeus.cx/wiki/Linux/Drivers/sdhci sdhci driver] has been reported to work for [[SD Card slot]]s

10.02.2006: Alpha version of [[Gkrellm-ThinkBat|Gkrellm-ThinkBat]] plugin

30.01.2006: Please test [[KThinkBat|KThinkBat-0.1.5_rc2]]

17.01.2006: Have a look at our new [[ThinkWiki:Anti_Spam_Policy|anti spam policy]]!

14.01.2006: ThinkWiki has been upgraded to [[Special:Version|mediawiki 1.5.5]]

Problems with SATA and Linux

2006-03-10T21:27:14Z

Spiney: /* BIOS error 2010 on user-installed hard disk */ undo spam

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Some ThinkPad models use a SATA controller for the system hard disk. This causes several complications for Linux installation. The following lists these problems and known workarounds. Note that the details are often version- and distribution-specific.

===Models using a SATA disk interface===
Models using a SATA controller and a SATA system disk:
*ThinkPad {{T60}}, {{T60p}}
*ThinkPad {{X60}}, {{X60s}}
*ThinkPad {{Z60t}}, {{Z60m}}
Models using a SATA controller and a PATA (IDE) system disk with a SATA-to-PATA bridge:
*ThinkPad {{T43}}, {{T43p}}
*ThinkPad {{R52}}
*ThinkPad {{X41}}, {{X41T}}

{{NOTE|Some of these problems (namely SMART support, power management and disk information) are solved in Linux 2.6.15 with the inclusion of libata pass-through. See the SATA driver [http://linux-ata.org/features.html features], [http://linux-ata.org/software-status.html software status] and [http://linux-ata.org/sata-status.html hardware status].}}
|}

==Hang on resume from suspend to RAM==

Linux kernels prior to 2.6.16 do not support suspend and resume for SATA devices. As a result, the machine hangs upon the first disk access after resume. A kernel patch ([http://lkml.org/lkml/2005/5/2/46 LKML posting]) fixes this by adding SATA power management support.

Current release-candidates for 2.6.16 ([http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.16-rc1 Changelog for 2.6.16-rc1]) have the patch already included, so no more patching will be necessary with 2.6.16.

===Patches===
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff Patch for kernel 2.6.12]
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.13-rc5.diff Patch for kernel 2.6.13-rc5]
* [http://lkml.org/lkml/2005/9/23/97 Patch for kernel 2.6.14]
* [http://www.xenotime.net/linux/SATA/2.6.15-rc/libata_suspend.patch Patch for kernel 2.6.15-rc4]
* [http://tpctl.sourceforge.net/tmp/sata_pm.2.6.15-rc6.patch Patch for kernels 2.6.15-rc6 through 2.6.15]

Some distributions already include this patch (e.g., {{Ubuntu}} Breezy, {{Gentoo}}'s gentoo-sources 2.6.15-r1), but some don't (e.g., {{Fedora}} 4). If your distribution doesn't include the patch, you will need to compile your own kernel with this patch included.

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169201 bug 169201: "SATA drives fail on laptop suspend"]
* [http://lkml.org/lkml/2005/11/15/385 Fix to libata.h recommended on LKML] in case you get "ata: abnormal state 0x80 on port 0x1F7"

==Failed resume from suspend to disk==

Suspend to disk (using [[swsusp]] or [[Software Suspend 2]]) needs to load the memory image from the SATA disk. For this to work, you either need an initrd with all the necessary SATA modules, or the SATA drivers compiled into the kernel.

==DVD drive not recognized==

The <tt>ata_piix</tt> SATA driver grabs ownership over the IDE ports when it is loaded, but (by default) does not support PATA ATAPI devices such as the Ultrabay optical drives. Thus, if the <tt>ide</tt> driver is compiled as a module and loaded after <tt>ata_piix</tt>, the DVD drive will not be recognized by either driver.

Either of the following configurations will work:
* For kernel 2.6.14 and newer: enable ATAPI support in the SATA system using {{bootparm|libata.atapi_enabled|1}} (see below; this is experimental).
* Compile IDE into the kernel (non-module).
* Compile both IDE and SATA as modules and make sure IDE is loaded first (the module is called 'ide_generic').

Note that the optical drive must be in the Ultrabay during system boot (Ultrabay device swapping is currently unsupported).

==No DMA on DVD drive==

Using the IDE driver, DMA support cannot be enabled on an Ultrabay optical drive:

# hdparm -d1 /dev/hdc

/dev/hdc:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)

As a result, the optical drive is slow, and in particular, too slow to play video DVDs.

One workaround is to use employ the <tt>ata_piix</tt> driver (instead of the IDE driver) for the optical drive. This requires enabling the ATAPI support of the <tt>ata_piix</tt> driver, which is under active development and not yet stable. Using this will probably devour all your data and go on to eat all the food in your fridge. But if you have full backups and an empty fridge, do the following:

* Grab the latest kernel (must be 2.6.14 or newer; the relevant code is under active development).
* Do one of the following:
** Enable the <tt>ata_piix</tt> and <tt>libata</tt>) drivers as built-in, and add {{bootparm|libata.atapi_enabled|1}} to your kernel command line (e.g., in in {{path|/boot/grub/menu.lst}}).
** Enable <tt>ata_piix</tt> and <tt>libata</tt>) as modules (this is often the default) and add "<tt>options libata atapi_enabled=1</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* Do one of the following:
** Disable the IDE system.
** Build the IDE driver as built-in (this is often the default) and add the {{bootparm|hdc|noprobe}} kernel argument (e.g., in in {{path|/boot/grub/menu.lst}}).
** Build the IDE driver as module and add "<tt>options ide hdc=noprobe</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* If you chose to use modules above, regenerate your <tt>initrd</tt> file.

If this doesn't work, use {{cmd|lspci -vn|}} to check whether one of the following chipsets is used in the Thinkpad:
{| border="1" cellspacing="0" cellpadding="2"
|-
!PCI ID
!Name
|-
|8086:7111
|Intel 82371AB/EB/MB PIIX4 IDE
|-
|8086:24db
|Intel 82801EB/ER (ICH5/ICH5R) IDE Controller
|-
|8086:25a2
|Intel 6300ESB PATA Storage Controller
|}
If yes, enable support for these chipsets has to be enabled by setting
#define ATA_ENABLE_PATA
in {{path|include/linux/libata.h}} (and report your ThinkPad model in the discussion page).

There have been reports that DVD burning doesn't work under this configuration, but it seems to work with kernel 2.6.14 and later (tested on a ThinkPad {{T43}} and {{T43p}} with a [[UltraBay Slim DVD Multi-Burner Plus]]).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163418 bug 163418: "can't enable DMA on DVD drive"]

==No DMA on system hard disk==

In recent Linux kernels, there are two modules capable of handling the ICH6 disk controller:
* <tt>ata_piix</tt>: the disk shows as {{path|/dev/sda}} and DMA is enabled.
* Generic IDE driver (<tt>ide-disk</tt>): the disk shows as {{path|/dev/hda}} and DMA is disabled.

The simplest way to enable DMA is to force the IDE driver to ignore the system hard disk by passing the {{bootparm|hda|noprobe}} kernel argument. The driver will then be handled by the <tt>ata_piix</tt> driver. Note that this will change its device name to {{path|/dev/sda}} (which may require changes in {{path|/etc/fstab}} and the boot loader) and may cause other problems as listed above.

(Observed on a ThinkPad T43 with Fedora Core kernel 2.6.13-1.1526_FC4.)

==No SMART support==

Prior to kernel 2.6.15, the Linux SATA system did not support SMART commands (e.g., via smartctl).

The necessary capability is "libata pass-through", which was incorporated into Linux 2.6.15-rc1 and later. A patch is available for older kernels:
* Kernel 2.6.12: http://rtr.ca/dell_i9300/kernel/kernel-2.6.12/03_libata_passthru.patch
* Kernel 2.6.13: http://rtr.ca/dell_i9300/kernel/kernel-2.6.13/02_libata_passthru.patch
* Kernel 2.6.14: http://www.foo.fh-furtwangen.de/~koenigr/02_libata_passthru.fixed.again.patch
* Kernel 2.6.14 with the above suspend-to-RAM patch: http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch

After applying the patch, run smartctl with the "-d ata" parameter:
:{{cmdroot|smartctl -d ata -a /dev/sda}}

==No disk power management==

Prior to kernel 2.6.15, the Linux SATA system did not support power management commands on these models.

The above patches for SMART support resolves this, and in particular enables the following commands:
* {{cmdroot|hdparm -y}} (spin down)
* {{cmdroot|hdparm -S num}} (automatic spin down timeout)
* {{cmdroot|hdparm -B num}} (advanced power management level)
Note that this command is still rejected:
* {{cmdroot|hdparm -M num}} (acoustic management)
(Tested with patched kernels 2.6.13.1 and 2.6.12-4 and a 60GB 7200RPM disk model HTS726060M9AT00.)

Note that even when [[Laptop-mode]] is used, the "hddtemp" daemon (as shipped with Fedora Core 4) will wake up the disk every minute, and must thus be disabled for power management to be effective. Its accesses are not visibile through the {{path|/proc/sys/vm/block_dump}} facility. It is unclear whether disk temperature can be monitored without causing the disk to spin up (on the {{T43}}, none of the {{path|/proc/acpi/ibm/thermal}} values corresponds to the disk's built-in temperature sensor).

==No disk information==

Prior to kernel 2.6.15, on these models the disk information could not be read by the standard commands such as:
*{{cmdroot|hdparm -i /dev/sda}}
*{{cmdroot|hdparm -I /dev/sda}}
The latter is fixed by the above patch for SMART support.

==No swapping of UltraBay device==

The <tt>libata</tt> driver does not yet support hot-swapping (or warm-swapping) of PATA devices. If you use a DVD or 2nd PATA HDD via the <tt>libata</tt> (SATA) driver, to swap them in or out you must power down the machine.

If you use the <tt>ide</tt> driver for a PATA UltraBay device, hot-swapping might work using [[lt_hotswap]], <tt>hdparm</tt>, <tt>idectl</tt> or <tt>hotswap</tt> (please report).However, since you use the <tt>ide</tt> driver, DMA will be disabled (see above).

If you use a SATA device in the UltraBay, <tt>libata</tt> hot-swapping might work (please report).

Swapping of the [[UltraBay Slim Battery]] does work.

==BIOS error 2010 on user-installed hard disk==

While not a Linux issue, note that there is an issue with installing alternative PATA (IDE) hard disks as the system drive. Unless the disk is one of the few approved disks listed inside the BIOS, you will get an BIOS error 2010 during system boot, and the disk may operate unreliably. See [[Problem with non-ThinkPad hard disks]].

Talk:Problems with SATA and Linux

2006-02-23T07:28:06Z

Spiney: about -rc4, removed one of the questions

I'm running gentoo on my T43; I had problems with X11 (opensource radeon driver) and a SATA-patched kernel (I tried both 2.6.14 and 2.6.15-gentoo). Suspend to RAM worked nicely, but starting X freezed the machine after a short time. I tried removing radeonfb from the kernel; with vesafb, everything seems to work.

-- Stefan, 10 Jan 2006

--------
That's strange - with the libata passthrough (IDE driver not in kernel) as set up in the text, my t43p DVD drive also will not record as hinted in the wikipage... DMA works fine, so DVD playing / ripping is smooth and quick. CD record functions also are absent. I have PATA enabled, and the suspend + SMART patches applied over 2.6.14.2.
--------
I can confirm this with 2.6.14.4, however with 2.6.15/15.1 with sata_pm patch it works.

-- Rasto, 24 Jan 2006

--------
regarding the "BIOS error 2010 on user-installed hard disk":
the text says that corruption occurs if you use a harddisk without the specific ibm bios. would be interesting if it is possible to fix this problem in the kernel so that you can use any disk and the kernel doesn't use specific ATA commands which are known to cause problems.

in the tabook i didn't find any specification of the SATA bridge. it would be interesting:
1) what type it is
2) if it is fixed on the mainboard or if it is possible to solder in a new one

----

Another interesting question is whether these ThinkPads can be hacked to accept a real SATA system disk, by bypassing the SATA-to-PATA bridge (this would probably involve some soldering and cutting). If the BIOS can also handle that then it may come in handy, since some new high-capacity 2.5" disks have only SATA versions.
--[[User:Thinker|Thinker]] 02:56, 8 Oct 2005 (CEST)

----

'''Z series'''

Since the Z series uses a SATA controller and disk, without the bridge, would it be possible to make SATA ATAPI support as a module that you could load only when using the optical drive? Then, for everyday use, the experimental options of PATA and ATAPI with ata_piix would not be needed, moving you one step further in the direction of stability.

----

I have an R52 with Ubuntu Breezy and no problems with SATA (I personally asked the developers to include the needed patches).

However, I'd like to know wheter there are any advantages with this configuration. Future proof? Power saving? Speed?

Anybody cares to comment?

-- [[User:Micampe|Michele]]

Straight SATA, like in the Z60m/t, will provide better upgrade options in the long run (the hard disk industry is slowly but surely moving to SATA), and maybe a small performance increase if your drive, controller and OS support command queueing (they probably don't). However, with the hybrid ThinkPad models that use a SATA-to-PATA bridge, like your R52, you get all the drawbacks and none of the benefits; plus there's the horrible issue with [[Problem with non-ThinkPad hard disks|drive compatibility]]. My impression is that Lenovo did this just as a convenient (for them!) transition path, in order to use new chipsets without comitting to (temporarily) scarcer and more expensive drives. In any case, they didn't even have the decency to make the UltraBay Slim accept SATA drives.

--[[User:Thinker|Thinker]] 18:10, 3 Nov 2005 (CET)
----
There is a [[UltraBay Slim SATA HDD Adapter]], but only compatible with the Z series (at least for the moment).

--[[User:Tonko|Tonko]] 03:12, 4 Nov 2005 (CET)

== updated libata_passthru.patch ==

FYI: when using the Suspend-to-RAM patch from http://lkml.org/lkml/2005/9/23/97 against 2.6.14 the libata_passthru.patch from the article doesn't apply any more, so I've put up an updated version at http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch

I give no warranties whatsoever whether it works or kills your hardware, but since I just removed duplicate parts already in the Suspend-to-RAM patch it should be ok.

--[[User:spiney|spiney]] 19:04, 4 Nov 2005 (CET)

Hi

Running 2.6.16-rc4 and I'm running into scsci errors and Input/output
errrors when resuming from suspend to ram. The suspend patch is
supposed to be in 2.6.16-rc1 and I'm booting with

title= 2.6.16-rc4
root (hd0,0)
kernel /boot/kernel-2.6.16-rc4 root=/dev/sda3 ro combined_mode=libata
libata.atapi_enabled=1 acpi_sleep=s3_bios processor.max_cstate=2
elevator=cfq ide1=noprobe

Thanks.

----

Don't know about -rc4, but -rc3 worked without problems, could you try that one instead? Maybe there was some bug introduced between these two versions. What's combined_mode=libata BTW?

--[[User:Spiney|spiney]] 08:28, 23 February 2006 (CET)
----

== ATA_ENABLE_PATA PCI IDs ==

Spiney, could you extend the article to explain what and why are the PCI IDs in the footnote about ATA_ENABLE_PATA?

--[[User:Thinker|Thinker]] 21:59, 4 Nov 2005 (CET)
----

Ok, done, feel free to fix the table because I'm a bit struggling with Wiki-style editing. ;) As for the why, those PCI IDs are the only ones affected by the ATA_ENABLE_PATA, as seen in {{path|drivers/scsi/ata_piix.c}} in the kernel source.

--[[User:spiney|spiney]] 11:19, 5 Nov 2005 (CET)
----

Will other cards work without ATA_ENABLE_PATA, or just fail? In the former case your instructions are right, but in the latter case we should tell the user to check the list of IDs in his ''current'' kernel and, if there's no match, to give up in the first place instead of following the rest of the instructions.

--[[User:Thinker|Thinker]] 12:48, 5 Nov 2005 (CET)
----

AFAICT if the chipset is supported by libata it will work, regardless of what low-level driver is used. Of course if there is no low-level driver for the chipset then even using the harddisk via libata will fail, but that's a different story. At least ATA_ENABLE_PATA will then make no difference since it's Intel PIIX (and compatible) only.

--[[User:spiney|spiney]] 13:24, 5 Nov 2005 (CET)
----

Not sure I got you. Is there any case where the instructions will work without ATA_ENABLE_PATA, given that all ThinkPad optical drives are PATA?

--[[User:Thinker|Thinker]] 13:41, 5 Nov 2005 (CET)
----

The instructions will work without ATA_ENABLE_PATA unless the Thinkpad uses one of the three chipsets listed in the article, as long as libata works at all, i.e. the system drive shows up as /dev/sda. The #define doesn't change the behaviour of libata for any other chipset, it's [http://linux.yyz.us/sata/sata-status.html#ich5 ata_piix] only.

Since I don't have a machine with one of the three chipsets (anyone?), I can't tell whether those work at all with libata, but I guess there's a reason why they're not enabled by default. It's just that defining ATA_ENABLE_PATA is only making sense for these three chipsets.

Any clearer now? If not, just run {{cmd|grep -r ATA_ENABLE_PATA /path/to/kernelsource|}} and see how seldom and where the #define is used.

--[[User:spiney|spiney]] 14:55, 5 Nov 2005 (CET)
----

All clear now. I thought it will work only if you have these chipsets ''and'' ATA_ENABLE_PATA=1. Thanks for the explanation!

--[[User:Thinker|Thinker]] 15:12, 5 Nov 2005 (CET)
----

Does any of the relevant ThinkPad models (listed in the article) use these chips? They look too old to be found on the SATA models.

--[[User:Thinker|Thinker]] 23:35, 9 Nov 2005 (CET)
----

I don't think so, I was about to add "in the unlikely event that you own one of these chipsets" or something.

--[[User:Spiney|spiney]] 07:56, 10 Nov 2005 (CET)
----

== DVD DMA with ide/sata as module ==

Did anyone get DVD DMA to work with either the IDE or SATA drivers compiled as modules? If so, please fill in the missing details in that section. I have it working only with both IDE and SATA built-in.

--[[User:Thinker|Thinker]] 17:58, 16 Nov 2005 (CET)
----

Basically using a Live-CD with a recent kernel (is there one with 2.6.14 already?) would be sufficient, since they usually use an initrd or something similar, don't they? I'll give the Debian distribution kernel a try when I get around to it (bit busy atm), after all there's 2.6.14 in sid.

But for people using their own kernel compiled from source I see no point in doing the module+initrd thing anyway, unless you want LVM for the root filesystem or other funky stuff.

--[[User:Spiney|spiney]] 19:22, 16 Nov 2005 (CET)
----

Hi

Can anyone tell me how those modules are called?

Thomas
--[[User:Thomas|thomas]] 19:48, 23 Jan 2006 (CET)
----

Hi, I have problems with kernel 2.6.14.6 and libata passthrough. After executing twice the command "cdrecord --scanbus" as root, I get the following message many times in dmesg: "sr 1:0:0:0: timing out command, waited 0s".

--[[User:Whoopie|Whoopie]] 12:53, 14 February 2006 (CET)

User talk:Dclatot

2006-02-22T22:56:10Z

Spiney:

I'd suggest you open up a terminal, type
man bash
and look up the sentence "The environment for any simple command or function may be augmented temporarily by prefixing it with parameter assignments, as described above in PARAMETERS. These assignment statements affect only the environment seen by that command." Or the section "Simple commands & pipelines" in
man zshall
in case you're using zsh. Feel free to read the manual of YOUR shell and find the appropriate documentation. And then try to understand it.

Thank you very much.

--[[User:Spiney|spiney]] 23:56, 22 February 2006 (CET)
----

Script for enabling the fingerprint reader with BioAPI

2006-02-22T22:46:55Z

Spiney: /* The script */ ok, let's play ping pong, undid Dcalot's change again

Using the [[Integrated Fingerprint Reader|integrated fingerprint reader]] under Linux is currently a fairly complicated [[How to enable the fingerprint reader|process]]. The following script automates the installation of the fingerprint software, for some Linux distributions. It covers most components (bioapi framework, driver, pam_bioapi, PAM setup, USB device permissions pamtester and enrolling), and handles all the downloading, patching and installation.

Usage: just copy into a file and run as root.

After installation, all PAM-enabled system functions will use the fingerprint reader (and if it fails, default to the usual password entry). This includes:
* KDE's KDM login (enter an empty password, then swipe finger)
* KDE's screensaver (enter an empty password, then swipe finger)
* Gnome's GDM login
* <tt>su</tt>
* <tt>sudo</tt>

Everything is intalled into {{path|/opt/bioapi}}, so it doesn't pollute your filesystem. The only files affected outside {{path|/opt/bioapi}} are the ldconfig configuration, PAM configuration, {{path|/etc/rc.local}} and a few symlinks in {{path|/lib/security}}.

For details, manual installation and hints for other distributions, see [[How to enable the fingerprint reader]].

===Distributions supported by this script===
* {{Fedora}} 4

If you add support for additional distributions, please update this script (using conditionals where necessary) instead of branching it.

==The script==

<pre>
#!/bin/bash
# Install UPEK fingerprint reader driver and associated software on Linux systems.
# Source: http://thinkwiki.org/wiki/Script_for_enabling_the_fingerprint_reader

set -e -E -x -u # verbose, abort if anything fails

WHERE=/opt/bioapi
PASSWD_ENROLLS=0 # should "passwd" do fingerprint enrollment (always)?

########################################
# Install bioapi:

mkdir -p $WHERE
wget -N http://www.qrivy.net/~michael/blua/bioapi/bioapi-latest.tar.bz2
sha1sum --check <<EOF
932425e847449e9612c6894dcbaf44630aecfc13 bioapi-latest.tar.bz2
EOF
tar xjf bioapi-latest.tar.bz2
pushd bioapi-1.2.2
./configure --with-Qt-dir=no --prefix=$WHERE
make
make install
install -m644 include/bioapi_util.h $WHERE/include/bioapi_util.h
install -m644 include/installdefs.h $WHERE/include/installdefs.h
install -m644 imports/cdsa/v2_0/inc/cssmtype.h $WHERE/include/cssmtype.h
chmod o-w $WHERE/var/bioapi
popd

########################################
# Tell ldconfig about bioapi libraries:

[ -d /etc/ld.so.conf.d ] || { echo "Unsupported distribution: no /etc/ld.so.conf.d directory."; exit 1; }
echo $WHERE/lib > /etc/ld.so.conf.d/bioapi.conf
ldconfig
ldconfig -p | grep -q bioapi || { echo "ldconfig doesn't see bioapi"; exit 1; }

########################################
# Install UPEK driver:

wget -N http://www.upek.com/support/download/TFMESS_BSP_LIN_1.0.zip
sha1sum --check <<EOF
c73466b5c3b26415b300d5c5ffb76deaefadeb32 TFMESS_BSP_LIN_1.0.zip
EOF
mkdir -p driver
pushd driver
unzip ../TFMESS_BSP_LIN_1.0.zip
PATH="$PATH:$WHERE/bin" sh install.sh $WHERE/lib/
cd NonGUI_Sample
perl -i -pe 'print "#include <stdlib.h>\n//DISABLED: " if m!^#include "port/bioapi_port.h"$!' main.c
gcc -o Sample main.c -I$WHERE/include -L$WHERE/lib -lbioapi100 -DUNIX -DLITTLE_ENDIAN
install Sample -m755 $WHERE/bin/upek-NonGUI_Sample
popd

SERIAL=`$WHERE/bin/BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"`

########################################
# Install (patched) pam_bioapi:

wget -N http://www.qrivy.net/~michael/blua/pam_bioapi/pam_bioapi-latest.tar.bz2
wget -N http://badcode.de/downloads/fingerprint.patch
sha1sum --check <<EOF
a0bdf3436e55f7dc8b4795243f08a4c9b399dec8 pam_bioapi-latest.tar.bz2
619254a5bcd3acb8bf1d72b15ea69bfe00f0f064 fingerprint.patch
EOF
tar xjvf pam_bioapi-latest.tar.bz2
pushd pam_bioapi-0.2.1
patch -p0 < ../fingerprint.patch
CPPFLAGS="-I$WHERE/include" LDFLAGS="-L$WHERE/lib" ./configure --prefix=$WHERE
make
make install
ln -vfs $WHERE/lib/security/pam_bioapi.so* /lib/security/
popd

########################################
# Install pamtester:

wget http://mesh.dl.sourceforge.net/sourceforge/pamtester/pamtester-0.1.2.tar.gz
sha1sum --check <<EOF
33bcc610d7f208b50a0a23c144bdbd1e2cae4ac6 pamtester-0.1.2.tar.gz
EOF
tar xzvf pamtester-0.1.2.tar.gz
pushd pamtester-0.1.2
./configure --prefix=$WHERE
make
make install
popd

########################################
# Configure pam to use pam_bioapi:

grep -q 'Fedora Core release 4' /etc/redhat-release || { echo \
"I don't know how to configure PAM on this distribution.
See: http://thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader#Configuring_pam";
exit 1; }

PAMFILE=/etc/pam.d/system-auth
if ! grep -q 'pam_bioapi\.so' $PAMFILE; then
perl -i -pe '
if (!$a && m/^auth.*pam_unix\.so/) {$a=1; print
"auth sufficient pam_bioapi.so '$SERIAL' /etc/bioapi/pam/\n"}
' $PAMFILE
if [ $PASSWD_ENROLLS == 1 ]; then
perl -i -pe '
if (!$p && m/^password/) {$p=1; print
"password required pam_bioapi.so '$SERIAL' /etc/bioapi/pam/\n"}
' $PAMFILE
fi
fi

########################################
# USB permissions (set now and add to startup):

RC_FILE=/etc/rc.local
SET_PERMS=$WHERE/bin/set_fingerprint_perms

cat > $SET_PERMS <<'EOF'
#!/bin/bash
# Make fingerprint reader USB device world-writable:
chmod -R a+X /proc/bus/usb
chmod 666 /proc/bus/usb/`/sbin/lsusb | sed -ne "/0483:2016/s/Bus\ $.*$\ Device\ $.*$:\ .*/\1\/\2/p"`
EOF
chmod 755 $SET_PERMS

$SET_PERMS

[ -e $RC_FILE ] || { echo "No $RC_FILE, can't handle this distribution."; exit 1; }
if ! grep -q 0483:2016 $SET_PERMS; then
echo $SET_PERMS >> $RC_FILE
fi

########################################
# Enroll:

mkdir -p /etc/bioapi/pam/$SERIAL
pushd /etc/bioapi/pam/$SERIAL
read -p "Now enroll all relevant Unix accounts (press Enter to start)."
$WHERE/bin/upek-NonGUI_Sample
popd

########################################
# Done:

set +x
cat<<EOF

Success.
* To test the fingerprint-enabled PAM login, run:
$WHERE/bin/pamtester -v login USERNAME authenticate
* Add the following command to your resume-from-suspend script:
$WHERE/bin/set_fingerprint_perms

EOF
</pre>

==Ideas for improvement==
* Support more distributions
* Minimize changes to {{path|/etc/pam.d/system-auth}} by creating a separate file (e.g., {{path|/etc/pam.d/bioapi-auth}}) and <tt>@include</tt>-ing it.
* Do something about {{path|/etc/pam.d/sshd}} - it invokes {{path|/etc/pam.d/system-auth}} by stacking, so remote SSH logins now invoke the fingerprint reader... See related discussion in [[How_to_enable_the_fingerprint_reader]].
* Install and configure a patched xscreensaver (as explained in [[How_to_enable_the_fingerprint_reader]]).
* Add "<tt>OnResume 10 /opt/bioapi/bin/set_fingerprint_perms</tt>" to [[Software Suspend 2|suspend2]]'s {{path|/etc/hibernate/hibernate.conf}}?

[[Category:Scripts]]

User talk:Akw

2006-02-22T18:43:00Z

Spiney: /* Backups */

Has anybody got useful suggestions?
Feel free to tell them!

--[[User:Akw|akw]] 11:46, 25 Sep 2004 (CEST)
----

== Suggestion: Introduction of Model-Type Categories ==

Hei,

first, thx for sysoping me. I feel honored. ;)

I just thought that we could have categories representing the TP models (not too detailed)...like
ThinkpadR50, ThinkpadT40p, ThinkpadA21 and so on.

This way we could add the specs, install notes and other pages to the according models category and this way provide a means of crossreferenced "show me all info about my model" access.

What do you think?

[[User:Wyrfel|Wyrfel]] 12:13, 25 Sep 2004 (CEST)

We could add the category views to the List in the Models section, since the specs are only attached to the model-numbers, not to the general name of the models.

[[User:Wyrfel|Wyrfel]] 12:16, 25 Sep 2004 (CEST)
----
Yes, that's a good idea, let's do it. I like the mediawiki category concept.

--[[User:Akw|akw]] 13:01, 25 Sep 2004 (CEST)
----

Hei, it works great.

Seems like we got a good start. ;-)
I mean, two days and we already have some really useful cross reference information gathering functionality!

However, i have three general issues we should make decisions about:

#If we rename all the Model categories to just T40, 600, X23, they would not all be sorted under T in the Models category, hence leading to better organisation. The backdrawing is that this causes them to spread out in the category listing that one can get by clicking on the Categories link of categorised pages. I think the advantage is bigger than the backdrawing, right? (Good that i just added a lot of them to different pages. ;) )
#We are using these strange not very expressive internal link names. Mediawiki seems to handle expressive names quite well, so shouldn't we just use real page titles as their links? Makes things easier for editors, makes things more readable in Category views and finally gives us nicer titles to the pages.
#Is there a way here to get some kind of back-buttons automatically included into the pages? I've seen that the wiki does this on subpages of userpages, but i tried giving hirarchical link structures (with slashes) in the install section and it didn't work the same way. Else i think we should sooner or later start including them by hand.

Greets...[[User:Wyrfel|Wyrfel]] 19:38, 25 Sep 2004 (CEST)
----
Hi,
I think so too, hope some others from the mailing list will join the building process.

Issues:
#Renaming of the model categories: I think it's a good idea! I see if I can patch the mediawiki software to the the Categories link point to ''Category:Main_Page''. I don't like the ''Special:Categories'' anyway, because it shows no treeview.
#awful pagenames: YES! ''T40psidInstallation'' could be also ''Installing Debian/Sid on a T40p''. Would be much nicer. :-)
#back-buttons:I don't know if there is an automatically working template or something. I will find it out.

By the way: I saw you are experimenting with designs for the mainpage. My approach was just a quick hack (basically copying from wikipedia..)
So if you have something nice-looking, just apply it! :-)

See you, [[User:Akw|akw]] 13:13, 26 Sep 2004 (CEST)
----

Hi,

ok, i'll start adjusting pages then. I agree to your point about the Category view...having the Link point to Categories:Main_Page would be nicer.

Concerning the designs...i'd like to experiment a bit more before applying it to the page...not really satisfied so far. However - i got used to your block layout. ;)

[[User:Wyrfel|Wyrfel]] 13:28, 26 Sep 2004 (CEST)
----
* [[:Category:Main_Page]] ''link patch'': done.

--[[User:Akw|akw]] 14:09, 26 Sep 2004 (CEST)
----

Great work. I think we are through with point 1 and 2 now.

The Category-Main page looks nice with the pic. I thought that we could add a specific picture to each Models category page. Would be nice.
I started gathering pictures the like of yours (white background, isometric perspective). I could scale them to a standard size.
Do you have any idea where i could find them all at once or more quickly than searching google images?
(Also thought about creating icons for the main page, but that will take a while (to be expected in november the earliest.)

[[User:Wyrfel|Wyrfel]] 15:28, 26 Sep 2004 (CEST)
----

Hei,

i just transformed all the distro pages into categories, gives similar advantages as with the ThinkPad models. Also relayouted them a bit while at it.

The bad news is that today is the last day i can do something, probably until middle of october, since the Telekom doesn't manage to give me a new phoneline in time, and from 6th to 12th i'll be in holidays. So good luck...i hope i get the line earlier, but you know the Telekom, i guess.

[[User:Wyrfel|Wyrfel]] 12:16, 29 Sep 2004 (CEST)
----
Hi Wyrfel,

YES... I know the Telekom... Happy holidays, anyway :-) Thanks for all the work.

Ciao, [[User:Akw|akw]] 12:54, 29 Sep 2004 (CEST)
----

== dynamic 3Dfps ==

Hei,

great work you did there again! Some suggestions: A sorting mechanism would be nice (best via up and down arrows on the table headers like in gtk apps) and a filter functionality (via select boxes in the table headers maybe?).
Also, the dynamic page doesn't have a talk page associated, do you think you might be able to move it there?

Best wishes...
[[User:Wyrfel|Wyrfel]] 01:48, 13 Oct 2004 (CEST)
----
* Sorting/Filtering: Yes, I thought about that, too: I will do it when I find time.
* Talk page: Unfortunately, "SpecialPages" cannot have discussion. So I put the discussion on the Header-Template ([[Template:Benchmarks_Header]]) which appears on the top of [[Special:Benchmarks]].
--[[User:Akw|akw]] 12:59, 14 Oct 2004 (CEST)
----
I finished sorting and filtering now. Just have a look at it. :-)

--[[User:Akw|akw]] 21:54, 15 Oct 2004 (CEST)
----

I'm impressed. ;) Really.
Do you do something in the web area professionally?
----
Thanks!
Not yet, I am still a student, but I hope I'll get my studies finished in March/April 2005.

--[[User:Akw|akw]] 15:19, 16 Oct 2004 (CEST)
----

== edit page modding? ==

Hei,

can you tell me how i can change the edit pages footer? Can't find any info about it and would like to put the policies page there. Is there a special template for this?

[[User:Wyrfel|Wyrfel]] 06:41, 29 Dec 2004 (CET)
----
Hmm, don't know. I'll have a look.. Thanks for creating [[Help:Editing]], that's great! Have a happy new year!

--[[User:Akw|akw]] 20:31, 30 Dec 2004 (CET)
----

You, too.

[[User:217.230.181.21|217.230.181.21]] 04:43, 31 Dec 2004 (CET)
----

Hei, please let the logo contest go until 28th of february at least, i'd like to submit something, but I'll be on holidays until 23rd. ;-)

[[User:Wyrfel|Wyrfel]] 03:34, 27 Jan 2005 (CET)
----
Hi [[User:Wyrfel|Wyrfel]],

superb! that's great!

--[[User:Akw|akw]] 10:20, 28 Jan 2005 (CET)
----

----
Hei,

could you please update the MediaWiki to at least 1.4? We have the problem that one can't use the same template more than 5 times on one page. This is fixed since 1.4. Thanks a lot.

[[User:Wyrfel|Wyrfel]] 03:00, 2 May 2005 (CEST)
----

== R51p?? ==

Are you sure the 'R51p' exists?

There is no mention of it on the IBM support site, and tabook.pdf, trwbook.pdf, tawbook.pdf or twbook.pdf also does not mention it.

----
You're right, removed it.

[[User:Wyrfel|Wyrfel]] 13:02, 5 May 2005 (CEST)
----

===ThinkWiki Update===
This is great! Thanks a lot. Unfortunately i can't help with the mod_rewrite problem. At work we had trouble with it as well, but i don't know any details about it. Good luck!

[[User:Wyrfel]] 12:46, 12 May 2005 (CEST)

Me agian. ;-) Just wanted to thank you for fixing the image display. (In case this happend accidentially...some images weren't found after the update. It seems to work for all of them now again.)

[[User:Wyrfel|Wyrfel]] 02:31, 20 May 2005 (CEST)
----

== page moves/deletes ==

Can you move the following pages:

These machines where marketed with lower-case 'c'
*360CS -> 360Cs
*750CS -> 750Cs
*755CS -> 755Cs
All the Other 'CS' where marketed with upper-case, so they are fine.

Also can you delete the '701' page, it never existed as discussed on its talk page.

----
Did these. We also have a mention of a 750e on the [[750 Family Device Support in Linux]] page. This doesn't have a category page, yet and information seems hard to gather. Tonko, if you know anything about it..... ;-)

[[User:Wyrfel|Wyrfel]] 00:05, 27 May 2005 (CEST)

----
I guess you mean the reference to a '750Ce'. I can find no reference to it in tabook, and also my EMEA references make no mention of it, so I doubt it was sold in either the Americas or EMEA. Could this simply be confusion with the 755CE?

Tonko
----
Can you delete the '365' page, such a machine did not exist. 
What did exist was the 365CS, 365C, 365CSD and 365CD for which I created pages.

Also are you sure the 700T existed? it is not in twbook, and my EMEA references do not have it either.

Tonko
----
===Vandalism & Spamming===
Hei,

is there a way you can delete the Vova22 and Vova38 user accounts? They have been used for spamming only.

Also, since we get the same kind of spamming attacs over and over again now and the responsible person uses different IPs, is there a way to prevent edits based on their content?

Regards,
[[User:Wyrfel|Wyrfel]] 03:36, 13 Oct 2005 (CEST)
----

My guess is that this guy is probably using an anonymous proxy such as http://tor.eff.org/ such that his IP address is different each time.
blocking the IP as such has little effect. Not sure what can be done about it, perhaps as you said we can try to block specific content but that just gets us in the same game spam blockers are in.

Another option would be to require users to login to edit pages, and make it such that bots cannot be used to create userids. But again, I am not sure that is the right option either. But looking at the changes made, the vast majority of valid changes seem to come from people who have a userid...

--[[User:Tonko|Tonko]] 15:25, 13 Oct 2005 (CEST)
----
I don't like requiring people to login to edit, but it might be worth thinking about if one can really keep bots from creating accounts. However, this would still allow real person vandalism and we would end up with junk user accounts that are not easy to remove. Also, how would we prevent bots from creating accounts? I do not like the "type the number in the picture below" kind of thing.

I was thinking about something like if a certain text is included in the edit, the whole edit would be rejected or offered for reediting. This way we would only have to maintain a list of links (or even domains) that we don't want to have here. Our job would not be as tough than that of spam blockers, cause we have a limited content target and hence can be sure that certain content is to be excluded.

[[User:Wyrfel|Wyrfel]] 17:28, 13 Oct 2005 (CEST)
----
For the moment I have protected the Help:Contents page since it seems to be a constant target, and I suspect it is a bot using an anonymous proxy.

--[[User:Tonko|Tonko]] 22:43, 13 Oct 2005 (CEST)
----
Sounds reasonable. I think we can even keep it protected, because standard users normally don't edit there. [[User:Wyrfel|Wyrfel]] 02:46, 14 Oct 2005 (CEST)
----

== Yet another MediaWiki upgrade ==

Hi Akw,

Thanks for running this great site! It really changed the "ThinkPad experience" for me.

There were several MediaWiki security updates released since the present version 1.4.4, and the new MediaWiki 1.5.x offers some nifty features like diff during preview. Any chance of an upgrade?
----
Maybe I try the upgrade for christmas ;-)

--[[User:Akw|akw]] 12:59, 26 Nov 2005 (CET)
----

I'm trying to provide variable-width notes using the conditional templates ("Template:If defined" etc.) from Wikipedia, but they don't work on ThinkWiki. I guess this is also because of the old MediaWiki version...

--[[User:Thinker|Thinker]] 04:08, 27 Dec 2005 (CET)
----

== Spam filtering ==

Judging by the weather, it must be spam season. Maybe it's possible to reject or silently drop posts based on strings/regexps? Most recent spam seems to have been posted by the same tool, whose favoriate conversation piece are

<pre>
<div id="zuenwa1651" style="overflow: auto; height: 1px;">
</pre>
and
<pre>
<div class=exf align='center' style='overflow:auto; height: 1px;'>
</pre>

Maybe this will buy us some quiet (until the next step in the spammers vs. humans arms race).

--[[User:Thinker|Thinker]] 23:37, 10 Dec 2005 (CET)
----

Perhaps it is possible to use $wgSpamBlacklist to setup a regex that blocks the most common spam keywords?

http://meta.wikimedia.org/wiki/Anti-spam_Features

--[[User:Tonko|Tonko]] 03:11, 18 Dec 2005 (CET)
----

Good idea, I'll check that tonight or tomorrow.

--[[User:Akw|akw]] 17:02, 19 Dec 2005 (CET)

== file uploads disabled ==

Hi,

As I mentioned already on the [[Issues with the Wiki]] page, file uploads are disabled.

--[[User:Tonko|Tonko]] 15:21, 15 January 2006 (CET)

Thank you, I fixed this now.

--[[User:Akw|akw]] 18:11, 15 January 2006 (CET)
----

== Backups ==

Just wondering - is there presently some mechanism for off-site backup of all content (database, images, configuration)? If not, I can help with that.

--[[User:Thinker|Thinker]] 20:57, 10 February 2006 (CET)
----

Given the recent database trouble, I'm becoming a bit concerned for our data... What's the situation backup-wise? My offer of help still stands.

--[[User:Thinker|Thinker]] 18:02, 22 February 2006 (CET)
----

Seconded, this Wiki is way too valuable to let it go up in smoke in case the server dies. So in case help is needed, just tell us. BTW, I just noticed this server is located in the same data center I have a couple of servers in, so backup wouldn't even count as 'external' traffic.

--[[User:Spiney|spiney]] 19:43, 22 February 2006 (CET)
----

User talk:Akw

2006-02-22T18:27:38Z

Spiney: /* Backups */

Has anybody got useful suggestions?
Feel free to tell them!

--[[User:Akw|akw]] 11:46, 25 Sep 2004 (CEST)
----

== Suggestion: Introduction of Model-Type Categories ==

Hei,

first, thx for sysoping me. I feel honored. ;)

I just thought that we could have categories representing the TP models (not too detailed)...like
ThinkpadR50, ThinkpadT40p, ThinkpadA21 and so on.

This way we could add the specs, install notes and other pages to the according models category and this way provide a means of crossreferenced "show me all info about my model" access.

What do you think?

[[User:Wyrfel|Wyrfel]] 12:13, 25 Sep 2004 (CEST)

We could add the category views to the List in the Models section, since the specs are only attached to the model-numbers, not to the general name of the models.

[[User:Wyrfel|Wyrfel]] 12:16, 25 Sep 2004 (CEST)
----
Yes, that's a good idea, let's do it. I like the mediawiki category concept.

--[[User:Akw|akw]] 13:01, 25 Sep 2004 (CEST)
----

Hei, it works great.

Seems like we got a good start. ;-)
I mean, two days and we already have some really useful cross reference information gathering functionality!

However, i have three general issues we should make decisions about:

#If we rename all the Model categories to just T40, 600, X23, they would not all be sorted under T in the Models category, hence leading to better organisation. The backdrawing is that this causes them to spread out in the category listing that one can get by clicking on the Categories link of categorised pages. I think the advantage is bigger than the backdrawing, right? (Good that i just added a lot of them to different pages. ;) )
#We are using these strange not very expressive internal link names. Mediawiki seems to handle expressive names quite well, so shouldn't we just use real page titles as their links? Makes things easier for editors, makes things more readable in Category views and finally gives us nicer titles to the pages.
#Is there a way here to get some kind of back-buttons automatically included into the pages? I've seen that the wiki does this on subpages of userpages, but i tried giving hirarchical link structures (with slashes) in the install section and it didn't work the same way. Else i think we should sooner or later start including them by hand.

Greets...[[User:Wyrfel|Wyrfel]] 19:38, 25 Sep 2004 (CEST)
----
Hi,
I think so too, hope some others from the mailing list will join the building process.

Issues:
#Renaming of the model categories: I think it's a good idea! I see if I can patch the mediawiki software to the the Categories link point to ''Category:Main_Page''. I don't like the ''Special:Categories'' anyway, because it shows no treeview.
#awful pagenames: YES! ''T40psidInstallation'' could be also ''Installing Debian/Sid on a T40p''. Would be much nicer. :-)
#back-buttons:I don't know if there is an automatically working template or something. I will find it out.

By the way: I saw you are experimenting with designs for the mainpage. My approach was just a quick hack (basically copying from wikipedia..)
So if you have something nice-looking, just apply it! :-)

See you, [[User:Akw|akw]] 13:13, 26 Sep 2004 (CEST)
----

Hi,

ok, i'll start adjusting pages then. I agree to your point about the Category view...having the Link point to Categories:Main_Page would be nicer.

Concerning the designs...i'd like to experiment a bit more before applying it to the page...not really satisfied so far. However - i got used to your block layout. ;)

[[User:Wyrfel|Wyrfel]] 13:28, 26 Sep 2004 (CEST)
----
* [[:Category:Main_Page]] ''link patch'': done.

--[[User:Akw|akw]] 14:09, 26 Sep 2004 (CEST)
----

Great work. I think we are through with point 1 and 2 now.

The Category-Main page looks nice with the pic. I thought that we could add a specific picture to each Models category page. Would be nice.
I started gathering pictures the like of yours (white background, isometric perspective). I could scale them to a standard size.
Do you have any idea where i could find them all at once or more quickly than searching google images?
(Also thought about creating icons for the main page, but that will take a while (to be expected in november the earliest.)

[[User:Wyrfel|Wyrfel]] 15:28, 26 Sep 2004 (CEST)
----

Hei,

i just transformed all the distro pages into categories, gives similar advantages as with the ThinkPad models. Also relayouted them a bit while at it.

The bad news is that today is the last day i can do something, probably until middle of october, since the Telekom doesn't manage to give me a new phoneline in time, and from 6th to 12th i'll be in holidays. So good luck...i hope i get the line earlier, but you know the Telekom, i guess.

[[User:Wyrfel|Wyrfel]] 12:16, 29 Sep 2004 (CEST)
----
Hi Wyrfel,

YES... I know the Telekom... Happy holidays, anyway :-) Thanks for all the work.

Ciao, [[User:Akw|akw]] 12:54, 29 Sep 2004 (CEST)
----

== dynamic 3Dfps ==

Hei,

great work you did there again! Some suggestions: A sorting mechanism would be nice (best via up and down arrows on the table headers like in gtk apps) and a filter functionality (via select boxes in the table headers maybe?).
Also, the dynamic page doesn't have a talk page associated, do you think you might be able to move it there?

Best wishes...
[[User:Wyrfel|Wyrfel]] 01:48, 13 Oct 2004 (CEST)
----
* Sorting/Filtering: Yes, I thought about that, too: I will do it when I find time.
* Talk page: Unfortunately, "SpecialPages" cannot have discussion. So I put the discussion on the Header-Template ([[Template:Benchmarks_Header]]) which appears on the top of [[Special:Benchmarks]].
--[[User:Akw|akw]] 12:59, 14 Oct 2004 (CEST)
----
I finished sorting and filtering now. Just have a look at it. :-)

--[[User:Akw|akw]] 21:54, 15 Oct 2004 (CEST)
----

I'm impressed. ;) Really.
Do you do something in the web area professionally?
----
Thanks!
Not yet, I am still a student, but I hope I'll get my studies finished in March/April 2005.

--[[User:Akw|akw]] 15:19, 16 Oct 2004 (CEST)
----

== edit page modding? ==

Hei,

can you tell me how i can change the edit pages footer? Can't find any info about it and would like to put the policies page there. Is there a special template for this?

[[User:Wyrfel|Wyrfel]] 06:41, 29 Dec 2004 (CET)
----
Hmm, don't know. I'll have a look.. Thanks for creating [[Help:Editing]], that's great! Have a happy new year!

--[[User:Akw|akw]] 20:31, 30 Dec 2004 (CET)
----

You, too.

[[User:217.230.181.21|217.230.181.21]] 04:43, 31 Dec 2004 (CET)
----

Hei, please let the logo contest go until 28th of february at least, i'd like to submit something, but I'll be on holidays until 23rd. ;-)

[[User:Wyrfel|Wyrfel]] 03:34, 27 Jan 2005 (CET)
----
Hi [[User:Wyrfel|Wyrfel]],

superb! that's great!

--[[User:Akw|akw]] 10:20, 28 Jan 2005 (CET)
----

----
Hei,

could you please update the MediaWiki to at least 1.4? We have the problem that one can't use the same template more than 5 times on one page. This is fixed since 1.4. Thanks a lot.

[[User:Wyrfel|Wyrfel]] 03:00, 2 May 2005 (CEST)
----

== R51p?? ==

Are you sure the 'R51p' exists?

There is no mention of it on the IBM support site, and tabook.pdf, trwbook.pdf, tawbook.pdf or twbook.pdf also does not mention it.

----
You're right, removed it.

[[User:Wyrfel|Wyrfel]] 13:02, 5 May 2005 (CEST)
----

===ThinkWiki Update===
This is great! Thanks a lot. Unfortunately i can't help with the mod_rewrite problem. At work we had trouble with it as well, but i don't know any details about it. Good luck!

[[User:Wyrfel]] 12:46, 12 May 2005 (CEST)

Me agian. ;-) Just wanted to thank you for fixing the image display. (In case this happend accidentially...some images weren't found after the update. It seems to work for all of them now again.)

[[User:Wyrfel|Wyrfel]] 02:31, 20 May 2005 (CEST)
----

== page moves/deletes ==

Can you move the following pages:

These machines where marketed with lower-case 'c'
*360CS -> 360Cs
*750CS -> 750Cs
*755CS -> 755Cs
All the Other 'CS' where marketed with upper-case, so they are fine.

Also can you delete the '701' page, it never existed as discussed on its talk page.

----
Did these. We also have a mention of a 750e on the [[750 Family Device Support in Linux]] page. This doesn't have a category page, yet and information seems hard to gather. Tonko, if you know anything about it..... ;-)

[[User:Wyrfel|Wyrfel]] 00:05, 27 May 2005 (CEST)

----
I guess you mean the reference to a '750Ce'. I can find no reference to it in tabook, and also my EMEA references make no mention of it, so I doubt it was sold in either the Americas or EMEA. Could this simply be confusion with the 755CE?

Tonko
----
Can you delete the '365' page, such a machine did not exist. 
What did exist was the 365CS, 365C, 365CSD and 365CD for which I created pages.

Also are you sure the 700T existed? it is not in twbook, and my EMEA references do not have it either.

Tonko
----
===Vandalism & Spamming===
Hei,

is there a way you can delete the Vova22 and Vova38 user accounts? They have been used for spamming only.

Also, since we get the same kind of spamming attacs over and over again now and the responsible person uses different IPs, is there a way to prevent edits based on their content?

Regards,
[[User:Wyrfel|Wyrfel]] 03:36, 13 Oct 2005 (CEST)
----

My guess is that this guy is probably using an anonymous proxy such as http://tor.eff.org/ such that his IP address is different each time.
blocking the IP as such has little effect. Not sure what can be done about it, perhaps as you said we can try to block specific content but that just gets us in the same game spam blockers are in.

Another option would be to require users to login to edit pages, and make it such that bots cannot be used to create userids. But again, I am not sure that is the right option either. But looking at the changes made, the vast majority of valid changes seem to come from people who have a userid...

--[[User:Tonko|Tonko]] 15:25, 13 Oct 2005 (CEST)
----
I don't like requiring people to login to edit, but it might be worth thinking about if one can really keep bots from creating accounts. However, this would still allow real person vandalism and we would end up with junk user accounts that are not easy to remove. Also, how would we prevent bots from creating accounts? I do not like the "type the number in the picture below" kind of thing.

I was thinking about something like if a certain text is included in the edit, the whole edit would be rejected or offered for reediting. This way we would only have to maintain a list of links (or even domains) that we don't want to have here. Our job would not be as tough than that of spam blockers, cause we have a limited content target and hence can be sure that certain content is to be excluded.

[[User:Wyrfel|Wyrfel]] 17:28, 13 Oct 2005 (CEST)
----
For the moment I have protected the Help:Contents page since it seems to be a constant target, and I suspect it is a bot using an anonymous proxy.

--[[User:Tonko|Tonko]] 22:43, 13 Oct 2005 (CEST)
----
Sounds reasonable. I think we can even keep it protected, because standard users normally don't edit there. [[User:Wyrfel|Wyrfel]] 02:46, 14 Oct 2005 (CEST)
----

== Yet another MediaWiki upgrade ==

Hi Akw,

Thanks for running this great site! It really changed the "ThinkPad experience" for me.

There were several MediaWiki security updates released since the present version 1.4.4, and the new MediaWiki 1.5.x offers some nifty features like diff during preview. Any chance of an upgrade?
----
Maybe I try the upgrade for christmas ;-)

--[[User:Akw|akw]] 12:59, 26 Nov 2005 (CET)
----

I'm trying to provide variable-width notes using the conditional templates ("Template:If defined" etc.) from Wikipedia, but they don't work on ThinkWiki. I guess this is also because of the old MediaWiki version...

--[[User:Thinker|Thinker]] 04:08, 27 Dec 2005 (CET)
----

== Spam filtering ==

Judging by the weather, it must be spam season. Maybe it's possible to reject or silently drop posts based on strings/regexps? Most recent spam seems to have been posted by the same tool, whose favoriate conversation piece are

<pre>
<div id="zuenwa1651" style="overflow: auto; height: 1px;">
</pre>
and
<pre>
<div class=exf align='center' style='overflow:auto; height: 1px;'>
</pre>

Maybe this will buy us some quiet (until the next step in the spammers vs. humans arms race).

--[[User:Thinker|Thinker]] 23:37, 10 Dec 2005 (CET)
----

Perhaps it is possible to use $wgSpamBlacklist to setup a regex that blocks the most common spam keywords?

http://meta.wikimedia.org/wiki/Anti-spam_Features

--[[User:Tonko|Tonko]] 03:11, 18 Dec 2005 (CET)
----

Good idea, I'll check that tonight or tomorrow.

--[[User:Akw|akw]] 17:02, 19 Dec 2005 (CET)

== file uploads disabled ==

Hi,

As I mentioned already on the [[Issues with the Wiki]] page, file uploads are disabled.

--[[User:Tonko|Tonko]] 15:21, 15 January 2006 (CET)

Thank you, I fixed this now.

--[[User:Akw|akw]] 18:11, 15 January 2006 (CET)
----

== Backups ==

Just wondering - is there presently some mechanism for off-site backup of all content (database, images, configuration)? If not, I can help with that.

--[[User:Thinker|Thinker]] 20:57, 10 February 2006 (CET)
----

Given the recent database trouble, I'm becoming a bit concerned for our data... What's the situation backup-wise? My offer of help still stands.

--[[User:Thinker|Thinker]] 18:02, 22 February 2006 (CET)
----

Seconded, this Wiki is way too valuable to let it go up in smoke in case the server dies. So in case help is needed, just tell us.

--[[User:Spiney|spiney]] 19:27, 22 February 2006 (CET)
----

Script for enabling the fingerprint reader with BioAPI

2006-02-22T18:22:34Z

Spiney: undid the last change once more, the line is correct

Problems with SATA and Linux

2006-02-20T20:22:25Z

Spiney: /* No DMA on DVD drive */ undid Waldi's edit, ATA_ENABLE_PATA has nothing to do with atapi_enabled, so don't mix those two

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Some ThinkPad models use a SATA controller for the system hard disk. This causes several complications for Linux installation. The following lists these problems and known workarounds. Note that the details are often version- and distribution-specific.

===Models using a SATA disk interface===
Models using a SATA controller and a SATA system disk:
*ThinkPad {{T60}}, {{T60p}}
*ThinkPad {{X60}}, {{X60s}}
*ThinkPad {{Z60t}}, {{Z60m}}
Models using a SATA controller and a PATA (IDE) system disk with a SATA-to-PATA bridge:
*ThinkPad {{T43}}, {{T43p}}
*ThinkPad {{R52}}
*ThinkPad {{X41}}, {{X41T}}

{{NOTE|Some of these problems (namely SMART support, power management and disk information) are solved in Linux 2.6.15 with the inclusion of libata pass-through. See the SATA driver [http://linux-ata.org/features.html features], [http://linux-ata.org/software-status.html software status] and [http://linux-ata.org/sata-status.html hardware status].}}
|}

==Hang on resume from suspend to RAM==

Linux kernels (as of 2.6.15-rc3) do not support suspend and resume for SATA devices. As a result, the machine hangs upon the first disk access after resume. A kernel patch ([http://lkml.org/lkml/2005/5/2/46 LKML posting]) fixes this by adding SATA power management support.

Current release-candidates for 2.6.16 ([http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.16-rc1 Changelog for 2.6.16-rc1]) have the patch already included], so no more patching will be necessary with 2.6.16.

===Patches===
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff Patch for kernel 2.6.12]
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.13-rc5.diff Patch for kernel 2.6.13-rc5]
* [http://lkml.org/lkml/2005/9/23/97 Patch for kernel 2.6.14]
* [http://www.xenotime.net/linux/SATA/2.6.15-rc/libata_suspend.patch Patch for kernel 2.6.15-rc4]
* [http://tpctl.sourceforge.net/tmp/sata_pm.2.6.15-rc6.patch Patch for kernels 2.6.15-rc6 through 2.6.15]

Some distributions already include this patch (e.g., {{Ubuntu}} Breezy, {{Gentoo}}'s gentoo-sources 2.6.15-r1), but some don't (e.g., {{Fedora}} 4).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169201 bug 169201: "SATA drives fail on laptop suspend"]

==Failed resume from suspend to disk==

Suspend to disk (using [[swsusp]] or [[Software Suspend 2]]) needs to load the memory image from the SATA disk. For this to work, you either need an initrd with all the necessary SATA modules, or the SATA drivers compiled into the kernel.

==DVD drive not recognized==

The <tt>ata_piix</tt> SATA driver grabs ownership over the IDE ports when it is loaded, but (by default) does not support PATA ATAPI devices such as the Ultrabay optical drives. Thus, if the <tt>ide</tt> driver is compiled as a module and loaded after <tt>ata_piix</tt>, the DVD drive will not be recognized by either driver.

Either of the following configurations will work:
* For kernel 2.6.14 and newer: enable ATAPI support in the SATA system using {{bootparm|libata.atapi_enabled|1}} (see below; this is experimental).
* Compile IDE into the kernel (non-module).
* Compile both IDE and SATA as modules and make sure IDE is loaded first (the module is called 'ide_generic').

Note that the optical drive must be in the Ultrabay during system boot (Ultrabay device swapping is currently unsupported).

==No DMA on DVD drive==

Using the IDE driver, DMA support cannot be enabled on an Ultrabay optical drive:

# hdparm -d1 /dev/hdc

/dev/hdc:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)

As a result, the optical drive is slow, and in particular, too slow to play video DVDs.

One workaround is to use employ the SATA driver (instead of the IDE driver) for the optical drive. This requires enabling two featues of the SATA driver, namely ATAPI support and PATA support, which are both in active development and far from stable. Using this will probably devour all your data and go on to eat all the food in your fridge. But if you have full backups and an empty fridge, do the following:

* Grab the latest kernel (must be 2.6.14 or newer; the relevant code is under active development).
* Do one of the following:
** Configure the SATA system (and in particular <tt>ata_piix</tt> and <tt>libata</tt>) as built-in and add {{bootparm|libata.atapi_enabled|1}} to your kernel command line (e.g., in in {{path|/boot/grub/menu.lst}}).
** Configure the SATA system as module (this is often the default) and add "<tt>options libata atapi_enabled=1</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* Do one of the following:
** Disable the IDE system.
** Build the IDE driver as built-in (this is often the default) and add the {{bootparm|hdc|noprobe}} kernel argument (e.g., in in {{path|/boot/grub/menu.lst}}).
** Build the IDE driver as module and add "<tt>options ide hdc=noprobe</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* If you chose to use modules above, regenerate your <tt>initrd</tt> file.

If this doesn't work, use {{cmd|lspci -vn|}} to check whether one of the following chipsets is used in the Thinkpad:
{| border="1" cellspacing="0" cellpadding="2"
|-
!PCI ID
!Name
|-
|8086:7111
|Intel 82371AB/EB/MB PIIX4 IDE
|-
|8086:24db
|Intel 82801EB/ER (ICH5/ICH5R) IDE Controller
|-
|8086:25a2
|Intel 6300ESB PATA Storage Controller
|}
If yes, enable support for these chipsets has to be enabled by setting
#define ATA_ENABLE_PATA
in {{path|include/linux/libata.h}} (and report your ThinkPad model in the discussion page).

There have been reports that DVD burning doesn't work under this configuration, but it seems to work with kernel 2.6.14 and later (tested on a ThinkPad {{T43}} and {{T43p}} with a [[UltraBay Slim DVD Multi-Burner Plus]]).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163418 bug 163418: "can't enable DMA on DVD drive"]

==No DMA on system hard disk==

In some Linux kernels, both the SATA driver and the IDE driver can handle the system hard disk. With the SATA driver, it shows as {{path|/dev/sda}} and DMA is enabled. With the IDE driver, it shows as {{path|/dev/hda}} and DMA is disabled.

The simplest way to enable DMA is to force the IDE driver to ignore the system hard disk by passing the {{bootparm|hda|noprobe}} kernel argument. The driver will then be handled by the SATA driver. Note that this will change its device name to {{path|/dev/sda}} (which may require changes in {{path|/etc/fstab}} and the boot loader) and may cause other problems as listed above.

(Observed on a ThinkPad T43 with Fedora Core kernel 2.6.13-1.1526_FC4.)

==No SMART support==

Prior to kernel 2.6.15, the Linux SATA system did not support SMART commands (e.g., via smartctl).

The necessary capability is "libata pass-through", which was incorporated into Linux 2.6.15-rc1 and later. A patch is available for older kernels:
* Kernel 2.6.12: http://rtr.ca/dell_i9300/kernel/kernel-2.6.12/03_libata_passthru.patch
* Kernel 2.6.13: http://rtr.ca/dell_i9300/kernel/kernel-2.6.13/02_libata_passthru.patch
* Kernel 2.6.14: http://www.foo.fh-furtwangen.de/~koenigr/02_libata_passthru.fixed.again.patch
* Kernel 2.6.14 with the above suspend-to-RAM patch: http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch

After applying the patch, run smartctl with the "-d ata" parameter:
:{{cmdroot|smartctl -d ata -a /dev/sda}}

==No disk power management==

Prior to kernel 2.6.15, the Linux SATA system did not support power management commands on these models.

The above patches for SMART support resolves this, and in particular enables the following commands:
* {{cmdroot|hdparm -y}} (spin down)
* {{cmdroot|hdparm -S num}} (automatic spin down timeout)
* {{cmdroot|hdparm -B num}} (advanced power management level)
Note that this command is still rejected:
* {{cmdroot|hdparm -M num}} (acoustic management)
(Tested with patched kernels 2.6.13.1 and 2.6.12-4 and a 60GB 7200RPM disk model HTS726060M9AT00.)

Note that even when [[Laptop-mode]] is used, the "hddtemp" daemon (as shipped with Fedora Core 4) will wake up the disk every minute, and must thus be disabled for power management to be effective. Its accesses are not visibile through the {{path|/proc/sys/vm/block_dump}} facility. It is unclear whether disk temperature can be monitored without causing the disk to spin up (on the {{T43}}, none of the {{path|/proc/acpi/ibm/thermal}} values corresponds to the disk's built-in temperature sensor).

==No disk information==

Prior to kernel 2.6.15, on these models the disk information could not be read by the standard commands such as:
*{{cmdroot|hdparm -i /dev/sda}}
*{{cmdroot|hdparm -I /dev/sda}}
The latter is fixed by the above patch for SMART support.

==No swapping of UltraBay device==

The <tt>libata</tt> driver does not yet support hot-swapping (or warm-swapping) of PATA devices. If you use a DVD or 2nd PATA HDD via the <tt>libata</tt> (SATA) driver, to swap them in or out you must power down the machine.

If you use the <tt>ide</tt> driver for a PATA UltraBay device, hot-swapping might work using <tt>hdparm</tt>, <tt>idectl</tt> or <tt>hotswap</tt> (please report). However, DMA will be disabled on these models (see above).

If you use a SATA device in the UltraBay, <tt>libata</tt> hot-swapping might work (please report).

Swapping of the [[UltraBay Slim Battery]] does work.

==BIOS error 2010 on user-installed hard disk==

While not a Linux issue, note that there is an issue with installing alternative PATA (IDE) hard disks as the system drive. Unless the disk is one of the few approved disks listed inside the BIOS, you will get an BIOS error 2010 during system boot, and the disk may operate unreliably. See [[Problem with non-ThinkPad hard disks]].

Talk:Tp smapi

2006-02-08T09:48:01Z

Spiney: /* Kernel Patch? */ addition to README file?

== Feedback ==

Great, great work! Really! This completely rocks. I just stopped my battery from charging at 77% and restarted charging a bit later, no problems whatsoever. BTW, this is on kernel 2.6.14.3.

--[[User:Spiney|spiney]] 21:25, 5 Dec 2005 (CET)
----
None of the fuctions is working on my T40, kernel 2.6.14-mm2.

--[[User:Lammic|lammic]], 2005.12.05

Works for me on a T41 running 2.6.12-10-686 (Ubuntu 5.10).

--[[User:berndtnm|berndtnm]], 2005.12.06

Including stop_charge_thresh? That one seems to be missing on the T42p.

--[[User:Thinker|Thinker]] 00:46, 7 Dec 2005 (CET)
----

tp_smapi works just fine on an R52 with Ubuntu Breezy stock kernel.

--[[User:Micampe|Micampe]] 12:52, 7 Dec 2005 (CET)

----

''To set the thresholds for starting and stopping battery charging (in percent of current capacity):''

'''current''' really? That'd be weird, I'd expect it to be percent of '''total''' capacity.

--[[User:Micampe|Micampe]] 14:39, 7 Dec 2005 (CET)

"Current full charge capacity", as opposed to "current remaining capacity" or "designed full charge capacity"...

--[[User:Thinker|Thinker]] 15:05, 7 Dec 2005 (CET)
----

Battery features don't work with my T41p. I can't check this with windows. Can anybody try these features?

-- Nils, 7 Dec 2005
----

Nils, does cdrom_speed work for you on the T41p? Could you provide the details requested in the README (dmesg etc.)?

--[[User:Thinker|Thinker]] 21:57, 7 Dec 2005 (CET)
----

CDRom Speed seems to work. (I see no warnings, but I have to do a speed test.) Now, I've send all outputs to the email-address in the readme.

-- Nils, 8 Dec 2005
----

All the features except the stop_charge_thresh seem to work here on a t42p.
One note, the start_charge_thresh seems to really be stop_charge_thresh. Ie, If I set that to lower than my current battery %, it will never charge,
and if I set it to 100 the battery charges all the way.

--[[User:Nirik|Nirik]] 16 Dec 2005
----

Nirik, "all the features" as of which version? For example, do the force_discharge{1,2} in tp_smapi 0.12 also work for you? See the table in the article page. About start_charge, that's odd. Can you send me a log of what you did, what was the result a what was the dmesg output for each operation?

--[[User:Thinker|Thinker]] 14:16, 16 Dec 2005 (CET)
----

System T40p:

<pre>
fairlight:/sys/devices/platform/smapi/BAT0# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge1
fairlight:/sys/devices/platform/smapi/BAT0# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge2
fairlight:/sys/devices/platform/smapi/BAT0# dmesg
tp_smapi: req_in: BX=2118 CX=100 DI=0 SI=0
tp_smapi: req_out: AX=8680 BX=2118 CX=100 DX=b2 DI=0 SI=0 ret=-38
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)
tp_smapi: cannot get force_discharge1 of battery 0: Function is not supported by SMAPI BIOS
tp_smapi: req_in: BX=2104 CX=100 DI=0 SI=0
tp_smapi: req_out: AX=80 BX=2103 CX=100 DX=78 DI=0 SI=0 ret=0
tp_smapi: cannot get force_discharge2 of battery 0: bx=2103
</pre>

So it seems force_discharge1 is not supported at all. But force_discharge2? By the way, i think wiki is a _very_ good idea for collecting information, but not for discussion. I would prefer a maillinglist. We can use sourceforge.

--[[User|StefanSchmidt]]

force_discharge2 is indicating a real error condition (bx=2103 which has bit 0x02 on), but I have no idea what the error is or how to fix it. Sorry. If you can trigger this function under Windows and have SoftICE or equivalent, maybe it can be worked out.

About the Wiki discussion, I'm not sure a mailing list is justified yet, but you can use the linux-thinkpad list or the e-mail address in the README.

--[[User:Thinker|Thinker]] 21:42, 16 Dec 2005 (CET)

OK, then i use linux-thinkpad to get more people involved. I'am away the next weeks, but i hope to find some time to hacking on tp_smapi.

--[[User:StefanSchmidt]]
----

Someone reported cd_speed works on T42 but on mine, it doesn't: this is 2378DXU

--[[User:eBug]] 22:55, 17 Dec 2005 (CET)
----

eBug, how does it fail? If the file doesn't exist, it means you didn't enable PROVIDE_CD_SPEED (see the README). If it does exist, can you provide the dmesg output when you read an write to the file?

--[[User:Thinker|Thinker]] 11:53, 18 Dec 2005 (CET)
----

To confirm:
tp_smapi 0.13 works with hdaps module loaded on T41 (2373-8RG). However, force_discharge*, inhibit_charge_minutes, start_charge_thresh, stop_charge_thresh don't seem to be implemented on this model.

--[[User:LJSBRokken|LJSBrokken]] 21 Dec 2005
----

tp_smapi version 0.13 with T23 (2647-3QG) (I have dual batteries)...

None of the functions which make any changes work...

<pre># cd /sys/devices/platform/smapi && cat BAT*/* > /dev/null
cat: BAT0/force_discharge1: Function not implemented
cat: BAT0/force_discharge2: Input/output error
cat: BAT0/inhibit_charge_minutes: Function not implemented
cat: BAT0/start_charge_thresh: Function not implemented
cat: BAT0/stop_charge_thresh: Function not implemented
cat: BAT1/force_discharge1: Function not implemented
cat: BAT1/force_discharge2: Input/output error
cat: BAT1/inhibit_charge_minutes: Function not implemented
cat: BAT1/start_charge_thresh: Function not implemented
cat: BAT1/stop_charge_thresh: Function not implemented</pre>

However, all the battery status information is available, and functions appear for both BAT0 and BAT1, regardless of when the UltraBay battery was inserted or ejected- this is very useful, it is the only way I can monitor my UltraBay battery unless it was present on boot.

--[[User:SystemParadox|SystemParadox]] 21:51, 4 Jan 2006 (CET)
----

SystemParadox, what's the dmesg output produced by "cat BAT0/force_discharge2"?

--[[User:Thinker|Thinker]] 22:02, 4 Jan 2006 (CET)
----

After the upgrade to 0.14 (with kernel 2.6.15, using the patch) I can't use inhibit_charge and start/stop_charge_thresh any longer (getting an input/output error), the dmesg debug output when {{cmd|cat|}}-ing those three files:

<pre>
tp_smapi: tp_smapi 0.14 loading...
tp_smapi: successfully loaded (smapi_port=0xb2).
tp_smapi: req_in: BX=2114 CX=100 DI=0 SI=0
tp_smapi: req_out: AX=ea210080 BX=ec192114 CX=c18d0700 DX=f7cc00b2 DI=f7f50000 SI=c18d0000 ret=-5
tp_smapi: SMAPI error: Unknown error code (func=2114)
tp_smapi: cannot get inhibit charge of battery 0: Unknown error code
tp_smapi: req_in: BX=2116 CX=100 DI=0 SI=0
tp_smapi: req_out: AX=c03b0080 BX=c18d2116 CX=c0160328 DX=ec7600b2 DI=ec760000 SI=a0810000 ret=-5
tp_smapi: SMAPI error: Unknown error code (func=2116)
tp_smapi: cannot get start thresh of battery 0: Unknown error code
tp_smapi: req_in: BX=211a CX=100 DI=0 SI=0
tp_smapi: req_out: AX=c03b0080 BX=c18d211a CX=c016032c DX=eb4500b2 DI=eb450000 SI=241e0000 ret=-5
tp_smapi: SMAPI error: Unknown error code (func=211a)
tp_smapi: cannot get stop thresh of battery 0: Unknown error code
</pre>

--[[User:Spiney|spiney]] 08:12, 10 Jan 2006 (CET)
----

Oops, the transition to 32-bit SMAPI calls was broken. Fixed in 0.15. Thanks for the quick report!

--[[User:Thinker|Thinker]] 12:10, 10 Jan 2006 (CET)
----

Yep, 0.15 works again. Quick response, bravo! :)

--[[User:Spiney|spiney]] 12:23, 10 Jan 2006 (CET)
----

On a T22, nothing seems to work with 0.16.

[[http://www.rafb.net/paste/results/fcUUDs49.html|dmesg output]] when doing cat *

I am using an Ultrabay2000 battery, so it would be really usefull to be able to control that

--[[User:nusse|nusse]]
----

Nusse: Not even the extended battery status? That does work on T23. About the control features, I believe they're not available on the T23; did you have any kind of (dis)charge control under WindowS?

--[[User:Thinker|Thinker]] 20:59, 11 Jan 2006 (CET)
----

I don't really know what 'extended battery' status means, but here an example:
<pre>
$ cat current_* /sys/devices/platform/smapi/BAT1
cat: current_avg: Input/output error
cat: current_now: Input/output error
</pre>
This is what happens when i cat any file in this directory and also in ../BAT1 :(

--[[User:nusse|nusse]] Thu Jan 12 22:07:26 CET 2006
----

Nusse: Yes, that's what I meant. What's the {{cmdroot|dmesg}} output generated by these commands?

--[[User:Thinker|Thinker]] 00:27, 13 Jan 2006 (CET)
----

Thinker: I attached some link to my first comment but it seems to be down and the link was wrong anyway.
<pre>
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)
tp_smapi: cannot get force_discharge of battery 0: Function is not supported by SMAPI BIOS
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2114)
tp_smapi: cannot get inhibit charge of battery 0: Function is not supported by SMAPI BIOS
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2116)
tp_smapi: cannot get start thresh of battery 0: Function is not supported by SMAPI BIOS
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=211a)
tp_smapi: cannot get stop thresh of battery 0: Function is not supported by SMAPI BIOS
thinkpad controller read(%hx,%hx): failed writing to 0x1610
thinkpad controller read(%hx,%hx): failed writing to 0x1610
</pre>

--[[User:nusse|nusse]] Fri Jan 13 14:35:57 CET 2006
----

Nusse: Thanks; but there's not much we can do. Maybe the T22 uses a different interface, or doesn't have that feature.

--[[User:Thinker|Thinker]] 23:23, 15 January 2006 (CET)
----

Thinker: Is there anything I can do to check if the interface is different? Changing 0x1610 to some random number?

Is there a chance to get it by try and error?

--[[User:nusse|nusse]] Mon Jan 16 19:10:12 CET 2006
----

0x1610 is the number of an IO port it writes to, so changing it to a random number will pretty much guarantee a system crash...

The only way I can think of for figuring out the T22 interface is to see what the Windows software does.

--[[User:Thinker|Thinker]] 19:47, 16 January 2006 (CET)
----

I have a R40 (2722-B3G), and several things don't work with 0.16 on linux 2.6.15.1:

<pre>
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)
tp_smapi: cannot get force_discharge of battery 0: Function is not supported by SMAPI BIOS
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2114)
tp_smapi: cannot get inhibit charge of battery 0: Function is not supported by SMAPI BIOS
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2116)
tp_smapi: cannot get start thresh of battery 0: Function is not supported by SMAPI BIOS
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=211a)
tp_smapi: cannot get stop thresh of battery 0: Function is not supported by SMAPI BIOS
</pre>

Don't know about Windows, haven't booted it for weeks nor used it for years...

--[[User:Wonka|Wonka]] 19:00, 19 January 2006 (CET)
----

Wonka: do the other features (i.e., extended battery status) work on your R40?

--[[User:Thinker|Thinker]] 20:30, 20 January 2006 (CET)
----

==Changing the CD speed when the CD is being accessed will hang your computer==

I don't have this problem on my T40p. CDROM is mounted and file on CD is opened. Change speed do '''not''' hang my system.

-- Stefan Schmidt
----

An open file looks fine if you're not reading/writing at that point. But my T43 does hangs on this:
# dd if=/dev/scd0 of=/dev/null &
# echo 1 > /sys/devices/platform/smapi/cdrom_speed

--[[User:Thinker|Thinker]] 16:41, 7 Dec 2005 (CET)
----

OK, sorry. I was to fast. My system hangs on this commands, too. :(

-- Stefan Schmidt

Works well. Great.

T42 2373-8zh. Working :cdrom_speed and start_charge_thresh. Untest : inhibit_charge_minutes.

-- Haifeng Chen

cdrom_speed works on my T40.

-- [[User:Lammic|lammic]], 2005.12.09

== Kernel Patch? ==

Hello Thinker,

would it be possible to provide the SMAPI support as kernel patch as well? Something along the lines of: (0.12 against 2.6.15-rc5)

''(deleted, see below for how to create a patch file)''

Deleted the tp_smapi.c file at the end, out of obvious reasons, and I'm not sure about the placement in the ACPI section, OTOH there it would be found easily next to ibm_acpi.

Providing a patch would help when recompiling the kernel often, I hate recompiling external modules every time (even got me a kernel-upgrade script to do most of it automatically). But of course it's up to you. :)

--[[User:Spiney|spiney]] 09:52, 16 Dec 2005 (CET)
----

I'll be glad to add this, but I don't want to go through additional manual steps in the release process (there are already quite a few). Can you add a "make patch" functionality to the Makefile, or something of the sort, to automatically generate a full patch (including tp_smapi.c) against current kernel sources?

Also, this shouldn't be under drivers/acpi, since it doesn't use ACPI at all (that's why I didn't make it a patch to ibm_acpi). I think the right place is drivers/firmware, like the dell_rbu driver for Dell laptops.

BTW, the convention for kernel patches is to start them once level higher:
diff -Nurp kernel-2.6.14-vanilla kernel-2.6.14-patched

--[[User:Thinker|Thinker]] 17:12, 16 Dec 2005 (CET)
----

Of course it's from the wrong level, as usual I was just lazy/inattentive. And at one point I'll remember who likes what patch format, promise. ;)

A patch target as in "create a new file holding a correct diff to current kernel source" would be rather difficult, since line numbers might change etc., but applying the patch should be straighforward with a bit of sed. Of course I could just do that, create a patch with the diff command and then apply the new patch file in reverse. ;)

--[[User:Spiney|spiney]] 18:36, 16 Dec 2005 (CET)
----

If it does that on a local copy (no changes the original kernel tree) and cleans up after itself, that's fine with me. :-)

--[[User:Thinker|Thinker]] 18:50, 16 Dec 2005 (CET)
----

Ok, here's a shell script that creates the patch, feel free to use it under the terms of the GPL. For example call it from your Makefile with the patch target: (I didn't want to put all the script into the Makefile, since the rules about escaping in Makefiles, well, escape me ;)

<pre>
#!/bin/bash

KDIR=/lib/modules/$(uname -r)/build
FDIR=drivers/firmware
OPWD=$(pwd)

TMPDIR=$(mktemp -d)
cd $TMPDIR

mkdir -p a/$FDIR
cp $KDIR/$FDIR/{Kconfig,Makefile} a/$FDIR
cp -r a b
sed -i -e '/endmenu/i\
config IBM_SMAPI\
tristate "IBM ThinkPad SMAPI Support"\
depends on X86\
---help---\
This adds SMAPI support on IBM ThinkPads, mostly used for battery\
charge control. For more information about this driver see\
<http://www.thinkwiki.org/wiki/SMAPI_support_for_Linux> .\
\
If you have an IBM ThinkPad laptop, say Y or M here.\
' b/$FDIR/Kconfig
sed -i -e '$a\
obj-$(CONFIG_IBM_SMAPI) += tp_smapi.o' b/$FDIR/Makefile
cp $OPWD/tp_smapi.c b/$FDIR
diff -Nurp a b > $OPWD/tp_smapi-$(uname -r).patch
rm -r a b
cd $OPWD
</pre>

BTW, [http://qbnz.com/highlighter/ GeSHi]-based syntax-highlighting would be great...

--[[User:Spiney|spiney]] 19:28, 16 Dec 2005 (CET)
----

Ah, neat sed foo. How about [http://tpctl.sourceforge.net/tmp/Makefile this] escapade, then?

What's the sed spell needed to replace the Makefile's
VER := 0.13
with auto-parsing of
#define TP_VERSION "0.13"
from tp_smapi.c?

--[[User:Thinker|Thinker]] 20:37, 16 Dec 2005 (CET)
----

Hmm, something like
VERFROMC=$(sed -ne 's/^#define TP_VERSION "$.*$"/\1/gp' tp_smapi.c)
sed -i -e "s/^VER := .*$/VER := $VERFROMC/" Makefile
should do (untested, from the top of my head, maybe the temporary variable isn't even necessary?). And neat Makefile wizardry, at one point I'll learn the syntax.

--[[User:Spiney|spiney]] 20:44, 16 Dec 2005 (CET)
----

Makefile escaping is horrible, keep avoiding it... Anyway, the updated [http://tpctl.sourceforge.net/tmp/Makefile make patch] seems to do the right thing.

--[[User:Thinker|Thinker]] 21:36, 16 Dec 2005 (CET)
----

Small documentation request: just needed to create a patch for the not-yet-installed 2.6.16-rc2, which is no problem with
make KSRC=/path/to/linux-2.6.16-rc2 KVER=2.6.16-rc2 patch
but I guess it would be a good addition to the README file. :)

--[[User:Spiney|spiney]] 10:48, 8 February 2006 (CET)
----

==Installation questions==
Amazing! I've loaded this module in my T43 which is running SuSE 10 with the kernel of 2.6.13-15. I have three points to share:

1. The battery control part seems to work but has a minor problem. I set the stop_charge_threshold to 70, but the battery stops charging at 55%. Don't know why and how to fix it. :P

2. I don't have the cd speed control function. Here is what I have under /sys/devices/platform/smapi/:

./ ../ ac_connected BAT0/ BAT1/ bus@ driver@ power/

3. SuSE 10 doesn't have the necessary C files under .../drivers/hwmon/, I copied them from a 2.6.14.5 kernel source. Maybe it causes the two problems above. :(

When I have time, I'll install the new kernel to see if the problems are gone and report the result.

--[[User:68.51.153.96|68.51.153.96]] 04:31, 2 Jan 2006 (CET)
----

1. It should stop charging at 70, but will only ''start'' charging when remaining capacity has dipped below <tt>start_charge_thresh</tt>.

2. See the note about PROVIDE_CD_SPEED.

3. That's should be needed only for patching the HDAPS driver in order to make it compatible with tp_smapi. If your kernel (which version is it?) doens't inlude the HDAPS driver anyway, you don't need to patch....

--[[User:Thinker|Thinker]] 09:28, 2 Jan 2006 (CET)
----

Thanks Thinker.

1. I discharged and recharged the battery again. This time, it stops at 68% percent, which is pretty good.

2. I missed the NOTE in README, for I just followed this wiki. :P

3. My kernel version is 2.6.13-15.

By the way, I just got this T43 whose model number is 266896U. I feel that the noise of the fan is much louder than my previous T21. I think it is so since it has a CPU with bigger power but am wondering if other T43 has the same big noise?

--[[User:Tyne|Tyne]] 00:14, 3 Jan 2006 (CET)
----

The note about PROVIDE_CD_SPEED is also in the Wiki...

About the T43 fan noise: yes, this is a very common (and annoying) problem. See [[Problem_with_fan_noise]] and our [[ACPI fan control script]], and send Lenovo a complaint in hope they'll fix this at the firmware level.

--[[User:Thinker|Thinker]] 08:48, 3 Jan 2006 (CET)
----

== Formatting ==

Wyrfel, that was some heavy editing you did... I agree with most changes (including the saner color choice). I did like those HINT floats, though - they keep the hints from interrupting the flow of text too much, and this particular text needs any help it can get.

--[[User:Thinker|Thinker]] 17:04, 3 Jan 2006 (CET)
----
Hei Thinker,

I'll look into it again. I felt that the floating HINTs were tearing the text apart too much. Maybe we could fix it by placing the clear marks somewhere else.

[[User:Wyrfel|Wyrfel]] 18:46, 3 Jan 2006 (CET)
----

== Dual battery operation with tp_smapi ==

It looks like it is working quite fine with tp_smapi-0.13 and 2.6.15 (it may also work with other versions, but those are the ones I have running right now).

The juicy details:

{{cmdroot|cd /sys/devices/platform/smapi/}}
{{cmdroot|cat ac_connected}}

{{cmdresult|0}}
{{cmdroot|cat BAT{0,1}/state}}
{{cmdresult|discharging}}
{{cmdresult|idle}}

{{cmdroot|echo 1 > BAT1/force_discharge1}}
{{cmdroot|cat BAT{0,1}/state}}
{{cmdresult|idle}}
{{cmdresult|discharging}}

Checking capacity values shows that the corrent battery is being depleted.

And remember, before you yank the CD/DVD drive out, issue:

{{cmdroot|cat eject > /proc/acpi/ibm/bay}}

----

Great! Which ThinkPad model is it? Could you also {{cmdroot|cat /sys/devices/platform/smapi/BAT{0,1}/force_discharge2}} and report the dmesg output (after {{cmdroot|make load}} or {{cmdroot|1=modprobe tp_smapi debug=1}})?

About the eject command, I think it should be possible to do that automatically when the Ultrabay handle is ejected, via <tt>acpid</tt>.

--[[User:Thinker|Thinker]] 15:45, 10 Jan 2006 (CET)
----

It's a T43 (2669). cat'ing force_discharge2 gives me an I/O error and I see

tp_smapi: cannot get force_discharge2 of battery 0: bx=2103

tp_smapi: cannot get force_discharge2 of battery 1: bx=2103

I find these errors irrelevant from the user's point of view, though.

Indeed, it should be possible to automatise the "eject" command. I should also be noted that once a force_discharge1 is set, it will NOT unset automatically, event when the AC is plugged back in. An obvious fix is to fiddle with the appropriate ACPI event to force_discharge1 back to 0 for all batteries once the AC is attached.

----

Thanks, this eliminates the last situation I imagined <tt>force_discharge2</tt> might work. The next tp_smapi version will remove <tt>force_discharge2</tt> and rename <tt>force_discharge1</tt> to <tt>force_discharge</tt>.

If you write those ACPI scripts, it would be great if you put them on the Wiki.

--[[User:Thinker|Thinker]] 16:31, 10 Jan 2006 (CET)
----

Well, I still do not preclude the fact that <tt>force_discharge2</tt> may be useful for something else on other models.

The ACPI scripts (as well as an installation guide) is underway. It may take a while, though.

----

See the new article: [[Using an Ultrabay battery]].

--[[User:Thinker|Thinker]] 17:05, 10 Jan 2006 (CET)
----

Hei Thinker,

i just renamed the new page. Will adjust your links later on. Keeping the redirect page until that's done. Please set any new links you create to the new page (the pages of the individual UltraBay batteries should contain a pointer).

On a sidenote: I would like to split the SMAPI support under Linux page into a tp_smapi driver page, just listing the features, and a "How to use tp_smapi" page. I would also split the thinkpad/tpctl page off that again. Any objections?

[[User:Wyrfel|Wyrfel]] 20:42, 10 Jan 2006 (CET)
----

ACK about the page rename (the old one did sound a bit out of line to my ear, but I couldn't spot why...).

About the splitting tp_smapi vs. thinkpad/tpctl, no objection.

About splitting tp_smapi: currently most of that section doubles as both a spec and a HOWTO, which I think is a convenient and concise way to describe things (hey, it must be right, the Perl docs do it!). I'm not sure there's much benefit in duplicating that. Perhaps we should wait for a critical mass of additional lore to accumulate?

--[[User:Thinker|Thinker]] 21:04, 10 Jan 2006 (CET)
----
Ok, i agree on the latter.

[[User:Wyrfel|Wyrfel]] 00:57, 11 Jan 2006 (CET)
----

==Article name capitalization==

Wikimedia autocapitalizes the article name upon submit. How do I concince Wikimedia that I really want a lowercase "t"? The underline is probably too much too ask...

--[[User:Thinker|Thinker]] 11:03, 11 Jan 2006 (CET)
----

Impossible, according to [http://en.wikipedia.org/wiki/Wikipedia:Canonicalization Wikipedia:Canonicalization].

--[[User:Thinker|Thinker]] 12:04, 11 Jan 2006 (CET)
----

==Status Table==
For at least the T series i think that charge control was not supported prior to the T42, hardware/BIOS side. Perhaps "N/A" flags would be better here?

I also created <nowiki>{{Isup}}</nowiki> style templates for status, they just include images, like {{Isup}}.
Not emotional about it, just wanted to let you know in case you want to use them.

Third and last...would it possibly be better to make the table headers more human readable like i.e. "lower charge threshold" or something like that instead of "start_charge_thresh"?

[[User:Wyrfel|Wyrfel]] 19:21, 11 Jan 2006 (CET)
----

About "N/A", sure, if we get reliable data about the hardware capabilities. Alas, most negative reports were just "it doesn't work", and in some cases gave contradictory information (SMAPI interface says a function is unsupported but user says it works under Windows).

About {{Iyes}} and friends, they're very cute, but I think think they're harder to parse visually and would add some clutter to an already dense table.

The table headers are just the names of the control files - that's important to keep, sine it's the most natural lookup key. Adding friendly description would be great, if we can fit them in (not everyone has an SXGA+ display...). I tried and failed.

--[[User:Thinker|Thinker]] 20:38, 11 Jan 2006 (CET)
----

I have a T41p and the windows tools still don't offer me battery management, even though it's quite a while since the T42 came out.

I'm ok with the rest.

[[User:Wyrfel|Wyrfel]] 22:35, 11 Jan 2006 (CET)
----

Talk:Problems with fglrx

2006-01-21T06:24:26Z

Spiney: /* 8.20.8 and later works with current Debian sid packages */

== using kernel AGP vs fglrx AGP ==

Anyone know whether this makes a performance and/or stability difference?

== 8.20.8 and later works with current Debian sid packages ==

<pre>
spiney@t43p:~$ dpkg -l xserver-xorg
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-============================-============================-==================
ii xserver-xorg 6.9.0.dfsg.1-2 the X.Org X server
spiney@t43p:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY FireGL V3200 Pentium 4 (SSE2) (FireGL) (GNU_ICD)
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)
</pre>

--[[User:Spiney|spiney]]
----

Ahh - thanks for the info. You perhaps compiled the modules for the drivers yourself and did not use the debian packaged fglrx-driver? Thus, it must be an unneeded limitation on the debian packaged driver which limits its installation... Full listing at http://packages.debian.org/unstable/x11/fglrx-driver which lists as required packages:

xserver-xorg (<< 6.8.99)
the X.Org X server
xserver-xorg (>= 6.8.0)

The first limitation (<<6.8.99) is what prevents installation. I'm sure I could force apt to install it, but I may go back to compiling the modules myself, as using fglrx 8.20.8 with kernel 2.6.15 needs a small patch to compile correctly anyway... --[[User:gsmenden|gsmenden]]

Spiney, where exactly do you have your package from? I re-build the 8.20.8-package from debian with the <<6.8.99 dependecy removed, but when I try to run X, I get
[R200Setup] X version mismatch - detected X.org 7.0.0.0, required X.org 6.8.0.0
(EE) Failed to load module "fglrx" (module requirement mismatch, 0)
Any hints? --[User:nomeata|nomeata]

I used the ati-installer (the huge download), created a Debian sid package and installed it, but got the same error. The installer seems to fetch the wrong driver version from the archive, so I extracted it with

{{cmd|./ati-driver-installer-8.20.8-i386.run --extract <sometempdir>|}}

and put the necessary files from the created {{path|<sometempdir>/x690}} subdirectory into {{path|/usr}} by hand. All IIRC, it's been some time since. :)

--[[User:Spiney|spiney]] 07:29, 11 Jan 2006 (CET)

Thanks for the pointer. This is how you get proper debian packages out of the ati-installer:
./ati-driver-installer-8.20.8-i386.run --extract fglrx-tmp
cd fglrx-tmp
$editor packages/Debian/ati-packager.sh # in the line "sid|unstable) X_DIR=x680;;", put a x690 for the x680
./fglrx-tmp/packages/Debian/ati-packager.sh --buildpkg sid
cd ..
sudo dpkg -i fglrx-kernel-src_8.20.8-1_i386.deb fglrx-driver_8.20.8-1_i386.deb
--[[User:Nomeata|Nomeata]] 00:35, 13 Jan 2006 (CET)

----

Nice - confirmed works on my T43p running sid. From then on (or until 8.21.x comes out) you'll have to tell apt to hold back fglrx-driver package, or it will try to "update" fglrx-driver to 8.20.8-1.1 and therefore revert back to the problematic drivers.
--[[User:gsmenden|gsmenden]]
----

Thanks for the info, Nomeata, that's a lot cleaner a solution than my manual way.

--[[User:Spiney|spiney]] 08:32, 13 Jan 2006 (CET)
----

To get this working under 2.6.15 with x.org 6.9, you will also need to apply a small patch - there is a link on the main article page. After you install the fglrx-driver package with the 6.9 versioning hack above, go to
/usr/src/modules
and copy the patch here. Modify the first two lines of the patch file to take out the "build_mod" directory, e.g. first line should begin with
--- fglrx.orig/firegl_public.c
and call it with the -p0 strip option. It should patch the firegl_public.c file cleanly. You can then install as usual for your kernel (2.6.14.x or 2.6.15) using module-assistant.

Update - although X will come up in kernel 2.6.15 with the fglrx drivers patched as above, there is some strange behavior exhibited in all of X apllications - frequent hanging of applications when closing windows. Reverting back to the radeon driver in 2.6.15 solves these - so it is likely the ATI proprietary driver causing some problems.

Yet another update - fglrx 8.21.7 is out as of 1/19/2006, now supporting OpenGL 2.0, so eventually we will have beautiful complex shading / fog effects on Linux, too. It works well with X.Org 6.9 out of the box.

Unfortunately, this version gives the same problems when used (unpatched) with kernel 2.6.15 with strange lockups occasionally requiring reset of X. I have not tried this with the ~10 line patch listed on the main site, but that patch not work for me with 8.20.8. Anybody else have experience with 2.6.15 and fglrx?

--[[User:gsmenden|gsmenden]] 12:39, 20 Jan 2006 (EST)
----

I don't know which patch you mean exactly (10 lines? the patch from lkml is just one line changed, no?), but I've been using 8.20.8 with 2.6.15 for quite some time (actually started with some -rc version IIRC), no lockups at all. No idea about 8.21.7 though, because I switched to 2.6.16-rc1 and can't compile the fglrx module at the moment, need to investigate the cause.

--[[User:Spiney|spiney]] 07:24, 21 January 2006 (CET)
----

== Disabling the external VGA port? ==

Does anyone know how disable the VGA port ''completely'' even when a cable is attached? Fiddling around with the DesktopSetup and ForceMonitor options didn't do the trick for me, and the MonitorLayout option found in some documentation is no longer valid in the current fglrx driver.

--[[User:Spiney|spiney]] 19:42, 10 Jan 2006 (CET)
----

== Debian-specific script to switch fglrx<->radeon ==

Don't know where to put it exactly, but if someone's interested (and using Debian), I've put up a [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_graphics_card_switching_fglrx_radeon script for easily switching graphics driver configurations]. Feedback appreciated (altho I haven't got any to the xscreensaver patch ;)), especially if someone could do something similar for other distributions (Gentoo being half-way there it seems) and incorporate it into the script.

--[[User:Spiney|spiney]] 15:25, 17 January 2006 (CET)
----

Template:Industry News

2006-01-19T12:47:04Z

Spiney:

19.01.2006 New [[fglrx]] driver version 8.21.7 released

14.01.2006 A bit old news: [http://www.businessweek.com/technology/content/dec2005/tc20051221_376268.htm?campaign_id=rss_tech Lenovo hires new CEO from Dell].

05.01.2006 Lenovo [http://www.pc.ibm.com/ww/thinkpad/x-t.html?re=home_primary_us announces] the next step in X and T series: [[:Category:X60|X60]], [[:Category:X60s|X60s]] and [[:Category:T60|T60]].

22.12.2005 [http://www.upek.com/support/dl_linux_bsp.asp Version 1.0 (final)] of the BSP for the UPEK fingerprint sensor released.

08.12.2005 New [[fglrx]] driver version 8.20.8 released

Talk:Additional options for the radeon driver

2006-01-17T14:39:20Z

Spiney: real dual-head with X.org 6.9.0?

The '''BIOSHotkeys''' and '''MergedNonRectangular''' options are unknown on my Fedora Core 4 with xorg-x11-6.8.2-37.FC4.49.2. [[User:Asgeirn|Asgeirn]] 09:39, 28 Sep 2005 (CEST)

== MergedFB messes up LCD screen ==

When I try to used any MergedFB configuration, my laptop screen goes crazy. I can see from the screen and the Xorg logs that the second monitor is setup and the mergedfb is active, but the laptop screen is completely unreadable, even when I switch back to the VTs in text mode. The screen is just a blur of colors. This happens no matter what the mergedfb size is. My system is a T41 (2373-7FU) with Radeon 7500 M7 LW.

Xinerama works just fine, but of course there is no direct rendering.

--216.234.144.30

----

Sounds like a refresh rate issue. Try the xorg.onf snippet in [[ATI Mobility Radeon X300]].

--[[User:Thinker|Thinker]] 04:18, 18 Nov 2005 (CET)
----

== real dual-head with X.org 6.9.0? ==

Anyone having a working configuration providing real dual-head setup (two independent screens, no moving of windows between them) with the radeon driver?

--[[User:Spiney|spiney]] 15:39, 17 January 2006 (CET)
----

Talk:Problems with fglrx

2006-01-17T14:25:26Z

Spiney: Debian-specific script to switch fglrx<->radeon

== using kernel AGP vs fglrx AGP ==

Anyone know whether this makes a performance and/or stability difference?

== 8.20.8 does work fine with current Debian sid packages ==

<pre>
spiney@t43p:~$ dpkg -l xserver-xorg
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-============================-============================-==================
ii xserver-xorg 6.9.0.dfsg.1-2 the X.Org X server
spiney@t43p:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY FireGL V3200 Pentium 4 (SSE2) (FireGL) (GNU_ICD)
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)
</pre>

--[[User:Spiney|spiney]]
----

Ahh - thanks for the info. You perhaps compiled the modules for the drivers yourself and did not use the debian packaged fglrx-driver? Thus, it must be an unneeded limitation on the debian packaged driver which limits its installation... Full listing at http://packages.debian.org/unstable/x11/fglrx-driver which lists as required packages:

xserver-xorg (<< 6.8.99)
the X.Org X server
xserver-xorg (>= 6.8.0)

The first limitation (<<6.8.99) is what prevents installation. I'm sure I could force apt to install it, but I may go back to compiling the modules myself, as using fglrx 8.20.8 with kernel 2.6.15 needs a small patch to compile correctly anyway... --[[User:gsmenden|gsmenden]]

Spiney, where exactly do you have your package from? I re-build the 8.20.8-package from debian with the <<6.8.99 dependecy removed, but when I try to run X, I get
[R200Setup] X version mismatch - detected X.org 7.0.0.0, required X.org 6.8.0.0
(EE) Failed to load module "fglrx" (module requirement mismatch, 0)
Any hints? --[User:nomeata|nomeata]

I used the ati-installer (the huge download), created a Debian sid package and installed it, but got the same error. The installer seems to fetch the wrong driver version from the archive, so I extracted it with

{{cmd|./ati-driver-installer-8.20.8-i386.run --extract <sometempdir>|}}

and put the necessary files from the created {{path|<sometempdir>/x690}} subdirectory into {{path|/usr}} by hand. All IIRC, it's been some time since. :)

--[[User:Spiney|spiney]] 07:29, 11 Jan 2006 (CET)

Thanks for the pointer. This is how you get proper debian packages out of the ati-installer:
./ati-driver-installer-8.20.8-i386.run --extract fglrx-tmp
cd fglrx-tmp
$editor packages/Debian/ati-packager.sh # in the line "sid|unstable) X_DIR=x680;;", put a x690 for the x680
./fglrx-tmp/packages/Debian/ati-packager.sh --buildpkg sid
cd ..
sudo dpkg -i fglrx-kernel-src_8.20.8-1_i386.deb fglrx-driver_8.20.8-1_i386.deb
--[[User:Nomeata|Nomeata]] 00:35, 13 Jan 2006 (CET)

----

Nice - confirmed works on my T43p running sid. From then on (or until 8.21.x comes out) you'll have to tell apt to hold back fglrx-driver package, or it will try to "update" fglrx-driver to 8.20.8-1.1 and therefore revert back to the problematic drivers.
--[[User:gsmenden|gsmenden]]
----

Thanks for the info, Nomeata, that's a lot cleaner a solution than my manual way.

--[[User:Spiney|spiney]] 08:32, 13 Jan 2006 (CET)
----

To get this working under 2.6.15 with x.org 6.9, you will also need to apply a small patch - there is a link on the main article page. After you install the fglrx-driver package with the 6.9 versioning hack above, go to
/usr/src/modules
and copy the patch here. Modify the first two lines of the patch file to take out the "build_mod" directory, e.g. first line should begin with
--- fglrx.orig/firegl_public.c
and call it with the -p0 strip option. It should patch the firegl_public.c file cleanly. You can then install as usual for your kernel (2.6.14.x or 2.6.15) using module-assistant.

Update - although X will come up in kernel 2.6.15 with the fglrx drivers patched as above, there is some strange behavior exhibited in all of X apllications - frequent hanging of applications when closing windows. Reverting back to the radeon driver in 2.6.15 solves these - so it is likely the ATI proprietary driver causing some problems...
--[[User:gsmenden|gsmenden]] 12:39, 14 Jan 2006 (EST)

== Disabling the external VGA port? ==

Does anyone know how disable the VGA port ''completely'' even when a cable is attached? Fiddling around with the DesktopSetup and ForceMonitor options didn't do the trick for me, and the MonitorLayout option found in some documentation is no longer valid in the current fglrx driver.

--[[User:Spiney|spiney]] 19:42, 10 Jan 2006 (CET)
----

== Debian-specific script to switch fglrx<->radeon ==

Don't know where to put it exactly, but if someone's interested (and using Debian), I've put up a [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_graphics_card_switching_fglrx_radeon script for easily switching graphics driver configurations]. Feedback appreciated (altho I haven't got any to the xscreensaver patch ;)), especially if someone could do something similar for other distributions (Gentoo being half-way there it seems) and incorporate it into the script.

--[[User:Spiney|spiney]] 15:25, 17 January 2006 (CET)
----

Problems with fglrx

2006-01-17T14:18:51Z

Spiney: /* Kernel-specific troubles */ 2.6.15-rc5 is not "current" any more

This page discusses issues with the ATI proprietary [[fglrx]] display driver.

== Known Troubles and Solutions ==

=== X-specific issues ===

The current ATI proprietary driver (8.20.8) will work with x.org 6.9. However, if you are running Debian sid and you upgrade your xserver-xorg, apt will force you to remove any debian-packaged fglrx drivers (package fglrx-driver depends on x.org << 6.8.99). You can just download the driver from the ATI site and install after modifying the Debian packager script to allow dependencies to be satisfied by x.org 6.9. See talk page for step-by-step commands.

After installing the fglrx driver, you can use module-assist to build the appropriate kernel module.

=== Kernel-specific troubles ===

Using the current ATI driver (8.20.8) with 2.6.15 or later needs a [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]. (info stolen from the table below, but put here for better visibility)

=== No hardware acceleration ===
If the ATI driver works only without the hardware acceleration, take into consideration that {{path|fglrx_dri.so}} was linked against libstdc++.so.5 which may not be present if your system uses gcc-3.4.

To fix this, compile gcc-3.3.5 and copy <tt>libstdc++.so.5*</tt> to {{path|/usr/lib}} and update the dynamic linker cache via {{cmdroot|ldconfig}}.

Another possible cause for broken hardware acceleration (2D and 3D) is the radeonfb framebuffer: Switching to vesafb or vesafb-tng is reported to solve the problem on some systems. Also it has proven helpful to not perform {{cmdroot|modprobe fglrx}} after boot but to have the module loaded via {{path|/etc/modules.autoload/kernel2.x}} at boottime instead.

=== Softlink hell ===

The [[fglrx]] installer replaces the standard X.org OpenGL implementation (Mesa) with its own files, potentially causing collisions with the distribution's file and package management. It is best to install the driver via a package built for your distribution, which will typically include the necessary kludges to make things work. See the [[fglrx]] page for pointers.

====Discussion====

If you install the driver and type "fglrxinfo" which shows you are still using the mesa indirect software GL renderer, you likely have some misplaced softlinks. I find this *really* frustrating, and do not know why it occasionally occurs -> I think it has to do with an apt-get upgrade that sometimes replaces these links. Anyway, go to

: cd /usr/X11R6/lib

and list your GL libraries and links

: ls -la *GL*

You should see something like:

: libGL.so -> libGL.so.1.2

and
: libGL.so.1 -> libGL.so.1.2

If you see a link to a mesa library (something like ->libGL.mesa.1.2), then that's your problem! Restore the softlink with a command similar to:
: ln -s <actual file> <softlink name>

e.g.
: ln -s libGL.so.1.2 libGL.so.1

For some reason, this link might "break" later, giving you the software rendering once more. I renamed the mesa library to mesa.bkup, and the system still found it and linked to it despite the name change. If you have to do this a lot, you could write a restoreGL script...

=====Gentoo=====
I did the above steps with no luck but it's working now so read on:

Because
: ldd /usr/X11R6/bin/glxinfo
showed that my system still uses the xorg-x11 mesa think and the above hint didn't work as expected I looked at this:
: libGL.so.1 => /usr/lib/opengl/xorg-x11/lib/libGL.so.1 (0x400a8000)
Afterwards I did:
: cd /usr/lib/opengl/xorg-x11/lib/
: mv libGL.so.1.2 libGL.so.1.2_backup
: ln -s /usr/lib/libGL.so.1.2 libGL.so.1.2
After another restart of X "fglrxinfo" showed that it's using the right libs now.

=====Alternative for Gentoo=====
Gentoo has built in tools for managing the OpenGL symlinks. They seem to be replacing the old tool with a new one, so one of the following should work for you:

: # opengl-update ati
: # eselect opengl set ati

Eselect is new, and still ~x86(as of the end of 2005), so you may not have it yet. opengl-update is the old tried-and-true method for managing the symlinks. If opengl-update doesn't fix it for you, you should probably tell [http://bugs.gentoo.org Gentoo Bugzilla](assuming they don't know yet)

=== Troubles using software suspend ===
When the computer resumes from suspend, X only displays a garbled image and the computer is frozen.
The problem is acknowledged in ATI's release notes and in knowledge base entry [https://support.ati.com/ics/support/KBResult.asp?searchFor=Search+Words&search.x=0&search.y=0&searchOption=id&questionID=737-218+&task=knowledge&searchTime=-1&productID=&folderID=-1&resultLimit=50 737-218]. Driver version 8.19.10 has "initial support for Suspend and Resume" but is working very nicely for most people (verified on T43, T43p and T42) without vbetool.

If you are using an older version of fglrx, using [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] to save/restore the video card state before/after suspend worked for some people. If you use [[Software Suspend 2|Software Suspend 2 (suspend2)]] scripts, you can simply uncomment <tt>EnableVbetool yes</tt> in {{path|/etc/hibernate/hibernate.conf}}. Be aware though that it breaks suspend/resume for drivers beginning with version 8.19.10, so remember to disable it again when upgrading.

{| cellspacing="0" cellpadding="2" border="1"
|+ tested with the following configurations
!model!!distro||kernel!!fglrx!!PM!!success!!comments
|-
|{{T42}}||SUSE 9.3||2.6.11||8.14.13||swsusp||yes||
|-
|{{T41p}}||???||2.6.14||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch]
|-
|{{T42p}}||Debian||2.6.10||Debian packaged||suspend2||yes||
|-
|{{T43}}||Debian sid||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 (but not earlier versions!)
|-
|{{T43}}||Debian etch||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 and without vbetool
|-
|{{T43}}||Ubuntu Breezy||2.6.12-10||8.19.10||swsusp||yes||Perfect. (Finally.)
|-
|{{T43}}||FC4||2.6.14.1||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch], requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)
|-
|{{T43}}||FC4||2.6.14.2||8.19.10||suspend2 2.2-rc11||yes||requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)
|-
|{{T43}}||FC4||2.6.14.3||8.19.10||suspend2 2.2-rc13||no||DRI enabled
|-
|{{T43}}||FC4||2.6.14.3||8.20.8||suspend2 2.2-rc13||no||DRI enabled
|-
|{{R50p}}||???||???||8.19.10||swsusp||yes||
|-
|{{T43p}}||Debian sid||2.6.14||8.19.10||Suspend to RAM||yes||without vbetool or UseDummyXServer, those two ''break'' the resume process here, with DRI enabled
|-
|{{T43p}}||Debian sid||2.6.14.3||8.20.8||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{R52}}||Debian sid||2.6.15-rc5||8.20.8||swsup||yes||both vbetool and UseDummyXServer disabled, DRI enabled, needs [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]
|}

=== Troubles with large RAM ===
Version 8.14.13 (and probably earlier versions) of the driver does not seem to be able to cope with large amounts of RAM: with 512 MB it works, with 1.5 GB it crashes the machine as soon as X is started. The problem is present only if the <tt>fglrx</tt> kernel module is loaded, but independently of whether {{kernelconf|CONFIG_HIGHMEM||||||}} is enabled. A workaround is to limit RAM by adding the {{bootparm|mem|864m}} kernel parameter.

Version 8.16.20 fixes the problem.

===Display switching ===
The switching between internal and external display doesn't work, because the driver blocks messing around with the chipset via ACPI. If you want to use this feature (i.e. during presentations), you should use the VESA server instead (experienced with a R52, Kernel 2.6.11, xorg 6.8.2, fglrx 8.16.20).

===Composite Support===
ATI has not officially supported composite windowing (alpha channel) enabling hardware acclerated translucent windows (primarily for 'eye candy.') Enabling Composite in KDE and the fglrx driver results in a very pretty desktop but unacceptably slow performance on a T43p with ATI's FireGL T2. It is still unusable in its current state (as of driver 8.19.10).

ATI promises support in the future when composite is officially supported by Xorg. Discussion of current status of drivers can be found in the Rage3d forums' (rage3d.com/board) Linux area. Rumor has it that the Microsoft Vista will support composite, so hopefully we will see it before then...

There were some rumors that composite support was fast with the open-source 2d accelerated drivers in x.org 6.9 (as opposed to 6.8.x). Alas, trying this gives better results than the proprietary drivers, but it is still too slow to be reasonably useful.

===Hardlock on X logout===
Up from driver version 8.19.10 you will expierence a system hard lock when logging out from X, if the session manager (kdm/gdm) is not properly configured. You have to tell the session manager to restart X.

In the kdm config file (gentoo: /usr/kde/<VERSION>/share/config/kdm/kdmrc) you have to add following to the section '[X-:*-Core]':

'''TerminateServer=true'''

In the gdm config file add:

'''AlwaysRestartServer=true '''

Information from the ATI butracker: http://ati.cchtml.com/show_bug.cgi?id=239

== Patches ==
The following patches might be needed for certain versions of fglrx.

===fglrx 8.20.8===

* [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 for kernel 2.6.15]

===fglrx (problem met at least with version 8.18.8)===
* [http://lkml.org/lkml/2005/9/22/183 for kernel >= 2.6.13 ] Missing verify_area bug

===fglrx 8.8.25 ===
* [http://www.rage3d.com/board/showthread.php?t=33798874 for kernels >= 2.6.10]
* [http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch For kernels >= 2.6.11-rc1]

Problems with SATA and Linux

2006-01-17T10:09:29Z

Spiney: /* Hang on resume from suspend to RAM */ info about 2.6.16-rc1

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Some ThinkPad models use a SATA controller for the system hard disk. This causes several complications for Linux installation. The following lists these problems and known workarounds. Note that the details are often version- and distribution-specific.

===Models using a SATA disk interface===
Models using a SATA controller and a SATA system disk:
*ThinkPad {{Z60t}}, {{Z60m}}
Models using a SATA controller and a PATA (IDE) system disk with a SATA-to-PATA bridge:
*ThinkPad {{T43}}, {{T43p}}
*ThinkPad {{R52}}
*ThinkPad {{X41}}, {{X41T}}

{{NOTE|Some of these problems (namely SMART support, power management and disk information) are solved in Linux 2.6.15 with the inclusion of libata pass-through. See the SATA driver [http://linux.yyz.us/sata/features.html features], [http://linux.yyz.us/sata/software-status.html software status] and [http://linux.yyz.us/sata/sata-status.html hardware status].}}
|}

==Hang on resume from suspend to RAM==

Linux kernels (as of 2.6.15-rc3) do not support suspend and resume for SATA devices. As a result, the machine hangs upon the first disk access after resume. A kernel patch ([http://lkml.org/lkml/2005/5/2/46 LKML posting]) fixes this by adding SATA power management support.

Current release-candidates for 2.6.16 ([http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.16-rc1 Changelog for 2.6.16-rc1]) have the patch already included], so no more patching will be necessary with 2.6.16.

===Patches===
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff Patch for kernel 2.6.12]
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.13-rc5.diff Patch for kernel 2.6.13-rc5]
* [http://lkml.org/lkml/2005/9/23/97 Patch for kernel 2.6.14]
* [http://www.xenotime.net/linux/SATA/2.6.15-rc/libata_suspend.patch Patch for kernel 2.6.15-rc4]
* [http://tpctl.sourceforge.net/tmp/sata_pm.2.6.15-rc6.patch Patch for kernels 2.6.15-rc6 through 2.6.15]

Some distributions already include this patch (e.g., {{Ubuntu}} Breezy), but some don't (e.g., {{Fedora}} 4).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169201 bug 169201: "SATA drives fail on laptop suspend"]

==Failed resume from suspend to disk==

Suspend to disk (using swsusp or [[Software Suspend 2]]) needs to load the memory image from the SATA disk. For this to work, you either need an initrd with all the necessary SATA modules, or the SATA drivers compiled into the kernel.

==DVD drive not recognized==

The <tt>ata_piix</tt> SATA driver grabs ownership over the IDE ports when it is loaded, but (by default) does not support PATA ATAPI devices such as the Ultrabay optical drives. Thus, if the <tt>ide</tt> driver is compiled as a module and loaded after <tt>ata_piix</tt>, the DVD drive will not be recognized by either driver.

Either of the following configurations will work:
* For kernel 2.6.14 and newer: enable ATAPI support in the SATA system using {{bootparm|libata.atapi_enabled|1}} (see below; this is experimental).
* Compile IDE into the kernel (non-module).
* Compile both IDE and SATA as modules and make sure IDE is loaded first (the module is called 'ide_generic').

Note that the optical drive must be in the Ultrabay during system boot (Ultrabay device swapping is currently unsupported).

==No DMA on DVD drive==

Using the IDE driver, DMA support cannot be enabled on an Ultrabay optical drive:

# hdparm -d1 /dev/hdc

/dev/hdc:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)

As a result, the optical drive is slow, and in particular, too slow to play video DVDs.

One workaround is to use employ the SATA driver (instead of the IDE driver) for the optical drive. This requires enabling two featues of the SATA driver, namely ATAPI support and PATA support, which are both in active development and far from stable. Using this will probably devour all your data and go on to eat all the food in your fridge. But if you have full backups and an empty fridge, do the following:

* Grab the latest kernel (must be 2.6.14 or newer; the relevant code is under active development).
* Do one of the following:
** Configure the SATA system (and in particular <tt>ata_piix</tt> and <tt>libata</tt>) as built-in and add {{bootparm|libata.atapi_enabled|1}} to your kernel command line (e.g., in in {{path|/boot/grub/menu.lst}}).
** Configure the SATA system as module (this is often the default) and add "<tt>options libata atapi_enabled=1</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* Do one of the following:
** Disable the IDE system.
** Build the IDE driver as built-in (this is often the default) and add the {{bootparm|hdc|noprobe}} kernel argument (e.g., in in {{path|/boot/grub/menu.lst}}).
** Build the IDE driver as module and add "<tt>options ide hdc=noprobe</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* If you chose to use modules above, regenerate your <tt>initrd</tt> file.

If this doesn't work, use {{cmd|lspci -vn|}} to check whether one of the following chipsets is used in the Thinkpad:
{| border="1" cellspacing="0" cellpadding="2"
|-
!PCI ID
!Name
|-
|8086:7111
|Intel 82371AB/EB/MB PIIX4 IDE
|-
|8086:24db
|Intel 82801EB/ER (ICH5/ICH5R) IDE Controller
|-
|8086:25a2
|Intel 6300ESB PATA Storage Controller
|}
If yes, enable support for these chipsets has to be enabled by setting
#define ATA_ENABLE_PATA
in {{path|include/linux/libata.h}} (and report your ThinkPad model in the discussion page).

There have been reports that DVD burning doesn't work under this configuration, but it seems to work with kernel 2.6.14 and later (tested on a ThinkPad {{T43}} and {{T43p}} with a [[UltraBay Slim DVD Multi-Burner Plus]]).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163418 bug 163418: "can't enable DMA on DVD drive"]

==No DMA on system hard disk==

In some Linux kernels, both the SATA driver and the IDE driver can handle the system hard disk. With the SATA driver, it shows as {{path|/dev/sda}} and DMA is enabled. With the IDE driver, it shows as {{path|/dev/hda}} and DMA is disabled.

The simplest way to enable DMA is to force the IDE driver to ignore the system hard disk by passing the {{bootparm|hda|noprobe}} kernel argument. The driver will then be handled by the SATA driver. Note that this will change its device name to {{path|/dev/sda}} (which may require changes in {{path|/etc/fstab}} and the boot loader) and may cause other problems as listed above.

(Observed on a ThinkPad T43 with Fedora Core kernel 2.6.13-1.1526_FC4.)

==No SMART support==

Prior to kernel 2.6.15, the Linux SATA system did not support SMART commands (e.g., via smartctl).

The necessary capability is "libata pass-through", which was incorporated into Linux 2.6.15-rc1 and later. A patch is available for older kernels:
* Kernel 2.6.12: http://rtr.ca/dell_i9300/kernel/kernel-2.6.12/03_libata_passthru.patch
* Kernel 2.6.13: http://rtr.ca/dell_i9300/kernel/kernel-2.6.13/02_libata_passthru.patch
* Kernel 2.6.14: http://www.foo.fh-furtwangen.de/~koenigr/02_libata_passthru.fixed.again.patch
* Kernel 2.6.14 with the above suspend-to-RAM patch: http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch

After applying the patch, run smartctl with the "-d ata" parameter:
:{{cmdroot|smartctl -d ata -a /dev/sda}}

==No disk power management==

Prior to kernel 2.6.15, the Linux SATA system did not support power management commands on these models.

The above patches for SMART support resolves this, and in particular enables the following commands:
* {{cmdroot|hdparm -y}} (spin down)
* {{cmdroot|hdparm -S num}} (automatic spin down timeout)
* {{cmdroot|hdparm -B num}} (advanced power management level)
Note that this command is still rejected:
* {{cmdroot|hdparm -M num}} (acoustic management)
(Tested with patched kernels 2.6.13.1 and 2.6.12-4 and a 60GB 7200RPM disk model HTS726060M9AT00.)

Note that even when [[Laptop-mode]] is used, the "hddtemp" daemon (as shipped with Fedora Core 4) will wake up the disk every minute, and must thus be disabled for power management to be effective. Its accesses are not visibile through the {{path|/proc/sys/vm/block_dump}} facility. It is unclear whether disk temperature can be monitored without causing the disk to spin up (on the {{T43}}, none of the {{path|/proc/acpi/ibm/thermal}} values corresponds to the disk's built-in temperature sensor).

==No disk information==

Prior to kernel 2.6.15, on these models the disk information could not be read by the standard commands such as:
*{{cmdroot|hdparm -i /dev/sda}}
*{{cmdroot|hdparm -I /dev/sda}}
The latter is fixed by the above patch for SMART support.

==No swapping of UltraBay device==

The <tt>libata</tt> driver does not yet support hot-swapping (or warm-swapping) of PATA devices. If you use a DVD or 2nd PATA HDD via the <tt>libata</tt> (SATA) driver, to swap them in or out you must power down the machine.

If you use the <tt>ide</tt> driver for a PATA UltraBay device, hot-swapping might work using <tt>hdparm</tt>, <tt>idectl</tt> or <tt>hotswap</tt> (please report). However, DMA will be disabled on these models (see above).

If you use a SATA device in the UltraBay, <tt>libata</tt> hot-swapping might work (please report).

Swapping of the [[UltraBay Slim Battery]] does work.

==BIOS error 2010 on user-installed hard disk==

While not a Linux issue, note that there is an issue with installing alternative PATA (IDE) hard disks as the system drive. Unless the disk is one of the few approved disks listed inside the BIOS, you will get an BIOS error 2010 during system boot, and the disk may operate unreliably. See [[Problem with non-ThinkPad hard disks]].

Talk:Problems with fglrx

2006-01-13T07:32:49Z

Spiney: /* 8.20.8 does work fine with current Debian sid packages */

Talk:IrDA

2006-01-12T13:37:48Z

Spiney: /* setpnp */ CONFIG_PNPACPI needed for patch?

The "wrong chip version ff" is a real issue, and having it mentioned makes sure that google searches turn it up with a solution.
[[User:Tonko|Tonko]] 01:41, 8 Oct 2005 (CEST)

----
The present text confused me (as you now have noticed). Maybe it should better reflect that the error is incorrect ("wrong chip version ff" instead of "FIR mode not enabled" or whatever). Would that be acceptable?

[[User:Pebolle|Paul Bolle]] 02:05, 8 Oct 2005 (CEST)
----
If you think you can explain it better, go right ahead. The IrDA document could use some major cleaning.

As long as we still point out that the only error in syslog is "Wrong chip version ff" when trying to load the FIR module without first activating the PnP device. It would be nice if the ISA-PNP patch to the nsc-ircc driver got accepted upstream, so we dont have to do these hacks anymore.
[[User:Tonko|Tonko]] 03:58, 8 Oct 2005 (CEST)
----
Tonko,

Is there a reason why you deleted the TODO entry for linux 2.6 kernel config for SIR? I would like to readd it, but like to hear your reason to remove it first.

[[User:Pebolle|Paul Bolle]] 10:23, 14 Oct 2005 (CEST)

== T23 debianized kernel with probs ==

Found another crazy thing here. T23 2648-2GG, with 2.6.13 and 2.6.14 (Debianized Source). Clear init of nsc-ircc and dongle, but the dongle stays offline (dark and blind). Booted with Knoppix or Bart-PE Windows give correct function of the whole device, viewed with a digicam shows some blinks at init. But not with plain 2.6.13 an 2.6.14 from Debian.
Eric

== setpnp ==

Hello,

since the nsc-ircc patch isn't in 2.6.15, I tried to go the setpnp route, but I don't even get to see {{path|/proc/bus/pnp}} even though I enabled the support for it in the kernel config (once I found out that I need to enable ISA support to even get the option). Has anyone successfully used setpnp to enable the IRDA port or is that just some sort of urban legend? ;)

--[[User:Spiney|spiney]] 19:12, 4 Jan 2006 (CET)
----

Make sure you enable pnp-bios support specifically when compiling the kernel, just enabling pnp support is not enough.
I must however admit that I have not done this, since my ancient TP 770 running a 2.4 kernel, which was at least 5 years ago.

I just looked at a 2.6 menuconfig myself, and could not find the option, but looking at my .config file I can see the CONFIG_PNPBIOS option, so you might just want to edit the config file directly, enable the PNPBIOS option, and run make oldconfig.

--[[User:Tonko|Tonko]] 19:38, 4 Jan 2006 (CET)
----

I do have the pnp-bios support enabled (the option is depending on ISA among others, checked the Kconfig file in the source tree to find it), and also the proc-Interface option, but still no go... maybe it's not compatible with CONFIG_PNPACPI? Oh well, nevermind, going back to the patch, that works with less hassles, I just hope it'll end up in the vanilla kernel eventually. Still thanks for the help.

--[[User:Spiney|spiney]] 20:22, 4 Jan 2006 (CET)
----

Ok, on further investigation (not giving up that easily ;) it really seems that CONFIG_PNPACPI is disabling PnPBIOS, at least dmesg showed something along the lines of "PnPBIOS: disabled by PnPACPI". But, after recompiling without PnPACPI, I still can't get it to work. I can use {{cmd|setpnp|}} and {{cmd|lspnp|}} just fine, but the nsc-ircc module won't load:

<pre>
t43p:~# lspnp 12
12 IBM0071 IBM Thinkpad infrared port
t43p:~# setpnp 12 io 0x2f8 irq 3
t43p:~# lspnp -v 12
12 IBM0071 IBM Thinkpad infrared port
dma 3
io 0x02f8-0x02ff
irq 3
t43p:~# modprobe nsc-ircc io=0x2f8 irq=3 dongle_id=0x09
FATAL: Error inserting nsc_ircc (/lib/modules/2.6.15/kernel/drivers/net/irda/nsc-ircc.ko): No such device
</pre>

Hmm, I'm getting somewhat annoyed... any ideas?

--[[User:Spiney|spiney]] 20:58, 4 Jan 2006 (CET)
----

have you tried just doing {{cmd|setpnp 12 on|}}

--[[User:Tonko|Tonko]] 21:05, 4 Jan 2006 (CET)
----

Yes, that was the first thing I tried, didn't help. BTW, I just fiddled around with lirc a bit (never tried it before), and the lirc_sir module works just fine:

<pre>
lirc_sir: I/O port 0x02f8, IRQ 3.
lirc_sir: Installed.
</pre>

and I was able to get it to control xmms.

{{cmd|setserial|}} doesn't claim the device either:

<pre>
t43p:~# setserial -ag /dev/ttyS0
/dev/ttyS0, Line 0, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 921600, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test
</pre>

I'm really out of ideas.

--[[User:Spiney|spiney]] 21:20, 4 Jan 2006 (CET)
----

Hmm, it should not be ttyS0, but ttyS1 which might be stepping on the resources
ttyS0 is IO 0x3f8 and IRQ 4, while ttyS1 is IO 0x2f8 and IRQ 3.

ttyS0 is your integrated serial port, which even ThinkPads without physical serial port have.

--[[User:Tonko|Tonko]] 21:29, 4 Jan 2006 (CET)
----
Sorry, I cut'n'paste the wrong device since I checked them both, the output for ttyS1 is identical (apart from "/dev/ttyS1, Line 1" of course).

--[[User:Spiney|spiney]] 21:36, 4 Jan 2006 (CET)
----
No idea what might be wrong, perhaps it does not work on more recent machines, or kernels.

As I said, it worked for me a long time ago on my 770X with ''something'' like this:

/bin/setserial /dev/ttyS1 uart none port 0 irq 0
setpnp 12 io 0x2f8 irq 3
setpnp 12 on
modprobe nsc-ircc dongle_id=0x09 io=0x2f8 irq=3

What is the error you get from nsc-ircc in syslog? the "Wrong chip version ff" error?

--[[User:Tonko|Tonko]] 22:22, 4 Jan 2006 (CET)
----

No errors are recorded at all (dmesg, syslog), just the message above on stderr from {{cmd|modprobe|}}.

--[[User:Spiney|spiney]] 09:27, 5 Jan 2006 (CET)
----

BTW, is it just me or does the nsc-ircc patch only work if CONFIG_PNPACPI is set in the kernel config? Otherwise the module loads fine, (but without stating in the kernel log that it found the dongle) and using IRDA does not work, irattach returns "irattach: ioctl(SIOCGIFFLAGS): No such device".

--[[User:Spiney|spiney]] 14:37, 12 Jan 2006 (CET)
----

Talk:Problems with fglrx

2006-01-11T06:29:11Z

Spiney: /* 8.20.8 does work fine with current Debian sid packages */

Talk:Problems with fglrx

2006-01-10T18:42:04Z

Spiney: question about VGA port, removed noexec /tmp issue since it's none anymore

Problems with SATA and Linux

2006-01-10T14:12:08Z

Spiney: /* Hang on resume from suspend to RAM */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Some ThinkPad models use a SATA controller for the system hard disk. This causes several complications for Linux installation. The following lists these problems and known workarounds. Note that the details are often version- and distribution-specific.

===Models using a SATA disk interface===
Models using a SATA controller and a SATA system disk:
*ThinkPad {{Z60t}}, {{Z60m}}
Models using a SATA controller and a PATA (IDE) system disk with a SATA-to-PATA bridge:
*ThinkPad {{T43}}, {{T43p}}
*ThinkPad {{R52}}
*ThinkPad {{X41}}, {{X41T}}

{{NOTE|Some of these problems (namely SMART support, power management and disk information) will be solved in Linux 2.6.15 with the inclusion of libata pass-through. See the SATA driver [http://linux.yyz.us/sata/features.html features], [http://linux.yyz.us/sata/software-status.html software status] and [http://linux.yyz.us/sata/sata-status.html hardware status].}}
|}

==Hang on resume from suspend to RAM==

Linux kernels (as of 2.6.15-rc3) do not support suspend and resume for SATA devices. As a result, the machine hangs upon the first disk access after resume. A kernel patch ([http://lkml.org/lkml/2005/5/2/46 LKML posting]) fixes this by adding SATA power management support.

Current kernel snapshots from the git-repository [http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9b847548663ef1039dd49f0eb4463d001e596bc3 have the patch already included], so hopefully no more patching will be necessary with 2.6.16.

===Patches===
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff Patch for kernel 2.6.12]
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.13-rc5.diff Patch for kernel 2.6.13-rc5]
* [http://lkml.org/lkml/2005/9/23/97 Patch for kernel 2.6.14]
* [http://www.xenotime.net/linux/SATA/2.6.15-rc/libata_suspend.patch Patch for kernel 2.6.15-rc4]
* [http://tpctl.sourceforge.net/tmp/sata_pm.2.6.15-rc6.patch Patch for kernels 2.6.15-rc6 through 2.6.15]

Some distributions already include this patch (e.g., {{Ubuntu}} Breezy), but some don't (e.g., {{Fedora}} 4).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169201 bug 169201: "SATA drives fail on laptop suspend"]

==Failed resume from suspend to disk==

Suspend to disk (using swsusp or [[Software Suspend 2]]) needs to load the memory image from the SATA disk. For this to work, you either need an initrd with all the necessary SATA modules, or the SATA drivers compiled into the kernel.

==DVD drive not recognized==

The <tt>ata_piix</tt> SATA driver grabs ownership over the IDE ports when it is loaded, but (by default) does not support PATA ATAPI devices such as the Ultrabay optical drives. Thus, if the <tt>ide</tt> driver is compiled as a module and loaded after <tt>ata_piix</tt>, the DVD drive will not be recognized by either driver.

Either of the following configurations will work:
* For kernel 2.6.14 and newer: enable ATAPI support in the SATA system using {{bootparm|libata.atapi_enabled|1}} (see below; this is experimental).
* Compile IDE into the kernel (non-module).
* Compile both IDE and SATA as modules and make sure IDE is loaded first (the module is called 'ide_generic').

Note that the optical drive must be in the Ultrabay during system boot (Ultrabay device swapping is currently unsupported).

==No DMA on DVD drive==

Using the IDE driver, DMA support cannot be enabled on an Ultrabay optical drive:

# hdparm -d1 /dev/hdc

/dev/hdc:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)

As a result, the optical drive is slow, and in particular, too slow to play video DVDs.

One workaround is to use employ the SATA driver (instead of the IDE driver) for the optical drive. This requires enabling two featues of the SATA driver, namely ATAPI support and PATA support, which are both in active development and far from stable. Using this will probably devour all your data and go on to eat all the food in your fridge. But if you have full backups and an empty fridge, do the following:

* Grab the latest kernel (must be 2.6.14 or newer; the relevant code is under active development).
* Do one of the following:
** Configure the SATA system (and in particular <tt>ata_piix</tt> and <tt>libata</tt>) as built-in and add {{bootparm|libata.atapi_enabled|1}} to your kernel command line (e.g., in in {{path|/boot/grub/menu.lst}}).
** Configure the SATA system as module (this is often the default) and add "<tt>options libata atapi_enabled=1</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* Do one of the following:
** Disable the IDE system.
** Build the IDE driver as built-in (this is often the default) and add the {{bootparm|hdc|noprobe}} kernel argument (e.g., in in {{path|/boot/grub/menu.lst}}).
** Build the IDE driver as module and add "<tt>options ide hdc=noprobe</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* If you chose to use modules above, regenerate your <tt>initrd</tt> file.

If this doesn't work, use {{cmd|lspci -vn|}} to check whether one of the following chipsets is used in the Thinkpad:
{| border="1" cellspacing="0" cellpadding="2"
|-
!PCI ID
!Name
|-
|8086:7111
|Intel 82371AB/EB/MB PIIX4 IDE
|-
|8086:24db
|Intel 82801EB/ER (ICH5/ICH5R) IDE Controller
|-
|8086:25a2
|Intel 6300ESB PATA Storage Controller
|}
If yes, enable support for these chipsets has to be enabled by setting
#define ATA_ENABLE_PATA
in {{path|include/linux/libata.h}} (and report your ThinkPad model in the discussion page).

There have been reports that DVD burning doesn't work under this configuration, but it seems to work with kernel 2.6.14 and later (tested on a ThinkPad {{T43}} and {{T43p}} with a [[UltraBay Slim DVD Multi-Burner Plus]]).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163418 bug 163418: "can't enable DMA on DVD drive"]

==No DMA on system hard disk==

In some Linux kernels, both the SATA driver and the IDE driver can handle the system hard disk. With the SATA driver, it shows as {{path|/dev/sda}} and DMA is enabled. With the IDE driver, it shows as {{path|/dev/hda}} and DMA is disabled.

The simplest way to enable DMA is to force the IDE driver to ignore the system hard disk by passing the {{bootparm|hda|noprobe}} kernel argument. The driver will then be handled by the SATA driver. Note that this will change its device name to {{path|/dev/sda}} (which may require changes in {{path|/etc/fstab}} and the boot loader) and may cause other problems as listed above.

(Observed on a ThinkPad T43 with Fedora Core kernel 2.6.13-1.1526_FC4.)

==No SMART support==

Prior to kernel 2.6.15, the Linux SATA system did not support SMART commands (e.g., via smartctl).

The necessary capability is "libata pass-through", which was incorporated into Linux 2.6.15-rc1 and later. A patch is available for older kernels:
* Kernel 2.6.12: http://rtr.ca/dell_i9300/kernel/kernel-2.6.12/03_libata_passthru.patch
* Kernel 2.6.13: http://rtr.ca/dell_i9300/kernel/kernel-2.6.13/02_libata_passthru.patch
* Kernel 2.6.14: http://www.foo.fh-furtwangen.de/~koenigr/02_libata_passthru.fixed.again.patch
* Kernel 2.6.14 with the above suspend-to-RAM patch: http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch

After applying the patch, run smartctl with the "-d ata" parameter:
:{{cmdroot|smartctl -d ata -a /dev/sda}}

==No disk power management==

Prior to kernel 2.6.15, the Linux SATA system did not support power management commands on these models.

The above patches for SMART support resolves this, and in particular enables the following commands:
* {{cmdroot|hdparm -y}} (spin down)
* {{cmdroot|hdparm -S num}} (automatic spin down timeout)
* {{cmdroot|hdparm -B num}} (advanced power management level)
Note that this command is still rejected:
* {{cmdroot|hdparm -M num}} (acoustic management)
(Tested with patched kernels 2.6.13.1 and 2.6.12-4 and a 60GB 7200RPM disk model HTS726060M9AT00.)

Note that even when [[Laptop-mode]] is used, the "hddtemp" daemon (as shipped with Fedora Core 4) will wake up the disk every minute, and must thus be disabled for power management to be effective. Its accesses are not visibile through the {{path|/proc/sys/vm/block_dump}} facility. It is unclear whether disk temperature can be monitored without causing the disk to spin up (on the {{T43}}, none of the {{path|/proc/acpi/ibm/thermal}} values corresponds to the disk's built-in temperature sensor).

==No disk information==

Prior to kernel 2.6.15, on these models the disk information could not be read by the standard commands such as:
*{{cmdroot|hdparm -i /dev/sda}}
*{{cmdroot|hdparm -I /dev/sda}}
The latter is fixed by the above patch for SMART support.

==No swapping of UltraBay device==

The <tt>libata</tt> driver does not yet support hot-swapping (or warm-swapping) of PATA devices. If you use a DVD or 2nd PATA HDD via the <tt>libata</tt> (SATA) driver, to swap them in or out you must power down the machine.

If you use the <tt>ide</tt> driver for a PATA UltraBay device, hot-swapping might work using <tt>hdparm</tt>, <tt>idectl</tt> or <tt>hotswap</tt> (please report). However, DMA will be disabled on these models (see above).

If you use a SATA device in the UltraBay, <tt>libata</tt> hot-swapping might work (please report).

Swapping of the [[UltraBay Slim Battery]] does work.

==BIOS error 2010 on user-installed hard disk==

While not a Linux issue, note that there is an issue with installing alternative PATA (IDE) hard disks as the system drive. Unless the disk is one of the few approved disks listed inside the BIOS, you will get an BIOS error 2010 during system boot, and the disk may operate unreliably. See [[Problem with non-ThinkPad hard disks]].

Problems with SATA and Linux

2006-01-10T14:05:24Z

Spiney: /* Patches */ patch from git doesn't work due to lack of ata_exec_internal()

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Some ThinkPad models use a SATA controller for the system hard disk. This causes several complications for Linux installation. The following lists these problems and known workarounds. Note that the details are often version- and distribution-specific.

===Models using a SATA disk interface===
Models using a SATA controller and a SATA system disk:
*ThinkPad {{Z60t}}, {{Z60m}}
Models using a SATA controller and a PATA (IDE) system disk with a SATA-to-PATA bridge:
*ThinkPad {{T43}}, {{T43p}}
*ThinkPad {{R52}}
*ThinkPad {{X41}}, {{X41T}}

{{NOTE|Some of these problems (namely SMART support, power management and disk information) will be solved in Linux 2.6.15 with the inclusion of libata pass-through. See the SATA driver [http://linux.yyz.us/sata/features.html features], [http://linux.yyz.us/sata/software-status.html software status] and [http://linux.yyz.us/sata/sata-status.html hardware status].}}
|}

==Hang on resume from suspend to RAM==

Linux kernels (as of 2.6.15-rc3) do not support suspend and resume for SATA devices. As a result, the machine hangs upon the first disk access after resume. A kernel patch ([http://lkml.org/lkml/2005/5/2/46 LKML posting]) fixes this by adding SATA power management support.

===Patches===
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff Patch for kernel 2.6.12]
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.13-rc5.diff Patch for kernel 2.6.13-rc5]
* [http://lkml.org/lkml/2005/9/23/97 Patch for kernel 2.6.14]
* [http://www.xenotime.net/linux/SATA/2.6.15-rc/libata_suspend.patch Patch for kernel 2.6.15-rc4]
* [http://tpctl.sourceforge.net/tmp/sata_pm.2.6.15-rc6.patch Patch for kernels 2.6.15-rc6 through 2.6.15]

Some distributions already include this patch (e.g., {{Ubuntu}} Breezy), but some don't (e.g., {{Fedora}} 4).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169201 bug 169201: "SATA drives fail on laptop suspend"]

==Failed resume from suspend to disk==

Suspend to disk (using swsusp or [[Software Suspend 2]]) needs to load the memory image from the SATA disk. For this to work, you either need an initrd with all the necessary SATA modules, or the SATA drivers compiled into the kernel.

==DVD drive not recognized==

The <tt>ata_piix</tt> SATA driver grabs ownership over the IDE ports when it is loaded, but (by default) does not support PATA ATAPI devices such as the Ultrabay optical drives. Thus, if the <tt>ide</tt> driver is compiled as a module and loaded after <tt>ata_piix</tt>, the DVD drive will not be recognized by either driver.

Either of the following configurations will work:
* For kernel 2.6.14 and newer: enable ATAPI support in the SATA system using {{bootparm|libata.atapi_enabled|1}} (see below; this is experimental).
* Compile IDE into the kernel (non-module).
* Compile both IDE and SATA as modules and make sure IDE is loaded first (the module is called 'ide_generic').

Note that the optical drive must be in the Ultrabay during system boot (Ultrabay device swapping is currently unsupported).

==No DMA on DVD drive==

Using the IDE driver, DMA support cannot be enabled on an Ultrabay optical drive:

# hdparm -d1 /dev/hdc

/dev/hdc:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)

As a result, the optical drive is slow, and in particular, too slow to play video DVDs.

One workaround is to use employ the SATA driver (instead of the IDE driver) for the optical drive. This requires enabling two featues of the SATA driver, namely ATAPI support and PATA support, which are both in active development and far from stable. Using this will probably devour all your data and go on to eat all the food in your fridge. But if you have full backups and an empty fridge, do the following:

* Grab the latest kernel (must be 2.6.14 or newer; the relevant code is under active development).
* Do one of the following:
** Configure the SATA system (and in particular <tt>ata_piix</tt> and <tt>libata</tt>) as built-in and add {{bootparm|libata.atapi_enabled|1}} to your kernel command line (e.g., in in {{path|/boot/grub/menu.lst}}).
** Configure the SATA system as module (this is often the default) and add "<tt>options libata atapi_enabled=1</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* Do one of the following:
** Disable the IDE system.
** Build the IDE driver as built-in (this is often the default) and add the {{bootparm|hdc|noprobe}} kernel argument (e.g., in in {{path|/boot/grub/menu.lst}}).
** Build the IDE driver as module and add "<tt>options ide hdc=noprobe</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* If you chose to use modules above, regenerate your <tt>initrd</tt> file.

If this doesn't work, use {{cmd|lspci -vn|}} to check whether one of the following chipsets is used in the Thinkpad:
{| border="1" cellspacing="0" cellpadding="2"
|-
!PCI ID
!Name
|-
|8086:7111
|Intel 82371AB/EB/MB PIIX4 IDE
|-
|8086:24db
|Intel 82801EB/ER (ICH5/ICH5R) IDE Controller
|-
|8086:25a2
|Intel 6300ESB PATA Storage Controller
|}
If yes, enable support for these chipsets has to be enabled by setting
#define ATA_ENABLE_PATA
in {{path|include/linux/libata.h}} (and report your ThinkPad model in the discussion page).

There have been reports that DVD burning doesn't work under this configuration, but it seems to work with kernel 2.6.14 and later (tested on a ThinkPad {{T43}} and {{T43p}} with a [[UltraBay Slim DVD Multi-Burner Plus]]).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163418 bug 163418: "can't enable DMA on DVD drive"]

==No DMA on system hard disk==

In some Linux kernels, both the SATA driver and the IDE driver can handle the system hard disk. With the SATA driver, it shows as {{path|/dev/sda}} and DMA is enabled. With the IDE driver, it shows as {{path|/dev/hda}} and DMA is disabled.

The simplest way to enable DMA is to force the IDE driver to ignore the system hard disk by passing the {{bootparm|hda|noprobe}} kernel argument. The driver will then be handled by the SATA driver. Note that this will change its device name to {{path|/dev/sda}} (which may require changes in {{path|/etc/fstab}} and the boot loader) and may cause other problems as listed above.

(Observed on a ThinkPad T43 with Fedora Core kernel 2.6.13-1.1526_FC4.)

==No SMART support==

Prior to kernel 2.6.15, the Linux SATA system did not support SMART commands (e.g., via smartctl).

The necessary capability is "libata pass-through", which was incorporated into Linux 2.6.15-rc1 and later. A patch is available for older kernels:
* Kernel 2.6.12: http://rtr.ca/dell_i9300/kernel/kernel-2.6.12/03_libata_passthru.patch
* Kernel 2.6.13: http://rtr.ca/dell_i9300/kernel/kernel-2.6.13/02_libata_passthru.patch
* Kernel 2.6.14: http://www.foo.fh-furtwangen.de/~koenigr/02_libata_passthru.fixed.again.patch
* Kernel 2.6.14 with the above suspend-to-RAM patch: http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch

After applying the patch, run smartctl with the "-d ata" parameter:
:{{cmdroot|smartctl -d ata -a /dev/sda}}

==No disk power management==

Prior to kernel 2.6.15, the Linux SATA system did not support power management commands on these models.

The above patches for SMART support resolves this, and in particular enables the following commands:
* {{cmdroot|hdparm -y}} (spin down)
* {{cmdroot|hdparm -S num}} (automatic spin down timeout)
* {{cmdroot|hdparm -B num}} (advanced power management level)
Note that this command is still rejected:
* {{cmdroot|hdparm -M num}} (acoustic management)
(Tested with patched kernels 2.6.13.1 and 2.6.12-4 and a 60GB 7200RPM disk model HTS726060M9AT00.)

Note that even when [[Laptop-mode]] is used, the "hddtemp" daemon (as shipped with Fedora Core 4) will wake up the disk every minute, and must thus be disabled for power management to be effective. Its accesses are not visibile through the {{path|/proc/sys/vm/block_dump}} facility. It is unclear whether disk temperature can be monitored without causing the disk to spin up (on the {{T43}}, none of the {{path|/proc/acpi/ibm/thermal}} values corresponds to the disk's built-in temperature sensor).

==No disk information==

Prior to kernel 2.6.15, on these models the disk information could not be read by the standard commands such as:
*{{cmdroot|hdparm -i /dev/sda}}
*{{cmdroot|hdparm -I /dev/sda}}
The latter is fixed by the above patch for SMART support.

==No swapping of UltraBay device==

The <tt>libata</tt> driver does not yet support hot-swapping (or warm-swapping) of PATA devices. If you use a DVD or 2nd PATA HDD via the <tt>libata</tt> (SATA) driver, to swap them in or out you must power down the machine.

If you use the <tt>ide</tt> driver for a PATA UltraBay device, hot-swapping might work using <tt>hdparm</tt>, <tt>idectl</tt> or <tt>hotswap</tt> (please report). However, DMA will be disabled on these models (see above).

If you use a SATA device in the UltraBay, <tt>libata</tt> hot-swapping might work (please report).

Swapping of the [[UltraBay Slim Battery]] does work.

==BIOS error 2010 on user-installed hard disk==

While not a Linux issue, note that there is an issue with installing alternative PATA (IDE) hard disks as the system drive. Unless the disk is one of the few approved disks listed inside the BIOS, you will get an BIOS error 2010 during system boot, and the disk may operate unreliably. See [[Problem with non-ThinkPad hard disks]].

Talk:SMAPI support for Linux

2006-01-10T11:23:27Z

Spiney: /* Feedback */ 0.15 works

Talk:SMAPI support for Linux

2006-01-10T07:12:33Z

Spiney: /* Feedback */ problems with 0.14

Talk:Problems with fglrx

2006-01-08T12:27:27Z

Spiney: /* 8.20.8 does work fine with current Debian sid packages */

===Non-executable /tmp===
When {{path|/tmp|}} is mounted with the noexec option, the fglrx driver will produce an error similar to (this is from a {{T43p}}, the dots are some random looking numbers)

{{cmdresult|Exec failed for command "/tmp/firegl1...." (Permission Denied)}}

It doesn't seem to be fatal, but is anyone else getting these? Unfortunately it's not recorded in the Xorg logfile, it can only be seen when starting Xorg from the console.

BTW, when Xorg is already running (with {{path|/tmp|}} executable) and I switch to tty1 and start another X session (with {{path|/tmp|}} mounted noexec)
{{cmd|mount -o remount,noexec /tmp|}}
{{cmd|xinit -- :14|}}

Xorg locks hard, no way to get back into the console or zap Xorg with CTRL-ALT-BS, only thing that still works is syncing disks and resetting via sys-request shortcuts.

--[[User:Spiney|spiney]] 09:01, 17 Nov 2005 (CET)
----

== using kernel AGP vs fglrx AGP ==

Anyone know whether this makes a performance and/or stability difference?

== 8.20.8 does work fine with current Debian sid packages ==

<pre>
spiney@t43p:~$ dpkg -l xserver-xorg
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-============================-============================-==================
ii xserver-xorg 6.9.0.dfsg.1-2 the X.Org X server
spiney@t43p:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY FireGL V3200 Pentium 4 (SSE2) (FireGL) (GNU_ICD)
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)
</pre>

Talk:Problems with fglrx

2006-01-08T12:25:55Z

Spiney: 8.20.8 does work fine with current Debian sid packages

===Non-executable /tmp===
When {{path|/tmp|}} is mounted with the noexec option, the fglrx driver will produce an error similar to (this is from a {{T43p}}, the dots are some random looking numbers)

{{cmdresult|Exec failed for command "/tmp/firegl1...." (Permission Denied)}}

It doesn't seem to be fatal, but is anyone else getting these? Unfortunately it's not recorded in the Xorg logfile, it can only be seen when starting Xorg from the console.

BTW, when Xorg is already running (with {{path|/tmp|}} executable) and I switch to tty1 and start another X session (with {{path|/tmp|}} mounted noexec)
{{cmd|mount -o remount,noexec /tmp|}}
{{cmd|xinit -- :14|}}

Xorg locks hard, no way to get back into the console or zap Xorg with CTRL-ALT-BS, only thing that still works is syncing disks and resetting via sys-request shortcuts.

--[[User:Spiney|spiney]] 09:01, 17 Nov 2005 (CET)
----

== using kernel AGP vs fglrx AGP ==

Anyone know whether this makes a performance and/or stability difference?

== 8.20.8 does work fine with current Debian sid packages ==

<pre>
spiney@t43p:~$ dpkg -l xserver-xorg
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-============================-============================-========================================================================
ii xserver-xorg 6.9.0.dfsg.1-2 the X.Org X server
spiney@t43p:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY FireGL V3200 Pentium 4 (SSE2) (FireGL) (GNU_ICD)
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)
</pre>

Problems with fglrx

2006-01-06T00:32:02Z

Spiney: /* Troubles using software suspend */ no idea what TerminateServer is, but I haven't used it back then

This page discusses issues with the ATI proprietary [[fglrx]] display driver.

== Known Troubles and Solutions ==

=== Kernel-specific troubles ===

Using the current ATI driver (8.20.8) with the current release candidate 2.6.15-rc5 needs a [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]. (info stolen from the table below, but put here for better visibility)

=== No hardware acceleration ===
If the ATI driver works only without the hardware acceleration, take into consideration that {{path|fglrx_dri.so}} was linked against libstdc++.so.5 which may not be present if your system uses gcc-3.4.

To fix this, compile gcc-3.3.5 and copy <tt>libstdc++.so.5*</tt> to {{path|/usr/lib}} and update the dynamic linker cache via {{cmdroot|ldconfig}}.

Another possible cause for broken hardware acceleration (2D and 3D) is the radeonfb framebuffer: Switching to vesafb or vesafb-tng is reported to solve the problem on some systems. Also it has proven helpful to not perform {{cmdroot|modprobe fglrx}} after boot but to have the module loaded via {{path|/etc/modules.autoload/kernel2.x}} at boottime instead.

=== Softlink hell ===

The [[fglrx]] installer replaces the standard X.org OpenGL implementation (Mesa) with its own files, potentially causing collisions with the distribution's file and package management. It is best to install the driver via a package built for your distribution, which will typically include the necessary kludges to make things work. See the [[fglrx]] page for pointers.

====Discussion====

If you install the driver and type "fglrxinfo" which shows you are still using the mesa indirect software GL renderer, you likely have some misplaced softlinks. I find this *really* frustrating, and do not know why it occasionally occurs -> I think it has to do with an apt-get upgrade that sometimes replaces these links. Anyway, go to

: cd /usr/X11R6/lib

and list your GL libraries and links

: ls -la *GL*

You should see something like:

: libGL.so -> libGL.so.1.2

and
: libGL.so.1 -> libGL.so.1.2

If you see a link to a mesa library (something like ->libGL.mesa.1.2), then that's your problem! Restore the softlink with a command similar to:
: ln -s <actual file> <softlink name>

e.g.
: ln -s libGL.so.1.2 libGL.so.1

For some reason, this link might "break" later, giving you the software rendering once more. I renamed the mesa library to mesa.bkup, and the system still found it and linked to it despite the name change. If you have to do this a lot, you could write a restoreGL script...

=====Gentoo=====
I did the above steps with no luck but it's working now so read on:

Because
: ldd /usr/X11R6/bin/glxinfo
showed that my system still uses the xorg-x11 mesa think and the above hint didn't work as expected I looked at this:
: libGL.so.1 => /usr/lib/opengl/xorg-x11/lib/libGL.so.1 (0x400a8000)
Afterwards I did:
: cd /usr/lib/opengl/xorg-x11/lib/
: mv libGL.so.1.2 libGL.so.1.2_backup
: ln -s /usr/lib/libGL.so.1.2 libGL.so.1.2
After another restart of X "fglrxinfo" showed that it's using the right libs now.

=====Alternative for Gentoo=====
Gentoo has built in tools for managing the OpenGL symlinks. They seem to be replacing the old tool with a new one, so one of the following should work for you:

: # opengl-update ati
: # eselect opengl set ati

Eselect is new, and still ~x86(as of the end of 2005), so you may not have it yet. opengl-update is the old tried-and-true method for managing the symlinks. If opengl-update doesn't fix it for you, you should probably tell [http://bugs.gentoo.org Gentoo Bugzilla](assuming they don't know yet)

=== Troubles using software suspend ===
When the computer resumes from suspend, X only displays a garbled image and the computer is frozen.
The problem is acknowledged in ATI's release notes and in knowledge base entry [https://support.ati.com/ics/support/KBResult.asp?searchFor=Search+Words&search.x=0&search.y=0&searchOption=id&questionID=737-218+&task=knowledge&searchTime=-1&productID=&folderID=-1&resultLimit=50 737-218]. Driver version 8.19.10 has "initial support for Suspend and Resume" but is working very nicely for most people (verified on T43, T43p and T42) without vbetool.

If you are using an older version of fglrx, using [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] to save/restore the video card state before/after suspend worked for some people. If you use [[Software Suspend 2|Software Suspend 2 (suspend2)]] scripts, you can simply uncomment <tt>EnableVbetool yes</tt> in {{path|/etc/hibernate/hibernate.conf}}. Be aware though that it breaks suspend/resume for drivers beginning with version 8.19.10, so remember to disable it again when upgrading.

{| cellspacing="0" cellpadding="2" border="1"
|+ tested with the following configurations
!model!!distro||kernel!!fglrx!!PM!!success!!comments
|-
|{{T42}}||SUSE 9.3||2.6.11||8.14.13||swsusp||yes||
|-
|{{T41p}}||???||2.6.14||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch]
|-
|{{T42p}}||Debian||2.6.10||Debian packaged||suspend2||yes||
|-
|{{T43}}||Debian sid||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 (but not earlier versions!)
|-
|{{T43}}||Debian etch||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 and without vbetool
|-
|{{T43}}||Ubuntu Breezy||2.6.12-10||8.19.10||swsusp||yes||Perfect. (Finally.)
|-
|{{T43}}||FC4||2.6.14.1||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch], requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)
|-
|{{T43}}||FC4||2.6.14.2||8.19.10||suspend2 2.2-rc11||yes||requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)
|-
|{{T43}}||FC4||2.6.14.3||8.19.10||suspend2 2.2-rc13||no||DRI enabled
|-
|{{T43}}||FC4||2.6.14.3||8.20.8||suspend2 2.2-rc13||no||DRI enabled
|-
|{{R50p}}||???||???||8.19.10||swsusp||yes||
|-
|{{T43p}}||Debian sid||2.6.14||8.19.10||Suspend to RAM||yes||without vbetool or UseDummyXServer, those two ''break'' the resume process here, with DRI enabled
|-
|{{T43p}}||Debian sid||2.6.14.3||8.20.8||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{R52}}||Debian sid||2.6.15-rc5||8.20.8||swsup||yes||both vbetool and UseDummyXServer disabled, DRI enabled, needs [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]
|}

=== Troubles with large RAM ===
Version 8.14.13 (and probably earlier versions) of the driver does not seem to be able to cope with large amounts of RAM: with 512 MB it works, with 1.5 GB it crashes the machine as soon as X is started. The problem is present only if the <tt>fglrx</tt> kernel module is loaded, but independently of whether {{kernelconf|CONFIG_HIGHMEM||||||}} is enabled. A workaround is to limit RAM by adding the {{bootparm|mem|864m}} kernel parameter.

Version 8.16.20 fixes the problem.

===Display switching ===
The switching between internal and external display doesn't work, because the driver blocks messing around with the chipset via ACPI. If you want to use this feature (i.e. during presentations), you should use the VESA server instead (experienced with a R52, Kernel 2.6.11, xorg 6.8.2, fglrx 8.16.20).

===Composite Support===
ATI has not officially supported composite windowing (alpha channel) enabling hardware acclerated translucent windows (primarily for 'eye candy.') Enabling Composite in KDE and the fglrx driver results in a very pretty desktop but unacceptably slow performance on a T43p with ATI's FireGL T2. It is still unusable in its current state (as of driver 8.19.10).

ATI promises support in the future when composite is officially supported by Xorg. Discussion of current status of drivers can be found in the Rage3d forums' (rage3d.com/board) Linux area. Rumor has it that the Microsoft Vista will support composite, so hopefully we will see it before then...

===Hardlock on X logout===
Up from driver version 8.19.10 you will expierence a system hard lock when logging out from X, if the session manager (kdm/gdm) is not properly configured. You have to tell the session manager to restart X.

In the kdm config file (gentoo: /usr/kde/<VERSION>/share/config/kdm/kdmrc) you have to add following to the section '[X-:*-Core]':

'''TerminateServer=true'''

In the gdm config file add:

'''AlwaysRestartServer=true '''

Information from the ATI butracker: http://ati.cchtml.com/show_bug.cgi?id=239

== Patches ==
The following patches might be needed for certain versions of fglrx.

===fglrx 8.20.8===

* [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 for kernel 2.6.15]

===fglrx (unspecified old version)===
* [http://lkml.org/lkml/2005/9/22/183 for kernel >= 2.6.13 ] Missing verify_area bug

===fglrx 8.8.25 ===
* [http://www.rage3d.com/board/showthread.php?t=33798874 for kernels >= 2.6.10]
* [http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch For kernels >= 2.6.11-rc1]

Talk:IrDA

2006-01-05T08:27:00Z

Spiney: /* setpnp */

Talk:IrDA

2006-01-04T20:36:48Z

Spiney: /* setpnp */

The "wrong chip version ff" is a real issue, and having it mentioned makes sure that google searches turn it up with a solution.
[[User:Tonko|Tonko]] 01:41, 8 Oct 2005 (CEST)

----
The present text confused me (as you now have noticed). Maybe it should better reflect that the error is incorrect ("wrong chip version ff" instead of "FIR mode not enabled" or whatever). Would that be acceptable?

[[User:Pebolle|Paul Bolle]] 02:05, 8 Oct 2005 (CEST)
----
If you think you can explain it better, go right ahead. The IrDA document could use some major cleaning.

As long as we still point out that the only error in syslog is "Wrong chip version ff" when trying to load the FIR module without first activating the PnP device. It would be nice if the ISA-PNP patch to the nsc-ircc driver got accepted upstream, so we dont have to do these hacks anymore.
[[User:Tonko|Tonko]] 03:58, 8 Oct 2005 (CEST)
----
Tonko,

Is there a reason why you deleted the TODO entry for linux 2.6 kernel config for SIR? I would like to readd it, but like to hear your reason to remove it first.

[[User:Pebolle|Paul Bolle]] 10:23, 14 Oct 2005 (CEST)

== T23 debianized kernel with probs ==

Found another crazy thing here. T23 2648-2GG, with 2.6.13 and 2.6.14 (Debianized Source). Clear init of nsc-ircc and dongle, but the dongle stays offline (dark and blind). Booted with Knoppix or Bart-PE Windows give correct function of the whole device, viewed with a digicam shows some blinks at init. But not with plain 2.6.13 an 2.6.14 from Debian.
Eric

== setpnp ==

Hello,

since the nsc-ircc patch isn't in 2.6.15, I tried to go the setpnp route, but I don't even get to see {{path|/proc/bus/pnp}} even though I enabled the support for it in the kernel config (once I found out that I need to enable ISA support to even get the option). Has anyone successfully used setpnp to enable the IRDA port or is that just some sort of urban legend? ;)

--[[User:Spiney|spiney]] 19:12, 4 Jan 2006 (CET)
----

Make sure you enable pnp-bios support specifically when compiling the kernel, just enabling pnp support is not enough.
I must however admit that I have not done this, since my ancient TP 770 running a 2.4 kernel, which was at least 5 years ago.

I just looked at a 2.6 menuconfig myself, and could not find the option, but looking at my .config file I can see the CONFIG_PNPBIOS option, so you might just want to edit the config file directly, enable the PNPBIOS option, and run make oldconfig.

--[[User:Tonko|Tonko]] 19:38, 4 Jan 2006 (CET)
----

I do have the pnp-bios support enabled (the option is depending on ISA among others, checked the Kconfig file in the source tree to find it), and also the proc-Interface option, but still no go... maybe it's not compatible with CONFIG_PNPACPI? Oh well, nevermind, going back to the patch, that works with less hassles, I just hope it'll end up in the vanilla kernel eventually. Still thanks for the help.

--[[User:Spiney|spiney]] 20:22, 4 Jan 2006 (CET)
----

Ok, on further investigation (not giving up that easily ;) it really seems that CONFIG_PNPACPI is disabling PnPBIOS, at least dmesg showed something along the lines of "PnPBIOS: disabled by PnPACPI". But, after recompiling without PnPACPI, I still can't get it to work. I can use {{cmd|setpnp|}} and {{cmd|lspnp|}} just fine, but the nsc-ircc module won't load:

<pre>
t43p:~# lspnp 12
12 IBM0071 IBM Thinkpad infrared port
t43p:~# setpnp 12 io 0x2f8 irq 3
t43p:~# lspnp -v 12
12 IBM0071 IBM Thinkpad infrared port
dma 3
io 0x02f8-0x02ff
irq 3
t43p:~# modprobe nsc-ircc io=0x2f8 irq=3 dongle_id=0x09
FATAL: Error inserting nsc_ircc (/lib/modules/2.6.15/kernel/drivers/net/irda/nsc-ircc.ko): No such device
</pre>

Hmm, I'm getting somewhat annoyed... any ideas?

--[[User:Spiney|spiney]] 20:58, 4 Jan 2006 (CET)
----

have you tried just doing {{cmd|setpnp 12 on|}}

--[[User:Tonko|Tonko]] 21:05, 4 Jan 2006 (CET)
----

Yes, that was the first thing I tried, didn't help. BTW, I just fiddled around with lirc a bit (never tried it before), and the lirc_sir module works just fine:

<pre>
lirc_sir: I/O port 0x02f8, IRQ 3.
lirc_sir: Installed.
</pre>

and I was able to get it to control xmms.

{{cmd|setserial|}} doesn't claim the device either:

<pre>
t43p:~# setserial -ag /dev/ttyS0
/dev/ttyS0, Line 0, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 921600, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test
</pre>

I'm really out of ideas.

--[[User:Spiney|spiney]] 21:20, 4 Jan 2006 (CET)
----

Hmm, it should not be ttyS0, but ttyS1 which might be stepping on the resources
ttyS0 is IO 0x3f8 and IRQ 4, while ttyS1 is IO 0x2f8 and IRQ 3.

ttyS0 is your integrated serial port, which even ThinkPads without physical serial port have.

--[[User:Tonko|Tonko]] 21:29, 4 Jan 2006 (CET)

Sorry, I cut'n'paste the wrong device since I checked them both, the output for ttyS1 is identical (apart from "/dev/ttyS1, Line 1" of course).

--[[User:Spiney|spiney]] 21:36, 4 Jan 2006 (CET)
----

Talk:IrDA

2006-01-04T20:20:49Z

Spiney: /* setpnp */

Talk:IrDA

2006-01-04T19:58:26Z

Spiney: /* setpnp */

Talk:IrDA

2006-01-04T19:22:39Z

Spiney: /* setpnp */

Talk:IrDA

2006-01-04T18:12:45Z

Spiney: setpnp

IrDA

2006-01-04T17:50:36Z

Spiney: /* ISA PnP patch */ also works with 2.6.15

== ThinkPad IrDA configuration ==

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

All IBM ThinkPads manufactured in the last years have integrated IrDA that can be used in one of two modes, SIR or FIR.
Some very old ThinkPads only support SIR mode, or might not have IrDA support at all. A newer VFIR standard exists, which supports speeds upto 16Mbps. However for the moment no ThinkPads support this.

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

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

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

=== Fast IR (FIR) ===
FIR is the preferred mode of IrDA operation and operates at a bandwidth of 4 Mbps
==== BIOS settings ====
Main problem here is that the chips FIR mode needs to be activated. On A, G, R, T and X model ThinkPads, the easiest way to activate FIR mode is by entering BIOS setup during boot-up by pressing {{key|F1}} when prompted.
Then, selecting 'Config' followed by 'Infrared' will allow you to control the IrDA operation. Here you will need to select the option to Enable the infra-red port. Be sure to save the changes, and then Exit. Make sure that you do not only enable the Device, also set the resources manually. Else, lirc will remain silent.

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

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

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

setpnp requires a kernel with pnp-bios support compiled in, which the {{Redhat}} and {{Fedora}} kernels lack.
==== ISA PnP patch ====
2.6 kernel ISA PnP Patches exist for the nsc-ircc driver, that allow the loading of the driver without the BIOS, setpnp or tpctl hacks. 
You will still have to call setserial and set the dongle_id parameter, as shown below.

* [http://steffenpingel.de/patches/nsc-ircc-pnp.diff 2.6.10 patch]
* [http://shamrock.dyndns.org/~ln/linux/nsc-ircc-pnp.2.6.12-rc6.diff 2.6.12-rc6 patch]
* [http://shamrock.dyndns.org/~ln/linux/nsc-ircc-pnp.2.6.12.diff 2.6.12 patch (applies cleanly to 2.6.12 through 2.6.15)]

This patch seems ''necessary'' in some cases (e.g., ThinkPad {{T43}} and kernel 2.6.14.2).

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

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

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

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

=== Known problems ===
* If the FIR mode is not activated, attempts to load the nsc-ircc module will result in an error in syslog of "Wrong chip version ff".
* After suspend the nsc-ircc module needs to be manually reloaded
* Module reloading does not work for me after a suspend. The IrDA port has to be actived.
rmmod nsc_ircc
echo disable > /sys/devices/pnp0/00\:0d/resources
echo activate > /sys/devices/pnp0/00\:0d/resources
modprobe nsc_ircc
The value <tt>pnp0/00\:0d</tt> can vary - look for a resources file containing the appropriate irq/dma/io values, e.g., using {{cmdroot|grep 0x2f8 /sys/devices/pnp*/*/resources}} .

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

* add fast PPP support:
:{{cmdroot|modprobe irnet}}
* if needed, limit further the size of the transmit window
:{{cmdroot|echo 1 > /proc/sys/net/irda/max_tx_window}}

== External links ==
*[http://irda.sourceforge.net/ Linux-IrDA Project] (External)
*[http://pcmcia-cs.sourceforge.net/ Linux PCMCIA Project] (External)
*[http://tpctl.sourceforge.net/ tpctl homepage] (External)
*[http://www.lirc.org/ Linux Infrared Remote Control] (External)

== Supported Models ==
'''IrDA 1.0 (SIR - 115Kbps)'''
* {{365C}}, {{365CD}}, {{365CS}}, {{365CSD}}, {{365E}}, {{365ED}}, {{365X}}, {{365XD}}
* {{560}}
* {{755CD}}, {{755CDV}}, {{755CE}}, {{755CSE}}, {{755CV}}, {{755CX}}
* {{760C}}, {{760CD}}, {{760E}}, {{760ED}}, {{760EL}}, {{760ELD}}, {{760L}}, {{760LD}}, {{760XD}}, {{760XL}}
* {{765D}}, {{765L}}
* {{PC110}}
'''IrDA 1.1 (FIR - 4Mbps)'''
* {{240}}, {{240X}}
* {{380}}, {{380D}}, {{380E}}, {{380ED}}, {{380XD}}, {{380Z}}
* {{385D}}, {{385ED}}, {{385XD}}
* {{390}}, {{390E}}, {{390X}}
* {{560E}}, {{560X}}, {{560Z}}
* {{570}}, {{570E}}
* {{600}}, {{600E}}, {{600X}}
* {{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}
* {{A Series}}
* {{i1720}}, {{i1721}}
* {{R Series}}
* {{T Series}}
* {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}} and {{X41T}}
* {{Z60m}}, {{Z60t}}
* {{TransNote}}

[[Category:Drivers]]

Problems with SATA and Linux

2006-01-04T17:13:48Z

Spiney: /* Patches */ rc6 patch works fine for 2.6.15

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Some ThinkPad models use a SATA controller for the system hard disk. This causes several complications for Linux installation. The following lists these problems and known workarounds. Note that the details are often version- and distribution-specific.

===Models using a SATA disk interface===
Models using a SATA controller and a SATA system disk:
*ThinkPad {{Z60t}}, {{Z60m}}
Models using a SATA controller and a PATA (IDE) system disk with a SATA-to-PATA bridge:
*ThinkPad {{T43}}, {{T43p}}
*ThinkPad {{R52}}
*ThinkPad {{X41}}, {{X41T}}

{{NOTE|Some of these problems (namely SMART support, power management and disk information) will be solved in Linux 2.6.15 with the inclusion of libata pass-through. See the SATA driver [http://linux.yyz.us/sata/features.html features], [http://linux.yyz.us/sata/software-status.html software status] and [http://linux.yyz.us/sata/sata-status.html hardware status].}}
|}

==Hang on resume from suspend to RAM==

Linux kernels (as of 2.6.15-rc3) do not support suspend and resume for SATA devices. As a result, the machine hangs upon the first disk access after resume. A kernel patch ([http://lkml.org/lkml/2005/5/2/46 LKML posting]) fixes this by adding SATA power management support.

===Patches===
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff Patch for kernel 2.6.12]
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.13-rc5.diff Patch for kernel 2.6.13-rc5]
* [http://lkml.org/lkml/2005/9/23/97 Patch for kernel 2.6.14]
* [http://www.xenotime.net/linux/SATA/2.6.15-rc/libata_suspend.patch Patch for kernel 2.6.15-rc4]
* [http://tpctl.sourceforge.net/tmp/sata_pm.2.6.15-rc6.patch Patch for kernel 2.6.15-rc6 (and also the 2.6.15 final)]

Some distributions already include this patch (e.g., {{Ubuntu}} Breezy), but some don't (e.g., {{Fedora}} 4).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169201 bug 169201: "SATA drives fail on laptop suspend"]

==Failed resume from suspend to disk==

Suspend to disk (using swsusp or [[Software Suspend 2]]) needs to load the memory image from the SATA disk. For this to work, you either need an initrd with all the necessary SATA modules, or the SATA drivers compiled into the kernel.

==DVD drive not recognized==

The <tt>ata_piix</tt> SATA driver grabs ownership over the IDE ports when it is loaded, but (by default) does not support PATA ATAPI devices such as the Ultrabay optical drives. Thus, if the <tt>ide</tt> driver is compiled as a module and loaded after <tt>ata_piix</tt>, the DVD drive will not be recognized by either driver.

Either of the following configurations will work:
* For kernel 2.6.14 and newer: enable ATAPI support in the SATA system using {{bootparm|libata.atapi_enabled|1}} (see below; this is experimental).
* Compile IDE into the kernel (non-module).
* Compile both IDE and SATA as modules and make sure IDE is loaded first (the module is called 'ide_generic').

Note that the optical drive must be in the Ultrabay during system boot (Ultrabay device swapping is currently unsupported).

==No DMA on DVD drive==

Using the IDE driver, DMA support cannot be enabled on an Ultrabay optical drive:

# hdparm -d1 /dev/hdc

/dev/hdc:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)

As a result, the optical drive is slow, and in particular, too slow to play video DVDs.

One workaround is to use employ the SATA driver (instead of the IDE driver) for the optical drive. This requires enabling two featues of the SATA driver, namely ATAPI support and PATA support, which are both in active development and far from stable. Using this will probably devour all your data and go on to eat all the food in your fridge. But if you have full backups and an empty fridge, do the following:

* Grab the latest kernel (must be 2.6.14 or newer; the relevant code is under active development).
* Do one of the following:
** Configure the SATA system (and in particular <tt>ata_piix</tt> and <tt>libata</tt>) as built-in and add {{bootparm|libata.atapi_enabled|1}} to your kernel command line (e.g., in in {{path|/boot/grub/menu.lst}}).
** Configure the SATA system as module (this is often the default) and add "<tt>options libata atapi_enabled=1</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* Do one of the following:
** Disable the IDE system.
** Build the IDE driver as built-in (this is often the default) and add the {{bootparm|hdc|noprobe}} kernel argument (e.g., in in {{path|/boot/grub/menu.lst}}).
** Build the IDE driver as module and add "<tt>options ide hdc=noprobe</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* If you chose to use modules above, regenerate your <tt>initrd</tt> file.

If this doesn't work, use {{cmd|lspci -vn|}} to check whether one of the following chipsets is used in the Thinkpad:
{| border="1" cellspacing="0" cellpadding="2"
|-
!PCI ID
!Name
|-
|8086:7111
|Intel 82371AB/EB/MB PIIX4 IDE
|-
|8086:24db
|Intel 82801EB/ER (ICH5/ICH5R) IDE Controller
|-
|8086:25a2
|Intel 6300ESB PATA Storage Controller
|}
If yes, enable support for these chipsets has to be enabled by setting
#define ATA_ENABLE_PATA
in {{path|include/linux/libata.h}} (and report your ThinkPad model in the discussion page).

There have been reports that DVD burning doesn't work under this configuration, but it seems to work with kernel 2.6.14 and later (tested on a ThinkPad {{T43}} and {{T43p}} with a [[UltraBay Slim DVD Multi-Burner Plus]]).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163418 bug 163418: "can't enable DMA on DVD drive"]

==No DMA on system hard disk==

In some Linux kernels, both the SATA driver and the IDE driver can handle the system hard disk. With the SATA driver, it shows as {{path|/dev/sda}} and DMA is enabled. With the IDE driver, it shows as {{path|/dev/hda}} and DMA is disabled.

The simplest way to enable DMA is to force the IDE driver to ignore the system hard disk by passing the {{bootparm|hda|noprobe}} kernel argument. The driver will then be handled by the SATA driver. Note that this will change its device name to {{path|/dev/sda}} (which may require changes in {{path|/etc/fstab}} and the boot loader) and may cause other problems as listed above.

(Observed on a ThinkPad T43 with Fedora Core kernel 2.6.13-1.1526_FC4.)

==No SMART support==

Prior to kernel 2.6.15, the Linux SATA system did not support SMART commands (e.g., via smartctl).

The necessary capability is "libata pass-through", which was incorporated into Linux 2.6.15-rc1 and later. A patch is available for older kernels:
* Kernel 2.6.12: http://rtr.ca/dell_i9300/kernel/kernel-2.6.12/03_libata_passthru.patch
* Kernel 2.6.13: http://rtr.ca/dell_i9300/kernel/kernel-2.6.13/02_libata_passthru.patch
* Kernel 2.6.14: http://www.foo.fh-furtwangen.de/~koenigr/02_libata_passthru.fixed.again.patch
* Kernel 2.6.14 with the above suspend-to-RAM patch: http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch

After applying the patch, run smartctl with the "-d ata" parameter:
:{{cmdroot|smartctl -d ata -a /dev/sda}}

==No disk power management==

Prior to kernel 2.6.15, the Linux SATA system did not support power management commands on these models.

The above patches for SMART support resolves this, and in particular enables the following commands:
* {{cmdroot|hdparm -y}} (spin down)
* {{cmdroot|hdparm -S num}} (automatic spin down timeout)
* {{cmdroot|hdparm -B num}} (advanced power management level)
Note that this command is still rejected:
* {{cmdroot|hdparm -M num}} (acoustic management)
(Tested with patched kernels 2.6.13.1 and 2.6.12-4 and a 60GB 7200RPM disk model HTS726060M9AT00.)

Note that even when [[Laptop-mode]] is used, the "hddtemp" daemon (as shipped with Fedora Core 4) will wake up the disk every minute, and must thus be disabled for power management to be effective. Its accesses are not visibile through the {{path|/proc/sys/vm/block_dump}} facility. It is unclear whether disk temperature can be monitored without causing the disk to spin up (on the {{T43}}, none of the {{path|/proc/acpi/ibm/thermal}} values corresponds to the disk's built-in temperature sensor).

==No disk information==

Prior to kernel 2.6.15, on these models the disk information could not be read by the standard commands such as:
*{{cmdroot|hdparm -i /dev/sda}}
*{{cmdroot|hdparm -I /dev/sda}}
The latter is fixed by the above patch for SMART support.

==No swapping of UltraBay device==

The <tt>libata</tt> driver does not yet support hot-swapping (or warm-swapping) of PATA devices. If you use a DVD or 2nd PATA HDD via the <tt>libata</tt> (SATA) driver, to swap them in or out you must power down the machine.

If you use the <tt>ide</tt> driver for a PATA UltraBay device, hot-swapping might work using <tt>hdparm</tt>, <tt>idectl</tt> or <tt>hotswap</tt> (please report). However, DMA will be disabled on these models (see above).

If you use a SATA device in the UltraBay, <tt>libata</tt> hot-swapping might work (please report).

Swapping of the [[UltraBay Slim Battery]] does work.

==BIOS error 2010 on user-installed hard disk==

While not a Linux issue, note that there is an issue with installing alternative PATA (IDE) hard disks as the system drive. Unless the disk is one of the few approved disks listed inside the BIOS, you will get an BIOS error 2010 during system boot, and the disk may operate unreliably. See [[Problem with non-ThinkPad hard disks]].

Talk:How to enable integrated fingerprint reader with BioAPI

2005-12-23T09:12:41Z

Spiney: /* Permission errors exclusive to xscreensaver */

==Changing the installation path==
By default, bioapi will install numerous files in {{path|/usr/local/<nowiki>{</nowiki>bin,lib,include<nowiki>}</nowiki>}}, including files with "self-explanatory" names such as {{path|/usr/local/bin/Sample}}. To prevent this pollution:
* Create a dedicated directory,say, {{path|/opt/bioapi}} .
* Append <tt>--prefix=/opt/bioapi</tt> to the <tt>./configure</tt> command of bioapi
* Append {{path|/opt/bioapi/bin}} to <tt>$PATH</tt> and {{path|/opt/bioapi/lib}} to <tt>$LD_LIBRARY_PATH</tt>
* Edit the install path in {{path|install.sh}} of the driver

--[[User:Thinker|Thinker]] 18:06, 30 Oct 2005 (CET)
----

== chmod 777 -R /usr/local/var/bioapi/ ==

Is the above necessary? I just made a debian package of xscreensaver with the patch applied, and when using the bioapi debian pacakge from [http://www.qrivy.net/~michael/temp/ Michael R. Crusoe's site] which has this directory put in /usr/var/bioapi I had not to change the permissions to world-writeable there. Write access to the logfile and usb device are necessary, but that directory works with 755 as well (even though it comes with 777 in Michael's package), and all files and subdirectories are 644/755 too.

--[[User:Spiney|spiney]] 00:08, 11 Nov 2005 (CET)
----

== Qt Compilation Success ==

Here it worked with qt ;)

== using absolute paths for commands ==

I don't know whether using absolute paths in the articles is a good idea, at least not for tools like {{cmd|lsusb|}} which are not established utilities (i.e. used for more than a decade or something ;)) and happen to be in different locations in different distributions. E.g. said {{cmd|lsusb|}} resides in {{path|/usr/sbin|}} on Debian systems.

--[[User:Spiney|spiney]] 16:45, 12 Nov 2005 (CET)
----

== BioAPI error #3 ==

Its kind of strage it used to work with everythig (kdm,console,lock,etc)
Now it only works with kdm. It allways gives back:

pam_bioapi[8113]: Unable to initialize Bioapi framework, BioAPI error #:3.

Even when I set the right permissions on /proc/bus/usb.

I am able to run the Sample program as normal user after setting the permissions, but when I change within a user session by su I amnot able to run the Sample program a also get an error Code #3.

From an other terminal (alt+strg+Fx) I am able to run the Sample program but at the login I still get the error #3.

I cant remember to have changed anything an d bevor I was able to login in a console with my fingerprint now only kdm is working even kde lock-session
isnt working anymore.

Any suggestions ?

==Permission errors exclusive to xscreensaver==

I followed the instructions above and got everything working, including non-root programs like xscreensaver. However, the script to change usbfs permissions is finicky and fails to work with a lot of things like suspend/resume. Therefore, I switched to specifying <tt>devgid=108,devmode=0660,busgid=108,busmode=0770,listgid=108,listmode=0660</tt> as mount parameters for usbfs, where group 108 is a group I created and added my normal user to. This seems like a much better way of doing things, and it almost works. However, xscreensaver (using the newer patch) gives the familiar <tt>Unable to load BioAPI BSP with UUID of <nowiki>{</nowiki>5550454b-2054-464d-2f45-535320425350<nowiki>}</nowiki>, BioAPI error #194d.</tt> error in {{path|/var/log/auth.log|}}. I don't think this is a straightfoward permissions problem because
<ul>
<li>the permissions in {{path|/proc/bus/usb|}} are correct by inspection</li>
<li>I can write to the device file as my normal user</li>
<li>other programs like {{cmd|test_verify-pam_bioapi|}} and [http://pamtester.sourceforge.net/ {{cmd|pamtester|}}] work as my normal user</li>
<li>the weirdest one: xscreensaver works when the {{cmd|xscreensaver|}} daemon is launched from within {{cmd|strace|}}. It's still running as my normal user ({{cmd|strace|}} is not setuid root). I have absolutely no idea what would cause this. I thought it might be an environment issue, but the difference in environment between the {{cmd|strace|}} session and my normal session is trivial.</li>
</ul>

At this point I'm hoping it's something dumb, but I'm out of ideas. The {{cmd|xscreensaver|}} error is <tt>pam_authenticate (...) ==> 7 (Authentication failure)</tt>, for the record.

--[[User:keegan|keegan]]
----

Could you provide all the log lines between pam_start and pam_end when running {{cmd|xscreensaver -verbose|}}?

BTW, the idea with using the mount options for usbfs is very good, maybe you should add that info to the article page? I use the permission changing script without problems, also after resume, but the usbfs version is probably easier to set up, most people will be able to find {{path|/etc/fstab|}}.

--[[User:Spiney|spiney]] 10:12, 23 Dec 2005 (CET)
----

==Driver Expiring!!!==
Don't anyone notice that both betas of the UPEK driver is expiring in
about a month in the new year, Jan 1st 2006? They really mean it!
I set my computer date to next year and get a message "the driver has expired" when using fingerprint reader! This is a grave threat to our computer lifestyle, i.e. for those of us who got it working and use it
daily:)
Is there any workaround other than setting the date back a year when
new year come and wait for new driver? Is there a way to figure out where exactly in the driver it checked the date and how? The must have set it
somewhere in file libtfmessbsp.so, but it is binary and I can't figure out how to Reverse Engineer it.

---Jiang

Yes, the beta driver will expire. The final version (which is due REALLY soon now) will not.

Sumedha

Any news? Just 9 days left to expiry. --[[User:Thinker|Thinker]] 21:36, 22 Dec 2005 (CET)

The final is out, get it at [http://www.upek.com/support/dl_linux_bsp.asp UPEK's download page]. And how does one edit the industry watch section of the main page?

--[[User:Spiney|spiney]] 21:39, 22 Dec 2005 (CET)

Ah, great! Both the article page and the driver page it points to are out of date... For the news, just follow the "[[ThinkWiki:News|News]]" link in the main page.

--[[User:Thinker|Thinker]] 21:44, 22 Dec 2005 (CET)

== Updated xscreensaver patch ==

I've tried to address some usability issues with the old patch, e.g. that it calls the PAM bioapi module twice before falling back to the normal authentication methods. It can be found on my [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_fingerprint_reader Fingerprint Reader] page, feedback is very welcome.

--[[User:Spiney|spiney]] 20:36, 22 Dec 2005 (CET)
----

Template:Industry News

2005-12-22T21:32:59Z

Spiney: topics moved to old news

22.12.2005 [http://www.upek.com/support/dl_linux_bsp.asp Version 1.0 (final)] of the BSP for the UPEK fingerprint sensor released.

08.12.2005 New [[fglrx]] driver version 8.20.8 released

11.11.2005 New [[fglrx]] driver version 8.19.10 released, adds suspend and PowerPlay

26.10.2005 New fglrx driver version 8.18.8 released

13.10.2005: Lenovo announces new R51e to be shipping with SUN StarOffice 8.

Template:Industry OldNews

2005-12-22T21:32:55Z

Spiney: topics moved to old news

15.09.2005: Lenovo announces new WideScreen Z Series. Read [http://www.pcmag.com/article2/0,1895,1858628,00.asp here] and [http://news.zdnet.com/2100-1040_22-5862939.html here].

14.09.2005: [http://www.qrivy.net/~michael/blua/upek-bsp.html Beta release] of BSP for UPEK fingerprint sensors released.

17.08.2005: New [[fglrx]] driver version 8.16.20 released

09.06.2005: New [[fglrx]] driver version 8.14.13 released

11.04.2005: IBM and Sanyo demonstrate [http://www.theregister.co.uk/2005/04/11/ibm_sanyo_notebook_fuel_cell/ Fuel Cell prototype]

16.02.2005: New [[fglrx]] driver version 8.10.19 released

04.02.2005: IBM sells its entire PC division to Lenovo (China's largest PC maker), exclusing the eSeries x86 range. The Think* brand is included in the deal and Lenovo has full use of it for 5 years.

17.01.2005: New [[fglrx]] driver version 8.8.25 (finally with X.Org 6.8 support)

28.11.2004: IBM recently released new T42 notebooks featuring Pentium M 765 processors, a FireGL T2 chip, 1GB of RAM and an integrated fingerprint scanner

09.11.2004: New [[fglrx]] driver version 3.14.6 

26.09.2004: [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=TPAD-RECALL IBM recalls 56 Watt Thinkpad AC Adaptors]

Talk:How to enable integrated fingerprint reader with BioAPI

2005-12-22T20:39:41Z

Spiney: /* Driver Expiring!!! */ the final is out

Talk:How to enable integrated fingerprint reader with BioAPI

2005-12-22T19:36:42Z

Spiney: Updated xscreensaver patch

Talk:Pentium M undervolting and underclocking

2005-12-21T10:05:58Z

Spiney: which patch to use?

Hei Thinker,

according to my notion of the character of this page, i thought it should possibly be renamed to something like "How to lower voltage and clock speed on Pentium M processors" ("lower" might be replaced by "finetune" or "manually lower" or "tweak" or something else expressing more the expert audience of the article). This has the following advantages:
*complies with the naming scheme ;-)
*has words more likely to be found in google (voltage vs. undervolting; clock, speed vs. underclocking)
*Are undervolting/underclocking proper english words anyway?
*Follows a scheme of "from general to specific". The topic of the article is underclocking/undervolting. That it's for Pentium M processors is kind of secondary to that.

What do you think? I can do it if you agree.

[[User:Wyrfel|Wyrfel]] 00:21, 21 Oct 2005 (CEST)
----

Good points. Personally I'm fond of short technical titles, but I agree about accessibility and consistency with the rest of the site. I have a feeling (though no proof) that the underclocking doesn't really work (as I noted recently), so how about "Reducing voltage on the Pentium M processor" for now?

BTW, "underclocking" is pretty standard techie jargon (and a clear parallel of the well-known "overclocking"). "Undervolting" is somewhat less common, though I've seen it in use.

--[[User:Thinker|Thinker]] 00:55, 21 Oct 2005 (CEST)
----

== which patch to use? ==

Since I might find the time to fiddle around with reducing the power consumption further, I wonder which of the 3 alternatives works best. Any recommendations?

--[[User:Spiney|spiney]] 11:05, 21 Dec 2005 (CET)
----

Talk:SMAPI support for Linux

2005-12-16T19:44:56Z

Spiney: /* Kernel Patch? */

Help:Reading

2005-12-16T19:26:36Z

Spiney: reverted, removed spam

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page is supposed to guide you in using [[ThinkWiki]]. It offers you strategies on how to find information here in case you need help about a specific topic or just want to know something about your ThinkPad or ThinkPads in general.
|}

==Generic starting points==
There are five generic starting points that can help you whatever your mission might be:
*You can start browsing on the [[ThinkWiki|ThinkWiki start page]]. We will try to keep all ThinkWiki pages accessable in a logical structure that branches out from there.
*You can always use the Search field on the left, enter some word designating what you are looking for, press the search button and hope that one of the search results will be helpful.
*From our [[:Category:Models|ThinkPad models overview]] you can pick your particular model page to get a list with all articles concerning that model.
*And on the [[:Category:Distributions|distributions]] page you can choose your distribution and find all pages containing information related to that distro.
*You can try browsing the [[:Category:ThinkWiki|Categories]].

==Finding help for a specific problem==
ThinkWiki most likely doesn't provide a single page covering exactly your problem. It rather offers you generic starting points where you can start your hunt for information that may give you clues to a solution. The most typical starting points for your solution hunt are:
*The [[Known Problems]] page list pages covering specific problems people have run into with partial or complete solutions to them.
*If you look for information on how to install a specific distro on a specific model, look at the [[Installation]] page.
*In case you have problems installing or configuring a special driver, look at the [[HOWTOs - Driver Installation|Driver installation HOWTO listing]].
*In case you need help or information about the preloaded system, backing it up or recovering it, look at the [[How to recover the preloaded OS|Preload Recovery page]].
*If you run into Power Management related problems, the [[How to make use of Power Management features|Power Management HOWTO]] should help.
There are several more HOWTO pages accessible from the [[ThinkWiki|ThinkWiki main page]]

==Finding information about a specific model==
There are two places to start for that:
*The [[:Category:Models|ThinkPad models overview]] page. It contains a list of all models known to the editors of ThinkWiki, each of them containing general information about that model as well as a list of all articles with information related to it. I.e. if you want to know about the ThinkPad X22, just click on the [[:Category:X22|X22]] page and you'll find all we know about it.
*The second place to look at is the [[Hardware Specifications]] page. Here you will find a list of model and type numbers, ordered by model. Just click on a type number and you'll find detailed specifications of exactly that type. In case your exact model-type number isn't there, look at one of the IBM provided PDF documents linked from that page.

==Finding information about ThinkPads in general==
If you are planning to buy a notebook and want to start with an overall impression of ThinkPads, try the following pages:
*The [[ThinkPad History]] gives a historic overview about the appearance of ThinkPads in chronological order, accompanied with some information about their specialties and features.
*The [[Thinkpad Technologies]] page lists several of the technologies found in various ThinkPads. Each single Technology page in turn holds a list of ThinkPads this featuring this technology.
*Look at the [[Components]] or [[:Category:Components|Components Category]] pages to find out about hardware used in ThinkPad computers.

==Finding information about your specific distribution==
As said above, the [[:Category:Distributions|distributions]] page holds a list of distributions you can find information about on ThinkWiki. Each of the single distribution pages listed there in turn contain a list of all articles with relevant information for that distribution.

==If you don't find what you are looking for==
Well, go figure - and let us know your findings here. ;-) Ok, more seriously, the [[Links]], [[Mailinglists]] and [[IRC]] pages list other sources of useful information. Also pay attention to the "External Sources" and "Related Links" sections found on almost every page. They usually contain a list of useful links to pages outside ThinkWiki. And of course, [http://www.google.org Google] is always your friend.

Good luck.

Talk:SMAPI support for Linux

2005-12-16T18:51:22Z

Spiney: /* Kernel Patch? */ edited for consistency

Talk:SMAPI support for Linux

2005-12-16T18:30:52Z

Spiney: reordered

Talk:SMAPI support for Linux

2005-12-16T18:28:59Z

Spiney: /* Kernel Patch? */ makepatch script

Great, great work! Really! This completely rocks. I just stopped my battery from charging at 77% and restarted charging a bit later, no problems whatsoever. BTW, this is on kernel 2.6.14.3.

--[[User:Spiney|spiney]] 21:25, 5 Dec 2005 (CET)
----
None of the fuctions is working on my T40, kernel 2.6.14-mm2.

--[[User:Lammic|lammic]], 2005.12.05

Works for me on a T41 running 2.6.12-10-686 (Ubuntu 5.10).

--[[User:berndtnm|berndtnm]], 2005.12.06

Including stop_charge_thresh? That one seems to be missing on the T42p.

--[[User:Thinker|Thinker]] 00:46, 7 Dec 2005 (CET)
----

tp_smapi works just fine on an R52 with Ubuntu Breezy stock kernel.

--[[User:Micampe|Micampe]] 12:52, 7 Dec 2005 (CET)

----

''To set the thresholds for starting and stopping battery charging (in percent of current capacity):''

'''current''' really? That'd be weird, I'd expect it to be percent of '''total''' capacity.

--[[User:Micampe|Micampe]] 14:39, 7 Dec 2005 (CET)

"Current full charge capacity", as opposed to "current remaining capacity" or "designed full charge capacity"...

--[[User:Thinker|Thinker]] 15:05, 7 Dec 2005 (CET)
----

Battery features don't work with my T41p. I can't check this with windows. Can anybody try these features?

-- Nils, 7 Dec 2005
----

Nils, does cdrom_speed work for you on the T41p? Could you provide the details requested in the README (dmesg etc.)?

--[[User:Thinker|Thinker]] 21:57, 7 Dec 2005 (CET)
----

CDRom Speed seems to work. (I see no warnings, but I have to do a speed test.) Now, I've send all outputs to the email-address in the readme.

-- Nils, 8 Dec 2005
----

All the features except the stop_charge_thresh seem to work here on a t42p.
One note, the start_charge_thresh seems to really be stop_charge_thresh. Ie, If I set that to lower than my current battery %, it will never charge,
and if I set it to 100 the battery charges all the way.

--[[User:Nirik|Nirik]] 16 Dec 2005
----

Nirik, "all the features" as of which version? For example, do the force_discharge{1,2} in tp_smapi 0.12 also work for you? See the table in the article page. About start_charge, that's odd. Can you send me a log of what you did, what was the result a what was the dmesg output for each operation?

--[[User:Thinker|Thinker]] 14:16, 16 Dec 2005 (CET)
----

==Changing the CD speed when the CD is being accessed will hang your computer==

I don't have this problem on my T40p. CDROM is mounted and file on CD is opened. Change speed do '''not''' hang my system.

-- Stefan Schmidt
----

An open file looks fine if you're not reading/writing at that point. But my T43 does hangs on this:
# dd if=/dev/scd0 of=/dev/null &
# echo 1 > /sys/devices/platform/smapi/cdrom_speed

--[[User:Thinker|Thinker]] 16:41, 7 Dec 2005 (CET)
----

OK, sorry. I was to fast. My system hangs on this commands, too. :(

-- Stefan Schmidt

Works well. Great.

T42 2373-8zh. Working :cdrom_speed and start_charge_thresh. Untest : inhibit_charge_minutes.

-- Haifeng Chen

cdrom_speed works on my T40.

-- [[User:Lammic|lammic]], 2005.12.09

== "thinkpad" module kernel compatibility ==

Ajunge, how do you compile the "thinkpad" module compile on kernel >=2.6.9? The latest thinkpad version (5.8) still uses "get_cpu_ptr" and "set_cpu_ptr", which were removed in 2.6.9.

--[[User:Thinker|Thinker]] 13:53, 10 Dec 2005 (CET)
----

== Kernel Patch? ==

Hello Thinker,

would it be possible to provide the SMAPI support as kernel patch as well? Something along the lines of: (0.12 against 2.6.15-rc5)

''(deleted, see below for how to create a patch file)''

Deleted the tp_smapi.c file at the end, out of obvious reasons, and I'm not sure about the placement in the ACPI section, OTOH there it would be found easily next to ibm_acpi.

Providing a patch would help when recompiling the kernel often, I hate recompiling external modules every time (even got me a kernel-upgrade script to do most of it automatically). But of course it's up to you. :)

--[[User:Spiney|spiney]] 09:52, 16 Dec 2005 (CET)
----

I'll be glad to add this, but I don't want to go through additional manual steps in the release process (there are already quite a few). Can you add a "make patch" functionality to the Makefile, or something of the sort, to automatically generate a full patch (including tp_smapi.c) against current kernel sources?

Also, this shouldn't be under drivers/acpi, since it doesn't use ACPI at all (that's why I didn't make it a patch to ibm_acpi). I think the right place is drivers/firmware, like the dell_rbu driver for Dell laptops.

BTW, the convention for kernel patches is to start them once level higher:
diff -Nurp kernel-2.6.14-vanilla kernel-2.6.14-patched

--[[User:Thinker|Thinker]] 17:12, 16 Dec 2005 (CET)
----

Of course it's from the wrong level, as usual I was just lazy/inattentive. And at one point I'll remember who likes what patch format, promise. ;)

A patch target as in "create a new file holding a correct diff to current kernel source" would be rather difficult, since line numbers might change etc., but applying the patch should be straighforward with a bit of sed. Of course I could just do that, create a patch with the diff command and then apply the new patch file in reverse. ;)

--[[User:Spiney|spiney]] 18:36, 16 Dec 2005 (CET)
----

If it does that on a local copy (no changes the original kernel tree) and cleans up after itself, that's fine with me. :-)

--[[User:Thinker|Thinker]] 18:50, 16 Dec 2005 (CET)
----

Ok, here's a shell script that creates the patch, feel free to use it under the terms of the GPL. For example call it from your Makefile with the patch target: (I didn't want to put all the script into the Makefile, since the rules about escaping in Makefiles, well, escape me ;)

<pre>
#!/bin/bash

KDIR=/lib/modules/$(uname -r)/build
FDIR=drivers/firmware
OPWD=`pwd`

TMPDIR=`mktemp -d`
cd $TMPDIR

mkdir -p a/$FDIR
cp $KDIR/$FDIR/{Kconfig,Makefile} a/$FDIR
cp -r a b
sed -i -e '/endmenu/i\
config IBM_SMAPI\
tristate "IBM ThinkPad SMAPI Support"\
depends on X86\
---help---\
This adds SMAPI support on IBM ThinkPads, mostly used for battery\
charge control. For more information about this driver see\
<http://www.thinkwiki.org/wiki/SMAPI_support_for_Linux> .\
\
If you have an IBM ThinkPad laptop, say Y or M here.\
' b/$FDIR/Kconfig
sed -i -e '$a\
obj-$(CONFIG_IBM_SMAPI) += tp_smapi.o' b/$FDIR/Makefile
cp $OPWD/tp_smapi.c b/$FDIR
diff -Nurp a b > $OPWD/tp_smapi-`uname -r`.patch
rm -r a b
cd $OPWD
</pre>

BTW, [http://qbnz.com/highlighter/ GeSHi]-based syntax-highlighting would be great...

--[[User:Spiney|spiney]] 19:28, 16 Dec 2005 (CET)
----

System T40p:

<pre>
fairlight:/sys/devices/platform/smapi/BAT0# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge1
fairlight:/sys/devices/platform/smapi/BAT0# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge2
fairlight:/sys/devices/platform/smapi/BAT0# dmesg
tp_smapi: req_in: BX=2118 CX=100 DI=0 SI=0
tp_smapi: req_out: AX=8680 BX=2118 CX=100 DX=b2 DI=0 SI=0 ret=-38
tp_smapi: SMAPI error: Function is not supported by SMAPI BIOS (func=2118)
tp_smapi: cannot get force_discharge1 of battery 0: Function is not supported by SMAPI BIOS
tp_smapi: req_in: BX=2104 CX=100 DI=0 SI=0
tp_smapi: req_out: AX=80 BX=2103 CX=100 DX=78 DI=0 SI=0 ret=0
tp_smapi: cannot get force_discharge2 of battery 0: bx=2103
</pre>

So it seems force_discharge1 is not supported at all. But force_discharge2? By the way, i think wiki is a _very_ good idea for collecting information, but not for discussion. I would prefer a maillinglist. We can use sourceforge.

--[[User|StefanSchmidt]]

Talk:SMAPI support for Linux

2005-12-16T17:36:40Z

Spiney: /* Kernel Patch? */ autologin silliness reverted

Great, great work! Really! This completely rocks. I just stopped my battery from charging at 77% and restarted charging a bit later, no problems whatsoever. BTW, this is on kernel 2.6.14.3.

--[[User:Spiney|spiney]] 21:25, 5 Dec 2005 (CET)
----
None of the fuctions is working on my T40, kernel 2.6.14-mm2.

--[[User:Lammic|lammic]], 2005.12.05

Works for me on a T41 running 2.6.12-10-686 (Ubuntu 5.10).

--[[User:berndtnm|berndtnm]], 2005.12.06

Including stop_charge_thresh? That one seems to be missing on the T42p.

--[[User:Thinker|Thinker]] 00:46, 7 Dec 2005 (CET)
----

tp_smapi works just fine on an R52 with Ubuntu Breezy stock kernel.

--[[User:Micampe|Micampe]] 12:52, 7 Dec 2005 (CET)

----

''To set the thresholds for starting and stopping battery charging (in percent of current capacity):''

'''current''' really? That'd be weird, I'd expect it to be percent of '''total''' capacity.

--[[User:Micampe|Micampe]] 14:39, 7 Dec 2005 (CET)

"Current full charge capacity", as opposed to "current remaining capacity" or "designed full charge capacity"...

--[[User:Thinker|Thinker]] 15:05, 7 Dec 2005 (CET)
----

Battery features don't work with my T41p. I can't check this with windows. Can anybody try these features?

-- Nils, 7 Dec 2005
----

Nils, does cdrom_speed work for you on the T41p? Could you provide the details requested in the README (dmesg etc.)?

--[[User:Thinker|Thinker]] 21:57, 7 Dec 2005 (CET)
----

CDRom Speed seems to work. (I see no warnings, but I have to do a speed test.) Now, I've send all outputs to the email-address in the readme.

-- Nils, 8 Dec 2005
----

All the features except the stop_charge_thresh seem to work here on a t42p.
One note, the start_charge_thresh seems to really be stop_charge_thresh. Ie, If I set that to lower than my current battery %, it will never charge,
and if I set it to 100 the battery charges all the way.

--[[User:Nirik|Nirik]] 16 Dec 2005
----

Nirik, "all the features" as of which version? For example, do the force_discharge{1,2} in tp_smapi 0.12 also work for you? See the table in the article page. About start_charge, that's odd. Can you send me a log of what you did, what was the result a what was the dmesg output for each operation?

--[[User:Thinker|Thinker]] 14:16, 16 Dec 2005 (CET)
----

==Changing the CD speed when the CD is being accessed will hang your computer==

I don't have this problem on my T40p. CDROM is mounted and file on CD is opened. Change speed do '''not''' hang my system.

-- Stefan Schmidt
----

An open file looks fine if you're not reading/writing at that point. But my T43 does hangs on this:
# dd if=/dev/scd0 of=/dev/null &
# echo 1 > /sys/devices/platform/smapi/cdrom_speed

--[[User:Thinker|Thinker]] 16:41, 7 Dec 2005 (CET)
----

OK, sorry. I was to fast. My system hangs on this commands, too. :(

-- Stefan Schmidt

Works well. Great.

T42 2373-8zh. Working :cdrom_speed and start_charge_thresh. Untest : inhibit_charge_minutes.

-- Haifeng Chen

cdrom_speed works on my T40.

-- [[User:Lammic|lammic]], 2005.12.09

== "thinkpad" module kernel compatibility ==

Ajunge, how do you compile the "thinkpad" module compile on kernel >=2.6.9? The latest thinkpad version (5.8) still uses "get_cpu_ptr" and "set_cpu_ptr", which were removed in 2.6.9.

--[[User:Thinker|Thinker]] 13:53, 10 Dec 2005 (CET)
----

== Kernel Patch? ==

Hello Thinker,

would it be possible to provide the SMAPI support as kernel patch as well? Something along the lines of: (0.12 against 2.6.15-rc5)

<pre>
diff -Nrp drivers/acpi.orig/Kconfig drivers/acpi/Kconfig
*** drivers/acpi.orig/Kconfig Thu Dec 15 19:58:21 2005
--- drivers/acpi/Kconfig Fri Dec 16 10:30:51 2005
*************** config ACPI_IBM
*** 206,211 ****
--- 206,221 ----

If you have an IBM ThinkPad laptop, say Y or M here.

+ config ACPI_IBM_SMAPI
+ tristate "IBM ThinkPad SMAPI Support"
+ depends on X86
+ ---help---
+ This adds SMAPI support on IBM ThinkPads, mostly used for battery
+ charge control. For more information about this driver see
+ <http://www.thinkwiki.org/wiki/SMAPI_support_for_Linux> .
+
+ If you have an IBM ThinkPad laptop, say Y or M here.
+
config ACPI_TOSHIBA
tristate "Toshiba Laptop Extras"
depends on X86
diff -Nrp drivers/acpi.orig/Makefile drivers/acpi/Makefile
*** drivers/acpi.orig/Makefile Thu Dec 15 19:58:21 2005
--- drivers/acpi/Makefile Fri Dec 16 10:27:36 2005
*************** obj-$(CONFIG_ACPI_DEBUG) += debug.o
*** 54,59 ****
--- 54,60 ----
obj-$(CONFIG_ACPI_NUMA) += numa.o
obj-$(CONFIG_ACPI_ASUS) += asus_acpi.o
obj-$(CONFIG_ACPI_IBM) += ibm_acpi.o
+ obj-$(CONFIG_ACPI_IBM_SMAPI) += tp_smapi.o
obj-$(CONFIG_ACPI_TOSHIBA) += toshiba_acpi.o
obj-y += scan.o motherboard.o
obj-$(CONFIG_ACPI_HOTPLUG_MEMORY) += acpi_memhotplug.o
diff -Nrp drivers/acpi.orig/tp_smapi.c drivers/acpi/tp_smapi.c
*** drivers/acpi.orig/tp_smapi.c Thu Jan 1 01:00:00 1970
--- drivers/acpi/tp_smapi.c Fri Dec 16 10:27:10 2005
***************
*** 0 ****
--- 1,1318 ----
</pre>

Deleted the tp_smapi.c file at the end, out of obvious reasons, and I'm not sure about the placement in the ACPI section, OTOH there it would be found easily next to ibm_acpi.

Providing a patch would help when recompiling the kernel often, I hate recompiling external modules every time (even got me a kernel-upgrade script to do most of it automatically). But of course it's up to you. :)

--[[User:Spiney|spiney]] 09:52, 16 Dec 2005 (CET)
----

I'll be glad to add this, but I don't want to go through additional manual steps in the release process (there are already quite a few). Can you add a "make patch" functionality to the Makefile, or something of the sort, to automatically generate a full patch (including tp_smapi.c) against current kernel sources?

Also, this shouldn't be under drivers/acpi, since it doesn't use ACPI at all (that's why I didn't make it a patch to ibm_acpi). I think the right place is drivers/firmware, like the dell_rbu driver for Dell laptops.

BTW, the convention for kernel patches is to start them once level higher:
diff -Nurp kernel-2.6.14-vanilla kernel-2.6.14-patched

--[[User:Thinker|Thinker]] 17:12, 16 Dec 2005 (CET)
----

Of course it's from the wrong level, as usual I was just lazy/inattentive. And at one point I'll remember who likes what patch format, promise. ;)

A patch target as in "create a new file holding a correct diff to current kernel source" would be rather difficult, since line numbers might change etc., but applying the patch should be straighforward with a bit of sed. Of course I could just do that, create a patch with the diff command and then apply the new patch file in reverse. ;)

--[[User:Spiney|spiney]] 18:36, 16 Dec 2005 (CET)
----

SMAPI support for Linux

2005-12-16T13:58:32Z

Spiney: /* Model-specific status */

ThinkPad laptops include a proprietary interface called SMAPI BIOS (System Management Application Program Interface) which provides some
hardware control functionality that is not exposed by any other interface (e.g., ACPI).

The SMAPI interfaces changes a lot between models, and is poorly documented, so Linux support is not exhaustive for most models. There are currently two SMAPI access mechanisms available: <tt>thinkpad</tt> and <tt>tpctl</tt> for older ThinkPads, and <tt>tp_smapi</tt> for newer ones.

{{WARN|These drivers use undocumented features and direct hardware access. They thus cannot be guaranteed to work, and may cause arbitrary damage
(especially on models they weren't tested on).}}

==Using the <tt>tp_smapi</tt> module==

The <tt>tp_smapi</tt> kernel module exposes some features of the SMAPI BIOS found on recent ThinkPads via a sysfs interface. Currently, the implemented functionality is control of battery charging (this is useful for [[Maintenance#Battery_Treatment|increasing battery lifetime]] or for using a leftover under-spec power supply that can't handle the combined power draw of running and charging), and control of CD/DVD speed.

* Project page: http://tpctl.sourceforge.net/
* You need to donwnload only the [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=171579 tp_smapi kernel module].

====Installation====

To compile and load the module:

# tar xzvf tp_smapi-0.12.tgz
# cd tp_smapi-0.12
# make load

To install permanently (optional):

# make install
# modprobe tp_smapi

====Battery charge control features====

To set the thresholds for starting and stopping battery charging (in percent of current full charge capacity):

# echo 40 > /sys/devices/platform/smapi/BAT0/start_charge_thresh
# echo 70 > /sys/devices/platform/smapi/BAT0/stop_charge_thresh
# cat /sys/devices/platform/smapi/BAT0/*_charge_thresh
40
70

To unconditionally inhibit charging for 17 minutes:

# echo 17 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes

To cancel charge inhibiting:

# echo 0 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes

To force battery discharging even if connected to AC, use one of these:

# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge1
# echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge2

(Probably only one of these will work on your laptop; please check the dmesg output to see which one, and update the status below.)

To cancel forced disharge, use one of these:

# echo 0 > /sys/devices/platform/smapi/BAT0/force_discharge1
# echo 0 > /sys/devices/platform/smapi/BAT0/force_discharge2

====Battery status features====

To view exteded battery status (see below about conflict with <tt>hdaps</tt>):

<pre>
# cat /sys/devices/platform/smapi/BAT0/installed
# cat /sys/devices/platform/smapi/BAT0/state # idle/charging/discharging
# cat /sys/devices/platform/smapi/BAT0/cycle_count
# cat /sys/devices/platform/smapi/BAT0/current_now # instantaneous current
# cat /sys/devices/platform/smapi/BAT0/current_avg # last minute average
# cat /sys/devices/platform/smapi/BAT0/power_now # instantaneous power
# cat /sys/devices/platform/smapi/BAT0/power_avg # last minute average
# cat /sys/devices/platform/smapi/BAT0/last_full_capacity
# cat /sys/devices/platform/smapi/BAT0/remaining_capacity
# cat /sys/devices/platform/smapi/BAT0/design_capacity
# cat /sys/devices/platform/smapi/BAT0/voltage
# cat /sys/devices/platform/smapi/BAT0/design_voltage
# cat /sys/devices/platform/smapi/BAT0/manufacturer
# cat /sys/devices/platform/smapi/BAT0/model
# cat /sys/devices/platform/smapi/BAT0/serial
# cat /sys/devices/platform/smapi/BAT0/barcoding
# cat /sys/devices/platform/smapi/BAT0/chemistry
# cat /sys/devices/platform/smapi/ac_connected
</pre>

The raw status data, including some fields not in the above (in case
you can figure them out):

# cat /sys/devices/platform/smapi/BAT0/dump

In all of the above, replace <tt>BAT0</tt> with <tt>BAT1</tt> to address the 2nd battery.

====Optical drive control features====

To control the speed of the optical drive:
# echo 0 yes_crash_my_computer > /sys/devices/platform/smapi/cd_speed # slow
# echo 1 yes_crash_my_computer > /sys/devices/platform/smapi/cd_speed # medium
# echo 2 yes_crash_my_computer > /sys/devices/platform/smapi/cd_speed # fast
# cat /sys/devices/platform/smapi/cd_speed
2
{{WARN|Changing the CD speed simultaneously with a read or write to the CD will '''hang your computer'''. This feature is thus disabled by default, but can be enabled using <tt>#define PROVIDE_CD_SPEED</tt>. The safe way to set the drive speed is using <tt>hdparm -E num</tt> or <tt>eject -x num</tt> for CD-ROM, and [http://safari.iki.fi/speedcontrol.c speedcontrol -x num] for DVD.}}

====Other features====

Other things that can be controlled through SMAPI, but are not supported in this version of the driver, include forcing battery discharge, PCI bus power saving, CPU power saving control and fan control. See the included README file for more information.

====Conflict with <tt>hdaps</tt>====

The extended battery status function conflicts with the [[HDAPS|hdaps]] kernel module (they use the same IO ports). If you load <tt>hdaps</tt> first, <tt>tp_smapi</tt> will disable its battery status functions (and log a message in the kernel log). If you load <tt>tp_smapi</tt> first, <tt>hdaps</tt> will refuse to load. Use <tt>rmmod</tt> to switch between the two.

Some of the battery status is also visible through ACPI ({{path|/proc/acpi/battery/*}}).

The charging control files (<tt>*_charge_thresh</tt> and <tt>inhibit_charge_minutes</tt>) don't have this problem.

====Model-specific status====

{| border="1" cellpadding="2"
|+<tt>tp_smapi</tt> feature support matrix
|-
! ×
! <tt>start_charge_ thresh</tt>
! <tt>stop_charge_ thresh</tt>
! <tt>inhbit_charge_ minutes</tt>
! <tt>cd_speed</tt>
! <tt>force_ discharge1</tt>
! <tt>force_ discharge2</tt>
! battery status files (see notice about <tt>hdaps</tt> above)
|-
! {{G41}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}}
|-
! {{R40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}}
|-
! {{R50p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}}
|-
! {{R51}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}}
|-
! {{R52}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}}
|-
! {{T40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}}
|-
! {{T40p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}}
|-
! {{T41}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}}
|-
! {{T41p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}}
|-
! {{T42}}
| {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}}
|-
! {{T42p}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}}
|-
! {{T43}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno}} || {{Cyes}}
|-
! {{T43p}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cno}} || {{Cyes}}
|-
! {{X24}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cyes}}
|-
! {{X31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cyes}}
|-
! {{X32}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}}
|-
! {{X40}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cyes}}
|-
! {{X41}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}}
|}

Please update the above and report your experience on the [[Talk:SMAPI support for Linux|discussion]] page. If the module loads but gives a "<tt>not supported</tt>" or "<tt>not implementeded</tt>" when you try to use some specific file in {{path|/sys/devices/platform/smapi/}}, please report the <tt>dmesg</tt> output and whether the corresponding functionality is available under Windows - maybe your ThinkPad just can't do that.

==Using the <tt>thinkpad</tt> module==

This solution consists of a module, called <tt>thinkpad</tt>, and a user-space tool caled <tt>tpctl</tt>. It provides very rich functionality for older ThinkPads, but on newer ThinkPads much of this functionality is exposed and supported through an ACPI interface and the SMAPI access does not work anymore. Kernel 2.6.9 and newer is unsupported; for kernel 2.6.3 and newer you need <tt>tpctl</tt> >=4.14 and <tt>thinkpad </tt> >=5.5. For details, see the [http://tpctl.sourceforge.net/README README] and [http://tpctl.sourceforge.net/SUPPORTED-MODELS list of supported models].

* Project page: http://tpctl.sourceforge.net/
* You need to download the [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=29354t thinkpad module] and [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=1204 tpctl userspace tool].
* There is also an optional GUI: [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=99929 configure-thinkpad].

[[Category:Tools]] [[Category:Patches]]