From: Matthias-Christian Ott <ott@mirix.org>
To: Andy Lutomirski <luto@mit.edu>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: iwlagn on Thinkpad X200
Date: Mon, 15 Feb 2010 15:31:38 +0100 [thread overview]
Message-ID: <20100215143137.GA4789@qi> (raw)
In-Reply-To: <4B79538F.4090501@mit.edu>
On Mon, Feb 15, 2010 at 09:00:47AM -0500, Andy Lutomirski wrote:
> Looks mostly reasonable to me. Did you try 'iwconfig wlan0 power on'?
Yes, it didn't make an improvement.
> If you're feeling adventurous, try iwlcore.no_sleep_autoadjust=0 and
> 'iwconfig wlan0 power on'. The combination works for me and
> decreases power consumption a lot at the cost of a little bit of
> latency.
It worked for me too, even if it just saved about 6 wake-ups per
second.
But I still wonder where the other parameters most users report about
have gone.
> --Andy
Regards,
Matthias-Christian
next prev parent reply other threads:[~2010-02-15 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 13:48 iwlagn on Thinkpad X200 Matthias-Christian Ott
2010-02-15 14:00 ` Andy Lutomirski
2010-02-15 14:31 ` Matthias-Christian Ott [this message]
2010-02-15 14:55 ` Andrew Lutomirski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100215143137.GA4789@qi \
--to=ott@mirix.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=luto@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox