rt2x00.serialmonkey.com

Support forum for the rt2x00 project
It is currently Mon Feb 08, 2010 10:14 pm

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.  [ 30 posts ]  Go to page 1, 2  Next

Did this post help you get your D-Link DWL-G122 Rev C1 USB adpater working?
Yes 100%  100%  [ 10 ]
No 0%  0%  [ 0 ]
Somewhat 0%  0%  [ 0 ]
Total votes : 10
Author Message
 Post subject: D-Link DWL-G122 Rev C1 USB adapter no lights [solved!]
PostPosted: Sat Nov 03, 2007 6:25 am 
Offline

Joined: Wed Oct 31, 2007 7:56 am
Posts: 15
This thread is a summarized continuation from here

D-Link DWL-G122 Rev C1 USB adpater has died?
http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?p=27105

The adapter is still functional but...

I am having trouble getting the rt73 driver to work with my D-Link DWL-G122 Rev C1 USB adapter.

Images of this usb adapter are here:
http://images.google.co.nz/images?q=D-Link%20DWL-G122

Everything seems to be setup correctly.

I've installed the rt73 driver but no lights show on the usb adapter and it cannot scan for access points.

I've summarized the relevant information for anyone who can help :-)

uname -r
Code:
2.6.20-16-generic


lsusb
Code:
Bus 007 Device 004: ID 07d1:3c03 D-Link System


lshw (relevant entry)
Code:
              *-usb:1
                   description: Generic USB device
                   product: 802.11 bg WLAN
                   vendor: Ralink
                   physical id: 3
                   bus info: usb@7:3
                   version: 0.01
                   capabilities: usb-2.00
                   configuration: driver=rt73 maxpower=300mA speed=480.0MB/s


cat /etc/modprobe.conf
Code:
alias wlan0 rt73


ifconfig -a
Code:
eth0      Link encap:Ethernet  HWaddr 00:19:D1:6A:C5:46
          inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::219:d1ff:fe6a:c546/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14834 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7070 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:8654293 (8.2 MiB)  TX bytes:1242781 (1.1 MiB)
          Base address:0x20c0 Memory:90300000-90320000

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:901 errors:0 dropped:0 overruns:0 frame:0
          TX packets:901 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:337597 (329.6 KiB)  TX bytes:337597 (329.6 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:15:E9:BA:C5:E9
          inet6 addr: fe80::215:e9ff:feba:c5e9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:704 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:34576 (33.7 KiB)  TX bytes:0 (0.0 b)

wlan0:ava Link encap:Ethernet  HWaddr 00:15:E9:BA:C5:E9
          inet addr:169.254.11.183  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1


iwconfig
Code:
wlan0     RT73 WLAN  ESSID:""
          Mode:Managed  Frequency=2.412 GHz  Bit Rate=54 Mb/s
          RTS thr:off   Fragment thr:off
          Link Quality=0/100  Signal level:-121 dBm  Noise level:-115 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


cat /etc/network/interfaces
Code:
# This file describes the network interfaces available on your system
# and how to activate them.

# The loopback network interface
auto lo
iface lo inet loopback
#address 127.0.0.1
#netmask 255.0.0.0

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.

# rt73 wireless network device using DHCP
auto wlan0
iface wlan0 inet dhcp
pre-up ifconfig wlan0 up
pre-up iwconfig wlan0 mode managed
pre-up iwconfig wlan0 essid Nexus
pre-up iwconfig wlan0 channel 6
pre-up iwpriv wlan0 set AuthMode=WPAPSK
pre-up iwpriv wlan0 set EncrypType=TKIP
pre-up iwpriv wlan0 set WPAPSK=<mykey>
pre-up iwpriv wlan0 set NetworkType=Infra


auto eth0
iface eth0 inet dhcp


modprobe.d/blacklist
Code:
# Added when rt73 module was installed
blacklist rt73usb
blacklist rt2570
blacklist rt2750usb
# Other modules that break rt73
blacklist rt2500usb
blacklist rt2x00lib


route
Code:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
link-local      *               255.255.0.0     U     0      0        0 wlan0
link-local      *               255.255.0.0     U     1000   0        0 eth0
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
default         *               0.0.0.0         U     1000   0        0 wlan0



As i said, it seems to be setup properly, the device is registered with the system but there is no lights / connectivity.

iwlist wlan0 scan
Code:
wlan0     No scan results


/etc/init.d/networking restart
Code:
* Reconfiguring network interfaces...                                                                                      RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.wlan0.pid with pid 7288
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:15:e9:ba:c5:e9
Sending on   LPF/wlan0/00:15:e9:ba:c5:e9
Sending on   Socket/fallback
There is already a pid file /var/run/dhclient.eth0.pid with pid 7340
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:19:d1:6a:c5:46
Sending on   LPF/eth0/00:19:d1:6a:c5:46
Sending on   Socket/fallback
DHCPRELEASE on eth0 to 192.168.0.1 port 67
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:15:e9:ba:c5:e9
Sending on   LPF/wlan0/00:15:e9:ba:c5:e9
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


From the terminal also:
Code:
ifconfig wlan0 up
iwconfig wlan0 mode managed
iwconfig wlan0 essid Nexus
iwconfig wlan0 channel 6
iwconfig wlan0 freq 2.4G
iwpriv wlan0 set AuthMode=WPAPSK
iwpriv wlan0 set EncrypType=TKIP
iwpriv wlan0 set WPAPSK=<mykey>
sleep 10
dhclient wlan0

has no effect, the dhclient can't find an ip address

I do have an ethernet cable plugged in for now. The results are the same without the cable plugged in and I'm using it to maintain internet connectivity. network restart finds an IP on eth0 straight away. I wish it was the same for wlan0!

I've uninstalled the network-manager app and installed RutilT which looks really good - if I had a wireless connection!

If anyone has any advice, please let me know, thanks :-)


Attachments:
File comment: I just replaced the debug log with this driver file. It's also attached to the post further down the page. This version of the driver works with the D-Link DWL-G122 Rev C1 USB adapter.
rt73-cvs-2007101214.tar.gz [296.39 KiB]
Downloaded 107 times


Last edited by davidwhthomas on Sat Nov 22, 2008 4:32 am, edited 5 times in total.
Top
 Profile  
 
 Post subject:
PostPosted: Sat Nov 03, 2007 11:18 am 
Offline

Joined: Sun Jun 03, 2007 4:00 pm
Posts: 195
Location: France
You can try this : Have a look, in /etc/udev/rules.d folder if there's a file named net_config.rules.
There should be only a line per network adapter. If you have more than one for your USB stick, you can safely remove these lines. A correct line will be created at next boot.


Top
 Profile  
 
 Post subject:
PostPosted: Sat Nov 03, 2007 2:14 pm 
Offline

Joined: Sat Nov 03, 2007 12:53 pm
Posts: 1
Hi,

had the same problem. My D-Link DWL-G122 USB-stick works with this older version attached. I use Ubuntu Feisty. If you want your stick working with WPA you have to follow the steps from the start:

1. PUT ALL IN RIGHT PLACE
- "lsmod | grep rt"
- blacklist the found rt-driver by inserting "blacklist rt*" in "/etc/modprobe.d/blacklist", replace * bei driver-number, like "rt73usb"
- make script "wlan" with following lines:

#!/bin/sh

IFACE=$1
ifconfig $IFACE up
sleep 3
iwconfig $IFACE mode managed
iwpriv $IFACE set AuthMode=WPAPSK
iwpriv $IFACE set EncrypType=TKIP
iwconfig $IFACE essid my_essid
iwpriv $IFACE set WPAPSK=my_password
dhclient $IFACE

- and replace "my_essid" and "WPAPSK=my_password" by your own routers settings and save as "wlan"
- copy script "wlan" to /usr/bin: "sudo cp wlan /usr/bin/wlan"
- change permissions "sudo chmod go+x /usr/bin/wlan"
- add line "/usr/bin/wlan wlan0;" in "/etc/init.d/bootmisc.sh" for autostarting script on boot
- replace "wlan0" if your wlan uses another device, like "rausb0" (in Ubuntu its probably "wlan0")

2. INSTALL KERNEL DRIVERS
- unpack attached driver package
- change to subdirectory "Module"
- type "make" and then "sudo make install" (you need "build-essential" and "kernel-headers" for your kernel for that, "uname -r" shows what kernel you use)
- now your kernel-module "rt73" should be installed
- type "sudo modprobe rt73" to load it
- check if module is there by "lsmod | grep rt"
- now check, if stick works: "sudo iwconfig wlan0 up" (replace by rausb0 if necessary)
- green light should blink now -> everything is in place and works, so reboot, to see if Ubuntu or your system loads everything in right order
- if green light doesn't blink, kernel module doesn't work
- PS: maybe you'll have to deactivate all network devices by "system / network"
- Good Luck :)

br
kris


Top
 Profile  
 
 Post subject:
PostPosted: Sat Nov 03, 2007 10:56 pm 
Offline

Joined: Wed Oct 31, 2007 7:56 am
Posts: 15
Starcrasher wrote:
You can try this : Have a look, in /etc/udev/rules.d folder if there's a file named net_config.rules.
There should be only a line per network adapter. If you have more than one for your USB stick, you can safely remove these lines. A correct line will be created at next boot.


Thanks for the suggestion.
I thought it might have been some kind of settings conflict.
However, I didn't have the file 'net_config.rules' listed there.


Last edited by davidwhthomas on Sat Nov 03, 2007 11:44 pm, edited 1 time in total.

Top
 Profile  
 
 Post subject:
PostPosted: Sat Nov 03, 2007 10:59 pm 
Offline

Joined: Wed Oct 31, 2007 7:56 am
Posts: 15
kris313 wrote:
Hi,

had the same problem. My D-Link DWL-G122 USB-stick works with this older version attached. I use Ubuntu Feisty. If you want your stick working with WPA you have to follow the steps from the start:

1. PUT ALL IN RIGHT PLACE
- "lsmod | grep rt"
- blacklist the found rt-driver by inserting "blacklist rt*" in "/etc/modprobe.d/blacklist", replace * bei driver-number, like "rt73usb"
- make script "wlan" with following lines:

#!/bin/sh

IFACE=$1
ifconfig $IFACE up
sleep 3
iwconfig $IFACE mode managed
iwpriv $IFACE set AuthMode=WPAPSK
iwpriv $IFACE set EncrypType=TKIP
iwconfig $IFACE essid my_essid
iwpriv $IFACE set WPAPSK=my_password
dhclient $IFACE

- and replace "my_essid" and "WPAPSK=my_password" by your own routers settings and save as "wlan"
- copy script "wlan" to /usr/bin: "sudo cp wlan /usr/bin/wlan"
- change permissions "sudo chmod go+x /usr/bin/wlan"
- add line "/usr/bin/wlan wlan0;" in "/etc/init.d/bootmisc.sh" for autostarting script on boot
- replace "wlan0" if your wlan uses another device, like "rausb0" (in Ubuntu its probably "wlan0")

2. INSTALL KERNEL DRIVERS
- unpack attached driver package
- change to subdirectory "Module"
- type "make" and then "sudo make install" (you need "build-essential" and "kernel-headers" for your kernel for that, "uname -r" shows what kernel you use)
- now your kernel-module "rt73" should be installed
- type "sudo modprobe rt73" to load it
- check if module is there by "lsmod | grep rt"
- now check, if stick works: "sudo iwconfig wlan0 up" (replace by rausb0 if necessary)
- green light should blink now -> everything is in place and works, so reboot, to see if Ubuntu or your system loads everything in right order
- if green light doesn't blink, kernel module doesn't work
- PS: maybe you'll have to deactivate all network devices by "system / network"
- Good Luck :)

br
kris


THANK-YOU!!!! THIS WORKED !!!! :D :D :D

The earlier version of the attached driver file worked!
There must be an issue with the newer version of the driver

The version that works is
rt73-cvs-2007101214
It is attached to an above post

You have resuscitated my USB adapter and it is now blinking and twinkling merrily :lol:

Note:
Quote:
- blacklist the found rt-driver by inserting "blacklist rt*" in "/etc/modprobe.d/blacklist", replace * bei driver-number, like "rt73usb"

I didn't need to add the blacklist drivers as they were already in
/etc/modprobe.d/blacklist

I removed the existing driver first with
Code:
modprobe -r rt73


I installed the new (older) driver with
Code:
cd rt73-cvs-2007101214/Module/
sudo -i
make clean
make
make install


I then restarted the computer and....

EVERYTHING IS WORKING!

Thanks to everyone for all your help,

When I first saw the lights come on on the adapter, I was ecstatic :wink:

cheers!

P.S
Another key thing I think perhaps is that I removed the network-manager app
Code:
sudo apt-get remove network-manager
sudo apt-get remove network-manager-gnome

and installed RutilT.
Code:
sudo apt-get install libgtk2.0-dev
sudo apt-get install g++-4.1
sudo apt-get install rutilt

I created a new 'profile' in RutilT for the connection and it got it up and running. RutilT manages the connection perfectly.
I hope this helps someone else too :D
Thanks serialmonkey!

UPDATE: I've attached the tarball again as it appears to have disappeared from the above post


Attachments:
File comment: Version that worked with D-Link DWL-G122 C1 and Ubuntu Feisty/Gutsy
rt73-cvs-2007101214.tar.gz [296.39 KiB]
Downloaded 212 times


Last edited by davidwhthomas on Thu Apr 17, 2008 9:31 am, edited 1 time in total.
Top
 Profile  
 
 Post subject: Packages
PostPosted: Sun Nov 04, 2007 3:43 pm 
Offline

Joined: Sun Jun 26, 2005 10:26 am
Posts: 1679
Location: Marseille, France
Nice you sorted everything out :)
You don't need to install libgtk2.0-dev and g++-4.1 if you use the rutilt package, this is only useful if you plan to compile it yourself. You should install the "g++" package, not a specific version, because you'll lack symbolic links and default compiler updates ;).

_________________
RutilT developer


Top
 Profile  
 
 Post subject: different adapter, same problem solved
PostPosted: Sun Nov 04, 2007 7:24 pm 
Offline

Joined: Sat Nov 03, 2007 11:07 am
Posts: 18
Location: Nice, France
Hi everybody.

I must say thankyou to kris313, because I was using rt73-cvs-2007110217
and experienced the problem I described in
http://rt2x00.serialmonkey.com/phpBB2/v ... php?t=4405

but with rt73-cvs-2007101214 everything is fine.

I would like to point out that I'm using a different adapter:
I don't have the D-link device, but an Edimax one.
Anyway, I gave my vote to the poll the same because I was so happy :D

Regards,
Giovanni Gherdovich


Top
 Profile  
 
 Post subject: Re: different adapter, same problem solved
PostPosted: Mon Nov 05, 2007 8:26 am 
Offline

Joined: Mon Nov 05, 2007 5:19 am
Posts: 2
GGhh wrote:
but with rt73-cvs-2007101214 everything is fine


Hi Giovanni,

I have the same problem when using rt73-cvs-2007110418. Could you please tell me where I may be able to get a copy of rt73-cvs-2007101214 ( URL ) ?

Many thanks,

Ed Chan


Top
 Profile  
 
 Post subject: pointing the above post
PostPosted: Mon Nov 05, 2007 8:38 am 
Offline

Joined: Sat Nov 03, 2007 11:07 am
Posts: 18
Location: Nice, France
Hi Ed,

Quote:
I have the same problem when using rt73-cvs-2007110418


I think the developing team should have a look on this issue.
The original poster, Spy84464 (he told in another thread yesterday),
me, and now you are experiencing problem with the latest release...

Quote:
Could you please tell me where I may be able to get a copy of rt73-cvs-2007101214 ( URL ) ?


Very easy: just log in the forum, scroll the window of this thread and you will
see that in a post of kris313 the rt73-cvs-2007101214 is attached.
Please note that if you are not logged in, you will not see any attachment.

Cheers,
Giovanni


Top
 Profile  
 
 Post subject: Re: pointing the above post
PostPosted: Mon Nov 05, 2007 10:52 am 
Offline

Joined: Mon Nov 05, 2007 5:19 am
Posts: 2
GGhh wrote:
Hi Ed,

[Very easy: just log in the forum, scroll the window of this thread and you will
see that in a post of kris313 the rt73-cvs-2007101214 is attached.
Please note that if you are not logged in, you will not see any attachment.



Thanks Giovanni, I did that, then got the "correct" source, compiled it and it works !!

Thanks to the other posters too.

Regards,

Ed Chan


Top
 Profile  
 
 Post subject: Re: pointing the above post
PostPosted: Tue Nov 06, 2007 1:09 am 
Offline

Joined: Tue Nov 06, 2007 12:50 am
Posts: 1
Hi !

It works !
Thanks to kris313 and the rt73-cvs-2007101214 build.

Cheers,
Sylvain


Top
 Profile  
 
 Post subject: that work but ...
PostPosted: Thu Nov 08, 2007 6:51 pm 
Offline

Joined: Thu Nov 08, 2007 3:54 pm
Posts: 3
Hello,

Thanks for your module, it nearly work well.

But i've got a large amount of errors messages in dmesg :

Code:
[  542.628000]  [<c03bc6c5>] start_kernel+0x235/0x380
[  542.628000]  [<c03bc230>] unknown_bootoption+0x0/0x260
[  542.628000]  =======================
[  542.636000] BUG: scheduling while atomic: swapper/0x10000200/0
[  542.636000]  [<c02da6e9>] __sched_text_start+0x459/0x580
[  542.636000]  [<eee6e6df>] RTMPSendRTSCTSFrame+0x23f/0x2f0 [rt73]
[  542.636000]  [<c01186f6>] __cond_resched+0x16/0x40
[  542.636000]  [<c02da83a>] cond_resched+0x2a/0x40
[  542.636000]  [<c016014d>] __kmalloc+0x7d/0xa0
[  542.636000]  [<ee8a050b>] ohci_urb_enqueue+0xcb/0x7e0 [ohci_hcd]
[  542.636000]  [<eee6ffc5>] RTUSBHardTransmit+0x1135/0x12c0 [rt73]
[  542.636000]  [<ee8a0cb3>] ohci_irq+0x83/0x200 [ohci_hcd]
[  542.640000]  [<ee904328>] usb_hcd_submit_urb+0x1e8/0x900 [usbcore]
[  542.640000]  [<eee674a3>] RTUSBInitTxDesc+0x53/0x80 [rt73]
[  542.640000]  [<eee67f30>] RTUSBBulkOutDataPacketComplete+0x0/0x310 [rt73]
[  542.640000]  [<eee67852>] RTUSBBulkOutDataPacket+0x1c2/0x1f0 [rt73]
[  542.640000]  [<eee67ad6>] RTUSBKickBulkOut+0x256/0x290 [rt73]
[  542.640000]  [<eee7090e>] RTMPSendPackets+0xae/0xe0 [rt73]
[  542.640000]  [<c0275898>] dev_hard_start_xmit+0x1d8/0x2b0
[  542.640000]  [<c0284278>] __qdisc_run+0x58/0x150
[  542.640000]  [<c0277236>] dev_queue_xmit+0x196/0x2c0
[  542.640000]  [<c0296f97>] ip_output+0x137/0x240
[  542.640000]  [<c02964b9>] ip_queue_xmit+0x1c9/0x480
[  542.640000]  [<c0117629>] __wake_up_common+0x39/0x60
[  542.640000]  [<c02ac6d1>] tcp_v4_send_check+0x41/0xe0
[  542.640000]  [<c02a6441>] tcp_transmit_skb+0x401/0x800
[  542.640000]  [<c02a33d4>] tcp_data_queue+0x434/0xbe0
[  542.640000]  [<c026f54f>] skb_checksum+0x4f/0x2d0
[  542.640000]  [<c0270b53>] __alloc_skb+0x53/0x120
[  542.640000]  [<c02a69a3>] tcp_send_ack+0xb3/0x100
[  542.640000]  [<c02a5168>] tcp_rcv_established+0x2c8/0x8c0
[  542.640000]  [<c02abc21>] tcp_v4_do_rcv+0x2c1/0x530
[  542.640000]  [<c028eb09>] ip_route_input+0x39/0xcc0
[  542.640000]  [<c01186f6>] __cond_resched+0x16/0x40
[  542.640000]  [<c02ae330>] tcp_v4_rcv+0x730/0x8a0
[  542.640000]  [<c0291d5c>] ip_local_deliver+0x11c/0x280
[  542.640000]  [<c0291a2c>] ip_rcv+0x27c/0x490
[  542.640000]  [<eebb4187>] packet_rcv_spkt+0x107/0x1b0 [af_packet]
[  542.640000]  [<c027537f>] netif_receive_skb+0x14f/0x300
[  542.640000]  [<c0276d8f>] process_backlog+0x7f/0x100
[  542.640000]  [<c0276f76>] net_rx_action+0x96/0x1c0
[  542.640000]  [<c011fcd2>] __do_softirq+0x52/0xa0
[  542.640000]  [<c011fd65>] do_softirq+0x45/0x50
[  542.640000]  [<c0105695>] do_IRQ+0x45/0x80
[  542.640000]  [<c0201706>] acpi_hw_register_write+0x154/0x187
[  542.640000]  [<c0104003>] common_interrupt+0x23/0x30
[  542.640000]  [<ee849e99>] acpi_processor_idle+0x1dd/0x384 [processor]
[  542.640000]  [<c01013cc>] cpu_idle+0x1c/0x60
[  542.640000]  [<c03bc6c5>] start_kernel+0x235/0x380
[  542.640000]  [<c03bc230>] unknown_bootoption+0x0/0x260
[  542.640000]  =======================
[  542.640000] BUG: scheduling while atomic: dd/0x10000100/4735
[  542.640000]  [<c02da6e9>] __sched_text_start+0x459/0x580
[  542.640000]  [<c01186f6>] __cond_resched+0x16/0x40
[  542.640000]  [<c02da83a>] cond_resched+0x2a/0x40
[  542.640000]  [<c016014d>] __kmalloc+0x7d/0xa0
[  542.640000]  [<ee8a050b>] ohci_urb_enqueue+0xcb/0x7e0 [ohci_hcd]
[  542.640000]  [<c01234e1>] do_gettimeofday+0x31/0xf0
[  542.640000]  [<ee904328>] usb_hcd_submit_urb+0x1e8/0x900 [usbcore]
[  542.640000]  [<eea25b80>] evdev_event+0x0/0x170 [evdev]
[  542.640000]  [<c023a66d>] atkbd_interrupt+0x1dd/0x5a0
[  542.640000]  [<eee67368>] RTUSBInitRxDesc+0x48/0x70 [rt73]
[  542.640000]  [<eee67b10>] RTUSBBulkRxComplete+0x0/0x40 [rt73]
[  542.640000]  [<c011fdb3>] tasklet_action+0x43/0x90
[  542.640000]  [<c011fcd2>] __do_softirq+0x52/0xa0
[  542.640000]  [<c011fd65>] do_softirq+0x45/0x50
[  542.640000]  [<c0105695>] do_IRQ+0x45/0x80
[  542.640000]  [<c0104003>] common_interrupt+0x23/0x30
[  542.640000]  [<c0176008>] file_update_time+0x18/0xa0
[  542.640000]  [<c0168f8b>] pipe_write+0x22b/0x470
[  542.640000]  [<c0162bd5>] do_sync_write+0xd5/0x120
[  542.640000]  [<c012dee0>] autoremove_wake_function+0x0/0x50
[  542.640000]  [<c01226ac>] __capable+0xc/0x20
[  542.640000]  [<c012dee0>] autoremove_wake_function+0x0/0x50
[  542.640000]  [<c016351e>] vfs_write+0xbe/0x190
[  542.640000]  [<c0162b00>] do_sync_write+0x0/0x120
[  542.640000]  [<c0163b91>] sys_write+0x41/0x70
[  542.640000]  [<c0102fc0>] sysenter_past_esp+0x69/0xa9
[  542.640000]  =======================


And my hard-drive is full 10 minutse after I plugged my key, then I have to reboot my computer.

For informations:
- I use ubuntu with kernel version
Code:
root@laptop:/opt/rt73-cvs-2007110803/Module# uname -a
Linux laptop 2.6.20-16-386 #2 Sun Sep 23 19:47:10 UTC 2007 i686 GNU/Linux


-my wifi key is a D-Link dwl-g122 ver C1
-I compiled the module rt73-cvs-2007110803.

modinfo :
Code:
root@laptop:/opt/rt73-cvs-2007110803/Module# modinfo rt73.ko
filename:       rt73.ko
license:        GPL
description:    Ralink RT73 802.11abg WLAN Driver 1.0.3.6 CVS 2007110803
author:         http://rt2x00.serialmonkey.com
srcversion:     848FC4F8ADF09D55B00C76F
alias:          usb:v1740p7100d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v2019pAB50d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v2019pAB01d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0769p31F3d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DF6p90ACd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DF6p9712d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v18E8p6238d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v18E8p6229d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v18E8p6196d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v148Fp2671d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v148Fp2573d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0pA874d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0pA861d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p6874d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0DB0p6877d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v13B1p0023d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v13B1p0020d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v06F8pE020d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v06F8pE010d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1472p0009d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1044p800Ad*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1044p8008d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v15A9p0004d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07D1p3C04d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07D1p3C03d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v14B2p3C22d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1371p9032d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1371p9022d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1631pC019d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v050Dp905Cd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v050Dp905Bd*dc*dsc*dp*ic*isc*ip*
alias:          usb:v050Dp705Ad*dc*dsc*dp*ic*isc*ip*
alias:          usb:v050Dp7050d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0411p00F4d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0B05p1724d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v0B05p1723d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v1690p0722d*dc*dsc*dp*ic*isc*ip*
alias:          usb:v07B8pB21Dd*dc*dsc*dp*ic*isc*ip*
depends:        usbcore
vermagic:       2.6.20-16-386 mod_unload 486
parm:           debug:Debug mask: n selects filter, 0 for none (int)
parm:           ifname:Network device name (default wlan%d) (charp)
parm:           firmName:Permit to load a different firmware: (default: rt73.bin)  (charp)


With this module I can use internet, but that crash after few minutes with full harddrive.


Top
 Profile  
 
 Post subject: pointing to other thread
PostPosted: Thu Nov 08, 2007 7:20 pm 
Offline

Joined: Sat Nov 03, 2007 11:07 am
Posts: 18
Location: Nice, France
Hello FabM,

Quote:
Thanks for your module, it nearly work well.
But i've got a large amount of errors [...]
-I compiled the module rt73-cvs-2007110803.


The cvs version wich is known to be the "snake-oil"http://en.wikipedia.org/wiki/Snake_oil
is the rt73-cvs-2007101214, wich is attached above by kris313
and worked fine for me.

So I didn't understand: you tried the rt73-cvs-2007101214, it worked,
and after you installed the rt73-cvs-2007110803 and you got problems?

Anyway, I think that a good thread about complaining on newer version
of rt73 is this one:
http://rt2x00.serialmonkey.com/phpBB2/v ... php?t=4414
The subject of the thread is "Latest rt73 CVS doesnt work",
wich I think is suitable for most of the problem that we, the poor users, find
along the way :)
Vern is looking at that threat; I think he is a developer, becouse he was
able to fix a problem in rt73-cvs-2007110217 just yesterday...

Maybe the developers can help you if you post debugging infos,
following the TESTING file (I did that and got my issue solved).

Cheers,
Giovanni


Top
 Profile  
 
 Post subject: Re: pointing to other thread
PostPosted: Thu Nov 08, 2007 8:56 pm 
Offline

Joined: Thu Nov 08, 2007 3:54 pm
Posts: 3
Sorry if I on the wrong thread, but i posted here because I'd exactly the same problem than davidwhthomas and the procedure that describe kris313 seems to worked (but only seems) in mine.

GGhh wrote:
So I didn't understand: you tried the rt73-cvs-2007101214, it worked,
and after you installed the rt73-cvs-2007110803 and you got problems?


hu ... Ok my mistake, in fact I didn't see their was an attachment and I downloaded the real daily cvs ...

But you can't see the attachment when you are not log in, and the first time I read this I was not log in.

then I will test this attachement, sorry for this mistake.

GGhh wrote:
Anyway, I think that a good thread about complaining on newer version
of rt73 is this one:
http://rt2x00.serialmonkey.com/phpBB2/v ... php?t=4414
The subject of the thread is "Latest rt73 CVS doesnt work",
wich I think is suitable for most of the problem that we, the poor users, find
along the way :)
Vern is looking at that threat; I think he is a developer, becouse he was
able to fix a problem in rt73-cvs-2007110217 just yesterday...


I will do that :-)

Thanks for the tip.

FabM


Top
 Profile  
 
 Post subject:
PostPosted: Fri Nov 09, 2007 1:36 am 
Offline

Joined: Tue Nov 06, 2007 2:52 pm
Posts: 1
Hello!
I also like to mention that rt73-cvs-2007101214 WORKED for me!!!
:D
So, many thanks to kris313 !!!

Like GGhh, I don't use a D-Link wireless USB adapter, but a Canyon CN-WF518 Wireless USB adapter. Infos about the product:
http://www.canyon-tech.com/products/con ... s/CN-WF518

First, I tried the rt73-cvs-2007110516 driver, which compiled & inserted well, BUT the AP scanning did not work at all. All I received was "wlan0 No scan results"

Then I entered this forum(registered first, to be able to see attachements :) ), discovered the kris313 attachement. After compiling & inserting module: VICTORYYYYYY!!! :D
Scanning WORKS!

I tested the "managed" mode (right now I'm connected to my wireless router with my Canyon), "ad-hoc" mode (my Canyon was "seen" by my girlfriend's wireless adapter, and she could connect to my computer, at 11Mb/s), and "monitor"(adapter switched to this mode without problems, but I don't know how to use it...:P )

Here are some details about my system:
Code:
# uname -a
Linux perhan 2.6.19-gentoo-r5 #1 SMP Fri Oct 26 02:58:53 EEST 2007 i686 AMD Athlon(tm) XP 1800+ AuthenticAMD GNU/Linux

# lsusb
Bus 001 Device 001: ID 0000:0000
Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp.
...

# iwconfig wlan0
wlan0     RT73 WLAN  ESSID:"dlink"
          Mode:Managed  Frequency=2.437 GHz  Access Point: 00:19:5B:B4:E0:9F
          Bit Rate=54 Mb/s
          RTS thr:off   Fragment thr=65534 B
          Encryption key:off
          Link Quality=79/100  Signal level:-60 dBm  Noise level:-99 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


The distance between my Canyon and the access point is about 5-6 meters, and there are two walls in the way, so I guess an link quality of about 80% is pretty good...

Another thing to notice: there are NO weirdy "dmesg" messages from rt73 or my usb card!

So (to FabM) use the kris313 attachment, I think will work smoothly!

I'm surprised about a single thing: I tested some CVS versions newer than the 2007101214 one, and that did not work. It's a bit odd that a working version is followed by some other non-working versions!
Do the development team knows about this thing?...


Anyway, to summarize:
Happy to announce that Canyon CN-WF518 Wireless USB adapter also WORKS with rt73 driver(rt73-cvs-2007101214) !!!
:D


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 30 posts ]  Go to page 1, 2  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 0 guests


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 © 2000, 2002, 2005, 2007 phpBB Group