From: "Lee Revell" <rlrevell@joe-job.com>
To: "Patrick Ale" <patrick.ale@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [IPW3945] Can't load microcode
Date: Sun, 4 Mar 2007 23:34:29 -0500 [thread overview]
Message-ID: <75b66ecd0703042034l4e50c88fueb31cfa508cf672f@mail.gmail.com> (raw)
In-Reply-To: <8d158e1f0703040841m634b37d4r9f2d4135f5f4dfd6@mail.gmail.com>
On 3/4/07, Patrick Ale <patrick.ale@gmail.com> wrote:
> ieee80211_crypt: registered algorithm 'NULL'
> ieee80211: 802.11 data/management/control stack, git-1.1.13
> ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
> ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0d
> ipw3945: Copyright(c) 2003-2006 Intel Corporation
> ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 22
> PCI: Setting latency timer of device 0000:05:00.0 to 64
> ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
> ipw3945: ipw3945.ucode load failed: Reason -2
> ipw3945: Could not read microcode: -2
> ipw3945: probe of 0000:05:00.0 failed with error -2
Error -2 is "No such file or directory". Maybe it expects the
firmware to be somewhere other than /lib/firmware or your driver and
firmware versions don't match. Try adding some debug printk()s around
the request_firmware() call in the driver.
If you're using out of tree drivers the error should be reported to
Intel rather than this list.
Lee
next prev parent reply other threads:[~2007-03-05 4:34 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
2007-03-05 4:34 ` Lee Revell [this message]
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=75b66ecd0703042034l4e50c88fueb31cfa508cf672f@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.ale@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 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®