From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 1 21:16:48 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F17C106564A for ; Thu, 1 Mar 2012 21:16:48 +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 6BD4A8FC19 for ; Thu, 1 Mar 2012 21:16:47 +0000 (UTC) Received: by lagv3 with SMTP id v3so1688904lag.13 for ; Thu, 01 Mar 2012 13:16:46 -0800 (PST) Received-SPF: pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.152.122.74 as permitted sender) client-ip=10.152.122.74; Authentication-Results: mr.google.com; spf=pass (google.com: domain of fernando.apesteguia@gmail.com designates 10.152.122.74 as permitted sender) smtp.mail=fernando.apesteguia@gmail.com; dkim=pass header.i=fernando.apesteguia@gmail.com Received: from mr.google.com ([10.152.122.74]) by 10.152.122.74 with SMTP id lq10mr6990300lab.7.1330636606230 (num_hops = 1); Thu, 01 Mar 2012 13:16:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZiRi1RD7siZWx9VibkKO32kf6tAZ3bPVyob1NGeuRtM=; b=XlxAyQcxBHf55gqS2Y40amjBXNh3bhsSRqSccdLs/VUJIVE9vCNK+sG4fQ/iEdBip8 Su/S0HjinrHvEnp6vQ1I7qOP/VtknjNbnmleasumPYcs3zOrn4oXf6Q2jKu0/v+0dB/O jkl1HEj3bWB0bp4Mtk3W9eqpwqid5DtDPfROJQex30h4kpkKXslhD5zZGkXQrcJsiimT secoGKob8U6NrS4OqahsJS6mwt5TS7jzYsb4FIdkxvp3SrK9WKtuCLwihp9SRO+43C+S bbyOj4BdNRji6oRmSewN8UttMqOibjUv1QeGXQaHjeIxrn1k+uCu5sLvWoB6lKGLx80D 2gqw== MIME-Version: 1.0 Received: by 10.152.122.74 with SMTP id lq10mr5711258lab.7.1330636606143; Thu, 01 Mar 2012 13:16:46 -0800 (PST) Received: by 10.152.13.72 with HTTP; Thu, 1 Mar 2012 13:16:46 -0800 (PST) In-Reply-To: References: <201202292045.11498.bschmidt@techwires.net> Date: Thu, 1 Mar 2012 22:16:46 +0100 Message-ID: From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: Adrian Chadd 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: Thu, 01 Mar 2012 21:16:48 -0000 On Thu, Mar 1, 2012 at 9:18 PM, Adrian Chadd wrote: > I'd suggest opening up a PR. > Done kern/165595 > > Unfortunately then I'd suggest testing various snapshots of > 9.0-CURRENT back to when 8.0 was branched from it.. we have to try and > find when/where it broke. > > Thanks, > > > Adrian > > 2012/3/1 Fernando Apestegu=EDa : > > On Wed, Feb 29, 2012 at 11:33 PM, Fernando Apestegu=EDa < > > fernando.apesteguia@gmail.com> wrote: > > > >> > >> > >> On Wed, Feb 29, 2012 at 8:45 PM, Bernhard Schmidt < > bschmidt@techwires.net>wrote: > >> > >>> 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 > >>> ipw2200 > >>> > > card > >>> > > > in this laptop with 8.2-RELEASE without problems. However I hav= e > >>> 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 a= nd > >>> > > 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 > make > >>> > > sure it isn't related to that. Also, all modules iwi(4) depends o= n > are > >>> > > pulled in automatically, even the firmware modules, no need to > load em > >>> > > through loader.conf. > >>> > > > >>> > > >>> > I copied GENERIC and removed the "device iwi" line. I rebooted but > still > >>> > 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 > kernel > >>> > when loading since I didn't change my loader.conf). Still the same > >>> error. > >>> > > >>> > > >>> > > >>> > > 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 kno= wn > >> 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?) bu= t > I > >> get a trapcode=3D12 coming from iwi_detach0x31 coming from iwi_attach0= x313 > >> 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=3D0x42= 208086 > >> rev=3D0x05 hdr=3D0x00 > >> bar [10] =3D type Memory, range 32, base 0x80000000, size 4096, > enabled > >> > >> > >> > >>> > >>> You could also try to rule out as many automatic things as possible. > >>> Remove everything related to wireless out of the kernel config, remov= e > >>> 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 > >>> > >> > > Hi again, > > > > I did it and I got the same result. After executing the last statement = I > > got the same error. For the record, I tried with a GENERIC kernel but > still > > no luck. I can't even get a kernel dump (I guess it crashes too early > > during booting?) > > > > Any ideas? > > > > How can I pin point what the problem is? > > > > Thanks > > > > > >> > >> I'll try to do it as soon as possible so I can give more information. > >> > >> Thanks in advance. > >> > >> > >>> > >>> -- > >>> Bernhard > >>> > >> > >> > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to " > freebsd-wireless-unsubscribe@freebsd.org" >