From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 29 22:33:41 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 862F3106566C for ; Wed, 29 Feb 2012 22:33:41 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id EC71E8FC08 for ; Wed, 29 Feb 2012 22:33:40 +0000 (UTC) Received: by lagv3 with SMTP id v3so1382572lag.13 for ; Wed, 29 Feb 2012 14:33:39 -0800 (PST) Received-SPF: pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.152.110.102 as permitted sender) client-ip=10.152.110.102; Authentication-Results: mr.google.com; spf=pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.152.110.102 as permitted sender) smtp.mail=fernando.apesteguia@gmail.com; dkim=pass header.i=fernando.apesteguia@gmail.com Received: from mr.google.com ([10.152.110.102]) by 10.152.110.102 with SMTP id hz6mr2420871lab.21.1330554819847 (num_hops = 1); Wed, 29 Feb 2012 14:33:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TBaE7C0c+B9X2grZYZEOhyoP8bmOzOJSKlFW3tVmbOE=; b=TMJI41qz3K3PryLV6utU097pfWorBzxamBG7bF/DM3fFad1c1cqJfoAFP47S4c8EUr VI1BvHMmQXgMcXNuH1Gzt8b8F78F7dAZRSKPXAp+4CPrpdoLy2MJzrRlF6EVJlL44EBj rhKPTFJbSDaE1nnMeBwMUpfGylEHwh1W46ZO8= MIME-Version: 1.0 Received: by 10.152.110.102 with SMTP id hz6mr1971393lab.21.1330554819759; Wed, 29 Feb 2012 14:33:39 -0800 (PST) Received: by 10.152.13.72 with HTTP; Wed, 29 Feb 2012 14:33:39 -0800 (PST) In-Reply-To: <201202292045.11498.bschmidt@techwires.net> References: <201202292045.11498.bschmidt@techwires.net> Date: Wed, 29 Feb 2012 23:33:39 +0100 Message-ID: From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: iwi firmware X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Feb 2012 22:33:41 -0000 On Wed, Feb 29, 2012 at 8:45 PM, Bernhard Schmidt w= rote: > On Wednesday 29 February 2012 18:06:43 Fernando Apestegu=EDa wrote: > > On Wed, Feb 29, 2012 at 10:09 AM, Bernhard Schmidt > > wrote: > > > > > On Tue, Feb 28, 2012 at 23:20, Fernando Apestegu=EDa > > > wrote: > > > > Hi all, > > > > > > > > I recently installed 9.0-RELEASE on my old laptop. I used the ipw22= 00 > > > card > > > > in this laptop with 8.2-RELEASE without problems. However I have > missed > > > > something I can't figure out. I get the message: > > > > > > > > iwi0: timeout processing command blocks for iwi_bss firmware > > > > iwi0: could not load main firmware iwi_bss > > > > > > > > This is what I have in my loader.conf: > > > > > > > > # Agree Intel's agreement license > > > > legal.intel_iwi.license_ack=3D1 > > > > > > > > # wireless support > > > > #if_iwi_load=3D"YES" This is in kernel now... > > > > wlan_load=3D"YES" > > > > firmware_load=3D"YES" > > > > > > > > iwi_bss_load=3D"YES" > > > > iwi_ibss_load=3D"YES" > > > > iwi_monitor_load=3D"YES" > > > > > > > > what am I missing? > > > > > > > > Thanks in advance. > > > > > > Hmm, there haven't been any major changes to iwi(4) between 8.2 and > > > 9.0, except what you've already noticed. You could try to remove > > > iwi(4) from the kernel config and use it as module again, just to mak= e > > > sure it isn't related to that. Also, all modules iwi(4) depends on ar= e > > > pulled in automatically, even the firmware modules, no need to load e= m > > > through loader.conf. > > > > > > > I copied GENERIC and removed the "device iwi" line. I rebooted but stil= l > > got the same message. I also tried removing the iwi device and > introducing > > the iwifw in the kernel (so I got a couple of complaints from the kerne= l > > when loading since I didn't change my loader.conf). Still the same erro= r. > > > > > > > > > Can you post dmesg and pciconf -lvc? > > > > > > > Yes. > > Thanks, nothing obvious in there though. > > I played a bit around with an iwi(4) device on a i386 and a amd64 box > and I was not able to reproduce the issue you are seeing. This smells > like it's related to the laptop you are using, which model is that? > It is an old Clevo D400K. The wireless always worked (with all the known ipw2200 firmware bugs...) > > Honestly, I have no clue currently what is to blame. > > Given that there were some ACPI/PCI bus changes between 8 and 9, mind > posting the pciconf -lb output for the iwi0 device? > Interesting. It occurred to me to disable the ACPI support in the bootloader. Guess what? I get a panic _every single time_ I try to boot. I don't have the complete backtrace (is it written anywhere on disk?) but I get a trapcode=3D12 coming from iwi_detach0x31 coming from iwi_attach0x313 coming from device_attach... (with the wireless card physically turn off). So you're probably right and this is related to ACPI. The result of pciconf -lb is: iwi0@pci0:0:5:0: class=3D0x028000 card=3D0x27028086 chip=3D0x4220808= 6 rev=3D0x05 hdr=3D0x00 bar [10] =3D type Memory, range 32, base 0x80000000, size 4096, enabl= ed > > You could also try to rule out as many automatic things as possible. > Remove everything related to wireless out of the kernel config, remove > the entries in loader.conf and rc.conf and run the following commands > after a reboot (no wlan modules should be loaded at that point): > > kldload wlan_ccmp > kldload wlan_tkip > kldload if_iwi > ifconfig wlan0 create wlandev iwi0 > wpa_supplicant -Dbsd -iwlan0 -c/etc/wpa_supplicant.conf -B > I'll try to do it as soon as possible so I can give more information. Thanks in advance. > > -- > Bernhard >