All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roland Vossen" <rvossen@broadcom.com>
To: Camaleón <noelamac@gmail.com>
Cc: "Dan Williams" <dcbw@redhat.com>,
	"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 12:03:41 +0200	[thread overview]
Message-ID: <4E52297D.9090301@broadcom.com> (raw)
In-Reply-To: <CAKprTDEUVa6ouH92G_8UMo20wYNnrhu76c_XAPYDtbCbRjqdLw@mail.gmail.com>

Hello Camaleón,

> Okay, I finally managed to compile a kernel with the required flag
> enabled and booted with it. I am attaching the resulting trace file,
> should you need additional information, kindly ask.

thanks! I did the same thing on my setup and diff'ed the resulting trace 
file with yours. I spotted a difference but it should not be relevant:

(your trace): drv_prepare_multicast: phy0 prepare mc (5)
(my trace): drv_prepare_multicast: phy0 prepare mc (1)

I am wondering if the problem could be explained by a RF kill switch 
being active. Can you send me the output of 'rfkill list' and 'lsmod' ?

Are there wireless-related LEDs on your machine and do they act 
differently between kernel 3.0.1 and 2.6.39-2 ?

Can you do a 'rfkill unblock all' to see if that makes a difference ?

Can you read this thread for more ideas: 
http://ubuntuforums.org/archive/index.php/t-1604665.html ?

Let me know how this works out, if unsuccessful we'll have to dig a bit 
deeper.

Thanks, Roland.








  reply	other threads:[~2011-08-22 10:06 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 [this message]
2011-08-22 11:27                 ` Camaleón
2011-08-22 12:57                   ` Roland Vossen
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=4E52297D.9090301@broadcom.com \
    --to=rvossen@broadcom.com \
    --cc=arend@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=dcbw@redhat.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 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.