LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 07-11-2008, 08:19 AM   #1
pellicle
Member
 
Registered: Jul 2008
Location: Finland
Distribution: RHEL4
Posts: 137

Rep: Reputation: 15
wireless can connect to access point but not getting IP (and then other issues)


Hi

I have just come back to place more information onto a post I made about my wireless lan card problem and found that my thread is not here.

I have no idea if a moderator deleted it or what however ... nothing appears very frustrating.

Anyway, I'll try to post this again.

For the past week I have been trying to get any NIC to work in my machine which I am trying to set up. It seems that I've finally been able (although I don't know how) to get the NIC (a RT-2651T card) recognised by the system.

After making and make installing nothing comes back with a modprobe
Code:
[root@localhost Module]# modprobe rt61
however when I did the following (as outlined in the serialmonkey documentation)

Code:
[root@localhost Module]# ifconfig wlan0 up
[root@localhost Module]# iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:18:F8:7B:4A:87
                    ESSID:"karistonkaiku"
                    Mode:Managed
                    Channel:11
                    Encryption key:off
                    Bit Rate:132Mb/s
                    Quality:43/100  Signal level:-80 dBm  Noise level:-256 dBm
          Cell 02 - Address: 00:13:64:27:55:0E
                    ESSID:"anitan"
                    Mode:Managed
                    Channel:2
                    Encryption key:off
                    Bit Rate:6Mb/s
                    Quality:0/100  Signal level:-62 dBm  Noise level:-256 dBm

Code:
[root@localhost ~]# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1467 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1467 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1671218 (1.5 MiB)  TX bytes:1671218 (1.5 MiB)

wlan0     Link encap:Ethernet  HWaddr 00:1A:EE:00:DA:6E
          inet6 addr: fe80::21a:eeff:fe00:da6e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9304 errors:0 dropped:0 overruns:0 frame:0
          TX packets:237 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:676645 (660.7 KiB)  TX bytes:4568 (4.4 KiB)
          Interrupt:201

[root@localhost ~]# iwconfig
lo        no wireless extensions.

sit0      no wireless extensions.

wlan0     RT61 Wireless  ESSID:"anitan"
          Mode:Managed  Frequency:2.417GHz  Access Point: 00:13:64:27:55:0E
          Bit Rate=54Mb/s
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality=84/100  Signal level:-55 dBm  Noise level:-79 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

[root@localhost ~]#
it would seem that I can now get my wireless card seen by my redhat system, however there remain some problems for it. After rebooting, I can't see the card anymore, and

issuing the commands again (ifconfig wlan up ... ) gives:
Code:
wlan0: unknown interface: no such device
Using the GUI tools, I see the following.

http://farm4.static.flickr.com/3022/...73822d67_o.jpg

I hope this page makes it this time
 
Old 07-11-2008, 08:39 AM   #2
pellicle
Member
 
Registered: Jul 2008
Location: Finland
Distribution: RHEL4
Posts: 137

Original Poster
Rep: Reputation: 15
so, now the problem is sort of two fold, I thought that I could get as far as I did, but now I can't anymore.

So, digging around I thought I'd start with examining the output of dmesg, where I see:

Code:
rt61: Could not load firmware! (is firmware file installed?)
which is not looking good.

so now I feel like I'm back to square one
 
Old 07-13-2008, 10:44 AM   #3
xadrith
Member
 
Registered: Oct 2007
Distribution: Slack 12.1
Posts: 43

Rep: Reputation: 15
I found some firmware drivers for the Ralink 61 here:

http://www.opendrivers.com/driver/23...-download.html

Have you tried installing the firmware yet? If so, what kind of output does dmesg give now?

x.D
 
Old 07-13-2008, 03:28 PM   #4
farslayer
Guru
 
Registered: Oct 2005
Location: Willoughby, Ohio
Distribution: linuxdebian
Posts: 7,230
Blog Entries: 5

Rep: Reputation: 185Reputation: 185
Firmware is on ralinks website... The firmware files are actually IN with the bzipped driver source.. .

http://www.ralinktech.com/ralink/Hom...ort/Linux.html

The README.txt file included with the driver source explains what to do with the firmware files...

Code:
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

4.1> $make install


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
 
Old 07-15-2008, 07:37 AM   #5
pellicle
Member
 
Registered: Jul 2008
Location: Finland
Distribution: RHEL4
Posts: 137

Original Poster
Rep: Reputation: 15
Hi

to the best of my knowledge I did all of that and the best that I got was that it locked up my box. I've since been trying another NIC but since that seems to be hapless I may just see if I can waste more time on the wireless NIC again.

I'll redo all that I did before to confirm that after it connects to the router it just locks up the entire box - solid!
 
Old 07-15-2008, 07:44 AM   #6
pellicle
Member
 
Registered: Jul 2008
Location: Finland
Distribution: RHEL4
Posts: 137

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by farslayer View Post


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

[/code]
also I do not have a Wireless directory in /etc

only ones under:

/usr/src/kernels/`uname -r`/drivers/net/wireless and
/lib/modules/`uname -r`/kernel/drivers/net/wireless

:-)
 
Old 07-15-2008, 08:28 PM   #7
farslayer
Guru
 
Registered: Oct 2005
Location: Willoughby, Ohio
Distribution: linuxdebian
Posts: 7,230
Blog Entries: 5

Rep: Reputation: 185Reputation: 185
Well if /etc/Wireles is where the Driver is coded to look for the firmware I would guess you should create those directories and copy the firmware to them as directed.
 
Old 07-15-2008, 11:52 PM   #8
pellicle
Member
 
Registered: Jul 2008
Location: Finland
Distribution: RHEL4
Posts: 137

Original Poster
Rep: Reputation: 15
Hi

Quote:
Originally Posted by farslayer View Post
Well if /etc/Wireles is where the Driver is coded to look for the firmware I would guess you should create those directories and copy the firmware to them as directed.
well, this is where I find there are just too many assumptions. You see, in the 20 years I've been programming one thing which gets drummed into one is "do not hard coded in directory locations".

So, for all I know the software is getting that location (which you mentioned) from some configuration file, from some built location. To me, just making it (mkdir /etc/Wireles) would be likely as not to fail. Further, if its needed why then does the installer (make file) make it?

This is where I say that the underlying weakness is in the entire system. Its not consistent (from distribution to distribution) in the toolset used, the locations of files, and the operation of installs.

I guess also (from the lack of definitive replies to my questions) that the sad truth is that noone else out there knows either and we're all guessing and doing detective work.

Last edited by pellicle; 07-15-2008 at 11:54 PM. Reason: added point
 
Old 07-16-2008, 01:48 AM   #9
pellicle
Member
 
Registered: Jul 2008
Location: Finland
Distribution: RHEL4
Posts: 137

Original Poster
Rep: Reputation: 15
for others who may struggle down this path, I'll continue to post on this thread till I give up.

this documents my path with the Ralink software mentioned above by Farslayer

the Makefile is flawed ... even though they provide both a 2.4 and 2.6 kernel, there are issues. Below is the output:

Code:
make -C /lib/modules/2.6.9-22.ELsmp/build SUBDIRS=/tmp/RT61_Linux_STA_v1.1.2.1/Module modules
make[1]: Entering directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.o
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c: In function `rt61_get_drvinfo':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c:78: warning: unused variable `pAd'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c: In function `rt61_get_regs_len':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c:97: warning: control reaches end of non-void function
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c: In function `rt61_get_regs':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c:103: warning: unused variable `pAd'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c:104: warning: unused variable `counter'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c: In function `rt61_ethtool_get_link':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c:120: warning: unused variable `pAd'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c:130: warning: control reaches end of non-void function
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c: In function `rt61_get_eeprom_len':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c:139: warning: control reaches end of non-void function
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c: In function `rt61_get_eeprom':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c:145: warning: unused variable `pAd'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c:146: warning: unused variable `counter'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c:159: warning: control reaches end of non-void function
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c: At top level:
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_main.c:169: warning: initialization from incompatible pointer type
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/mlme.o
/tmp/RT61_Linux_STA_v1.1.2.1/Module/mlme.c: In function `STAMlmePeriodicExec':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/mlme.c:740: warning: unused variable `RxSignal'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/mlme.c: In function `MsgTypeSubst':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/mlme.c:3439: warning: unused variable `Return'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/mlme.c: In function `AsicSendCommandToMcu':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/mlme.c:5327: warning: 'i' might be used uninitialized in this function
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/connect.o
/tmp/RT61_Linux_STA_v1.1.2.1/Module/connect.c: In function `LinkDown':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/connect.c:1095: warning: unused variable `CurTxRxCsr4'
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/sync.o
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/assoc.o
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/auth.o
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/auth_rsp.o
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.o
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.c: In function `REPORT_ETHERNET_FRAME_TO_LLC':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.c:79: warning: unused variable `pRxPkt'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.c: In function `REPORT_ETHERNET_FRAME_TO_LLC_WITH_NON_COPY':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.c:116: warning: unused variable `pRxPkt'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.c: In function `RTMPHandleRxDoneInterrupt':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.c:656: warning: ISO C90 forbids mixed declarations and code
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.c:688: warning: ISO C90 forbids mixed declarations and code
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.c: In function `RTMPHardTransmit':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.c:2136: warning: unused variable `PacketInfo'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.c:2136: warning: unused variable `NextPacketInfo'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_data.c:2137: warning: unused variable `pNextPacketBufVA'
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_init.o
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_init.c: In function `RTMPReadParametersFromFile':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_init.c:3947: warning: unused variable `i'
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/sanity.o
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_wep.o
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.o
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c:708: warning: return type defaults to `int'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c: In function `rt_ioctl_giwscan':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c:931: warning: assignment from incompatible pointer type
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c:933: warning: assignment from incompatible pointer type
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c:939: warning: assignment from incompatible pointer type
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c:885: warning: unused variable `i'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c:875: warning: unused variable `essid'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c:876: warning: unused variable `varie_cnt'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c:877: warning: unused variable `pTmp'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c:712: warning: unused variable `current_val'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c: In function `rt_ioctl_siwessid':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c:1287: warning: unused variable `i'
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c: In function `rt_ioctl_siwencode':
/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_info.c:1749: warning: unused variable `keyBuf'
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/eeprom.o
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_tkip.o
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/wpa.o
/tmp/RT61_Linux_STA_v1.1.2.1/Module/wpa.c:2494:2: warning: no newline at end of file
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/md5.o
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_task.o
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_wext.o
In file included from /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_wext.h:44,
                 from /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_wext.c:41:
include/net/iw_handler.h:294: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:294: warning: its scope is only this definition or declaration, which is probably not what you want
include/net/iw_handler.h:380: error: `ETH_ALEN' undeclared here (not in a function)
include/net/iw_handler.h:412: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:421: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:426: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:431: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:436: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:440: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h: In function `iwe_stream_add_event':
include/net/iw_handler.h:460: warning: implicit declaration of function `memcpy'
make[2]: *** [/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_wext.o] Error 1
make[1]: *** [_module_/tmp/RT61_Linux_STA_v1.1.2.1/Module] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
make: *** [all] Error 2
 
Old 07-16-2008, 01:54 AM   #10
pellicle
Member
 
Registered: Jul 2008
Location: Finland
Distribution: RHEL4
Posts: 137

Original Poster
Rep: Reputation: 15
if you ignore the warnings (inadvisable but doable) there are still 2 errors. However if one isn't a programmer, and blithely trudges on the result of the make install is:

Code:
make -C /lib/modules/2.6.9-22.ELsmp/build SUBDIRS=/tmp/RT61_Linux_STA_v1.1.2.1/Module modules
make[1]: Entering directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
  CC [M]  /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_wext.o
In file included from /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_wext.h:44,
                 from /tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_wext.c:41:
include/net/iw_handler.h:294: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:294: warning: its scope is only this definition or declaration, which is probably not what you want
include/net/iw_handler.h:380: error: `ETH_ALEN' undeclared here (not in a function)
include/net/iw_handler.h:412: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:421: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:426: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:431: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:436: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h:440: warning: "struct net_device" declared inside parameter list
include/net/iw_handler.h: In function `iwe_stream_add_event':
include/net/iw_handler.h:460: warning: implicit declaration of function `memcpy'
make[2]: *** [/tmp/RT61_Linux_STA_v1.1.2.1/Module/rtmp_wext.o] Error 1
make[1]: *** [_module_/tmp/RT61_Linux_STA_v1.1.2.1/Module] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
make: *** [all] Error 2
also, worth noting is that I can't find anything which then puts the rt61.ko file into the correct location. As near as I understand this, it should be something like /lib/modules/`uname -r`/kernel drivers/net (note the backticks on the uname -r)

also, the steps of moving the binary firmware files to the location seems to be commented out in the makefile

Code:
#	auto copy *.bin to /etc/Wireless/RT61STA
#	mkdir /etc/Wireless ;
#	mkdir /etc/Wireless/RT61STA ;
#	cp $(shell pwd)/*.bin /etc/Wireless/RT61STA ;
#	cp $(shell pwd)/*.dat /etc/Wireless/RT61STA ;

#	Copy file  on Mandriva 2007.1	
#	cp $(shell pwd)/*.bin /lib/firmware/ ;
perhaps because of the errors there is no .ko file produced

Last edited by pellicle; 07-16-2008 at 01:57 AM. Reason: whopsie
 
Old 07-16-2008, 07:56 AM   #11
pellicle
Member
 
Registered: Jul 2008
Location: Finland
Distribution: RHEL4
Posts: 137

Original Poster
Rep: Reputation: 15
now serial monkey (with a fresh install)

I found that there was too much pollution of files from the make of the Realtek driver, so I thought (since I have nothing invested in this system) I'd wipe it clean again and start afresh with the serialmonkey version of the drivers. this is what I found so far:

--> start of file, lets do the make

Code:
[root@localhost Module]# make
make[1]: Entering directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
  CC [M]  /tmp/rt61-cvs-2008071005/Module/rtmp_main.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/mlme.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/connect.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/sync.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/assoc.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/auth.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/auth_rsp.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/rtmp_data.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/rtmp_init.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/sanity.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/rtmp_wep.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/wpa.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/md5.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/rtmp_tkip.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/rtmp_info.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/eeprom.o
  CC [M]  /tmp/rt61-cvs-2008071005/Module/rt2x00debug.o
  LD [M]  /tmp/rt61-cvs-2008071005/Module/rt61.o
  Building modules, stage 2.
  MODPOST
  CC      /tmp/rt61-cvs-2008071005/Module/rt61.mod.o
  LD [M]  /tmp/rt61-cvs-2008071005/Module/rt61.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
!!! WARNING: Module file much too big (>1MB)
!!! Check your kernel settings or use 'strip'
*** Module rt61.ko built successfully
ok ... a warning, things too big ... what's next

Code:
[root@localhost Module]# make install
*** Install module in /lib/modules/2.6.9-22.ELsmp/extra ...
make[1]: Entering directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
  INSTALL /tmp/rt61-cvs-2008071005/Module/rt61.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.9-22.EL-smp-i686'
/sbin/depmod -a
*** Update /etc/modprobe.d/ralink alias for wlan*
*** Config dir /etc/modprobe.d not found
*** Install firmware in /lib/firmware ...
*** Check old config ...
couple of warnings, nothing too scary ... now, lets confirm what's now been made one at a time starting from the first line

--> *** Update /etc/modprobe.d/ralink alias for wlan*

well that's a fluff up! As you can see below the code then basically adds this line into the modprobe.d/ralink file

and why then is there this step in the README file (step 4)

Code:
          # modprobe rt61 [debug=<mask>]
is it because they knew that the make was wrong?? I need to understand what needs to be done, as I need to ensure that the preconditions are actually right before executing this.

as I understand it (please someone jump in if I'm wrong here) the entry in /etc/modprobe.conf is perhaps linked in some way to the filename (such as by name without the .ko extention) to the files in
/lib/modules/`uname -r`/kernel/drivers/net

dunno ... way too many "dunno's" in this.

Lets also look at the existing module dependencies (depmod). My manpage on modprobe says that I need to check dmesg to see what the results are as some functions are now part of the kernel ... great!

So if anyone out there reading this can fill me in on what modprobe rt61 does, and what needs to be where before its done I'd be very grateful.



Code:
IF_NAME :=     wlan*
 MODULE_NAME := rt61
 MODULE_OBJECT := $(MODULE_NAME).ko
 MODULE_CONF := /etc/modprobe.d/ralink
...
	if ! grep -q '$(IF_NAME)' $(MODULE_CONF) ; then \
		echo "alias $(IF_NAME) $(MODULE_NAME)" >> $(MODULE_CONF) ; \
which is wrong for RHEL the location is /etc/modprobe.conf so such an entry needs to be put into /etc/modprobe.conf

as its only an alias, so perhaps this can be done by the gui tools?

next, this line stands out alone in the makefile:

Code:
	/sbin/depmod -a
what's it supposed to do?

now, what about the Firmware? Bewdy, the firmware's there :-)
Code:
[root@localhost Module]# ls /lib/firmware
BCM2033-FW.bin  BCM-LEGAL.txt  rt2561s.bin
BCM2033-MD.hex  rt2561.bin     rt2661.bin
NOTE: some important changes in the structure have resulted in some new bits which are confusing, for example there were files put into /etc/Wireless/RT61STA however the code now puts stuff into /lib/firmware. NB:

Code:
FIRMWARES :=   rt2*.bin
FIRM_DIR :=    /lib/firmware
...
	@echo "*** Install firmware in $(FIRM_DIR) ..."; \
	if ! [ -d $(FIRM_DIR) ]; then \
		mkdir $(FIRM_DIR); \
	fi; \
	cp -f $(FIRMWARES) $(FIRM_DIR)
the make file then goes on to check if the old DEPRECATED stuff is there...

Code:
CONFIG_DIR :=  /etc/Wireless/RT61STA
OLD_IF_NAME := ra0
CONFIG_FILE := rt61sta.dat
...
	if [ -d $(CONFIG_DIR) ]; then \
		echo "!!!"; \
		echo "!!! WARNING: DEPRECATED CONFIG FOUND !"; \
		echo "!!!"; \
		echo "!!! -> Update your config and remove $(CONFIG_DIR)"; \
		if [ -f $(CONFIG_DIR)/$(CONFIG_FILE) ]; then \
			echo "!!! -> $(CONFIG_FILE) file is deprecated:" \
					"use iwconfig/iwpriv instead"; \
and then tells you NOT to use the stuff in /etc/Wireless/RT61STA

I recall that I had a problem with my card not being recognized, so I've gone and got the latest pci.ids file with the one from pci-ids.ucw.cz and it now at least doesn't show that its an unknown card

BUT still don't work!

I'm so glad that Linux is so simple, if this was windows, it would have given me the option to "have disk" and install a driver for an unknown card.

Sheesh!

more as I get further into this
 
Old 07-16-2008, 08:19 AM   #12
pellicle
Member
 
Registered: Jul 2008
Location: Finland
Distribution: RHEL4
Posts: 137

Original Poster
Rep: Reputation: 15
some further digging has revealed:

there is a file called modules.dep (in /lib/modules/2.6.9-22ELsmp/)

if I grep for rt61 I get:

/lib/modules/2.6.9-22ELsmp/extra/rt61.ko

this file is the right size and time/date for the compile which I just did for the Serialmonkey driver set.

interestingly, when I do dmesg | grep rt61 I get the lines:

Code:
[root@localhost ~]# dmesg | grep -i rt61
rt61: 1.1.0 CVS 2008071005 http://rt2x00.serialmonkey.com
rt61: Could not load firmware! (is firmware file installed?)
rt61: 1.1.0 CVS 2008071005 http://rt2x00.serialmonkey.com
rt61: RT61: RfIcType= 3
even though its seemingly there:

Code:
[root@localhost ~]# ls /lib/firmware
BCM2033-FW.bin  BCM-LEGAL.txt  rt2561s.bin
BCM2033-MD.hex  rt2561.bin     rt2661.bin
the thot plickens
 
Old 07-16-2008, 07:53 PM   #13
farslayer
Guru
 
Registered: Oct 2005
Location: Willoughby, Ohio
Distribution: linuxdebian
Posts: 7,230
Blog Entries: 5

Rep: Reputation: 185Reputation: 185
If you are unhappy about having to use binary firmware to get a card working, then do what I do and purchase a Card that uses FREE Open Drivers that do not require firmware... problem solved..

I use ralink wireless cards, but of the variety that do not have firmware files to deal with.

You also have the option of using ndiswrapper with the firmware files to get the card working
 
Old 07-16-2008, 11:45 PM   #14
pellicle
Member
 
Registered: Jul 2008
Location: Finland
Distribution: RHEL4
Posts: 137

Original Poster
Rep: Reputation: 15
Farslayer

you may or may not recall that I am new to Linux, so what you say below does not seem helpful, in fact it just seems "smug".

Quote:
Originally Posted by farslayer View Post
If you are unhappy about having to use binary firmware to get a card working, then do what I do and purchase a Card that uses FREE Open Drivers that do not require firmware... problem solved..

I use ralink wireless cards, but of the variety that do not have firmware files to deal with.

You also have the option of using ndiswrapper with the firmware files to get the card working
  • I did not know that there was such a thing as a card which does or does not use firmware (so how could I be happy or unhappy with such, nor was I griping about "cards that use firmware")
  • If you know of ralink cards which would work well, rather than just smile and say such exist, how about offering help and telling me which cards you've had success with?
  • you may recall me saying I've had trouble with ndiswrapper too

the reason I've written extensively about my problem is to give those who may wish to offer help as good a background on my problem and what I've attempted to do as possible.
 
Old 07-18-2008, 12:12 AM   #15
farslayer
Guru
 
Registered: Oct 2005
Location: Willoughby, Ohio
Distribution: linuxdebian
Posts: 7,230
Blog Entries: 5

Rep: Reputation: 185Reputation: 185
take it however you like, it's still a valid suggestion.

I DID offer help in the way of a link to a web page, if you follow it there is information about supported wireless cards on that page. The list is provided by the Free software Foundation. It does mention some cards require firmware, but if you look, you can find one that works easily such as the ASUS WL-107G listed near the top of the page.

Quote:
The Free Software Foundation has purchased and successfully tested these Ralink devices with free systems:

* Asus WL-107G PCMCIA card
* Linksys WUSB54G USB 2.0 802.11g/b 54Mbps (11 Mbps with b)

.
.
.
.
Note that some other RT chipsets, including the RT2501, RT61 and RT2571W/RT2671, require firmware that is not released under a free software license. This makes these devices incompatible with a fully free system.
NO I don't recall reading the thread about ndiswrapper, Obviously I saw the thread since I posted in it to suggest updating your pci.ids file. Theres a lot of activity on this board so I may not recall everything you have tried to get your system working, when it's spread around multiple threads.

best of luck
 
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Fluxbuntu Broadcom Wireless sees access point doesn't connect simsie Linux - Wireless Networking 1 02-23-2008 07:24 AM
Issues Setting Up a Wireless Access Point on Ubuntu Server 7.4 with BCM4306 card sneakyjoe Linux - Wireless Networking 0 08-14-2007 12:45 AM
Unable to connect to private wireless access point jwholey Linux - Wireless Networking 1 04-24-2007 04:55 AM
Can no longer connect to wireless access point ebaker Linux - Wireless Networking 2 03-23-2005 09:23 PM
Wireless - can't connect to access point SilverGator Linux - Wireless Networking 5 06-21-2004 07:48 AM


All times are GMT -5. The time now is 08:12 AM.

Main Menu
 
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
identi.ca: @linuxquestions
Facebook: @linuxquestions
Open Source Consulting | Domain Registration