All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guan Xin <guanx.bac@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [Bug] Various abnormal WiFi behaviors with Linux 3.8 on arm/imx23
Date: Mon, 4 Mar 2013 01:44:52 +0100	[thread overview]
Message-ID: <CANeMGR5a78oq63N4Fr9x0kEQue3GiXeMX7L9Om5-AqUUxdzEPQ@mail.gmail.com> (raw)

Hello,

I have just moved from Linux 3.7.x to Linux 3.8.x because 3.7.x is
EOL-ed. On an iMX233-OLinuXino-MICRO with USB WiFi adapters I got the
following problems which were never present in Linux 3.7.x.

Error 1:
At first I used a USB-WiFi adapter with the RTL8192CU chip. The
rtlwifi driver showed nothing wrong in dmesg. However, I could get
nothing when scanning for APs. It looks exactly like there are no AP
at all. Of course I could not associate with my AP either.
I also tried to use the manufacturer's driver, same problem.

Error 2:
Then I changed to use an adapter with the RT5370 chip. This time I got
scanning working. It can also associate with the AP and works as
expected. The problem is -- when I tried to add the wlan IF to a
bridge, I got this:
"can't add wlan0 to bridge br0: Operation not supported"

Here are some of my kernel config options:
CONFIG_RT2X00=m
CONFIG_RT2500USB=m
CONFIG_RT73USB=m
CONFIG_RT2800USB=m
CONFIG_RT2800USB_RT33XX=y
CONFIG_RT2800USB_RT35XX=y
CONFIG_RT2800USB_RT53XX=y
CONFIG_RT2800USB_UNKNOWN=y
CONFIG_RT2800_LIB=m
CONFIG_RT2X00_LIB_USB=m
CONFIG_RT2X00_LIB=m
CONFIG_RT2X00_LIB_FIRMWARE=y
CONFIG_RT2X00_LIB_CRYPTO=y
CONFIG_RT2X00_LIB_LEDS=y
# CONFIG_RT2X00_DEBUG is not set
CONFIG_RTL8192CU=m
CONFIG_RTLWIFI=m
CONFIG_RTLWIFI_DEBUG=y
CONFIG_RTL8192C_COMMON=m

I will post more information if necessary.

Best regards,
Guan

             reply	other threads:[~2013-03-04  0:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  0:44 Guan Xin [this message]
2013-03-04 22:43 ` [Bug] Various abnormal WiFi behaviors with Linux 3.8 on arm/imx23 Guan Xin
2013-03-07 23:15   ` Guan Xin

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=CANeMGR5a78oq63N4Fr9x0kEQue3GiXeMX7L9Om5-AqUUxdzEPQ@mail.gmail.com \
    --to=guanx.bac@gmail.com \
    --cc=linux-kernel@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.