All of lore.kernel.org
 help / color / mirror / Atom feed
From: Forest Bond <forest@alittletooquiet.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Anyone using rtl8192de with 2.4GHz 802.11g?
Date: Thu, 12 Jul 2012 11:25:46 -0400	[thread overview]
Message-ID: <20120712152545.GA9489@alittletooquiet.net> (raw)
In-Reply-To: <4FFE2F38.7030604@lwfinger.net>

[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]

Hi Larry,

On Wed, Jul 11, 2012 at 08:58:16PM -0500, Larry Finger wrote:
> On 07/11/2012 08:32 PM, Forest Bond wrote:
> >On Wed, Jul 11, 2012 at 07:58:04PM -0500, Larry Finger wrote:
> >>On 07/11/2012 07:21 PM, Forest Bond wrote:
> >>>The rtl8192de driver is working fine for me at 5GHz, but I am having trouble
> >>>getting scan results for 2.4GHz 802.11g networks.  I have been doing a lot of
> >>>debugging but am not making much progress.  I suspect the 802.11 b/g/n phy is
> >>>not being initialized correctly, but I'm pretty far outside my domain on this
> >>>one.
> >>>
> >>>Is anyone successfully using this driver with a 2.4GHz 802.11g network?
> >>
> >>I have several different models - some work better than others. What
> >>is the PCI ID for yours?
> >
> >This is the one I have:
> >
> >02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:8193]
> >02:00.1 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:8193] (rev 01)
> 
> It turns out that both kinds have the same ID. I think one of them
> is a prototype, while the other is probably a production unit.
> Obviously, bitrot has set in while I wasn't testing. With the kernel
> driver, neither unit can even scan in the 2.4 GHz band. Using the
> latest version of the vendor driver, the production version connects
> with APs running WEP, WPA, or WPA2. The prototype can only handle
> WEP.
> 
> Obviously, I have some work to do. In the meantime, I will send you
> a tarball containing the vendor driver - privately so as not to spam
> the list.

Thank you, I appreciate that.

Of course, my preference would be to fix up the kernel driver.  I don't mind
doing some manual bisection with compat-wireless releases unless you think that
would be a total waste of time.  Do you have any sense for what the last working
kernel version would have been?

As you suggest, we may need to use the vendor driver in the meantime.  Thanks
again for sending it over (although I suspect it is the same version I
downloaded from Realtek's web site).

Thanks,
Forest
-- 
Forest Bond
http://www.alittletooquiet.net
http://www.rapidrollout.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-07-12 15:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12  0:21 Anyone using rtl8192de with 2.4GHz 802.11g? Forest Bond
2012-07-12  0:58 ` Larry Finger
2012-07-12  1:32   ` Forest Bond
2012-07-12  1:58     ` Larry Finger
2012-07-12 15:25       ` Forest Bond [this message]
2012-07-12 16:23         ` Larry Finger
2012-07-12 18:17           ` Forest Bond
2012-07-12 21:07             ` Forest Bond
2012-07-12 21:57               ` Forest Bond
2012-07-13  3:14                 ` Larry Finger
2012-07-13 14:40                   ` Forest Bond

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=20120712152545.GA9489@alittletooquiet.net \
    --to=forest@alittletooquiet.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.