Wireless Extension version problem?

jeffk42 · 05-17-2005, 12:10 PM

I have a Compaq R3000Z AMD64 3700+ running FC3 x86_64 and kernel 2.6.11-1.14.

I'm using ndiswrapper for the Broadcom wireless card, but I'm getting the following when I run iwconfig:

Code:

Warning: Driver for device wlan0 recommend version 18 
of Wireless Extension, but has been compiled with version 17, 
therefore some driver features may not be available...

Now, it seems that "some driver features" includes a usable connection. Everything looks fine, I can scan for AP's, etc. (I get that message in iwlist as well), and I can even connect to an AP from what I can tell. I just can't actually get anywhere with it.

iwconfig -v gives me the following:

Code:

iwconfig  Wireless-Tools version 27
          Compatible with Wireless Extension v11 to v17.

Kernel    Currently compiled with Wireless Extension v17.

wlan0     Recommend Wireless Extension v18 or later,
          Currently compiled with Wireless Extension v17.

Can anyone help me with this? I'm not sure how to deal with this problem.

Thanks,
Jeff

Ephracis · 05-17-2005, 12:30 PM

Your kernel is compiled with WE 17 and you need 18.

So what you should do is either

1) Patch your kernel source with a new WE
2) Or try a kernel that has WE 18.

I am using kernel 2.6.11.7 and it only has v. 17 so I do not know if there is any kernel that has v. 18 actually, I would guess that you need to patch the kernel to get the new version.

jeffk42 · 05-17-2005, 01:59 PM

So.... how would I go about patching the kernel? Is it something I should even try if I'm no guru on the subject?

finegan · 05-17-2005, 08:40 PM

The extensions mismatch probably isn't it. Usually you can ignore that. Take a look at the ndiswrapper mailing list, there are a lot of issues right now running the windows driver (32-bit), with a kernel wrapper for a native 64-bit install.

Cheers,

Finegan

jeffk42 · 05-18-2005, 07:12 AM

Quote:

Originally posted by finegan
The extensions mismatch probably isn't it. Usually you can ignore that. Take a look at the ndiswrapper mailing list, there are a lot of issues right now running the windows driver (32-bit), with a kernel wrapper for a native 64-bit install.

Cheers,

Finegan

What's really bothering me about this is the fact that it was running flawlessly until I reformatted/reinstalled FC3. I never had any issues at all.

finegan · 05-18-2005, 11:20 AM

Quote:

Originally posted by jeffk42
What's really bothering me about this is the fact that it was running flawlessly until I reformatted/reinstalled FC3. I never had any issues at all.

Really? Just curious, I've got a friend fighting with his 64-bit Gateway machine and ndis, under Gentoo and native 64-bit, was your Fedora 2 install 64-bit or the stock 32?

Cheers,

Finegan

jeffk42 · 05-18-2005, 12:50 PM

Quote:

Originally posted by finegan
Really? Just curious, I've got a friend fighting with his 64-bit Gateway machine and ndis, under Gentoo and native 64-bit, was your Fedora 2 install 64-bit or the stock 32?

Cheers,

Finegan

I've never run Fedora 2 on this machine, just 3. It's always been 64-bit. I think I may have figured out the problem, but I won't know for sure until I'm at home with the AP. I think using ndiswrapper-1.1 might solve my problem. It's the only thing I can think of that is different than before (I'm using ndiswrapper-1.2rc1 now)

What problem is your friend having? I may have run across it before...