I have been trying to compile the Atmel WLAN drivers for my Linksys WUSB11 2.6 but it keeps returning an error that there is an undeclared variable SIOCIWFIRSTPRIV in the vnetusb.cpp file. I went into the file and there is, in fact, an undeclared variable but I can't figure out where they wish to declare it or what as. The only time they use it is in two other #declare statements.. Example (not actually from code but similar):
#declare SIOCIWPRIVA SIOCIWFIRSTPRIV + 0x01
Has anyone had this problem or does anyone know how to solve it?

I just got a clean compile using the snapshot from 12-23, what version are you using?

Cheers,

Finegan

I used the 12-23 sources as well. What distro/kernel are you using? I am currently running Mandrake 8.1/2.4.8. I think it might be something with the early kernel or the distro. I'm actually downloading Red Hat 8 now to see if that fixes the problem. Hopefully I can get it to work as I can't return the WUSB11 and I don't want to spend extra money on a wireless bridge, etc...

Also, I searched on google and found that I could add:
#ifndef SIOCIWFIRSTPRIV
#define SIOCIWFIRSTPRIV SIOCDEVPRIVATE
#endif
to define it. After adding it though, the compiler told me that there were multiple instances of a case in the switch. I found it but I wasn't sure how to fix it. The instances were (I think):
case SIOCDEVPRIVATE
case SIOCIWPRIVA
SIOCIWPRIVA was defined as "SIOCIWFIRSTPRIV + 0x0" so obviously, it is the same as DEVPRIVATE... Any thoughts?

aha, there were some extreme changes to how the kernel handles networking modules around 2.4.10, don't worry that old Mandrake will handle a newer kernel, I was running 2.4.16 on a Mandy 8.0 laptop a long while ago. Even if you get it to compile, I doubt it will load... your kernel is at least a year and change old.

Mine was on a stock Slack 8.1 with gcc 2.95.3 and 2.4.20-xfs, although I really hope the problem isn't with the compiler, check the atmel site to see if the funky 2.96.x that shipped with the middle 8.x Mandrakes isn't the issue, that was one of the biggest issues with Mandy and RH for a long time. gcc -v will tell you the name of the compiler; and if it looks clear, grab yourself a copy of the 2.4.20 source, fun stuff!

Cheers,

Finegan

I have the Mandrake 9 cd's that use the 2.4.19 kernel by default. I think I'll attempt an upgrade rather than recompile/install a whole new kernel with my little knowledge for now. Hopefully that will work with the drivers but what about the undeclared variable or the multiple-use case statement? If I remove the declaration that I found, will the new kernel have the variable built in or is there something I'm missing? If I don't remove the variable I need to put the code from the SIOCIWPRIVA case somewhere (maybe at the end of the SIOCPRIVATE case?)... If that doesn't work, I guess I can try RH8.

I have no idea why mine compiled and yours didn't, I'de have to trace through a lot of C, which I suck at, and I'm willing to bet the dropped variable is in an apendix section of code that doesn't get used anyway. Distro doesn't matter, its all compiler, and if you use a newer Mandrake or a newer RedHat, either way you'll be using a 3.x.x compiler, a much newer one than you're using now.

Also, most importantly you'll be using a kernel it can load into.

Cheers,

Finegan

I did a clean install of Mandrake 9 and the compilation worked but depmod -a said that there were unresolved symbols in the module. I actually froze the computer a few times trying to use modprobe with the unresolved symbols because the Makefile uses depmod -aq so you don't see the errors. I finally thought to check when lsmod returned that the module was "initializing" after like 5 minutes. Have you experienced the unresolved symbols? I can't figure it out and it is driving me crazy!

Also, what should I enter for mode type? I was thinking "Infrastructure" but I was thinking that it might be case-sensitive or something...

That is just odd module behavior, I honestly don't know and really infact doubt the module is working correctly. I would poke through the mailing list archive or the bugs lists from the atmel driver page and see if anyone else is having issues with Mandy 9's stock 2.4.19.

Cheers,

Finegan