From owner-freebsd-current@FreeBSD.ORG Wed Oct 19 09:17:37 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C30BF16A41F; Wed, 19 Oct 2005 09:17:37 +0000 (GMT) (envelope-from wsk@gddsn.org.cn) Received: from gddsn.org.cn (gddsn.org.cn [218.19.164.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0322443D53; Wed, 19 Oct 2005 09:17:36 +0000 (GMT) (envelope-from wsk@gddsn.org.cn) Received: from [192.168.168.135] (unknown [211.96.21.221]) by gddsn.org.cn (Postfix) with ESMTP id 8465F38CB4D; Wed, 19 Oct 2005 16:13:25 +0800 (CST) Message-ID: <43560006.6020707@gddsn.org.cn> Date: Wed, 19 Oct 2005 16:12:54 +0800 From: Suken Woo User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; zh-CN; rv:1.7.7) Gecko/20050424 X-Accept-Language: zh-cn,zh MIME-Version: 1.0 To: Bill Paul , current@freebsd.org, mobile@freebsd.org, hardware@freebsd.org References: <20051018200611.7474E16A42F@hub.freebsd.org> In-Reply-To: <20051018200611.7474E16A42F@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 19 Oct 2005 12:24:25 +0000 Cc: Subject: Re: Netgear WG511 drivers help X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2005 09:17:38 -0000 Bill Paul Wrote: >>Suken Woo Wrote: >> >> >> >>>>lists: >>>>the Netgear WG511 dosen't support on freebsd and ndis wrapper doesn't >>>>work either >>>>anybody could give any help?? >>>>_______________________________________________ >>>>freebsd-mobile@freebsd.org mailing list >>>>http://lists.freebsd.org/mailman/listinfo/freebsd-mobile >>>>To unsubscribe, send any mail to >>>>"freebsd-mobile-unsubscribe@freebsd.org" >>>> >>>> >>>> >>>> >>>Did your Netgear WG511 say 'Atheros' on its packaging? >>>what does pciconf -lv say about it? >>> >>>I have a WG511T and it works fine its a Atheros. >>> >>>Mike >>> >>> >>> >>> >>the WG511 useing the difference chip set i though. and here's my >>pciconfig -lv lists: >>none1@pci3:0:0: class=0x020000 card=0x4e001385 chip=0x1faa11ab rev=0x03 >>hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' >> class = network >> subclass = ethernet >>and some dmesgs: >>cardbus0: Resource not specified in CIS: id=14, size=10000 >>cardbus0: at device 0.0 (no driver attached) >> >>BTW,my card's type is WG511 v2. >> >> > >I have the following: > >none7@pci1:0:0: class=0x020000 card=0x1faa11ab chip=0x1faa11ab rev=0x03 hdr=0x00 > vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' > class = network > subclass = ethernet > >This is a Marvell 8335 card, and it works with the latest incarnation >of Project Evil in -current: > >ndis0: mem 0x88010000-0x8801ffff,0x88020000-0x8802ffff irq 9 at device 0.0 on cardbus0 >ndis0: NDIS API version: 5.1 > >Note however that I've been experiencing a peculiar problem with my >particular card and laptop. The card is a no-name brand ("Mentor"), >and I'm using it in my Sony Vaio Picturebook laptop. For the most >part it works ok: I can initialize it, get it to associate, I can >even do WPA2 with it using wpa_supplicant. The only problem is that >after it's been running for a while (usually several hours, though >sometimes sooner), the laptop will freeze up. Typically when it happens, >one of the LEDs on the card will be flashing, which I think means it's >become disassociated or the re-keying interval has expired. Sadly, >since the whole laptop wedges up completely, I have no clue what's >causing the problem. > >I haven't noticed the same problem when testing the same card with >my Soekris board at home, and I don't have another laptop or card >to test it with, so I'm at a bit of a loss. I've tried everything I >can think of to try and get the laptop to cough up some useful info >but with no joy. The fact that I can only get it to crash maybe once >or twice a day doesn't help. > >I suspect the issue is related to WPA2 somehow, so if you're not >going to use that, you may not notice any problems. Give it a try >and see what happens. > >-Bill > >-- >============================================================================= >-Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu > wpaul@windriver.com | Wind River Systems >============================================================================= > you're just BEGGING to face the moose >============================================================================= > > > yep, u r right here! use the latest incarnation of Project Evil in -CURRENT. it's working now and thank u very much :-P below is my ndis: cardbus0: Resource not specified in CIS: id=14, size=10000 ndis0: mem 0xd0220000-0xd022ffff,0xd0230000-0xd023ffff irq 11 at device 0.0 on cardbus0 ndis0: NDIS API version: 5.1 ndis0: Ethernet address: 00:0f:b5:86:85:a8