From: jeremy lansman <jeremy.lansman@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Channel Estimation Question
Date: Fri, 24 Oct 2014 21:05:29 +0200 [thread overview]
Message-ID: <544AA2F9.6050806@gmail.com> (raw)
Hi.
I beg your pardon for asking a newbe question...but..here goes anyway.
My problem is with an Intel Advanced 6230. I have noted over the year +
I have used it under Ubuntu that it seems to have a problem when I move
the laptop. This is consistent with a channel estimation (tap
equalizer) issue under COFDM modulation.
No, I do not know about wi-fi, and I do not relish digging into driver
stuff. But I do know digital RF in general.
If it is going to take more hoursout of my life , maybe I should buy an
external wi-fi for the lap top and put up with the resultant klutz.
This is ping to my AP after I move about:
64 bytes from 10.5.50.1: icmp_seq=509 ttl=64 time=1057 ms
64 bytes from 10.5.50.1: icmp_seq=510 ttl=64 time=5382 ms
64 bytes from 10.5.50.1: icmp_seq=511 ttl=64 time=4386 ms
64 bytes from 10.5.50.1: icmp_seq=512 ttl=64 time=3383 ms
64 bytes from 10.5.50.1: icmp_seq=513 ttl=64 time=2376 ms
64 bytes from 10.5.50.1: icmp_seq=514 ttl=64 time=1438 ms
64 bytes from 10.5.50.1: icmp_seq=515 ttl=64 time=433 ms
64 bytes from 10.5.50.1: icmp_seq=516 ttl=64 time=823 ms
64 bytes from 10.5.50.1: icmp_seq=517 ttl=64 time=1533 ms
This is if I sit still a while:
64 bytes from 10.5.50.1: icmp_seq=583 ttl=64 time=1.18 ms
64 bytes from 10.5.50.1: icmp_seq=584 ttl=64 time=1.79 ms
64 bytes from 10.5.50.1: icmp_seq=585 ttl=64 time=0.871 ms
64 bytes from 10.5.50.1: icmp_seq=586 ttl=64 time=2.96 ms
64 bytes from 10.5.50.1: icmp_seq=587 ttl=64 time=1.28 ms
64 bytes from 10.5.50.1: icmp_seq=588 ttl=64 time=1.57 ms
64 bytes from 10.5.50.1: icmp_seq=589 ttl=64 time=1.03 ms
WIFI worked after I installed Unbuntu Trusty, but an update seems to
have broken it, sending performance back to what it was under 12.04.
So.. do you think it might be a simple fix related to channel estimation?
Thank you.
--
Jeremy Lansman
New York City USA, +1 347 696 0120
Western Cape RSA, +27 21 300 2105
Anchorage AK USA,+1 907 339 3800
Skype Lansmankyes
Fax 27862460713
next reply other threads:[~2014-10-24 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 19:05 jeremy lansman [this message]
2014-10-25 16:10 ` Channel Estimation Question Emmanuel Grumbach
2014-10-29 11:11 ` jeremy lansman
2014-10-29 11:58 ` Emmanuel Grumbach
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=544AA2F9.6050806@gmail.com \
--to=jeremy.lansman@gmail.com \
--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).