From owner-freebsd-mobile@FreeBSD.ORG Fri Mar 27 21:22:36 2009 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 1F24C10656BA; Fri, 27 Mar 2009 21:22:36 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by mx1.freebsd.org (Postfix) with ESMTP id 708B28FC17; Fri, 27 Mar 2009 21:22:35 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by ey-out-2122.google.com with SMTP id 4so243514eyf.7 for ; Fri, 27 Mar 2009 14:22:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bIBG5zVZ35HALnDPPn1n+LyEPeY6rFsY+HQn3/JxJA0=; b=mYnnrU9634nlurhiJqXkBRx+71xhqKuP8iVS8dtj08ZJWFBDjwDl/Z3v4NKQgiT1/S OcHef+PC1IhbC1J1F1NXA9YHZoiu5emyr9GuOdplyjOR+/vrI8+yb/l6EJEYdPu4TRKE eLint0/zdaKhtxJ5AX4M1ZZI2N9D68jKeU8pY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=w9UBT0a3D+X2AiN56/gQuqoHt9W34Muya25A/5hSGUNov4TOB3Fw39mcX6tueyKowZ JvKoocMNezFwtAegSPMIopuvqG581/SXszIq7BhPMjY7OOOskAwn5ukKrpXSmXQ4ImU8 j66KcTQMM4uGGLAv1+oBSMOVkkDq0BeY8LGCU= MIME-Version: 1.0 Received: by 10.210.45.17 with SMTP id s17mr1914074ebs.93.1238188953910; Fri, 27 Mar 2009 14:22:33 -0700 (PDT) In-Reply-To: <200903272016.n2RKGZ1m001583@yoda.pixi.com> References: <200903272016.n2RKGZ1m001583@yoda.pixi.com> Date: Fri, 27 Mar 2009 22:22:33 +0100 Message-ID: <3a142e750903271422x6917ff87p663411f27fe63484@mail.gmail.com> From: "Paul B. Mahol" To: knowtree@aloha.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: Intel 5100AGN ndis driver problem 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: Fri, 27 Mar 2009 21:22:37 -0000 On 3/27/09, knowtree@aloha.com wrote: > On 3/21/09, Ganbold wrote: >> Paul B. Mahol wrote: >>> On 3/19/09, Ganbold wrote: >>> >>>> Hi, >>>> >>>> I'm trying to use ndis driver for Intel 5100AGN and got >>>> following error: >>>> >>>> beastie# grep ndis /var/log/messages >>>> Mar 19 23:41:21 beastie kernel: ndis0: mem >>>> 0xf4300000-0xf4301fff irq 17 at device 0.0 on pci3 >>>> Mar 19 23:41:21 beastie kernel: ndis0: [ITHREAD] >>>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS API version: 5.1 >>>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown >>>> error) >>>> >>>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown >>>> error) >>>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x08ff product >>>> 0x2810 bus uhub1 >>>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x0a5c product >>>> 0x2145 bus uhub1 >>>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x17ef product >>>> 0x1004 bus uhub3 >>>> Mar 19 23:41:53 beastie kernel: ugen1.3: at >>>> usbus1 (disconnected) >>>> Mar 19 23:41:57 beastie kernel: ugen1.3: at >>>> usbus1 >>>> Mar 19 23:41:57 beastie root: Unknown USB device: vendor 0x0a5c product >>>> 0x2145 bus uhub1 >>>> Mar 19 23:45:36 beastie kernel: wlan0: Ethernet address: >>>> 00:21:6b:9a:23:8e >>>> Mar 19 23:52:02 beastie kernel: pid 9861 (initial thread) is using >>>> legacy pty devices >>>> Mar 20 00:08:06 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown >>>> error) >>>> ... >>>> ndis0 at pci0:3:0:0: class=0x028000 card=0x12118086 chip=0x42378086 >>>> rev=0x00 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> class = network >>>> >>>> I'm running: >>>> beastie# uname -an >>>> FreeBSD beastie.micom.mng.net 8.0-CURRENT FreeBSD 8.0-CURRENT #5 >>>> r190040M: Thu Mar 19 21:45:37 ULAT 2009 >>>> tsgan at beastie.micom.mng.net:/usr/obj/usr/src/sys/DEVIL_WITNESS i386 >>>> >>>> >>>> Any idea how to fix this issue? >>>> Please let me know if you need more info. >>>> >>> >>> How you generate ndis module? >>> Post whole output _after_ is module loaded >>> _not_ just lines containing ndis. >>> >>> also enable debug.ndis sysctl. >>> >>I generated module issuing following command: >> >>ndisgen NETw5x32.inf NETw5x32.sys >> >>After module is generated, loading modules gives (debug.ndis=1): >> >> >>Mar 21 16:18:33 beastie kernel: no match for KeBugCheck >>Mar 21 16:18:33 beastie kernel: ndis0: mem >>0xf4300000-0xf4301fff irq 17 at device 0.0 on pci3 >>Mar 21 16:18:33 beastie kernel: ndis0: [ITHREAD] >>Mar 21 16:18:33 beastie kernel: ndis0: NDIS API version: 5.1 >>Mar 21 16:18:33 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown error) >>Mar 21 16:18:33 beastie root: Unknown USB device: vendor 0x08ff product >>0x2810 bus uhub1 >>Mar 21 16:18:33 beastie root: Unknown USB device: vendor 0x0a5c product >>0x2145 bus uhub1 >>Mar 21 16:18:33 beastie root: Unknown USB device: vendor 0x17ef product >>0x1004 bus uhub3 >>Mar 21 16:18:34 beastie kernel: attach done. >>Mar 21 16:18:35 beastie kernel: halting done. >> >>Ganbold > > I am seeing the exact same thing on 7.1-RELEASE, minus the USB errors. I > have the same Intel chipset in a Fujitsu T1010 laptop. I downloaded the XP > driver from Intel, had the same file names as above. When I ran ndisgen it > asked me for the names of the files even through I specified them on the > command line. Other than that the build process seemed fine. When I used > kldload to test it I got the unknown error message but the system seemed > happy so I set it up to load from loader.conf and added an entry for it in > /etc/rc.conf. When I rebooted the hardware probe hung at the ndis driver. > > After I managed to boot without the kernel module I tried again to load > with kldload. After the NDIS ERROR line I see > > WARNING: using obsoleted if_watchdog interface > > Next comes the MAC address, then a page fault followed by a reboot. I tried > it several times with same results. That panic should be fixed in CURRENT, if not, post backtrace from textdump for the start. > Is there anything I can do to help solve this? Again I am running 7.1 not > HEAD. Something in NDISulator initialization code looks to be broken, but current showstopper are error codes that are not documented anywhere. -- Paul