From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Fri, 11 Mar 2005 09:40:26 +0000 Subject: Re: Prism54 -- error loading firmware Message-Id: <1110534026.4918.69.camel@localhost.localdomain> List-Id: References: <42313FDA.8050402@jg555.com> In-Reply-To: <42313FDA.8050402@jg555.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On Fri, 2005-03-11 at 01:17 -0800, Jim Gifford wrote: > Kay Sievers wrote: >=20 > >What does: > > cat /proc/sys/kernel/hotplug > > > >print? > > > > =20 > > > /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=20 > (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=3D'Fri Mar 11 01:02:48 PST 2005' > SUBSYSTEM=3Dmodule > HOTPLUG_ARGS> DEVPATH=3D/module/firmware_class > HOTPLUG_TYPE=3Dmodule > ACTION=ADd > SEQNUM88 > from hotplug_d.log > --------419-------- > 1110532093 add /class/firmware/0000:02:00.0 > PHYSDEVPATH=3D/devices/pci0000:00/0000:00:0a.0/0000:02:00.0 > SUBSYSTEM=3Dfirmware DEVPATH=3D/class/firmware/0000:02:00.0 > FIRMWARE=3Disl3890 PATH=3D/sbin:/bin:/usr/sbin:/usr/bin > ACTION=ADd _=3D/usr/bin/env PWD=3D/ HOME=3D/ SHLVL=3D2 PHYSDEVDRIVER=3Dpr= ism54 > PHYSDEVBUS=3Dpci 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=14396&op=3Dclick _______________________________________________ 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