another DWL-G630 problem (with errror msgs!)Forum: Networking Topic: another DWL-G630 problem (with errror msgs!) started by: stormy Posted by stormy on Nov. 30 2005,05:17
First off I have just done a fresh install of dsl 1.2.1.Secondly the leds on the card light up (and stay lit afterwards) during the auto-detection phase of bootup. But there is no wlan0 or ath0, only lo. I read on another dwl-g630 related post that the mad-wifi drivers were built into linux - ath_pci. Also this is the C2 dwl-g630.
I did an lsmod just in case, but to no avail. Both wlan and ath_hal modules load with ease though. So with my led lights still blinking I decided to use ndiswrapper. I've used it once before on a USRobotics card and it worked very well. I've also seen many post about it working with this particular card.
Then:
I then did a modprobe ndiswrapper. No errors, so I did an ifconfig. Still no wireless iface. Just lonely old 'lo'. But wait, let's check dmesg:
Honestly I'm lost. Any help you can provide would be great. I really need my wifi :< -Thanks in advance Posted by tempestuous on Nov. 30 2005,07:15
You may be closer than you realise. "ifconfig" only shows ACTIVE network interfaces. Run "ifconfig -a" to see ALL network interfaces.Also, you may be confusing ifconfig with iwconfig. iwconfig will display all network interfaces with Linux wireless extensions. This means most, but not all, wireless interfaces. You can load your MADWiFi modules individually if you prefer with insmod, but it's easier just to do - modprobe ath_pci If your ath0 interface is present, now you just need to setup the wireless connection - iwconfig ath0 essid MY_ESSID key 1234567890 mode managed pump -i ath0 Similar story with ndiswrapper, but make sure you unload any MADWiFi modules before attempting to use ndiswrapper. MADWiFi drivers are included in many Linux distributions, but don't assume this in all cases. Posted by stormy on Nov. 30 2005,07:28
ifconfig (-a), iwconfig - neither show any wireless iface. sorry for not being more clear. neither ndiswrapper or madwifi is working in this case as you can see from the dmesg output.
|