[Prism54-users] device soft reset timed out on ixdp425

Luis R. Rodriguez mcgrof@ruslug.rutgers.edu
Sun, 1 Feb 2004 06:06:33 -0500


Hey,

I just completed the fix for this. Please try latest snapshot. I'm
actually on my 3com card now writing this e-mail ;)

	Luis

On Sat, Jan 31, 2004 at 12:32:24PM +0800, Lai Li wrote:
> hi~
> 
> i have change the wireless_tool on my embedded system ,and the error
> messge disappear.
> but my 802.11b/g mini-pci card is still not working.
> 
> when i try  patch-2.4.23-prism54-cvs20031217.bz2
> #dmesg
> Loaded prism54 driver, version 1.0.2.2
> eth0: islpci_open()
> eth0: resetting device...
> eth0: uploading firmware...
> remove_proc_entry: 00:03.0/loading busy, count=1
> remove_proc_entry: firmware/00:03.0 busy, count=1
> eth0: firmware uploaded done, now triggering reset..
> de_put: deferred delete of loading
> de_put: deferred delete of 00:03.0
> 
> but when i try patch-2.4.23-prism54-cvs20031221.bz2
> #dmesg
> Loaded prism54 driver, version 1.0.2.2
> eth0: islpci_open()
> eth0: resetting device...
> eth0: uploading firmware...
> eth0: firmware uploaded done, now triggering reset...
> 
> 
> but when i use wireless_tools on two of these patches,the card is still
> not working.
> 
> for example...
> #iwlist  eth0 scanning
> eth0      Failed to read scan data : Invalid argument
> 
> 
> by the way, i use the same card and latest cvs patch on my x86PC
> linux-2.4.24,
> the card is fine and working correctly.
> 
> ?b ??, 2004-01-30 22:15, Lai Li ?g?D?G
> 
> > hi~~
> > 
> > i try patch-2.4.23-prism54-cvs20031217.bz2 on my ixdp425
> > #modprob prism54
> > #ifconfig eth0 up
> > #ifconfig eth0
> > eth0      Link encap:Ethernet  HWaddr 00:00:00:00:00:00
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           Interrupt:26 Base address:0xc000
> > 
> > #iwconfig eth0
> > lo        no wireless extensions.
> > 
> > #dmesg
> > Loaded prism54 driver, version 1.0.2.2
> > eth0: islpci_open()
> > eth0: resetting device...
> > eth0: uploading firmware...
> > eth0: firmware uploaded done, now triggering reset...
> > eth0 (WE) : Buffer for request 8B1B too small (0<1)
> > 
> > it is vary strange!!
> > when i use iwconfig
> > eth0 (WE) : Buffer for request 8B1B too small (0<1) <-----it will show
> > in dmesg
> > and iwconfig can not find eth0.
> > 
> > i will try 1221 and 0115 patch later!!
> > 
> > ?b ??, 2004-01-30 10:39, Luis R. Rodriguez ?g?D?G 
> > 
> > > This seems to be a common problem. I think its not my device anymore and
> > > there's a bug at islpci_open / probe time. I'd say try an older driver
> > > for now and let us know your results. Which one? Try perhaps these:
> > > http://prism54.org/pub/linux/snapshot/tars/2003-12/prism54-cvs20031217.tar.bz2
> > > http://prism54.org/pub/linux/snapshot/tars/2003-12/prism54-cvs20031221.tar.bz2
> > > http://prism54.org/pub/linux/snapshot/tars/2004-01/prism54-cvs20040115.tar.bz2
> > > 
> > > I also see we must not have your card's subsytem IDs in our list. Can
> > > you please submit your lspci -v -v -v -n output to us and the cardname/model?
> > > 
> > > 	Luis
> > > 
> > > On Fri, Jan 30, 2004 at 10:34:19AM +0800, Lai Li wrote:
> > > > hi all
> > > > 
> > > > i have ixdp425, isl3890 minipci card and uclinux-2.4.22, 
> > > > and i use latest kernel patch from cvs.
> > > > 
> > > > when ifconfig eth0 up,the message i saw is at below.....
> > > > 
> > > > <46>Jan  1 00:01:37 klogd: Loaded prism54 driver, version 1.0.2.2
> > > > <47>Jan  1 00:01:37 klogd: eth0: prism54 driver detected card model:
> > > > PRISM Duette/GT
> > > > <47>Jan  1 00:01:37 klogd: eth0: islpci_open()
> > > > <47>Jan  1 00:01:37 klogd: eth0: resetting device...
> > > > <47>Jan  1 00:01:37 klogd: eth0: uploading firmware...
> > > > <47>Jan  1 00:01:37 klogd: eth0: firmware uploaded done, now triggering
> > > > reset...
> > > > <43>Jan  1 00:01:47 klogd: eth0: device soft reset timed out
> > > > 
> > > > what should i do??
> > > > thx