From owner-freebsd-questions@freebsd.org Mon Jan 9 23:58:09 2017 Return-Path: Delivered-To: freebsd-questions@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 07317CA85E3 for ; Mon, 9 Jan 2017 23:58:09 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay10.qsc.de (mailrelay10.qsc.de [212.99.163.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ACD517B0 for ; Mon, 9 Jan 2017 23:58:07 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay10.qsc.de; Tue, 10 Jan 2017 00:58:15 +0100 Received: from r56.edvax.de (port-92-195-83-137.dynamic.qsc.de [92.195.83.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id CDDA33CBF9; Tue, 10 Jan 2017 00:58:02 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v09Nw15L003570; Tue, 10 Jan 2017 00:58:01 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Tue, 10 Jan 2017 00:58:01 +0100 From: Polytropon To: Anton Yuzhaninov Cc: freebsd-questions@freebsd.org Subject: Re: Edison tactic - 1.ifconfig wlan0 ssid myssid , work but some missed ,2.pkg install Message-Id: <20170110005801.a089a5b3.freebsd@edvax.de> In-Reply-To: <8b8e732e-42cb-9337-02ad-25115a17edb8@citrin.ru> References: <1483886536.3077593.840915257.60D1F4BB@webmail.messagingengine.com> <20170108165630.540acb46.freebsd@edvax.de> <941e4b56-0d6b-ee11-bf87-0a3b96ccd80a@passap.ru> <20170108190338.682794e7.freebsd@edvax.de> <8b8e732e-42cb-9337-02ad-25115a17edb8@citrin.ru> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay10.qsc.de with 7EA3168343E X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1859 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2017 23:58:09 -0000 On Mon, 9 Jan 2017 18:22:18 -0500, Anton Yuzhaninov wrote: > On 01/08/17 13:03, Polytropon wrote: > >> IWN(4) states that an iwn adapter uses a lodable firmware. > >> Is it actually loaded? > > Isn't that firmware already part of the GENERIC kernel? > > If not, "man iwn" has the relevant items that should be > > added to /boot/loader.conf (or "iwnfn" for all of the > > available firmwares). > > > > Firmware for iwn is build as module and can be loaded from modeles path. > There is no need to add entries to loader.conf > > dmesg should contain strings like: > iwn0: iwn_read_firmware: ucode rev=0x12a80601 Thank you, _that_ is really valuable information. I have seen the modules, but I wasn't sure if they needed to be loaded via loader.conf or if this would happen automatically. So for the OP, firmware is not the problem, as "ifconfig -a" already stated that the iwn0 and wlan0 devices are available. He's probably kust lacking the crazy configuration details that the wireless network requires. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...