From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <larry.finger@lwfinger.net>
Cc: Johannes Berg <johannes@sipsolutions.net>,
bcm43xx-dev@lists.berlios.de, "linux-kernel,
" <linux-kernel@vger.kernel.org>
Subject: Re: Kernel NULL pointer when loading bcm43xx-mac80211 with fwpostfix = ".fw4"
Date: Sat, 7 Apr 2007 19:45:30 +0200 [thread overview]
Message-ID: <200704071945.30680.mb@bu3sch.de> (raw)
In-Reply-To: <4617D862.7010202@lwfinger.net>
On Saturday 07 April 2007 19:44, Larry Finger wrote:
> Johannes Berg wrote:
> > On Sat, 2007-04-07 at 15:51 +0200, Michael Buesch wrote:
> >> On Saturday 07 April 2007 02:01, Larry Finger wrote:
> >>> The current mb and wireless-dev git trees both get a kernel NULL pointer in "param_set_copystring"
> >>> when modprobe'ing bcm43xx-mac80211 with a line of 'options bcm43xx-mac80211 fwpostfix = ".fw4"' in
> >>> /etc/modprobe.conf.local. This construction used to work and still does for bcm43xx-softmac. I
> >>> compared the code between the two versions and cannot see any real differences. Any suggestions?
> >> Uhm, fwpostfix=.fw4 works fine for me when I pass it to modprobe.
> >
> > I use
> > $ cat /etc/modprobe.d/bcm43xx
> > options bcm43xx-mac80211 fwpostfix=-v4
> > options bcm43xx_mac80211 fwpostfix=-v4
> > options bcm43xx fwpostfix=-v3
> >
> > and it works great.
>
> My bad. As shown above, I had white space around the equals - a no-no. Removing it fixed the
> problem. The examples both of you showed gave me the clue.
Hm, probably a bug in the modparam subsystem, though.
I'd say it shouldn't crash, at least.
--
Greetings Michael.
parent reply other threads:[~2007-04-07 17:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4617D862.7010202@lwfinger.net>]
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=200704071945.30680.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=johannes@sipsolutions.net \
--cc=larry.finger@lwfinger.net \
--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.