madiwifi wifi0 missing

chrisortiz · 12-15-2005, 02:47 PM

i'm trying to get a 3com 3crpag175 pccard to work using the madwifi driver. The driver installation went ok, however when i type iwconfig the wifi0 interface does not show up

here is the output from lspci

Quote:

02:00.0 Ethernet controller: 3Com Corporation 3CRPAG175 Wireless PC Card (rev 01)
Subsystem: 3Com Corporation: Unknown device 1026

any thoughts?

Hangdog42 · 12-17-2005, 11:00 AM

It is possible that madwifi calls the card something else. Does iwconfig see any wireless cards? Also, are you sure the madwifi module is loaded? Have a look at the output of lsmod if you're not sure.

kirmet · 02-15-2006, 09:08 AM

hi there ... i have the same problem
im using a IBM T41 with WG511T (definitly atheros chipset

)
on the backtrack live distro (slackware)

make & make install works smoothly

Code:

#ifconfig ath0 down
#rmmod -w ath_pci
#modprobe ath_pci
#ifconfig ath0 up
#ifconfig -a -> show NO wifi0 interface

i tried it with different madwifi-ng versions, it always the same problem. madwifi docs/mans say that the ng drivers will create a virtual interface (wifiN) for every physical interface (default athN).

every following commands like

Code:

wlanconfig ath0 create wlandev wifi0 wlanmode sta/ap/whateva

fail of course due to error

Code:

wlanconfig:ioctl: no such device

kirmet · 02-15-2006, 09:43 AM

leave them noobs some time i say - most problems will vanish

got it working now

had to unplug the wlan adapter during bootup
make & make install
modprobe didnt work
insmod ath_pci.ko (in the ~/ath/ directory worked just fine)
wlanconfig ath0 destroy
wlanconfig ath0 create wlandev wifi0 wlanmod sta
and suddenly some kinky wifi0 interface appeared

greez kirmet

JunctaJuvant · 02-15-2006, 10:47 AM

Quote:

Originally Posted by kirmet

leave them noobs some time i say - most problems will vanish

got it working now

had to unplug the wlan adapter during bootup
make & make install
modprobe didnt work
insmod ath_pci.ko (in the ~/ath/ directory worked just fine)
wlanconfig ath0 destroy
wlanconfig ath0 create wlandev wifi0 wlanmod sta
and suddenly some kinky wifi0 interface appeared

greez kirmet

This is weird. The new madwifi-ng code (since 1/23/2006) should upon loading the module automatically by default create a VAP (ath0) from the base device (wifi0), see VAP autocreation and madwifi-ng features. So there should be no need to use the wlanconfig command at all if you only use station mode, neither on the command line nor in scipts. Or maybe I've overlooked something?

kirmet · 02-16-2006, 03:58 AM

Quote:

Originally Posted by JunctaJuvant

This is weird. The new madwifi-ng code (since 1/23/2006) should upon loading the module automatically by default create a VAP (ath0) from the base device (wifi0), see VAP autocreation and madwifi-ng features. So there should be no need to use the wlanconfig command at all if you only use station mode, neither on the command line nor in scipts. Or maybe I've overlooked something?

no you are right i didnt make that clear.

upon loading the driver via
insmod ath_pci.ko
the int. wifi0 apeared.

it was my urge to destroy and recreate that let me use the wlanconfig command *g* i wanted to see if the command works as it should.

why it doesnt work when the adapter is plugged in during reboot is not clear at all thought. it would help my curiosity a lot if someone could enlighten me with that.