Re: RT5390 not working with rt2800pci

[Anisse Astier <anisse@astier.eu>]

On Mon, 16 Apr 2012 20:11:45 +1000, Julian Calaby <julian.calaby@gmail.com> wrote :

> Hi Anisse
> 
[...]
> >> > Ok, so let's look at this a bit closer: the "iw info" diff you
> >> > provided before makes me think that there is some form of regulatory
> >> > setting difference between the working and non-working cards. I would
> >> > guess that this would be visible in the dmesg output, could you boot
> >> > with a working card, save the dmesg, then boot with a non-working
> >> > card, save the dmesg, diff them and reply with that diff? I'm guessing
> >> > that there would be some lines in there about CRDA or regulatory which
> >> > would be different.
> >> I don't think this is related, but I'll try to provide the two dmesg,
> >> with today's wireless-next.
> > Full dmesgs are in attachment. I booted both machines with module
> > rt2800pci blacklisted, and then loaded it manually with modprobe, so the
> > interesting parts should be at the end.
> 
> Thanks for the dmesgs, however it's kinda annoying that there's no
> real differences between them.
> 
> >> This might be polluted by the fact that the "working" card succeded in
> >> connecting(on channel 6), which then changed the regulatory domain. I'll
> >> try to get unpolluted results.
> 
> You shouldn't be having any regulatory issues connecting to an AP on
> channel 6. In general, it's channels above 11 (I think) that are
> occasionally masked by different regulatory settings.
> 
> > Almost. The cause was that passive scanning brought a beacon on channel
> > 13, and this beacon caused regulatory domain change:
> >
> > --- 1604-dmesg-NOWORKI-truncated        2012-04-16 10:26:03.000000000 +0200
> > +++ 1604-dmesg-WORKI-truncated  2012-04-16 10:26:04.000000000 +0200
> > @@ -45,4 +45,6 @@
> >  phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 3, TXop: 0.
> >  phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 7, TXop: 0.
> >  ADDRCONF(NETDEV_UP): wlan0: link is not ready
> > +cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0
> > +cfg80211: Pending regulatory request, waiting for it to be processed...
> >  EXT3-fs (sda5): using internal journal
> 
> Not quite, it seems that CRDA never got sent the request, which is
> odd, however this is on the working card so it doesn't explain the
> non-working ones.
> 
> >> > Also, what channel is your AP on and what region of the world are you
> >> > in? (I'm guessing Europe from your email address, but which country
> >> > specifically)
> >> I'm in France, but using another wireless card, I can scan APs on
> >> channels 1,2,3,6,8,10,11,13.
> 
> That sounds right.
> 
> I'm at a loss to explain it any further, which is annoying. At this
> point, I'm guessing that there's some subtle hardware difference, or
> something like that. It could be something as complicated as incorrect
> or broken components, or something as simple as a dry solder join on
> the antenna connection.
> 
> Where did you get the cards?
I got them inside netbooks we bought from our provider in China. Is that
really relevant? They're on the market anyway.

I can provide a photo of the chip if anyone is interested (I posted the
markings in the first message of the discussion).

> 
> Does anyone else who's more knowledgeable than me have any idea what's
> happening here?
> 
> Thanks,
>