1.7.4 firmware as S-record, finally

Jared Brokaw jared at broadbandcentral.us
Tue Jul 1 19:10:20 EDT 2003


I should clarify:

1: When I used 1.7.4, I was unable to associate any clients with the AP.
The AP would constantly pop in and out of existance.  The card behaved as
thought it were constantly resetting itself as soon as it was finished
initalizing.

2: We were on sta firmware 1.4.9 and were seeing the error messages below in
the logs.  After about 24-48 hours, clients could no longer associate.  As
existing clients would disassociate, no more would come on so eventually the
mac table in the card would go to a count of 0 clients.

3: I have recently flashed several of our cards with 1.5.6 in the intrerest
of solving the problem we are seeing in 1.4.9.  My gut tells me we are
hitting up against some kind of performance barrier of the intersil firmware
or chipset.

Many thanks to Pavel Roskin for his comments briefly after sending this out!

jb


----- Original Message ----- 
From: "Jared Brokaw" <jared at broadbandcentral.us>
To: <hostap at shmoo.com>
Sent: Tuesday, July 01, 2003 4:50 PM
Subject: Re: 1.7.4 firmware as S-record, finally


> I am using the senao cards and when I flashed to 1.7.4, the cards would no
> longer function adequately in hostap mode under freebsd.  I'm not sure at
> this point if that is some kind of incompatability between the freebsd
> driver and the 1.7.4 firmware, but it definitely didn't work, I use
multiple
> clients to test.  I had to revert to 1.5.6.  I'm hoping this firmware
solves
> a problem we are seeing when having between 70 and 90 users on the radio.
> About every 24 to 48 hours, the thing starts spewing the following in the
> syslog:
>
> May 28 06:48:06 host /kernel: wi0: timeout in wi_seek to fc85/0; last
> status 800b
> May 28 06:48:06 host /kernel: wi0: timeout in wi_seek to fc28/0; last
> status 800b
> May 28 06:48:06 host /kernel: wi0: timeout in wi_seek to fc23/0; last
> status 800b
> May 28 06:48:06 host /kernel: wi0: timeout in wi_seek to fc24/0; last
> status 800b
> May 28 06:48:06 host /kernel: wi0: timeout in wi_seek to fc80/0; last
> status 800b
> May 28 06:48:06 host /kernel: wi0: wi_cmd: busy bit won't clear.
> May 28 06:48:06 host /kernel: wi0: wi_cmd: busy bit won't clear.
> May 28 06:48:06 host /kernel: wi0: failed to allocate 1594 bytes on NIC
> May 28 06:48:06 host /kernel: wi0: tx buffer allocation failed
> May 28 06:48:06 host /kernel: wi0: wi_cmd: busy bit won't clear.
> May 28 06:48:06 host /kernel: wi0: failed to allocate 1594 bytes on NIC
> May 28 06:48:06 host /kernel: wi0: mgmt. buffer allocation failed
> May 28 06:48:06 host /kernel: wi0: wi_cmd: busy bit won't clear.
> May 28 06:48:06 host /kernel: wi0: xmit failed
>
> I guess we'll see.  Since I've seen similar problems with linux drivers
and
> these cards, and since the firmware prior to 1.4.9 was complete garbage,
I'm
> concluding these problems lie within the firmware.  If not, I can rewrite
> the driver, but before I put that effort into it, I thought I would at
least
> try the 1.5.6 first.  Anyone here using BSD seen this on or after
sta1.4.9?
> Thanks!!!
>
> jb
>
> ----- Original Message ----- 
> From: "Pavel Roskin" <proski at gnu.org>
> To: <hostap at shmoo.com>
> Sent: Tuesday, July 01, 2003 3:50 PM
> Subject: 1.7.4 firmware as S-record, finally
>
>
> > Hello!
> >
> > I've just noticed that Intersil firmware 1.7.4 is available here:
> > http://www.netgate.com/support/prism_firmware/
> >
> > Only flashable firmware for Prism 2.5 chipset is available
(sf010704.hex).
> > I tried to flash it by prism2_srec, and it worked.
> >
> > -- 
> > Regards,
> > Pavel Roskin
> > _______________________________________________
> > HostAP mailing list
> > HostAP at shmoo.com
> > http://lists.shmoo.com/mailman/listinfo/hostap
> >
> >
>
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>
>



More information about the HostAP mailing list