linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Prism54 -- error loading firmware
Date: Fri, 11 Mar 2005 08:12:54 +0000	[thread overview]
Message-ID: <1110528774.4918.4.camel@localhost.localdomain> (raw)
In-Reply-To: <42313FDA.8050402@jg555.com>

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

On Thu, 2005-03-10 at 22:51 -0800, Jim Gifford wrote:
> Everytime I try to get the firmware to load for my prism54 based card I 
> get the following error messages.
> 
> Loaded prism54 driver, version 1.2
> ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
> eth0: resetting device...
> eth0: uploading firmware...
> prism54: request_firmware() failed for 'isl3890'
> eth0: could not upload firmware ('isl3890')
> eth0: islpci_reset: failure
> 
> I have made sure the directory specified in firmware.agent is correct. 
> /lib/firmware
> 
> I have placed the firmware into that directory.
> 
> I'm using a LFS 6.x based system, with udev 054, hotplug 9_23, and 
> 2.6.11.2 kernel.

What does:
  cat /proc/sys/kernel/hotplug

print?

Please record the hotplug event timing with the attached script, by
placing it as:
  /etc/hotplug.d/default/00-log.hotplug

And post the corresponding timestamps from syslog too, while loading the
module that requests the firmware.

Kay

[-- Attachment #2: 00-log.hotplug --]
[-- Type: application/x-shellscript, Size: 140 bytes --]

  parent reply	other threads:[~2005-03-11  8:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11  6:51 Prism54 -- error loading firmware Jim Gifford
2005-03-11  7:38 ` Stefan Schweizer
2005-03-11  7:42 ` Jim Gifford
2005-03-11  8:12 ` Kay Sievers [this message]
2005-03-11  9:17 ` Jim Gifford
2005-03-11  9:40 ` Kay Sievers
2005-03-11 16:04 ` Jim Gifford
2005-03-11 18:36 ` Jim Gifford

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=1110528774.4918.4.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@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).