Date: Mon, 23 Jun 2003 18:41:43 +0200 From: Eirik Oeverby <ltning@anduin.net> To: freebsd-current@freebsd.org Cc: rob@robhulme.com Subject: Re: Problem with wi in CURRENT (and 5.1) Message-ID: <20030623184143.14331d23.ltning@anduin.net> In-Reply-To: <20030623162611.GA54473@dragon.nuxi.com> References: <000201c334bd$f4092850$0b07a8c0@hal9000> <20030623162611.GA54473@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=.mkypNLd6eVPb+X Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, this is exactly the problem I have with my wi-driven card aswell. I have a pretty standard Lucent card (Orinoco Silver, 64bit), PCMCIA, in my ThinkPad T21 (see another thread specifically about that machine and its issues with 5.1). It will work for a while, then start spitting out error messages like wi0: bad alloc 55c != 2a2, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 573 != 2a2, cur 0 nxt 0 wi0: device timeout and wi0: timeout in wi_seek to fc02/0 wi0: timeout in wi_seek to fc03/0 and ofcourse the messages you describe. Pulling the card out and re-inserting it, then ifconfig, brings it back to life for a few minutes or as much as half an hour or so. At first I thought it was a signal level problem, but it's not. I also thought it's an encryption problem, but that's not it either. So I'm really confused - it worked perfectly for weeks on end with 4.8, and now in 5.1/CURRENT it screws me over like this. Firmware is at the latest level. Just my two cents to confirm your story ;) /Eirik On Mon, 23 Jun 2003 09:26:11 -0700 "David O'Brien" <freebsd-current@freebsd.org> wrote: > On Tue, Jun 17, 2003 at 11:48:13AM +0100, Robert Hulme wrote: > > I'm having some problems with wi in 5-CURRENT and 5.1 in general. > > I'm using a Proxim Skyline 802.11b PC Card (which I believe uses the > > Prism 2 chipset). The PC Card is using the 0.3.0 primary and 0.8.3 > > secondary firmware (which I believe is the latest). I have a Dell > > Inspiron 8200. > > > > The card works fine in Windows XP and FreeBSD 5.0, but in 5.1 if I > > use ifconfig to bring up the card (for example during boot) it locks > > my laptop up for about a minute while I get loads of error messages > > appear on screen. Eventually I get a 'init failed' and 'tx buffer > > allocation failed (error 12)' error, and although ifconfig says the > > interface is up it doesn't actually work. > > See if there isn't updated firmware for your card. Rumor has it the > MS-Windows driver uploads the latest firmware version into the RAM on > the card. > > For Lucent cards you want any versoin 8 firmware from > http://www.expressresponse.com/cgi-bin/proxim02/showFaq.cgi?session_id=1055265419.6837.7&type=&product=Client_Product > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" --=.mkypNLd6eVPb+X Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+9y3HdAvR8ct7fEcRAkOMAJ42hTtsX4F35rZSCgQPK9zlwt9DLQCeIBgz Lo7ohNANLKHrRTftPVeJw40= =uEE8 -----END PGP SIGNATURE----- --=.mkypNLd6eVPb+X--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030623184143.14331d23.ltning>