Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Sep 2008 16:10:06 -0300
From:      "Flavio Junior" <billpp@gmail.com>
To:        freebsd-current@freebsd.org
Subject:   Re: iwn: Errors during make iwn.ko
Message-ID:  <58aa8d780809251210w7184b73dj8c0b987c324eee28@mail.gmail.com>
In-Reply-To: <48DBBF35.9090502@math.missouri.edu>
References:  <58aa8d780809241601i724ec7c2p5fd13a3b18027a64@mail.gmail.com> <alpine.BSF.2.00.0809241837310.89093@cauchy.math.missouri.edu> <58aa8d780809250837gbf45204gb007c1ad46812ade@mail.gmail.com> <48DBBF35.9090502@math.missouri.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Very thanks Stephen..

With your recomendations and reading (again) iwn and wlan manpage I
achieve get wlan working with -current drivers.

I'd needed to recompile iwn drivers from current and reinstall it and
create manually wlan0 device with ifconfig wlan create wlandev iwn0,
but everything works.

TA.

--

Fl=E1vio do Carmo J=FAnior

On Thu, Sep 25, 2008 at 1:41 PM, Stephen Montgomery-Smith
<stephen@math.missouri.edu> wrote:
> Flavio Junior wrote:
>>
>> I'd tried to use that driver but, all operations gives me "unable to
>> get *operation* results".
>>
>> dmesg shows me no error, and detects when I disable wireless button
>> (iwn0: RF switch: radio disabled).
>>
>> I'm sure that have wireless network around (I'm writing this e-mail usin=
g
>> one).
>>
>> Does someone there using iwn driver?
>> Maybe I have forget something ;/
>
> As it happens, I am using the iwn driver.  (That is why I happened to kno=
w
> about it so quickly - incidentally I'm sorry for my snappy tone last time=
.)
>
> Are you doing all the "wlan" stuff that CURRENT now requires for wireless
> cards - for example, in my rc.conf I have:
>
> wlans_iwn0=3D"wlan0"
> ifconfig_wlan0=3D"DHCP"
>
> and all subsequent ifconfig and dhclient commands are done using wlan0.
>
> (And also, my guess is that the iwn driver you were using was a backport =
to
> FreeBSD-STABLE, which doesn't have all this wlan stuff, and hence is
> incompatible with CURRENT.)
>
>



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