Steve Holdoway wrote: > On Wed, 19 Jul 2006 11:47:04 +1200 > Roger Searle <[EMAIL PROTECTED]> wrote: > > >> On Tue, 18 Jul 2006 23:04:10 +1200 >> >>> Roger Searle <[EMAIL PROTECTED]> wrote: >>> >>> >>> >>>> I have a new installation of kubuntu (dapper) on my acer travelmate >>>> 230. Nice! So easy to install software... >>>> >>>> I've spent a couple of hours becoming increasingly unsure on how to get >>>> a dwl-g630 wireless card functioning. System Settings Hardware and >>>> Internet & Network don't give me any clues about how to have the card >>>> detected. I've not seen the lights come on on the card, have not >>>> installed any modules. I've looked through lsmod but have no idea what >>>> to look for! Mixed messages from my friend google. >>>> >>>> Any pointers appreciated. >>>> Roger >>>> >>>> >>>> >>>> >>> Although it's very difficult to ascertain from the dlink website, it looks >>> like at least the Revision C version of this card is based on the atheros >>> chipset. If so, the madwifi project over at sourceforge may well be the way >>> forward for you. >>> >>> Steve >>> >>> >>> >> I have determined that this card is Revision D. Google tells me this >> uses the AR5212 Atheros chipset. I have downloaded the madwifi-0.9.1 >> drivers and extracted to /usr/src - ie I have a /usr/src/madwifi-0.9.1 >> folder with various folders. I've used adept to install the kernel >> headers and source files. >> >> Have I missed anything? Do I now just need to cd into the madwifi >> folder and do "make" and then "make install"? (this being new territory >> for me, I'm wanting to check I'm on the right track before proceeding...) >> >> And in case this is relevant - if the machine boots with the card >> inserted, the power light on the card flashes after logging on, and >> lspci gives >> 0000:03:00.0 Ethernet controller: Atheros Communications, Inc,: Unknown >> device 001a (rev 01) >> and iwconfig gives several "no wireless extensions". >> >> > Sorry, had to check - I've been fighting with an IBM interface lately, which > still requires the sacrifice of virgins - no mean feat round here (: > > Have a quick read though the docs, but I'm pretty certain that you've got it > right. You may need to modprobe atheros or similar to get it up and running, > and add the following lines to /etc/network/interfaces... > > auto ath0 > iface ath0 inet dhcp > pre-up /sbin/iwpriv ath0 mode 0 > pre-up /sbin/iwconfig ath0 essid <MyESSid> channel <MyChannel> key > <MyKey> > > > Where MyESSid, MyChannel and MyKey are defined at your ap. The last 2 lines > will connect to your ap, and the iface... line will use your existing dhcp > server to allocate the IP stuff. If you manually allocate that, then you'll > need to change the above to... > > > auto ath0 > iface ath0 inet static > pre-up /sbin/iwpriv ath0 mode 0 > pre-up /sbin/iwconfig ath0 essid "<MyESSid>" channel <MyChannel> key > <MyKey> > address a.b.c.d > netmask 255.255.255.0 > network a.b.c.0 > broadcast a.b.c.255 > gateway a.b.c.e > > ( Assuming a normal Class C network ). > > Hope this makes sense. > > Steve > > >
have modified /etc/network/interfaces (added the last 2 lines) auto ath0 iface ath0 inet dhcp pre-up /sbin/iwpriv ath0 mode 0 pre-up /sbin/iwconfig ath0 essid for-me-to-know channel 6 key and-you-to-find-out [EMAIL PROTECTED]:~$ sudo ifup ath0 ath0 no private ioctls. Failed to bring up ath0. Which isn't a surprise, given the module issue isn't right yet, it would seem... Ready to go though!
