LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-14-2006, 03:26 PM   #16
Mr. Spencer
LQ Newbie
 
Registered: May 2004
Location: Netherlands
Distribution: Suse 10.0, Slackware 10.2
Posts: 19

Original Poster
Rep: Reputation: 0

Quote:
Originally Posted by cwwilson721
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.
 
Old 08-14-2006, 03:28 PM   #17
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Rep: Reputation: 67
'make' usually only works with the 2.4 kernel.

Use the line I gave you above.
 
Old 08-14-2006, 03:46 PM   #18
Mr. Spencer
LQ Newbie
 
Registered: May 2004
Location: Netherlands
Distribution: Suse 10.0, Slackware 10.2
Posts: 19

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Alien Bob
Hi

If you add parameters to rc.wireless.conf. like
Code:
ESSID="SPEEDTOUCH6E9193"
MODE="MANAGED"
KEY="AD26A55618"
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:
Code:
IFNAME[1]="ra0"
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]="yes"
WLAN_ESSID[1]=SPEEDTOUCH6E9193
WLAN_MODE[1]=Managed
WLAN_IWPRIV[1]="AuthMode=WPAPSK EncrypType=TKIP WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
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.
 
Old 08-14-2006, 03:50 PM   #19
Mr. Spencer
LQ Newbie
 
Registered: May 2004
Location: Netherlands
Distribution: Suse 10.0, Slackware 10.2
Posts: 19

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by cwwilson721
'make' usually only works with the 2.4 kernel.

Use the line I gave you above.
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.
 
Old 08-14-2006, 03:52 PM   #20
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Rep: Reputation: 67
The readme is wrong? Perish the thought....lol


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...


I just did it yesterday...
 
Old 08-14-2006, 03:53 PM   #21
Mr. Spencer
LQ Newbie
 
Registered: May 2004
Location: Netherlands
Distribution: Suse 10.0, Slackware 10.2
Posts: 19

Original Poster
Rep: Reputation: 0
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.
 
Old 08-14-2006, 04:02 PM   #22
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Rep: Reputation: 67
Use it anyway. It works. Try it.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Wireless connection problem: NETGEAR MA401RA pcmcia madrico Linux - Hardware 4 07-28-2006 01:32 PM
rt2500 wifi cards in ubuntu dapper-strange problems anuski Linux - Wireless Networking 2 06-13-2006 09:55 AM
network connection (PCMCIA) dying zefo Slackware 0 04-29-2006 03:47 AM
RaLink RT2500 loosing connection Bjerrk *BSD 1 03-17-2006 07:40 AM
Rt2500 wlan problems Bjerrk Linux - Hardware 3 11-13-2005 04:59 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:15 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration