ThinkWiki - User contributions [en]

Talk:Problem with high pitch noises

2006-06-16T07:58:49Z

Squashball:

==Discussion of "Limit ACPI CPU power states"==

*Stefan Baums: I raised this issue on the linux-kernel mailing list, and from there it was forwarded to the acpi-devel mailing list. See the discussion [http://sourceforge.net/mailarchive/forum.php?thread_id=7593600&forum_id=6102 here] and [http://sourceforge.net/mailarchive/forum.php?thread_id=7599419&forum_id=6102 here]. Results: The <code>idle=halt</code> kernel parameter disables ACPI C-state switching entirely (i.e., locks the processor in C1). It is preferable to pass to the ACPI processor component the option {{bootparm|max_cstate|2}}, which only disables the problematic states C3 and C4. The only way to accomplish this that worked for me was to compile the ACPI processor component permanently into the kernel (<tt>CONFIG_ACPI_PROCESSOR=y</tt>) and then enable it by adding the parameter {{bootparm|processor.max_cstate|2}} to the boot command line (and of course removing {{bootparm|idle|halt}}). Now the computer switches back and forth between C1 and C2, but avoids the noise-inducing C3 and C4, and frequency scaling works regardless. [Update: I now use the default Ubuntu kernel, with <code>processor</code> as a module, and disabled C3 and C4 by modifying {{path|/etc/init.d/acpid}} as explained on the article page.] ({{X41}})
*Simon Eggert: The {{bootparm|processor.max_cstate|3}} option worked for me on my {{T43p}} thanks.
* Adding <code>options processor max_cstate=2</code> in {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}} on my SuSE 9.3 installation) prevents the CPU permanently from entering into C3 and higher states. ({{X40}}, {{R52}})
* [[User:Thinker|Thinker]]: On one {{T43}}, this worked even with {{bootparm|processor.max_cstate|3}}. That is, C3 was silent and only C4 produced whining (at both HZ=100 and HZ=250).
* [[User:Thinker|Thinker]]: These options affect power consumption when the CPU is idle. Here are the figures on one ThinkPad T43:
** {{bootparm|processor.max_cstate|4}}: 15160mW (default, noisy)
** {{bootparm|processor.max_cstate|3}}: 15770mW (660mW higher, silent)
** {{bootparm|processor.max_cstate|2}}: 16100mW (2940mW higher, silent)

* [[User:Gsmenden|gsmenden]]: On a debian system, no modprobe.conf, can use modutils to add max_cstate line. On my t43p the noise only occcurs when on battery power after suspend / resume cycle. It is definitely is still present when hard disk is spun down. Nevertheless there may be multiple sources of this (quite annoying) sound.

* [[User:Gsmenden|gsmenden]]: Update - if you don't want to use modutils, can manually load it on bootup by adding "processor max_cstate=3" in /etc/modules on a debian system. Noise still present upon resume though on my t43p though :(

* [[User:Nephiel|Nephiel]]: My {{Z60m}} also had the "screeching when on battery" problem with Ubuntu 5.10. Editing {{path|/etc/init.d/acpid}} as described worked. It needed C2: C3 was quieter but still noticeable.

* Michael Kiausch: On my {{x41}} the noise disappears on unloading uhci-hcd module (no matter which c-state), unfortunately this is not an option as this disables usb. ''edit:'' only works if HZ=100

* Just tested M. Kiausch's suggestion on a {{t43}}. The high-pitch noise is gone (HZ=100, cstate=4), but there is a low-pitch noise with about the same "beat". It is much less audible though, and I really had to keep an ear close to the exhaust to hear it. But the noise is still there.

* Michael Kiausch: You're right, same low-pitch-noise on {{x41}}, but it is really hard to hear. Does anyone know in which way the usb-uhci is related to the c-states?

* [[User:Slurm|Slurm]] The high-pitch noise occurs on my x41 only if i'm on battery and my mouse(usb, optical) is plugged in.

* Martin Aumueller: Upgrading the BIOS on my X60s from 1.04 to 1.06 solved the noise problem for me, however it seems to draw about 500 mW more power with the newer BIOS.

== Harddisk related noise ==

on my T43p the noise definitely comes from the harddisk and can be heard both in Windows and Linux. Only at boot time, before the harddisk spins up, or when I manually spin down the harddisk with

{{cmdroot|hdparm -y /dev/sda}}

the system is silent.

Hi, I don't have an IBM but Dell Latitude D410 laptop. My problem is that not only the high pitch noise is produced but the processor itself comes very busy when speedstep-centrino module is loaded. On karamba monitor (not very reliable but I can feel the difference) I get 50-100% processor occupation. Right now I'm recompiling my 2.6.14 kernel to 100Hz timer freq. (was 250) and we'll see what happens.

If you have any suggestions don't hestite since I practically can't use speedsteping because battery discharges rapidly

Cheers
Wojtek

== Noise from Wlan ==
Hi, I have a high frequency noise from my wifi modul: It occurs only with linux, only in battery mode. Disabling wifi via hardware switch disables the noise! 
Any Ideas? 
Florian 
EDIT: Giving the cpus something to calc disables the noise, too! 
EDIT2: "Turn off CPU power saving in in BIOS" seems (!!) to solve the problem! But where is the connection to the wlan?

== Noise from Fan ==
http://forum.thinkpads.com/viewtopic.php?p=171683

Talk:Problems with SATA and Linux

2006-06-13T06:17:52Z

Squashball: /* DVD DMA with ide/sata as module */

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

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

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

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

Talk:Problems with SATA and Linux

2006-06-13T06:11:02Z

Squashball: /* DVD DMA with ide/sata as module */

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

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

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

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

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

Talk:Problems with SATA and Linux

2006-06-12T10:38:46Z

Squashball: /* DVD DMA with ide/sata as module */

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

== updated libata_passthru.patch ==

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

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

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

Hi

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

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

Thanks.

----

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

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

== ATA_ENABLE_PATA PCI IDs ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hi

Can anyone tell me how those modules are called?

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

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

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

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

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

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

Talk:Problems with SATA and Linux

2006-06-11T07:17:45Z

Squashball: /* DVD DMA with ide/sata as module */

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

== updated libata_passthru.patch ==

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

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

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

Hi

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

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

Thanks.

----

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

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

== ATA_ENABLE_PATA PCI IDs ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hi

Can anyone tell me how those modules are called?

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

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

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

Where the hell do I find the libata module?

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

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

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

Talk:Problems with SATA and Linux

2006-06-11T07:16:13Z

Squashball: /* occasional hang upon resume with various kernels */

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

== updated libata_passthru.patch ==

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

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

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

Hi

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

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

Thanks.

----

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

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

== ATA_ENABLE_PATA PCI IDs ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hi

Can anyone tell me how those modules are called?

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

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

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

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

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

Talk:Problems with SATA and Linux

2006-06-11T07:15:22Z

Squashball: /* occasional hang upon resume with various kernels */

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

== updated libata_passthru.patch ==

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

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

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

Hi

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

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

Thanks.

----

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

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

== ATA_ENABLE_PATA PCI IDs ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hi

Can anyone tell me how those modules are called?

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

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

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

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

Where the hell do I find the libata module?

-- [[User:squashball|squashball]] 09:05, 11 Junr 2006 (CEST)

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

Talk:Problem with high pitch noises

2006-06-07T12:59:39Z

Squashball: /* Noise from Wlan */

==Discussion of "Limit ACPI CPU power states"==

*Stefan Baums: I raised this issue on the linux-kernel mailing list, and from there it was forwarded to the acpi-devel mailing list. See the discussion [http://sourceforge.net/mailarchive/forum.php?thread_id=7593600&forum_id=6102 here] and [http://sourceforge.net/mailarchive/forum.php?thread_id=7599419&forum_id=6102 here]. Results: The <code>idle=halt</code> kernel parameter disables ACPI C-state switching entirely (i.e., locks the processor in C1). It is preferable to pass to the ACPI processor component the option {{bootparm|max_cstate|2}}, which only disables the problematic states C3 and C4. The only way to accomplish this that worked for me was to compile the ACPI processor component permanently into the kernel (<tt>CONFIG_ACPI_PROCESSOR=y</tt>) and then enable it by adding the parameter {{bootparm|processor.max_cstate|2}} to the boot command line (and of course removing {{bootparm|idle|halt}}). Now the computer switches back and forth between C1 and C2, but avoids the noise-inducing C3 and C4, and frequency scaling works regardless. [Update: I now use the default Ubuntu kernel, with <code>processor</code> as a module, and disabled C3 and C4 by modifying {{path|/etc/init.d/acpid}} as explained on the article page.] ({{X41}})
*Simon Eggert: The {{bootparm|processor.max_cstate|3}} option worked for me on my {{T43p}} thanks.
* Adding <code>options processor max_cstate=2</code> in {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}} on my SuSE 9.3 installation) prevents the CPU permanently from entering into C3 and higher states. ({{X40}}, {{R52}})
* [[User:Thinker|Thinker]]: On one {{T43}}, this worked even with {{bootparm|processor.max_cstate|3}}. That is, C3 was silent and only C4 produced whining (at both HZ=100 and HZ=250).
* [[User:Thinker|Thinker]]: These options affect power consumption when the CPU is idle. Here are the figures on one ThinkPad T43:
** {{bootparm|processor.max_cstate|4}}: 15160mW (default, noisy)
** {{bootparm|processor.max_cstate|3}}: 15770mW (660mW higher, silent)
** {{bootparm|processor.max_cstate|2}}: 16100mW (2940mW higher, silent)

* [[User:Gsmenden|gsmenden]]: On a debian system, no modprobe.conf, can use modutils to add max_cstate line. On my t43p the noise only occcurs when on battery power after suspend / resume cycle. It is definitely is still present when hard disk is spun down. Nevertheless there may be multiple sources of this (quite annoying) sound.

* [[User:Gsmenden|gsmenden]]: Update - if you don't want to use modutils, can manually load it on bootup by adding "processor max_cstate=3" in /etc/modules on a debian system. Noise still present upon resume though on my t43p though :(

* [[User:Nephiel|Nephiel]]: My {{Z60m}} also had the "screeching when on battery" problem with Ubuntu 5.10. Editing {{path|/etc/init.d/acpid}} as described worked. It needed C2: C3 was quieter but still noticeable.

* Michael Kiausch: On my {{x41}} the noise disappears on unloading uhci-hcd module (no matter which c-state), unfortunately this is not an option as this disables usb. ''edit:'' only works if HZ=100

* Just tested M. Kiausch's suggestion on a {{t43}}. The high-pitch noise is gone (HZ=100, cstate=4), but there is a low-pitch noise with about the same "beat". It is much less audible though, and I really had to keep an ear close to the exhaust to hear it. But the noise is still there.

* Michael Kiausch: You're right, same low-pitch-noise on {{x41}}, but it is really hard to hear. Does anyone know in which way the usb-uhci is related to the c-states?

* [[User:Slurm|Slurm]] The high-pitch noise occurs on my x41 only if i'm on battery and my mouse(usb, optical) is plugged in.

== Harddisk related noise ==

on my T43p the noise definitely comes from the harddisk and can be heard both in Windows and Linux. Only at boot time, before the harddisk spins up, or when I manually spin down the harddisk with

{{cmdroot|hdparm -y /dev/sda}}

the system is silent.

Hi, I don't have an IBM but Dell Latitude D410 laptop. My problem is that not only the high pitch noise is produced but the processor itself comes very busy when speedstep-centrino module is loaded. On karamba monitor (not very reliable but I can feel the difference) I get 50-100% processor occupation. Right now I'm recompiling my 2.6.14 kernel to 100Hz timer freq. (was 250) and we'll see what happens.

If you have any suggestions don't hestite since I practically can't use speedsteping because battery discharges rapidly

Cheers
Wojtek

== Noise from Wlan ==
Hi, I have a high frequency noise from my wifi modul: It occurs only with linux, only in battery mode. Disabling wifi via hardware switch disables the noise! 
Any Ideas? 
Florian 
EDIT: Giving the cpus something to calc disables the noise, too! 
EDIT2: "Turn off CPU power saving in in BIOS" seems (!!) to solve the problem! But where is the connection to the wlan?

Talk:Problem with high pitch noises

2006-06-07T12:47:28Z

Squashball: /* Noise from Wlan */

==Discussion of "Limit ACPI CPU power states"==

*Stefan Baums: I raised this issue on the linux-kernel mailing list, and from there it was forwarded to the acpi-devel mailing list. See the discussion [http://sourceforge.net/mailarchive/forum.php?thread_id=7593600&forum_id=6102 here] and [http://sourceforge.net/mailarchive/forum.php?thread_id=7599419&forum_id=6102 here]. Results: The <code>idle=halt</code> kernel parameter disables ACPI C-state switching entirely (i.e., locks the processor in C1). It is preferable to pass to the ACPI processor component the option {{bootparm|max_cstate|2}}, which only disables the problematic states C3 and C4. The only way to accomplish this that worked for me was to compile the ACPI processor component permanently into the kernel (<tt>CONFIG_ACPI_PROCESSOR=y</tt>) and then enable it by adding the parameter {{bootparm|processor.max_cstate|2}} to the boot command line (and of course removing {{bootparm|idle|halt}}). Now the computer switches back and forth between C1 and C2, but avoids the noise-inducing C3 and C4, and frequency scaling works regardless. [Update: I now use the default Ubuntu kernel, with <code>processor</code> as a module, and disabled C3 and C4 by modifying {{path|/etc/init.d/acpid}} as explained on the article page.] ({{X41}})
*Simon Eggert: The {{bootparm|processor.max_cstate|3}} option worked for me on my {{T43p}} thanks.
* Adding <code>options processor max_cstate=2</code> in {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}} on my SuSE 9.3 installation) prevents the CPU permanently from entering into C3 and higher states. ({{X40}}, {{R52}})
* [[User:Thinker|Thinker]]: On one {{T43}}, this worked even with {{bootparm|processor.max_cstate|3}}. That is, C3 was silent and only C4 produced whining (at both HZ=100 and HZ=250).
* [[User:Thinker|Thinker]]: These options affect power consumption when the CPU is idle. Here are the figures on one ThinkPad T43:
** {{bootparm|processor.max_cstate|4}}: 15160mW (default, noisy)
** {{bootparm|processor.max_cstate|3}}: 15770mW (660mW higher, silent)
** {{bootparm|processor.max_cstate|2}}: 16100mW (2940mW higher, silent)

* [[User:Gsmenden|gsmenden]]: On a debian system, no modprobe.conf, can use modutils to add max_cstate line. On my t43p the noise only occcurs when on battery power after suspend / resume cycle. It is definitely is still present when hard disk is spun down. Nevertheless there may be multiple sources of this (quite annoying) sound.

* [[User:Gsmenden|gsmenden]]: Update - if you don't want to use modutils, can manually load it on bootup by adding "processor max_cstate=3" in /etc/modules on a debian system. Noise still present upon resume though on my t43p though :(

* [[User:Nephiel|Nephiel]]: My {{Z60m}} also had the "screeching when on battery" problem with Ubuntu 5.10. Editing {{path|/etc/init.d/acpid}} as described worked. It needed C2: C3 was quieter but still noticeable.

* Michael Kiausch: On my {{x41}} the noise disappears on unloading uhci-hcd module (no matter which c-state), unfortunately this is not an option as this disables usb. ''edit:'' only works if HZ=100

* Just tested M. Kiausch's suggestion on a {{t43}}. The high-pitch noise is gone (HZ=100, cstate=4), but there is a low-pitch noise with about the same "beat". It is much less audible though, and I really had to keep an ear close to the exhaust to hear it. But the noise is still there.

* Michael Kiausch: You're right, same low-pitch-noise on {{x41}}, but it is really hard to hear. Does anyone know in which way the usb-uhci is related to the c-states?

* [[User:Slurm|Slurm]] The high-pitch noise occurs on my x41 only if i'm on battery and my mouse(usb, optical) is plugged in.

== Harddisk related noise ==

on my T43p the noise definitely comes from the harddisk and can be heard both in Windows and Linux. Only at boot time, before the harddisk spins up, or when I manually spin down the harddisk with

{{cmdroot|hdparm -y /dev/sda}}

the system is silent.

Hi, I don't have an IBM but Dell Latitude D410 laptop. My problem is that not only the high pitch noise is produced but the processor itself comes very busy when speedstep-centrino module is loaded. On karamba monitor (not very reliable but I can feel the difference) I get 50-100% processor occupation. Right now I'm recompiling my 2.6.14 kernel to 100Hz timer freq. (was 250) and we'll see what happens.

If you have any suggestions don't hestite since I practically can't use speedsteping because battery discharges rapidly

Cheers
Wojtek

== Noise from Wlan ==
Hi, I have a high frequency noise from my wifi modul: It occurs only with linux, only in battery mode. Disabling wifi via hardware switch disables the noise!
Any Ideas?
Florian
EDIT: Giving the cpus something to calc disables the noise, too!
EDIT2: "Turn off CPU power saving in in BIOS" seems (!!) to solve the problem! But where is the connection to the wlan?

Talk:Problem with high pitch noises

2006-06-07T12:28:02Z

Squashball: /* Noise from Wlan */

==Discussion of "Limit ACPI CPU power states"==

*Stefan Baums: I raised this issue on the linux-kernel mailing list, and from there it was forwarded to the acpi-devel mailing list. See the discussion [http://sourceforge.net/mailarchive/forum.php?thread_id=7593600&forum_id=6102 here] and [http://sourceforge.net/mailarchive/forum.php?thread_id=7599419&forum_id=6102 here]. Results: The <code>idle=halt</code> kernel parameter disables ACPI C-state switching entirely (i.e., locks the processor in C1). It is preferable to pass to the ACPI processor component the option {{bootparm|max_cstate|2}}, which only disables the problematic states C3 and C4. The only way to accomplish this that worked for me was to compile the ACPI processor component permanently into the kernel (<tt>CONFIG_ACPI_PROCESSOR=y</tt>) and then enable it by adding the parameter {{bootparm|processor.max_cstate|2}} to the boot command line (and of course removing {{bootparm|idle|halt}}). Now the computer switches back and forth between C1 and C2, but avoids the noise-inducing C3 and C4, and frequency scaling works regardless. [Update: I now use the default Ubuntu kernel, with <code>processor</code> as a module, and disabled C3 and C4 by modifying {{path|/etc/init.d/acpid}} as explained on the article page.] ({{X41}})
*Simon Eggert: The {{bootparm|processor.max_cstate|3}} option worked for me on my {{T43p}} thanks.
* Adding <code>options processor max_cstate=2</code> in {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}} on my SuSE 9.3 installation) prevents the CPU permanently from entering into C3 and higher states. ({{X40}}, {{R52}})
* [[User:Thinker|Thinker]]: On one {{T43}}, this worked even with {{bootparm|processor.max_cstate|3}}. That is, C3 was silent and only C4 produced whining (at both HZ=100 and HZ=250).
* [[User:Thinker|Thinker]]: These options affect power consumption when the CPU is idle. Here are the figures on one ThinkPad T43:
** {{bootparm|processor.max_cstate|4}}: 15160mW (default, noisy)
** {{bootparm|processor.max_cstate|3}}: 15770mW (660mW higher, silent)
** {{bootparm|processor.max_cstate|2}}: 16100mW (2940mW higher, silent)

* [[User:Gsmenden|gsmenden]]: On a debian system, no modprobe.conf, can use modutils to add max_cstate line. On my t43p the noise only occcurs when on battery power after suspend / resume cycle. It is definitely is still present when hard disk is spun down. Nevertheless there may be multiple sources of this (quite annoying) sound.

* [[User:Gsmenden|gsmenden]]: Update - if you don't want to use modutils, can manually load it on bootup by adding "processor max_cstate=3" in /etc/modules on a debian system. Noise still present upon resume though on my t43p though :(

* [[User:Nephiel|Nephiel]]: My {{Z60m}} also had the "screeching when on battery" problem with Ubuntu 5.10. Editing {{path|/etc/init.d/acpid}} as described worked. It needed C2: C3 was quieter but still noticeable.

* Michael Kiausch: On my {{x41}} the noise disappears on unloading uhci-hcd module (no matter which c-state), unfortunately this is not an option as this disables usb. ''edit:'' only works if HZ=100

* Just tested M. Kiausch's suggestion on a {{t43}}. The high-pitch noise is gone (HZ=100, cstate=4), but there is a low-pitch noise with about the same "beat". It is much less audible though, and I really had to keep an ear close to the exhaust to hear it. But the noise is still there.

* Michael Kiausch: You're right, same low-pitch-noise on {{x41}}, but it is really hard to hear. Does anyone know in which way the usb-uhci is related to the c-states?

* [[User:Slurm|Slurm]] The high-pitch noise occurs on my x41 only if i'm on battery and my mouse(usb, optical) is plugged in.

== Harddisk related noise ==

on my T43p the noise definitely comes from the harddisk and can be heard both in Windows and Linux. Only at boot time, before the harddisk spins up, or when I manually spin down the harddisk with

{{cmdroot|hdparm -y /dev/sda}}

the system is silent.

Hi, I don't have an IBM but Dell Latitude D410 laptop. My problem is that not only the high pitch noise is produced but the processor itself comes very busy when speedstep-centrino module is loaded. On karamba monitor (not very reliable but I can feel the difference) I get 50-100% processor occupation. Right now I'm recompiling my 2.6.14 kernel to 100Hz timer freq. (was 250) and we'll see what happens.

If you have any suggestions don't hestite since I practically can't use speedsteping because battery discharges rapidly

Cheers
Wojtek

== Noise from Wlan ==
Hi, I have a high frequency noise from my wifi modul: It occurs only with linux, only in battery mode. Disabling wifi via hardware switch disables the noise!
Any Ideas?
Florian
EDIT: Giving the cpus something to calc disables the noise, too!

Talk:Problem with high pitch noises

2006-06-07T12:16:44Z

Squashball:

==Discussion of "Limit ACPI CPU power states"==

*Stefan Baums: I raised this issue on the linux-kernel mailing list, and from there it was forwarded to the acpi-devel mailing list. See the discussion [http://sourceforge.net/mailarchive/forum.php?thread_id=7593600&forum_id=6102 here] and [http://sourceforge.net/mailarchive/forum.php?thread_id=7599419&forum_id=6102 here]. Results: The <code>idle=halt</code> kernel parameter disables ACPI C-state switching entirely (i.e., locks the processor in C1). It is preferable to pass to the ACPI processor component the option {{bootparm|max_cstate|2}}, which only disables the problematic states C3 and C4. The only way to accomplish this that worked for me was to compile the ACPI processor component permanently into the kernel (<tt>CONFIG_ACPI_PROCESSOR=y</tt>) and then enable it by adding the parameter {{bootparm|processor.max_cstate|2}} to the boot command line (and of course removing {{bootparm|idle|halt}}). Now the computer switches back and forth between C1 and C2, but avoids the noise-inducing C3 and C4, and frequency scaling works regardless. [Update: I now use the default Ubuntu kernel, with <code>processor</code> as a module, and disabled C3 and C4 by modifying {{path|/etc/init.d/acpid}} as explained on the article page.] ({{X41}})
*Simon Eggert: The {{bootparm|processor.max_cstate|3}} option worked for me on my {{T43p}} thanks.
* Adding <code>options processor max_cstate=2</code> in {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}} on my SuSE 9.3 installation) prevents the CPU permanently from entering into C3 and higher states. ({{X40}}, {{R52}})
* [[User:Thinker|Thinker]]: On one {{T43}}, this worked even with {{bootparm|processor.max_cstate|3}}. That is, C3 was silent and only C4 produced whining (at both HZ=100 and HZ=250).
* [[User:Thinker|Thinker]]: These options affect power consumption when the CPU is idle. Here are the figures on one ThinkPad T43:
** {{bootparm|processor.max_cstate|4}}: 15160mW (default, noisy)
** {{bootparm|processor.max_cstate|3}}: 15770mW (660mW higher, silent)
** {{bootparm|processor.max_cstate|2}}: 16100mW (2940mW higher, silent)

* [[User:Gsmenden|gsmenden]]: On a debian system, no modprobe.conf, can use modutils to add max_cstate line. On my t43p the noise only occcurs when on battery power after suspend / resume cycle. It is definitely is still present when hard disk is spun down. Nevertheless there may be multiple sources of this (quite annoying) sound.

* [[User:Gsmenden|gsmenden]]: Update - if you don't want to use modutils, can manually load it on bootup by adding "processor max_cstate=3" in /etc/modules on a debian system. Noise still present upon resume though on my t43p though :(

* [[User:Nephiel|Nephiel]]: My {{Z60m}} also had the "screeching when on battery" problem with Ubuntu 5.10. Editing {{path|/etc/init.d/acpid}} as described worked. It needed C2: C3 was quieter but still noticeable.

* Michael Kiausch: On my {{x41}} the noise disappears on unloading uhci-hcd module (no matter which c-state), unfortunately this is not an option as this disables usb. ''edit:'' only works if HZ=100

* Just tested M. Kiausch's suggestion on a {{t43}}. The high-pitch noise is gone (HZ=100, cstate=4), but there is a low-pitch noise with about the same "beat". It is much less audible though, and I really had to keep an ear close to the exhaust to hear it. But the noise is still there.

* Michael Kiausch: You're right, same low-pitch-noise on {{x41}}, but it is really hard to hear. Does anyone know in which way the usb-uhci is related to the c-states?

* [[User:Slurm|Slurm]] The high-pitch noise occurs on my x41 only if i'm on battery and my mouse(usb, optical) is plugged in.

== Harddisk related noise ==

on my T43p the noise definitely comes from the harddisk and can be heard both in Windows and Linux. Only at boot time, before the harddisk spins up, or when I manually spin down the harddisk with

{{cmdroot|hdparm -y /dev/sda}}

the system is silent.

Hi, I don't have an IBM but Dell Latitude D410 laptop. My problem is that not only the high pitch noise is produced but the processor itself comes very busy when speedstep-centrino module is loaded. On karamba monitor (not very reliable but I can feel the difference) I get 50-100% processor occupation. Right now I'm recompiling my 2.6.14 kernel to 100Hz timer freq. (was 250) and we'll see what happens.

If you have any suggestions don't hestite since I practically can't use speedsteping because battery discharges rapidly

Cheers
Wojtek

== Noise from Wlan ==
Hi, I have a high frequency noise from my wifi modul: It occurs only with linux, only in battery mode. Disabling wifi via hardware switch disables the noise!
Any Ideas?
Florian