Re: [Madwifi-users] some madwifi problems

[Sam L. <sa...@er...>]

On Wednesday 28 January 2004 06:47 am, ma buse wrote:
> hi all
>
> i ran into some problems with the madwifi driver.
> first
> of all i am using bleeding edge software. that means i
> update my software very often to the latest available
> versions. at the moment i have fedora core devel on my
> notebook with madwifi cvs driver of today. the wlan
> card is a netgear 511t.
>
> now the issues:
> fedora kernel 2.6.x is shipped without a "vmlinux"
> file
> in the kernel rpm. the build mechanism of madwifi
> relies
> on the kernel tool "modpost" which needs an installed
> vmlinux. other external modules dont use modpost but
> use
> the "make -C $KERNELSRC SUBDIRS=$MODULDIR modules"
> mechanism. can that be changed in madwifi for the
> 2.6.x
> users?
>

I don't know what the "correct way" is to do the modpost thing.  If you send 
me a patch to do what works for you I'll consider it.  I've already had to 
fix a couple of problems in modpost in 2.6.0 (that didn't appear to have been 
fixed later) so avoiding modpost might be a good thing.

> of course i build my own kernel with some enhancements
> so
> i have the vmlinux file for my kernels. "make"ing the
> driver is ok. i get some warnings however which are
> the
> same with the official kernel rpm. perhaps this one is
> important:
> if_ath_pci.c: In function `ath_pci_resume':
> if_ath_pci.c:237: Warnung: ignoring return value of
> `pci_enable_device', declared with attribute
> warn_unused_result
>
> the strange point is now that the card works. exaclty
> once. that means i can use the card with an AP or with
> kismet but after removing and reinserting the card it
> is nonfunctional.
> the leds of the card stay dark.
> the kernel log shows that the module counter is 4:
> kernel: unregister_netdevice: waiting for ath0 to
> become free. Usage count = 4
> i have no idea what keeps the module "busy".
> it is really annoying to reboot the system after using
> madwifi (this is not windows afterall ;).
>

Presumably something is holding a reference to the module.  When I've seen 
this happen the references vanish after a few seconds as if a timer were 
going off and then the module is unloaded.

> another issue is wpa. i am trying to get xsupplicant
> to work with a wrt54g access point but to no avail.
> does it work for anyone? if you have it running and
> dont like to write much then please write a short
> "yes"
> or "no" with your hardware combo, please. of course
> i'd like to get a more detailed description of the
> configuration though.

xsupplicant implements 802.1x and wpa != 802.1x.  The open1x folks said that 
xsupplicant works with the driver.  I'm still trying to duplicate their 
results but am hungup on non-driver issues.

	Sam