From owner-freebsd-mobile@FreeBSD.ORG Thu Aug 14 22:39:32 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A27B37B401 for ; Thu, 14 Aug 2003 22:39:32 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C22EF43FA3 for ; Thu, 14 Aug 2003 22:39:31 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9/8.12.3) with ESMTP id h7F5ZjFL025157; Thu, 14 Aug 2003 23:35:45 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 14 Aug 2003 23:36:55 -0600 (MDT) Message-Id: <20030814.233655.35978822.imp@bsdimp.com> To: cjclark@alum.mit.edu, cristjc@comcast.net From: "M. Warner Losh" In-Reply-To: <20030814235432.GA85523@blossom.cjclark.org> References: <20030814235432.GA85523@blossom.cjclark.org> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: Linksys WPC11 v4 and Netgear MA401RA Troubles X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Aug 2003 05:39:32 -0000 In message: <20030814235432.GA85523@blossom.cjclark.org> "Crist J. Clark" writes: : At first, nothing was working at all until I learned the magical, : hw.cbb.start_memory="0x2000000", incantation. Now NEWCARD actually : works. 0x20000000 might be too low. I typically see this set to 0xfxxxxxxx. : I found my MA401 seems to work fine with OLDCARD on both 5.1 and : 4.8. At least, it gets loaded up and ifconfig(8) sees it fine. Since : I've only ever had one card working, I don't have much of a network to : test on yet. Cool. : However, the MA401 is making trouble in NEWCARD, as in the system : locks up. Locks up hard. The only way out is to power cycle. Before I : found the miracle of hw.cbb.start_memory, the card didn't work, but it : didn't lock up the system either. The debug output looked like, I don't understand why this isn't working for you, unless you don't have wi in your generic kernel for some reason. 5.1 should have support for this card. I know that current does, and cvs seems to tell me that 5.1 should also. Warner