public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Rogério Brito" <rbrito@ime.usp.br>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Still some problems with the rt2x00 driver
Date: Tue, 25 Nov 2008 09:42:09 +0100	[thread overview]
Message-ID: <200811250942.09259.IvDoorn@gmail.com> (raw)
In-Reply-To: <3977BB08-9149-41E4-B187-235F36204E4E@ime.usp.br>

Hi,

> There are two strange things that I've noticed, though and that I  
> feel need to be fixed:

For both cases:
Is there anything in the log regading the drivers or mac80211?

Ivo

> 1 - the rt63 driver used by a PCMCIA card DWL-G630 model has, for  
> many kernels (from 2.6.24 and up to and including kernel 2.6.27, as  
> shipped by Ubuntu for ia32), shown a strange behavior: after  
> everything is working correctly, the network simply becomes  
> unavailable, with the gnome network monitor showing that the card has  
> no signal. If I issue the command "iwconfig ra0 ap any", for example,  
> the card starts working again.
> 
> (Actually, I put this on a cron job to be executed every minute, but  
> even then, there are time windows where the card is not working). I'm  
> not in front of the notebook (a very old Armada V300 that my parents  
> are using for production), so I don't know if the card looses  
> association with the Access Point or not. I can check that, if nobody  
> else reported this problem yet.
> 
> 2 - the rt2500usb driver that I use on a very old iBook G3 (powerpc)  
> also works fine and has a similar, but not identical behaviour: the  
> DWL-G122 USB stick that I have works fine once associated and when it  
> is transferring data. Once I leave the network unused for, say, 2  
> minutes, the connection with the AP is dropped. Here, also, issuing  
> "iwconfig wlan0 ap any" makes it work again.
> 
> Notice the difference in both cases: with the PCMCIA/ia32 case, no  
> matter if there is traffic on the network or not, the the connection  
> is interrupted. With the USB/powerpc case, if there is traffic, the  
> connection remains working fine.
> 
> > Note that I am not going to push it to 2.6.26 since I don't know if  
> > the
> > patch will cause problems in other parts of the driver.
> 
> There's no problem. I can compile vanilla kernels from kernel.org  
> without any problems.
> 
> 
> Thanks for your kind help, Rogério Brito.
> 



  reply	other threads:[~2008-11-25  8:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20 17:57 [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd) Rogério Brito
2008-06-20 18:48 ` Ivo van Doorn
2008-06-20 19:58   ` Rogério Brito
2008-06-25 19:49     ` Rogério Brito
2008-06-29 18:51       ` Ivo van Doorn
2008-07-08  3:55         ` Rogério Brito
2008-07-08 13:58           ` Ivo van Doorn
2008-07-13  0:20             ` Rogério Brito
2008-08-04 13:26       ` Ivo van Doorn
2008-08-07 17:01         ` [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc Rogério Brito
2008-11-25  3:19         ` Still some problems with the rt2x00 driver Rogério Brito
2008-11-25  8:42           ` Ivo van Doorn [this message]
2008-12-02  1:56             ` Rogério Brito
2008-12-02  2:00               ` Rogério Brito

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200811250942.09259.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rbrito@ime.usp.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox