Re: Can't connect to wireless network with recent -CURRENT
On Thursday, 3 July 2003 at 16:33:30 +0200, Harti Brandt wrote: On Thu, 3 Jul 2003, M. Warner Losh wrote: MWLIn message: [EMAIL PROTECTED] MWLHarti Brandt [EMAIL PROTECTED] writes: MWL: I think the same problem was reported by Rob Holmes two weeks ago and by MWL: me (although with lesser detail) yesterday. I converted my kernel from MWL: OLDBUS to NEWBUS and now one out of four or five tries the card works, but MWL: this is really annoying. I have an Inspiron 8200 and an Avaya (that is a MWL: Lucent) card. I have found no solution until now. MWL MWLThe lucent problem is well known and has been known for a long time. MWLIt was broken between 5.0 and 5.1 for some people with lucent cards MWL(not me and mine). Enabling WITNESS seens to help, but that likely MWLmeans that it is a race that the overhead of WITNESS tickles in MWLcertain ways. Sam indicated he'd try to find some time to fix it. MWLThere's something subtle going on with the lucent cards, and I've MWLgiven up trying to find it. I just do't have the time. Updating the firmware from www.agere.com to 8.72.1 has cured the problem (except for two messages from the kernel): Jul 3 16:09:05 harti kernel: wi0: bad alloc 204 != 201, cur 0 nxt 0 Jul 3 16:09:09 harti kernel: wi0: bad alloc 208 != 205, cur 0 nxt 0 Hmm. I'd look on that as a workaround, not a fix. The driver shouldn't become more sensitive towards microcode revisions. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: Can't connect to wireless network with recent -CURRENT
On Thu, 3 Jul 2003, Greg 'groggy' Lehey wrote: GgLI've just upgraded my laptop to a recent -CURRENT, and since then I've GgLbeen having a lot of network problems. Here's a rough chronology: GgL GgL- Machine is a Dell Inspiron 7500, which I've been using with releases GgL 4 and 5 of FreeBSD without problems for the last 3 years. It's GgL usually connected to my house 802.11b network, which is run by an GgL old 486 in ad-hoc mode, no WEP. I use DHCP to set up the GgL connection. GgL GgL- Things worked fine up to my last kernel: GgL GgL Jun 26 14:03:43 kondoparinga kernel: FreeBSD 5.0-CURRENT #0: Sun May 11 13:25:03 CST 2003 GgL GgL- On 28 June, I upgraded to the then -CURRENT. I had a lot of trouble GgL getting things working, including the following from the gateway GgL machine: GgL GgL Jun 29 09:35:15 air-gw dhcpd: DHCPREQUEST for 192.109.197.199 from 00:02:2d:04:09:3a via wi0 GgL Jun 29 09:35:15 air-gw dhcpd: DHCPACK on 192.109.197.199 to 00:02:2d:04:09:3a via wi0 GgL Jun 29 09:35:16 air-gw dhcpd: DHCPDECLINE on 192.109.197.199 from 00:02:2d:04:09:3a via wi0 GgL Jun 29 09:35:16 air-gw dhcpd: Abandoning IP address 192.109.197.199: declined. GgL Jun 29 09:35:16 air-gw dhcpd: DHCPDISCOVER from 00:02:2d:04:09:3a via wi0 GgL Jun 29 09:35:16 air-gw dhcpd: DHCPOFFER on 192.109.197.199 to 00:02:2d:04:09:3a via wi0 GgL GgL Nothing was mentioned in the log files on the laptop. GgL GgL- I managed to connect, however, and things worked for a while, but GgL the machine kept freezing. I tried with a 100 Mb/s Ethernet card, GgL and it had problems too. With both network cards, it reported GgL various error messages which I didn't write down because I thought GgL they would be logged; unfortunately they weren't. The one from wi0 GgL is still occurring: GgL GgL wi0: bad alloc 3b4 != ff, cur 0 nxt 0 GgL GgL- I built a new kernel and world on 1 July. Since then I haven't had GgL any trouble with the system freezing up, but and was no longer able GgL to connect at all with the wireless card. After booting, I get: GgL GgL wi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 GgLinet6 fe80::202:2dff:fe04:93a%wi0 prefixlen 64 scopeid 0x3 GgLinet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 GgLether 00:02:2d:04:09:3a GgLmedia: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps) GgLstatus: associated GgLssid Netname 1:Netname GgLstationname FreeBSD WaveLAN/IEEE node GgLchannel 3 authmode OPEN powersavemode OFF powersavesleep 100 GgLwepmode OFF weptxkey 1 GgL GgL However, no traffic comes through. GgL GgLIt's pretty clear that it's this laptop: I have other machines on the GgLnet which work without problems, and this machine also works if I boot GgLit with 4.8-STABLE. GgL GgLAny thoughts? I think the same problem was reported by Rob Holmes two weeks ago and by me (although with lesser detail) yesterday. I converted my kernel from OLDBUS to NEWBUS and now one out of four or five tries the card works, but this is really annoying. I have an Inspiron 8200 and an Avaya (that is a Lucent) card. I have found no solution until now. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't connect to wireless network with recent -CURRENT
In message: [EMAIL PROTECTED] Harti Brandt [EMAIL PROTECTED] writes: : I think the same problem was reported by Rob Holmes two weeks ago and by : me (although with lesser detail) yesterday. I converted my kernel from : OLDBUS to NEWBUS and now one out of four or five tries the card works, but : this is really annoying. I have an Inspiron 8200 and an Avaya (that is a : Lucent) card. I have found no solution until now. The lucent problem is well known and has been known for a long time. It was broken between 5.0 and 5.1 for some people with lucent cards (not me and mine). Enabling WITNESS seens to help, but that likely means that it is a race that the overhead of WITNESS tickles in certain ways. Sam indicated he'd try to find some time to fix it. There's something subtle going on with the lucent cards, and I've given up trying to find it. I just do't have the time. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't connect to wireless network with recent -CURRENT
On Thu, 3 Jul 2003, M. Warner Losh wrote: MWLIn message: [EMAIL PROTECTED] MWLHarti Brandt [EMAIL PROTECTED] writes: MWL: I think the same problem was reported by Rob Holmes two weeks ago and by MWL: me (although with lesser detail) yesterday. I converted my kernel from MWL: OLDBUS to NEWBUS and now one out of four or five tries the card works, but MWL: this is really annoying. I have an Inspiron 8200 and an Avaya (that is a MWL: Lucent) card. I have found no solution until now. MWL MWLThe lucent problem is well known and has been known for a long time. MWLIt was broken between 5.0 and 5.1 for some people with lucent cards MWL(not me and mine). Enabling WITNESS seens to help, but that likely MWLmeans that it is a race that the overhead of WITNESS tickles in MWLcertain ways. Sam indicated he'd try to find some time to fix it. MWLThere's something subtle going on with the lucent cards, and I've MWLgiven up trying to find it. I just do't have the time. Updating the firmware from www.agere.com to 8.72.1 has cured the problem (except for two messages from the kernel): Jul 3 16:09:05 harti kernel: wi0: bad alloc 204 != 201, cur 0 nxt 0 Jul 3 16:09:09 harti kernel: wi0: bad alloc 208 != 205, cur 0 nxt 0 harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
