From: Mark Huijgen <mark.sf.net@huijgen.tk>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Larry Finger <Larry.Finger@lwfinger.net>,
Broadcom Wireless <bcm43xx-dev@lists.berlios.de>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ANN] b43 LP-PHY support (BCM4310/4312/4315) working (partially)!
Date: Wed, 19 Aug 2009 16:00:10 +0200 [thread overview]
Message-ID: <4A8C056A.4050005@huijgen.tk> (raw)
In-Reply-To: <69e28c910908190654v231d66c7k6a223f481f702c7c@mail.gmail.com>
Gábor Stefanik wrote:
> 2009/8/19 Mark Huijgen <mark.sf.net@huijgen.tk>:
>
>> Gábor Stefanik wrote:
>>
>>> Mark, could you produce a dmesg output with the new firmware, patches
>>> applied, and channel set to 1? Post the output of dmesg after scanning
>>> & probably associating, if possible. (Scan/assoc may produce messages
>>> in dmesg.)
>>>
>>>
>> I tested this already, but with default chan set to 1, I cannot get the
>> interface up.
>> This is somewhere in my mail, but it got a bit messy after I noticed
>> that after
>> changing some of the code my modules got installed in another directory
>> (-dirty).
>>
>> I just restarted the notebook, but now the results are different again...
>>
>> New firmware, with patches applied and default channel 7:
>> [ 72.160057] b43-phy1: Loading firmware version 478.104 (2008-07-01
>> 00:50:23)
>> [ 72.163484] b43-phy1 debug: RC calib: Failed to switch to channel 7,
>> error = -5
>> [ 72.168100] b43-phy1 debug: Switch to init channel failed, error = -5.
>>
>> Recompile module with default chan 1, patches still applied and new
>> firmware,
>> # modprobe -r b43 && modprobe b43 verbose=3 && ifconfig wlan0 up
>>
>> [ 430.259877] b43-phy2 debug: Switch to init channel failed, error = -5.
>>
>> Recompile again, but with default chan back to 7, still patched and
>> still new firmware.
>> So same as in first situation:
>> # modprobe -r b43 && modprobe b43 verbose=3 && ifconfig wlan0 up
>>
>> [ 524.748062] b43-phy3 debug: Chip initialized
>>
>> And I can get my interface up and working!
>>
>> Without this procedure I have not been able to get a working chip. Seems
>> the partially
>> initialized state after each try, allows the next try to get a bit
>> further. And together with
>> the default channel switching between 1 and 7, I get a working chip, but
>> a chip that does
>> not seem to be able to find my AP thats on channel 1.
>>
>> If I now change default chan to 1 again, I am getting the same error as
>> in step 2 above.
>> I have not been able to get the interface up with default chan set to 1.
>>
>> Mark
>>
>>
>>
>
> What do you see in dmesg after running a scan?
>
After step 2, interface cannot be brought up:
# iw dev wlan0 scan
command failed: Network is down (-100)
No extra output in dmesg
After step 3 (so with default chan 7 again), interface comes up and I
can scan:
# iw dev wlan0 scan
<<list of scan results>>
No extra output generated in dmesg.
I must add that I do not have debugging messages enabled for any
mac80211 related options, only for b43 module.
Mark
next prev parent reply other threads:[~2009-08-19 14:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 20:29 [ANN] b43 LP-PHY support (BCM4310/4312/4315) now ready for testing! Gábor Stefanik
2009-08-18 23:41 ` Luis R. Rodriguez
2009-08-18 23:41 ` Luis R. Rodriguez
2009-08-18 23:42 ` Luis R. Rodriguez
2009-08-18 23:42 ` Luis R. Rodriguez
2009-08-19 8:42 ` Mark Huijgen
2009-08-19 11:28 ` Gábor Stefanik
2009-08-19 12:43 ` [ANN] b43 LP-PHY support (BCM4310/4312/4315) working (partially)! Mark Huijgen
2009-08-19 13:04 ` Johannes Berg
2009-08-19 13:26 ` Gábor Stefanik
2009-08-19 13:49 ` Mark Huijgen
2009-08-19 13:54 ` Gábor Stefanik
2009-08-19 14:00 ` Mark Huijgen [this message]
2009-08-19 14:03 ` Gábor Stefanik
2009-08-19 14:24 ` Mark Huijgen
2009-08-19 14:54 ` Gábor Stefanik
2009-08-20 7:14 ` Mark Huijgen
2009-08-20 7:15 ` Mark Huijgen
2009-08-20 11:45 ` Gábor Stefanik
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=4A8C056A.4050005@huijgen.tk \
--to=mark.sf.net@huijgen.tk \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@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.