From owner-freebsd-questions@FreeBSD.ORG Wed Aug 9 15:47:37 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEC0F16A4DF; Wed, 9 Aug 2006 15:47:37 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1469343D69; Wed, 9 Aug 2006 15:47:36 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from localhost (jn@ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id k79FlZuv068213; Wed, 9 Aug 2006 08:47:36 -0700 (PDT) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-questions@freebsd.org Date: Wed, 9 Aug 2006 11:47:32 -0400 User-Agent: KMail/1.9.3 References: <44DA01D0.8070107@gmx.net> In-Reply-To: <44DA01D0.8070107@gmx.net> X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608091147.32939.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on ns1.jnielsen.net X-Virus-Status: Clean Cc: questions@freebsd.org, Frank Staals Subject: Re: Ndis + Netgear WG311v3 ; Won't attach device correctly X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2006 15:47:37 -0000 On Wednesday 09 August 2006 11:40, Frank Staals wrote: > The only thing changed since the first time I loaded the module was I > copied it to /boot/kernel and I added WG311v3XP_sys_load="YES" to > /boot/loader.conf but those changes shouldn't have effect on not > correctly loading it I think. This is the key. I can't remember where I read it but this is a documented caveat of the ndis driver. Windows doesn't typically invoke network drivers until after the system is loaded, so some drivers won't work in FreeBSD unless they're loaded after the system is up. So take the line out of /boot/loader.conf, test that the driver works correctly if you reboot and kldload it manually, then make an rc script or something to automatically load the driver later in the boot process. JN