problem with madwifi drivers
YenJung Chang
yenjung
Fri Nov 26 05:05:20 PST 2004
Oscar,
Please remove wlan.o, ath_hal.o and ath_pci.o first, then re-insert again.
Command as following:
rmmod ath_pci
rmmod ath_hal
rmmod wlan
Please do it as the order.
yj.
On Fri, 26 Nov 2004 13:58:11 +0100, Oscar p <reeopp at hotmail.com> wrote:
> Hi YenJung!!
>
> These are tehe results
>
> dhcppc0:~ # cd /home/oscar/madwifi/madwifi-20041021/net80211/
> dhcppc0:/home/oscar/madwifi/madwifi-20041021/net80211 # cd ..
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan.o
> insmod: error inserting 'net80211/wlan.o': -1 File exists
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_acl.o
> insmod: error inserting 'net80211/wlan_acl.o': -1 Unknown symbol in module
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_wep.o
> insmod: error inserting 'net80211/wlan_wep.o': -1 Unknown symbol in module
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_tkip.o
> insmod: error inserting 'net80211/wlan_tkip.o': -1 Unknown symbol in module
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod net80211/wlan_ccmp.o
> insmod: error inserting 'net80211/wlan_ccmp.o': -1 Unknown symbol in module
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath_hal/ath_hal.o
> insmod: error inserting 'ath_hal/ath_hal.o': -1 File exists
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 # insmod ath/ath_pci.o
> insmod: error inserting 'ath/ath_pci.o': -1 File exists
> dhcppc0:/home/oscar/madwifi/madwifi-20041021 #
>
> some of them seem to be already included while some others not (don't know
> why). I can send you the log from madwifi installation if you think it can
> help...
>
> Oscar
>
> >From: YenJung Chang <yenjung at gmail.com>
> >Reply-To: YenJung Chang <yenjung at gmail.com>
> >To: Oscar p <reeopp at hotmail.com>
> >CC: hostap at shmoo.com
> >Subject: Re: problem with madwifi drivers
> >Date: Fri, 26 Nov 2004 20:51:57 +0800
>
>
> >
> >OK...
> >This my steps to insert madwifi modules, maybe you can give it a try
> >and then tell us what you get.
> >
> >cd ${madwifi}
> >insmod net80211/wlan.o
> >insmod net80211/wlan_acl.o
> >insmod net80211/wlan_wep.o
> >insmod net80211/wlan_tkip.o
> >insmod net80211/wlan_ccmp.o
> >insmod ath_hal/ath_hal.o
> >insmod ath/ath_pci.o
> >
> >yj.
> >
> >On Fri, 26 Nov 2004 13:33:17 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > > Hi YenJung
> > > This is what I get:
> > > dhcppc0:/ # insmod
> >/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o
> > > insmod: error inserting
> > > '/home/oscar/madwifi/madwifi-20041021/net80211/wlan_tkip.o': -1 Unknown
> > > symbol in module
> > >
> > > Thanks once more!!!!
> > > Oscar
> > >
> > > >From: YenJung Chang <yenjung at gmail.com>
> > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > >To: Oscar p <reeopp at hotmail.com>
> > > >CC: hostap at shmoo.com
> > > >Subject: Re: problem with madwifi drivers
> > > >Date: Fri, 26 Nov 2004 20:29:02 +0800
> > >
> > >
> > > >
> > > >If you compiled madwifi as kernel module, the modules with prefixed
> > > >"wlan_" were in
> > > >directory "madwifi/net80211". You can command as:
> > > >
> > > >insmod ${madwifi}/net80211/wlan_tkip.o
> > > >
> > > >please replace the ${madwifi} with the actual path of madwifi in your
> > > >machine.
> > > >
> > > >
> > > >If you compiled madwifi within kernel image, there is no madwifi
> > > >modules needed to insert.
> > > >
> > > >yj.
> > > >
> > > >On Fri, 26 Nov 2004 12:32:27 +0100, Oscar p <reeopp at hotmail.com> wrote:
> > > > >
> > > > > Hi YenJung
> > > > >
> > > > > Sorry but where shall I insert them?
> > > > >
> > > > > BR/ Oscar
> > > > >
> > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > >CC: hostap at shmoo.com
> > > > > >Subject: Re: problem with madwifi drivers
> > > > > >Date: Fri, 26 Nov 2004 17:12:44 +0800
> > > > >
> > > > >
> > > > > >
> > > > > >OK....
> > > > > >I guess you just inserted wlan.o, ath_hal.o and ath_pci.o modules,
> > > >right?
> > > > > >
> > > > > >Please also insert wlan_wep.o wlan_tkip.o and wlan_ccmp.o, those
> >are
> > > > > >all in net80211 directory.
> > > > > >
> > > > > >yj.
> > > > > >
> > > > > >
> > > > > >On Thu, 25 Nov 2004 15:21:46 +0100, pepe perez <reeopp at hotmail.com>
> > > >wrote:
> > > > > > > Hi YenJung!
> > > > > > > I think I already tried it, anyway I have just tried again and
> >not
> > > >so
> > > > > >much
> > > > > > > difference:
> > > > > > >
> > > > > > > dhcppc0:~ # wpa_supplicant -iath0 -c/etc/wpa_supplicant.conf -d
> > > > > > > Configuration file '/etc/wpa_supplicant.conf' ->
> > > > > >'/etc/wpa_supplicant.conf'
> > > > > > > Reading configuration file '/etc/wpa_supplicant.conf'
> > > > > > > ctrl_interface='/var/run/wpa_supplicant'
> > > > > > > ctrl_interface_group=0
> > > > > > > eapol_version=1
> > > > > > > ap_scan=1
> > > > > > > Priority group 1
> > > > > > > id=0 ssid='OSCARLAN'
> > > > > > > Using existing control interface directory.
> > > > > > > EAPOL: SUPP_PAE entering state DISCONNECTED
> > > > > > > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > > > > > > EAPOL: SUPP_BE entering state INITIALIZE
> > > > > > > EAP: EAP entering state DISABLED
> > > > > > > EAPOL: External notification - portEnabled=0
> > > > > > > EAPOL: External notification - portValid=0
> > > > > > > wpa_driver_madwifi_set_wpa: enabled=1
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > Failed to enable WPA in the driver.
> > > > > > > wpa_driver_madwifi_set_wpa: enabled=0
> > > > > > > ioctl[IEEE80211_IOCTL_SETOPTIE]: Operation not supported
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > Failed to disable WPA in the driver.
> > > > > > > wpa_driver_madwifi_set_drop_unencrypted: enabled=0
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > wpa_driver_madwifi_set_countermeasures: enabled=0
> > > > > > > ioctl[IEEE80211_IOCTL_SETPARAM]: Operation not supported
> > > > > > > Control interface directory not empty - leaving it behind
> > > > > > >
> > > > > > > It looks like something else is going on, meybe in configuration
> >or
> > > > > > > compilation....
> > > > > > >
> > > > > > > Thanks a lot for your help!!!
> > > > > > > Oscar
> > > > > > >
> > > > > > > >From: YenJung Chang <yenjung at gmail.com>
> > > > > > > >Reply-To: YenJung Chang <yenjung at gmail.com>
> > > > > > > >To: pepe perez <reeopp at hotmail.com>
> > > > > > > >CC: hostap at shmoo.com
> > > > > > > >Subject: Re: problem with madwifi drivers
> > > > > > > >Date: Thu, 25 Nov 2004 21:20:22 +0800
> > > > > > > >
> > > > > > > >AFAIK, the interface name of madwifi is "ath0", hence, the
> > > >interface
> > > > > > > >in your command should be -iath0, not -iwlan0.
> > > > > > > >
> > > > > > > >yj.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> >_________________________________________________________________
> > > > > > > Don't just search. Find. Check out the new MSN Search!
> > > > > > > http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> > > > > > >
> > > > > > >
> > > > >
> > > > > _________________________________________________________________
> > > > > Express yourself instantly with MSN Messenger! Download today it's
> >FREE!
> > > > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> > > > >
> > > > >
> > >
> > > _________________________________________________________________
> > > Don't just search. Find. Check out the new MSN Search!
> > > http://search.msn.com/
> > >
> > >
>
> _________________________________________________________________
>
>
> Express yourself instantly with MSN Messenger! Download today it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
More information about the Hostap
mailing list