ThinkWiki - User contributions [en]

How to setup Bluetooth

2006-08-14T18:52:04Z

Elm:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#efefef; align:right;">
This HOWTO tells you how to install and configure Bluetooth on your Linux driven ThinkPad and how to make the most common Bluetooth applications (like connecting your mobile phone etc.) work.
</div>
|}

==BlueZ Installation==

=== Mount a mobile phone with bluetooth ===

{{NOTE|You don't need any other package except the ones described here.}}

{{NOTE|The ibm bluetooth card can works like an usb-dongle. You don't need the bcm203x module}}

For {{Gentoo}} do the following:
* First of all, we must config your kernel

:{{cmdroot|cd /usr/src/linux}}
:{{cmdroot|make menuconfig}}

:{{kernelconf|CONFIG_USB|<*>|Support for Host-side USB|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_DEVICEFS|[*]|USB device file system|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_EHCI_HCD|<*>|EHCI HCD (USB 2.0) support|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_UHCI|<*>|UHCI HCD support|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_OHCI|<*>|OHCI HCD support|USB support|Device Drivers||}}

:{{kernelconf|CONFIG_BT|<M>|Bluetooth subsystem support|Networking|||}}
:{{kernelconf|CONFIG_BT_L2CAP|<M>|L2CAP protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_RFCOMM|<M>|RFCOMM protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_RFCOMM_TTY|[*]|RFCOMM TTY support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_HCIUSB|<M>|HCI USB driver|Bluetooth device drivers|Bluetooth subsystem support|Networking|}}

:{{cmdroot|make && make modules_install}}

* Install the requiered packages
For exchange files we need the fuse filesystem. FuseFS is also implemented in the kernel, but it does not work for me.
:{{cmdroot|emerge fuse}}
:{{cmdroot|emerge bluez-libs}}
:{{cmdroot|emerge bluez-utils}}
:{{cmdroot|emerge openobex}}
:{{cmdroot|emerge obexftp}}
:{{cmdroot|emerge obexfs}}

* Modify /etc/bluetooth/hcid.conf
options {
autoinit yes"
security user
pairing multi
pin_helper /usr/bin/bluepin
}
device {
name testname
class 0x3e0100
iscan enable
pscan enable
lm accept
lp rswitch,hold,sniff,park
}

* load the modules:
:{{cmdroot|modprobe fuse}}
:{{cmdroot|modprobe bluetooth}}
:{{cmdroot|modprobe ehci-hcd}}
:{{cmdroot|modprobe uhci-hcd}}
:{{cmdroot|modprobe hci_usb}}
:{{cmdroot|modprobe l2cap}}
:{{cmdroot|modprobe rfcomm}}

* activate your bluetooth (show howto ibm-acpi for more details)
:{{cmdroot|echo enable >/proc/acpi/ibm/bluetooth}}

* start the bluetooth device:
:{{cmdroot|/etc/init.d/bluetooth start}}

* turn on bluetooth of your mobile phone (visible mode)
* get the mac-address of your phone
:{{cmdroot|hcitool scan}}

* mount your phone - don't forget to umount it when you're finished
:{{cmdroot|mkdir /mnt/phone}}
:{{cmdroot|mount -t fuse "obexfs#-b00:16:20:32:25:3C -B6" /mnt/phone}}
''use your mac-address instead of my 00:16:20:32:25:3C and don't forget the -b option in front of the mac''

finished, now you can improve this howto ;-)

Tested with ibm x41, sony ericsson k750i, nokia 6280.

----

===Building from source===
Get the source packages from [http://www.bluez.org www.bluez.org].

Build each of them with the usual steps:
:{{cmduser|./configure && make}}
:{{cmdroot|make install}}

===Gentoo ebuilds===
Under {{Gentoo}}, install the following ebuilds:
*net-wireless/bluez-bluefw
*net-wireless/bluez-firmware
*net-wireless/bluez-hcidump
*net-wireless/bluez-hciemu
*net-wireless/bluez-libs
*net-wireless/bluez-utils

{{NOTE|net-wireless/bluez-kernel is not needed, since the current version is included in your kernel.}}

===Other distributions===
You will find packages for {{Debian}}, {{Redhat}} and {{Slackware}} on the [http://www.bluez.org/packages.html packages page] of the BlueZ project.

==Enabling Bluetooth==
If Bluetooth is disabled and you have [[Ibm-acpi]] running you could enable/disable bluetooth by entering:
:{{cmdroot|echo enable > /proc/acpi/ibm/bluetooth}}
or
:{{cmdroot|echo disable > /proc/acpi/ibm/bluetooth}}

==Configuring the kernel==
Since the Bluetooth card is connected to the USB subsystem, you will need to enable USB support in your kernel:
:{{kernelconf|CONFIG_USB|<M>|Support for Host-side USB|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_DEVICEFS|[*]|USB device file system|USB support|Device Drivers||}}

Choose an appropriate USB host driver, one of:
:{{kernelconf|CONFIG_USB_EHCI_HCD|<M>|EHCI HCD (USB 2.0) support|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_UHCI|<M>|UHCI HCD support|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_OHCI|<M>|OHCI HCD support|USB support|Device Drivers||}}

Enable Bluetooth subsystem and drivers:
:{{kernelconf|CONFIG_BT|<*>|Bluetooth subsystem support|Networking|||}}
:{{kernelconf|CONFIG_BT_L2CAP|<*>|L2CAP protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_SCO|<*>|SCO links support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_RFCOMM|<*>|RFCOMM protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_RFCOMM_TTY|[*]|RFCOMM TTY support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_BNEP|<*>|BNEP protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_HID|<*>|HID protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_HCIUSB|<M>|HCI USB driver|Bluetooth device drivers|Bluetooth subsystem support|Networking|}}
:{{kernelconf|CONFIG_BT_HCIUSB_SCO|[*]|SCO (voice) support|Bluetooth device drivers|Bluetooth subsystem support|Networking|}}

Make sure that the according modules are loaded:
:{{cmdroot|modprobe uhci_hcd ; modprobe ehci_hcd ; modprobe hci_usb}}

==Serial connection over Bluetooth==
One common application is to connect your mobile phone and use it as a modem to connect to the internet via GPRS or 3G (UMTS). A lot of phones do this through using AT-commands on a serial over Bluetooth connection.

By configuring {{path|/etc/bluetooth/rfcomm.conf}} correctly, you'll get a device {{path|/dev/rfcomm0}}.

Eventually one could use the command:
:{{cmdroot|rfcomm bind 0 00:15:A0:7A:90:F2 3}}

The hardware address should be replaced with that of your phone. If you don't know the hardware address of your phone yet, you can get it by running:
:{{cmdroot|hcitool scan}}

The last parameter ('3') is the channel to use. I spent quite some time fighting before I found out of that one; I didn't find it documented anywhere, but by running
:{{cmdroot|sdptool records 00:15:A0:7A:90:F2}}
I found channel 3 to be the right one for my phone. You will have to experiment to find the right one for your phone setup; for T-Mobile GSM/GPRS carrier in USA this is channel 1.
{{NOTE|By experimenting, the bluetooth stack on the cellphone may crash. Reboot it if that happens.}}

Alternativly one could use the following to find the right channel:
:{{cmdroot|sdptool search DUN}}

Inquiring ...
Searching for DUN on 00:11:22:33:44:55 ...
Service Name: Dial-up Networking
Service RecHandle: 0x10001
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4

Now {{path|/dev/rfcomm0}} exists.

At this point you can use an automatic dialing utility such as wvdial, editing the config file to point to the modem at {{path|/dev/rfcomm0}}, and everything should work just like a land line!

{{NOTE|If you experience strange disconnects while using wvdial, disable "Carrier Check" in your wvdial configuration.}}

You may directly access the modem (i.e. by using minicom:)
:{{cmduser|minicom -s}}
set the serial device to be {{path|/dev/rfcomm0}}, choose 'exit' and then the AT-commands can be typed in.
With my operator (Telenor, Norway) it seemed simple enough, I just entered
:ATDT *99#
and lots of cryptic letters started dancing across the screen, indicating a ppp session startup.

To configure pppd create {{path|/etc/ppp/peers/nokia}} with particularly those lines:
/dev/rfcomm0
connect '/usr/sbin/chat -v -f /etc/ppp/chat-nokia'
debug
10.0.1.3
crtscts
noipdefault
ipcp-accept-local
defaultroute
novj
nobsdcomp
novjccomp
nopcomp
noaccomp
usepeerdns

Furthermore, you need a simple chat script. Create {{path|/etc/ppp/chat-nokia}}:
'TIMEOUT' '5'
'ABORT' 'BUSY'
'ABORT' 'ERROR'
'ABORT' 'NO ANSWER'
'ABORT' 'NO CARRIER'
'ABORT' 'NO DIALTONE'
'ABORT' 'Invalid Login'
'ABORT' 'Login incorrect'
'' 'ATZ'
'OK' 'ATDT*99#'
'~--' ''

Here's a script that works for Cingular's network:
TIMEOUT 35
ECHO ON
ABORT '\nBUSY\r'
ABORT '\nERROR\r'
ABORT '\nNO ANSWER\r'
ABORT '\nNO CARRIER\r'
ABORT '\nNO DIALTONE\r'
ABORT '\nRINGING\r\n\r\nRINGING\r'
'' \rAT
OK 'AT+CGDCONT=1,"IP","WAP.CINGULAR"'
OK ATD*99***1#
CONNECT ""

See more [https://help.ubuntu.com/community/BluetoothDialup#preview here]

Run pppd with:
:{{cmduser|pppd call nokia}}
This should establish the internet connection.

{{NOTE|Different network operators may require different call strings. For many carriers (including T-Mobile USA) "*99#" works without additional parameters.}}

For editing phonebook / ringtones / etc., the gammu utils (http://www.gamu.net) has been reported to work well, but this appears to be primarily for Nokia phones.

==File Transfer==
File transfers are accomplished through OBEX transfer, which I believe is basically an FTP over bluetooth connection. Once you have bonded with your phone (yes, I know you love your sexy RAZR, but here I mean paired it with your laptop via bluetooth), you can easily use "obexftp" to transfer files. As an example,

:obexftp -b 00:01:02:03:04:05 -l

will list the root directory of the phone with bluetooth address 00:01:02:03:04:05. Refer to the man page for more of the unique commands. What a wonderful interface! Unfortunately there doesn't seem to be a way to get a standard 'ftp' session using familiar commands (e.g. 'mget').

For a more user-friendly experience, you can use the kde tools, just launch
:kbtobexclient

for a file browser. In the Location: option put
:obex://[00:01:02:03:04:05]

to list the files. Note that the brackets *are* necessary. From there, you can list directories easily and batch download files.

==Troubleshooting==
If you cant get hci0 up with a /etc/init.d/bluetooth restart (or similar) then you might want to try a
:{{cmdroot|hciconfig hci0 down && hciconfig hci0 up}}
(solved the problem on a X60s (debian/testing))

==External Links==
*http://gagravarr.org/series-60/
*http://www.polycon.fi/~laa/biblo/linux_gprs.html
*[http://www.gentoo.org/doc/en/bluetooth-guide.xml Guide on how to set up Bluetooth in Gentoo]
*[http://www.linux.ie/articles/bluetoothheadset.php www.linux.ie:Linux and Bluetooth Headset howto (AKA: Fedora, BTSCO, Bluez, Jabra and Skype)]

[[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]]

Talk:Problems with SATA and Linux

2006-08-12T15:02:49Z

Elm:

__TOC__

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

-- Stefan, 10 Jan 2006

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

-- Rasto, 24 Jan 2006

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

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

----

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

----

'''Z series'''

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

----

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

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

Anybody cares to comment?

-- [[User:Micampe|Michele]]

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

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

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

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

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

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

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

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

== updated libata_passthru.patch ==

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

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

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

Hi

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

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

Thanks.

----

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

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

== ATA_ENABLE_PATA PCI IDs ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hi

Can anyone tell me how those modules are called?

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

Where the hell do I find the libata module?

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

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

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

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

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

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

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

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

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

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

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

== occasional hang upon resume with various kernels ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

----

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

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

== Problem with 2.6.16 ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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