LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 07-26-2007, 01:40 PM   #1
pliqui
Member
 
Registered: Feb 2007
Location: Caracas, Venezuela
Distribution: Debian x64
Posts: 156

Rep: Reputation: 17
Installing a Linksys WMP54G wireless card


Hello all, i'm trying to setup a wireless card, a linksys WMP54G. i dont know the version but i'm sure the chipset is ralinktech RT2500, because i used the drivers for windows from ranliktech
my kernel
Code:
Linux debian 2.6.21-2-k7 #1 SMP Wed Jul 11 04:29:08 UTC 2007 i686 GNU/Linux
i used this tutorial to install it
but nothing happens http://rt2x00.serialmonkey.com/wiki/...n_rt2500_Howto

but when i'm doing the module-assistant auto-install rt2500-source i got this error.

Code:
touch config.mk \                                                          ↑ 
 │         && /usr/bin/make clean                                             ▮ 
 │ make[1]: Entering directory `/usr/src/modules/rt2500'                      ▒ 
 │ make[1]: Leaving directory `/usr/src/modules/rt2500'                       ▒ 
 │ dh_clean                                                                   ▒ 
 │ /usr/bin/make  -f debian/rules kdist_clean kdist_config binary-modules     ▒ 
 │ make[1]: Entering directory `/usr/src/modules/rt2500'                      ▒ 
 │ touch config.mk \                                                          ▒ 
 │         && /usr/bin/make clean                                             ▒ 
 │ make[2]: Entering directory `/usr/src/modules/rt2500'                      ▒ 
 │ make[2]: Leaving directory `/usr/src/modules/rt2500'                       ▒ 
 │ dh_clean                                                                   ▒ 
 │ for templ in ; do \                                                        ▒ 
 │     cp $templ `echo $templ | sed -e 's/_KVERS_/2.6.21-2-k7/g'` ; \         ▒ 
 │   done
seems the card is installed
Code:
lspci | grep RT2500
04:08.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
how can i enable it?.

Thanks !!
 
Old 07-28-2007, 02:54 PM   #2
Lunate
LQ Newbie
 
Registered: Jul 2007
Distribution: Gentoo
Posts: 16

Rep: Reputation: 0
lspci would show the card even if the driver wasn't installed. Use dmesg or tail /var/log/messages to see if the driver detected the card or not. modprobe rt2500 loads the driver.

I would advice you to use the next-gen drivers though (rt2x00), and install them according to the README file.
 
Old 07-29-2007, 04:53 PM   #3
pliqui
Member
 
Registered: Feb 2007
Location: Caracas, Venezuela
Distribution: Debian x64
Posts: 156

Original Poster
Rep: Reputation: 17
Thank for the info but i did the commands you wrote but i couldnt find the wireless card (i'm new to linux, so i can make mistakes)

and for the drivers you sent to me, the 1st thing on the readme is the kernel.

The minimal required kernel version is 2.6.22-rc1 is what the driver is need and i have Linux debian 2.6.21-2-k7. So i can use those drivers?

Thanks !

Last edited by pliqui; 07-29-2007 at 05:01 PM.
 
Old 10-11-2007, 06:25 PM   #4
Rex Bachmann
LQ Newbie
 
Registered: Oct 2007
Distribution: SuSE Leap 42.1
Posts: 5

Rep: Reputation: 0
Linksys WMP54G PCI-Adapter v4.1

So, I'm stuck in a new temporary place with only wireless Internet connectivity

I bought a Linksys WMP54G PCI-Adapter v4.1 for my openSuSE 10.2 system (Linux kernel 2.6.18.2-34)and am trying to get to work. I hoep the RT61 driver is the correct one.

I've followed the build instructions (to the extent they are explicit, and to the extent they are not, I have taken my best guess).


The build-instructions from the README

Quote:
RT61

2007_1003_RT61_Linux_STA_v1.1.1.0 driver

* README
*
* Ralink Tech Inc.
*
* hypertexttransferprotocol://worldwideweb.ralinktech.com
*

=======================================================================
ModelName:
===========
RT61 Wireless Lan Linux Driver


=======================================================================
Driver lName:
===========
rt61.o/rt61.ko


=======================================================================
Supporting Kernel:
===================
linux kernel 2.4 and 2.6 series.
Tested in Redhat 7.3 or later.


=======================================================================
Description:
=============
This is a linux device driver for Ralink RT61 a/b/g WLAN Card.


=======================================================================
Contents:
=============
Makefile.4 : Makefile for kernel 2.4 series
Makefile.6 : Makefile for kernel 2.6 series
Makefile.RTL865x : Makefile for big endian platform
*.c : c files
*.h : header files


=======================================================================
Features:
==========
This driver implements basic IEEE802.11. Infrastructure and adhoc mode with
open or shared or WPA-PSK or WPA2-PSK authentication method.
NONE, WEP, TKIP and AES encryption.


=======================================================================
Build Instructions:
====================

1> $tar -xvzf RT61_Linux_STA_Drv_x.x.x.x.tar.gz
go to "./RT61_Linux_STA_Drv_x.x.x.x/Module" directory.

2> $cp Makefile.4 ./Makefile # [kernel 2.4]
or
$cp Makefile.6 ./Makefile # [kernel 2.6]
or
$cp Makefile.RTL865x ./Makefile # big endian platform

3> [kernel 2.4]
$chmod 755 Configure
$make config # config build linux os version

4> $make all # compile driver source code

5> $cp rt2561.bin /etc/Wireless/RT61STA/ # copy firmware
$cp rt2561s.bin /etc/Wireless/RT61STA/
$cp rt2661.bin /etc/Wireless/RT61STA/

6> $dos2unix rt61sta.dat
$cp rt61sta.dat /etc/Wireless/RT61STA/rt61sta.dat
# !!!check if it is a binary file before loading !!!

7> $load
#[kernel 2.4]
# $/sbin/insmod rt61.o
# $/sbin/ifconfig ra0 inet YOUR_IP up

#[kernel 2.6]
# $/sbin/insmod rt61.ko
# $/sbin/ifconfig ra0 inet YOUR_IP up

Well, here's what I did:


homecomputer:/home/[my name]/builds # tar -xvzf /home/[my name]/downloads/RAlink-d
ownloads/2007_1003_RT61_Linux_STA_v1.1.1.0.tgz
2007_1003_RT61_Linux_STA_v1.1.1.0/
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/assoc.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/auth.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/auth_rsp.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/config.mk
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/Configure
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/connect.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/eeprom.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/ifcfg-ra0
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/iwpriv_usage.txt
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/load
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/Makefile
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/Makefile.4
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/Makefile.6
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/Makefile.RTL865x
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/md5.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/md5.h
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.h
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/oid.h
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/README
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/ReleaseNote
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rt2561.bin
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rt2561s.bin
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rt2661.bin
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rt2661.h
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rt61sta.dat
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp.h
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_data.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_def.h
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_info.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_init.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_main.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_task.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_tkip.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_type.h
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_wep.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rt_config.h
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/sanity.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/STA_iwpriv_ATE_usage.txt
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/sync.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/unload
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/wpa.c
2007_1003_RT61_Linux_STA_v1.1.1.0/Module/wpa.h
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/defconfig
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/driver.h
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/drivers.c
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/driver_ralink.c
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/driver_ralink.h
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/events.c
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/Makefile
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/README
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/vssver.scc
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/wpa_supplicant.c
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/wpa_supplicant_example.conf
2007_1003_RT61_Linux_STA_v1.1.1.0/WPA_Supplicant/wpa_supplicant_i.h
. . . . .
homecomputer:/home/[my name]/builds # ls /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0
Module WPA_Supplicant
homecomputer:/home/[my name]/builds # cd /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0 # cd /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # ls
assoc.c Makefile.4 rt2561s.bin rtmp_task.c
auth.c Makefile.6 rt2661.bin rtmp_tkip.c
auth_rsp.c Makefile.RTL865x rt2661.h rtmp_type.h
config.mk md5.c rt61sta.dat rtmp_wep.c
Configure md5.h rt_config.h sanity.c
connect.c mlme.c rtmp_data.c STA_iwpriv_ATE_usage.txt
eeprom.c mlme.h rtmp_def.h sync.c
ifcfg-ra0 oid.h rtmp.h unload
iwpriv_usage.txt README rtmp_info.c wpa.c
load ReleaseNote rtmp_init.c wpa.h
Makefile rt2561.bin rtmp_main.c
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # cp Makefile.6 ./Makefile
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # make all
make -C /lib/modules/2.6.18.2-34-default/build SUBDIRS=/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module modules
make[1]: Entering directory `/usr/src/linux-2.6.18.2-34-obj/i386/default'
make -C ../../../linux-2.6.18.2-34 O=../linux-2.6.18.2-34-obj/i386/default modules
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_main.o
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_main.c: In function RT61_probe:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_main.c:229: warning: device is used uninitialized in this function
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.o
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c: In function STAMlmePeriodicExec:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c:733: warning: unused variable RxSignal
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c: In function MsgTypeSubst:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c:3394: warning: unused variable Return
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c: In function AsicSetRxAnt:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c:5439: warning: R77 may be used uninitialized in this function
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c: In function RadarDetectionStop:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c:5877: warning: R66 may be used uninitialized in this function
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c: In function AsicSendCommandToMcu:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c:5345: warning: i may be used uninitialized in this function
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c: In function AsicAdjustTxPower:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c:4327: warning: BbpR1 may be used uninitialized in this function
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c: In function AsicSwitchChannel:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/mlme.c:3647: warning: BbpReg may be used uninitialized in this function
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/connect.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/sync.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/assoc.o
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/assoc.c: In function link_status_handler:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/assoc.c:810: warning: embedded \0 in format
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/assoc.c:834: warning: embedded \0 in format
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/auth.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/auth_rsp.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_data.o
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_data.c: In function RTMPHandleRxDoneInterrupt:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_data.c:652: warning: ISO C90 forbids mixed declarations and code
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_data.c:684: warning: ISO C90 forbids mixed declarations and code
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_data.c: In function RTMPSendRTSCTSFrame:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_data.c:1982: warning: unused variable IrqFlags
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_data.c: In function RTMPHardTransmit:
/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_data.c:2164: warning: unused variable IrqFlags
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_init.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/sanity.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_wep.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_info.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/eeprom.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_tkip.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/wpa.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/md5.o
CC [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_task.o
LD [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rt61.o
Building modules, stage 2.
MODPOST
CC /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rt61.mod.o
LD [M] /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rt61.ko
make[1]: Leaving directory `/usr/src/linux-2.6.18.2-34-obj/i386/default'
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module #
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # ls
assoc.c iwpriv_usage.txt rt2561.bin rtmp_info.c .rtmp_wep.o.cmd
assoc.o load rt2561s.bin rtmp_info.o sanity.c
.assoc.o.cmd Makefile rt2661.bin .rtmp_info.o.cmd sanity.o
auth.c Makefile.4 rt2661.h rtmp_init.c .sanity.o.cmd
auth.o Makefile.6 rt61.ko rtmp_init.o STA_iwpriv_ATE_usage.txt
.auth.o.cmd Makefile.RTL865x .rt61.ko.cmd .rtmp_init.o.cmd sync.c
auth_rsp.c md5.c rt61.mod.c rtmp_main.c sync.o
auth_rsp.o md5.h rt61.mod.o rtmp_main.o .sync.o.cmd
.auth_rsp.o.cmd md5.o .rt61.mod.o.cmd .rtmp_main.o.cmd .tmp_versions
config.mk .md5.o.cmd rt61.o rtmp_task.c unload
Configure mlme.c .rt61.o.cmd rtmp_task.o wpa.c
connect.c mlme.h rt61sta.dat .rtmp_task.o.cmd wpa.h
connect.o mlme.o rt_config.h rtmp_tkip.c wpa.o
.connect.o.cmd .mlme.o.cmd rtmp_data.c rtmp_tkip.o .wpa.o.cmd
eeprom.c Module.symvers rtmp_data.o .rtmp_tkip.o.cmd
eeprom.o oid.h .rtmp_data.o.cmd rtmp_type.h
.eeprom.o.cmd README rtmp_def.h rtmp_wep.c
ifcfg-ra0 ReleaseNote rtmp.h rtmp_wep.o
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # less /home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module/rtmp_data.c [just to see results below for lines mentioned in the warnings]
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # cp rt61sta.dat /etc/Wireless/RT61STA/rt61sta.dat
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # ls /etc/Wireless/RT61STA/rt61sta.dat
rt61sta.dat
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # /sbin/insmod rt61.ko
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # load
bash: load: command not found
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # $load
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # $/sbin/insmod rt61.ko
bash: $/sbin/insmod: No such file or directory
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module # /sbin/insmod rt61.ko
insmod: error inserting 'rt61.ko': -1 File exists
homecomputer:/home/[my name]/builds/2007_1003_RT61_Linux_STA_v1.1.1.0/Module #



Now, as you can see, I misunderstood the directions and I didn't do the "$load" until after I had issued the "/sbin/insmod rt61.ko"-order (Why is it "$load" needs the dollar sign to work, but "$/sbin/insmod" doesn't work with it???) Anyway, does the error message "insmod: error inserting 'rt61.ko': -1 File exists" mean there will be trouble or just that the order, once issued, can't be issued again, but is nevertheless valid? If there's trouble to be expected from this, is there some way for me to undo the damage?

I checked the DOS-version before, and the Unix-version after, of the file rt61sta.dat, as the build-instructions mandate ("# !!!check if it is a binary file before loading !!!"). There is binary code visible in the DOS-version, but none visible in the Unix-version. I assume this is a desirable result of the conversion. Otherwise, I don't know what to make of this little aside from the coders. Comments welcome.

The last part of the load-instructions: "# $/sbin/ifconfig ra0 inet YOUR_IP up"; I don't understand.

Is "YOUR_IP" supposed to be generic for the wireless device's IP address?

And the configuration that follows this on the so-called WPA_Supplicant, is this optional and can it be done at a separate time? It looks really, really complicated. Much too much so for a nontechie. The instruction keep talking about editing the separate files in the directory in various ways or 3.) "updat[ing] to the file "[WHATEVER]" we provide". And there's quite a number of them. What's a nontechie, noncoder to do here?

Any informed commentary on these matters will help me get back my home Internet---this is being posted of necessity from the campus computer system---and will be greatly appreciated.

Thanks.
 
Old 10-15-2007, 05:25 PM   #5
Rex Bachmann
LQ Newbie
 
Registered: Oct 2007
Distribution: SuSE Leap 42.1
Posts: 5

Rep: Reputation: 0
Linksys WMP54G v4.1 under XP Professional

Just an update. I could still use having those questions I posed addressed by some knowledgeable person, because, so far as I can tell, SuSE 10.2 isn't even seeing the Linksys WMP54-g v4.1 PCI adapter.

I've issued the command dmesg several times. If the Linksys adapter is being detected, it is totally unobvious in the output of that command. (The output reports on, e.g., PCI: IRQ 5 and 11, but what it says I can't comprehend.)

Issuing the "/sbin/ifconfig ra0 inet [YOUR_IP] up" produces only the message that "no such device found". The system's apparently not seeing the ra0(Ralink)-chip.

I've also tried using YAST to graphically install the driver, again to no effect, as far as I can tell.

To check that this wasn't a hardware problem, I removed the adapter from the computer, installed the accompanying Windows drivers into the XP Professional partition (which I hadn't visited more than twice in the past year) and re´nserted the adapter into the PCI slot and---voilÓ---the device worked almost effortlessly. (And I found out what the service provider's name is from the Windows set-up screen, but how to find its numeric IP address for issuing the Linux command? It's given there only by company name.)

Of course, Windows not long after that went wonky on me---doesn't it always?---but, at the very least, I found out the problems I'm having installing under Linux are not with the hardware.

Any suggestions on the Linux software front?


Thanks for any help.
 
Old 10-30-2007, 06:31 PM   #6
Rex Bachmann
LQ Newbie
 
Registered: Oct 2007
Distribution: SuSE Leap 42.1
Posts: 5

Rep: Reputation: 0
Wireless or "bust"!



Well, here it is a couple of weeks later and through hit-and-miss loading of modules and drivers it seems that I've finally, somehow---and I've made lots of mistakes along the way---gotten the Linksys WMP 54g v.4.1 installed and recognized by the system.

The information on the device set-up in KNetworkmanager dialog-box (before I try to connect to the network) reads:


RaLink RT2561/rt61 802.11g PCI
Device raX [note: every time I edit the file the number reported by KNetworkManager goes up; I'm up to ra6 now]
IP: 0.0.0.0
Hardware Address: wlan-id-00:1c:10:6a:e8:e2
subnetmask: 0.0.0.0
broadcast: 0.0.0.0
Network: Rowan House
Access Point: 00:17:3F:57:09:32
Bandwidth: unknown
signal strength: [various from -1 to 57 to 76]
frequency: 0.000 GHz
encrypted: yes
Encryption Protocol: WEP [the service doesn't seem to offer WPA, and in any case the Linksys Installation Guide says that "Non-Linksys wireless products require a WEP key to be entered."]
Device active: no
Network active: no


When I try connecting, a second dialog box opens that says at the top "configuring device" and at the bottom "activating: stage 28%", then, after about 30 to 45 seconds, it dies and returns me to the KNetworkmanager dialog box for (re-)entering the WPA Passphrase, and the process begins all over again. ("Hell is repetition.")

I have read of issues such as SuSE 10.2's (supposedly) not being able to connect wirelessly except under "root", but, in setting up the interface the first time, it tells you in the instructions: "Normally only the system administrator is allowed to activate and deńctivate a network interface. With User Controlled, an ordinary user may control the interface with KInternet."

Needless to say, I set the system for "user-controlled".

If there is a separate "KInternet" application or interface that I'm supposed to use, I haven't been able to find it (and I'm pretty sure I loaded all of the KDE development packages).

As I said, I've used everything and the kitchen sink to get as far as I have. Specifically, I've attempted to configure the driver with both CLI (through vi(m)) and, where that seemed not to work, with the KNetworkmanager. Is the Networkmanager perhaps trying to do something at odds with CLI configuration I've already done? (Curiously, though YAST recognizes the device, I have never yet been able to configure the relevant files using iwconfig as the README to the driver tells me I should be able to do.)

I provide the contents of the two crucial files for the device. Would someone knowledgeable please help me diagnose the problem, if it lies there?
_______________________________________________


contents of /etc/sysconfig/network/ifcfg-wlan-id-00:1c:10:6a:e8:e2 (after latest editing)

BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.2.1'
MTU='54Mbp'
NAME='Linksys RT2561/RT61 802.11g PCI'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
UNIQUE='ybFX.9rjj_7emlyB'
USERCONTROL='yes'
WIRELESS_AP=''
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='54'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY='[10-digit number withheld for security reasons]'
WIRELESS_CLIENT_KEY_PASSWORD='[8-place alphabetic password withheld for security reasons]'
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID=''
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0='h:[same 10-digit number as in the WIRELESS_CLIENT_KEY above]'
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='64'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='yes'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK=''
_nm_name='bus-pci-0000:00:08.0'
_________________________________________________
contents of /etc/Wireless/RT61STA/rt61sta.dat/rt61sta.dat:

[Default]
CountryRegion=0
CountryRegionABand=7
WirelessMode=0
SSID=AP350 [Note: supplied by the system, not by me]
NetworkType=Infra
Channel=0
AuthMode=OPEN
EncrypType=NONE
DefaultKeyID=1
Key1Type=0
Key1Str=[10-digit number withheld for security reasons]
Key2Type=0
Key2Str=
Key3Type=0
Key3Str=
Key4Type=0
Key4Str=
WPAPSK=abcdefghijklmnopqrstuvwxyz
TxBurst=0
PktAggregate=0
WmmCapable=0
APSDCapable=0
APSDAC=0;0;0;0
BGProtection=0
IEEE80211H=0
TxRate=0
RTSThreshold=2347
FragThreshold=2346
RoamThreshold=75
PSMode=CAM
TxPreamble=0
FastRoaming=0

_________________________________________________

So, computer docs, what's ailing me here?

Bad configuration?

Bad IP address? Does it need the "MAC" address instead the generic Belkin address (192.168.2.1)? (Actually, I thought that, with DHCP enabled, the system would find the correct address if the device detected the router's signal, but since that didn't seem to work, I added it to the file.)
Do I have the "key"---which nobody knew what was---that I was given entered into the wrong slot(s)? I put the 10-digit number I was given into the WIRELESS_CLIENT_KEY-slot, 'cause I didn't know what else to do with it and Linksys's installation guide says there has to be something. (Note the system is classifying this hexadecimal (h).)
Did I enter it in the wrong slot?

Another possible issue: Is the ethernet card running interference? (Since it's not connected to anything at present, I would doubt it, but . . . .)

Believe me, I've tried Linksys online (from campus computers) and Belkin router people on the telephone (from INDIA, no less) and they've all been clueless and useless.

The system now seems to read the presence of the device and the device seems to be working, yet I'm not getting anything. (Browsers still can't find the servers.) At this point I think I need just a little help from the "experts" to get me over the hump and get this thing working so I can have home wireless Internet access.

Any comments/suggestions on the situation or the set-up???
 
Old 10-31-2007, 04:45 PM   #7
pliqui
Member
 
Registered: Feb 2007
Location: Caracas, Venezuela
Distribution: Debian x64
Posts: 156

Original Poster
Rep: Reputation: 17
i just gave up... ndiswrapper FTW

Well, few days l8er after this post i tried ndiswrapper utility and worked just fine. My idea was not to use some emulated drivers, i wanted to use some native ones, but right now i just uninstall ndiswrapper and I'm not using the wireless card. Bought a very long cable and plug into the router i was having issues with the wireless, every time i tried to assign a default ip 192.168.1.101 for example didn't work at all, couldn't connect to internet or the other machine.

So for now, no wireless for me and still kinda new to linux, even tho i'm using it since the past 6 months, every day i'm learning something new and my expertise is still low.

Hopefully someone will help you, i will check it out and try to see what i can found in forums or web pages.

Gl
 
Old 11-01-2007, 07:29 AM   #8
tommcd
Senior Member
 
Registered: Jun 2006
Location: Philadelphia PA USA
Distribution: Lubuntu, Slackware
Posts: 2,230

Rep: Reputation: 292Reputation: 292Reputation: 292
Quote:
Originally Posted by Rex Bachmann View Post
So, I'm stuck in a new temporary place with only wireless Internet connectivity

I bought a Linksys WMP54G PCI-Adapter v4.1 for my openSuSE 10.2 system (Linux kernel 2.6.18.2-34)and am trying to get to work. I hoep the RT61 driver is the correct one.

I've followed the build instructions (to the extent they are explicit, and to the extent they are not, I have taken my best guess).
Rex,
If you need the rt61 driver try the one from serialmonkey instead of the one from Ralink:
http://rt2x00.serialmonkey.com/wiki/index.php/Downloads
The serialmonkey drivers are still being developed and include bug fixes not present in the drivers from Ralink. The rt61 driver from serialmonkey works well in ubuntu, slackware, zenwalk and frugalware for me. First try the CVS hourly tarball, if that don't work then try the last beta release of the driver. I don't know much about Suse, but listen to this podcast about Suse. The guy describes in great detail how he got the rt61 driver working. Good luck!
http://thelip.net/?p=66

Last edited by tommcd; 11-01-2007 at 07:38 AM.
 
Old 11-04-2007, 02:31 PM   #9
Rex Bachmann
LQ Newbie
 
Registered: Oct 2007
Distribution: SuSE Leap 42.1
Posts: 5

Rep: Reputation: 0
"Uncle!"

tommcd wrote:

Quote:
If you need the rt61 driver try the one from serialmonkey instead of the one from Ralink:
http://rt2x00.serialmonkey.com/wiki/index.php/Downloads
The serialmonkey drivers are still being developed and include bug fixes not present in the drivers from Ralink.
Thanks for the advice.

Hate to tell you this, but I already have tried it/them. That's what I was referring to when I said I had been "through hit-and-miss loading of modules and drivers" and "I've used everything and the kitchen sink to get as far as I have." I honestly don't know which drivers the system is responding to, although it would seem that it's the RaLink one(s). I read another how-to on getting those "serial-monkey" drivers working on any system and the guy gave contradictory instructions to ones I'd already followed. (He said, never use the "make install"-command with these drivers. Too late! Somebody else on the Internet I'd already read seemed to say different. Again, that's what partly what I meant by "I've made lot's of mistakes".)

At this point my kernel may be so mucked up none of them will work correctly. Who knows? So, although I hadn't planned to "upgrade" to open SuSE 10.3, it's supposed to have the relevant modules included in the latest kernel version, so I'll probably just get that and see whether it will work. If not, then I'll try loading the latest "serial-monkey" stuff to the new SuSE version and see where that leads.

Lastly, it should be noted that I started out my original inquiries on this wireless business on the SuSE (wireless-Internet) forums, to no good effect. That's why I came here.

Frankly, I'm exhausted from this whole depressing experience.

But, thanks, anyway.
 
Old 11-06-2007, 09:11 AM   #10
pliqui
Member
 
Registered: Feb 2007
Location: Caracas, Venezuela
Distribution: Debian x64
Posts: 156

Original Poster
Rep: Reputation: 17
Hey rex, why don't you try to use ndiswrapper http://ndiswrapper.sourceforge.net/joomla/ worked very good with my wireless, i even use ranlinktech drivers and not linksys http://www.ralinktech.com.tw/data/dr...7_0.1.0.29.exe

its very easy to setup and work very good, i was kinda stubborn because i didn't want to use emulated drivers just native, but that didn't happened, so, try this and let me know

Pliqui
 
Old 01-19-2008, 05:30 PM   #11
Adam Moore
LQ Newbie
 
Registered: Jan 2008
Location: San Francisco, CA
Distribution: openSuSE 10.2
Posts: 4

Rep: Reputation: 0
I have been trying to get my WMP54G v4.1 Linksys Wireless-G working on openSuSE 10.2 and lots of other distros. I am so fed up with Linux. It has seemed for the better part of a decade that I always have some critical hardware that is not recognized by Linux. This particular problem has me so angry I'm spitting and breaking things. Why God, why doesn't anywhere on the internet have a solution for this problem?!!! Can someone just tell me if I should go out and buy another card? Because I'm about ready to declare Jihad on Linksys and Linux.
 
Old 01-19-2008, 08:46 PM   #12
XavierP
Moderator
 
Registered: Nov 2002
Location: Kent, England
Distribution: Debian Testing
Posts: 19,192
Blog Entries: 4

Rep: Reputation: 475Reputation: 475Reputation: 475Reputation: 475Reputation: 475
Adam have you tried the solutions posted above? Unfortunately, many hardware manufacturers do not release Linux drivers, all I can suggest is that you politely contact them to explain that you are a customer and would like to have your card working.

If the above suggestions don't work, you could look into DriverLoader.

Welcome to LQ
 
Old 01-20-2008, 01:11 PM   #13
Adam Moore
LQ Newbie
 
Registered: Jan 2008
Location: San Francisco, CA
Distribution: openSuSE 10.2
Posts: 4

Rep: Reputation: 0
Angry Tried everything

This sucks. The learning curve for a working Linux system is a PhD in Computer Science. If this is a common problem (it is, I've checked), why isn't there an automated (or simple) way to install drivers? I'm sorry, but command line directions are horribly uninformative and beyond the scope of a non-tech user to modify for their specific issue. I don't have a problem with understanding the more technical side, but why when it's obviously not necessary? Either there is one #%$* solution for one specific piece of hardware (Linksys WMP54G v4.1), or there is not. I don't care if it has the same chipset as another brand, if the instructions don't explicitly state compatibility with my PARTICULAR model, I'm not going to waste my time trying their solution. Why isn't there ONE FREAKING SOLUTION that you can Google for getting the Linksys WMP54G v4.1 working under Linux? Why? Please explain why it works for some people GIVEN THE EXACT SAME VARIABLES?!!! I find the "solutions" are poorly explained or are missing assumed knowledge between steps. Is this a distro specific problem? Will upgrading fix it? Why aren't more people bitching about this? Why me?

I'm using a clean install of openSuSE 10.2 on a remarkably vanilla system.
 
Old 01-20-2008, 09:34 PM   #14
tommcd
Senior Member
 
Registered: Jun 2006
Location: Philadelphia PA USA
Distribution: Lubuntu, Slackware
Posts: 2,230

Rep: Reputation: 292Reputation: 292Reputation: 292
Quote:
Originally Posted by Adam Moore View Post
I have been trying to get my WMP54G v4.1 Linksys Wireless-G working on openSuSE 10.2 and lots of other distros. I am so fed up with Linux. It has seemed for the better part of a decade that I always have some critical hardware that is not recognized by Linux. This particular problem has me so angry I'm spitting and breaking things. Why God, why doesn't anywhere on the internet have a solution for this problem?!!! Can someone just tell me if I should go out and buy another card? Because I'm about ready to declare Jihad on Linksys and Linux.
Adam, if your WMP54G v4.1 card uses one of the Ralink drivers perhaps you could try Ubuntu instead of Suse. On Ubuntu Gutsy my Ralink rt61 based Belkin wireless card worked out of the box on Gutsy. I did not have to install any additional drivers.
 
Old 01-21-2008, 10:23 AM   #15
Adam Moore
LQ Newbie
 
Registered: Jan 2008
Location: San Francisco, CA
Distribution: openSuSE 10.2
Posts: 4

Rep: Reputation: 0
I've tried Ubuntu and it's worse by a wide margin. Believe it or not, I'm switching to openSUSE 11.0-a1 where I can use the driver natively, and can hassle the NVIDIA and Kernel developers with direct and relevant feedback. I'm not afraid of getting my hands dirty and writing a custom driver, it's just the time overhead is really annoying when I feel I have better things to do (like paid work). And the simple solution is buy a better wireless card, which I am also doing after a strongly worded letter to Linksys about their chipset decisions. Thanks for the help, but the answer to every Linux problem (for me) is still buy additional, compatible hardware. I can't think of a single Windows OS that required me to buy as much peripheral hardware as every single Linux OS I've ever had the misfortune to use. We're talking about tools here, and sometimes Linux is the only right tool for the job. I just hate the time-suck ramp-up that is unavoidable inherent with a Linux system install. Boo! *hiss* I mean really, we're talking about trouble with a Linksys product. I thought the Linux community smoothed that wrinkle years ago and I end up with the one device where everyone shrugs and says "Oh well".
 
  


Reply

Tags
linksys, networking, rt2500, wireless, wmp54g


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
linksys wmp54g wireless card + ubuntu 7.04 neocorps Linux - Newbie 7 01-14-2008 02:47 AM
Linksys WMP54G v4.1 Wireless PCI Card teadrinker Slackware 2 11-18-2006 05:30 PM
linksys wmp54g wireless card for suse 9 gsr_kashyap Linux - Wireless Networking 2 10-19-2006 02:16 AM
linksys wireless router & linksys wmp54g wireless card rude_reality Linux - Wireless Networking 13 05-25-2006 06:01 AM
Linksys Wireless G PCI card (WMP54G I think) OneSeventeen Linux - Wireless Networking 2 04-09-2005 08:09 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 04:53 PM.

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