From owner-freebsd-current@freebsd.org Fri Jan 6 19:08:55 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8764CA271B for ; Fri, 6 Jan 2017 19:08:55 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B82451869; Fri, 6 Jan 2017 19:08:55 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) Received: from [172.31.128.104] (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by freefall.freebsd.org (Postfix) with ESMTP id EF859455C; Fri, 6 Jan 2017 19:08:54 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) From: "Jonathan Anderson" To: "Pete Wright" Cc: freebsd-current@freebsd.org Subject: Re: PQ_LAUNDRY: unexpected behaviour Date: Fri, 06 Jan 2017 14:07:02 -0500 Message-ID: In-Reply-To: References: <1596d0f6d6d.1266583c3319360.3590554896761456790@nextbsd.org> <74A6C6D0-90A4-4DB2-8D89-5D2B1E495F88@FreeBSD.org> <15974c6426d.12945df5e62589.5931208946643250381@nextbsd.org> <1779f83b-687d-ac6f-587f-90bdc6d61c20@nomadlogic.org> <4778A6AC-97CF-4AE0-957A-7768964867D9@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (1.9.6r5319) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 06 Jan 2017 19:08:55 -0000 On 6 Jan 2017, at 13:53, Pete Wright wrote: > > i've been having the same problems with iwm too (failing to load > firmware on boot). my trick has been to either boot into an old > kernel where iwm was mostly usable. also i've commented out the line > enabling wlan0 in my rc.conf then uncommented it after boot and > manually running "service netif start" to bring up iwm. that method > works most of the time... > -pete I am able to load iwm (iwm7265fw), but there are some networks that I just can't connect to (INIT -> INIT, swscan_cancel_scan, repeat). Attaching to an iPhone hotspot is one example of a not-entirely-helpful network, but there is other, more typical infrastructure that gives trouble too. There is an iwm8xxx in the room that seems to work fine, however... I do not meddle in the affairs of wi-fi, for it is subtle and quick to anger. :) Jon -- Jonathan Anderson jonathan@FreeBSD.org