From owner-freebsd-current@FreeBSD.ORG Tue Nov 6 17:32:08 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD07716A417 for ; Tue, 6 Nov 2007 17:32:08 +0000 (UTC) (envelope-from frankstaals@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 4A77613C4B8 for ; Tue, 6 Nov 2007 17:32:08 +0000 (UTC) (envelope-from frankstaals@gmx.net) Received: (qmail invoked by alias); 06 Nov 2007 17:32:05 -0000 Received: from ip176-173-59-62.adsl.versatel.nl (EHLO Rena.FStaals.net) [62.59.173.176] by mail.gmx.net (mp057) with SMTP; 06 Nov 2007 18:32:05 +0100 X-Authenticated: #25365336 X-Provags-ID: V01U2FsdGVkX1/loA1UuEvl0KapqMdmKMCtnqcxEwYASkO9PTg4qk bjinLv03J7ZJ8R Message-ID: <4730A4E1.8090006@gmx.net> Date: Tue, 06 Nov 2007 18:31:13 +0100 From: Frank Staals User-Agent: Thunderbird 2.0.0.6 (X11/20070929) MIME-Version: 1.0 To: Sam Leffler References: <472A6708.9030109@clearchain.com> <472B779B.9060002@gmx.net> <472B9597.2050108@clearchain.com> <473082C5.5080700@gmx.net> <4730A1D1.8020607@errno.com> In-Reply-To: <4730A1D1.8020607@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Mailman-Approved-At: Tue, 06 Nov 2007 17:53:26 +0000 Cc: freebsd-current , Benjamin Close Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 06 Nov 2007 17:32:08 -0000 Sam Leffler wrote: > Frank Staals wrote: >> Benjamin Close wrote: >>> Frank Staals wrote: >> >>>> >>>> >>>> >>>> Everything works fine with the connection itself. Allthough >>>> sometimes when switching from tty9 to tty0 and back the system >>>> locks up. I've had it before when switching from tty1 to tty0. >>>> Anyone with the same problems ? >>>> >>>> Anyway; Great work on the driver so far :D >>>> >>> I've similar issues and believe it might be due to the amount of >>> kernel printfs that are happening. Can you sysctl debug.wpi=0 and >>> see if the problem still exists? >>> By chance are you using ZFS? I caught a memory modified after free >>> panic in zfs the other day pid was from syslogd. I'm trying to work >>> out if it's related. >>> >>> Cheers, >>> Benjamin >>> >> When setting debug.wpi to 0 it seems like the problem is gone. I'm >> not using ZFS by the way. I did have a problem connecting to the AP >> at my university though; the driver wouldn't assosicate whatever I >> tried. I didn't have a chance to do some extensive testing though. It >> might be because of the WEP+wpa_supplicant + ca certificate method >> that is required to authenticate. Anyway I'll let it know if there is >> an actual problem with the driver itself > > Rule of thumb in debugging wireless issues (and most others for that > matter): simplify your config if at all possible. In this case try > checking things out w/o wpa_supplicant (i.e. no crypto). > > When debugging, start at the top and work your way down to rule out > problems at each layer. In this case collect a wpa_supplicant debug > log first, then check for issues at the net80211 layer (wlandebug, > wlanstats, etc.), then finally check at the driver level. > > Sam > For at home wpi is working fine, and I indeed used the method you described above. Unfortunately I don't have the luxury of that extended testing methods at my university since I can't turn off encryption and the weird authentication methods there ;) -- -Frank Staals