suse 10.1 , z-com isl3886 prismchip Firmware gesucht

[scheichlinux]

Hallo

Ich habe eine WLAN Problem mit meiner

Z-com ils3886 PCI

Karte.

Ich habe die Firmware

2.7.0.0.arm

in den Ordner /lib/firmware

und eine Kopie davon nochmals
nach /lib/firmware/isl3886

kopiert.

Ohne Erfolg

kriege nur folgende Meldung:

eth0: resetting device...
eth0: uploading firmware...
prism54: request_firmware() failed for 'isl3886'
eth0: could not upload firmware ('isl3886')
eth0: islpci_reset: failure
dot11req_reset: the macaddress and setdefaultmib arguments are currently unsupported.



Bin echt ratlos

hat jemand eine Idee?



Danke


tom

[Rain_maker]

eth0: resetting device...
eth0: uploading firmware...
prism54: request_firmware() failed for 'isl3886'
eth0: could not upload firmware ('isl3886')
eth0: islpci_reset: failure
dot11req_reset: the macaddress and setdefaultmib arguments are currently unsupported.

Ich verstehe die Fehlermeldung so, daß das FirmwareFILE "isl3886" nicht gefunden wird, welches in /lib/firmware vom System erwartet wird.

Also:

1. Ordner "isl3886" in /lib/firmware löschen

2. 2.7.0.0.arm in 'isl3886' umbenennen und in /lib/firmware kopieren.

Greetz,

RM

[scheichlinux]

Hallo Rain Maker

Danke für den Tipp

Jetzt läd er die Firmware und dann kommt einiges Unverständliches das ich nicht verstehe




eth0: resetting device...
eth0: uploading firmware...
eth0: firmware version: 2.7.0.0
eth0: firmware upload complete
eth0: timeout waiting for mgmt response 250, triggering device
eth0: timeout waiting for mgmt response 225, triggering device
eth0: timeout waiting for mgmt response 200, triggering device
eth0: timeout waiting for mgmt response 175, triggering device
eth0: timeout waiting for mgmt response 150, triggering device
eth0: timeout waiting for mgmt response 125, triggering device
eth0: timeout waiting for mgmt response 100, triggering device
eth0: timeout waiting for mgmt response 75, triggering device
eth0: timeout waiting for mgmt response 50, triggering device
eth0: timeout waiting for mgmt response 25, triggering device
eth0: timeout waiting for mgmt response
eth0: mgt_commit_list: failure. oid=ff020008 err=-110
eth0: timeout waiting for mgmt response 250, triggering device
eth0: timeout waiting for mgmt response 225, triggering device
eth0: timeout waiting for mgmt response 200, triggering device
eth0: timeout waiting for mgmt response 175, triggering device
eth0: timeout waiting for mgmt response 150, triggering device
eth0: timeout waiting for mgmt response 125, triggering device
eth0: timeout waiting for mgmt response 100, triggering device
eth0: timeout waiting for mgmt response 75, triggering device
eth0: timeout waiting for mgmt response 50, triggering device
eth0: timeout waiting for mgmt response 25, triggering device
eth0: timeout waiting for mgmt response
eth0: mgt_commit_list: failure. oid=ff020003 err=-110
eth0: timeout waiting for mgmt response 250, triggering device
eth0: timeout waiting for mgmt response 225, triggering device
eth0: timeout waiting for mgmt response 200, triggering device
eth0: timeout waiting for mgmt response 175, triggering device
eth0: timeout waiting for mgmt response 150, triggering device
eth0: timeout waiting for mgmt response 125, triggering device
eth0: timeout waiting for mgmt response 100, triggering device
eth0: timeout waiting for mgmt response 75, triggering device
eth0: timeout waiting for mgmt response 50, triggering device
eth0: timeout waiting for mgmt response 25, triggering device
eth0: timeout waiting for mgmt response
eth0: mgt_commit_list: failure. oid=10000000 err=-110
eth0: timeout waiting for mgmt response 250, triggering device
eth0: timeout waiting for mgmt response 225, triggering device
eth0: timeout waiting for mgmt response 200, triggering device
eth0: timeout waiting for mgmt response 175, triggering device
eth0: timeout waiting for mgmt response 150, triggering device
eth0: timeout waiting for mgmt response 125, triggering device
eth0: timeout waiting for mgmt response 100, triggering device
eth0: timeout waiting for mgmt response 75, triggering device
eth0: timeout waiting for mgmt response 50, triggering device
eth0: timeout waiting for mgmt response 25, triggering device
eth0: timeout waiting for mgmt response
eth0: mgt_commit_list: failure. oid=17000007 err=-110
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=19000001 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=10000002 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=19000004 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=12000000 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=12000001 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=12000002 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=12000004 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=12000005 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=12000006 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=12000007 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=12000003 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=150007e0 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=ff02000c err=-12
eth0: mgmt tx queue is still full
eth0: mgt_commit_list: failure. oid=ff020003 err=-12
eth0: mgmt tx queue is still full
eth0: mgt_update_addr: failure
eth0: mgt_commit: failure
eth0: interface reset failure
prism54: Your card/socket may be faulty, or IRQ line too busy :(
ident: nic h/w: id=0x8026 1.0.0
ident: pri f/w: id=0x15 1.1.3
ident: sta f/w: id=0x1f 1.7.1
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/4
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/12
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Prism2 card SN: 000000000000
dot11req_reset: the macaddress and setdefaultmib arguments are currently unsupported.



Was kann ich tun?

Danke


tom

[Rain_maker]

prism54: Your card/socket may be faulty, or IRQ line too busy

==>

http://www.google.de/search?q=prism54%3A+Your+card/socket+may+be+faulty,+or+IRQ+line+too+busy&ie=UTF-8&oe=UTF-8

Hier würde ich ansetzen.

Kannst Du die Karte denn einrichten?

http://de.opensuse.org/WLAN_Probleme

Was sagt denn
/sbin/lspci ?

Siehe auch:

http://www.prism54.org/

Greetz,

RM

[scheichlinux]

Hallo Rain Maker

Vielen Dank für die Tipps

lspci sagt:

02:02.0 Network controller: Intersil Corporation ISL3886 [Prism Javelin/Prism Xbow] (rev 01)

also lebt das Teil.


Den Google-Link habe ich durchverfolgt.
Danke nochmals; diese Spur hatte ich schon abgesucht

Vom Prism-Link (Danke) habe ich bereits den Treiber geholt den er jetzt geladen hatte.

(Die Installation mit ndiswrapper scheiterte auch)

Deshalb habe ich hier gepostet.


die hwinfo zeigt Folgendes:

27: PCI 202.0: 0282 WLAN controller
[Created at pci.300]
UDI: /org/freedesktop/Hal/devices/pci_1260_3886
Unique ID: rBUF.xzAIyb84Vs8
Parent ID: 6NW+.Wc+DHj8LOy0
SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:02.0
SysFS BusID: 0000:02:02.0
Hardware Class: network
Model: "Z-Com ISL3886 [Prism Javelin/Prism Xbow]"
Vendor: pci 0x1260 "Intersil Corporation"
Device: pci 0x3886 "ISL3886 [Prism Javelin/Prism Xbow]"
SubVendor: pci 0x17cf "Z-Com, Inc."
SubDevice: pci 0x0036
Revision: 0x01
Driver: "prism54"
Device File: eth0
Features: WLAN
Memory Range: 0xd0200000-0xd0201fff (rw,non-prefetchable)
IRQ: 11 (36901 events)
Module Alias: "pci:v00001260d00003886sv000017CFsd00000036bc02sc80 i00"
Driver Info #0:
Driver Status: prism54 is active
Driver Activation Cmd: "modprobe prism54"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #18 (PCI bridge)



Was kann ich noch tun?


Danke

tom

[UranusI]

hat einer eine Lösung bei Euch gefunden? ...