Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Mar 2009 00:54:15 -0400
From:      David Horn <dhorn2000@gmail.com>
To:        =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= <olivier@freenas.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Is iwn drivers working on Current ?
Message-ID:  <25ff90d60903132154p41d9fb7bx4723bde6dcccf17f@mail.gmail.com>
In-Reply-To: <3131aa530903131416j4928df70hc18c2b8cb97e8237@mail.gmail.com>
References:  <3131aa530903122323n73b671b5y4cb4a4a8896efa14@mail.gmail.com> <25ff90d60903130852p40e153a6hac10340e7eb9d876@mail.gmail.com> <3131aa530903131416j4928df70hc18c2b8cb97e8237@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 13, 2009 at 5:16 PM, Olivier Cochard-Labb=E9
<olivier@freenas.org> wrote:
> 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
>

Since you disabled ipv6, and still have the issue, then ipv6/rtsol
accessing iwn0 instead of wlan0 is not the issue for your instance.

I just replicated your problem with a new set of rc.conf variables on
iwn0 including:

ifconfig_wlan0=3D"country US WPA DHCP" instead of my default:
ifconfig_wlan0=3D"WPA DHCP".   I will dig a bit further and see if I can
understand any reason for the country ifconfig setting to cause this
issue (error 35 at boot), but it smells like a bug to me.

Will your wireless card function for you without the "country FR" setting ?
Give it a try regardless of functionality, just to see if the error 35
goes away.

I also notice that attempting to set the country parameter on the
wlanX device after the interface is marked "UP" results in an error
message of SIOCS80211: Device busy

In any case, I suggest that it is time to file a PR.

Good Luck.

---Dave



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25ff90d60903132154p41d9fb7bx4723bde6dcccf17f>