linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Moreau <thierry.moreau@connotech.com>
To: Peter Wu <peter@lekensteyn.nl>
Cc: Larry Finger <Larry.Finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: rtlwifi (rtl8192ce) consistently reports EBUSY error, but scanning works
Date: Thu, 06 Mar 2014 18:59:49 +0000	[thread overview]
Message-ID: <5318C5A5.7060604@connotech.com> (raw)
In-Reply-To: <2046728.MUZsZig9to@al>

On 03/06/14 14:54, Peter Wu wrote:
> On Wednesday 05 March 2014 19:16:08 Thierry Moreau wrote:
>> On 03/05/14 16:40, Larry Finger wrote:
>>> Please give me the exact set of commands you use to get this problem. If
>>> possible, capture the console output. As I am currently running
>>> long-term tests of the latest version of rtl8192ce using an RTL8188CE
>>> (10ec:8176), it will be a perfect time to test.
>>
>> Here is the command script, and the console log
>> (....sh 2>&1 | tee ....log)
>
> Instead of cat, I used single-second sleeps as can be seen in the attached
> script. Our logs are roughly the same (I have replaced the last three bytes of
> the MAC address by XX for privacy). The rtlwifi module is patched[1], hence
> the out-of-tree marking.
>
> What is the problem that you are experiencing?
>

Indeed a good question! Likely there is no problem. Likely a
misunderstanding from my part of the wifi logic.

I was going step by step in my integration and I (wrongly?) assumed that 
the command to set a channel in the wifi configuration was a requirement 
for my next step: scanning done on an older wifi system detected signals 
from multiple channels but the newer system scanning saw only channel 1, 
hence I assumed that the newer scanning scheme needed channel changes by 
the user space logic.

Now a number of clues (including your log below -- thanks) point towards 
the inconsequential-ness of the EBUSY result in the specific command I 
was using as a milestone.

Other clues: a) suggestion by Larry to try other tools, and b) an EBUSY 
return code in net/wireless/chan.c .

Somewhere else I might learn how scanning on multiple channels can work, 
but I no longer care for my deployment priorities.

> I am able to connect although
> it took half a minute for the first ICMP ping packets to pass (and then there
> is still a lot of packet loss). This pattern is observable on the past 2.5
> weeks that I have been running ping tests (ping every second to the gateway).
>
>> Is it possible that the Shuttle system be arranged with a digital output
>> enabling/inhibiting the Realtek wifi interface active participation in
>> wifi protocol?
>
> I didn't understand the first part, are you referring to a possible mistake in
> attaching the antennas? When I opened up the case, I saw two antennas that
> were properly secured to the card.
>

Please ignore this other hypothesis.

Thanks a lot to Larry and Peter. If you don't ear from me, please assume 
that I successfully installed hostapd and I am an happy rtlwifi user 
with the kernel 3.14.

-- Thierry Moreau

  reply	other threads:[~2014-03-06 18:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05  6:36 rtlwifi (rtl8192ce) consistently reports EBUSY error, but scanning works Thierry Moreau
2014-03-05  7:12 ` Larry Finger
2014-03-05 16:27   ` Thierry Moreau
2014-03-05 16:40     ` Larry Finger
2014-03-05 19:16       ` Thierry Moreau
2014-03-06 14:54         ` Peter Wu
2014-03-06 18:59           ` Thierry Moreau [this message]
2014-03-06 15:57         ` Larry Finger
2014-03-06 17:40           ` Dan Williams
2014-03-05 10:51 ` Peter Wu

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=5318C5A5.7060604@connotech.com \
    --to=thierry.moreau@connotech.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=peter@lekensteyn.nl \
    /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).