From: Mike Turner <miketurner.forum@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: rtl8192cu beacon fix unreliable
Date: Fri, 13 Feb 2015 10:48:47 +0000 (UTC) [thread overview]
Message-ID: <loom.20150213T114021-973@post.gmane.org> (raw)
When using hostapd and an rtl8192cu Wireless USB adaptor the beacon
doesn't start sometimes. This was tested with the
kernel/git/davem/net-next.git repository
and
3423eb92315865d76cb8d488513bfef6ab9251d0
This behaviour is apparently random. If the beacon starts OK then it
continues. If a beacon isn't generated then it never starts. Repeating
cycles of hostapd stop/start may or may not generate a beacon. There are
no specific error messages displayed either on console or in syslog. I
have repeated hostapd stop/start a number of consecutive times and
received a beacon each time, however I have also done this a number of
times and never generated a beacon.
We have succesfully used the pvaret-rtl8192cu driver which is based on the
vendor driver and used that in conjunction with the modified hostapd code
that requires use of the rtl871xdrv driver interface and as far as we have
seen it always generates a beacon.
Platform is a custom designed Atmel-ARM CPU (AT91SAM9G25) with a D-Link
DWA-121.
next reply other threads:[~2015-02-13 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 10:48 Mike Turner [this message]
2015-02-18 21:27 ` rtl8192cu beacon fix unreliable Larry Finger
[not found] ` <CALA4C6XecJ+zGGfWkO51red7S-2mNoVC6vkD0ama1AGat2QOHg@mail.gmail.com>
2015-02-19 18:19 ` Larry Finger
2015-02-20 11:44 ` Mike Turner
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.20150213T114021-973@post.gmane.org \
--to=miketurner.forum@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).