Date: Fri, 14 Aug 2015 10:41:33 -0700 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Thomas Mueller <mueller6724@bellsouth.net>, Gleb Smirnoff <glebius@freebsd.org> Subject: Re: CFT: ndis(4) testers needed! Message-ID: <2028674.06lC1bRjxX@ralph.baldwin.cx> In-Reply-To: <632901.91790.bm@smtp116.sbc.mail.ne1.yahoo.com> References: <20150731121226.GJ889@FreeBSD.org> <20150813070713.GE75813@glebius.int.ru> <632901.91790.bm@smtp116.sbc.mail.ne1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, August 13, 2015 08:21:44 AM Thomas Mueller wrote: > > T> Thinking I might have used the wrong syntax with ifconfig, I tried again with rsu0 instead of ndis0 or other failed attempts, and was successful connecting to Internet. > > > AFAIU, if you got rsu(4) driver in your kernel it will attach to the hardware, > > and the ndis(4) driver won't be able to. > > > Have you tried to used ndis(4) before on an unpatched vanilla FreeBSD? > > > Totus tuus, Glebius. > > I have tried to use ndis before, but never successfully. I used custom kernel, but src tree was not patched. > > Do I have to build a separate kernel without rsu to test ndis, or is disabling at loader good enough? > > set hint.rsu.0.disabled="1" This isn't sufficient. This leaves the device named rsu0 but disables it without letting other drivers attach to it. You need to remove the rsu driver entirely or use devctl to force the driver to ndis. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2028674.06lC1bRjxX>