Hi, Ivo.

First of all, thank you so much for helping with this issue. It is
greatly appreciated.

On Jun 08 2008, Ivo van Doorn wrote:
quoted text
> Hi,
> 
> > 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 text
> > > 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 text
> > > * 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? :-)
> > 
> > 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?

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 text
> 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 text
> 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?

I just grabbed the script. Here is the output with the options enabled
and the results are attached here.

quoted text
> 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