Where???
 

Where can i get linux dlink dwl-650 air plus drivers

i need them desperately

Drivers for the DWL-650+ are here. You would probably be better off getting a non-ACX100 based card though.

Håkan

ok i got that but dont know how to install it..

please help im a newb

If you looked a little harder they have links and in which they have a specific newbie link here: http://www.houseofcraig.net/acx100_howto.php

ok sry... thanks

hmm.. im still confused..

can someone waste a little time and give the direct link the the best drivers for the dlink dwl650 air plus..

im running the newest mandrake if that helps.. and also instructions on how i get from 1 computer to another.. im on my other comp which is running winxp

Those are the best drivers and most likely only drivers. These drivers are specifically for your chipset used in this card. No other drivers are going to work most likely.

yeah well i dont understand how to download/install them

im new 2 linux and dont understand all those commands

Well, don't know what to tell you really then. I don't think I could explain it any better than what or how that page explains how to install them.

heres what it says

"To obtain a copy of the driver via CVS, please do the following:
$ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/acx100 login
$ cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/acx100 co acx100
When prompted for a password, just hit Enter.

The CVS versions have also been tagged as acx100_0_1c, acx100_0_1d and acx100_0_1e, and so on.

Due to the current extreme lag of the public SourceForge CVS server, it may take about a day for the changes to arrive in public CVS. The driver version can be verified e.g. using "cvs log README".
Note that the CVS server is also pretty unreliable (probably due to extremely high load).
You might frequently get:
end of file from server (consult above messages if any)
To fix this, either retry multiple times, or run it in a bash shell loop even, until it succeeds (abort with Ctrl-C):
while true; do COMMAND; done

Tarballs
Although CVS is much preferred (you can download incremental changes instead of redownloading an entire tarball), we also provide snapshots of various acx100 versions.

Incremental patches
Starting with version 0.2.0pre6 we also provide patches against the last release in the files section of the project page. "




------------------
first of all... what does this mean!?
$ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/acx100 login
$ cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/acx100 co acx100

where do i type that in!?!

If you don't understand a command, you can always read the manual on it by typing:

man <command>

Maybe this will help you. Linux is not easy, if you want to learn it, your going to have to learn how to read docs and manual pages to get anywhere with using Linux or it might not be worth your time.

Those instructions are pretty straight forward, I don't think you would actually need to know the commands fully to follow the directions.

Why don't you just start off, attempt it and if you run into any problems, then ask for help on something specific.

I really won't know what else to tell you unless you want me to come over and do it for you.. :rolleyes:

lol..

Ok.. need some more help...

i dont understand these instructions..

----------------------------------------------------------
Using a text-editor like gedit, kedit, or kate, open the file /etc/modules.conf, type: kedit /etc/modules.conf &, substitute your editor of choice for kedit, if you're not using a windowing system, then type: vi /etc/modules.conf, hit the "i" key to go to edit mode, do your editing and when finished, hit esc to go back to command mode, and then type :x to save the file and exit vi, if you feel that you've hopelessly screwed things up, type esc for command mode and :q! to quit without saving, then start over. Add this line: options acx100_pci use_eth_name=1 debug=0x01 firmware_dir=/lib/modules/acx100_fmwe to the end of the file and save it. If you're using a PCI card, you'll need to add this line as well: alias eth0 acx100_pci, if there is already an alias there for eth0 and you're sure you have another ethernet/lan card in your machine, use eth1 instead and use eth1 as your devicename in all instructions that follow!. CardBus (pcmcia) users don't need or want this line, the hotplug system will load the module
-----------------------------------------------------------

does someone have aim or some chat program so its easier??

anyway.. i dont understand what to do.. i hit the i key and it just types and i.

help

i have the files in the correct directory but i cant figure where to go from there

You do not need to press "i" if you are using kedit, gedit, kate, etc. "i" is a VI command that changes the mode to insert.

Ok. The instructions are telling you to modify the /etc/modules.conf file. You need to open this file somehow. I do not recommend that you, being a beginner, use vi (a command line text file editor).

Instead, you should (and probably aleady are) run KEDIT, GKEDIT or some other graphic text editor. Open the /etc/modules.conf file. The only problem is you wont be able to save directly, as the /etc/modules.conf file has root permissions. Most likely you are logged in as a non-root user (at least you should be!) and thus the current instance of whatever application you are running will have permissions equivalent to your user.

So, what do you do then? Try this: open a command line. type "su" and press enter. Enter the root password. You should know what this is. If you don't, there's no sense in going any further.

Now you are root. Don't try going beyond the scope of what I'm telling, you, otherwise you could potentially destroy your system. Root is dangerous and must be treated with absolute care.

Still at the command line (as root now), you need to type "kedit". I'm assuming you're in KDE, so kedit should be available. If not, try 'gedit'. Soon it will load. Don't worry about any text you see scrolling on the command line window. The system is just creating some files. Now if it errors, well, yeah, that's useful information. File->Open, and go to /etc/ and open the modules.conf file.

From here, it's fairly straight forward. This is nothing more than editting a file. In fact, all you need to do is add the following to the end of the file.
The instructions note that if you are using a PCI card, you need to add this as well (after the above line):
Then, simply save the file and close. Type "exit" on the command line.

HTH

gotcha.. thanks a lot frozen