Prism54 -- error loading firmware

DISCUSSION Jim Gifford 3 participants 8 messages Mar 11, 2005

Share & tools

Jim Gifford

author

2005-03-11 06:51 UTC #0 lore raw

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.

Signature · 15 lines

----
Jim Gifford
[email protected]



-------------------------------------------------------
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_id396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Stefan Schweizer

2005-03-11 07:38 UTC #1 lore raw

Quoted 7 lines · Jim Gifford

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

Does your card maybe have "made in China" on it?
The newer china-version does not yet work with the prism54-driver.

regards,
Stefan Schweizer

-------------------------------------------------------
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_id396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Jim Gifford

author

2005-03-11 07:42 UTC #2 lore raw

In reply to Jim Gifford

Quoted 13 lines · Stefan Schweizer

Quoted 9 lines · Jim Gifford
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

Quoted 8 lines

Does your card maybe have "made in China" on it?
The newer china-version does not yet work with the prism54-driver.
regards,
Stefan Schweizer

First thing I checked, it's the V1 card made in Taiwan. Class 0280: 1260:3890 Subsystem: 10b8:2835

This is a SMC2835W

Signature · 15 lines

----
Jim Gifford
[email protected]



-------------------------------------------------------
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_id396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Kay Sievers

2005-03-11 08:12 UTC #3 lore raw

In reply to Jim Gifford

Quoted 11 lines · Jim Gifford

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

Quoted 7 lines

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

Jim Gifford

author

2005-03-11 09:17 UTC #4 lore raw

In reply to Jim Gifford

Quoted 7 lines · Kay Sievers

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

/sbin/hotplug

Quoted 10 lines

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

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')
Mar 11 01:04:47 laptop eth0: islpci_reset: failure
Mar 11 01:04:54 laptop eth0: hot unplug detected
Mar 11 01:04:54 laptop eth0: removing device

from events
HOTPLUG_TIME='Fri Mar 11 01:02:48 PST 2005'
SUBSYSTEM=module
HOTPLUG_ARGSDEVPATH=/module/firmware_class
HOTPLUG_TYPE=module
ACTIONd
SEQNUM88

HOTPLUG_TIME='Fri Mar 11 01:02:48 PST 2005'
SUBSYSTEM=class
HOTPLUG_ARGSDEVPATH=/class/firmware
HOTPLUG_TYPE=class
ACTIONd
SEQNUM89

HOTPLUG_TIME='Fri Mar 11 01:02:48 PST 2005'
SUBSYSTEM=module
HOTPLUG_ARGSDEVPATH=/module/prism54
HOTPLUG_TYPE=module
ACTIONd
SEQNUM90

HOTPLUG_TIME='Fri Mar 11 01:02:48 PST 2005'
SUBSYSTEM=drivers
HOTPLUG_ARGSDEVPATH=/bus/pci/drivers/prism54
HOTPLUG_TYPE=drivers
ACTIONd
SEQNUM91

from hotplug_d.log

--------415--------
1110532073 remove /class/net/eth0
PHYSDEVPATH=/devices/pci0000:00/0000:00:0a.0/0000:02:00.0 SUBSYSTEM=net DEVPATH=/class/net/eth0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=remove _=/usr/bin/env PWD=/ HOME=/ SHLVL=2 PHYSDEVDRIVER<59x INTERFACE=eth0 PHYSDEVBUS=pci SEQNUMA5 --------415--------

--------416--------
1110532073 remove /devices/pci0000:00/0000:00:0a.0/0000:02:00.0
PCI_SLOT_NAME00:02:00.0 PCI_IDB7:5257 SUBSYSTEM=pci DEVPATH=/devices/pci0000:00/0000:00:0a.0/0000:02:00.0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=remove _=/usr/bin/env PWD=/ PCI_SUBSYS_IDB7:5C57 HOME=/ SHLVL=2 PHYSDEVBUS=pci PCI_CLASS 000 SEQNUMA6 --------416--------

--------417--------
1110532082 add /devices/pci0000:00/0000:00:0a.0/0000:02:00.0
PCI_SLOT_NAME00:02:00.0 PCI_ID60:3890 SUBSYSTEM=pci DEVPATH=/devices/pci0000:00/0000:00:0a.0/0000:02:00.0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTIONd _=/usr/bin/env PWD=/ PCI_SUBSYS_IDB8:2835 HOME=/ SHLVL=2 PHYSDEVBUS=pci PCI_CLASS(000 SEQNUMA7 --------417--------

--------418--------
1110532082 add /class/net/eth0
PHYSDEVPATH=/devices/pci0000:00/0000:00:0a.0/0000:02:00.0 SUBSYSTEM=net DEVPATH=/class/net/eth0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTIONd _=/usr/bin/env PWD=/ HOME=/ SHLVL=2 PHYSDEVDRIVER=prism54 INTERFACE=eth0 PHYSDEVBUS=pci SEQNUMA8 --------418--------

--------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--------

--------420--------
1110532103 remove /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 ACTION=remove _=/usr/bin/env PWD=/ HOME=/ SHLVL=2 PHYSDEVDRIVER=prism54 PHYSDEVBUS=pci SEQNUMB0 --------420--------

--------422--------
1110532119 remove /devices/pci0000:00/0000:00:0a.0/0000:02:00.0
PCI_SLOT_NAME00:02:00.0 PCI_ID60:3890 SUBSYSTEM=pci DEVPATH=/devices/pci0000:00/0000:00:0a.0/0000:02:00.0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=remove _=/usr/bin/env PWD=/ PCI_SUBSYS_IDB8:2835 HOME=/ SHLVL=2 PHYSDEVBUS=pci PCI_CLASS(000 SEQNUMB2 --------422--------

--------421--------
1110532119 remove /class/net/eth0
PHYSDEVPATH=/devices/pci0000:00/0000:00:0a.0/0000:02:00.0 SUBSYSTEM=net DEVPATH=/class/net/eth0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=remove _=/usr/bin/env PWD=/ HOME=/ SHLVL=2 PHYSDEVDRIVER=prism54 INTERFACE=eth0 PHYSDEVBUS=pci SEQNUMB1 --------421--------

--------423--------
1110532324 add /devices/pci0000:00/0000:00:0a.0/0000:02:00.0
PCI_SLOT_NAME00:02:00.0 PCI_IDB7:5257 SUBSYSTEM=pci DEVPATH=/devices/pci0000:00/0000:00:0a.0/0000:02:00.0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTIONd _=/usr/bin/env PWD=/ PCI_SUBSYS_IDB7:5C57 HOME=/ SHLVL=2 PHYSDEVBUS=pci PCI_CLASS 000 SEQNUMB3 --------423--------

--------424--------
1110532324 add /class/net/eth0
PHYSDEVPATH=/devices/pci0000:00/0000:00:0a.0/0000:02:00.0 SUBSYSTEM=net DEVPATH=/class/net/eth0 PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTIONd _=/usr/bin/env PWD=/ HOME=/ SHLVL=2 PHYSDEVDRIVER<59x INTERFACE=eth0 PHYSDEVBUS=pci SEQNUMB4 --------424--------

Signature · 15 lines

----
Jim Gifford
[email protected]



-------------------------------------------------------
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_id396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Kay Sievers

2005-03-11 09:40 UTC #5 lore raw

In reply to Jim Gifford

Quoted 10 lines · Jim Gifford

Quoted 7 lines · Kay Sievers
What does:
cat /proc/sys/kernel/hotplug
print?
/sbin/hotplug

Ok, so it's not a udev issue.

Quoted 28 lines

Quoted 6 lines
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

Quoted 8 lines

--------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

Jim Gifford

author

2005-03-11 16:04 UTC #6 lore raw

In reply to Jim Gifford

Quoted 6 lines · Kay Sievers

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.

Quoted 9 lines

And what does:
ls -l /lib/firmware/
print?
Kay

(root@laptop)-(01:15 AM Fri Mar 11)-(/tmp)

# ls -l /lib/firmware
total 96
-rwxr-xr-x  1 root root 93996 2003-08-17 11:56 isl3890
(root@laptop)-(08:03 AM Fri Mar 11)-(/tmp)

Signature · 15 lines

----
Jim Gifford
[email protected]



-------------------------------------------------------
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_id396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Jim Gifford

author

2005-03-11 18:36 UTC #7 lore raw

In reply to Jim Gifford

Figured it out,
It appears I had to sysfs loaded, it was checking the /initrd/sys,
instead of the /sys, after I updated my bootscript to remove the initrd completly it worked.