From owner-freebsd-questions@FreeBSD.ORG Sun Mar 6 06:45:50 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEE4D16A4CE for ; Sun, 6 Mar 2005 06:45:49 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D64D43D1D for ; Sun, 6 Mar 2005 06:45:49 +0000 (GMT) (envelope-from normal1.lists@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so985579wri for ; Sat, 05 Mar 2005 22:45:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=U3mT96+TtiWncurynQ7ZX6UH7UeCMUxypGnIEdZ5S195F86LIPDjq36cURy+bD2c2sp3q4UmBF9lZ/iA8tVT40JdCPZBAGSHpequw04ULjeLnbXD9y/Kappr3pBU5k/rVhx1JBj6HyoS0Mi66UBoKVqaw3KWY1xqmaBXHcAoIrM= Received: by 10.54.86.14 with SMTP id j14mr40870wrb; Sat, 05 Mar 2005 22:45:48 -0800 (PST) Received: by 10.54.2.45 with HTTP; Sat, 5 Mar 2005 22:45:48 -0800 (PST) Message-ID: Date: Sat, 5 Mar 2005 22:45:48 -0800 From: gabriel To: racerx@makeworld.com In-Reply-To: <422A6872.7000706@makeworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <422a3b4c.6460c00f.48d7.412b@smtp.gmail.com> <422A6872.7000706@makeworld.com> cc: freebsd-questions Subject: Re: D-Link NIC. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: gabriel List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Mar 2005 06:45:50 -0000 Interestingly enough, even though I've compiled the driver into the kernel, the card isnt recognized by it. dolores# kldload if_ath.ko kldload: can't load if_ath.ko: File exists dolores# interface if_ath.1 already present in the KLD 'kernel'! and nothing in ifconfig. I think I'm out of options? Should I give up? Cheers! On Sat, 05 Mar 2005 20:18:26 -0600, Chris wrote: > gabriel wrote: > > I _am_ certain that it works because I have the pc dual booting > > windows and it works there. The problem is I dont know what the > > default driver is I should use. > > > > Cheers! > > > > > > On Sun, 6 Mar 2005 04:35:33 +0530, Subhro wrote: > > > >> > >>Indian Institute of Information Technology > >>Subhro Sankha Kar > >>Block AQ-13/1, Sector V > >>Salt Lake City > >>PIN 700091 > >>India > >> > >>>-----Original Message----- > >>>From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd- > >>>questions@freebsd.org] On Behalf Of gabriel > >>>Sent: Sunday, March 06, 2005 2:57 > >>>To: freebsd-questions > >>>Subject: Re: D-Link NIC. > >>> > >>>Can anyone provide any insight? > >>> > >>>ndis0: flags=8802 mtu 1500 > >>> ether 00:11:95:87:8b:e4 > >>> media: IEEE 802.11 Wireless Ethernet autoselect > >>> status: no carrier > >>> ssid "" > >>> channel -1 authmode OPEN powersavemode OFF powersavesleep 100 > >>> rtsthreshold 2312 protmode CTS > >>> wepmode OFF weptxkey 1 > >>>dolores# > >>> > >>>if I try to use dhcp the ip address will just go to zeroes. :\ > >> > >>Are you positive that the DHCP function of your AP works perfectly? I am > >>asking thing because I have come across a couple of routers which happily > >>routes packets to static IPs but messes everything up as soon as it is asked > >>to handle DHCP. > >> > >>Also I strongly feel something fishy in the WLAN interface being detected as > >>ndisX instead of wiX. The first thing I would do is use the default driver > >>*even* if some documentation says that it is buggy. > >> > >>Regards, > >>S. > >> > >> > >> > > > > > > > > Try the ath driver. > http://www.freebsd.org/cgi/man.cgi?query=ath&sektion=4&manpath=FreeBSD+5.3-RELEASE > > -- > Best regards, > Chris > > Teamwork is essential. It allows you to blame someone else. > -- gabriel, Member of: FreeBSD-Announce FreeBSD-Hardware FreeBSD-Multimedia FreeBSD-questions