From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Prism54 -- error loading firmware
Date: Fri, 11 Mar 2005 09:40:26 +0000 [thread overview]
Message-ID: <1110534026.4918.69.camel@localhost.localdomain> (raw)
In-Reply-To: <42313FDA.8050402@jg555.com>
On Fri, 2005-03-11 at 01:17 -0800, Jim Gifford wrote:
> Kay Sievers wrote:
>
> >What does:
> > cat /proc/sys/kernel/hotplug
> >
> >print?
> >
> >
> >
> /sbin/hotplug
Ok, so it's not a udev issue.
> >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.
> From syslog
> Mar 11 01:04:19 laptop Loaded prism54 driver, version 1.2
> Mar 11 01:04:19 laptop PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
> Mar 11 01:04:19 laptop ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11
> (level, low) -> IRQ 11
> Mar 11 01:04:37 laptop eth0: resetting device...
> Mar 11 01:04:37 laptop eth0: uploading firmware...
> Mar 11 01:04:47 laptop prism54: request_firmware() failed for 'isl3890'
> Mar 11 01:04:47 laptop eth0: could not upload firmware ('isl3890')
> from events
> HOTPLUG_TIME='Fri Mar 11 01:02:48 PST 2005'
> SUBSYSTEM=module
> HOTPLUG_ARGS> DEVPATH=/module/firmware_class
> HOTPLUG_TYPE=module
> ACTIONd
> SEQNUM88
> from hotplug_d.log
> --------419--------
> 1110532093 add /class/firmware/0000:02:00.0
> PHYSDEVPATH=/devices/pci0000:00/0000:00:0a.0/0000:02:00.0
> SUBSYSTEM=firmware DEVPATH=/class/firmware/0000:02:00.0
> FIRMWARE=isl3890 PATH=/sbin:/bin:/usr/sbin:/usr/bin
> ACTIONd _=/usr/bin/env PWD=/ HOME=/ SHLVL=2 PHYSDEVDRIVER=prism54
> PHYSDEVBUS=pci SEQNUMA9
> --------419--------
All three logs snippets seems to belong to a different driver loading
sequence. :) Please make sure that they all fro the same events.
You may try add some debug to the firmware loading script to see what
the script is actually doing.
And what does:
ls -l /lib/firmware/
print?
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-03-11 9:40 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
2005-03-11 9:17 ` Jim Gifford
2005-03-11 9:40 ` Kay Sievers [this message]
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=1110534026.4918.69.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).