Well, you could post the output of dmesg (you may have to be root to run it) and see if there are additional messages. The other thing to try would be to run depmod -A and see if that cleans up the errors. Usually that kind of error happens when the kernel and the module aren't entirely in sync.

This problem was one of those little bits of esoterica that drive me nuts. I have absolutely no idea why you have to have compiled a kernel before you can compile a module.

Don't worry about it. Just enjoy being one post closer to being an LQ Addict.

We only ever delete posts in very extremem circumstances. It's not a problem - just try to avoid doing it again.

Ok sorry about the double posting.

Ok here is what happened:

I ran depmod -a and had no errors. But when I tried to run the modprobe I still had the same exact error. Maybe its the module file? I could try installing another version of linux-wlan-ng. Maybe that could work? If I do want to install an older version how do I get rid of the new one? There is a guy on the HCL who seemed to get my adapter working with the pre11 version. Should I give that one a try(even though he is running it on a 2.4 kernel)?

I'm not sure that version hopping is going to help. You're certainly welcome to try, but I'm not going to hold my breath.

The problem seems to be that you need to have compiled a kernel from source in order to get this to work. That link I gave you on to the linux-wlan lists pretty much said that.

OK, when you compile a kernel, you usually do the following

make menuconfig
make
make install
make modules
make modules_install

Now I'm trying not to blow up your rig by compiling a bad kernel, but get enough done so that linux-wlan has enough to go on. You've already got the make menuconfig covered by your make oldconfig and you did the make. Maybe the next thing to try is the make modules and then recompile linux-wlan and try again. If you avoid the install steps, you shouldn't blow up your kernel.

Alright I ran make modules but still got the same message. I am posting what showed up on dmesg:

prism2_usb: disagrees about version of symbol p80211netdev_rx
prism2_usb: Unknown symbol p80211netdev_rx
prism2_usb: disagrees about version of symbol register_wlandev
prism2_usb: Unknown symbol register_wlandev
prism2_usb: disagrees about version of symbol wlan_unsetup
prism2_usb: Unknown symbol wlan_unsetup
prism2_usb: disagrees about version of symbol unregister_wlandev
prism2_usb: Unknown symbol unregister_wlandev
prism2_usb: disagrees about version of symbol p80211netdev_hwremoved
prism2_usb: Unknown symbol p80211netdev_hwremoved
prism2_usb: disagrees about version of symbol wlan_setup
prism2_usb: Unknown symbol wlan_setup
prism2_usb: disagrees about version of symbol p80211netdev_rx
prism2_usb: Unknown symbol p80211netdev_rx
prism2_usb: disagrees about version of symbol register_wlandev
prism2_usb: Unknown symbol register_wlandev
prism2_usb: disagrees about version of symbol wlan_unsetup
prism2_usb: Unknown symbol wlan_unsetup
prism2_usb: disagrees about version of symbol unregister_wlandev
prism2_usb: Unknown symbol unregister_wlandev
prism2_usb: disagrees about version of symbol p80211netdev_hwremoved
prism2_usb: Unknown symbol p80211netdev_hwremoved
prism2_usb: disagrees about version of symbol wlan_setup
prism2_usb: Unknown symbol wlan_setup

Dont know if it helps much. any ideas?

This is a suggestion I hate to make......I think your going to have to compile and run your own kernel. The error messages you're posting are definitely the result of a module and a kernel not being in sync, and I don't know how to resolve that other than by compiling and running a new kernel.

There is plenty of advice around here on compiling and running a kernel (my favorites are the sticky threads at the top of the Slackware forum) so you should be able to find plenty of advice. Just make sure that wireless support is either compilied into the kernel or is available as a module.

Oh.... Do I have too?

Ok fine I'll do it. Damn I wished it wouldn't come to this. Oh well im not running make config though thats like 3 hours worth of answering questions. I don't think my mind can take it.

Oh, ick. Don't do that. Use make xconfig (if you have X running) or make menuconfig if you are working with X turned off. Either one is a MUCH nicer experience.

You know, that might be a question to direct at the linux-wlan group. I'll admit that I'm an ignoramus about the kernel, but it makes no sense why linux-wlan can't work with a precompiled kernel. Heck, I bet most people use the precompiled kernels that came with their distro.

You know... Mandrake 10 has great support for such things... I was having a similar problem.

Get into the Mandrake Controll center and click networking -> new connection -> wireless connection

If it says anything other than Manual Choice, pick that, it should work. Nice and easy.

Well I did try that. It just went back into picking it. It happens because the Linux drivers are not installed.

Ok sorry for posting this after so long but I have not had any time.

I am going to install the Kernel tomorrow to see if it works. Now should I run Make oldconfig or the other option(xconfig or menueconfig). I know it should work with the kernel but I am just going to install it anyway I think it will be a good experience(I hope). Is it a good idea to reinstall and configure the kernel using the old tree or just making a brand new kernel by downloading a more recent source tree?

That one is pretty much personal preference. I prefer using a more recent kernel, but again, that is a personal preference. I know other prefer the 2.4 kernels because they have been worked on for so long. My experience is that the 2.6 are stable, but I'm not pushing them to the limits.

If you run make oldconfig with a new kernel tree, it will ask you about any settings that aren't addressed by the old config. That can get a bit tedious however so I prefer to spend some quality time with make xconfig and set up things there.