Re: Problem with wi in CURRENT (and 5.1)
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.7type=product=Client_Product ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with wi in CURRENT (and 5.1)
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 [EMAIL PROTECTED] 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.7type=product=Client_Product ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
RE: Problem with wi in CURRENT (and 5.1)
I am already running the latest firmware, and it works in 5.0 but not in 5.1 or 5-CURRENT. Is anyone going to take a look at this? It seems that wi is broken for a significant number of people (there have been several emails like mine recently to current and mobile) in 5.1+ -Rob -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David O'Brien Sent: 23 June 2003 17:26 To: Robert Hulme Cc: [EMAIL PROTECTED] 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?se ssion_id=1055265419.6837.7type=product=Client_Product ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problem with wi in CURRENT (and 5.1)
Thanks for the support :-D Pulling the card out, reinserting it and doing ifconfig sadly doesn't help me :( -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eirik Oeverby Sent: 23 June 2003 17:42 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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.7type=product=Client_Product ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with wi in CURRENT (and 5.1)
Hi. On Mon, Jun 23, 2003 at 06:34:00PM +0100, Robert Hulme wrote: I am already running the latest firmware, and it works in 5.0 but not in 5.1 or 5-CURRENT. Is anyone going to take a look at this? It seems that wi is broken for a significant number of people (there have been several emails like mine recently to current and mobile) in 5.1+ Most messages and all of the problems go away, when I use WITNESS in the Kernel. This seems to be a timing issue. Do you have WITNESS turned on or turned off in the Kernel? If it is not set, could you add options WITNESS to your kernel config and check if the problem is still there? - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with wi in CURRENT (and 5.1)
Hello. 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. The problem came up between June 7 and June 15 in -CURRENT. 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. I have an Orinoco Gold Card. HP Omnibook 500. ACPI disabled (the notebook has APM, with ACPI I don't see battery capacity). I tried with and without WEP. The network works fine for some time, then blocks for a while and starts working again. wi0: timeout in wi_cmd 0x0002; event status 0x8000 wi0: wi_cmd: busy bit won't clear. Looks similar at my Notebook: wi0: Lucent Technologies WaveLAN/IEEE at port 0x100-0x13f irq 10 function 0 config 1 on pccard0 wi0: 802.11 address: 00:02:2d:51:a2:35 wi0: using Lucent Technologies, WaveLAN/IEEE wi0: Lucent Firmware: Station (8.10.1) wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps wi0: bad alloc 21e != 207, cur 0 nxt 0 wi0: bad alloc 24b != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 26a != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 283 != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 29a != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 2b1 != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 2c8 != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 2df != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 2f6 != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 30d != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 324 != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 33b != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 352 != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 369 != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 380 != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 397 != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 3ae != 234, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 3c5 != 234, cur 0 nxt 0 wi0: device timeout [and further] complete dmesg, debugging output and stuff will be sent on request. I was silently hoping that others have this problem too and somebody cares, because I do not have any time to do anything at the moment. But at least I offer my help in giving hints. Thanx, Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
