i just bought:

-> D-LINK DI-614+
-> D-LINK DWL-520+

does anyone knows how to configure this under linux!??
(RedHat 7.3 Gnome)

thanx!

The 614 is just a wireless router, it'll do it its job just fine regardless of what's talking to it.

The dwl-520 I think I covered most of the steps in this thread already. You'll want to get the newest orinoco modules from here, compile them and then make certain you have wireless_tools installed (RH doesn't put it on there by default unless you specify "laptop" or "everything"), and then you should be good to go.

Gnome, KDE, whichever, none of them have a functioning graphic configurator for the card, this is going to be from the command line.

Post back if you get at all stuck,

Cheers,

Finegan

any HOW TO's or a guide
or maybe detailed explanation!??

i'm totally new to linux!

thanx!!!

You have to remember that wireless networking under Linux is just catching on, and HOW-Tos are hard to come by, especially ones that deal with desktop PCI cards that aren't as obvious as PCMCIA. The 2 I know of over at the Linux Documentation Project are pretty abysmal. I've rattled this off a lot, but here goes again. Almost all of this is from a command line, there is no GUI way of doing this just yet, although a couple of interesting projects are in the works:

Install the wireless_tools-???.rpm from the RedHat distribution CDs. Its usually just as easy as stick the cd in, poking around it with your window manager (one of the 2-3, it moves around between releases), and clicking on it.

The rest is all from the command line, and remember if you get no output back from any of these commands, that's almost always a good thing.

The drivers that shipped with the 2.4.18 kernel don't cover the PCI card you have. Download the source package from here. Version .12b should be fine, its compiled fine for me a couple of times. Stick it in just about any old directory. Unpack it and make it and install it with the following commands:

tar xvzf orinoco-0.12b.tar.gz
cd orinoco-0.12b/
make
make install

If those go off with no errors, you're doing well, if you do get errors, post back.

Now, to see if the drivers are working:

modprobe orinoco_pci
dmesg

Dmesg is the kernel's log of recognizing hardware as the kernel loaded, since a module is just another piece of the kernel, when its loaded and binds to some chunk of hardware, the new bit will be added to the end of dmesg. It should have a whole bunch of info about the card, the version, and a name for it, ethX, where X is a number. If this is the only ethernet device in the machine it will almost definately be eth0. I'll write the rest assuming that it is.

Now, lets bring up the card and give it some info:

ifconfig eth0 192.168.1.10 up (This brings up the device and gives it an IP address.)
iwconfig eth0 essid nameofwirelessnetwork (the essid is the name of whatever the wireless network goes by. Usually something like Linksys to begin with., iwconfig is one of the pieces of the wireless tools package from before.)
iwconfig eth0 rate auto (the rate at which data transfer will be set, you can force it to 1M/bit, 2, 5.5, and 11, but best just leave it at auto.)
iwconfig eth0 mode managed ( the 3 modes are: managed, which the Dlink router almost definately uses, ad-hoc, for pier-to-pier, and master (the same job of your wireless router), which your card can't do (with these drivers), but the tools are built for all cards.
You can set many other things through iwconfig and the other wireless tools, check out the man pages on them, but that should be the minimum necessary to get you connected, unless you're running encryption: WEP can be a headache. That's:

iwconfig eth0 enc Keynameornumberhere

Now, hit "iwconfig" with no arguments, i.e. nothing after iwconfig. It'll probably complain that wireless extensions is mis-matched, but that isn't a big deal, if you get information for eth0, you're good.

Most of these wireless routers are built to deal out IP addresses through dhcp, so manually invoke the client daemon for that with:

dhcpcd eth1

If you've got a new command prompt, you're golden, they're talking and you've got an IP from the router. Now, to automagic all of this:

I don't think the wireless scripts from /etc/pcmcia will get applied to this unless it were a pcmcia card so here's the ghettor-riffic hack I always use: edit /etc/rc.d/rc.local with something like pico. rc.local is the very last script run when the machine boots:

pico /etc/rc.d/rc.local

All of the pico commands will be at the bottom of the screen, they're easy. Add in the commands from above that you used:

ifconfig eth0 up
iwconfig eth0 essid bobbobbob
iwconfig eth0 rate auto
iwconfig eth0 mode managed
iwconfig eth0 enc yadyada
dhcpcd eth0

That should do it. If your machine is out of range of the wireless router or if for some reason the wireless router is down, when you boot up its going to sit there for 60 seconds or 2 minutes (again, I don't know the RH and dhcpcd defaults any longer) before it gives up and finishes booting normally. Many people mistake this for a hang.

Luck,

Finegan

Hi finegan and freakboy,
Since this thread is live again and I am also on this for last few days, I think I will just make use of it. I recently got a mother board by via ( mini-itx ), and we loaded win-xp on it. But even with the std windows driver which came with the card, it was not recognized. I then loaded RH7.3 and tried but had no luck. This board is also pci bios 2.1 compatible.
Freakboy, If you get it working, can you please post output of
dmesg | grep -i pci

Thanks,
--Sarin

Ok...

wireless tools isntalled...
**One problem i had with this was building the rpm!!!
i had a package called... wireless-tools-20-3.src.rpm
and i was trying to install it but nothing happend
does anybody knows how to build that kind of package!??
well, what i did is downloaded the wireless-tools-20-3.i383.rpm
from the net and everything went perfect... success...
**

now... i did:
tar xvzf orinoco-0.12b.tar.gz *it created a dir*
cd orinoco-0.12b *to access the dir!*
make *it gave me an error!!*
make install *same error*

THE ERROR:
cc -MD -02 -Wall -Estrinct-prototypes -pipe -D__Kernel__ -DPCMCIA_DEBUG=1
-DMODULE -DEXPORT_SYMTAB -I/lib/modules/2.4.18-3/build/include -c hermes.c
make: cc: Command not found
make: *** [hermes.o] Error 127

whats your advice, finegan!??

any ideas!??

Yeah... you haven't got a compiler installed. RedHat these days thinks RPM is the end all be all of everything and no one should be installing from source code... silly buggers, they don't install a compiler anymore unless you select the "developer" section during install.

Usually its not just as easy as rpm -U gcc.whatever. If you have one of those nifty wirly-do package managers with RedHat that'll auto-install dependancy RPMS that'll be the best bet, otherwise its a matter of snagging the first CD and trying to rpm -U cc-something or other and gcc-2.96 I think is still the RH default. cc is the precompiler. They'll probably both bitch about a ton of dependancies like make... no you have that, or it would have errored on the first line... hopefully you just need those 2.

Luck,

Finegan

Hi,
RH uses gcc and I find that 7.3 has gcc 2.96 as pointed out by finegan. You will still have a cc as a link to gcc. In my m/c it is in /usr/bin. To see if gcc is installed or not try, rpm -qi gcc. It will give you a description of the package along with the install date if it is installed or it will say it is not installed. Let me know if you find it difficult to install gcc. I will surely try to help.
--Sarin

Atlast we got it working with mini-itx board after reinstalling win-xp on it. Now I know I was wrong with my doubts about pci bios versions problem. Now I will try with RH7.3
--Sarin

ok, man have i made it far
i got 2.4.19 kernel compiled, and i jacked it up to all helll....so i tried and tried, and finally got it working, even with my built in ethernet(somehow i managd to screw that up) well i got it all working, then i got my pcmcia workin too, cuz when it boots it says start pcmcia or something alone those lines...so ok its all cherry till now. im tryin to compile in my dwl-650 (and i even work for their support line i just dont kno liux much yet) heres what ive gotten, and if anybody could point me in the right direction or what im doin wrong here...

soo i get the file linux-wlan-ng-0.1.9.tar.gz
i uncompress it..yaaay
i go into the dir, then run make config...everything goes 110% well, no errors..i had plenty before. and it says configuration successful, so i know that part went fine...i even know all the locations of my source and stuff(thanx yall)

next im supposed to run make all so i run it..seems to go thru fine right? well several times i get this....it enters several directories for my wlan stuff then leaves the dir saying nothing to do..

make[1]: Leaving directory `/usr/src/linux-wlan-ng-0.1.9/doc'
make[1]: Entering directory `/usr/src/linux-wlan-ng-0.1.9/man'
Nothing to do...
make[1]: Leaving directory `/usr/src/linux-wlan-ng-0.1.9/man'
make[1]: Entering directory `/usr/src/linux-wlan-ng-0.1.9/etc'
set -e; for d in pcmcia wlan; do make -C $d all; done
make[2]: Entering directory `/usr/src/linux-wlan-ng-0.1.9/etc/pcmcia'
Nothing to do
make[2]: Leaving directory `/usr/src/linux-wlan-ng-0.1.9/etc/pcmcia'
make[2]: Entering directory `/usr/src/linux-wlan-ng-0.1.9/etc/wlan'
echo "Nothing to do"
Nothing to do
make[2]: Leaving directory `/usr/src/linux-wlan-ng-0.1.


ok since im a noob at this i continue on thinking all is well and type make install...then i get this

make[2]: Leaving directory `/usr/src/linux-wlan-ng-0.1.9/src/mkmeta'
make[2]: Entering directory `/usr/src/linux-wlan-ng-0.1.9/src/wlancfg'
cp wlancfg /sbin
make[2]: Leaving directory `/usr/src/linux-wlan-ng-0.1.9/src/wlancfg'
/sbin/depmod -a
depmod: *** Unresolved symbols in /lib/modules/2.4.19/net/p80211.o
make[1]: *** [install] Error 1
make[1]: Leaving directory `/usr/src/linux-wlan-ng-0.1.9/src'
make: *** [install] Error 2


and i get these errors each time, and i have no real idea as to what to do...i kno some gurus out there gots to have the know how to show me the light. where am i goin wrong, i specify al the source dir's properly and everything 'seems' to go fine, but i kno ive jacked something up..
and also when i did my new kernel, i made sure to include all the wireless tools and utils that were available...so where am i goin wrong here? any help yall? thanx in advance

There are 3 sets of drivers in Linux for the DWL-650, heck for any of the prism2, 2.5 and 3 based wireless cards... the ones that DLINK, LInksys and the other manufacturers point you to are by far the most annoying to try to get compiled!!!

You might have built support for the dlink into the kernel without knowing it.

Are you still using pcmcia-cs or did you enable pcmcia in the kernel?

If you've enable in-kernel pcmcia, which I bet you have since that was the default with RH7.3 anyway and I don't think they give you the pcmcia_core module from the card services package anymore... then look to see if you have this module:

/lib/modules/2.4.19/kernel/drivers/net/wireless/orinoco.(anything)
this patch and sticking it in /etc/pcmcia. It'll tell pcmcia's cardmgr that it can bind the orinoco_cs module to the dlink card when it sees it.

Now onto how to manipulate the card settings... what you compiled into the kernel (hopefully, but it seems you were rather exhaustive), was the wireless extensions, which create a directory in /proc that the wireless_tools package can then manipulate to change setting like rate, mode, encryption, yaydya.

The Linux-wlan project doesn't use wireless extensions, ignores them, and basically went their own way.

to make sure you have wireless tools, which you almost certainly do since this is a laptop:

man iwconfig


You can only use the command as root, but anyone can read the man page, so that'll tell you if its there.

Restart pcmcia and listen for 2 identical high pitched beeps... then you're good to go. Use iwconfig to manipulate the settings...

Now, if you don't have the orinoco_cs modules:

Download the newer drivers from here, and just untar, make, make install them... the .12 is about 2 versions ahead of what's in 2.4.19, but most of the bugs were worked out as far back a .06b. You don't have to rebuild the kernel to get their functionality unless you left out some important other wireless support.

Aight, that's all I can think of, post back where you get stuck, this can be tricky.

Also, I have read a lot of reports about the orinoco modules not doing a good job for linksys wpc11 cards, just running slowly... if that happens I can point you to the 3rd, yes THIRD project that deals with these cards! No matter what it'll be easire than debugging a bad compile of the linux-wlan goop.

Cheers,

Finegan

ok, well when i compiled the kernel, i enabled pcmcia support, i also compiled in the pcmcia-cs thing from dlinks page thinking maybe my pcmcia was working right, soi think i have them both in there if that is possible, but im not sure which one im using...theyre there i know that

when it boots it says pcmcia init or something, and it goes OK but i never get the beeps that it says u should...

i compiled in wireless tools from the kernel, and theyre there
i also compiled in the ones that are linuxwlan-ng or something, and anotherset with iwspy and some others, well when i type the commands they work, but it says no wireless extensions and nowhere oin any part of my system can i find the other ethernet device active...ill be doin some more work l;ater on this and post my progress

When you compile pcmcia support in from the kernel, its the active one. Now here's the weird part:

All of the kernel modules for the pcmcia bus itself, and all of the support for cards are kernel modules, but it still uses the pcmcia-cs /etc/pcmcia directory of configuration files as well as the program cardmgr that binds modules to the pcmcia_core.o module in the case of pcmcia-cs or yenta_socket.o in the case of in-kernel.

To see which one is doing the job:

dmesg | more

If You see something like:

Yenta IRQ list 0689, PCI irq11
Socket status: 3000010

That's in-kernel,

Pcmcia-cs will have a dmesg report like:

Linux PCMCIA Card Services 3.1.26
kernel build: 2.2.19 #22 Wed Jun 20 18:12:16 PDT 2001
options: [pci] [cardbus]

The linux-wlan-ng project is completely incompatible with in-kernel pcmcia, hence the soggy compile.

Start from there.

Cheers,

Finegan

uh, i have both those showing up,the it goes like this

Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: Found IRQ 11 for device 00:0a.0
IRQ routing conflict for 00:07.5, have irq 5, want irq 11
PCI: Sharing irq 11 with 00:0b.0
Intel PCIC probe: not found.

somethign about my usb hub then this

Yenta IRQ List 0408, PCI irq11
Socket Status 30000010

then onto my usb again


so obviously theres a conflict or did i manage to instsall the kernel pcmcia and enable the other pcmcia module too??
and like i said those wireless toosl work
iwconfig says lo and eth0 no wireless extensions..
iwspy interface doesnt support wireless statictic collection.

so i think i managed to get the tools in there, and i managed to enable pcmcia, twice which is causing some sort of conflict..

but i have hope
when i goto my control center, and go under information to pcmcia, for card0 it shows dlink dwl-650 wireless adapter, so it is there but not working because of the pcmcia conflict? where have i gone wrong, i feel so close now!

such a learning expereince ive been having with linux lately, been lovin it, just feel like dumb, because it seems like im doin something right, onkly to go another step or two wrong, but hey eventually its working

any advice on what to do, or how to fix my conflict if that is the case