[Prism54-users] RE: Z-com XG-600 and prism54 (bit longer, sorry)

Thu, 12 Feb 2004 18:59:34 +0000

Hello,
Am Donnerstag, 12. Februar 2004 01:49 schrieb Jianpeng Dong:

> 1. You need to download the lastest wireless extension tools.
ok. it seems to be the v15 extensions, because I am using a 2.4.22 kernel
Therefore it is a mandrake issue. Dont know if this might be a problem with
the loading of the firmware...
> 2. did you put the firmware in the right place?
It is on the right place and named "isl3890" as said in the ReadMe. So I
think this cant be the prob. here. Anyway, it is finally loaded, it seems
after dhclient runs. ?-)

thomas
> 
> JP

> Hello,
> 
> with all the postings I found here and in the forums, I managed to get my
> Z-com XG-600 (built-in in laptop) to work fine with Mandrake 9.2 and the
> prism54 driver.
> 
> firmware: 1.0.4.3
> kernel: 2.4.22-26mdk
> prism54-driver: 04/02/01
> wireless-tools: 26-1mdk
> 
> Nontheless, there are some "issues". Perhaps someone can give an advice...
> 
> 1. With iwconfig eth1 the following is displayed:
> 
> Warning: Driver for device eth1 recommend version 16 of Wireless
> Extension, but has been compiled with version 15, therefore some driver
> features may not be available...
> 
> Is it a mandrake package problem?
> 
> 2. While doing the "service network start" ifup of the device lasts very
> long with the following in /var/log/syslog:
> 
> Feb 10 11:41:51 laptom kernel: eth1: islpci_open()
> Feb 10 11:41:51 laptom kernel: eth1: resetting device...
> Feb 10 11:41:51 laptom kernel: eth1: uploading firmware...
> Feb 10 11:42:01 laptom kernel: prism54: request_firmware() failed for
> 'isl3890'
> Feb 10 11:42:01 laptom kernel: eth1: could not upload firmware ('isl3890')
> Feb 10 11:42:01 laptom ifplugd(eth1)[3718]: Using interface
> eth1/00:60:B3:98:76:7C
> Feb 10 11:42:01 laptom kernel: eth1: islpci_open()
> Feb 10 11:42:01 laptom kernel: eth1: resetting device...
> Feb 10 11:42:01 laptom kernel: eth1: uploading firmware...
> Feb 10 11:42:11 laptom kernel: prism54: request_firmware() failed for
> 'isl3890'
> Feb 10 11:42:11 laptom kernel: eth1: could not upload firmware ('isl3890')
> Feb 10 11:42:11 laptom kernel: eth1: islpci_open()
> Feb 10 11:42:11 laptom kernel: eth1: resetting device...
> Feb 10 11:42:11 laptom kernel: eth1: uploading firmware...
> Feb 10 11:42:21 laptom kernel: prism54: request_firmware() failed for
> 'isl3890'
> Feb 10 11:42:21 laptom kernel: eth1: could not upload firmware ('isl3890')
> Feb 10 11:42:21 laptom kernel: eth1: islpci_open()
> Feb 10 11:42:21 laptom kernel: eth1: resetting device...
> Feb 10 11:42:21 laptom kernel: eth1: uploading firmware...
> Feb 10 11:42:31 laptom kernel: prism54: request_firmware() failed for
> 'isl3890'
> Feb 10 11:42:31 laptom kernel: eth1: could not upload firmware ('isl3890')
> Feb 10 11:42:31 laptom kernel: eth1: islpci_open()
> Feb 10 11:42:31 laptom kernel: eth1: resetting device...
> Feb 10 11:42:31 laptom kernel: eth1: uploading firmware...
> Feb 10 11:42:41 laptom kernel: prism54: request_firmware() failed for
> 'isl3890'
> Feb 10 11:42:41 laptom kernel: eth1: could not upload firmware ('isl3890')
> Feb 10 11:42:41 laptom ifplugd(eth1)[3718]: Using detection mode: wireless
> extension
> Feb 10 11:42:41 laptom ifplugd(eth1)[3718]: ifplugd 0.15 successfully
> initialized, link beat detected.
> Feb 10 11:42:41 laptom ifplugd(eth1)[3718]: Executing
> '/etc/ifplugd/ifplugd.action eth1 up'.
> Feb 10 11:42:42 laptom kernel: eth1: islpci_open()
> Feb 10 11:42:42 laptom kernel: eth1: resetting device...
> Feb 10 11:42:42 laptom kernel: eth1: uploading firmware...
> Feb 10 11:42:51 laptom ifplugd(eth1)[3718]: Killing child.
> Feb 10 11:42:51 laptom ifplugd(eth1)[3718]: client: Determining IP
> information for eth1...
> Feb 10 11:42:51 laptom ifplugd(eth1)[3718]: Program execution failed,
> return value is 0.
> Feb 10 11:42:51 laptom ifplugd(eth1)[3718]: Exiting.
> Feb 10 11:42:51 laptom network: Schnittstelle ťeth1Ť aktivieren:  failed
> Feb 10 11:42:52 laptom kernel: prism54: request_firmware() failed for
> 'isl3890'
> Feb 10 11:42:52 laptom kernel: eth1: could not upload firmware ('isl3890')
> Feb 10 11:42:52 laptom dhclient: receive_packet failed on eth1: Network is
> down
> Feb 10 11:42:56 laptom dhclient: DHCPREQUEST on eth1 to 255.255.255.255
> port 67
> Feb 10 11:42:56 laptom dhclient: send_packet: Network is down
> Feb 10 11:43:03 laptom dhclient: DHCPREQUEST on eth1 to 255.255.255.255
> port 67
> Feb 10 11:43:03 laptom dhclient: send_packet: Network is down
> Feb 10 11:43:15 laptom dhclient: DHCPDISCOVER on eth1 to 255.255.255.255
> port 67 interval 6
> Feb 10 11:43:15 laptom dhclient: send_packet: Network is down
> Feb 10 11:43:21 laptom dhclient: DHCPDISCOVER on eth1 to 255.255.255.255
> port 67 interval 9
> Feb 10 11:43:21 laptom dhclient: send_packet: Network is down
> Feb 10 11:43:30 laptom dhclient: DHCPDISCOVER on eth1 to 255.255.255.255
> port 67 interval 15
> Feb 10 11:43:30 laptom dhclient: send_packet: Network is down
> Feb 10 11:43:45 laptom dhclient: DHCPDISCOVER on eth1 to 255.255.255.255
> port 67 interval 11
> Feb 10 11:43:45 laptom dhclient: send_packet: Network is down
> Feb 10 11:43:56 laptom dhclient: DHCPDISCOVER on eth1 to 255.255.255.255
> port 67 interval 14
> Feb 10 11:43:56 laptom dhclient: send_packet: Network is down
> Feb 10 11:44:10 laptom dhclient: DHCPDISCOVER on eth1 to 255.255.255.255
> port 67 interval 6
> Feb 10 11:44:10 laptom dhclient: send_packet: Network is down
> Feb 10 11:44:16 laptom dhclient: No DHCPOFFERS received.
> Feb 10 11:44:16 laptom dhclient: Trying recorded lease 192.168.2.102
> Feb 10 11:44:16 laptom kernel: eth1: islpci_open()
> Feb 10 11:44:16 laptom kernel: eth1: resetting device...
> Feb 10 11:44:16 laptom kernel: eth1: uploading firmware...
> Feb 10 11:44:16 laptom kernel: eth1: firmware uploaded done, now
> triggering reset...
> Feb 10 11:44:18 laptom dhclient: bound: renewal in 1071070189 seconds.
> 
> It seems that there are probs with loading the firmware. Is it a
> driver/firmware issue? Can I do to improve on that? The card is finally
> running.
> 
> Any hints would be apreciated.
> 
> Thanks,
> 
> Thomas
> 
> _______________________________________________
> Prism54-users mailing list
> Prism54-users@prism54.org
> http://prism54.org/mailman/listinfo/prism54-users