From: "Patrick Ale" <patrick.ale@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [IPW3945] Can't load microcode
Date: Sun, 4 Mar 2007 16:48:08 +0000 [thread overview]
Message-ID: <8d158e1f0703040848l48064204pe5f994ba4663cd0c@mail.gmail.com> (raw)
In-Reply-To: <8d158e1f0703040841m634b37d4r9f2d4135f5f4dfd6@mail.gmail.com>
On 3/4/07, Patrick Ale <patrick.ale@gmail.com> wrote:
> Hi,
>
> I just downloaded the latest kernel drivers, daemon and microcode for
> my Intel Wireless card. everything built correctly, the microcode is
> placed in /lib/firmware and when running /etc/init.d/ipw3945d-start I
> get the following dmesg
Extra info:
When doing a /sbin/ipw3945d --kill && /sbin/ipw3945d I get:
ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
ipw3945: uCode verification failed at addr 0x00003800+0 (of 2396)
ipw3945: Unable to load firmware: -5
ipw3945: MAC is in deep sleep!
ipw3945: Unable to load firmware: -5
ipw3945: MAC is in deep sleep!
ipw3945: Unable to load firmware: -5
ipw3945: MAC is in deep sleep!
ipw3945: Unable to load firmware: -5
ipw3945: MAC is in deep sleep!
ipw3945: Unable to load firmware: -5
ipw3945: MAC is in deep sleep!
ipw3945: MAC is in deep sleep!
ipw3945: MAC is in deep sleep!
ipw3945: MAC is in deep sleep!
ipw3945: Unable to initialize device after 5 attempts.
ipw3945: MAC is in deep sleep!
ipw3945: Unable to int nic
ipw3945: MAC is in deep sleep!
ipw3945: Unable to int nic
ipw3945: MAC is in deep sleep!
ipw3945: Unable to int nic
ipw3945: MAC is in deep sleep!
ipw3945: Unable to int nic
ipw3945: MAC is in deep sleep!
ipw3945: Unable to int nic
ipw3945: MAC is in deep sleep!
ipw3945: Unable to int nic
next prev parent reply other threads:[~2007-03-04 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 16:41 Patrick Ale
2007-03-04 16:48 ` Patrick Ale [this message]
2007-03-05 4:34 ` Lee Revell
2007-03-05 9:54 ` Patrick Ale
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=8d158e1f0703040848l48064204pe5f994ba4663cd0c@mail.gmail.com \
--to=patrick.ale@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®