Date: Fri, 13 Mar 2009 22:16:41 +0100 From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= <olivier@freenas.org> To: David Horn <dhorn2000@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Is iwn drivers working on Current ? Message-ID: <3131aa530903131416j4928df70hc18c2b8cb97e8237@mail.gmail.com> In-Reply-To: <25ff90d60903130852p40e153a6hac10340e7eb9d876@mail.gmail.com> References: <3131aa530903122323n73b671b5y4cb4a4a8896efa14@mail.gmail.com> <25ff90d60903130852p40e153a6hac10340e7eb9d876@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi David, > Questions to help see if you are seeing the same problem: > > 1) =A0Do you have ipv6_enabled=3D"yes" in rc.conf ? Yes, if I comment this line and reboot, my new error messages are still: iwn0: error, INTR=3D2000000<SW_ERROR> STATUS=3D0x0 iwn0: iwn_config: configure command failed, error 35 iwn0: iwn_init_locked: could not configure device, error 35 iwn0: iwn_config: configure command failed, error 35 iwn0: iwn_init_locked: could not configure device, error 35 > 2) =A0Report on the results of "ifconfig -l" > [root@d630]~#ifconfig -l iwn0 bge0 fwip0 lo0 xl0 bridge0 wlan0 iwn0 is the first interface in my case too! > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dconf/132179 I've apply your patch (and re-enable IPv6 too), but no change.. > The real issue is likely a bug in the iwn driver. Hi think so, because without IPv6 it still didn't works. Regards, Olivier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3131aa530903131416j4928df70hc18c2b8cb97e8237>