rt2x00.serialmonkey.com

Support forum for the rt2x00 project
It is currently Thu May 23, 2013 11:34 am

View unanswered posts | View active topics


Board index » Legacy Driver Support » rt2500 (pci) Legacy 802.11b/g Support

All times are UTC


Forum rules


Important: Read Project restructuring announcement regarding the pending removal of the legacy drivers from this project.



Forum locked This topic is locked, you cannot edit posts or make further replies.  Page 1 of 1
  [ 14 posts ] 
  Print view Previous topic | Next topic 
Author Message
raphy
PostPosted: Sat Feb 21, 2009 6:23 pm 
Offline

Joined: Sat Feb 21, 2009 6:20 pm
Posts: 10
Hello everyone,

Yesterday I was playing with my r2500 wifi card, and i tried to change the mac address. Unfortunately, after that, it didn't work anymore, even after a reboot.

Sometimes it will have its original address, somtimes its mac address will be 00:00:00:00:00:00.

There is no error messages at all, but when i tried to connect to my AP, iwconfig shows that i'm not associated, or associated with a link quality of 0/100.

I tried to reinstall the driver (serial monkey one), but without success.
Currently, I'm using this same card with ndiswrapper with the original mac address, so obviously the card is fine. The ralink driver works too (I mean, as badly as it usually does).

Does anyone ever had this problem? The ndiswrapper module has poor performance, I would be glad if I could use the serial monkey driver again?

Here is what the relevant part of the dmesg looks like: Quote:
Quote:
rt2500 0000:01:08.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16
rt2500: 1.1.0 CVS CVS Release http://rt2x00.serialmonkey.com
rt2500: Info - Mac address changed to: 00:21:00:81:93:c3.
rt2500 0000:01:08.0: PCI INT A disabled
rt2500 0000:01:08.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16
rt2500: 1.1.0 CVS CVS Release http://rt2x00.serialmonkey.com
udev: renamed network interface ra0 to ra3
device ra3 entered promiscuous mode
rt2500 0000:01:08.0: PCI INT A disabled


Any idea is welcome


Last edited by raphy on Sat Feb 21, 2009 7:09 pm, edited 1 time in total.

Top
 Profile  
 
IvD
PostPosted: Sat Feb 21, 2009 6:29 pm 
Offline
Site Admin

Joined: Sun Jun 05, 2005 1:01 pm
Posts: 5905
Location: Haarlem, The Netherlands
Please provide kernel version/driver version/distro/debug information etc etc.
If the _rt2x00_ driver is failing, provide the rt2x00 debug messages, if the _legacy_ drive is failing provide the legacy debug messages.

_________________
Regards,
Ivo van Doorn
Project Administrator
http://rt2x00.serialmonkey.com
Top
 Profile  
 
raphy
PostPosted: Sat Feb 21, 2009 6:40 pm 
Offline

Joined: Sat Feb 21, 2009 6:20 pm
Posts: 10
Ok, sorry.

So I'm using the kernel 2.6.28 (gentoo revisited), with the driver CVS 1.1.0 (but with a revision that worked fine until yesterday).

As for the debug information, that's the problem, there's is no error message. Modprobe rt2500 works fine, ifconfig ra0 up works fine, but if I tried to use the iwconfig command to connect to an ap, it doesn't, but there is still no error message at all.
Example:
Code:
fitz raph # iwconfig ra0 essid Neuf\ Wifi key off channel auto
fitz raph # iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

ra0       RT2500 Wireless  ESSID:""
          Mode:Managed  Frequency=2.412 GHz  Bit Rate=11 Mb/s   Tx-Power:-2 dBm
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality=0/100  Signal level:-120 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

fitz raph #


Also, the ifconfig used to give an output like this:
Code:
ra0       Link encap:UNSPEC  HWaddr 00-11-09-BF-AD-E8-6C-6F-00-00-00-00-00-00-00-00


Now, it's something like this:
Code:
ra0       Link encap:Ethernet  HWaddr 00:11:09:bf:ad:e8


Maybe that can give you an hint.
Top
 Profile  
 
IvD
PostPosted: Sat Feb 21, 2009 7:07 pm 
Offline
Site Admin

Joined: Sun Jun 05, 2005 1:01 pm
Posts: 5905
Location: Haarlem, The Netherlands
Ok, you are using the legacy driver and not rt2x00. I'll move this to the correct forum.

_________________
Regards,
Ivo van Doorn
Project Administrator
http://rt2x00.serialmonkey.com
Top
 Profile  
 
raphy
PostPosted: Sat Feb 21, 2009 7:09 pm 
Offline

Joined: Sat Feb 21, 2009 6:20 pm
Posts: 10
Oh I thought the legacy drivers were the old one from Ralink. My bad. I'll change my first message.
Top
 Profile  
 
IvD
PostPosted: Sat Feb 21, 2009 7:19 pm 
Offline
Site Admin

Joined: Sun Jun 05, 2005 1:01 pm
Posts: 5905
Location: Haarlem, The Netherlands
Well since you are using 2.6.28 anyway, you could try to use the in-kernel rt2500 driver to see if that works better..

_________________
Regards,
Ivo van Doorn
Project Administrator
http://rt2x00.serialmonkey.com
Top
 Profile  
 
raphy
PostPosted: Sat Feb 21, 2009 7:32 pm 
Offline

Joined: Sat Feb 21, 2009 6:20 pm
Posts: 10
Unfortunately their driver is still unusable (the connection get stuck after a few minutes and has to be restarted). But it works "as usual", as well as the windows driver with ndiswrapper. The only driver that doesn't work anymore is your driver, which ironically was the only one who worked decently (it is actually very good).
Top
 Profile  
 
IvD
PostPosted: Sat Feb 21, 2009 7:44 pm 
Offline
Site Admin

Joined: Sun Jun 05, 2005 1:01 pm
Posts: 5905
Location: Haarlem, The Netherlands
raphy wrote:
Unfortunately their driver is still unusable (the connection get stuck after a few minutes and has to be restarted).


Could you post more information (+ debug info) on the rt2x00 forum (the one where you initially posted this topic)?

raphy wrote:
The only driver that doesn't work anymore is your driver


Well technically, the rt2x00 driver is "ours", and the legacy driver which you are referring to is the Ralink driver + patches from us. ;)
In any case, both are maintained by us. :)

_________________
Regards,
Ivo van Doorn
Project Administrator
http://rt2x00.serialmonkey.com
Top
 Profile  
 
raphy
PostPosted: Sat Feb 21, 2009 7:54 pm 
Offline

Joined: Sat Feb 21, 2009 6:20 pm
Posts: 10
IvD wrote:
raphy wrote:
Unfortunately their driver is still unusable (the connection get stuck after a few minutes and has to be restarted).


Could you post more information (+ debug info) on the rt2x00 forum (the one where you initially posted this topic)?


Sure, how do I get the debug information?

IvD wrote:
raphy wrote:
The only driver that doesn't work anymore is your driver


Well technically, the rt2x00 driver is "ours", and the legacy driver which you are referring to is the Ralink driver + patches from us. ;)
In any case, both are maintained by us. :)


So the in-kernel driver is the 2x00 driver from your project?

I'll recompile my kernel and give you info about the in-built rt2500 driver.
Top
 Profile  
 
IvD
PostPosted: Sat Feb 21, 2009 8:04 pm 
Offline
Site Admin

Joined: Sun Jun 05, 2005 1:01 pm
Posts: 5905
Location: Haarlem, The Netherlands
raphy wrote:
Sure, how do I get the debug information?


When compiling the kernel, enable the config option CONFIG_RT2X00_DEBUG
After that you will find debug messages in /var/log/messages as usual.

raphy wrote:
IvD wrote:
raphy wrote:
The only driver that doesn't work anymore is your driver


Well technically, the rt2x00 driver is "ours", and the legacy driver which you are referring to is the Ralink driver + patches from us. ;)
In any case, both are maintained by us. :)


So the in-kernel driver is the 2x00 driver from your project?


That is right.

raphy wrote:
I'll recompile my kernel and give you info about the in-built rt2500 driver.


Thanks.

_________________
Regards,
Ivo van Doorn
Project Administrator
http://rt2x00.serialmonkey.com
Top
 Profile  
 
Vern
PostPosted: Sun Feb 22, 2009 4:15 pm 
Offline
User avatar

Joined: Sat Jan 14, 2006 6:29 pm
Posts: 897
Location: Carlsbad, California
raphy wrote:
So I'm using the kernel 2.6.28 (gentoo revisited), with the driver CVS 1.1.0 (but with a revision that worked fine until yesterday).
Sounds like you may not have recompiled the legacy driver for kernel 2.6.28. If you do, you'll probably get compile errors because the kernel interface has changed yet again.

Thanks,

_________________
Yr Hmbl Obt Svt & c
Bryan - In favor of Big Oil. Big fan of General Grievous.
Top
 Profile  
 
raphy
PostPosted: Sun Feb 22, 2009 4:21 pm 
Offline

Joined: Sat Feb 21, 2009 6:20 pm
Posts: 10
And yet, it compiles perfectly.

Code:
 * Fetching CVS module source/rt2500 into /usr/portage/distfiles/cvs-src ...                           
 * Running  cvs -q -f -z1 -d ":pserver:anonymous:@rt2400.cvs.sourceforge.net:/cvsroot/rt2400" login   
Logging in to :pserver:anonymous@rt2400.cvs.sourceforge.net:2401/cvsroot/rt2400                       
 * Running  cvs -q -f -z1 -d ":pserver:anonymous@rt2400.cvs.sourceforge.net:/cvsroot/rt2400" checkout  source/rt2500                                                                                         
U source/rt2500/CHANGELOG                                                                             
U source/rt2500/FAQ                                                                                   
U source/rt2500/LICENSE                                                                               
U source/rt2500/THANKS                                                                                 
U source/rt2500/Module/Makefile                                                                       
U source/rt2500/Module/README                                                                         
U source/rt2500/Module/RT2500STA.dat                                                                   
U source/rt2500/Module/TESTING                                                                         
U source/rt2500/Module/assoc.c                                                                         
U source/rt2500/Module/auth.c                                                                         
U source/rt2500/Module/auth_rsp.c                                                                     
U source/rt2500/Module/connect.c                                                                       
U source/rt2500/Module/eeprom.c                                                                       
U source/rt2500/Module/ifcfg-ra0                                                                       
U source/rt2500/Module/iwpriv_usage.txt                                                               
U source/rt2500/Module/md5.c                                                                           
U source/rt2500/Module/md5.h                                                                           
U source/rt2500/Module/mlme.c                                                                         
U source/rt2500/Module/mlme.h                                                                         
U source/rt2500/Module/oid.h                                                                           
U source/rt2500/Module/rt2560.h                                                                       
U source/rt2500/Module/rt2x00debug.c                                                                   
U source/rt2500/Module/rt2x00debug.h                                                                   
U source/rt2500/Module/rt_config.h                                                                     
U source/rt2500/Module/rtmp.h                                                                         
U source/rt2500/Module/rtmp_data.c                                                                     
U source/rt2500/Module/rtmp_def.h                                                                     
U source/rt2500/Module/rtmp_info.c                                                                     
U source/rt2500/Module/rtmp_init.c                                                                     
U source/rt2500/Module/rtmp_main.c                                                                     
U source/rt2500/Module/rtmp_tkip.c                                                                     
U source/rt2500/Module/rtmp_type.h                                                                     
U source/rt2500/Module/rtmp_wep.c                                                                     
U source/rt2500/Module/sanity.c                                                                       
U source/rt2500/Module/sync.c                                                                         
U source/rt2500/Module/wpa.c                                                                           
U source/rt2500/Module/wpa.h                                                                           
 * Copying source/rt2500 from /usr/portage/distfiles/cvs-src ...                                       
 * CVS module source/rt2500 is now in /var/tmp/paludis/net-wireless-rt2500-9999/work                   
>>> Done src_unpack                                                                                   
>>> Starting src_compile                                                                               
 * Preparing rt2500 module                                                                             
make HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= -C /usr/src/linux M=/var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module modules                                   
make: Entering directory `/usr/src/linux-2.6.28-gentoo-r1'                                             
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/rtmp_main.o             
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/mlme.o                   
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/connect.o               
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/sync.o                   
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/assoc.o                 
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/auth.o                   
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/auth_rsp.o               
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/rtmp_data.o             
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/rtmp_init.o             
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/sanity.o                 
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/rtmp_wep.o               
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/wpa.o                   
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/md5.o                   
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/rtmp_tkip.o             
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/rtmp_info.o             
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/rt2x00debug.o           
  CC [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/eeprom.o                 
  LD [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/rt2500.o                 
  Building modules, stage 2.                                                                           
  MODPOST 1 modules                                                                                   
  CC      /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/rt2500.mod.o             
  LD [M]  /var/tmp/paludis/net-wireless-rt2500-9999/work/source/rt2500/Module/rt2500.ko               
make: Leaving directory `/usr/src/linux-2.6.28-gentoo-r1'                                             
>>> Done src_compile


Weird isn't it? :shock:
Top
 Profile  
 
Vern
PostPosted: Tue Feb 24, 2009 4:21 pm 
Offline
User avatar

Joined: Sat Jan 14, 2006 6:29 pm
Posts: 897
Location: Carlsbad, California
Hi raphy,

Actually, on second thought (I often think after speaking), I can see where that may be the case. The problem is that the net device structure has changed in 2.6.28. So it could compile cleanly, but still have problems when you try to run it.

Thanks,

_________________
Yr Hmbl Obt Svt & c
Bryan - In favor of Big Oil. Big fan of General Grievous.
Top
 Profile  
 
raphy
PostPosted: Tue Feb 24, 2009 10:01 pm 
Offline

Joined: Sat Feb 21, 2009 6:20 pm
Posts: 10
Yeah, that may be a valid theory. Unfortunately, I can go back to previous kernel as my partitions are in EXT4, and the driver doesn't compile with the kernel 2.6.29. Stuck :D
Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  Page 1 of 1
  [ 14 posts ] 

Board index » Legacy Driver Support » rt2500 (pci) Legacy 802.11b/g Support

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group