From owner-freebsd-current@FreeBSD.ORG Thu Dec 16 03:08:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B64216A4CE for ; Thu, 16 Dec 2004 03:08:26 +0000 (GMT) Received: from out010.verizon.net (out010pub.verizon.net [206.46.170.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8123743D2D for ; Thu, 16 Dec 2004 03:08:25 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen ([70.21.161.195]) by out010.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041216030824.YUQV24714.out010.verizon.net@RabbitsDen>; Wed, 15 Dec 2004 21:08:24 -0600 From: "Alexandre \"Sunny\" Kovalenko" To: Sam Leffler In-Reply-To: <20041212184020.W3369@ync.qbhto.arg> References: <41BBA812.2030006@errno.com> <20041212184020.W3369@ync.qbhto.arg> Content-Type: text/plain; charset=iso-8859-5 Date: Wed, 15 Dec 2004 22:07:12 -0500 Message-Id: <1103166432.995.15.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit X-Authentication-Info: Submitted using SMTP AUTH at out010.verizon.net from [70.21.161.195] at Wed, 15 Dec 2004 21:08:24 -0600 cc: current@freebsd.org Subject: Re: WEP and 802.11 drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Dec 2004 03:08:26 -0000 On Sun, 2004-12-12 at 18:41 -0800, Doug Barton wrote: > On Sat, 11 Dec 2004, Sam Leffler wrote: > > > I've been able to reproduce some of the problems people are having. Until I > > can fix them please try building wlan and wlan_wep into your kernel so the > > cipher module isn't loaded on the fly. I believe that should eliminate the > > double fault panic and various related traps. > > I didn't even have a chance to report this, but I was getting this > problem with the ndis driver. Your fix worked, thanks for suggesting it. > > Doug > Since adding wlan_wep to the kernel config, I do not have traps and double faults, but neither I have wireless connectivity -- card gets configured and claims to associate, occasionally I even get as far as obtaining address via DHCP, but that is all I can get. Intermittently I get 'host is down' from ping. At that point, ifconfig would show 'status' as 'no carrier'. I have observed this with both Prism2-based cards (using wi driver) and Broadcom based with ndis wrapper. Presence or absence of WEP does not seem to make a difference. Since your E-mail sounded like work-in-progress, I was not sure whether additional details are needed, however, if they are, please let me know and I will be happy to furnish them. -- Alexandre "Sunny" Kovalenko (Олександр Коваленко)