From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 15:25:18 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DCE1B991; Sun, 31 Mar 2013 15:25:18 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) by mx1.freebsd.org (Postfix) with ESMTP id 94DCE75; Sun, 31 Mar 2013 15:25:18 +0000 (UTC) Received: by mail-yh0-f53.google.com with SMTP id q3so238644yhf.12 for ; Sun, 31 Mar 2013 08:25:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ug8KR1XhFeLTKkUmnIbjsw8IFiEMJr3kcIJh8fcQYQE=; b=NWpznTDutotB62jaEcKKgHCgAw9og4wUX+0C8QPdi5SCaJllmHu9MhEjNEqbifdqUL rwm1jNmzEN1Uk0kExE2/CxYLqyddSl2Mk48t6Xj5t2CpbrOaBHS7SzxlRzjafTAi1uez uG1IaKdVh4DjOu2kt+328+RL1hEfFNK//jM08GFAPcAgcg/zvIGzBpypsp99zGIJlZ9+ y99WR+8pe5d8Iiq0nxGdIkj2aTz4Y9IafELiOjRw5J2K15Z3t2n0qWdWP0eQx/eb9a0A X0H3vs8eQb/QwnTDVU9V4xA3U1YGjrf6sPWgl58x0iQLACMD04zWmfjB+6lvwDcxdGDk F3ig== X-Received: by 10.236.92.241 with SMTP id j77mr6542765yhf.147.1364743518158; Sun, 31 Mar 2013 08:25:18 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id 30sm19261491yhb.6.2013.03.31.08.25.17 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 31 Mar 2013 08:25:17 -0700 (PDT) Message-ID: <51585558.8040202@gmail.com> Date: Sun, 31 Mar 2013 10:25:12 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <51578BAC.4090608@gmail.com> <515826B9.6070509@gmail.com> In-Reply-To: <515826B9.6070509@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Mar 2013 15:25:18 -0000 I tried updating today to the new code, it seemed to make it worse and never get decent ping times. With the code from before, it's dependent on boot, either it will work fine on boot or fail. But it has to be related to the "handled npkts 0" message. When I'm getting no messages, it's perfect. The number and speed of the messages is the inverse of the network quality. When it's an intermittent loss, it degrades a couple seconds before the messages start. On 3/31/2013 7:06 AM, Joshua Isom wrote: > If I drop down to one 8Gb stick, and I don't have other wifi devices > near causing interference, I can get a reliable connection and low loss. > If I have 16Gb, I can get about a minute or two of decent ping times > before it degrades to multi-second pings of the router. Even at 8Gb, > it's not guaranteed on boot, but rebooting does seem to fix it. At > 16Gb, I tried two different sticks just to see if maybe it was one bad > chip but it didn't change it. That means it's probably an address > conflict, or cache size issue, right? > > On 3/31/2013 1:25 AM, Adrian Chadd wrote: >> does downgrading the motherboard/ram fix it? >> >> You were already running 64 bit, right? What if you just boot with 2gb >> of ram? >> >> >> >> >> adrian >>