Date: Fri, 10 Jul 2009 13:28:23 -0500 From: Stephen Montgomery-Smith <stephen@missouri.edu> To: kevin <stringflow@gmail.com> Cc: Sam Leffler <sam@freebsd.org>, freebsd-current@freebsd.org Subject: Re: About iwn firmware Message-ID: <4A578847.5060201@missouri.edu> In-Reply-To: <d4b0fbf00907101115m62bf74b9lc6c2443478240c09@mail.gmail.com> References: <d4b0fbf00907100639t7a91f4afmf826d3f47b438116@mail.gmail.com> <4A5777F6.5040700@freebsd.org> <d4b0fbf00907101115m62bf74b9lc6c2443478240c09@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
kevin wrote: > On Sat, Jul 11, 2009 at 1:18 AM, Sam Leffler <sam@freebsd.org> wrote: > >> kevin wrote: >> >>> Hi, >>> I notice iwn's firmware hasn't been updated for a long time.Is there any >>> plan to import newer version iwn firmware ? current version is >>> iwlwifi-4965-ucode-4.44.17 in the source tree, while latest version is >>> iwlwifi-4965-ucode-228.61.2.24. >>> >>> http://www.intellinuxwireless.org/?n=downloads&f=ucodes_4965 >>> >>> >> Not sure why you want newer firmware. If it's for newer chip support then >> that requires driver changes and is non-trivial. >> >> Sam >> >> iwn driver works well when system up.but it is not so robust.it will stop > transfer data and throw some errors in these conditions: > 1 . mount nfs via wireless network,if i transfer a lot of data.it may stop > receiving data after some time. > 2 . wireless network is busy, then some one reboot the wireless AP.it may > throw some errors and stop working. > 3 . Find wireless network works slow and switch to Ethernet,.if try > /etc/rc.d/netif restart, it may throw some errors and stop working. > > > all these are fixed by reboot system(reload iwn and iwnfw dose not work at > most time). i also find iwn driver printe a lot of microcode error related > messages when it failed(not easy to reproduce it). > > No official Change Log, i just notice the *description *in gentoo > bug#202818. I have had the same experiences. They are not that frequent, so I can live with it, but if someone were to fix it, that would be great.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A578847.5060201>