Problems with rt2x00 USB interface on powerpc
Hi.
I have an iBook G3 600MHz combo (late 2001 model, powerpc) with a USB wireless card rt2x00 that doesn't work.
I just compiled a fresh 2.6.26-rc4 kernel and it can't get a lease from the access point, even though it is able to see the access point.
The userland here is Debian unstable (sid) and I can perform some of the steps in the direction of configuring the interface. For instance, the following works (I am using wep as the encryption system with other systems running under Linux, but, unfortunately, EVEN disabling encryption for the sake of the tests doesn't help here):
*insert USB card*
ifconfig wlan0 up
iwconfig wlan0 essid "default"
iwconfig wlan0 s:my-key
iwconfig wlan0 ap any
(Here it shows that it can see the access point) dhclient wlan0
(Here, it is unable to grab an IP addess from the access point)
I have all the information available (like the revision of my USB device) for any developer that could help me in eliminating this bug from the kernel on big-endian architectures.
Thanks in advance, Rogério.
P.S.: I am not currently subscribed to linux-kernel, so I would appreciate any copies of the replies. Thanks.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.orgHi there.
I just did some more tests and I would like to report them here.
Quoted 2 lines · Rogério Brito
I have an iBook G3 600MHz combo (late 2001 model, powerpc) with a USB wireless card rt2x00 that doesn't work.
It seems that we have some problems with the USB card even on ia32:
after it is configured, I have to issue the command "iwconfig wlan0 ap any" all the time so that I can be able to download anything or even resolve names.
With a PCMCIA rt2500 adapter, I don't have such problems when running a stock Ubuntu kernel from Hardy Heron.
So, it seems that the problem is a little deeper than just some endianness thing to it.
Regards, Rogério Brito.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.orgQuoted 14 lines · Rogério Brito
Hi.
I have an iBook G3 600MHz combo (late 2001 model, powerpc) with a USB wireless card rt2x00 that doesn't work.
I just compiled a fresh 2.6.26-rc4 kernel and it can't get a lease from the access point, even though it is able to see the access point.
The userland here is Debian unstable (sid) and I can perform some of the steps in the direction of configuring the interface. For instance, the following works (I am using wep as the encryption system with other systems running under Linux, but, unfortunately, EVEN disabling encryption for the sake of the tests doesn't help here):
Quoted 8 lines
*insert USB card*
ifconfig wlan0 up
iwconfig wlan0 essid "default"
iwconfig wlan0 s:my-key
iwconfig wlan0 ap any
(Here it shows that it can see the access point) dhclient wlan0
(Here, it is unable to grab an IP addess from the access point)
You should set the key _before_ setting the essid.
John
Signature · 2 lines
John W. Linville [email protected]
First of all, thanks John for taking the time to reply to my message.
Quoted 12 lines · John W. Linville
Quoted 11 lines · Rogério Brito
I have an iBook G3 600MHz combo (late 2001 model, powerpc) with a USB wireless card rt2x00 that doesn't work.
I just compiled a fresh 2.6.26-rc4 kernel and it can't get a lease from the access point, even though it is able to see the access point.
The userland here is Debian unstable (sid) and I can perform some of the steps in the direction of configuring the interface. For instance, the following works (I am using wep as the encryption system with other systems running under Linux, but, unfortunately, EVEN disabling encryption for the sake of the tests doesn't help here):
(...)
Quoted 3 lines
Quoted 1 line
(Here, it is unable to grab an IP addess from the access point)
You should set the key _before_ setting the essid.
Thanks, but that unfortunately doesn't seem to help. :-(
I have taken dmesg "snapshots" of my system together with many other information regarding how it is configured and I put it at my homepage, at <http://www.ime.usp.br/debug/>.
Quoted 1 line
From what I am seeing, it looks like the bug mentioned in
<http://bugzilla.kernel.org/show_bug.cgi?id=9388>, but I don't get the stack trace that is present there and I'm just trying to use WEP instead of WPA or anything fancier.
Thanks for all the help and please let me know if further information can be helpful for debugging this situation.
Thanks again, Rogerio Brito
Quoted 19 lines · Rog?rio Brito
First of all, thanks John for taking the time to reply to my message.
Quoted 12 lines · John W. Linville
Quoted 11 lines · Rogério Brito
I have an iBook G3 600MHz combo (late 2001 model, powerpc) with a USB wireless card rt2x00 that doesn't work.
I just compiled a fresh 2.6.26-rc4 kernel and it can't get a lease from the access point, even though it is able to see the access point.
The userland here is Debian unstable (sid) and I can perform some of the steps in the direction of configuring the interface. For instance, the following works (I am using wep as the encryption system with other systems running under Linux, but, unfortunately, EVEN disabling encryption for the sake of the tests doesn't help here):
(...)
Quoted 2 lines
Quoted 1 line
(Here, it is unable to grab an IP addess from the access point)
Quoted 7 lines
Quoted 1 line
You should set the key _before_ setting the essid.
Thanks, but that unfortunately doesn't seem to help. :-(
I have taken dmesg "snapshots" of my system together with many other information regarding how it is configured and I put it at my homepage, at <http://www.ime.usp.br/debug/>.
404
Quoted 4 lines
Quoted 1 line
From what I am seeing, it looks like the bug mentioned in
<http://bugzilla.kernel.org/show_bug.cgi?id=9388>, but I don't get the stack trace that is present there and I'm just trying to use WEP instead of WPA or anything fancier.
Did you apply this patch?
http://bugzilla.kernel.org/attachment.cgi?id=14384
John
Signature · 2 lines
John W. Linville [email protected]
Hi, again, John.
Quoted 6 lines · John W. Linville
Quoted 3 lines · Rog?rio Brito
I have taken dmesg "snapshots" of my system together with many other information regarding how it is configured and I put it at my homepage, at <http://www.ime.usp.br/debug/>.
404
I think that you should have received a later reply telling about the typo in the address above. It should have been:
<http://www.ime.usp.br/~rbrito/debug/>.
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
From what I am seeing, it looks like the bug mentioned in
<http://bugzilla.kernel.org/show_bug.cgi?id=9388>, but I don't get the stack trace that is present there and I'm just trying to use WEP instead of WPA or anything fancier.
Did you apply this patch?
http://bugzilla.kernel.org/attachment.cgi?id=14384
No, I did not. Is it still relevant with -rc4 or with -rc5? I still get the same problem with -rc5 (but I will have to test it a bit more with -rc5). Just as a refresher:
* I can set everything on the iBook with the wireless key plugged;
* The wireless key *sees* the AP, even with encryption (that is, it grabs the MAC address of the AP, it (sometimes) shows me the signal strength, and if I issue "iwconfig wlan0 ap any", I see both the led of the wireless key blink and an increase of amount of data transmitted and received with "ifconfig wlan0");
* With everything set this way, if I do "dhclient wlan0", it doesn't get a lease from the AP---actually, despite the fact that it is possible to see the other point, dhclient goes, after some attempts of getting a lease, to background, but no address is ever gotten;
* Just to rule out possible problems with something sent to the address 255.255.255.255 (which is reported as being done by dhclient), I tried to configure the address by hand via ifconfig, but, for instance, I couldn't ping my AP (which I can from other computers with a rt61pci driver and a PCMCIA connection);
* As I mentioned above, I have no problems with the rt61pci driver, but the USB one doesn't seem to work (unfortunately, the iBook does not have a PCMCIA slot). With a notebook with an on-board Intel wireless card, I *also* don't have any problems.
Well, thanks, for the help so far. I hope that we can solve this issue quite soon, as I need this iBook for work.
I am willing to help as much as I can and test anything (even something that might be "experimental"). I think that this is as good a tester that you can get, right? :-)
Thanks, Rogério Brito.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.orgHi again, John.
I'm including Ivo van Doorn in this e-mail. I hope that the problem gets solved soon.
Quoted 8 lines · Rogério Brito
Hi, again, John.
Quoted 5 lines · John W. Linville
Quoted 3 lines · Rog?rio Brito
I have taken dmesg "snapshots" of my system together with many other information regarding how it is configured and I put it at my homepage, at <http://www.ime.usp.br/debug/>.
Quoted 5 lines
Quoted 1 line
404
I think that you should have received a later reply telling about the typo in the address above. It should have been:
<http://www.ime.usp.br/~rbrito/debug/>.
This time I hope that I have not done anything incorrectly.
Quoted 11 lines
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
From what I am seeing, it looks like the bug mentioned in
<http://bugzilla.kernel.org/show_bug.cgi?id=9388>, but I don't get the stack trace that is present there and I'm just trying to use WEP instead of WPA or anything fancier.
Did you apply this patch?
http://bugzilla.kernel.org/attachment.cgi?id=14384No, I did not. Is it still relevant with -rc4 or with -rc5? I still get the same problem with -rc5 (but I will have to test it a bit more with -rc5).
Unfortunately, this patch won't even apply with 2.6.26-rc5 as the code seems to have changed a lot between that date and today. For instance, there doesn't seem to exist a function called "rt2500usb_config_mac_addr" in the rt2x00 directory (just did a grep on my unconnected iBook).
I hope that this helps Ivo to understand what the issue is:
Quoted 22 lines
Just as a refresher:
* I can set everything on the iBook with the wireless key plugged;
* The wireless key *sees* the AP, even with encryption (that is, it grabs the MAC address of the AP, it (sometimes) shows me the signal strength, and if I issue "iwconfig wlan0 ap any", I see both the led of the wireless key blink and an increase of amount of data transmitted and received with "ifconfig wlan0");
* With everything set this way, if I do "dhclient wlan0", it doesn't get a lease from the AP---actually, despite the fact that it is possible to see the other point, dhclient goes, after some attempts of getting a lease, to background, but no address is ever gotten;
* Just to rule out possible problems with something sent to the address 255.255.255.255 (which is reported as being done by dhclient), I tried to configure the address by hand via ifconfig, but, for instance, I couldn't ping my AP (which I can from other computers with a rt61pci driver and a PCMCIA connection);
* As I mentioned above, I have no problems with the rt61pci driver, but the USB one doesn't seem to work (unfortunately, the iBook does not have a PCMCIA slot). With a notebook with an on-board Intel wireless card, I *also* don't have any problems.
Quoted 6 lines
Well, thanks, for the help so far. I hope that we can solve this issue quite soon, as I need this iBook for work.
I am willing to help as much as I can and test anything (even something that might be "experimental"). I think that this is as good a tester that you can get, right? :-)
Again, I am willing to test any "intrusive" change as I still don't have valuable data on that machine. BTW, I have firmware from Debian's ralink-firmware package (which should be what ralink has released) installed on this machine.
I don't know if the firmware is needed in my case or not, though (my USB adaptor is a D-Link DWL-G122 H/W Ver. B1, F/W Ver.: 2.03---took that info from the back of the stick).
Oh, I should mention that MacOS X is able to use the card without any problems on this machine and with encryption. (I may have forgotten to say that before). And, just to rule out things, I can test this USB adaptor on a ia32 notebook running Ubuntu's Hardy Heron, but I don't know how much patched their kernel is.
Thanks, Rogério Brito.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.orgHi,
Quoted 9 lines
Quoted 9 lines
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
From what I am seeing, it looks like the bug mentioned in
<http://bugzilla.kernel.org/show_bug.cgi?id=9388>, but I don't get the stack trace that is present there and I'm just trying to use WEP instead of WPA or anything fancier.
Did you apply this patch?
http://bugzilla.kernel.org/attachment.cgi?id=14384
Quoted 7 lines
Quoted 2 lines
No, I did not. Is it still relevant with -rc4 or with -rc5? I still get the same problem with -rc5 (but I will have to test it a bit more with -rc5).
Unfortunately, this patch won't even apply with 2.6.26-rc5 as the code seems to have changed a lot between that date and today. For instance, there doesn't seem to exist a function called "
rt2500usb_config_mac_addr" in the rt2x00 directory (just did a grep on my unconnected iBook).
That patch was a bugfix for 2.6.25. The bug it fixed isn't present in the 2.6.26 cycle.
Quoted 29 lines
Quoted 22 lines
Just as a refresher:
* I can set everything on the iBook with the wireless key plugged;
* The wireless key *sees* the AP, even with encryption (that is, it grabs the MAC address of the AP, it (sometimes) shows me the signal strength, and if I issue "iwconfig wlan0 ap any", I see both the led of the wireless key blink and an increase of amount of data transmitted and received with "ifconfig wlan0");
* With everything set this way, if I do "dhclient wlan0", it doesn't get a lease from the AP---actually, despite the fact that it is possible to see the other point, dhclient goes, after some attempts of getting a lease, to background, but no address is ever gotten;
* Just to rule out possible problems with something sent to the address 255.255.255.255 (which is reported as being done by dhclient), I tried to configure the address by hand via ifconfig, but, for instance, I couldn't ping my AP (which I can from other computers with a rt61pci driver and a PCMCIA connection);
* As I mentioned above, I have no problems with the rt61pci driver, but the USB one doesn't seem to work (unfortunately, the iBook does not have a PCMCIA slot). With a notebook with an on-board Intel wireless card, I *also* don't have any problems.Quoted 6 lines
Well, thanks, for the help so far. I hope that we can solve this issue quite soon, as I need this iBook for work.
I am willing to help as much as I can and test anything (even something that might be "experimental"). I think that this is as good a tester that you can get, right? :-)
Quoted 8 lines
Again, I am willing to test any "intrusive" change as I still don't have valuable data on that machine. BTW, I have firmware from Debian's ralink-firmware package (which should be what ralink has released) installed on this machine.
I don't know if the firmware is needed in my case or not, though (my USB adaptor is a D-Link DWL-G122 H/W Ver. B1, F/W Ver.: 2.03---took that info from the back of the stick).
Which driver is actually being used? rt2500usb or rt73usb? Also what was the last kernel version on which the driver worked for you?
If there was a last known working kernel, could you download the debugfs script:
http://rt2x00.serialmonkey.com/phpBB/download/file.php?id=1969
enable debugfs and MAC80211_DEBUGFS and RT2X00_LIB_DEBUGFS in your kernel, and run the script to dump all registers from the hardware to a file?
Please do this for both the working kernel as the non-working kernel so I can see if there is a register initialization problem which could have been triggered by an endian-problem.
Ivo
Hi, Ivo.
First of all, thank you so much for helping with this issue. It is greatly appreciated.
Quoted 9 lines · Ivo van Doorn
Hi,
Quoted 4 lines
Unfortunately, this patch won't even apply with 2.6.26-rc5 as the code seems to have changed a lot between that date and today. For instance, there doesn't seem to exist a function called "
rt2500usb_config_mac_addr" in the rt2x00 directory (just did a grep on my unconnected iBook).That patch was a bugfix for 2.6.25. The bug it fixed isn't present in the 2.6.26 cycle.
Nice to know that. I saw that the code has changed quite a good amount...
Anyway, I don't know if you saw the various outputs that I put at my homepage (lots of dmesgs with the 2.6.26-rc4 kernel):
http://www.ime.usp.br/~rbrito/debug/
(Not included here because the list has limits on the size of e-mails, AFAIK).
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Just as a refresher:
* I can set everything on the iBook with the wireless key plugged;
* The wireless key *sees* the AP, even with encryption (that is, it grabs the MAC address of the AP, it (sometimes) shows me the signal strength, and if I issue "iwconfig wlan0 ap any", I see both the led of the wireless key blink and an increase of amount of data transmitted and received with "ifconfig wlan0");
Just a comment here: it seems that with the -rc5 kernel I don't get always the wireless key seeing the AP... Sometimes it shows "Not Associated". I will try to reproduce that with an -rc4 kernel again.
Quoted 26 lines
Quoted 26 lines
Quoted 14 lines
* With everything set this way, if I do "dhclient wlan0", it doesn't get a lease from the AP---actually, despite the fact that it is possible to see the other point, dhclient goes, after some attempts of getting a lease, to background, but no address is ever gotten;
* Just to rule out possible problems with something sent to the address 255.255.255.255 (which is reported as being done by dhclient), I tried to configure the address by hand via ifconfig, but, for instance, I couldn't ping my AP (which I can from other computers with a rt61pci driver and a PCMCIA connection);
* As I mentioned above, I have no problems with the rt61pci driver, but the USB one doesn't seem to work (unfortunately, the iBook does not have a PCMCIA slot). With a notebook with an on-board Intel wireless card, I *also* don't have any problems.Quoted 6 lines
Well, thanks, for the help so far. I hope that we can solve this issue quite soon, as I need this iBook for work.
I am willing to help as much as I can and test anything (even something that might be "experimental"). I think that this is as good a tester that you can get, right? :-)
Again, I am willing to test any "intrusive" change as I still don't have valuable data on that machine. BTW, I have firmware from Debian's ralink-firmware package (which should be what ralink has released) installed on this machine.
Quoted 5 lines
Quoted 3 lines
I don't know if the firmware is needed in my case or not, though (my USB adaptor is a D-Link DWL-G122 H/W Ver. B1, F/W Ver.: 2.03---took that info from the back of the stick).
Which driver is actually being used? rt2500usb or rt73usb?
The driver that actually gets loaded is rt2500usb. I tried rmmod'ing rt2500usb and loading rt73usb, but a quick iwconfig doesn't even show the interfaces.
Quoted 2 lines
Also what was the last kernel version on which the driver worked for you?
Unfortunately, I don't have any kernel for which this has worked for me. I just did an experiment: I plugged the adaptor on a ia32 notebook where a rt61pci works fine (it is running Ubuntu's Hardy---well, actually, there are some problems, but I can get to that latter), but the USB key was non working with the symptoms that I described above.
Quoted 4 lines
If there was a last known working kernel, could you download the debugfs script:
http://rt2x00.serialmonkey.com/phpBB/download/file.php?id=1969enable debugfs and
MAC80211_DEBUGFSandRT2X00_LIB_DEBUGFSin your kernel, and run the script to dump all registers from the hardware to a file?
I just grabbed the script. Here is the output with the options enabled and the results are attached here.
Quoted 3 lines
Please do this for both the working kernel as the non-working kernel so I can see if there is a register initialization problem which could have been triggered by an endian-problem.
That was my first suspicion: and endianess problem. But now I am not so sure.
Thanks again, Rogério Brito.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org2.6.26-rc5-2
driver: rt2500usb
version: 2.1.4
compiled: Jun 8 2008 17:08:54dev_flags: 0x00000e2f
rt chip: 1201
rf chip: 0005
revision:00000005
csr length: 128
eeprom length: 53
bbp length: 96
rf length: 5
csr
0 :0x00050000
1 :0x00040000
2 :0x13000000
3 :0xe9460000
4 :0x8a8d0000
5 :0x13000000
6 :0x51460000
7 :0x65100000
8 :0x09800000
9 :0xff1d0000
10 :0x00140000
11 :0x000a0000
12 :0x013a0000
13 :0x11110000
14 :0x1e110000
15 :0x01ee0000
16 :0x00000000
17 :0x01fe0000
18 :0x005a0000
19 :0xff000000
20 :0x00020000
21 :0x1e460000
22 :0x00530000
23 :0x00000000
24 :0x00000000
25 :0x00000000
26 :0x00000000
27 :0x00000000
28 :0x00000000
29 :0x00000000
30 :0x00000000
31 :0x00000000
32 :0x1ec00000
33 :0xb1620000
34 :0x007e0000
35 :0xb3af0000
36 :0xb3aa0000
37 :0x8c8d0000
38 :0x8b8a0000
39 :0x86870000
40 :0x00850000
41 :0x01620000
42 :0x000a0000
43 :0x00000000
44 :0x140a0000
45 :0x70380000
46 :0x0c130000
47 :0x06090000
48 :0x03050000
49 :0x02030000
50 :0xfa000000
51 :0x000b0000
52 :0x00030000
53 :0xe78f0000
54 :0x00000000
55 :0x00000000
56 :0x00000000
57 :0x00000000
58 :0x00000000
59 :0x00000000
60 :0x00000000
61 :0x00000000
62 :0x00000000
63 :0x00000000
64 :0x00000000
65 :0x00000000
66 :0x00000000
67 :0x00000000
68 :0x00000000
69 :0x00000000
70 :0x00000000
71 :0x00000000
72 :0x00000000
73 :0x00000000
74 :0x00000000
75 :0x00000000
76 :0x00000000
77 :0x00000000
78 :0x00000000
79 :0x00000000
80 :0x00000000
81 :0x00000000
82 :0x00000000
83 :0x00000000
84 :0x00000000
85 :0x00000000
86 :0x00000000
87 :0x00000000
88 :0x00000000
89 :0x00000000
90 :0x00000000
91 :0x00000000
92 :0x00000000
93 :0x00000000
94 :0x00000000
95 :0x00000000
96 :0x12210000
97 :0x00030000
98 :0x00000000
99 :0x00000000
100 :0x000f0000
101 :0x82060000
102 :0x821e0000
103 :0x91000000
104 :0x00000000
105 :0x0e070000
106 :0x54000000
107 :0x00000000
108 :0x00000000
109 :0x00000000
110 :0x00000000
111 :0x00000000
112 :0x032c0000
113 :0xfb580000
114 :0x63110000
115 :0x0a1f0000
116 :0x00000000
117 :0x00000000
118 :0x00000000
119 :0x00000000
120 :0x00000000
121 :0x00000000
122 :0x02e10000
123 :0x00000000
124 :0x00000000
125 :0x00000000
126 :0x00000000
127 :0x00000422
eeprom
0 :0x2570
1 :0x0104
2 :0x1300
3 :0xe946
4 :0x8a8d
5 :0xffff
6 :0xffff
7 :0xffff
8 :0xffff
9 :0xffff
10 :0xffff
11 :0x2829
12 :0xfff0
13 :0x00ff
14 :0x112c
15 :0x1518
16 :0x1618
17 :0x3e00
18 :0xffff
19 :0xffff
20 :0xffff
21 :0xffff
22 :0xffff
23 :0xffff
24 :0xffff
25 :0xffff
26 :0xffff
27 :0xffff
28 :0xffff
29 :0xffff
30 :0x1717
31 :0x1717
32 :0x1717
33 :0x1717
34 :0x1617
35 :0x1616
36 :0x1616
37 :0xffff
38 :0xffff
39 :0xffff
40 :0xffff
41 :0xffff
42 :0xffff
43 :0xffff
44 :0xffff
45 :0xffff
46 :0xffff
47 :0xffff
48 :0x0032
49 :0x6880
50 :0x3850
51 :0x6f5f
52 :0xfa00
bbp
0 :0x13
1 :0x55
2 :0x06
3 :0x02
4 :0x19
5 :0x0b
6 :0x10
7 :0x00
8 :0x00
9 :0x00
10 :0x00
11 :0x04
12 :0x01
13 :0xa8
14 :0x1a
15 :0x30
16 :0xac
17 :0x00
18 :0x18
19 :0xff
20 :0x1e
21 :0x18
22 :0x18
23 :0x08
24 :0x80
25 :0x50
26 :0x08
27 :0x23
28 :0x18
29 :0x18
30 :0x10
31 :0x2b
32 :0xb9
33 :0x55
34 :0x12
35 :0x50
36 :0x11
37 :0x05
38 :0x00
39 :0xc4
40 :0x02
41 :0x60
42 :0x09
43 :0x34
44 :0x0b
45 :0x6e
46 :0x70
47 :0x0a
48 :0x04
49 :0x02
50 :0x68
51 :0x18
52 :0x04
53 :0x10
54 :0x18
55 :0x2d
56 :0x08
57 :0x10
58 :0x08
59 :0x02
60 :0x3e
61 :0x5f
62 :0x00
63 :0x00
64 :0x01
65 :0x03
66 :0x00
67 :0x00
68 :0x00
69 :0x00
70 :0x46
71 :0x00
72 :0x00
73 :0x00
74 :0xd4
75 :0xff
76 :0x19
77 :0x05
78 :0x08
79 :0x00
80 :0x00
81 :0x05
82 :0x14
83 :0x50
84 :0xc0
85 :0x10
86 :0xcf
87 :0x00
88 :0x00
89 :0x00
90 :0x00
91 :0x00
92 :0x00
93 :0x00
94 :0x00
95 :0x00
rf
0 :0x00000000
1 :0x00022010
2 :0x000008a6
3 :0x00062d11
4 :0x00000e07
wlan0 Link encap:Ethernet HWaddr 00:13:46:e9:8d:8a
UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Scan completed :
Cell 01 - Address: 00:13:46:51:10:65
ESSID:"default"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=51/100 Signal level=-53 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=0000005b34700179wlan0 IEEE 802.11 ESSID:"default"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated Tx-Power=22 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Hi,
Quoted 9 lines
Quoted 7 lines
Quoted 4 lines
Unfortunately, this patch won't even apply with 2.6.26-rc5 as the code seems to have changed a lot between that date and today. For instance, there doesn't seem to exist a function called "
rt2500usb_config_mac_addr" in the rt2x00 directory (just did a grep on my unconnected iBook).That patch was a bugfix for 2.6.25. The bug it fixed isn't present in the 2.6.26 cycle.
Nice to know that. I saw that the code has changed quite a good amount...
Hehe, yes rt2x00 code is moving quit a lot per kernel release.
Quoted 3 lines
Anyway, I don't know if you saw the various outputs that I put at my homepage (lots of dmesgs with the 2.6.26-rc4 kernel):
http://www.ime.usp.br/~rbrito/debug/
Yeah, saw them.
Quoted 9 lines
Quoted 5 lines
Quoted 3 lines
I don't know if the firmware is needed in my case or not, though (my USB adaptor is a D-Link DWL-G122 H/W Ver. B1, F/W Ver.: 2.03---took that info from the back of the stick).
Which driver is actually being used? rt2500usb or rt73usb?
The driver that actually gets loaded is rt2500usb. I tried rmmod'ing rt2500usb and loading rt73usb, but a quick iwconfig doesn't even show the interfaces.
That means it really is a rt2500usb device. ;)
Quoted 8 lines
Quoted 2 lines
Also what was the last kernel version on which the driver worked for you?
Unfortunately, I don't have any kernel for which this has worked for me. I just did an experiment: I plugged the adaptor on a ia32 notebook where a rt61pci works fine (it is running Ubuntu's Hardy---well, actually, there are some problems, but I can get to that latter), but the USB key was non working with the symptoms that I described above.
That is most unfortunate, since register dumps are usually most usefull when I can compare the actual register values between a working and non-working setup. However I just realized I had a D-Link stick myself, and apparently I have the exact same model/type. I'll compile a 2.6.26-rc5 kernel and see if that stick works for me, if so, I have the working register dump. And if not, then we can rule out endian problems.
Quoted 7 lines
Quoted 4 lines
If there was a last known working kernel, could you download the debugfs script:
http://rt2x00.serialmonkey.com/phpBB/download/file.php?id=1969enable debugfs and
MAC80211_DEBUGFSandRT2X00_LIB_DEBUGFSin your kernel, and run the script to dump all registers from the hardware to a file?I just grabbed the script. Here is the output with the options enabled and the results are attached here.
Thanks.
Ivo
Hi, Ivo.
Thank you very much for your very kind reply.
Quoted 6 lines · Ivo van Doorn
Hi,
Quoted 2 lines
Nice to know that. I saw that the code has changed quite a good amount...
Hehe, yes rt2x00 code is moving quit a lot per kernel release.
Granted. :-) You have been working quite a lot. :-)
Quoted 5 lines
Quoted 3 lines
Anyway, I don't know if you saw the various outputs that I put at my homepage (lots of dmesgs with the 2.6.26-rc4 kernel):
http://www.ime.usp.br/~rbrito/debug/Yeah, saw them.
Hope that they prove somewhat useful.
Quoted 11 lines
Quoted 9 lines
Quoted 5 lines
Quoted 3 lines
I don't know if the firmware is needed in my case or not, though (my USB adaptor is a D-Link DWL-G122 H/W Ver. B1, F/W Ver.: 2.03---took that info from the back of the stick).
Which driver is actually being used? rt2500usb or rt73usb?
The driver that actually gets loaded is rt2500usb. I tried rmmod'ing rt2500usb and loading rt73usb, but a quick iwconfig doesn't even show the interfaces.
That means it really is a rt2500usb device. ;)
Yes. :) I have firmware files installed under /lib/firmware also (taken from Debian's unstable release---which is what I am using). Are they needed?
Quoted 10 lines
Quoted 9 lines
Quoted 2 lines
Also what was the last kernel version on which the driver worked for you?
Unfortunately, I don't have any kernel for which this has worked for me. I just did an experiment: I plugged the adaptor on a ia32 notebook where a rt61pci works fine (it is running Ubuntu's Hardy---well, actually, there are some problems, but I can get to that latter), but the USB key was non working with the symptoms that I described above.
Quoted 3 lines
That is most unfortunate, since register dumps are usually most usefull when I can compare the actual register values between a working and non-working setup.
Ok. I will try to compile an 2.6.18 kernel with the out-of-tree modules. I hope that this can prove useful. I plan on getting register dumps (and I also hope that it will work; perhaps getting the register values with the legacy rt2500 drivers would help you, if they are available at all. I don't even know if they will work here, but I guess that I will give them a shot).
Quoted 4 lines
However I just realized I had a D-Link stick myself, and apparently I have the exact same model/type. I'll compile a 2.6.26-rc5 kernel and see if that stick works for me, if so, I have the working register dump. And if not, then we can rule out endian problems.
Thank you so much.
I will compile other versions of the kernel just to see if I can see the status of the driver with other versions of kernels/drivers. Since I just installed a cross-compiler yesterday night on a *much* faster machine, I don't have to wait more than 1 hour for each kernel modification that I make (this iBook is slow).
As I said earlier, I plan on doing whatever test you want me to.
Thanks, Rogério Brito.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.orgHi again, Ivo.
Quoted 5 lines · Rogério Brito
Quoted 4 lines · Ivo van Doorn
However I just realized I had a D-Link stick myself, and apparently I have the exact same model/type. I'll compile a 2.6.26-rc5 kernel and see if that stick works for me, if so, I have the working register dump. And if not, then we can rule out endian problems.
I just observed one thing: with a 2.6.26-rc5 kernel, I always get "Access Point: Not-Associated" with that script that I sent you earlier. On the other hand, with 2.6.26-rc4, I can actually associate to the AP (i.e., I see its MAC address).
I may have changed some parameters for the kernel compilation between the two of them. I will see if I can reproduce the problem with the same .config file for the kernel.
Thanks, Rogério Brito.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.orgHi, yet again, Ivo.
Quoted 5 lines · Ivo van Doorn
Quoted 5 lines
Unfortunately, I don't have any kernel for which this has worked for me. I just did an experiment: I plugged the adaptor on a ia32 notebook where a rt61pci works fine (it is running Ubuntu's Hardy---well, actually, there are some problems, but I can get to that latter), but the USB key was non working with the symptoms that I described above.
Correction here: I just went to the ia32 notebook again and, now, running Ubuntu's hardy kernel (which is a patched 2.6.24 kernel, AFAIK---yes, it is; just checked it) I could make the D-Link stick work fine.
Unfortunately, it seems that while Ubuntu has debugfs compiled, it doesn't have the rt2x00 debug information compiled in the standard kernel (I will see if they have any debug version of their kernel---this ia32 notebook is a Celeron 466MHz and it is also slow at compiling kernels, just as the iBook is and it is my parents' only machine).
Unfortunately, I can't get your script to run here, since I got:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
root@rbrito-laptop:~# LANG= bash Desktop/regdump.txt ls: cannot access /debug/ieee80211/phy*/rt[0-9]*/: No such file or directory root@rbrito-laptop:~# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Quoted 6 lines
That is most unfortunate, since register dumps are usually most usefull when I can compare the actual register values between a working and non-working setup. However I just realized I had a D-Link stick myself, and apparently I have the exact same model/type. I'll compile a 2.6.26-rc5 kernel and see if that stick works for me, if so, I have the working register dump. And if not, then we can rule out endian problems.
Well, I think that I was a bit hasty with my tests on ia32 and this Ubuntu notebook.
Here is, BTW, the output of iwconfig on this machine, where I could get the stick working:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
root@rbrito-laptop:~# iwconfig lo no wireless extensions.
wmaster0 no wireless extensions.
ra0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.437 GHz Access Point:
00:13:46:51:10:65
Bit Rate=2 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Link Quality=71/100 Signal level=-50 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
wmaster1 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"default"
Mode:Managed Frequency:2.437 GHz Access Point:
00:13:46:51:10:65
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX Link Quality=47/100 Signal level=-77 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
root@rbrito-laptop:~#
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Notice that the field "Link Quality" is quite lower with the USB stick.
As you may have already noticed, I really do want to get this straightened, so that I can use my iBook at work and will do many things to get this to work well (and to have your drivers better in the short term).
Thanks, Rogério Brito.
P.S.: This message was written with the USB stick and an SSH connection. :-)
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.orgHi, Ivo and John.
I don't know if you received my earlier message.
Quoted 3 lines · Rogério Brito
Correction here: I just went to the ia32 notebook again and, now, running Ubuntu's hardy kernel (which is a patched 2.6.24 kernel, AFAIK---yes, it is; just checked it) I could make the D-Link stick work fine.
The only problem that I had is that I had to reissue the command "iwconfig wlan0 ap any" or, otherwise, the connection with the AP would be dropped (I can get a log for you to peruse, if you wish).
Quoted 9 lines · Ivo van Doorn
Quoted 7 lines
That is most unfortunate, since register dumps are usually most usefull when I can compare the actual register values between a working and non-working setup. However I just realized I had a D-Link stick myself, and apparently I have the exact same model/type. I'll compile a 2.6.26-rc5 kernel and see if that stick works for me, if so, I have the working register dump. And if not, then we can rule out endian problems.
Oh, these endianness problems are a headache. I just fixed some in one small program in lame (the MP3 compressor), but in the end, I finally won. :-)
Anyway, did you have some time to check your D-Link stick? I am willing to test more things or other kernel trees, if that is helpful to the project.
Regards, Rogério Brito.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.orgQuoted 4 lines · Rogério Brito
Hi, Ivo and John.
I don't know if you received my earlier message.
Quoted 8 lines
Quoted 3 lines · Rogério Brito
Correction here: I just went to the ia32 notebook again and, now, running Ubuntu's hardy kernel (which is a patched 2.6.24 kernel, AFAIK---yes, it is; just checked it) I could make the D-Link stick work fine.
The only problem that I had is that I had to reissue the command "iwconfig wlan0 ap any" or, otherwise, the connection with the AP would be dropped (I can get a log for you to peruse, if you wish).
What does "iwconfig wlan0" show _before_ doing the "iwconfig wlan0 ap any"?
John
Signature · 2 lines
John W. Linville [email protected]
Hi,
Quoted 6 lines
Oh, these endianness problems are a headache. I just fixed some in one small program in lame (the MP3 compressor), but in the end, I finally won. :-)
Anyway, did you have some time to check your D-Link stick? I am willing to test more things or other kernel trees, if that is helpful to the project.
Kernel is compiling right now, I did attempt to test this earlier, but something has changed in the IDE/SATA drivers or something because I 2.6.26 no longer recognized my hard disk during boot which obviously makes booting quite complicated. ;)
Ivo
Hi, Ivo and John.
Quoted 4 lines · John W. Linville
Quoted 3 lines · Rogério Brito
I don't know if you received my earlier message.
On Jun 08 2008, Rogério Brito wrote:
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
Correction here: I just went to the ia32 notebook again and, now, running Ubuntu's hardy kernel (which is a patched 2.6.24 kernel, AFAIK---yes, it is; just checked it) I could make the D-Link stick work fine.
The only problem that I had is that I had to reissue the command "iwconfig wlan0 ap any" or, otherwise, the connection with the AP would be dropped (I can get a log for you to peruse, if you wish).
Let me be a bit more detailed here: when I connected the D-Link stick on the ia32 notebook with Ubuntu's 2.6.24 kernel, if I *didn't* issue the command "iwconfig wlan0 ap any" *periodically* (say, with
# while true; iwconfig wlan0 ap any; sleep 10; done ), then the connection would die: the dmesg logs would indicate that the AP lost connection with the stick.
By the way, I see this exactly same behaviour with the rt61pci driver on the same machine (with the only difference being that the interface name is ra0 instead of wlan0): I even put a cron job to issue the command every minute, so that my parents (which are using a PCMCIA card that uses the rt61pci) don't have to learn about the nasty things of networking.
Anyway, I would be happy to get the D-Link USB stick getting a lease from the AP as a first step. This way, I think that I could help you both much more than what I can now, and I would be a step closer into the direction of ditching MacOS X.
Quoted 1 line
What does "iwconfig wlan0" show _before_ doing the "iwconfig wlan0 ap any"?
Actually, it shows the output that I listed before in the mail that had the script "levanta.sh" attached (which was blocked by many people's e-mail servers): both interfaces up and configured with the same AP (but the ra0 one with the DHCP daemon disabled).
(In that message, I mentioned something along the lines: notice that the Signal Strength is reported to be higher on the ra0 interface than on the wlan0, despite both working on ia32).
Regards, Rogério Brito.
P.S.: Sorry for an e-mail not more detailed. I'm not with physical access to my parent's notebook.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.orgHi, Ivo.
Quoted 5 lines · Ivo van Doorn
Hi,
Quoted 3 lines
Oh, these endianness problems are a headache. I just fixed some in one small program in lame (the MP3 compressor), but in the end, I finally won. :-)
Just for the record, it is an ABX tool that I'm refactoring so that you can compare two songs (one original and one compressed) and choose (from a randomly chosen one) which is the original track. You might be surprised at how LAME works well with even very low bitrates.
The program wasn't working with big-endian arches, but I fixed that yesterday. :-)
Quoted 5 lines
Quoted 3 lines
Anyway, did you have some time to check your D-Link stick? I am willing to test more things or other kernel trees, if that is helpful to the project.
Kernel is compiling right now,
Nice. Thank you.
Quoted 4 lines
I did attempt to test this earlier, but something has changed in the IDE/SATA drivers or something because I 2.6.26 no longer recognized my hard disk during boot which obviously makes booting quite complicated. ;)
Obviously. :-) I'm waiting to get rid of MacOS X from this iBook. I still want it to be with me for quite some time.
Thank you very much, Rogério.
P.S.: If you want me to test anything else, like a git tree or something, please, don't hesitate to ask. I want the driver to work for me (of course) and to have it work better for all the people with ra wireless chips.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.orgQuoted 7 lines
Quoted 5 lines
Quoted 3 lines
Anyway, did you have some time to check your D-Link stick? I am willing to test more things or other kernel trees, if that is helpful to the project.
Kernel is compiling right now,
Nice. Thank you.
Unfortunately I haven't that much time to test it, and the allmodconfig kernel is still providing the same problems as my usual configuration. I am a bit closer at tracking this down, but I won't have another shot at this before the weekend :S
Ivo
Hi, Ivo.
I finally found a x86-64 (little-endian) where I could test the D-Link stick.
Quoted 3 lines · Ivo van Doorn
Unfortunately I haven't that much time to test it, and the allmodconfig kernel is still providing the same problems as my usual configuration.
Thanks quite unfortunate. For me, I can't make -rc5 associate with the AP, which is a regression regarding -rc4. With -rc4, on this x86-64 machine, at least I could associate and everything looked fine, but like with the iBook, I can't get a dhcp lease from the AP. :-(
(BTW, I think that I can do some sessions of "git bisect" to find which patch has modified this behavior).
I compiled the kernel with debugfs, like you instructed me and got a register dump of the kernel on this machine and looking at it, there seems to have some endianness things going on, but I am not qualified to say anything about this.
Quoted 2 lines
I am a bit closer at tracking this down, but I won't have another shot at this before the weekend :S
:-(
Well, I'm attaching the diff between the regdump from the earlier try on the iBook and the regdump from this x86-64. I think that some conclusions may be drawn from it, since it seems to be your domain of expertise.
Thanks, Rogério Brito.
P.S.: If John can say something that you would like me to try, I will do my best.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.orgregdump-x86-64.txt renamed from output-regdump.txt +72 -72
@@ -1,7 +1,7 @@ -2.6.26-rc5-2 +2.6.26-rc4-1 driver: rt2500usb version: 2.1.4 -compiled: Jun 8 2008 17:08:54 +compiled: Jun 13 2008 00:11:03 dev_flags: 0x00000e2f rt chip: 1201 rf chip: 0005
@@ -13,29 +13,29 @@ rf length: 5 csr -0 :0x00050000 -1 :0x00040000 -2 :0x13000000 -3 :0xe9460000 -4 :0x8a8d0000 -5 :0x13000000 -6 :0x51460000 -7 :0x65100000 -8 :0x09800000 -9 :0xff1d0000 -10 :0x00140000 -11 :0x000a0000 -12 :0x013a0000 -13 :0x11110000 -14 :0x1e110000 -15 :0x01ee0000 +0 :0x00000005 +1 :0x00000004 +2 :0x00001300 +3 :0x0000e946 +4 :0x00008a8d +5 :0x00001300 +6 :0x00005146 +7 :0x00006510 +8 :0x00000980 +9 :0x0000ff1d +10 :0x00000014 +11 :0x0000000a +12 :0x0000013a +13 :0x00001111 +14 :0x00001e11 +15 :0x000001ee 16 :0x00000000 -17 :0x01fe0000 -18 :0x005a0000 -19 :0xff000000 -20 :0x00020000 -21 :0x1e460000 -22 :0x00530000 +17 :0x000001fe +18 :0x0000005a +19 :0x0000ff00 +20 :0x00000002 +21 :0x00001e46 +22 :0x00000053 23 :0x00000000 24 :0x00000000 25 :0x00000000
@@ -45,28 +45,28 @@ 29 :0x00000000 30 :0x00000000 31 :0x00000000 -32 :0x1ec00000 -33 :0xb1620000 -34 :0x007e0000 -35 :0xb3af0000 -36 :0xb3aa0000 -37 :0x8c8d0000 -38 :0x8b8a0000 -39 :0x86870000 -40 :0x00850000 -41 :0x01620000 -42 :0x000a0000 +32 :0x00001ec0 +33 :0x0000b162 +34 :0x0000007e +35 :0x0000b3af +36 :0x0000b3aa +37 :0x00008c8d +38 :0x00008b8a +39 :0x00008687 +40 :0x00000085 +41 :0x00000162 +42 :0x0000000a 43 :0x00000000 -44 :0x140a0000 -45 :0x70380000 -46 :0x0c130000 -47 :0x06090000 -48 :0x03050000 -49 :0x02030000 -50 :0xfa000000 -51 :0x000b0000 -52 :0x00030000 -53 :0xe78f0000 +44 :0x0000140a +45 :0x00007038 +46 :0x00000c13 +47 :0x00000609 +48 :0x00000305 +49 :0x00000203 +50 :0x0000fa00 +51 :0x0000000b +52 :0x00000003 +53 :0x0000e78f 54 :0x00000000 55 :0x00000000 56 :0x00000000
@@ -109,38 +109,38 @@ 93 :0x00000000 94 :0x00000000 95 :0x00000000 -96 :0x12210000 -97 :0x00030000 +96 :0x00001221 +97 :0x00000003 98 :0x00000000 99 :0x00000000 -100 :0x000f0000 -101 :0x82060000 -102 :0x821e0000 -103 :0x91000000 +100 :0x0000000f +101 :0x00008206 +102 :0x0000821e +103 :0x00009100 104 :0x00000000 -105 :0x0e070000 -106 :0x54000000 +105 :0x00000e07 +106 :0x00005400 107 :0x00000000 108 :0x00000000 109 :0x00000000 110 :0x00000000 111 :0x00000000 -112 :0x032c0000 -113 :0xfb580000 -114 :0x63110000 -115 :0x0a1f0000 +112 :0x000000ad +113 :0x00009bcf +114 :0x0000186c +115 :0x000002e8 116 :0x00000000 117 :0x00000000 118 :0x00000000 119 :0x00000000 120 :0x00000000 121 :0x00000000 -122 :0x02e10000 +122 :0x0000009c 123 :0x00000000 124 :0x00000000 125 :0x00000000 126 :0x00000000 -127 :0x00000422 +127 :0x00000000 eeprom 0 :0x2570
@@ -199,7 +199,7 @@ bbp 0 :0x13 -1 :0x55 +1 :0x63 2 :0x06 3 :0x02 4 :0x19
@@ -211,7 +211,7 @@ 10 :0x00 11 :0x04 12 :0x01 -13 :0xa8 +13 :0x70 14 :0x1a 15 :0x30 16 :0xac
@@ -227,7 +227,7 @@ 26 :0x08 27 :0x23 28 :0x18 -29 :0x18 +29 :0x6e 30 :0x10 31 :0x2b 32 :0xb9
@@ -240,20 +240,20 @@ 39 :0xc4 40 :0x02 41 :0x60 -42 :0x09 -43 :0x34 -44 :0x0b -45 :0x6e -46 :0x70 +42 :0x0f +43 :0x0f +44 :0x16 +45 :0x65 +46 :0xeb 47 :0x0a 48 :0x04 -49 :0x02 -50 :0x68 -51 :0x18 -52 :0x04 +49 :0x03 +50 :0xf8 +51 :0x1d +52 :0x2e 53 :0x10 54 :0x18 -55 :0x2d +55 :0x7d 56 :0x08 57 :0x10 58 :0x08
Hi again, Ivo and John.
I have finally made the rt2x00 work on the x86-64 with the kernel 2.6.25.
Just as a reminder:
* with kernel 2.6.26-rc4, I could associate with the AP, but could not get a DHCP lease;
* with kernel 2.6.26-rc5, I could not even associate with the AP.
So, it seems that we have some regressions here. :-(
Quoted 4 lines
Well, I'm attaching the diff between the regdump from the earlier try on the iBook and the regdump from this x86-64. I think that some conclusions may be drawn from it, since it seems to be your domain of expertise.
I'm attaching here 3 files: the old output from regdump (taken from the ibook), the new, working (with kernel 2.6.25.4) regdump and their diff. Notice that there are some inverted values there, but they are shorts (i.e., 16-bit integers) that are inverted, instead of the inverted values being bytes.
I think that this may mean that your work may be easier on debugging the driver (I hope so!).
Thanks for any help, Rogério Brito.
Signature · 3 lines
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org2.6.26-rc5-2
driver: rt2500usb
version: 2.1.4
compiled: Jun 8 2008 17:08:54dev_flags: 0x00000e2f
rt chip: 1201
rf chip: 0005
revision:00000005
csr length: 128
eeprom length: 53
bbp length: 96
rf length: 5
csr
0 :0x00050000
1 :0x00040000
2 :0x13000000
3 :0xe9460000
4 :0x8a8d0000
5 :0x13000000
6 :0x51460000
7 :0x65100000
8 :0x09800000
9 :0xff1d0000
10 :0x00140000
11 :0x000a0000
12 :0x013a0000
13 :0x11110000
14 :0x1e110000
15 :0x01ee0000
16 :0x00000000
17 :0x01fe0000
18 :0x005a0000
19 :0xff000000
20 :0x00020000
21 :0x1e460000
22 :0x00530000
23 :0x00000000
24 :0x00000000
25 :0x00000000
26 :0x00000000
27 :0x00000000
28 :0x00000000
29 :0x00000000
30 :0x00000000
31 :0x00000000
32 :0x1ec00000
33 :0xb1620000
34 :0x007e0000
35 :0xb3af0000
36 :0xb3aa0000
37 :0x8c8d0000
38 :0x8b8a0000
39 :0x86870000
40 :0x00850000
41 :0x01620000
42 :0x000a0000
43 :0x00000000
44 :0x140a0000
45 :0x70380000
46 :0x0c130000
47 :0x06090000
48 :0x03050000
49 :0x02030000
50 :0xfa000000
51 :0x000b0000
52 :0x00030000
53 :0xe78f0000
54 :0x00000000
55 :0x00000000
56 :0x00000000
57 :0x00000000
58 :0x00000000
59 :0x00000000
60 :0x00000000
61 :0x00000000
62 :0x00000000
63 :0x00000000
64 :0x00000000
65 :0x00000000
66 :0x00000000
67 :0x00000000
68 :0x00000000
69 :0x00000000
70 :0x00000000
71 :0x00000000
72 :0x00000000
73 :0x00000000
74 :0x00000000
75 :0x00000000
76 :0x00000000
77 :0x00000000
78 :0x00000000
79 :0x00000000
80 :0x00000000
81 :0x00000000
82 :0x00000000
83 :0x00000000
84 :0x00000000
85 :0x00000000
86 :0x00000000
87 :0x00000000
88 :0x00000000
89 :0x00000000
90 :0x00000000
91 :0x00000000
92 :0x00000000
93 :0x00000000
94 :0x00000000
95 :0x00000000
96 :0x12210000
97 :0x00030000
98 :0x00000000
99 :0x00000000
100 :0x000f0000
101 :0x82060000
102 :0x821e0000
103 :0x91000000
104 :0x00000000
105 :0x0e070000
106 :0x54000000
107 :0x00000000
108 :0x00000000
109 :0x00000000
110 :0x00000000
111 :0x00000000
112 :0x032c0000
113 :0xfb580000
114 :0x63110000
115 :0x0a1f0000
116 :0x00000000
117 :0x00000000
118 :0x00000000
119 :0x00000000
120 :0x00000000
121 :0x00000000
122 :0x02e10000
123 :0x00000000
124 :0x00000000
125 :0x00000000
126 :0x00000000
127 :0x00000422
eeprom
0 :0x2570
1 :0x0104
2 :0x1300
3 :0xe946
4 :0x8a8d
5 :0xffff
6 :0xffff
7 :0xffff
8 :0xffff
9 :0xffff
10 :0xffff
11 :0x2829
12 :0xfff0
13 :0x00ff
14 :0x112c
15 :0x1518
16 :0x1618
17 :0x3e00
18 :0xffff
19 :0xffff
20 :0xffff
21 :0xffff
22 :0xffff
23 :0xffff
24 :0xffff
25 :0xffff
26 :0xffff
27 :0xffff
28 :0xffff
29 :0xffff
30 :0x1717
31 :0x1717
32 :0x1717
33 :0x1717
34 :0x1617
35 :0x1616
36 :0x1616
37 :0xffff
38 :0xffff
39 :0xffff
40 :0xffff
41 :0xffff
42 :0xffff
43 :0xffff
44 :0xffff
45 :0xffff
46 :0xffff
47 :0xffff
48 :0x0032
49 :0x6880
50 :0x3850
51 :0x6f5f
52 :0xfa00
bbp
0 :0x13
1 :0x55
2 :0x06
3 :0x02
4 :0x19
5 :0x0b
6 :0x10
7 :0x00
8 :0x00
9 :0x00
10 :0x00
11 :0x04
12 :0x01
13 :0xa8
14 :0x1a
15 :0x30
16 :0xac
17 :0x00
18 :0x18
19 :0xff
20 :0x1e
21 :0x18
22 :0x18
23 :0x08
24 :0x80
25 :0x50
26 :0x08
27 :0x23
28 :0x18
29 :0x18
30 :0x10
31 :0x2b
32 :0xb9
33 :0x55
34 :0x12
35 :0x50
36 :0x11
37 :0x05
38 :0x00
39 :0xc4
40 :0x02
41 :0x60
42 :0x09
43 :0x34
44 :0x0b
45 :0x6e
46 :0x70
47 :0x0a
48 :0x04
49 :0x02
50 :0x68
51 :0x18
52 :0x04
53 :0x10
54 :0x18
55 :0x2d
56 :0x08
57 :0x10
58 :0x08
59 :0x02
60 :0x3e
61 :0x5f
62 :0x00
63 :0x00
64 :0x01
65 :0x03
66 :0x00
67 :0x00
68 :0x00
69 :0x00
70 :0x46
71 :0x00
72 :0x00
73 :0x00
74 :0xd4
75 :0xff
76 :0x19
77 :0x05
78 :0x08
79 :0x00
80 :0x00
81 :0x05
82 :0x14
83 :0x50
84 :0xc0
85 :0x10
86 :0xcf
87 :0x00
88 :0x00
89 :0x00
90 :0x00
91 :0x00
92 :0x00
93 :0x00
94 :0x00
95 :0x00
rf
0 :0x00000000
1 :0x00022010
2 :0x000008a6
3 :0x00062d11
4 :0x00000e07
2.6.25.4-1
driver: rt2500usb
version: 2.0.14
compiled: Jun 13 2008 01:33:03dev_flags: 0x0001012f
rt chip: 1201
rf chip: 0005
revision:00000005
csr length: 128
eeprom length: 53
bbp length: 96
rf length: 5
csr
0 :0x00000005
1 :0x00000004
2 :0x00001300
3 :0x0000e946
4 :0x00008a8d
5 :0x00001300
6 :0x00005146
7 :0x00006510
8 :0x00000980
9 :0x0000ff1d
10 :0x00000014
11 :0x00000005
12 :0x0000016c
13 :0x00001111
14 :0x00001e11
15 :0x000001ee
16 :0x00000000
17 :0x000001fe
18 :0x0000005a
19 :0x0000ff00
20 :0x00000003
21 :0x00001e46
22 :0x00000053
23 :0x00000000
24 :0x00000000
25 :0x00000000
26 :0xffff0000
27 :0x00000000
28 :0x00000000
29 :0x00000000
30 :0x00000000
31 :0x00000000
32 :0x00001ec0
33 :0x0000b11a
34 :0x0000007e
35 :0x0000b3af
36 :0x0000b3aa
37 :0x00008c8d
38 :0x00008b8a
39 :0x00008687
40 :0x00000085
41 :0x00000162
42 :0x0000000e
43 :0x0000015f
44 :0x0000140a
45 :0x00007038
46 :0x00000c13
47 :0x00000609
48 :0x00000305
49 :0x00000203
50 :0x0000fa00
51 :0x00000003
52 :0x00000003
53 :0x0000e78f
54 :0x00000000
55 :0x00000000
56 :0x00000000
57 :0x00000000
58 :0x00000000
59 :0x00000000
60 :0x00000000
61 :0x00000000
62 :0x00000000
63 :0x00000000
64 :0x00000000
65 :0x00000000
66 :0x00000000
67 :0x00000000
68 :0x00000000
69 :0x00000000
70 :0x00000000
71 :0x00000000
72 :0x00000000
73 :0x00000000
74 :0x00000000
75 :0x00000000
76 :0x00000000
77 :0x00000000
78 :0x00000000
79 :0x00000000
80 :0x00000000
81 :0x00000000
82 :0x00000000
83 :0x00000000
84 :0x00000000
85 :0x00000000
86 :0x00000000
87 :0x00000000
88 :0x00000000
89 :0x00000000
90 :0x00000000
91 :0x00000000
92 :0x00000000
93 :0x00000000
94 :0x00000000
95 :0x00000000
96 :0x00001221
97 :0x00000003
98 :0x00000000
99 :0x00000000
100 :0x0000000f
101 :0x00008206
102 :0x0000821e
103 :0x00009160
104 :0x00000000
105 :0x00000e07
106 :0x00005400
107 :0x00000000
108 :0x00000000
109 :0x00000000
110 :0x00000000
111 :0x00000000
112 :0x00000000
113 :0x000001a9
114 :0x00000038
115 :0x00000000
116 :0x00000000
117 :0x00000000
118 :0x00000169
119 :0x00000011
120 :0x00000000
121 :0x00000000
122 :0x00000a01
123 :0x00000000
124 :0x00000000
125 :0x00000000
126 :0x00000000
127 :0x00000000
eeprom
0 :0x2570
1 :0x0104
2 :0x1300
3 :0xe946
4 :0x8a8d
5 :0xffff
6 :0xffff
7 :0xffff
8 :0xffff
9 :0xffff
10 :0xffff
11 :0x2829
12 :0xfff0
13 :0x00ff
14 :0x112c
15 :0x1518
16 :0x1618
17 :0x3e00
18 :0xffff
19 :0xffff
20 :0xffff
21 :0xffff
22 :0xffff
23 :0xffff
24 :0xffff
25 :0xffff
26 :0xffff
27 :0xffff
28 :0xffff
29 :0xffff
30 :0x1717
31 :0x1717
32 :0x1717
33 :0x1717
34 :0x1617
35 :0x1616
36 :0x1616
37 :0xffff
38 :0xffff
39 :0xffff
40 :0xffff
41 :0xffff
42 :0xffff
43 :0xffff
44 :0xffff
45 :0xffff
46 :0xffff
47 :0xffff
48 :0x0032
49 :0x6880
50 :0x3850
51 :0x6f5f
52 :0xff37
bbp
0 :0x13
1 :0x45
2 :0x1e
3 :0x02
4 :0x19
5 :0x09
6 :0x00
7 :0x0e
8 :0x00
9 :0x00
10 :0x00
11 :0x04
12 :0x00
13 :0x70
14 :0x1a
15 :0x30
16 :0xac
17 :0x60
18 :0x18
19 :0xff
20 :0x1e
21 :0x18
22 :0x18
23 :0x08
24 :0x68
25 :0x38
26 :0x08
27 :0x23
28 :0x18
29 :0x18
30 :0x10
31 :0x2b
32 :0xb9
33 :0x55
34 :0x12
35 :0x50
36 :0x11
37 :0x05
38 :0x00
39 :0xc4
40 :0x02
41 :0x60
42 :0x08
43 :0x01
44 :0x78
45 :0x00
46 :0x38
47 :0x0a
48 :0x04
49 :0x02
50 :0x68
51 :0x56
52 :0x2e
53 :0x10
54 :0x18
55 :0x7b
56 :0x08
57 :0x10
58 :0x08
59 :0x02
60 :0x3f
61 :0x6f
62 :0x00
63 :0x00
64 :0x01
65 :0x03
66 :0x00
67 :0x00
68 :0x00
69 :0x00
70 :0x46
71 :0x00
72 :0x00
73 :0x00
74 :0xd4
75 :0xff
76 :0x19
77 :0x05
78 :0x08
79 :0x00
80 :0x00
81 :0x05
82 :0x14
83 :0x50
84 :0xc0
85 :0x10
86 :0x74
87 :0x04
88 :0x00
89 :0x00
90 :0x00
91 :0x00
92 :0x00
93 :0x00
94 :0x00
95 :0x00
rf
0 :0x00000000
1 :0x00022010
2 :0x000008a6
3 :0x00063711
4 :0x00000e07
new.output-regdump.txt renamed from old.output-regdump.txt +89 -89
@@ -1,8 +1,8 @@ -2.6.26-rc5-2 +2.6.25.4-1 driver: rt2500usb -version: 2.1.4 -compiled: Jun 8 2008 17:08:54 -dev_flags: 0x00000e2f +version: 2.0.14 +compiled: Jun 13 2008 01:33:03 +dev_flags: 0x0001012f rt chip: 1201 rf chip: 0005 revision:00000005
@@ -13,60 +13,60 @@ rf length: 5 csr -0 :0x00050000 -1 :0x00040000 -2 :0x13000000 -3 :0xe9460000 -4 :0x8a8d0000 -5 :0x13000000 -6 :0x51460000 -7 :0x65100000 -8 :0x09800000 -9 :0xff1d0000 -10 :0x00140000 -11 :0x000a0000 -12 :0x013a0000 -13 :0x11110000 -14 :0x1e110000 -15 :0x01ee0000 +0 :0x00000005 +1 :0x00000004 +2 :0x00001300 +3 :0x0000e946 +4 :0x00008a8d +5 :0x00001300 +6 :0x00005146 +7 :0x00006510 +8 :0x00000980 +9 :0x0000ff1d +10 :0x00000014 +11 :0x00000005 +12 :0x0000016c +13 :0x00001111 +14 :0x00001e11 +15 :0x000001ee 16 :0x00000000 -17 :0x01fe0000 -18 :0x005a0000 -19 :0xff000000 -20 :0x00020000 -21 :0x1e460000 -22 :0x00530000 +17 :0x000001fe +18 :0x0000005a +19 :0x0000ff00 +20 :0x00000003 +21 :0x00001e46 +22 :0x00000053 23 :0x00000000 24 :0x00000000 25 :0x00000000 -26 :0x00000000 +26 :0xffff0000 27 :0x00000000 28 :0x00000000 29 :0x00000000 30 :0x00000000 31 :0x00000000 -32 :0x1ec00000 -33 :0xb1620000 -34 :0x007e0000 -35 :0xb3af0000 -36 :0xb3aa0000 -37 :0x8c8d0000 -38 :0x8b8a0000 -39 :0x86870000 -40 :0x00850000 -41 :0x01620000 -42 :0x000a0000 -43 :0x00000000 -44 :0x140a0000 -45 :0x70380000 -46 :0x0c130000 -47 :0x06090000 -48 :0x03050000 -49 :0x02030000 -50 :0xfa000000 -51 :0x000b0000 -52 :0x00030000 -53 :0xe78f0000 +32 :0x00001ec0 +33 :0x0000b11a +34 :0x0000007e +35 :0x0000b3af +36 :0x0000b3aa +37 :0x00008c8d +38 :0x00008b8a +39 :0x00008687 +40 :0x00000085 +41 :0x00000162 +42 :0x0000000e +43 :0x0000015f +44 :0x0000140a +45 :0x00007038 +46 :0x00000c13 +47 :0x00000609 +48 :0x00000305 +49 :0x00000203 +50 :0x0000fa00 +51 :0x00000003 +52 :0x00000003 +53 :0x0000e78f 54 :0x00000000 55 :0x00000000 56 :0x00000000
@@ -109,38 +109,38 @@ 93 :0x00000000 94 :0x00000000 95 :0x00000000 -96 :0x12210000 -97 :0x00030000 +96 :0x00001221 +97 :0x00000003 98 :0x00000000 99 :0x00000000 -100 :0x000f0000 -101 :0x82060000 -102 :0x821e0000 -103 :0x91000000 +100 :0x0000000f +101 :0x00008206 +102 :0x0000821e +103 :0x00009160 104 :0x00000000 -105 :0x0e070000 -106 :0x54000000 +105 :0x00000e07 +106 :0x00005400 107 :0x00000000 108 :0x00000000 109 :0x00000000 110 :0x00000000 111 :0x00000000 -112 :0x032c0000 -113 :0xfb580000 -114 :0x63110000 -115 :0x0a1f0000 +112 :0x00000000 +113 :0x000001a9 +114 :0x00000038 +115 :0x00000000 116 :0x00000000 117 :0x00000000 -118 :0x00000000 -119 :0x00000000 +118 :0x00000169 +119 :0x00000011 120 :0x00000000 121 :0x00000000 -122 :0x02e10000 +122 :0x00000a01 123 :0x00000000 124 :0x00000000 125 :0x00000000 126 :0x00000000 -127 :0x00000422 +127 :0x00000000 eeprom 0 :0x2570
@@ -195,35 +195,35 @@ 49 :0x6880 50 :0x3850 51 :0x6f5f -52 :0xfa00 +52 :0xff37 bbp 0 :0x13 -1 :0x55 -2 :0x06 +1 :0x45 +2 :0x1e 3 :0x02 4 :0x19 -5 :0x0b -6 :0x10 -7 :0x00 +5 :0x09 +6 :0x00 +7 :0x0e 8 :0x00 9 :0x00 10 :0x00 11 :0x04 -12 :0x01 -13 :0xa8 +12 :0x00 +13 :0x70 14 :0x1a 15 :0x30 16 :0xac -17 :0x00 +17 :0x60 18 :0x18 19 :0xff 20 :0x1e 21 :0x18 22 :0x18 23 :0x08 -24 :0x80 -25 :0x50 +24 :0x68 +25 :0x38 26 :0x08 27 :0x23 28 :0x18
@@ -240,26 +240,26 @@ 39 :0xc4 40 :0x02 41 :0x60 -42 :0x09 -43 :0x34 -44 :0x0b -45 :0x6e -46 :0x70 +42 :0x08 +43 :0x01 +44 :0x78 +45 :0x00 +46 :0x38 47 :0x0a 48 :0x04 49 :0x02 50 :0x68 -51 :0x18 -52 :0x04 +51 :0x56 +52 :0x2e 53 :0x10 54 :0x18 -55 :0x2d +55 :0x7b 56 :0x08 57 :0x10 58 :0x08 59 :0x02 -60 :0x3e -61 :0x5f +60 :0x3f +61 :0x6f 62 :0x00 63 :0x00 64 :0x01
@@ -284,8 +284,8 @@ 83 :0x50 84 :0xc0 85 :0x10 -86 :0xcf -87 :0x00 +86 :0x74 +87 :0x04 88 :0x00 89 :0x00 90 :0x00
@@ -299,5 +299,5 @@ 0 :0x00000000 1 :0x00022010 2 :0x000008a6 -3 :0x00062d11 +3 :0x00063711 4 :0x00000e07