From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 16:27:57 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2F84D4FA for ; Mon, 24 Nov 2014 16:27:57 +0000 (UTC) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5CE8B89 for ; Mon, 24 Nov 2014 16:27:56 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id r20so6415176wiv.8 for ; Mon, 24 Nov 2014 08:27:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=suAarfXYg+lklP3fy4qPxcy7r6KRiHYngei2AfNjbIs=; b=c9Oy5naB+wfBkDxxzp5q2RES3ErirC0KHXuOZM/AHQAG5B5MkBE0+JBXbFOIFaM9ZN EJrO77A3XbTGj0aSwrlFvRaM2aGfyQFMqn8Qq7ZRPzvtW9Qweenn8jO7Jzj1dp18ahCL eZ/wTUJlZdxMrkR93IHV+pQB4xADfWLWfck3DCcb+1C7CG1gEP3E2EJj9Khd5XGIyn9L hgHQEYAQGarfWzJTlS5IDI3hTKYcLH7z+3YpqfCSomN1qmfSbQL+ASd65Wfc2mkewcMj ZSSxM9GPZ9PBZDklVpvv1c2HsfObXxHxwRe5HEfuCmoLJyhLG9xSF9TaF0sglTuzxHjK XrWg== MIME-Version: 1.0 X-Received: by 10.194.24.103 with SMTP id t7mr15746287wjf.15.1416846475184; Mon, 24 Nov 2014 08:27:55 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.136 with HTTP; Mon, 24 Nov 2014 08:27:55 -0800 (PST) In-Reply-To: <20141124141234.GG30752@tweddell.de> References: <20141124141234.GG30752@tweddell.de> Date: Mon, 24 Nov 2014 08:27:55 -0800 X-Google-Sender-Auth: m69zYsO5OYlArSxrfURGTMFBqSE Message-ID: Subject: Re: iwn fails to scan on E6330 From: Adrian Chadd To: Bastian Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 16:27:57 -0000 Hi! You need to create wlan0 first before you use it. # ifconfig wlan0 create wlandev iwn0 # ifconfig wlan0 up # ifconfig wlan0 list scan (bringing it 'up' will start scanning) -a On 24 November 2014 at 06:12, Bastian wrote: > Hi all, > > I have to say, the BSD world is quite new to me. It peeked my interest > long time ago, but a week a ago I was brave enough to give it a try on a > real physical box. A Latitude E6330. > > In general the installation was straight forward. For now I just face > troubles with GPT (another topic) and iwn. > > Here is what my machine has: > ----- > root@zam709:~ # pciconf -lv iwn0 > iwn0@pci0:2:0:0: class=0x028000 card=0x13218086 chip=0x00828086 rev=0x34 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Centrino Advanced-N 6205 [Taylor Peak]' > class = network > > root@zam709 ~ 0 > 59 # kldstat -v | grep iwn > 158 pci/iwn > 17 1 0xffffffff820cc000 52db4 iwn1000fw.ko (/boot/kernel/iwn1000fw.ko) > 509 iwn1000fw_fw > 18 1 0xffffffff8211f000 ad28f iwn2030fw.ko (/boot/kernel/iwn2030fw.ko) > 510 iwn2030fw_fw > 19 1 0xffffffff821cd000 2e58a iwn4965fw.ko (/boot/kernel/iwn4965fw.ko) > 511 iwn4965fw_fw > 20 1 0xffffffff821fc000 53a21 iwn5000fw.ko (/boot/kernel/iwn5000fw.ko) > 512 iwn5000fw_fw > 21 1 0xffffffff82250000 52d42 iwn5150fw.ko (/boot/kernel/iwn5150fw.ko) > 513 iwn5150fw_fw > 22 1 0xffffffff822a3000 6f71e iwn6000fw.ko (/boot/kernel/iwn6000fw.ko) > 514 iwn6000fw_fw > 23 1 0xffffffff82313000 a5d05 iwn6000g2afw.ko (/boot/kernel/iwn6000g2afw.ko) > 515 iwn6000g2afw_fw > 24 1 0xffffffff823b9000 70fc2 iwn6000g2bfw.ko (/boot/kernel/iwn6000g2bfw.ko) > 516 iwn6000g2bfw_fw > 25 1 0xffffffff8242a000 73265 iwn6050fw.ko (/boot/kernel/iwn6050fw.ko) > > > root@zam709:~ # ifconfig iwn0 > iwn0: flags=8802 metric 0 mtu 2290 > ether 6c:88:14:18:fb:d0 > nd6 options=21 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > > > root@zam709:~ # time ifconfig iwn0 up scan > ifconfig: unable to get scan results > 0.007u 0.028s 0:00.03 66.6% 370+400k 2+0io 0pf+0w > > root@zam709:~ # uname -a > FreeBSD zam709 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014 > root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > ----- > > From the logs above you can see that the kernel has a built in module > for iwn and the firmwares are loaded. The kernel sees the interface and > I can bring it up. But when trying to scan for available BSSs, the scan > command return immediately without success (exit 1). > > Right now I suspect the firmware is somehow wrongly configured. But I > cannot find any logs about firmwares in the logs. > > Q: What is the proper procedure to debug a startup of the iwn module? > > Coming from the linux administration, I failed to gain knowledge how the > firmware is handeled. I tried to enable different sets of firmware > which were to enable just single firmware and up to enable all availabel > firmwares. I used kldload/unload for this. > > Q: When are the firmwares getting effectively used? Meaning, how does > dynamically loading/unloading a firmware change the bahaviour of the > module? > or > When does a module expect a firmware to be available and does it > accepts a runtime cahnge of the firmware? > > Q: As the iwn module is compiled into the kernel, how can I restart > this inorder it might read in the firmware again? > > Other questions I have: > > Q: Which is the poper firmware for my wireless device? > > > > Many thanks, > -- > Bastian > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"