From: Erich Titl <erich.titl@think.ch>
To: linux-wireless@vger.kernel.org
Subject: Re: b43 driver and WEP (solved)
Date: Tue, 06 Jan 2015 08:02:45 +0100 [thread overview]
Message-ID: <54AB8895.1020301@think.ch> (raw)
In-Reply-To: <54AB31EB.6020801@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
Am 06.01.2015 um 01:52 schrieb Larry Finger:
> On 01/05/2015 05:53 PM, Erich Titl wrote:
>> Hi Larry
>>
>> Am 05.01.2015 um 22:18 schrieb Larry Finger:
>>> On 01/05/2015 03:07 AM, Erich Titl wrote:
>> ...
>>>
>>> I then generated a 3.10.63 kernel, rebooted and retested. It also works.
>>>
>>> One thing would be to try disabling hardware encryption using option
>>> "nohwcrypt=1". You might also check to determine what key slot your AP
>>> is expecting to use. My AP has only a single key setup. It calls it #1
>>> while Linux is using #0, but that is expected.
>>
>> Thanks a lot for coming back on this issue. I have been digging into the
>> code and found the culprit tonight. The arc4 module was not loaded and
>> WEP could not be initialized. The puzzling thing is, the outgoing dhcp
>> packet passed.... weird.
>
> Glad you found it. Strange that loading mac80211 did not force loading.
> Have you run 'depmod -a' on the modules?
This is an embedded device with quite a small footprint. It does not
have all the drivers by default. Yes, I ran depmod -a, but depmod
produces only one line for arc4, so no luck.
kernel/crypto/arc4.ko.gz:
cheers
Erich
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 1908 bytes --]
next prev parent reply other threads:[~2015-01-06 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 9:07 b43 driver and WEP Erich Titl
2015-01-05 21:18 ` Larry Finger
2015-01-05 23:49 ` Pat Erley
2015-01-05 23:53 ` b43 driver and WEP (solved) Erich Titl
2015-01-06 0:52 ` Larry Finger
2015-01-06 7:02 ` Erich Titl [this message]
2015-01-06 8:29 ` Johannes Berg
2015-01-06 10:38 ` Erich Titl
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=54AB8895.1020301@think.ch \
--to=erich.titl@think.ch \
--cc=linux-wireless@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 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).