Ok, i did it, woot ! I am dual booting windows 2k pro and slackware 9.0 . I got my wireless internet working with windows, but i can't get it to work with slackware 9.0 . I have no clue how to install drivers in linux or where to get them or if my wireless is even suported by slackware 9.0 . Any help with this would be much appreciated. You can Instant message me on my screenname ematrixxx or just leave a post and I will see it in a minute. Thankyou for your help again.

Once again it is a linksys wusb ver 2.6 wireless.

I've got the exact same problem :-(
..only i'm on mandrake 9.0
i believe you are supposed to use an "amtel wlan" driver but i've had problems getting it to install on my distribution.
maybe you'll have some luck with it

http://www.amtelwlandriver.sourceforge.net

try www.linux-wlan.org

I have mandrake 9.0 and slackware 9.0 installed on 2 different notebooks. The atmelwlandriver works on both, so don't give up.

You need to first make sure you have the development packages and the kernel source installed for your distribution. To test this, from a root console type: gcc -v, you should get version info back, not a "command not found". Next, type: ls -l /lib/modules/`uname -r`/build, that's a lowercase L, the character surrounding the uname -r is the one on the same key as the "~" which is left of the 1 key. build is a symlink to a directory under /usr/src/, which needs to exist and be populated.

If all goes well, download the atmelwlandriver source from this link: http://prdownloads.sourceforge.net/a...r.bz2?download
when it asks where to put it, I suggest /usr/src/ or /usr/local/src, depending, for this example we'll use /usr/local/src.
here's a list of commands to now exec from a root console:
1. cd /usr/local/src
2. bunzip2 atmelwlandriver.2.1.2.2.tar.bz2
3. tar xf atmelwlandriver.2.1.2.2.tar
4. cd atmelwlandriver
5. make config
6 These questions appear line-by-line, answer accordingly:
Build all [y/N] : n
Set extra module version information [y/N] : n
Build Debug version [y/N] : n
Build USB Drivers [y/N] : y
Build USB 503A RFMD Driver [y/N] : y
Build USB RFMD 505 Driver [y/N] : y
Build USB RFMD 505 + 2958 Driver [y/N] : y
Build PCMCIA Drivers [y/N] : n
Build miniPCI Driver [y/N] : n
Build applications [y/N] : n

Then something like this will appear:

Kernel Version Running 2.4.19-16mdk
Found Kernel Source Directory (/lib/modules/2.4.19-16mdk/build)
Finished. Now run make clean, all, install

7. make all
8. make install

post back if/when you get here, or before if you get errors.

Ok, all the stuff worked well. No problem, thankyou very much for that. However my network has a WEP encryption for the wireless, it is 64 bit and i know the hex for the encryption but I don't know how to make linux use it so i can go on my wireless network. The encryption is 64 bit. I would very much preffer to keep that up and not to have to drop it. Do you know how i can do this ?

wait nevermind, everything didn't work right, after i rebooted the folders where i installed the drivers vanished like they were never there. In my root directory i made a folder named usr inside that i made one named local and that is where i did it all, is that what i was supposed to do ? or where is the usr/local file located ??? lol

aight i tried installing the amtel driver with the above configuration and it all worked out good
the only thing that caught my attention was that when i did 'make install' it said something about a directory (i think pcmcia or similar) was either not a file or just not there or w/e i forget. after that it said OK and returned to the root prompt

maybe i'm doing "OK" then haha

i dont think i need WEP encryption or whatever ematrixxx said he needs but i do have all the information i believe i need to connect to our (home..) network such as my default gateway, DHCP servers, IP Address and physical adress

thanks for all the help !
~mike

ematrixxx,
It doesn't much matter where you located the atmelwlandriver directory, ie whereever you tar xf'd it to is fine, just so's you can get back there , from a root console, type cd /root and then ls -A and see if you can then cd down into the atmelwlandriver directory, once there, cd one more time to the objs directory, then see if some modules (.o files) and some .map files exist with today's date by doing a ls -l, if so you've done well.

gatblast45,
Sorry, forgot about that little mandrake snafu, from a root console type this: ln -s /lib/modules/`uname -r`/kernel/drivers/net/pcmcia /lib/modules/`uname -r`/pcmcia, all on one line, let it wrap if it wants to. Then from you atmelwlandriver directory, type make install again.

Here's what i got even after i added the command you told me to enter and typed make install:

[root@localhost amtelwlandriver]# make install
set -x
grep: /etc/pcmcia/wireless.opts: No such file or directory
install: cannot create regular file `/etc/pcmcia/': Is a directory
depmod -aq
OK
[root@localhost amtelwlandriver]#

umm yeah.. help plz :-D

Ok, that pcmcia stuff is an error in their script (I'm assuming so, since you're using a usb device and told it not to make the pcmcia drivers)

In the meantime, type ls -l /lib/modules/`uname -r`/kernel/drivers/usb and look in the list for some new modules with today's date, they would have the .o extension unlike the existing ones which would have the .gz extension. If you see them and the depmod went ok as it appears to have, it's time to load these puppies and figure out which one you'll need. Post back with the names of the modules and we'll issue some cmds to load and test.

EDIT: sorry 'bout that, I keep forgetting you're using a usb device (mine's a pcmcia card), note that I changed the look in directory from /lib/.../pcmcia to /lib/..../usb

I have a problem, when I am in slackware, whenever I try to access the floppy which I am sure has the driver on it, and yes I know its a good. It doesn't see anything in the floppy drive. The same when I put in other floppies. The previous time when I installed the driver it worked fine and it saw everything on the disk. Whats going on ????

okay i typed the command and i got this from the modules list

usbvnet5_2958.o
usbvnet5.o
usbvnetr.o

thnx for everything

Im still having the problem with my floppy drive when I am in slackware ???

ematrixxx,
it sounds like you need to mount the floppy, try this: mount /dev/fd0 /mnt/floppy, then cd /mnt/floppy and your files should be there. Before removing the floppy, be sure to: unmount /mnt/floppy and wait for the light to go out.

gat,
now the trick is to determine which of those 3 will be the right one, I'm gonna guess it's usbvnet5.o, although it's just a guess. Anyway, some preliminary testing: with the device in, from a root console type: cat /proc/bus/usb/devices post the relevant output.

ps: sorry to take so long getting back to you, my wife made me vacuum and mop the floors, doh! Also, sorry to be doing this in such a fragmented way, but I don't have the device, so I'm figuring it out along with you.