Date: Thu, 27 Feb 2014 07:46:08 +0000 From: Tom Murphy <freebsd@pertho.net> To: Adrian Chadd <adrian@freebsd.org> Cc: Alexandr <shuriku@shurik.kiev.ua>, Tom Murphy <freebsd@pertho.net>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: iwn(4) in -HEAD supporting Centrino Wireless-N 135 Message-ID: <20140227074607.GA3325@freya.pertho.net> In-Reply-To: <CAJ-VmomsEdS5nm8rX6245rAEhVxWeOc4aO9AYrmEBHuUKHG=Tw@mail.gmail.com> References: <20140226123709.GA31099@syn.pertho.net> <CAJ-Vmom=b5tPTh1qWNG=zV5qM=Wzf1BRe5%2B2-ndrR648NSFmkw@mail.gmail.com> <530EE7F4.3080903@shurik.kiev.ua> <CAJ-VmomsEdS5nm8rX6245rAEhVxWeOc4aO9AYrmEBHuUKHG=Tw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Adrian, If I set -ht on wlan0 it works. I have to put it in rc.conf for it to work, though. ifconfig_wlan0="DHCP WPA -country GB -ht" So it does look like 11n isn't right. Kind regards, Tom On Wed, Feb 26, 2014 at 11:32:17PM -0800, Adrian Chadd wrote: > Yeah, try to verify if it's this or not. > > It's quite possible that there's some NIC setup for 11n that isn't > completely correct. > > > -a > > > > On 26 February 2014 23:23, Alexandr <shuriku@shurik.kiev.ua> wrote: > > May be it is similar to my problem. It connects to AP for a few seconds > > and then drop a connection. It situation 100% reproducible in 11n mode, > > but in 11g works fine. > > > > http://docs.freebsd.org/cgi/mid.cgi?5304B48E.8070404 > > > > 26.02.2014 17:09, Adrian Chadd пишет: > >> Hi, > >> > >> Yeah, there's likely something missing. But I just at the moment have > >> no time to debug this. > >> > >> > >> -a > >> > >> > >> On 26 February 2014 04:37, Tom Murphy <freebsd@pertho.net> wrote: > >>> Hi all, > >>> > >>> I compiled a fresh kernel from -HEAD and rebooted in the hope that my > >>> laptop's wifi would now be supported (I saw the commit messages in January > >>> about it possibly supporting Centrino Wireless-N 135). However, while > >>> it does attempt to bring the wifi up, the link just goes up and down > >>> and does not work properly. > >>> > >>> Knowing that the BSDs are fairly close and share some code, I did try > >>> the OpenBSD driver and it works. Is there some code that could be missing > >>> from the FreeBSD iwn(4) to stabilize it? I'd be happy to test any patches. > >>> > >>> Kind regards, > >>> Tom > >>> > >>> wlan0: no link ......wlan0: link state changed to UP > >>> wlan0 link stage up -> down > >>> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 > >>> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 > >>> wlan0: link state changed to UP > >>> wlan0: link state down -> up > >>> (more DHCPDISCOVER) > >>> wlan0 link stage up -> down > >>> > >>> Rise and repeat. > >>> > >>> iwn0: <Intel Centrino Wireless-N 135> mem 0xf7900000-0xf7901fff irq 18 at device 0.0 on pci3 > >>> > >>> _______________________________________________ > >>> freebsd-current@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140227074607.GA3325>