From: "Roland Vossen" <rvossen@broadcom.com>
To: Camaleón <noelamac@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"Brett Rudley" <brudley@broadcom.com>,
"Henry Ptasinski" <henryp@broadcom.com>,
"Arend Van Spriel" <arend@broadcom.com>,
"networkmanager-list@gnome.org" <networkmanager-list@gnome.org>
Subject: Re: brcmsmac driver only works when sitting next to the AP
Date: Mon, 22 Aug 2011 14:57:25 +0200 [thread overview]
Message-ID: <4E525235.7060501@broadcom.com> (raw)
In-Reply-To: <20110822112737.GA5936@stt008.linux.site>
Hi Camaleón,
thanks for the additional information you provided.
> One difference, though, is that now (with kernel 3.0.0) when I shutdown
> the system it hangs at NetworkManager if wifi LED is on. As soon as I
> turn off the wifi led, the system can continue the shutdown.
> Moreover, "service network-manager stop" returns "failed" unless I
> first turn off the wifi led (and so phy0 hard blocked is set as "yes").
Interesting observations. Ok, lets keep this in the back of our minds
but first focus on the bad scan results.
>> Can you do a 'rfkill unblock all' to see if that makes a difference ?
>> It makes no difference. No wifi networks are detected automatically
nor connecting manually to a hidden network is possible (unless I sit
next to the AP).
Hmmm, so it seems that rfkill switch functionality is not causing the
bad scan result.
Can you try to disable Bluetooth (e.g. by temporary blacklisting the
bluetooth modules) ? Bluetooth operates in the same frequency band as WiFi.
Would you happen to know if with kernel 2.6.39, the brcmsmac driver was
active as well (and not a different driver) ?
> Just in case this helps, I have tried another wifi adapater (USB, based
> on rt2xx chipset) and works like a charm, I mean, it detects the
> avialbale wifi networks and automatically stablishes a connection with
> mine.
Lets shoot for that as well :-)
Thanks, Roland.
next prev parent reply other threads:[~2011-08-22 12:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 12:16 brcmsmac driver only works when sitting next to the AP Camaleón
2011-08-16 11:36 ` Roland Vossen
2011-08-16 15:40 ` Dan Williams
2011-08-17 10:39 ` Roland Vossen
2011-08-18 8:07 ` Roland Vossen
2011-08-19 14:32 ` Roland Vossen
2011-08-19 15:21 ` Camaleón
2011-08-21 21:43 ` Camaleón
2011-08-22 10:03 ` Roland Vossen
2011-08-22 11:27 ` Camaleón
2011-08-22 12:57 ` Roland Vossen [this message]
2011-08-22 13:28 ` Camaleón
2011-08-22 13:55 ` Roland Vossen
2011-08-22 14:27 ` Camaleón
2011-08-23 8:41 ` Roland Vossen
2011-08-23 8:59 ` Camaleón
2011-08-23 9:27 ` Roland Vossen
2011-08-23 9:53 ` Camaleón
2011-08-23 10:38 ` Roland Vossen
2011-08-23 10:53 ` Camaleón
2011-08-23 11:23 ` Roland Vossen
2011-08-23 14:06 ` Camaleón
2011-08-23 14:18 ` Roland Vossen
2011-08-23 14:48 ` Camaleón
2011-08-23 14:58 ` Roland Vossen
2011-08-23 15:27 ` Camaleón
2011-08-23 17:37 ` Roland Vossen
2011-08-23 18:01 ` Camaleón
2011-08-22 14:15 ` Roland Vossen
2011-08-22 14:28 ` Camaleón
2011-08-22 16:37 ` Dan Williams
2011-08-19 20:47 ` Dan Williams
2011-08-22 6:52 ` Roland Vossen
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=4E525235.7060501@broadcom.com \
--to=rvossen@broadcom.com \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=henryp@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=networkmanager-list@gnome.org \
--cc=noelamac@gmail.com \
/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).