From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 26 21:35:55 2008 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A6971065679 for ; Wed, 26 Mar 2008 21:35:55 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: from coruscant.far-far-away.com (coruscant.far-far-away.us [70.91.196.65]) by mx1.freebsd.org (Postfix) with SMTP id F10E38FC34 for ; Wed, 26 Mar 2008 21:35:54 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: (qmail 22147 invoked from network); 26 Mar 2008 17:37:42 -0400 Received: from unknown (HELO alderaan) (68.162.198.134) by coruscant.far-far-away.us with SMTP; 26 Mar 2008 17:37:42 -0400 Message-ID: From: "Yousif Hassan" To: "Torfinn Ingolfsen" , References: <200803181157.m2IBvBLb000594@tausa.cc.uit.no><200803261002.m2QA2VNZ036148@tausa.cc.uit.no> <20080326184712.50100aac.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20080326184712.50100aac.torfinn.ingolfsen@broadpark.no> Date: Wed, 26 Mar 2008 17:37:42 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6000.16480 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16545 Cc: Subject: Re: if_wpi will not work for me X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2008 21:35:55 -0000 Torfinn Ingolfsen wrote: > Johan Johansen wrote: > >> Returning from my vacation, I notice that my problem is somewhat >> different from what some of you other guys describe. I cant get a >> wpi-device to work with at all. >> >> Booting without acpi makes no differens. >> Applying patch wpi_releng7.diff makes no differens. >> >> Before I load if_wpi, pciconf says >> none0@pci0:8:0:0: class=0x028000 card=0x135c103c >> chip=0x42228086 rev=0x02 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '10418086 Intel 3945ABG Wireless LAN controller' >> class = network >> and after >> wpi0@pci0:8:0:0: class=0x028000 card=0x135c103c >> chip=0x42228086 rev=0x02 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '10418086 Intel 3945ABG Wireless LAN controller' >> class = network >> but still no wpi0 present. >> >> So, would it help to buy more memory, and if I do, where should I put >> it? > > Just curious: why do you think that buying more memory will help? > Because of the "cabn't allocate memory resource" message? > AFAIU, that message indicates that there is something wrong with the > way your acpi / bios tells FreeBSD what memory / how much memory it > needs, not that the machine itself has too little memory. To wit, my experience has been that this message is innocuous. This has been confirmed by Ben, who wrote the driver. I used to get these messages but the wpi0 device would attach fine (it tends to get buried during bootup messages after all that scroll - check dmesg). In addition, Andrew's latest patches to -current and -stable resolve this message - it no longer appears for me. So Johan, do not buy more memory simply to solve this issue! Did you try those latest patches, and do you still see a problem? If your pciconf is reporting a "wpi0@...." in the device list, it seems improbable that the device didn't attach - in that case you'd have seen "noneX@..." This may be stating the obvious, but there are specific steps you need to do to enable this device, including accepting a license via /boot/loader.conf; did you follow them? Do you have a dmesg confirming that the device did not attach? Do you have the output of ifconfig for us to look at? --Y