Date: Fri, 13 Mar 2009 11:52:21 -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: <25ff90d60903130852p40e153a6hac10340e7eb9d876@mail.gmail.com> In-Reply-To: <3131aa530903122323n73b671b5y4cb4a4a8896efa14@mail.gmail.com> References: <3131aa530903122323n73b671b5y4cb4a4a8896efa14@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 13, 2009 at 2:23 AM, Olivier Cochard-Labb=E9 <olivier@freenas.org> wrote: > Hi, > > I try to use the iwn drivers on my Dell Latitude D630 laptop on a > up-to-date current, but I can't. > > I've an Intel 4965AGN card, and here is the result of pciconf -lv : > > iwn0@pci0:12:0:0: =A0 =A0 =A0 class=3D0x028000 card=3D0x11218086 chip=3D0= x42298086 > rev=3D0x61 hdr=3D0x00 > =A0 =A0vendor =A0 =A0 =3D 'Intel Corporation' > =A0 =A0device =A0 =A0 =3D 'Intel 4965AGN Intel Wireless WiFi Link > 4965AGN(supporting 802.11a/b/g/Draft-N)' > =A0 =A0class =A0 =A0 =A0=3D network > > I've put on /boot/loader.conf the magics lines: > legal.intel_iwn.license_ack=3D1 The license ack for iwn is not needed anymore btw. > if_iwn_load=3D"YES" > > my /etc/rc.conf is configured like that: > wlans_iwn0=3D"wlan0" > ifconfig_wlan0=3D"country FR WPA DHCP" > > and the /etc/wpa_supplicant.conf was tested using 2 others differents > wirelles card (USB rum and PCMCIA=A0ath) without problem. > But I have this error message on dmesg: > > iwn0: need multicast update callback > iwn0: error, INTR=3D2000000<SW_ERROR> STATUS=3D0x0 > 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 > iwn0: iwn_transfer_firmware: timeout waiting for first alive notice, erro= r 35 > iwn0: iwn_init_locked: could not load firmware, error 35 I have seen these exact same error 35 issues. > > (The wireless switch is on the ON position, and this wireless works > when booting with Linux Ubuntu). > > And not association possible... > > Here are some other information: > > [root@d630]~#ifconfig wlan0 > wlan0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu = 1500 > =A0 =A0 =A0 =A0ether 00:1d:e0:72:10:01 > =A0 =A0 =A0 =A0inet6 fe80::21d:e0ff:fe72:1001%wlan0 prefixlen 64 scopeid = 0x7 > =A0 =A0 =A0 =A0media: IEEE 802.11 Wireless Ethernet autoselect (autoselec= t) > =A0 =A0 =A0 =A0status: no carrier > =A0 =A0 =A0 =A0ssid "" channel 13 (2472 Mhz 11g) > =A0 =A0 =A0 =A0regdomain ETSI country F2 authmode WPA1+WPA2/802.11i priva= cy ON > =A0 =A0 =A0 =A0deftxkey UNDEF txpower 30 bmiss 10 scanvalid 60 protmode C= TS wme > =A0 =A0 =A0 =A0roaming MANUAL > [root@d630]~#ifconfig wlan0 list scan > [root@d630]~#ifconfig wlan0 list caps > drivercaps=3D581e001<STA,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,WPA1,WPA2,WME> > [root@d630]~#uname -a > FreeBSD d630.freenas.org 8.0-CURRENT FreeBSD 8.0-CURRENT #14: Thu Mar > 12 14:17:22 CET 2009 <snip> > Does someone know where the problem is ? Yes, I have seen this problem with iwn on current, but unfortunately do not know a real "fix" at the moment. For me, it seems to be timing related at boot time, caused by IPv6 rtsol starting on the interface before iwn had settled. iwn0 should never be initialized by rtsol, as it is the hardware 802.11 interface. wlan0 should be initialized instead. (-current vap code) Questions to help see if you are seeing the same problem: 1) Do you have ipv6_enabled=3D"yes" in rc.conf ? 2) Report on the results of "ifconfig -l" In my case, iwn0 was the first interface in the list, resulting in rtsol starting on iwn0 (and not some other interface). There are several unique issues here, but I believe that a work-around patch that I wrote to /etc/network.subr that might help is attached to PR conf/132179: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dconf/132179 The real issue is likely a bug in the iwn driver. Someone with real knowledge of the iwn code would probably give better insight than me. Sam ? Brandon ? Good Luck. --_Dave > > Thanks for your help, > > Olivier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25ff90d60903130852p40e153a6hac10340e7eb9d876>