linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: rtl8192cu: testing with EdiMax USB
Date: Fri, 13 Sep 2013 10:29:20 +0100	[thread overview]
Message-ID: <5232DAF0.6040907@ilande.co.uk> (raw)

Hi all,

So talking to some colleagues at work, I managed to find someone else 
who uses the EdiMax USB dongle and persuaded them to lend it to me for 
the weekend in order to see whether it could be related to a hardware 
difference with my OEM dongle.

I've just tested with the EdiMax USB dongle which reports as "Bus 004 
Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n 
Wireless Adapter [Realtek RTL8188CUS]" in lsusb, which I believe is 
exactly the same hardware that Larry is using. And again I still see the 
problem with disassociation.

I spent a bit more time tinkering further with debug=0x5, forgetting 
that I had left your last diagnostic patch applied. Based upon when the 
beacon output disappears in the logs (after updating the power 
registers), it does seem likely that is a power-related problem.

The two power-related messages that stand out to me are:

1) Repeated output of "pHalData->bHwRadioOff and eRfPowerStateToSet do 
not match: pHalData->bHwRadioOff 0, eRfPowerStateToSet 0" messages

2) rtl92c_dm_txpower_tracking_callback_thermalmeter() seems to be called 
X seconds before the "AP off for X seconds" messages

Larry - I've sent you the complete debug off-list from the EdiMax, so it 
should be a like-for-like comparison with your setup. Hopefully 
comparing with your output will help you work out exactly what the 
problem is.


ATB,

Mark.

             reply	other threads:[~2013-09-13  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13  9:29 Mark Cave-Ayland [this message]
2013-09-13 13:01 ` rtl8192cu: testing with EdiMax USB Mark Cave-Ayland
2013-09-13 13:27   ` Mark Cave-Ayland
2013-09-13 18:00     ` Larry Finger
2013-09-13 18:20       ` Mark Cave-Ayland

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=5232DAF0.6040907@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=Larry.Finger@lwfinger.net \
    --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).