ThinkWiki - User contributions [en]

Talk:Problems with SATA and Linux

2006-10-10T12:15:55Z

Tobixen: /* Patch against SATA-resume problem with T60 */

__TOC__

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)
----

Is it possible to enable AHCI on the Z60m? There doesn't seem to be an option for it in the BIOS, even after updating to the latest BIOS version (1.19). I don't think it's enabled by default since the "ata_piix" driver finds my controller and the "ahci" driver doesn't.

--[[User:Wyzard|Wyzard]] 06:06, 12 August 2006 (CEST)
----

Ok, I got it working with compatibility instead of AHCI (X60s) but I would like to know whats the difference between those two? Anybody with a quick explanation?

@Wyzard: AFAIK you have to switch it within BIOS and if you can't then you can't use ata_piix.

--[[User:elm|elm]] 16:46, 12 August 2006 (CEST)

== 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)
----

Where the hell do I find the libata module?

--[[User:squashball|squashball]] 09:09, 11 June 2006 (CET)

The relevant driver is called ata_piix. The ata_piix driver uses a chunk of shared kernel code called libata.

--[[User:Thinker|Thinker]] 09:33, 11 June 2006 (CEST)

Ok, Thanks. Nevertheless I am not able to get my drive working. It's a T60...

--[[User:squashball|squashball]] 12:29, 12 June 2006 (CET)

Your T60 uses AHCI by default. You have to change the BIOS settings to "compatibility mode" to use the HDD and DVD drive with ata_piix. Then, you're also able to hotswap your ultrabay. But for this, a patch for ibm_acpi is needed.

--[[User:Whoopie|Whoopie]] 14:57, 12 June 2006 (CEST)

Yeah, thanks, it's working now! Where was I supposed to find this info?
EDIT: But DMA is still off and can't be enabled.

--[[User:squashball|squashball]] 07:58, 13 June 2006 (CET)

DMA is enabled by default with libata. Do a "dmesg |grep DMA" and you'll see. You can't use hdparm to see the settings for your hdd. BTW, if you have more questions, you could join IRC ##ibmthinkpad.

--[[User:Whoopie|Whoopie]] 11:04, 13 June 2006 (CEST)
----

== occasional hang upon resume with various kernels ==

I keep having trouble with resume after suspend to ram. Occasionally, it takes longer to wake up and then is in a semi-hanged
state, i.e. nothing having to do with actual reading from the disk works. (what was running, as aterm
is still running, ls works, when the listing is buffered, but hangs if it is not).
Kernel is 2.6.15 with sata-pm patch. Later 2.6.15 kernels hang always and it's the same with 2.6.16.
Could perhaps somebody, for whom it works without problems post his .config somewhere?
I'm out of ideas.

--[[User:Rasto|Rasto]] 14:46, 20 March 2006 (CET)

I have the same problem with my x41 and 2.6.16 or 2.6.16-r1 running on Gentoo. Sometimes resume is ok and sometimes the disk doesn't resume. I can't see any log because the disk is unwritable after resume. The logs on F12 is full of io error.
I tested many different kernel configs, unloading modules before suspend, stopping services...
Like Rasto, I'm out of ideas...

--[[User:Pplr|Pplr]] 19:21, 8 April 2006 (CEST)

You could try http://rtr.ca/dell_i9300/kernel/kernel-2.6.16/02_libata_resume_fix.patch
This patch worked for me.

--[[User:Whoopie|Whoopie]] 21:21, 8 April 2006 (CEST)

Hello, according to the first lines of the article, resume does not work prior to kernel 2.6.16, i.e. the computer hangs up just a second after it comes back. I just switched from 2.6.15 to 2.6.16 but the problem still remains. I have a Z60M thinkpad. So this has obviously the same problem as the T60.

-- [[User:Bjoern.thalheim|BjÃ¶rn]] 14:37, 10 April 2006 (CEST)

Increasing the timeouts seems to do the trick. I applied it about two weeks ago, and it works since.

-- [[User:Rasto|Rasto]] 09:59, 11 April 2006 (CEST)

Ubuntu Dapper with 2.6.15-23 is also exhibiting this problem even though the sata_pm patch is applied. Bjorn, which timeout are you referring to?

-- [[User:nmuntz|nmuntz]] 09:08, 13 June 2006 (MDT)

== Suspend to RAM on X41 not working with Debian-packaged 2.6.16 ==

I just tried the Debian package of the Linux 2.6.16 kernel on my [[X41]] to see if suspend-to-RAM would work. Unfortunately, it didn't. The laptop suspends just fine, but when it's turned back on, the backlight remains off, there is a lot of disk activity for a while, and then the computer just shuts off. When turned on again, it boots normally. Suspend-to-disk works fine, just like before.

On a different note, CPU throttling broke on my system with the new kernel. I can no longer modprobe acpi-cpufreq. [[User:Ehn|Ehn]] 04:28, 22 March 2006 (CET)

:The latter issue was solved by using speedstep-centrino instead of acpi-cpufreq. [[User:Ehn|Ehn]] 23:25, 9 April 2006 (CEST)
----

Neither problem is related to this article, so it's unlikely to be answered here.

--[[User:Thinker|Thinker]] 17:37, 22 March 2006 (CET)
----

Hm. It seems to be a problem with sata power management for me, so I guess this could be one of the places.

[[User:Rasto|Rasto]] 17:45, 22 March 2006 (CET)
---

Ehn, by "disk activity" do you mean a constantly on HDD LED and no disk movement noises, or ''real'' disk activity with the LED flashing and disk noise? The former is likely to be the SATA problem, the latter rules out the SATA problem.

--[[User:Thinker|Thinker]] 18:44, 22 March 2006 (CET)

:The latter. There is real disk activity, indicated by LED flashing <em>and</em> disk movement noise, for about 30 seconds, before the machine gives up and shuts down. If this is not SATA-related, what might it be? [[User:Ehn|Ehn]] 23:23, 9 April 2006 (CEST)

----

Sorry, I didn't realize Ehn has two problems, and I considered your post as aimed at my and Ehn's. Never mind then.

[[User:Rasto|Rasto]] 10:47, 23 March 2006 (CET)

== Problem with 2.6.16 ==

ok, seems like we have a new problem:
After upgrading from 2.6.15 to 2.6.16 my DVD device is not recognised anymore by libsata.
The only way to get working is by using the ide layer - without DMA of course.
Can anyone confirm this?

--[[User:Defiant|Erik]] 17:49, 23 Mar 2006 (CET)
--------

Try the kernel parameter '''combined_mode=libata''', does this help? Also, have you enabled libata's ATAPI support as described in the article?

--[[User:Thinker|Thinker]] 20:31, 23 March 2006 (CET)
----

Yes, I'm using the command line parameter libata.atapi_enable=1 - up to 2.6.15 it works fine.
About the combined_mode parameter: Also tried it, though the Author of this patch mentioned that the default behavior did not changed.
I will continue hungting this problem when I find some time.

--[[User:Defiant|Erik]] 7:12, 24 Mar 2006 (CET)
-----

I can confirm Eriks problem. After updating to 2.6.16 I have it, too. libata.atapi_enable=1 is still on kernel command line. With some help of Michael Ott I figured out that this only happens if you have the current suspend2 patches applied.
Using a vanilla 2.6.16 works as expected.

--[[User:Mobst|mobst]] 14:30, 24 Mar 2006 (CET)
-----

Ahh thanks. Finding the problem in the suspend2 patch should be an easy task.
I just hope for some free time this weekend!

--[[User:Defiant|Erik]] 18:31, 24 Mar 2006 (CET)
-----

Uhm, looks like [[ZolnOtt|ZolnOtt]] was faster, he added the note to
http://thinkwiki.org/wiki/Problems_with_SATA_and_Linux#No_DMA_on_DVD_drive

--[[User:Defiant|Erik]] 20:02, 24 Mar 2006 (CET)

== Patch against SATA-resume problem with T60 ==

I only have a Fujitsu-Siemens C1320, but I had the same problem with resuming from suspend with a SATA disk and kernel 2.6.16 as mentioned for the T60. I solved the problem for me by merging several patches (patches.fixes/libata-increase-timeout-for-resume, patches.fixes/ahci-suspend, patches.fixes/ahci-atapi-sense-request, patches.drivers/libata-acpi-suspend, patches.fixes/libata-resume-drive_port-mode, patches.fixes/ahci-init-on-resume, patches.drivers/libata-device-spindown)
from the OpenSuSE kernel 2.6.16-12 to vanilla 2.6.16.5. You'll find my patch at http://www.spinnaker.de/linux/c1320/sata-resume-2.6.16.5.patch. I expect this to solve the T60 problem, so I provide the patch here, as this wiki helped me so much with my laptop.

--[[User:Rrosenfeld|Rrosenfeld]] 23:12, 16 April 2006 (CEST)

I just want to let you know that I managed to get Suspend-to-RAM working on the T60. I'm using Gentoo's suspend2-sources-2.6.16-r2 as base and applied the above patches from Rrosenfeld (thanks!) and additionally this [https://bugzilla.novell.com/attachment.cgi?id=75844&action=view one] (here the corresponding [https://bugzilla.novell.com/show_bug.cgi?id=162090 bug]).

--[[User:Sts|sts]] 22:52, 17 April 2006 (CEST)

same here. applied both patches to gentoo suspend-sources-2.6.16-r5 --- working. sweet.

--[[User:Husemann|dr who]] 21:51, 3 May 2006 (CEST)

however: powersave (powersaved) is a spoiler: it will cause the resume operation to get stuck at "reading back caches" and eventually result in a kernel panic. stopping powersaved before hibernating does not prevent it: it seems that running powersaved just once will screw things up. interesting and nasty. but not a show stopper (IMHO).

--[[User:Husemann|dr who]] 17:14, 10 May 2006 (CEST)

that's not powersaved's fault. kernel panics are always kernel (or hardware) bugs. i experienced this kind of lockups when using different cpufreq governors at once (that's probaly something one shoudln't do?). i'm now using only cpufreq_userspace and don't have any problems.

--[[User:Sts|sts]] 15:11, 11 May 2006 (CEST)

Having exactly the same SATA wakeup problem on my Z60t, using FC5. Can the patch from rosenfeld be applied also to the FC5 kernelsource?

--[[User:SzentivÃ¡nyi|szenti]] 21:29, 11 May 2006 (CEST)

Latest fedora (FC5) 2.6.17-1.2139_FC5smp kernel solved the problem on my T60p. I have successfully resumed a number of times now.

--[[User:Gfbarros|Guil]] 20:38, 27 June 2006 (CEST)

Vanilla 2.6.17.8 lets me suspend and resume on a T60p. But I had to set the SATA mode to Compatibility (ata-piix) in the BIOS. The other catch is that if you suspend from a console rather than X, you get a black screen. Fn-F7 back to X gets your display back. Of course, if you don't have X up, you're kind of stuck and the safest thing to do is to tell the machine to reboot. The keyboard still works, so you have to type blind.

--jlquinn 17 Aug 2006 (signature button didn't work properly)

jlquinn: see [[How to recover from corrupted textmode]].

--[[User:Thinker|Thinker]] 17:20, 17 August 2006 (CEST)

By giving the kernel the option acpi_sleep=s3_bios I've managed to get suspend to work from the console mode - though I still have the SATA-problem. I'm running the gentoo kernel 2.6.17-r8, and will now try the tips from jlquinn...

--[[User:Tobixen|Tobixen]] 14:15, 10 October 2006 (CEST)
----

== removal of cd/dvd problems rambling? ==

Should we remove the ramblings that are now the last section of the page? That's just generic information on how to properly use cdrecord (and it is incomplete and incorrect to add insult to injury...). If you use libata with ATAPI enabled and a new kernel, it *just works*, as the drive will look like a 100% SCSI device to cdrecord...

--[[User:Hmh|hmh]] 06:12, 4 October 2006 (CEST)

Agreed.
--[[User:Thinker|Thinker]] 14:01, 4 October 2006 (CEST)

Talk:Problems with SATA and Linux

2006-10-10T12:12:46Z

Tobixen: /* Patch against SATA-resume problem with T60 */

__TOC__

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)
----

Is it possible to enable AHCI on the Z60m? There doesn't seem to be an option for it in the BIOS, even after updating to the latest BIOS version (1.19). I don't think it's enabled by default since the "ata_piix" driver finds my controller and the "ahci" driver doesn't.

--[[User:Wyzard|Wyzard]] 06:06, 12 August 2006 (CEST)
----

Ok, I got it working with compatibility instead of AHCI (X60s) but I would like to know whats the difference between those two? Anybody with a quick explanation?

@Wyzard: AFAIK you have to switch it within BIOS and if you can't then you can't use ata_piix.

--[[User:elm|elm]] 16:46, 12 August 2006 (CEST)

== 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)
----

Where the hell do I find the libata module?

--[[User:squashball|squashball]] 09:09, 11 June 2006 (CET)

The relevant driver is called ata_piix. The ata_piix driver uses a chunk of shared kernel code called libata.

--[[User:Thinker|Thinker]] 09:33, 11 June 2006 (CEST)

Ok, Thanks. Nevertheless I am not able to get my drive working. It's a T60...

--[[User:squashball|squashball]] 12:29, 12 June 2006 (CET)

Your T60 uses AHCI by default. You have to change the BIOS settings to "compatibility mode" to use the HDD and DVD drive with ata_piix. Then, you're also able to hotswap your ultrabay. But for this, a patch for ibm_acpi is needed.

--[[User:Whoopie|Whoopie]] 14:57, 12 June 2006 (CEST)

Yeah, thanks, it's working now! Where was I supposed to find this info?
EDIT: But DMA is still off and can't be enabled.

--[[User:squashball|squashball]] 07:58, 13 June 2006 (CET)

DMA is enabled by default with libata. Do a "dmesg |grep DMA" and you'll see. You can't use hdparm to see the settings for your hdd. BTW, if you have more questions, you could join IRC ##ibmthinkpad.

--[[User:Whoopie|Whoopie]] 11:04, 13 June 2006 (CEST)
----

== occasional hang upon resume with various kernels ==

I keep having trouble with resume after suspend to ram. Occasionally, it takes longer to wake up and then is in a semi-hanged
state, i.e. nothing having to do with actual reading from the disk works. (what was running, as aterm
is still running, ls works, when the listing is buffered, but hangs if it is not).
Kernel is 2.6.15 with sata-pm patch. Later 2.6.15 kernels hang always and it's the same with 2.6.16.
Could perhaps somebody, for whom it works without problems post his .config somewhere?
I'm out of ideas.

--[[User:Rasto|Rasto]] 14:46, 20 March 2006 (CET)

I have the same problem with my x41 and 2.6.16 or 2.6.16-r1 running on Gentoo. Sometimes resume is ok and sometimes the disk doesn't resume. I can't see any log because the disk is unwritable after resume. The logs on F12 is full of io error.
I tested many different kernel configs, unloading modules before suspend, stopping services...
Like Rasto, I'm out of ideas...

--[[User:Pplr|Pplr]] 19:21, 8 April 2006 (CEST)

You could try http://rtr.ca/dell_i9300/kernel/kernel-2.6.16/02_libata_resume_fix.patch
This patch worked for me.

--[[User:Whoopie|Whoopie]] 21:21, 8 April 2006 (CEST)

Hello, according to the first lines of the article, resume does not work prior to kernel 2.6.16, i.e. the computer hangs up just a second after it comes back. I just switched from 2.6.15 to 2.6.16 but the problem still remains. I have a Z60M thinkpad. So this has obviously the same problem as the T60.

-- [[User:Bjoern.thalheim|BjÃ¶rn]] 14:37, 10 April 2006 (CEST)

Increasing the timeouts seems to do the trick. I applied it about two weeks ago, and it works since.

-- [[User:Rasto|Rasto]] 09:59, 11 April 2006 (CEST)

Ubuntu Dapper with 2.6.15-23 is also exhibiting this problem even though the sata_pm patch is applied. Bjorn, which timeout are you referring to?

-- [[User:nmuntz|nmuntz]] 09:08, 13 June 2006 (MDT)

== Suspend to RAM on X41 not working with Debian-packaged 2.6.16 ==

I just tried the Debian package of the Linux 2.6.16 kernel on my [[X41]] to see if suspend-to-RAM would work. Unfortunately, it didn't. The laptop suspends just fine, but when it's turned back on, the backlight remains off, there is a lot of disk activity for a while, and then the computer just shuts off. When turned on again, it boots normally. Suspend-to-disk works fine, just like before.

On a different note, CPU throttling broke on my system with the new kernel. I can no longer modprobe acpi-cpufreq. [[User:Ehn|Ehn]] 04:28, 22 March 2006 (CET)

:The latter issue was solved by using speedstep-centrino instead of acpi-cpufreq. [[User:Ehn|Ehn]] 23:25, 9 April 2006 (CEST)
----

Neither problem is related to this article, so it's unlikely to be answered here.

--[[User:Thinker|Thinker]] 17:37, 22 March 2006 (CET)
----

Hm. It seems to be a problem with sata power management for me, so I guess this could be one of the places.

[[User:Rasto|Rasto]] 17:45, 22 March 2006 (CET)
---

Ehn, by "disk activity" do you mean a constantly on HDD LED and no disk movement noises, or ''real'' disk activity with the LED flashing and disk noise? The former is likely to be the SATA problem, the latter rules out the SATA problem.

--[[User:Thinker|Thinker]] 18:44, 22 March 2006 (CET)

:The latter. There is real disk activity, indicated by LED flashing <em>and</em> disk movement noise, for about 30 seconds, before the machine gives up and shuts down. If this is not SATA-related, what might it be? [[User:Ehn|Ehn]] 23:23, 9 April 2006 (CEST)

----

Sorry, I didn't realize Ehn has two problems, and I considered your post as aimed at my and Ehn's. Never mind then.

[[User:Rasto|Rasto]] 10:47, 23 March 2006 (CET)

== Problem with 2.6.16 ==

ok, seems like we have a new problem:
After upgrading from 2.6.15 to 2.6.16 my DVD device is not recognised anymore by libsata.
The only way to get working is by using the ide layer - without DMA of course.
Can anyone confirm this?

--[[User:Defiant|Erik]] 17:49, 23 Mar 2006 (CET)
--------

Try the kernel parameter '''combined_mode=libata''', does this help? Also, have you enabled libata's ATAPI support as described in the article?

--[[User:Thinker|Thinker]] 20:31, 23 March 2006 (CET)
----

Yes, I'm using the command line parameter libata.atapi_enable=1 - up to 2.6.15 it works fine.
About the combined_mode parameter: Also tried it, though the Author of this patch mentioned that the default behavior did not changed.
I will continue hungting this problem when I find some time.

--[[User:Defiant|Erik]] 7:12, 24 Mar 2006 (CET)
-----

I can confirm Eriks problem. After updating to 2.6.16 I have it, too. libata.atapi_enable=1 is still on kernel command line. With some help of Michael Ott I figured out that this only happens if you have the current suspend2 patches applied.
Using a vanilla 2.6.16 works as expected.

--[[User:Mobst|mobst]] 14:30, 24 Mar 2006 (CET)
-----

Ahh thanks. Finding the problem in the suspend2 patch should be an easy task.
I just hope for some free time this weekend!

--[[User:Defiant|Erik]] 18:31, 24 Mar 2006 (CET)
-----

Uhm, looks like [[ZolnOtt|ZolnOtt]] was faster, he added the note to
http://thinkwiki.org/wiki/Problems_with_SATA_and_Linux#No_DMA_on_DVD_drive

--[[User:Defiant|Erik]] 20:02, 24 Mar 2006 (CET)

== Patch against SATA-resume problem with T60 ==

I only have a Fujitsu-Siemens C1320, but I had the same problem with resuming from suspend with a SATA disk and kernel 2.6.16 as mentioned for the T60. I solved the problem for me by merging several patches (patches.fixes/libata-increase-timeout-for-resume, patches.fixes/ahci-suspend, patches.fixes/ahci-atapi-sense-request, patches.drivers/libata-acpi-suspend, patches.fixes/libata-resume-drive_port-mode, patches.fixes/ahci-init-on-resume, patches.drivers/libata-device-spindown)
from the OpenSuSE kernel 2.6.16-12 to vanilla 2.6.16.5. You'll find my patch at http://www.spinnaker.de/linux/c1320/sata-resume-2.6.16.5.patch. I expect this to solve the T60 problem, so I provide the patch here, as this wiki helped me so much with my laptop.

--[[User:Rrosenfeld|Rrosenfeld]] 23:12, 16 April 2006 (CEST)

I just want to let you know that I managed to get Suspend-to-RAM working on the T60. I'm using Gentoo's suspend2-sources-2.6.16-r2 as base and applied the above patches from Rrosenfeld (thanks!) and additionally this [https://bugzilla.novell.com/attachment.cgi?id=75844&action=view one] (here the corresponding [https://bugzilla.novell.com/show_bug.cgi?id=162090 bug]).

--[[User:Sts|sts]] 22:52, 17 April 2006 (CEST)

same here. applied both patches to gentoo suspend-sources-2.6.16-r5 --- working. sweet.

--[[User:Husemann|dr who]] 21:51, 3 May 2006 (CEST)

however: powersave (powersaved) is a spoiler: it will cause the resume operation to get stuck at "reading back caches" and eventually result in a kernel panic. stopping powersaved before hibernating does not prevent it: it seems that running powersaved just once will screw things up. interesting and nasty. but not a show stopper (IMHO).

--[[User:Husemann|dr who]] 17:14, 10 May 2006 (CEST)

that's not powersaved's fault. kernel panics are always kernel (or hardware) bugs. i experienced this kind of lockups when using different cpufreq governors at once (that's probaly something one shoudln't do?). i'm now using only cpufreq_userspace and don't have any problems.

--[[User:Sts|sts]] 15:11, 11 May 2006 (CEST)

Having exactly the same SATA wakeup problem on my Z60t, using FC5. Can the patch from rosenfeld be applied also to the FC5 kernelsource?

--[[User:SzentivÃ¡nyi|szenti]] 21:29, 11 May 2006 (CEST)

Latest fedora (FC5) 2.6.17-1.2139_FC5smp kernel solved the problem on my T60p. I have successfully resumed a number of times now.

--[[User:Gfbarros|Guil]] 20:38, 27 June 2006 (CEST)

Vanilla 2.6.17.8 lets me suspend and resume on a T60p. But I had to set the SATA mode to Compatibility (ata-piix) in the BIOS. The other catch is that if you suspend from a console rather than X, you get a black screen. Fn-F7 back to X gets your display back. Of course, if you don't have X up, you're kind of stuck and the safest thing to do is to tell the machine to reboot. The keyboard still works, so you have to type blind.

--jlquinn 17 Aug 2006 (signature button didn't work properly)

jlquinn: see [[How to recover from corrupted textmode]].

--[[User:Thinker|Thinker]] 17:20, 17 August 2006 (CEST)
----

By giving the kernel the option acpi_sleep=s3_bios I've managed to get suspend to work from the console mode - though I still have the SATA-problem. I'm running the gentoo kernel 2.6.17-r8, and will now try the tips from jlquinn...

== removal of cd/dvd problems rambling? ==

Should we remove the ramblings that are now the last section of the page? That's just generic information on how to properly use cdrecord (and it is incomplete and incorrect to add insult to injury...). If you use libata with ATAPI enabled and a new kernel, it *just works*, as the drive will look like a 100% SCSI device to cdrecord...

--[[User:Hmh|hmh]] 06:12, 4 October 2006 (CEST)

Agreed.
--[[User:Thinker|Thinker]] 14:01, 4 October 2006 (CEST)

Problem with display remaining black after resume

2006-10-10T05:44:14Z

Tobixen:

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}, {{Z60m}}
*ThinkPad {{X60s}}

==Affected Operating Systems==
*Linux (it's a kernel issue)
*FreeBSD (6.x at least)

==Solutions==
===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===
see [[1400x1050 on Intel 915GM]].
===Solution for ThinkPads with ATI graphic chips (or Intel 915/945GM)===
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this would look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it would look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In [[:Category:OpenSUSE|OpenSUSE]] 10.1 (at least on a T43p), it's necessary to override the default options for s2ram if you're using the newer ATI driver. This can be done putting {{bootparm|SUSPEND2RAM_FORCE|"yes"}} and {{bootparm|SUSPEND2RAM_ACPI_SLEEP|"3"}} in {{path|/etc/powersave/sleep}}.

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves.

In {{Fedora}}, it may be necessary with the Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}} to comment out the VBE post and restore. Also, the laptop, after waking up, may go back to sleep immediately or whenever the AC adapter is disconnected. When this happens, it's caused by a bug in the HAL daemon that incorrectly reports certain ACPI events. This is a known problem and a simple workaround is described [http://live.gnome.org/GnomePowerManager/Faq#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].

{{NOTE|It is possible this method will not work if the laptop is docked. It is also possible that the cited workaround for the HAL daemon bug will not work on some machines. A kludgier workaround in this event is to kill the HAL daemon on suspend. This necessitates the resuscitation of GPM upon resume.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
*For a R50e the only thing needed to make suspend to ram work in Ubuntu 6.06 is adding
Option "VBERestore" "yes"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}, and the example script below.

The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi
===Solution for ThinkPads with ATI graphic (and possibly other) chips and FreeBSD===

The FreeBSD acpi(4) manpage mentions a tunable parameter, "hw.acpi.reset_video":

hw.acpi.reset_video
Reset the video adapter from real mode during the resume path.
Some systems need this help, others have display problems if it
is enabled. Default is 0 (disabled).

This tunable can be set by adding the following line to your FreeBSD machine's /boot/loader.conf file:

hw.acpi.reset_video="1"

And rebooting your machine. Hopefully, the next time you resume from a suspend, you'll see your video again. This solution doesn't appear to be specific to ATI hardware in any way, so I presume it would be helpful for video chipsets other than ATI, as well.

If this entry doesn't help you, you might consider searching in the [http://lists.freebsd.org/pipermail/freebsd-mobile/ FreeBSD-Mobile email-list archive] for more insight.

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

Installation instructions for the ThinkPad T60p

2006-10-06T06:38:09Z

Tobixen: /* Processor type and features */

[[Category:T60p]]
==Installing Ubuntu Dapper==

To get it going:

* Get Dapper i386 (I used the Daily ISO DVD).

* Install the default distribution.

It will work, but you need an SMP kernel, and accelerated and higher resolution graphics, so:

* Install the i686-smp kernel (search for 'linux-kernel' in synaptic).

* Search for fglrx in synaptic, and install the fglrx modules, X driver and ATI control panel.

* Edit /etc/X11/xorg.conf, so each of the "Modeline" entries contains a 1600x1200 resolution as well (or whatever the top resolution of your LCD panel is), and change the driver section as follows:

Section "Device"
Identifier "ATI Technologies, Inc. ATI Default Card"
Driver "fglrx" <----- ADD THIS LINE
#Driver "vesa" <---- COMMENT OUT THIS LINE
BusID "PCI:1:0:0"
ChipID 0x71c5 <----- '''MAYBE''' ADD THIS LINE
EndSection

[On my UXGA t60p the ChipID line was actually fatal to getting fglrx to start up (/var/log/Xorg.0.log showed the driver falling back to VESA and fgl_glxgears would crash). Without that ChipID line my chip was identified as:

Chipset: "MOBILITY FireGL V5200 (M56 71C4)" (Chipset = 0x71c4)

which appears to correspond exactly to my machine's spec, and fgl_glxgears worked fine.]

Reboot, and you should be done. Check "cat /proc/cpuinfo" shows two CPUs, and run fgl_glxgears and check you get around 580 frames a second.

I've reported [https://launchpad.net/distros/ubuntu/+bug/46527 bug 46527] on the lack of screen driver detection, so hopefully this will get even easier.

Note you do NOT need to install ATI drivers from the ATI site. The Ubuntu drivers are sufficient.

Thanks to Rich Tango-Lowy (see below) for the hint re chip detection.

==Kubuntu Dapper Live CD==

If you're trying to install from the Kubuntu Desktop CD, you'll never make it to the login screen because the ATI display driver isn't recognized.

* Ctrl-Alt-F1
* sudo nano /etc/X11/xorg.conf
* change the display driver line that looks like:

Driver "ati"

to

Driver "vesa"

[I think I remember that it was "ati", but I could be wrong. In any
case this is very clearly the only Driver line in the ATI device specification section]

* Save and exit
* sudo /etc/init.d kdm restart

Now you get a login screen.

== Installing Gentoo 2006.0 ==

===Boot from Live CD===
Upon booting off the live cd you will come to the kernel selection prompt.
Enter:
gentoo doscsi
I had some trouble getting the wired NIC to be linked to the driver, often getting an error that the EEPROM failed a check. If this happens, you can try re-inserting the module,
>rmmod e1000; modprobe e1000
or rebooting and trying again. The wireless card isn't supported by the live cd so you're going to have to stick to wired for now.

===/etc/make.conf Settings===
The make.conf settings are the first thing you want to setup correctly before you proceed with the rest of the install process. All future updates will depend upon these settings as well.
CFLAGS="-march=prescott -O2 -pipe -msse3 -fomit-frame-pointer
VIDEO_CARDS="fglrx vesa fbdev"
INPUT_DEVICES="keyboard mouse synaptics"
FEATURES="sandbox ccache distlocks autoaddcvs parallel-fetch"
MAKEOPTS="-j3"
For a more complete discussion of the CFLAGS to use for a Core Duo processor, see [http://forums.gentoo.org/viewtopic-t-448761-highlight-core+duo+prescott.html?sid=97485d7e26a1f77e2bb06fa437a448ff this forum thread]. Some users recommend that the USE variable has the ibm value in it (eg. USE="ibm") but the Gentoo website says this is only for Power PC64 systems; I don't think we should use it. If anyone can shed more light on this, please update this section.

===Kernel Settings===
I was able to get the laptop running from i686 gentoo sources and recommend this to anyone installing Gentoo on their T60p. Alot of graphics support is left out of the kernel since the best graphics performance is with ATI's propietary drivers which you can emerge at the end of the kernel compile.
====Processor type and features====
* Turn on Symmetric multi-processing support.
* Set processor family to Pentium M.
* Turn off toshiba and dell laptop support.
* Set timer frequency to 1000 Hz since this is a desktop system.
* Found on a [http://forum.thinkpads.com/viewtopic.php?t=19031 forum posting] that "Hotpluggable CPU" should be set to get acpi sleep to work. Go figure...

====Power management options====
* Turn on all ACPI settings (especially IBM Thinkpad Extras) except ASUS/Medion and Toshiba Laptop Extras.
* Turn on CPU Frequency scaling.
** Turn on powersave, userspace, ondemand and conservative governor.
** Turn off ACPI Processor P-States driver.
** Turn off all AMD and Cyrix options.
** Turn on Intel Enhanced SpeedStep and Intel Speedstep on ICH-M chipsets (ioport interface).
** Turn off Intel SpeedStep on 440BX/ZX/MX chipsets (SMI interface).
** Turn off Intel Pentium 4 clock modulation, nVidia nForce2 FSB changing and Transmeta LongRun.
====Bus options====
* Turn on PCI Express support.
* Turn on Message Signaled Interupts.
* Turn on PCCard support and CardBus yenta-compatible bridge support.
====Networking support====
* Turn off Generic IEEE 802.11 Networking Stack.
* Turn on IrDA (infrared) subsystem support and sub-options.
* Turn on Bluetooth subsystem support and sub-options.
* Turn off Amateur Radio support (unless you work with actual radios.)
====Device Drivers====
* Turn off Memory Technology Devices.
* Turn off parallel port support.
* Turn on SCSI device support. In "low-level device drivers", chose the Serial ATA (SATA) support. Build it as a part of the kernel, and not as a kernel module.
* Turn off Fusion MPT device support.
* Turn on IEEE 1394 (FireWire) support.
* Turn on Network device support.
** Turn off all options in all categories under Network device support except the stated ones below.
** Turn on Intel(R) PRO/1000 Gigabit Ethernet support under Ethernet (1000 Mbit).
** Turn on Wireless LAN drivers (non-hamradio) & Wireless Extensions and none of the sub-options underneath.
** Most people do not need Fibre channel, ATM, WAN or PPP/SLIP support (if you do then turn it on. PPP is needed for GPRS/UMTS connectivity)
* Character device options...
** Turn off Parallel printer support.
** Turn on Intel/AMD/VIA HW Random Number Generator support.
** Turn on /dev/nvram support.
** Turn off /dev/agpgart (AGP Support).
** Turn off Direct Rendering Manager.
** Support for the [[Embedded_Security_Subsystem|Fritz Chip]] is located in "TPM Devices".
* Turn off all Graphics support options except the stated ones below,
** Turn on VESA VGA graphics support and set VESA driver type to vesafb.
** Turn on Enable firmware EDID and Enable Video Mode Handling Helpers.
** Turn on Support for the framebuffer splash.
* '''IMPORTANT:''' Turn off all Wireless device support under USB support -> USB Network Adapters or you will tear your hair out trying to get wireless.
* Turn on Sound card support.
** Turn on Advanced Linux Sound Architecture.
** Turn off all ISA, PCI, USB, generic and PCMCIA device options the stated on below.
** Turn on Intel HD Audio under PCI devices.
* Turn off all MMC/SD Card support options.
* Turn off LED devices.
* Cryptographic options... (needed for the wireless card ipw9345)
** Turn on AES chiphers
** Turn on Michael MIC keyed digest algorithm

That should do it. (I know, that's it.)
That should make sure that you have all the drivers necessary to boot the system and be able to use all your hardware (almost).

===Portage Ebuilds===

Always make sure you run this command before going any further so you can get the latest portage build and version...
emerge --sync && emerge portage

Since September 24 2006 I was able to make the latest ati-drivers work on the T60p without adding any lines to the unmask file (/etc/portage/package.unmask) under the gentoo-sources kernel. You should be able to run...
emerge ati-drivers
...without any problems.

Don't forget to emerge all the Thinkpad software as well...
emerge tpb tp_smapii tpctl

Then you can start to setup the wireless in this order at the command line...
/bin/sh /usr/portage/net-wireless/ieee80211/files/remove-old /usr/src/linux
emerge ieee80211 ipw3945 ipw3945d wireless-tools
/sbin/ipw3945d
ifconfig eth1 up

===xorg.conf Settings===

A piece of code is worth a thousand words; here is my xorg.conf that works at 3000-5000 FPS so far. I am still trying to find better parameters, but this is the best I got it to run so far. I intentionally left out the InputDevice section since I disabled my Synaptics pad (I like the center joystick better.) Just modify your xorg.conf sections with what is shown below.

Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
Load "dri"
Load "glx"
EndSection

Section "Device"
Identifier "VideoCard"
Driver "fglrx"
VendorName "ati"
BusID "PCI:1:0:0"
Option "VideoOverlay" "off"
EndSection

Section "dri"
Group "video"
Mode 0666
EndSection

Section "Extensions"
Option "XVideo" "Enable"
EndSection

Section "Screen"
Identifier "Screen"
Device "VideoCard"
Monitor "Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Make sure you assign your username to the video group in the /etc/group file or you will net get DRI (Direct Rendering) support. When debugging your running X windows system, always check /var/log/Xorg.0.log for any errors or hints at what may be configured incorrectly. This is how I was able to get so far with the graphics.

==External Sources==
*[http://arscognita.com/~richtl/T60p/index.html Rich Tango-Lowy's Mandriva 2007 Cooker on T60p page]
*[http://buzzy.tesuji.org/thinkpad_t60p.html Jon Lin's Gentoo Thinkpad T60p]

Installation instructions for the ThinkPad T60p

2006-10-03T07:05:08Z

Tobixen: /* Device Drivers */ - found that the AES chiphers was also required by the wifi card

[[Category:T60p]]
==Installing Ubuntu Dapper==

To get it going:

* Get Dapper i386 (I used the Daily ISO DVD).

* Install the default distribution.

It will work, but you need an SMP kernel, and accelerated and higher resolution graphics, so:

* Install the i686-smp kernel (search for 'linux-kernel' in synaptic).

* Search for fglrx in synaptic, and install the fglrx modules, X driver and ATI control panel.

* Edit /etc/X11/xorg.conf, so each of the "Modeline" entries contains a 1600x1200 resolution as well (or whatever the top resolution of your LCD panel is), and change the driver section as follows:

Section "Device"
Identifier "ATI Technologies, Inc. ATI Default Card"
Driver "fglrx" <----- ADD THIS LINE
#Driver "vesa" <---- COMMENT OUT THIS LINE
BusID "PCI:1:0:0"
ChipID 0x71c5 <----- '''MAYBE''' ADD THIS LINE
EndSection

[On my UXGA t60p the ChipID line was actually fatal to getting fglrx to start up (/var/log/Xorg.0.log showed the driver falling back to VESA and fgl_glxgears would crash). Without that ChipID line my chip was identified as:

Chipset: "MOBILITY FireGL V5200 (M56 71C4)" (Chipset = 0x71c4)

which appears to correspond exactly to my machine's spec, and fgl_glxgears worked fine.]

Reboot, and you should be done. Check "cat /proc/cpuinfo" shows two CPUs, and run fgl_glxgears and check you get around 580 frames a second.

I've reported [https://launchpad.net/distros/ubuntu/+bug/46527 bug 46527] on the lack of screen driver detection, so hopefully this will get even easier.

Note you do NOT need to install ATI drivers from the ATI site. The Ubuntu drivers are sufficient.

Thanks to Rich Tango-Lowy (see below) for the hint re chip detection.

==Kubuntu Dapper Live CD==

If you're trying to install from the Kubuntu Desktop CD, you'll never make it to the login screen because the ATI display driver isn't recognized.

* Ctrl-Alt-F1
* sudo nano /etc/X11/xorg.conf
* change the display driver line that looks like:

Driver "ati"

to

Driver "vesa"

[I think I remember that it was "ati", but I could be wrong. In any
case this is very clearly the only Driver line in the ATI device specification section]

* Save and exit
* sudo /etc/init.d kdm restart

Now you get a login screen.

== Installing Gentoo 2006.0 ==

===Boot from Live CD===
Upon booting off the live cd you will come to the kernel selection prompt.
Enter:
gentoo doscsi
I had some trouble getting the wired NIC to be linked to the driver, often getting an error that the EEPROM failed a check. If this happens, you can try re-inserting the module,
>rmmod e1000; modprobe e1000
or rebooting and trying again. The wireless card isn't supported by the live cd so you're going to have to stick to wired for now.

===/etc/make.conf Settings===
The make.conf settings are the first thing you want to setup correctly before you proceed with the rest of the install process. All future updates will depend upon these settings as well.
CFLAGS="-march=prescott -O2 -pipe -msse3 -fomit-frame-pointer
VIDEO_CARDS="fglrx vesa fbdev"
INPUT_DEVICES="keyboard mouse synaptics"
FEATURES="sandbox ccache distlocks autoaddcvs parallel-fetch"
MAKEOPTS="-j3"
For a more complete discussion of the CFLAGS to use for a Core Duo processor, see [http://forums.gentoo.org/viewtopic-t-448761-highlight-core+duo+prescott.html?sid=97485d7e26a1f77e2bb06fa437a448ff this forum thread]. Some users recommend that the USE variable has the ibm value in it (eg. USE="ibm") but the Gentoo website says this is only for Power PC64 systems; I don't think we should use it. If anyone can shed more light on this, please update this section.

===Kernel Settings===
I was able to get the laptop running from i686 gentoo sources and recommend this to anyone installing Gentoo on their T60p. Alot of graphics support is left out of the kernel since the best graphics performance is with ATI's propietary drivers which you can emerge at the end of the kernel compile.
====Processor type and features====
* Turn on Symmetric multi-processing support.
* Set processor family to Pentium M.
* Turn off toshiba and dell laptop support.
* Set timer frequency to 1000 Hz since this is a desktop system.
====Power management options====
* Turn on all ACPI settings (especially IBM Thinkpad Extras) except ASUS/Medion and Toshiba Laptop Extras.
* Turn on CPU Frequency scaling.
** Turn on powersave, userspace, ondemand and conservative governor.
** Turn off ACPI Processor P-States driver.
** Turn off all AMD and Cyrix options.
** Turn on Intel Enhanced SpeedStep and Intel Speedstep on ICH-M chipsets (ioport interface).
** Turn off Intel SpeedStep on 440BX/ZX/MX chipsets (SMI interface).
** Turn off Intel Pentium 4 clock modulation, nVidia nForce2 FSB changing and Transmeta LongRun.
====Bus options====
* Turn on PCI Express support.
* Turn on Message Signaled Interupts.
* Turn on PCCard support and CardBus yenta-compatible bridge support.
====Networking support====
* Turn off Generic IEEE 802.11 Networking Stack.
* Turn on IrDA (infrared) subsystem support and sub-options.
* Turn on Bluetooth subsystem support and sub-options.
* Turn off Amateur Radio support (unless you work with actual radios.)
====Device Drivers====
* Turn off Memory Technology Devices.
* Turn off parallel port support.
* Turn on SCSI device support. In "low-level device drivers", chose the Serial ATA (SATA) support. Build it as a part of the kernel, and not as a kernel module.
* Turn off Fusion MPT device support.
* Turn on IEEE 1394 (FireWire) support.
* Turn on Network device support.
** Turn off all options in all categories under Network device support except the stated ones below.
** Turn on Intel(R) PRO/1000 Gigabit Ethernet support under Ethernet (1000 Mbit).
** Turn on Wireless LAN drivers (non-hamradio) & Wireless Extensions and none of the sub-options underneath.
** Most people do not need Fibre channel, ATM, WAN or PPP/SLIP support (if you do then turn it on. PPP is needed for GPRS/UMTS connectivity)
* Character device options...
** Turn off Parallel printer support.
** Turn on Intel/AMD/VIA HW Random Number Generator support.
** Turn on /dev/nvram support.
** Turn off /dev/agpgart (AGP Support).
** Turn off Direct Rendering Manager.
** Support for the [[Embedded_Security_Subsystem|Fritz Chip]] is located in "TPM Devices".
* Turn off all Graphics support options except the stated ones below,
** Turn on VESA VGA graphics support and set VESA driver type to vesafb.
** Turn on Enable firmware EDID and Enable Video Mode Handling Helpers.
** Turn on Support for the framebuffer splash.
* '''IMPORTANT:''' Turn off all Wireless device support under USB support -> USB Network Adapters or you will tear your hair out trying to get wireless.
* Turn on Sound card support.
** Turn on Advanced Linux Sound Architecture.
** Turn off all ISA, PCI, USB, generic and PCMCIA device options the stated on below.
** Turn on Intel HD Audio under PCI devices.
* Turn off all MMC/SD Card support options.
* Turn off LED devices.
* Cryptographic options... (needed for the wireless card ipw9345)
** Turn on AES chiphers
** Turn on Michael MIC keyed digest algorithm

That should do it. (I know, that's it.)
That should make sure that you have all the drivers necessary to boot the system and be able to use all your hardware (almost).

===Portage Ebuilds===

Always make sure you run this command before going any further so you can get the latest portage build and version...
emerge --sync && emerge portage

Since September 24 2006 I was able to make the latest ati-drivers work on the T60p without adding any lines to the unmask file (/etc/portage/package.unmask) under the gentoo-sources kernel. You should be able to run...
emerge ati-drivers
...without any problems.

Don't forget to emerge all the Thinkpad software as well...
emerge tpb tp_smapii tpctl

Then you can start to setup the wireless in this order at the command line...
/bin/sh /usr/portage/net-wireless/ieee80211/files/remove-old /usr/src/linux
emerge ieee80211 ipw3945 ipw3945d wireless-tools
/sbin/ipw3945d
ifconfig eth1 up

===xorg.conf Settings===

A piece of code is worth a thousand words; here is my xorg.conf that works at 3000-5000 FPS so far. I am still trying to find better parameters, but this is the best I got it to run so far. I intentionally left out the InputDevice section since I disabled my Synaptics pad (I like the center joystick better.) Just modify your xorg.conf sections with what is shown below.

Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
Load "dri"
Load "glx"
EndSection

Section "Device"
Identifier "VideoCard"
Driver "fglrx"
VendorName "ati"
BusID "PCI:1:0:0"
Option "VideoOverlay" "off"
EndSection

Section "dri"
Group "video"
Mode 0666
EndSection

Section "Extensions"
Option "XVideo" "Enable"
EndSection

Section "Screen"
Identifier "Screen"
Device "VideoCard"
Monitor "Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Make sure you assign your username to the video group in the /etc/group file or you will net get DRI (Direct Rendering) support. When debugging your running X windows system, always check /var/log/Xorg.0.log for any errors or hints at what may be configured incorrectly. This is how I was able to get so far with the graphics.

==External Sources==
*[http://arscognita.com/~richtl/T60p/index.html Rich Tango-Lowy's Mandriva 2007 Cooker on T60p page]
*[http://buzzy.tesuji.org/thinkpad_t60p.html Jon Lin's Gentoo Thinkpad T60p]

Installation instructions for the ThinkPad T60p

2006-10-03T07:00:11Z

Tobixen: /* Portage Ebuilds */ - I needed some more help to get the wifi up

[[Category:T60p]]
==Installing Ubuntu Dapper==

To get it going:

* Get Dapper i386 (I used the Daily ISO DVD).

* Install the default distribution.

It will work, but you need an SMP kernel, and accelerated and higher resolution graphics, so:

* Install the i686-smp kernel (search for 'linux-kernel' in synaptic).

* Search for fglrx in synaptic, and install the fglrx modules, X driver and ATI control panel.

* Edit /etc/X11/xorg.conf, so each of the "Modeline" entries contains a 1600x1200 resolution as well (or whatever the top resolution of your LCD panel is), and change the driver section as follows:

Section "Device"
Identifier "ATI Technologies, Inc. ATI Default Card"
Driver "fglrx" <----- ADD THIS LINE
#Driver "vesa" <---- COMMENT OUT THIS LINE
BusID "PCI:1:0:0"
ChipID 0x71c5 <----- '''MAYBE''' ADD THIS LINE
EndSection

[On my UXGA t60p the ChipID line was actually fatal to getting fglrx to start up (/var/log/Xorg.0.log showed the driver falling back to VESA and fgl_glxgears would crash). Without that ChipID line my chip was identified as:

Chipset: "MOBILITY FireGL V5200 (M56 71C4)" (Chipset = 0x71c4)

which appears to correspond exactly to my machine's spec, and fgl_glxgears worked fine.]

Reboot, and you should be done. Check "cat /proc/cpuinfo" shows two CPUs, and run fgl_glxgears and check you get around 580 frames a second.

I've reported [https://launchpad.net/distros/ubuntu/+bug/46527 bug 46527] on the lack of screen driver detection, so hopefully this will get even easier.

Note you do NOT need to install ATI drivers from the ATI site. The Ubuntu drivers are sufficient.

Thanks to Rich Tango-Lowy (see below) for the hint re chip detection.

==Kubuntu Dapper Live CD==

If you're trying to install from the Kubuntu Desktop CD, you'll never make it to the login screen because the ATI display driver isn't recognized.

* Ctrl-Alt-F1
* sudo nano /etc/X11/xorg.conf
* change the display driver line that looks like:

Driver "ati"

to

Driver "vesa"

[I think I remember that it was "ati", but I could be wrong. In any
case this is very clearly the only Driver line in the ATI device specification section]

* Save and exit
* sudo /etc/init.d kdm restart

Now you get a login screen.

== Installing Gentoo 2006.0 ==

===Boot from Live CD===
Upon booting off the live cd you will come to the kernel selection prompt.
Enter:
gentoo doscsi
I had some trouble getting the wired NIC to be linked to the driver, often getting an error that the EEPROM failed a check. If this happens, you can try re-inserting the module,
>rmmod e1000; modprobe e1000
or rebooting and trying again. The wireless card isn't supported by the live cd so you're going to have to stick to wired for now.

===/etc/make.conf Settings===
The make.conf settings are the first thing you want to setup correctly before you proceed with the rest of the install process. All future updates will depend upon these settings as well.
CFLAGS="-march=prescott -O2 -pipe -msse3 -fomit-frame-pointer
VIDEO_CARDS="fglrx vesa fbdev"
INPUT_DEVICES="keyboard mouse synaptics"
FEATURES="sandbox ccache distlocks autoaddcvs parallel-fetch"
MAKEOPTS="-j3"
For a more complete discussion of the CFLAGS to use for a Core Duo processor, see [http://forums.gentoo.org/viewtopic-t-448761-highlight-core+duo+prescott.html?sid=97485d7e26a1f77e2bb06fa437a448ff this forum thread]. Some users recommend that the USE variable has the ibm value in it (eg. USE="ibm") but the Gentoo website says this is only for Power PC64 systems; I don't think we should use it. If anyone can shed more light on this, please update this section.

===Kernel Settings===
I was able to get the laptop running from i686 gentoo sources and recommend this to anyone installing Gentoo on their T60p. Alot of graphics support is left out of the kernel since the best graphics performance is with ATI's propietary drivers which you can emerge at the end of the kernel compile.
====Processor type and features====
* Turn on Symmetric multi-processing support.
* Set processor family to Pentium M.
* Turn off toshiba and dell laptop support.
* Set timer frequency to 1000 Hz since this is a desktop system.
====Power management options====
* Turn on all ACPI settings (especially IBM Thinkpad Extras) except ASUS/Medion and Toshiba Laptop Extras.
* Turn on CPU Frequency scaling.
** Turn on powersave, userspace, ondemand and conservative governor.
** Turn off ACPI Processor P-States driver.
** Turn off all AMD and Cyrix options.
** Turn on Intel Enhanced SpeedStep and Intel Speedstep on ICH-M chipsets (ioport interface).
** Turn off Intel SpeedStep on 440BX/ZX/MX chipsets (SMI interface).
** Turn off Intel Pentium 4 clock modulation, nVidia nForce2 FSB changing and Transmeta LongRun.
====Bus options====
* Turn on PCI Express support.
* Turn on Message Signaled Interupts.
* Turn on PCCard support and CardBus yenta-compatible bridge support.
====Networking support====
* Turn off Generic IEEE 802.11 Networking Stack.
* Turn on IrDA (infrared) subsystem support and sub-options.
* Turn on Bluetooth subsystem support and sub-options.
* Turn off Amateur Radio support (unless you work with actual radios.)
====Device Drivers====
* Turn off Memory Technology Devices.
* Turn off parallel port support.
* Turn on SCSI device support. In "low-level device drivers", chose the Serial ATA (SATA) support. Build it as a part of the kernel, and not as a kernel module.
* Turn off Fusion MPT device support.
* Turn on IEEE 1394 (FireWire) support.
* Turn on Network device support.
** Turn off all options in all categories under Network device support except the stated ones below.
** Turn on Intel(R) PRO/1000 Gigabit Ethernet support under Ethernet (1000 Mbit).
** Turn on Wireless LAN drivers (non-hamradio) & Wireless Extensions and none of the sub-options underneath.
** Most people do not need Fibre channel, ATM, WAN or PPP/SLIP support (if you do then turn it on. PPP is needed for GPRS/UMTS connectivity)
* Character device options...
** Turn off Parallel printer support.
** Turn on Intel/AMD/VIA HW Random Number Generator support.
** Turn on /dev/nvram support.
** Turn off /dev/agpgart (AGP Support).
** Turn off Direct Rendering Manager.
** Support for the [[Embedded_Security_Subsystem|Fritz Chip]] is located in "TPM Devices".
* Turn off all Graphics support options except the stated ones below,
** Turn on VESA VGA graphics support and set VESA driver type to vesafb.
** Turn on Enable firmware EDID and Enable Video Mode Handling Helpers.
** Turn on Support for the framebuffer splash.
* '''IMPORTANT:''' Turn off all Wireless device support under USB support -> USB Network Adapters or you will tear your hair out trying to get wireless.
* Turn on Sound card support.
** Turn on Advanced Linux Sound Architecture.
** Turn off all ISA, PCI, USB, generic and PCMCIA device options the stated on below.
** Turn on Intel HD Audio under PCI devices.
* Turn off all MMC/SD Card support options.
* Turn off LED devices.
* Turn on Michael MIC keyed digest algorithm under Cryptographic API (for wireless card ipw9345.)

That should do it. (I know, that's it.)
That should make sure that you have all the drivers necessary to boot the system and be able to use all your hardware (almost).

===Portage Ebuilds===

Always make sure you run this command before going any further so you can get the latest portage build and version...
emerge --sync && emerge portage

Since September 24 2006 I was able to make the latest ati-drivers work on the T60p without adding any lines to the unmask file (/etc/portage/package.unmask) under the gentoo-sources kernel. You should be able to run...
emerge ati-drivers
...without any problems.

Don't forget to emerge all the Thinkpad software as well...
emerge tpb tp_smapii tpctl

Then you can start to setup the wireless in this order at the command line...
/bin/sh /usr/portage/net-wireless/ieee80211/files/remove-old /usr/src/linux
emerge ieee80211 ipw3945 ipw3945d wireless-tools
/sbin/ipw3945d
ifconfig eth1 up

===xorg.conf Settings===

A piece of code is worth a thousand words; here is my xorg.conf that works at 3000-5000 FPS so far. I am still trying to find better parameters, but this is the best I got it to run so far. I intentionally left out the InputDevice section since I disabled my Synaptics pad (I like the center joystick better.) Just modify your xorg.conf sections with what is shown below.

Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
Load "dri"
Load "glx"
EndSection

Section "Device"
Identifier "VideoCard"
Driver "fglrx"
VendorName "ati"
BusID "PCI:1:0:0"
Option "VideoOverlay" "off"
EndSection

Section "dri"
Group "video"
Mode 0666
EndSection

Section "Extensions"
Option "XVideo" "Enable"
EndSection

Section "Screen"
Identifier "Screen"
Device "VideoCard"
Monitor "Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Make sure you assign your username to the video group in the /etc/group file or you will net get DRI (Direct Rendering) support. When debugging your running X windows system, always check /var/log/Xorg.0.log for any errors or hints at what may be configured incorrectly. This is how I was able to get so far with the graphics.

==External Sources==
*[http://arscognita.com/~richtl/T60p/index.html Rich Tango-Lowy's Mandriva 2007 Cooker on T60p page]
*[http://buzzy.tesuji.org/thinkpad_t60p.html Jon Lin's Gentoo Thinkpad T60p]

Installation instructions for the ThinkPad T60p

2006-10-03T06:58:41Z

Tobixen: /* Device Drivers */ - Access to the "Fritz Chip" can be compiled in

[[Category:T60p]]
==Installing Ubuntu Dapper==

To get it going:

* Get Dapper i386 (I used the Daily ISO DVD).

* Install the default distribution.

It will work, but you need an SMP kernel, and accelerated and higher resolution graphics, so:

* Install the i686-smp kernel (search for 'linux-kernel' in synaptic).

* Search for fglrx in synaptic, and install the fglrx modules, X driver and ATI control panel.

* Edit /etc/X11/xorg.conf, so each of the "Modeline" entries contains a 1600x1200 resolution as well (or whatever the top resolution of your LCD panel is), and change the driver section as follows:

Section "Device"
Identifier "ATI Technologies, Inc. ATI Default Card"
Driver "fglrx" <----- ADD THIS LINE
#Driver "vesa" <---- COMMENT OUT THIS LINE
BusID "PCI:1:0:0"
ChipID 0x71c5 <----- '''MAYBE''' ADD THIS LINE
EndSection

[On my UXGA t60p the ChipID line was actually fatal to getting fglrx to start up (/var/log/Xorg.0.log showed the driver falling back to VESA and fgl_glxgears would crash). Without that ChipID line my chip was identified as:

Chipset: "MOBILITY FireGL V5200 (M56 71C4)" (Chipset = 0x71c4)

which appears to correspond exactly to my machine's spec, and fgl_glxgears worked fine.]

Reboot, and you should be done. Check "cat /proc/cpuinfo" shows two CPUs, and run fgl_glxgears and check you get around 580 frames a second.

I've reported [https://launchpad.net/distros/ubuntu/+bug/46527 bug 46527] on the lack of screen driver detection, so hopefully this will get even easier.

Note you do NOT need to install ATI drivers from the ATI site. The Ubuntu drivers are sufficient.

Thanks to Rich Tango-Lowy (see below) for the hint re chip detection.

==Kubuntu Dapper Live CD==

If you're trying to install from the Kubuntu Desktop CD, you'll never make it to the login screen because the ATI display driver isn't recognized.

* Ctrl-Alt-F1
* sudo nano /etc/X11/xorg.conf
* change the display driver line that looks like:

Driver "ati"

to

Driver "vesa"

[I think I remember that it was "ati", but I could be wrong. In any
case this is very clearly the only Driver line in the ATI device specification section]

* Save and exit
* sudo /etc/init.d kdm restart

Now you get a login screen.

== Installing Gentoo 2006.0 ==

===Boot from Live CD===
Upon booting off the live cd you will come to the kernel selection prompt.
Enter:
gentoo doscsi
I had some trouble getting the wired NIC to be linked to the driver, often getting an error that the EEPROM failed a check. If this happens, you can try re-inserting the module,
>rmmod e1000; modprobe e1000
or rebooting and trying again. The wireless card isn't supported by the live cd so you're going to have to stick to wired for now.

===/etc/make.conf Settings===
The make.conf settings are the first thing you want to setup correctly before you proceed with the rest of the install process. All future updates will depend upon these settings as well.
CFLAGS="-march=prescott -O2 -pipe -msse3 -fomit-frame-pointer
VIDEO_CARDS="fglrx vesa fbdev"
INPUT_DEVICES="keyboard mouse synaptics"
FEATURES="sandbox ccache distlocks autoaddcvs parallel-fetch"
MAKEOPTS="-j3"
For a more complete discussion of the CFLAGS to use for a Core Duo processor, see [http://forums.gentoo.org/viewtopic-t-448761-highlight-core+duo+prescott.html?sid=97485d7e26a1f77e2bb06fa437a448ff this forum thread]. Some users recommend that the USE variable has the ibm value in it (eg. USE="ibm") but the Gentoo website says this is only for Power PC64 systems; I don't think we should use it. If anyone can shed more light on this, please update this section.

===Kernel Settings===
I was able to get the laptop running from i686 gentoo sources and recommend this to anyone installing Gentoo on their T60p. Alot of graphics support is left out of the kernel since the best graphics performance is with ATI's propietary drivers which you can emerge at the end of the kernel compile.
====Processor type and features====
* Turn on Symmetric multi-processing support.
* Set processor family to Pentium M.
* Turn off toshiba and dell laptop support.
* Set timer frequency to 1000 Hz since this is a desktop system.
====Power management options====
* Turn on all ACPI settings (especially IBM Thinkpad Extras) except ASUS/Medion and Toshiba Laptop Extras.
* Turn on CPU Frequency scaling.
** Turn on powersave, userspace, ondemand and conservative governor.
** Turn off ACPI Processor P-States driver.
** Turn off all AMD and Cyrix options.
** Turn on Intel Enhanced SpeedStep and Intel Speedstep on ICH-M chipsets (ioport interface).
** Turn off Intel SpeedStep on 440BX/ZX/MX chipsets (SMI interface).
** Turn off Intel Pentium 4 clock modulation, nVidia nForce2 FSB changing and Transmeta LongRun.
====Bus options====
* Turn on PCI Express support.
* Turn on Message Signaled Interupts.
* Turn on PCCard support and CardBus yenta-compatible bridge support.
====Networking support====
* Turn off Generic IEEE 802.11 Networking Stack.
* Turn on IrDA (infrared) subsystem support and sub-options.
* Turn on Bluetooth subsystem support and sub-options.
* Turn off Amateur Radio support (unless you work with actual radios.)
====Device Drivers====
* Turn off Memory Technology Devices.
* Turn off parallel port support.
* Turn on SCSI device support. In "low-level device drivers", chose the Serial ATA (SATA) support. Build it as a part of the kernel, and not as a kernel module.
* Turn off Fusion MPT device support.
* Turn on IEEE 1394 (FireWire) support.
* Turn on Network device support.
** Turn off all options in all categories under Network device support except the stated ones below.
** Turn on Intel(R) PRO/1000 Gigabit Ethernet support under Ethernet (1000 Mbit).
** Turn on Wireless LAN drivers (non-hamradio) & Wireless Extensions and none of the sub-options underneath.
** Most people do not need Fibre channel, ATM, WAN or PPP/SLIP support (if you do then turn it on. PPP is needed for GPRS/UMTS connectivity)
* Character device options...
** Turn off Parallel printer support.
** Turn on Intel/AMD/VIA HW Random Number Generator support.
** Turn on /dev/nvram support.
** Turn off /dev/agpgart (AGP Support).
** Turn off Direct Rendering Manager.
** Support for the [[Embedded_Security_Subsystem|Fritz Chip]] is located in "TPM Devices".
* Turn off all Graphics support options except the stated ones below,
** Turn on VESA VGA graphics support and set VESA driver type to vesafb.
** Turn on Enable firmware EDID and Enable Video Mode Handling Helpers.
** Turn on Support for the framebuffer splash.
* '''IMPORTANT:''' Turn off all Wireless device support under USB support -> USB Network Adapters or you will tear your hair out trying to get wireless.
* Turn on Sound card support.
** Turn on Advanced Linux Sound Architecture.
** Turn off all ISA, PCI, USB, generic and PCMCIA device options the stated on below.
** Turn on Intel HD Audio under PCI devices.
* Turn off all MMC/SD Card support options.
* Turn off LED devices.
* Turn on Michael MIC keyed digest algorithm under Cryptographic API (for wireless card ipw9345.)

That should do it. (I know, that's it.)
That should make sure that you have all the drivers necessary to boot the system and be able to use all your hardware (almost).

===Portage Ebuilds===

Always make sure you run this command before going any further so you can get the latest portage build and version...
emerge --sync && emerge portage

Since September 24 2006 I was able to make the latest ati-drivers work on the T60p without adding any lines to the unmask file (/etc/portage/package.unmask) under the gentoo-sources kernel. You should be able to run...
emerge ati-drivers
...without any problems.

Don't forget to emerge all the Thinkpad software as well...
emerge tpb tp_smapii tpctl

Then you can start to setup the wireless in this order at the command line...
/bin/sh /usr/portage/net-wireless/ieee80211/files/remove-old /usr/src/linux
emerge ieee80211 ipw3945 ipw3945d wireless-tools

===xorg.conf Settings===

A piece of code is worth a thousand words; here is my xorg.conf that works at 3000-5000 FPS so far. I am still trying to find better parameters, but this is the best I got it to run so far. I intentionally left out the InputDevice section since I disabled my Synaptics pad (I like the center joystick better.) Just modify your xorg.conf sections with what is shown below.

Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
Load "dri"
Load "glx"
EndSection

Section "Device"
Identifier "VideoCard"
Driver "fglrx"
VendorName "ati"
BusID "PCI:1:0:0"
Option "VideoOverlay" "off"
EndSection

Section "dri"
Group "video"
Mode 0666
EndSection

Section "Extensions"
Option "XVideo" "Enable"
EndSection

Section "Screen"
Identifier "Screen"
Device "VideoCard"
Monitor "Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Make sure you assign your username to the video group in the /etc/group file or you will net get DRI (Direct Rendering) support. When debugging your running X windows system, always check /var/log/Xorg.0.log for any errors or hints at what may be configured incorrectly. This is how I was able to get so far with the graphics.

==External Sources==
*[http://arscognita.com/~richtl/T60p/index.html Rich Tango-Lowy's Mandriva 2007 Cooker on T60p page]
*[http://buzzy.tesuji.org/thinkpad_t60p.html Jon Lin's Gentoo Thinkpad T60p]

Installation instructions for the ThinkPad T60p

2006-10-03T06:52:50Z

Tobixen: /* Device Drivers */ - The SATA driver has to be compiled into kernel to allow direct booting from harddisk

[[Category:T60p]]
==Installing Ubuntu Dapper==

To get it going:

* Get Dapper i386 (I used the Daily ISO DVD).

* Install the default distribution.

It will work, but you need an SMP kernel, and accelerated and higher resolution graphics, so:

* Install the i686-smp kernel (search for 'linux-kernel' in synaptic).

* Search for fglrx in synaptic, and install the fglrx modules, X driver and ATI control panel.

* Edit /etc/X11/xorg.conf, so each of the "Modeline" entries contains a 1600x1200 resolution as well (or whatever the top resolution of your LCD panel is), and change the driver section as follows:

Section "Device"
Identifier "ATI Technologies, Inc. ATI Default Card"
Driver "fglrx" <----- ADD THIS LINE
#Driver "vesa" <---- COMMENT OUT THIS LINE
BusID "PCI:1:0:0"
ChipID 0x71c5 <----- '''MAYBE''' ADD THIS LINE
EndSection

[On my UXGA t60p the ChipID line was actually fatal to getting fglrx to start up (/var/log/Xorg.0.log showed the driver falling back to VESA and fgl_glxgears would crash). Without that ChipID line my chip was identified as:

Chipset: "MOBILITY FireGL V5200 (M56 71C4)" (Chipset = 0x71c4)

which appears to correspond exactly to my machine's spec, and fgl_glxgears worked fine.]

Reboot, and you should be done. Check "cat /proc/cpuinfo" shows two CPUs, and run fgl_glxgears and check you get around 580 frames a second.

I've reported [https://launchpad.net/distros/ubuntu/+bug/46527 bug 46527] on the lack of screen driver detection, so hopefully this will get even easier.

Note you do NOT need to install ATI drivers from the ATI site. The Ubuntu drivers are sufficient.

Thanks to Rich Tango-Lowy (see below) for the hint re chip detection.

==Kubuntu Dapper Live CD==

If you're trying to install from the Kubuntu Desktop CD, you'll never make it to the login screen because the ATI display driver isn't recognized.

* Ctrl-Alt-F1
* sudo nano /etc/X11/xorg.conf
* change the display driver line that looks like:

Driver "ati"

to

Driver "vesa"

[I think I remember that it was "ati", but I could be wrong. In any
case this is very clearly the only Driver line in the ATI device specification section]

* Save and exit
* sudo /etc/init.d kdm restart

Now you get a login screen.

== Installing Gentoo 2006.0 ==

===Boot from Live CD===
Upon booting off the live cd you will come to the kernel selection prompt.
Enter:
gentoo doscsi
I had some trouble getting the wired NIC to be linked to the driver, often getting an error that the EEPROM failed a check. If this happens, you can try re-inserting the module,
>rmmod e1000; modprobe e1000
or rebooting and trying again. The wireless card isn't supported by the live cd so you're going to have to stick to wired for now.

===/etc/make.conf Settings===
The make.conf settings are the first thing you want to setup correctly before you proceed with the rest of the install process. All future updates will depend upon these settings as well.
CFLAGS="-march=prescott -O2 -pipe -msse3 -fomit-frame-pointer
VIDEO_CARDS="fglrx vesa fbdev"
INPUT_DEVICES="keyboard mouse synaptics"
FEATURES="sandbox ccache distlocks autoaddcvs parallel-fetch"
MAKEOPTS="-j3"
For a more complete discussion of the CFLAGS to use for a Core Duo processor, see [http://forums.gentoo.org/viewtopic-t-448761-highlight-core+duo+prescott.html?sid=97485d7e26a1f77e2bb06fa437a448ff this forum thread]. Some users recommend that the USE variable has the ibm value in it (eg. USE="ibm") but the Gentoo website says this is only for Power PC64 systems; I don't think we should use it. If anyone can shed more light on this, please update this section.

===Kernel Settings===
I was able to get the laptop running from i686 gentoo sources and recommend this to anyone installing Gentoo on their T60p. Alot of graphics support is left out of the kernel since the best graphics performance is with ATI's propietary drivers which you can emerge at the end of the kernel compile.
====Processor type and features====
* Turn on Symmetric multi-processing support.
* Set processor family to Pentium M.
* Turn off toshiba and dell laptop support.
* Set timer frequency to 1000 Hz since this is a desktop system.
====Power management options====
* Turn on all ACPI settings (especially IBM Thinkpad Extras) except ASUS/Medion and Toshiba Laptop Extras.
* Turn on CPU Frequency scaling.
** Turn on powersave, userspace, ondemand and conservative governor.
** Turn off ACPI Processor P-States driver.
** Turn off all AMD and Cyrix options.
** Turn on Intel Enhanced SpeedStep and Intel Speedstep on ICH-M chipsets (ioport interface).
** Turn off Intel SpeedStep on 440BX/ZX/MX chipsets (SMI interface).
** Turn off Intel Pentium 4 clock modulation, nVidia nForce2 FSB changing and Transmeta LongRun.
====Bus options====
* Turn on PCI Express support.
* Turn on Message Signaled Interupts.
* Turn on PCCard support and CardBus yenta-compatible bridge support.
====Networking support====
* Turn off Generic IEEE 802.11 Networking Stack.
* Turn on IrDA (infrared) subsystem support and sub-options.
* Turn on Bluetooth subsystem support and sub-options.
* Turn off Amateur Radio support (unless you work with actual radios.)
====Device Drivers====
* Turn off Memory Technology Devices.
* Turn off parallel port support.
* Turn on SCSI device support. In "low-level device drivers", chose the Serial ATA (SATA) support. Build it as a part of the kernel, and not as a kernel module.
* Turn off Fusion MPT device support.
* Turn on IEEE 1394 (FireWire) support.
* Turn on Network device support.
** Turn off all options in all categories under Network device support except the stated ones below.
** Turn on Intel(R) PRO/1000 Gigabit Ethernet support under Ethernet (1000 Mbit).
** Turn on Wireless LAN drivers (non-hamradio) & Wireless Extensions and none of the sub-options underneath.
** Most people do not need Fibre channel, ATM, WAN or PPP/SLIP support (if you do then turn it on.)
* Character device options...
** Turn off Parallel printer support.
** Turn on Intel/AMD/VIA HW Random Number Generator support.
** Turn on /dev/nvram support.
** Turn off /dev/agpgart (AGP Support).
** Turn off Direct Rendering Manager.
* Turn off all Graphics support options except the stated ones below,
** Turn on VESA VGA graphics support and set VESA driver type to vesafb.
** Turn on Enable firmware EDID and Enable Video Mode Handling Helpers.
** Turn on Support for the framebuffer splash.
* '''IMPORTANT:''' Turn off all Wireless device support under USB support -> USB Network Adapters or you will tear your hair out trying to get wireless.
* Turn on Sound card support.
** Turn on Advanced Linux Sound Architecture.
** Turn off all ISA, PCI, USB, generic and PCMCIA device options the stated on below.
** Turn on Intel HD Audio under PCI devices.
* Turn off all MMC/SD Card support options.
* Turn off LED devices.
* Turn on Michael MIC keyed digest algorithm under Cryptographic API (for wireless card ipw9345.)

That should do it. (I know, that's it.)
That should make sure that you have all the drivers necessary to boot the system and be able to use all your hardware (almost).

===Portage Ebuilds===

Always make sure you run this command before going any further so you can get the latest portage build and version...
emerge --sync && emerge portage

Since September 24 2006 I was able to make the latest ati-drivers work on the T60p without adding any lines to the unmask file (/etc/portage/package.unmask) under the gentoo-sources kernel. You should be able to run...
emerge ati-drivers
...without any problems.

Don't forget to emerge all the Thinkpad software as well...
emerge tpb tp_smapii tpctl

Then you can start to setup the wireless in this order at the command line...
/bin/sh /usr/portage/net-wireless/ieee80211/files/remove-old /usr/src/linux
emerge ieee80211 ipw3945 ipw3945d wireless-tools

===xorg.conf Settings===

A piece of code is worth a thousand words; here is my xorg.conf that works at 3000-5000 FPS so far. I am still trying to find better parameters, but this is the best I got it to run so far. I intentionally left out the InputDevice section since I disabled my Synaptics pad (I like the center joystick better.) Just modify your xorg.conf sections with what is shown below.

Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
Load "dri"
Load "glx"
EndSection

Section "Device"
Identifier "VideoCard"
Driver "fglrx"
VendorName "ati"
BusID "PCI:1:0:0"
Option "VideoOverlay" "off"
EndSection

Section "dri"
Group "video"
Mode 0666
EndSection

Section "Extensions"
Option "XVideo" "Enable"
EndSection

Section "Screen"
Identifier "Screen"
Device "VideoCard"
Monitor "Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Make sure you assign your username to the video group in the /etc/group file or you will net get DRI (Direct Rendering) support. When debugging your running X windows system, always check /var/log/Xorg.0.log for any errors or hints at what may be configured incorrectly. This is how I was able to get so far with the graphics.

==External Sources==
*[http://arscognita.com/~richtl/T60p/index.html Rich Tango-Lowy's Mandriva 2007 Cooker on T60p page]
*[http://buzzy.tesuji.org/thinkpad_t60p.html Jon Lin's Gentoo Thinkpad T60p]

Installation instructions for the ThinkPad T60

2006-10-03T06:20:11Z

Tobixen: /* Distribution-specific instructions */ - I found this link causually, it really helped me with my T60

Specific installation notes for the ThinkPad {{T60}}.

==Distribution-specific instructions==

*{{Install|Ubuntu| 6.06 Flight 5|T60}}
*{{Install|Fedora| Core 5| T60}}
*{{Install|Suse| 10.1| T60}}
* For Gentoo, there exists [[Installation_instructions_for_the_ThinkPad_T60p|installation instructions for T60p]], the sister model.

== Compatibility ==
* [http://www.emperorlinux.com/mfgr/lenovo/toucan/?tab=details&id=358 Thinkpad T60] page on [http://www.emperorlinux.com emperorlinux.com] (compatibility review and custom kernel)

ATI Mobility Radeon X300

2006-08-09T11:52:07Z

Tobixen: The 3D-section was duplicated.

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ATI Mobility Radeon X300 ===
This is an ATI video adapter

=== Features ===
* Chipset: ATI M22
* PCI ID: 1002:5460
* PCI Express x16
* 32 or 64MB GDDR1 on-chip video memory
* "HyperMemory": can use system memory for graphics processing
* "PowerPlay 4.0" technology for dynamic engine clock, memory clock and core voltage, refresh rate reduction and thermal status reporting.
</div>
|style="vertical-align:top" |
|}

See [http://www.ati.com/products/radeonx300/specs.html specifications] from ATI, as well as the [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "snapshot" data sheet] (referes to the 32MB on-chip, 128MB "HyperMemory" version).

=== Linux driver ===

The X.org [[radeon]] driver works well and support most (but not all) features. ATI provides [[fglrx]], a closed-source alternative adding some functionality such as TV out and 3D acceleration.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correct.

==== External VGA port ====
There are known problems. Both the <tt>radeon</tt> and [[fglrx]] drivers turn off the switching between internal and external port.

=====With the <tt>vesa</tt> driver=====
Using the "vesa" driver built into X.org, mode switching modes. However, this loses acceleration and some capabilities.

=====With the <tt>radeon</tt> driver=====
On-the-fly swiching doesn't work. To activate both ports in clone mode with a reasonable CRT refresh rate, use the following in {{path|/etc/X11/xorg.conf}}:

Section "Device"
Identifier "Videocard0"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility X300"

Driver "radeon"
Option "DynamicClocks" "on"

Option "MergedFB" "on"
Option "MonitorLayout" "LVDS, CRT"
Option "CRT2Hsync" "50-75"
Option "CRT2VRefresh" "50-82"
EndSection

Note that without the <tt>MonitorLayout</tt> option, if the external monitor is connected when X starts then the LCD will be deactivated and you will need to restart X.

(Tested wth Fedora Core 4 on ThinkPad {{T43}}).

See also the related discussion about [[Additional options for the radeon driver]].

=====With the [[fglrx]] driver=====
On-the-fly works with <tt>aticonfig</tt> in the newest Drivers, see [[Fglrx#Display_Switching_.28Dynamic_Display_Management.29|Display Switching]]. Additionally, to use both ports there is the possibility to either have the monitor connected during X startup, or force activation of both ports by adding
Option "ForceMonitors" "lvds,crt1"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}. Powering the CRT port consumes 400-500mW, regardless of whether a CRT is attached.

==== S-Video port (TV-out) ====

Works with the proprietary [[fglrx]] driver (as of version 8.19.10). To activate, add
Option "ForceMonitors" "lvds,tv"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}} and restart X.

==== DVI port ====
??

=== 3D acceleration ===
OpenGL 3D acceleration is provided by the proprietary [[fglrx]] driver (when DRI is enabled). Note that performance is affected by the power saving mode.

The open source <tt>r300</tt> [[DRM]] module also aims to provide 3D acceleration. This currently requires the CVS/GIT versions of [[X.org]], [[DRM]] and [[Mesa]], and has been observed to occasionally crash (e.g., when running Google Earth or <tt>ppracer</tt>on a {{T43}}). You can [[How to compile an experimental X server|install it experimentally]] for testing.

=== Linux kernel Framebuffer driver ===

radeonfb might cause problems with hardware acceleration under X on some systems, vesafb and vesafb-tng on the other hand has been reported to work just fine.

=== Clock rates, voltage and power===
{| border="1" cellspacing="0" cellpadding="2"
|+ Clock rates, voltages and power {{footnote|1}}
! Mode !! core freq !! memory freq !! voltage !! idle !! 3DMarks (Windows, 1600x1200, LCD only)
|-
| Performance || 300 || 230 MHz || 1.15V || 2.98 W || 8.28 W
|-
| Balanced || 183 || 210 MHz || 1.00V || 1.71 W || 3.88 W
|-
| Battery || 120 || 105 MHz || 1.00V || 1.61 W || 2.74 W
|}

{| border="1" cellspacing="0" cellpadding="2"
|+ ATI drivers for Windows {{footnote|2}} and [[fglrx]]
! Mode !! core freq !! memory freq
|-
| Performance || 297.00 || 229.50
|-
| Balanced || 209.25 || 182.25
|-
| Battery || 104.63 || 121.50
|}

Experimentally, the difference between the Performance and Battery settings under Linux with the <tt>radeon</tt> driver and <tt>DynamicClocks</tt> enabled is roughly 0.3W and 3-4 degrees in GPU temperature on a ThinkPad {{T43}}. Further frequency reduction leads to display flickering or corruption.

See [[How to make use of Graphics Chips Power Management features]] for details on how to control this using [[Rovclock]], [[How to make use of Graphics Chips Power Management features|<tt>DynamicClocks</tt> option to the <tt>radeon</tt> driver]] and or the [[fglrx]] driver.

Presently the lowest idle-mode power consumption is achieved using the proprietary [[fglrx]] driver and
# aticonfig --set-powerstate=1 --effective=now

=== ThinkPads this chip may be found in ===
* {{R52}}
* {{T43}}
* {{Z60m}}

{{footnotes|
#according to the [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "Snapshot" data sheet] (which refers to the 32MB on-chip, 128MB "HyperMemory" version)
#inspected using [http://www.pbus-167.com/chc.htm Notebook Hardware Control]
}}

[[Category:Components]]

IBM Integrated Bluetooth IV with 56K Modem (BMDC-3)

2005-12-04T07:22:32Z

Tobixen:

__NOTOC__
{| width="100%"
|style="vertical-align:top" |[[Image:Logo_bluetooth.jpg|Bluetooth Logo]]
|style="vertical-align:top" |
<div style="margin:0px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== IBM Integrated Bluetooth IV with 56K Modem (BMDC-3) ===
This is a combination USB Bluetooth and AC97 Modem Adapter that is installed in a [[CDC slot]].
=== Bluetooth Features ===
* Chipset: Broadcom
* USB VID/PID: 0A5C:201E
=== Modem Features ===
* Chipset: Conexant
* AC'97 Modem
</div>
|}
=== IBM Partnumbers ===
*IBM FRU PN: 39T0022 ($37.50 in July 2005) - ''no longer available at IBM''
*IBM FRU PN: 39T0024 ($49.00 in September 2005) - ''no longer available at IBM''
*IBM FRU PN: 39T0026 ($50.00 in November 2005)

This part takes the place of the 56K Modem board.
It requires a Bluetooth antenna, and some ThinkPads built without Bluetooth already have the antenna installed -- the antenna wire may be found disconnected and taped under the Modem board.

In addition to the Modem/BT module, a Bluetooth Thinkpad also uses an extra indicator LED below the LCD display, and another indicator LED on the top of the lid. To see these two LEDs, two new clear plates are required. The entire set of replacement sticker plates can be ordered as FRU 26R8409 ($11.50 as of November 2005). (formerly FRU: 13R2455)

As of November 2005, IBM charged $13.50 for Airborne shipping, for a total of $75.00 for the BMDC-3 and replacement sticker plates.

See: https://www-132.ibm.com/content/home/store_IBMPublicUSA/en_US/parts/parts_r.html

=== Linux Bluetooth driver ===
The Bluetooth device is implemented using USB. Enabling/disabling bluetooth leads to USB connect and disconnect events. It can be enabled or disabled by:

* pressing the {{key|Fn}}{{key|F5}} key combination;
* using [[ibm-acpi]].

As Bluetooth is implemented using USB, this will only work with USB drivers enabled:

:modprobe uhci-hcd ; modprobe ehci-hcd

The bcm203x kernel module, which is included in recent kernels, supports this chipset. Since the Bluetooth device is using USB, you have to make sure to '''compile it as a module'''. If it's built into the kernel, the kernel won't detect the chip at boottime (when Bluetooth is turned off).

Use bluez-utils (http://www.bluez.org/) or fancier software like the GNOME Bluetooth subsystem (http://usefulinc.com/software/gnome-bluetooth) to use the device.

Some problems have been reported using bluetooth after a suspend/resume cycle on the T43. These problems can be mitigated by unloading the USB kernel modules (uhci_hcd, ehci_hcd, hci_usb, bcm203x) before the machine is put to sleep, and by re-loading these modules when the machine wakes up again.

On a T43p you must ensure that you call hotplug (re)start upon resume or you will lose bluetooth functionality. See the ACPI area for sample suspend scripts, or if bluetooth flakes on a debian system at any time you can manually call

:/etc/init.d/hotplug restart

and then it will come back with another {{key|Fn}}{{key|F5}} press.

=== Linux Modem driver ===
Although the [http://www.smlink.com/ Smartlink] driver for Agere modems is able to communicate with the modem via AT commands, it cannot dial out (contradicting reports welcome!).

If your favourite distribution does not include a hsfmodem driver (search for "hsfmodem" or "Conexant"), you can try the one from Linuxant: http://www.linuxant.com/drivers (14k free as in beer, 56k+Fax license 15$, they explain this policy under: http://www.linuxant.com/store/faq.php )

=== ThinkPads this card may be found in ===
* {{R52}}
* {{T43}}, {{T43p}}
* {{X32}}
* {{X41}}, {{X41T}}
* {{Z60m}}, {{Z60t}}

===See also===
* [[BluetoothGentooNokia | User story on how to connect to Internet through a Bluetooth phone]]

===External Sources===
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51427 IBM's page about configuring Bluetooth under Linux]

[[Category:Components]]

How to setup Bluetooth

2005-12-04T07:19:24Z

Tobixen:

This is a subjective story about my experiences connecting a Thinkpad T43 running Gentoo and a Nokia N70 using Bluetooth, but I suppose most of the stuff here is generic stuff about how to connect laptops with linux with cellphones using bluetooth.

The kernel used was 2.6.14-gentoo, patched up to get the SATA working after suspend-to-memory.

First of all, installation of Bluez; the following gentoo ebuilds was installed:

:net-wireless/bluez-bluefw
:net-wireless/bluez-firmware
:net-wireless/bluez-hcidump
:net-wireless/bluez-hciemu
:net-wireless/bluez-libs
:net-wireless/bluez-utils

net-wireless/bluez-kernel was also installed, but later I read it should not be needed when running 2.6-kernel - it could even be harmful.

The first blocker I met was that I failed to realize the bluetooth adapter is connected to the laptop through the USB interface. I could not turn on/off the bluetooth LED using Fn-F5 nor by enabling it through /proc/acpi/ibm/bluetooth. After loading USB modules it worked as a charm:

:modprobe uhci_hcd ; modprobe ehci_hcd

In the kernel configuration, I turned most of the bluetooth stuff to <M>; it can be found in the Networking section of the linux configuration. However, I found out that "RFCOMM protocols support" and "RFCOMM TTY support" (CONFIG_BT_RFCOMM and CONFIG_BT_RFCOMM_TTY) has to be built into the kernel (and not as a module), and to get that right, Bluetooth (CONFIG_BT) and L2CAP (CONFIG_BT_L2CAP) also has to be configured as built-in.

I found an explaination at http://www.gentoo.org/doc/en/bluetooth-guide.xml about how to set up Bluetooth in Gentoo. I followed most of the steps, but be particularly aware of the notes above on kernel configuration.

One of the reasons for getting that bluetooth connection up was to be able to use GPRS or 3G (UMTS) for connecting my laptop to internet. I was googling a bit on it, and I was pretty surprised to learn that one should communicate with the modem using AT-commands - that's stuff we did in the previous millenium, causing our modems to make lots of fancy sounds. By configuring /etc/bluetooth/rfcomm.conf correctly, I got a device /dev/rfcomm0 - eventually one could use the command:

:rfcomm bind 0 00:15:A0:7A:90:F2 3

Where the HW address should be replaced with that of your phone - if you don't know the hardware address of your phone yet, you can find it running:
:hcitool scan
and '3' is the channel to use. I spent quite some time fighting before I found out of that one; I didn't find it documented anywhere, but by running
:sdptool records 00:15:A0:7A:90:F2
I found channel 3 to be the right one for my phone. Some guides suggested "1" as value without any explaination. By experimenting, I managed more or less to crash the bluetooth stack on the cellphone so it had to be rebooted.

Now that /dev/rfcomm0 exists, one can try to access it i.e. by using minicom:
:minicom -s
set the serial device to be '/dev/rfcomm0', chose 'exit' and then the AT-commands can be typed in. With my operator (Telenor, Norway) it seemed simple enough, I just entered
:ATDT *99#
and lots of cryptic letters started dancing across the screen, indicating a ppp session startup.

Then, to run pppd - I created /etc/ppp/peers/nokia with particularly those lines:
:/dev/rfcomm0
:connect '/usr/sbin/chat -v -f /etc/ppp/chat-nokia'
:debug
:10.0.1.3
:crtscts
:noipdefault
:ipcp-accept-local
:defaultroute
:novj
:nobsdcomp
:novjccomp
:nopcomp
:noaccomp
:usepeerdns

and a simple /etc/ppp/chat-nokia
:'TIMEOUT' '5'
:'ABORT' 'BUSY'
:'ABORT' 'ERROR'
:'ABORT' 'NO ANSWER'
:'ABORT' 'NO CARRIER'
:'ABORT' 'NO DIALTONE'
:'ABORT' 'Invalid Login'
:'ABORT' 'Login incorrect'
:'' 'ATZ'
:'OK' 'ATDT*99#'
:'~--' ''

and then I entered
:pppd call nokia
and I got Internet.

For doing anything else, I think gammu is the best option, though I didn't get it to communicate with my phone yet.

http://gagravarr.org/series-60/

http://www.polycon.fi/~laa/biblo/linux_gprs.html

How to setup Bluetooth

2005-12-04T07:16:59Z

Tobixen:

This is a subjective story about my experiences connecting a Thinkpad T43 running Gentoo and a Nokia N70 using Bluetooth, but I suppose most of the stuff here is generic stuff about how to connect laptops with linux with cellphones using bluetooth.

The kernel used was 2.6.14-gentoo, patched up to get the SATA working after suspend-to-memory.

First of all, installation of Bluez; the following gentoo ebuilds was installed:

:net-wireless/bluez-bluefw
:net-wireless/bluez-firmware
:net-wireless/bluez-hcidump
:net-wireless/bluez-hciemu
:net-wireless/bluez-libs
:net-wireless/bluez-utils

net-wireless/bluez-kernel was also installed, but later I read it should not be needed when running 2.6-kernel - it could even be harmful.

The first blocker I met was that I failed to realize the bluetooth adapter is connected to the laptop through the USB interface. I could not turn on/off the bluetooth LED using Fn-F5 nor by enabling it through /proc/acpi/ibm/bluetooth. After loading USB modules it worked as a charm:

:modprobe uhci_hcd ; modprobe ehci_hcd

In the kernel configuration, I turned most of the bluetooth stuff to <M>; it can be found in the Networking section of the linux configuration. However, I found out that "RFCOMM protocols support" and "RFCOMM TTY support" (CONFIG_BT_RFCOMM and CONFIG_BT_RFCOMM_TTY) has to be built into the kernel (and not as a module), and to get that right, Bluetooth (CONFIG_BT) and L2CAP (CONFIG_BT_L2CAP) also has to be configured as built-in.

I found an explaination at http://www.gentoo.org/doc/en/bluetooth-guide.xml about how to set up Bluetooth in Gentoo. I followed most of the steps, but be particularly aware of the notes above on kernel configuration.

One of the reasons for getting that bluetooth connection up was to be able to use GPRS or 3G (UMTS) for connecting my laptop to internet. I was googling a bit on it, and I was pretty surprised to learn that one should communicate with the modem using AT-commands - that's stuff we did in the previous millenium, causing our modems to make lots of fancy sounds. By configuring /etc/bluetooth/rfcomm.conf correctly, I got a device /dev/rfcomm0 - eventually one could use the command:

:rfcomm bind 0 00:15:A0:7A:90:F2 3

Where the HW address should be replaced with that of your phone - if you don't know the hardware address of your phone yet, you can find it running:
:hcitool scan
and '3' is the channel to use. I spent quite some time fighting before I found out of that one; I didn't find it documented anywhere, but by running
:sdptool records 00:15:A0:7A:90:F2
I found channel 3 to be the right one.

Now that /dev/rfcomm0 exists, one can try to access it i.e. by using minicom:
:minicom -s
set the serial device to be '/dev/rfcomm0', chose 'exit' and then the AT-commands can be typed in. With my operator (Telenor, Norway) it seemed simple enough, I just entered
:ATDT *99#
and lots of cryptic letters started dancing across the screen, indicating a ppp session startup.

Then, to run pppd - I created /etc/ppp/peers/nokia with particularly those lines:
:/dev/rfcomm0
:connect '/usr/sbin/chat -v -f /etc/ppp/chat-nokia'
:debug
:10.0.1.3
:crtscts
:noipdefault
:ipcp-accept-local
:defaultroute
:novj
:nobsdcomp
:novjccomp
:nopcomp
:noaccomp
:usepeerdns

and a simple /etc/ppp/chat-nokia
:'TIMEOUT' '5'
:'ABORT' 'BUSY'
:'ABORT' 'ERROR'
:'ABORT' 'NO ANSWER'
:'ABORT' 'NO CARRIER'
:'ABORT' 'NO DIALTONE'
:'ABORT' 'Invalid Login'
:'ABORT' 'Login incorrect'
:'' 'ATZ'
:'OK' 'ATDT*99#'
:'~--' ''

and then I entered
:pppd call nokia
and I got Internet.

For doing anything else, I think gammu is the best option, though I didn't get it to communicate with my phone yet.

http://gagravarr.org/series-60/

http://www.polycon.fi/~laa/biblo/linux_gprs.html

How to setup Bluetooth

2005-12-04T07:15:33Z

Tobixen: Initial edition, needs lots of fixups

This is a subjective story about my experiences connecting a Thinkpad T43 running Gentoo and a Nokia N70 using Bluetooth, but I suppose most of the stuff here is generic stuff about how to connect laptops with linux with cellphones using bluetooth.

The kernel used was 2.6.14-gentoo, patched up to get the SATA working after suspend-to-memory.

First of all, installation of Bluez; the following gentoo ebuilds was installed:

:net-wireless/bluez-bluefw
:net-wireless/bluez-firmware
:net-wireless/bluez-hcidump
:net-wireless/bluez-hciemu
:net-wireless/bluez-libs
:net-wireless/bluez-utils

net-wireless/bluez-kernel was also installed, but later I read it should not be needed when running 2.6-kernel - it could even be harmful.

The first blocker I met was that I failed to realize the bluetooth adapter is connected to the laptop through the USB interface. I could not turn on/off the bluetooth LED using Fn-F5 nor by enabling it through /proc/acpi/ibm/bluetooth. After loading USB modules it worked as a charm:

:modprobe uhci_hcd ; modprobe ehci_hcd

In the kernel configuration, I turned most of the bluetooth stuff to <M>; it can be found in the Networking section of the linux configuration. However, I found out that "RFCOMM protocols support" and "RFCOMM TTY support" (CONFIG_BT_RFCOMM and CONFIG_BT_RFCOMM_TTY) has to be built into the kernel (and not as a module), and to get that right, Bluetooth (CONFIG_BT) and L2CAP (CONFIG_BT_L2CAP) also has to be configured as built-in.

I found an explaination at http://www.gentoo.org/doc/en/bluetooth-guide.xml about how to set up Bluetooth in Gentoo. I followed most of the steps, but be particularly aware of the notes above on kernel configuration.

One of the reasons for getting that bluetooth connection up was to be able to use GPRS or 3G (UMTS) for connecting my laptop to internet. I was googling a bit on it, and I was pretty surprised to learn that one should communicate with the modem using AT-commands - that's stuff we did in the previous millenium, causing our modems to make lots of fancy sounds. By configuring /etc/bluetooth/rfcomm.conf correctly, I got a device /dev/rfcomm0 - eventually one could use the command:

:rfcomm bind 0 00:15:A0:7A:90:F2 3

Where the HW address should be replaced with that of your phone - if you don't know the hardware address of your phone yet, you can find it running:
:hcitool scan
and '3' is the channel to use. I spent quite some time fighting before I found out of that one; I didn't find it documented anywhere, but by running
:sdptool records 00:15:A0:7A:90:F2
I found channel 3 to be the right one.

Now that /dev/rfcomm0 exists, one can try to access it i.e. by using minicom:
:minicom -s
set the serial device to be '/dev/rfcomm0', chose 'exit' and then the AT-commands can be typed in. With my operator (Telenor, Norway) it seemed simple enough, I just entered
:ATDT *99#
and lots of cryptic letters started dancing across the screen, indicating a ppp session startup.

Then, to run pppd - I created /etc/ppp/peers/nokia with particularly those lines:
:/dev/rfcomm0
:connect '/usr/sbin/chat -v -f /etc/ppp/chat-nokia'
:debug
:10.0.1.3
:crtscts
:noipdefault
:ipcp-accept-local
:defaultroute
:novj
:nobsdcomp
:novjccomp
:nopcomp
:noaccomp
:usepeerdns

and a simple /etc/ppp/chat-nokia
'TIMEOUT' '5'
'ABORT' 'BUSY'
'ABORT' 'ERROR'
'ABORT' 'NO ANSWER'
'ABORT' 'NO CARRIER'
'ABORT' 'NO DIALTONE'
'ABORT' 'Invalid Login'
'ABORT' 'Login incorrect'
'' 'ATZ'
'OK' 'ATDT*99#'
'~--' ''

and then I entered
:pppd call nokia
and I got Internet.

For doing anything else, I think gammu is the best option, though I didn't get it to communicate with my phone yet.

http://gagravarr.org/series-60/
http://www.polycon.fi/~laa/biblo/linux_gprs.html