If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below. ** If you are logged in, most ads will not be displayed. **

WARNING:
It seems that there are modules left from previous MadWifi installations.
If you are unistalling the MadWifi modules please press "r" to remove them.
If you are installing new MadWifi modules, you should consider removing those
already installed, or else you may experience problems during operation.
Remove old modules?

WARNING:
It seems that there are modules left from previous MadWifi installations.
If you are unistalling the MadWifi modules please press "r" to remove them.
If you are installing new MadWifi modules, you should consider removing those
already installed, or else you may experience problems during operation.
Remove old modules?

okay, looking good. If you do /sbin/modprobe ath_pci now, and it gives the same error, all I can assume is the drivers are just not installed to the directory where they need to be, but they should be somewhere on your system. So we need to know where they are if that is the case...

it happened from doing comand "export KERNELRELEASE=`uname -r" i was looking at this UserDocs/Troubleshooting - MadWifi - Trac "After building and installing madwifi modprobe doesn't find the modules!" i thought that was my problem but i guess not my goof... sorry bout that...

I'm just spoiled I guess... This module runs Atheros wireless devices perfectly for me on Slackware and Crux. I'm using ath_pci on Crux right now for this post...

I read that the error you got can be caused by running a different kernel than the one you are compiling for. You've built for 2.6.20-2931.fc7xen. Is this the exact same kernel you are running under? If in doubt, do:

Code:

uname -a

And see if they match exactly. If they do match, there's someting else going on I'd be unfamiliar with. If it were me, and they matched and I still get the errors, I'd try installing the module/driver with yum again.

Oops.. just saw this...

Code:

make[1]: Entering directory `/usr/src/kernels/2.6.22.4-65.fc7-x86_64'

This is likely the cause of the errors. There are two symlinks in /lib/modules/ 2.6.20-2931.fc7xen. One is "build" the other is "source." Both point back to the kernel in /usr/src/kernels. Do:

Code:

cd /lib/modules/2.6.20-2931.fc7xen

Then:

Code:

ls -l

...and post the results here. I suspect you have symlinks pointing to the wrong kernel.

OOOOOHH i see the problem now i've bin installing to /lib/modules/2.6.22.4-65.fc7/net but when i go to modprobe ath_pci it looks in /lib/modules/2.6.20-2931.fc7xen/net i think thats a problem. Thanks for sticking with me on this

The problem is you are building your module while in 2.6.20-2931.fc7xen, but "build is pointing to 2.6.22.4-65.fc7-x86_64.You need to go back to where I showed you how to delete the symlink "build" and make a new one. Just like what I showed you before. If you'll do this, you'll likely get it compiled right and you can move on. Nothing will happen until you correct the symlink "build" and have it pointing back to kernel 2.6.20-2931.fc7xen instead of 2.6.22.4-65.fc7-x86_64.

i think i said it before but i don't have that kernel folder i only /usr/src/kernels/2.6.22.4-65.fc7-x86_64 thats all i'll look around my computer for another one but i didn't have this either there was no kernels folder before you got me to update my kernel. your right though about the symlick this is what it is: /lib/modules/2.6.20-2931.fc7xen/build/2.6.22.4-65.fc7-x86_64