From owner-freebsd-current@FreeBSD.ORG Wed Feb 26 12:37:14 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83F479A2 for ; Wed, 26 Feb 2014 12:37:14 +0000 (UTC) Received: from mx1.pertho.net (87-194-102-137.bethere.co.uk [87.194.102.137]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 45A411539 for ; Wed, 26 Feb 2014 12:37:13 +0000 (UTC) Received: from syn.pertho.net (syn [10.0.29.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: tom) by syn.pertho.net (Postfix) with ESMTPSA id 1CE6D1D449D for ; Wed, 26 Feb 2014 12:37:11 +0000 (GMT) Date: Wed, 26 Feb 2014 12:37:09 +0000 From: Tom Murphy To: freebsd-current@freebsd.org Subject: iwn(4) in -HEAD supporting Centrino Wireless-N 135 Message-ID: <20140226123709.GA31099@syn.pertho.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailman-Approved-At: Wed, 26 Feb 2014 12:53:40 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2014 12:37:14 -0000 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: mem 0xf7900000-0xf7901fff irq 18 at device 0.0 on pci3