All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 23 Aug 2011 16:18:24 +0200	[thread overview]
Message-ID: <4E53B6B0.8010605@broadcom.com> (raw)
In-Reply-To: <CAKprTDHVcEgZvNE6Ububoaf1WH+LAcHD35YriNaj47JnsVL=Xg@mail.gmail.com>

>> that is great. Ok, do you have the kernel sources on your system ? If so, cd
>> to the root of the source tree and issue these commands to build the driver:
>>
>> make SUBDIRS=drivers/staging/brcm80211 clean
>> make SUBDIRS=drivers/staging/brcm80211 modules
>
> Done!

perfect !

>> if that works, do a 'modprobe mac80211' followed by a 'insmod
>> drivers/staging/brcm80211/brcmutil/brcmutil.ko'
>
> root@stt300:/usr/src/linux-source-3.0.0# insmod
> drivers/staging/brcm80211/brcmutil/brcmutil.ko
> insmod: can't read 'drivers/staging/brcm80211/brcmutil/brcmutil.ko':
> No such file or directory
>
> Ah, okay...
> root@stt300:/usr/src/linux-source-3.0.0# insmod
> drivers/staging/brcm80211/util/brcmutil.ko

Ah, the source tree had some renaming. It is named 'brcmutil' in my 
source but in the source you are using it is still named 'util'.

> root@stt300:/usr/src/linux-source-3.0.0#
>
>> followed by a 'insmod drivers/staging/brcm80211/brcmsmac/brcmsmac.ko'.
>
> Mmm... this one returned an error:
>
> root@stt300:/usr/src/linux-source-3.0.0# insmod
> drivers/staging/brcm80211/brcmsmac/brcmsmac.ko
> insmod: error inserting
> 'drivers/staging/brcm80211/brcmsmac/brcmsmac.ko': -1 Unknown symbol in
> module
>
> And dmesg shows:
>
> [16235.934894] brcmsmac: Unknown symbol bcm_chspec_malformed (err 0)
> [16235.934985] brcmsmac: Unknown symbol bcm_pktq_init (err 0)
> [16235.935035] brcmsmac: Unknown symbol bcm_bitcount (err 0)
> [16235.935092] brcmsmac: Unknown symbol bcm_pktq_peek_tail (err 0)
> [16235.935130] brcmsmac: Unknown symbol bcm_pktq_mdeq (err 0)
> [16235.935283] brcmsmac: Unknown symbol bcm_pktq_pdeq (err 0)
> [16235.935329] brcmsmac: Unknown symbol bcm_chspec_ctlchan (err 0)
> [16235.935375] brcmsmac: Unknown symbol bcm_pkt_buf_free_skb (err 0)
> [16235.935414] brcmsmac: Unknown symbol bcm_iovar_lencheck (err 0)
> [16235.935457] brcmsmac: Unknown symbol bcm_pkttotlen (err 0)
> [16235.935519] brcmsmac: Unknown symbol bcm_ether_atoe (err 0)
> [16235.935581] brcmsmac: Unknown symbol bcm_crc8 (err 0)
> [16235.935636] brcmsmac: Unknown symbol bcm_pkt_buf_get_skb (err 0)
> [16235.935677] brcmsmac: Unknown symbol bcm_pktq_penq_head (err 0)
> [16235.935735] brcmsmac: Unknown symbol bcm_pktq_pdeq_tail (err 0)
> [16235.935774] brcmsmac: Unknown symbol bcm_pktq_pflush (err 0)
> [16235.935827] brcmsmac: Unknown symbol bcm_pktq_penq (err 0)
> [16235.935882] brcmsmac: Unknown symbol bcm_pktq_flush (err 0)

These symbols are contained in the 'brcmutil.ko' module. Can you check 
with lsmod that brcmutil is indeed loaded ?

Thanks, Roland.


  reply	other threads:[~2011-08-23 14:18 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
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 [this message]
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=4E53B6B0.8010605@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 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.