From owner-freebsd-questions@FreeBSD.ORG Wed Oct 20 16:47:47 2004 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 8009616A4CE for ; Wed, 20 Oct 2004 16:47:47 +0000 (GMT) Received: from audiogram.mail.pas.earthlink.net (audiogram.mail.pas.earthlink.net [207.217.120.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D22043D41 for ; Wed, 20 Oct 2004 16:47:47 +0000 (GMT) (envelope-from algould@datawok.com) Received: from 31-21.lctv-ubr2-blk1.cablelynx.com ([206.255.31.21] helo=[192.168.63.10]) by audiogram.mail.pas.earthlink.net with asmtp (TLSv1:RC4-MD5:128) (Exim 4.34) id 1CKJcn-0002oa-Ic; Wed, 20 Oct 2004 09:47:46 -0700 From: "Andrew L. Gould" To: freebsd-questions@freebsd.org, e.schuele@computer.org Date: Wed, 20 Oct 2004 11:47:53 -0500 User-Agent: KMail/1.6.2 References: <200410201022.26723.e.schuele@comcast.net> <200410201058.08112.e.schuele@comcast.net> In-Reply-To: <200410201058.08112.e.schuele@comcast.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200410201147.53705.algould@datawok.com> X-ELNK-Trace: ee791d459e3d6817d780f4a490ca69564776905774d2ac4b8ece72399d7679bed3f738aee0eca37e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 206.255.31.21 Subject: Re: Cardbus Atheros 5212 and Dell laptop(s)... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2004 16:47:47 -0000 On Wednesday 20 October 2004 10:58 am, Eric Schuele wrote: > On Wednesday 20 October 2004 10:22 am, Eric Schuele wrote: > > Hello, > > > > I'm having difficulty getting my Atheros 5212 based card to work in > > either of my dell laptops. =A0The card only has its power LED on for > > about half a second when it is identified by the os (5.3BETA7), > > then it goes off. =A0dhclient causes the link LED to blink in a very > > consistent manner but it never aquires any info from DHCP server. > > I should also note that it will not associate with any WAP even when > I force all settings (IP address, wepkey, etc..)... > > Thanks, When I moved to FreeBSD 5*, I found that I had to remove certain=20 wireless configuration options that worked in FreeBSD 4*. That was=20 with a wi device; but the later configuration works well with my new=20 atheros devices. I'm using the following atheros products successfully: D-Link DWL-G520 (pci in a generic desktop running FreeBSD 5.3RC1) D-Link DWL-G650 (pccard in a Dell Inspiron 8100 running FreeBSD 5.2.1) =46YI: D-Link is displaying the Atheros logo on the retail boxes of its=20 atheros chipset products; which should make purchasing these easier. I use the script below, with a real wep code and different IP addresses,=20 for each of these devices. Other than setting hostname info=20 in /etc/rc.conf and /etc/hosts, I haven't edited any other network=20 configuration files. (Beware the effects of email wordwrap.) #!/bin/sh # /usr/local/etc/rc.d/ath0 NIC=3Dath0 case $1 in start) ifconfig ${NIC} inet 192.168.42.21 netmask 255.255.255.0 ssid datawok =20 wepmode on wepkey 0x1111111111=20 route add default 192.168.42.1 echo search cablelynx.com > /etc/resolv.conf echo nameserver 24.204.0.4 >> /etc/resolv.conf echo nameserver 24.204.0.5 >> /etc/resolv.conf echo ${NIC} ;; dyn) ifconfig ${NIC} ssid datawok wepmode on wepkey 0x1111111111 dhclient ${NIC} echo ${NIC} ;; stop) [ -s /var/run/dhclient.pid ] && kill `cat /var/run/dhclient.pid` && =20 rm /var/run/dhclient.pid=20 ifconfig ${NIC} remove echo " ${NIC} removed" ;; status) ifconfig ${NIC} ;; *) echo "usage: /usr/local/etc/${NIC} [start|dyn|stop|status]" ;; esac ##end of script Best of luck, Andrew Gould