Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ive read just about every post I could find about this stupid thing and STILL it refuses to work. Whenever i do make config for the drivers I get the error "x windows include files missing" , ive tried installing pcmcia-cs to make it work and I still get the same error, what is the deal??????? I do everything else and I get the card to show up in ifconfig -a but then in iwconfig eth0 has no wireless extensions. im running lindows 4 which has kernel 2.4.20. Im seriously at the end of my patience, been working on this for a good 3 days. somebody PLEASE help me.
I'm assuming the module got loaded successfully and did not need you to do "insmod -f" on it. And that if you type "lsmod" from a console/terminal you see it listed.
The "no wireless extensions" issue has to do with a couple of settings that were either set or not set when the original kernel was compiled. Usually the config file that was used to compile the kernel is found somewhere in your /boot directory, it may be .config (dot config) or may be named something like "config" or "config-2.4.20", browse your /boot directory and open the most likely candidate in a text editor, then search for these 2 vars:
CONFIG_NET_WIRELESS, and CONFIG_NET_PCMCIA_RADIO.
If those vars either aren't there, or are set to "n", then wireless extension support is not present.
To get wireless extensions, you would need to re-compile the kernel changing only those 2 vars to "y" and changing nothing else, this can be fun, or it can be more annoying than what you're willing to endure. As an alternative, I would hope lindows has a choice of different kernels you could install and that you would be able to launch their "Control Center" or whatever the actual application is, and navigate to somewhere that allows you to install a different kernel. You could then pick a kernel with "wireless support", this would be the best scenario, that way you don't have to compile the kernel yourself.
The error message you refer to: "x windows include..." is annoying, but harmless, it just means that the setup utility for X-windows did not get built, obviously the module did get built or you would not get a device in your ifconfig -a, I truly hope the lvnet.
As an alternative to try before doing anything else, see if the other utility got built, it should be in atmelwlandriver/src/apps/cmd_line, and will be named nvnet, lvnet, fvnet, etc. In a terminal window, cd to that directory and type "./fvnet" (use the right name) and see if it comes up and works for you.
to tell you the truth i dont even know what a module is. Ive just started messing around with this type of stuf fin linux. Basically these are my steps:
I downloaded the atmel driver and extracted it to /home
ran make config
followed your options for yes an no
make all
make install
then i edited the pcmcia config file and added the two lines for the belkin
shows up in lsmod
shows up in ifconfig -a
shows up in iwconfig but "no wireless extensions"
and thats about it...
any step im missing here?
Would I just be better off going with a different version of linux? The only reeason i used lindows is because it doesnt take up much space and it looks nice.
Ive also tried compiling the kernel several times but each time i get an error after a few minutes, different with each time i download it. Really annoying.
Ah, the "make install" is not a step that co-exists with my howto, it adds things to /etc/pcmcia/config and places a startup-script in your path. It's basically either/or, that's why I don't have you do that in the howto. In any case, you may want to try slackware, mandrake or redhat as I have no experience w/Lindows. Not that Lindows is bad, just that I'll be taking shots in the dark as far as helping you get this going. To me, Slackware takes up the least amount of room and looks very nice also with KDE as default.
However, we don't have to give up on lindows just yet...did you check your config file in /boot? and, did you see if lvnet, nvnet or fvnet exists in that directory?
Ok I just looked in my current kernel config and both of those options are enabled, so Im lost. There must be a step im missing or screwing up or something, if you could please go through exactly what to do from begining to end to get this thing working as simple as possible I would really appreciate it. Ive done everything as far as I can tell right but it still doesnt work.
Sorry, that just happened to me also ( I have a different wireless card in my notebook right now so I hadn't tried it since my last compile) Anyway, cd back to that directory and do "chmod u+x fvnet", then "./fvnet", then, if it finds an atmel card (which of course for me it doesn't right now) you should be able to config your device.
If you see pcmf502rd.o in lsmod then I'm going to assume the kernel compile went wrong and that the error is related to re-compiling the kernel, happened to me in the beginning, maybe it happened to you also.
The config file in /boot is *supposed* to be an accurate representation of the configuration of the currently running kernel, *but*, if you've re-compiled the kernel, the config you really need to examine is going to be found as .config (dot config) in /usr/src/linux (may be /usr/src/linux-2.4.20), check that one if you would please.
Have you tried downloading a module from my howto for this chipset? I hope the slack9 module will work for you, the kernel version matches yours, let's check the gcc version, type "gcc -v" and look for "gcc version 3.2", also does pcmf502rd show up in lsmod or not?
Ouch, sadly I have no modules available that were compiled with that version of gcc, you're going to have to do it locally, this is going to work...
First, I'm thinking if your config is showing those vars set to "y", then the module must be bad, delete it out of wherever it is under /lib/modules/2.4.20 (cd to that dir and do "find -name pcmf502rd.o", then cd to it's location and rm it).
Then, go back to the atmelwlandriver source directory and do "make clean", then "make config", then only answer "y" to "build pcmcia drivers" and "build rev d driver" (or whatever it says about rev d), you should not get *any* errors. If it comes back and asks for the "location of external pcmcia", then post back and we'll fix that.
good work, now you'll need to copy the file to /lib/modules/2.4.20/kernel/drivers/net/pcmcia, from the atmelwlandriver top level dir, use "cp objs/pcmf502rd.o /lib/modules/2.4.20/kernel/drivers/net/pcmcia", then do "depmod -a", don't be alarmed by the "unresolved symbols", I get them on every machine/distro that I use this driver on, it still works w/slack, redhat, and mandrake, hopefully we can say that about debian soon.
once the depmod completes, do "rmmod pcmf502rd", then "cardctl eject" and then "cardctl insert", check lsmod for the presence of pcmf502rd, then ifconfig -a, then iwconfig...cross your fingers as you type
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.