SlackwareThis Forum is for the discussion of Slackware Linux.
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.
What, EXACTLY, did you type when you made the ralink drivers?
The linr should say
Code:
make -C /usr/src/linux SUBDIRS=$PWD modules
I followed the readme file's instructions and typed 'make' and then 'make install'. The next line that came up after 'make' was the line I copied here before. After that, make continued to build the drivers without problem until it brought up the prompt again.
you don't need to add these same parameters (witht their WLAN_ prefix) to rc.inet1.conf. You can do either one or the other. If both files contain a value for the same parameter, the value in rc.inet1.conf will override the value in rc.wireless.conf.
So I've read on several sites. That's why I edited both but only pasted the rc.inet1.conf file at first and used that. It's only as a last resort that I also pasted the rc.wireless.conf in /etc/rc.d.
Some questions/remarks:
A WEP key like this should be a series of 26 HEX characters (0123456789abcdef) if you use 128bit WEP (look in rc.wireless.conf for several examples) or provide an ASCII string (a readable passphrase usually). The format in which these are configured is different.
This is a HEX WEP key definition:
Code:
KEY="4b7b4e23233b3d6a5954274375"
while this is a WEP key defined by a passphrase:
Code:
KEY="s:mysecretstring"
See the difference? The "s:" tells iwconfig that an ASCII string follows instead of HEX characters.
Your own value definition fits neither of the two. Not only that, but the remainder of your configuration shows you really want to use WPA:
So the advice would be to get rid of those "KEY=...." statements.
Furthermore, the rt2500 driver does not use wpa_supplicant for the WPA support, so you should leave out that second line. The first line is OK, provided you add a 63 HEX-character WPA key there in place of the AD26A55618...
That leaves something like:
while removing all your configuration from rc.wireless.conf. Remember to not use the settings in RT2500STA.dat (remove that file) if you want Slackware to configure the card using the rc conf files.
Eric
The AD26A66518 key is, according to the user guide, the hex-code for WEP and also the WPA-key. The Modem/Router has a sticker on the back that shows the following:
WEP (HEX):AD26A55618
WPA: AD26A55618
I've gone through the setup process for WPA and the guide states that for a 64-bit key (or 128-bit), you need to type I think 10 or more ASCII characters. I don't have it handy, so I can't tell you exactly how many. On a previous occassion, I did put the s: in front of the passphrase in rc.inet1.conf but even with that (see my first post), I couldn't connect. Or rather, according to the RaConfig tab showing activity, the connection was made and immediately broken and remade ad infinitum. As for the configuration of the modem, as far as I can tell, by doing as if I was making a new WPA key, I could only add a passphrase. Nowhere did it show a hex representation of the passphrase.
I haven't checked to see if the .dat file is there, but I thought that was only build if you used RaConfig and since I didn't build it, I didn't check. Still doesn't explain why now, unlike previous times, the card's lights don't light up.
I'll try that, thanks. How is it that make only works with the 2.4 kernel? Isn't it the same as the ./configure-make-make install usually used when working with source code? And according to the readme in the files, it should work for both 2.4 and 2.6 kernels.
I've been doing it that way for a long time now, and it works. I think it started from when I tried the ralink drivers, and when I carried it over to the serialmonkey ones, it worked. And always has...
CW, I just checked. I have the Ralink Sourcecode on this computer and the line you gave is indeed for 2.6 kernels but thatis with the Ralink source. The Serialmonkey readme used 'make' for both kernels.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.