From: Daniel Lublin <quite@hack.org>
To: linux-wireless@vger.kernel.org
Subject: values in /proc/net/wireless are static, doesn't change; iwlwifi, Intel 6205
Date: Thu, 11 Jun 2015 07:55:23 +0000 (UTC) [thread overview]
Message-ID: <loom.20150611T094911-428@post.gmane.org> (raw)
I'm on a thinkpad X230 with Intel Advanced-N 6205 card, iwlwifi driver.
Reading /proc/net/wireless, I find that the values there does not change. No
matter me moving around, changing distance to my AP. On my old machine (X60),
I was used to sometimes using for example wavemon(1) to find out where I get
the best reception. I this a limitation of my network card, driver, or some
combitation? As designed, or a flaw?
The values in question: Quality link/level/noise: 52. -58. -256
next reply other threads:[~2015-06-11 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 7:55 Daniel Lublin [this message]
2015-06-11 8:06 ` values in /proc/net/wireless are static, doesn't change; iwlwifi, Intel 6205 Johannes Berg
2015-06-11 8:30 ` Daniel Lublin
2015-06-11 8:39 ` Johannes Berg
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=loom.20150611T094911-428@post.gmane.org \
--to=quite@hack.org \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).