[DragonFlyBSD - Bug #2968] (Resolved) iwn(4) doesn't associate anymore

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Fri Jul 7 12:13:00 PDT 2017

Issue #2968 has been updated by cmusser.

Status changed from New to Resolved

This doesn't seem to be a problem now. I am using a 4.9 nightly on an x220 and it associates reliably.

Bug #2968: iwn(4) doesn't associate anymore

* Author: cmusser
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
The iwn wireless interface in recent versions of 4.7 master can no longer associate with a base station. ifconfig reports "no carrier" and the scan_results command in wpa_cli requently returns "FAIL-BUSY", but not always.

Backing out commit 3aca8a4433acf84c92d5511261b53f2749a67ba8 restores the functionality. That commit was a logic change to 'full-offload scanning'.

Here is the dmsesg line specifically describing the hardware in question:

iwn0: <Intel Centrino Advanced-N 6205> mem 0xf0c00000-0xf0c01fff irq 17 at device 0.0 on pci3

I have two laptops that exhibit this behavior (they have the same wireless interface): a Lenovo x220 and a Lenovo X1 Carbon

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list