Re: Allnet ALL0271 Firmware upload failure

"Aurelius Robert BAIER" <[email protected]>
Newsgroups gmane.linux.drivers.prism54.user
Organization hullabaluh, Teil der Hulla-Gruppe
Message-ID <opsb5gv0icjv9q8h@phoenix>
Hi Steve,

Thank you for answering!

less /proc/sys/kernel/hotplug  -> /sbin/hotplug

I think this should be o.k. The output of lspci -vv is:

$0000:00:0c.0 Network controller: Intersil Corporation Intersil ISL3890  
[Prism GT/Prism Duette] (rev 01)
$        Subsystem: Tekram Technology Co.,Ltd. ALLNET ALL0271 Wireless PCI  
Adapter
$        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-  
ParErr- Stepping- SERR- FastB2B-
$        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR-
$        Latency: 80 (2500ns min, 7000ns max), cache line size 08
$        Interrupt: pin A routed to IRQ 18
$        Region 0: Memory at ea000000 (32-bit, non-prefetchable)
$        Capabilities: [dc] Power Management version 1
$                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA  
PME(D0+,D1+,D2+,D3hot+,D3cold+)
$                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

So it's really an 3890-card with PrismGT chip. The power light at the back  
pannel is shining and the card is shown with iwconfig:
$eth2      NOT READY!  ESSID:"wullanetz"
$          Mode:Managed  Channel:6  Access Point: 00:00:00:00:00:00
$          Tx-Power=31 dBm   Sensitivity=0/200
$          Retry min limit:0   RTS thr=0 B   Fragment thr=0 B
$          Encryption key:AAAA-AAAA-AAAA-AAAA-AAAA-AAAA   Security  
mode:restricted
$          Link Quality:0  Signal level:0  Noise level:0
$          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
$          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
(the key is not the real key, but the output is the same)



The error message is the following:
$Loaded prism54 driver, version 1.1
$eth2: islpci_open()
$eth2: resetting device...
$eth2: uploading firmware...
$eth2: prism54 driver detected card model: PRISM Duette/GT
$prism54: request_firmware() failed for 'isl3890'
$eth2: could not upload firmware ('isl3890')
$eth2: islpci_open()
$eth2: resetting device...
$eth2: uploading firmware...
$prism54: request_firmware() failed for 'isl3890'
$eth2: could not upload firmware ('isl3890')

In addition the firmware.agent is present and executable, the firmware is  
in the correct folder (/usr/lib/hotplug/firmware: isl3890.arm and isl3890.  
The output of hotplug is:
$phoenix root # hotplug
$Usage: /etc/hotplug.d/default/default.hotplug AgentName [AgentArguments]
$AgentName values on this system:  dasd firmware ieee1394 input net pci  
scsi tape usb

So hotplug feels responsible for firmware.

I think the sys file system is mounted becaue in /sys there are things  
listed like:
$ls /sys/
$block     bus       class     devices   firmware  module    power

I hope I've written all the important things.

Thank you very much for your help!!
Aurel



On Tue, 3 Aug 2004 08:10:34 +0100 (BST), <[email protected]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tue, 3 Aug 2004, Aurelius Robert BAIER wrote:
>
>> I have an ALL0271 and cannot upload the firmware. The firmware is in
>> /usr/lib/hotplug/firmware/isl3890.arm and isl3890. The firmware.agent is
>> present. The error message is "request_firmware() failed for 'isl3890'".
>> The error message appears when I load the module prism54 from a 2.6.7
>> kernel. Thanks very much for help.
>
> Check that /proc/sys/kernel/hotplug points at the right place (probably
> /sbin/hotplug).
>
> - --
>
>  - Steve         Jabber: [email protected]     Web:  
> http://www.nexusuk.org/
>
>      Servatis a periculum, servatis a maleficum - Whisper, Evanescence
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> Comment: Public key available at http://www.nexusuk.org/pubkey.txt
>
> iD8DBQFBDzpv5zUOsIV3bqERApdJAJ9mYvVcBDQrT7BWOgNdbqPxiSqFPgCeN4UA
> lbdAiULrhOh0Ek+ArnbEmT0=
> =bKW7
> -----END PGP SIGNATURE-----



-- 
http://hullabaluh.ch
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.