Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I hate answering an "it hurts when I do this" question with a "don't do that" answer, but the orinoco modules are already there, compiled, and they actually work well with the DWL520. With kernel 2.4.20 you got .11b of the driver, which handles the newer firmware of the prism2.5 cards that the DWL-520 (and a bunch of others is based on). It hacks and barfs on encryption.
However, the .13x series of the orinoco is much better at WEP, and actually compiles easily...
ifconfig eth0 192.168.0.23 up
iwconfig eth0 essid Higgnet (on an opensystem actually unnecessary)
route add default gw 192.168.0.1
I tried to compile the needed modules into my kernel, but I'm having a little bit of trouble.
I managed to get orinico_cs in there with all of its necessary components, but orinico_pci is nowhere to be found. The only other module in there is plain old orinoco.
I'm pretty sure the problem is that I didn't enable PLX9052 based PCI cards, which it told me to do for full functionality, but I can't find that option in 'menuconfig'. I'm wondering if there's a way that I can just find the source for it, and compile and insert it into /lib/modules by hand.
I located orinoco_pci. It turns out it was experimental, and I had it so that it wouldn't prompt me for experimental options.
The modules are installed and working, but I still can't get the thing to connect to my server! I have no idea what is going on here. My network does not have a wep, and I have eth0 aliased to orinoco_pci .
There aren't any error messages generated, yet it still doesn't actually connect to my network. I can't even use 'route' to add the default gw. please help me!!
I won't be able to access the slack-box in question for a couple of days. As soon as I can, I'll give you those outputs, and I've got a few things I want to try, so hopefully this'll be over with pretty soon.
I got back to the house with the slackware box, and had my wlan up in no time. The real problem was that I didn't understand the BSD init system, so I was bringing up eth0 with iwconfig a little too late. There were also some other trivial proglems with my neighbors stupid linksys router, but I got that under control in no time.
I just spent a while debugging this, and I've found pretty much what causes it, and (maybe) what goes wrong. I am using a DWL=520 with the orinico_pci module.
"The crash" is basically network services being dumped. This doesn't happen in the way that the device loses its assigned adress, but that my card becomes disconnected from the wireless network. It happens almost immediately if I connect to the server from inside the network for ftp or vnc, but not when i connect for ssh.
Do get the network service back up, I have to bring the interface down, unload the module, and then re-run the network startup scripts.