Re: wpi and firmware error
On Tue, Aug 04, 2009 at 11:13:04AM -0400, Luis Useche wrote: > I downgraded the firmware to version 3.1 and so far the problem is gone. Whether I'm using firmware version 3.1 with OpenBSD 4.5 (or 2.14.1.5 with OpenBSD 4.3 and 4.4), I get the firmware errors when I'm connected to the wireless access points at my university. But with the access points that I've tried at home and at airports, wpi appears to work fine. For me, the errors appear to be specific to certain access points, but independent of the firmware version.
Re: wpi and firmware error
I downgraded the firmware to version 3.1 and so far the problem is gone. Luis Useche use...@gmail.com On Sun, Aug 2, 2009 at 9:16 PM, Matthew Szudzik wrote: > On Sun, Aug 02, 2009 at 09:03:37PM -0400, Luis Useche wrote: >> From time to time my network card stop working and a error message appears: >> >> wpi0: fatal firmware error > > I've been experiencing the same problem for about a year--ever since my > university installed new access points. The old access points worked > fine with wpi, but the new access points cause frequent firmware errors. > Some days I just give up on wireless and connect an ethernet cable...
Re: wpi and firmware error
On Sun, Aug 02, 2009 at 09:03:37PM -0400, Luis Useche wrote: > From time to time my network card stop working and a error message appears: > > wpi0: fatal firmware error I've been experiencing the same problem for about a year--ever since my university installed new access points. The old access points worked fine with wpi, but the new access points cause frequent firmware errors. Some days I just give up on wireless and connect an ethernet cable...
wpi and firmware error
Hello, >From time to time my network card stop working and a error message appears: wpi0: fatal firmware error firmware error log (count=1): error type = "SYSASSERT" (0x0005) error data = 0x0074 branch link = 0x08B60274 interrupt link = 0x03203560 time= 3916204702 driver status: tx ring 0: qid=0 cur=19 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=0 queued=0 tx ring 4: qid=4 cur=19 queued=0 tx ring 5: qid=5 cur=0 queued=0 rx ring: cur=6 802.11 state 4 The network start working again when I call dhclient. Since I could have my network back again pretty quickly is not a critical issue. However, having the problem is annoying. I am using wpi-firmware-3.2.tgz Does any one else have this problem? Best, Luis Useche use...@gmail.com
