Date: Tue, 09 May 2006 08:28:37 +0200 From: Gregers Petersen <gp.ioa@cbs.dk> To: Jeff Rollin <jeff.rollin@gmail.com>, freebsd-mobile@freebsd.org Subject: Re: Wireless woes Message-ID: <44603695.5010701@cbs.dk> In-Reply-To: <8a0028260605082216i76f3ac39x838e3ef180f8ed25@mail.gmail.com> References: <8a0028260604281015x403f3bedm82cf690672e0b939@mail.gmail.com> <445FD0C8.4000707@errno.com> <8a0028260605081655p38b3b3a3p10b9207ba0058db6@mail.gmail.com> <4460113B.9030303@errno.com> <8a0028260605082216i76f3ac39x838e3ef180f8ed25@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeff Rollin wrote: > I was the one with the C3 version D-Link card --> What if you try to run through the whole process again, just to check (+ this is what I do + please feel free to correct me if I'm wrong in any way): 1. Press the card into the correct 'socket'. 2. (as 'su' run) kldload if_ath 3. (as 'su' run) ifconfig ath0 up 4. (as 'su' run) ifconfig ath0 - look at the info, and then decide if you need to do further actions, such as: 5. connecting to a specific AP (again via ifconfig) 6. getting an IP-adress (via dhclient) The PC-card should "show up" after you have loaded the kernel module and made the PC-card "active" with 'up', but if nothing happens then you might have either hardware problems or 'strangeness'. As I remember it your using an IBM R51 --> I have the same laptop with the build-in Intel 2200BG card and it works just fine for daily office use combined with the iwi-driver (from ports) - so if you have the same build-in card I would like to ask if your already have this one working (and just need the PC-card for other stuff, just as I do) ? Sincerely -- Gregers Petersen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44603695.5010701>