On Tue, 2012-03-20 at 21:16 +0200, Anastas Giokov wrote:
> > On Tue, 2009-04-28 at 09:42 -0700, Howard Chu wrote:
> > > Dan Williams wrote:
> > > > On Fri, 2009-04-24 at 15:18 -0700, Howard Chu wrote:
> > > >> Dan Williams wrote:
> > > >>> On Mon, 2009-04-20 at 15:37 -0700, Howard Chu wrote:
> > >
On Tue, 2009-04-28 at 09:42 -0700, Howard Chu wrote:
>/Dan Williams wrote:/
>/> On Fri, 2009-04-24 at 15:18 -0700, Howard Chu wrote:/
>/>> Dan Williams wrote:/
>/>>> On Mon, 2009-04-20 at 15:37 -0700, Howard Chu wrote:/
>/ Howard Chu wrote:/
>/> This is probably more related to the ath9k d
On Tue, 2009-04-28 at 09:42 -0700, Howard Chu wrote:
> Dan Williams wrote:
> > On Fri, 2009-04-24 at 15:18 -0700, Howard Chu wrote:
> >> Dan Williams wrote:
> >>> On Mon, 2009-04-20 at 15:37 -0700, Howard Chu wrote:
> Howard Chu wrote:
> > This is probably more related
Dan Williams wrote:
On Fri, 2009-04-24 at 15:18 -0700, Howard Chu wrote:
Dan Williams wrote:
On Mon, 2009-04-20 at 15:37 -0700, Howard Chu wrote:
Howard Chu wrote:
This is probably more related to the ath9k driver, but I wanted to start here
in case anyone is familiar wit
On Fri, 2009-04-24 at 15:18 -0700, Howard Chu wrote:
> Dan Williams wrote:
> > On Mon, 2009-04-20 at 15:37 -0700, Howard Chu wrote:
> >> Howard Chu wrote:
> >>> This is probably more related to the ath9k driver, but I wanted to start
> >>> here
> >>> in case anyone is familiar
Dan Williams wrote:
On Mon, 2009-04-20 at 15:37 -0700, Howard Chu wrote:
Howard Chu wrote:
This is probably more related to the ath9k driver, but I wanted to start here
in case anyone is familiar with it. I've been seeing this for the past couple
months, and I just now rebuilt NM fresh from git
On Mon, 2009-04-20 at 15:37 -0700, Howard Chu wrote:
> Howard Chu wrote:
> > This is probably more related to the ath9k driver, but I wanted to start
> > here
> > in case anyone is familiar with it. I've been seeing this for the past
> > couple
> > months, and I just now rebuilt NM fresh from git
Alexander Sack wrote:
On Mon, Apr 20, 2009 at 06:24:33PM -0700, Howard Chu wrote:
Since killing NM prevents the problem from showing up, I don't see how
this can be a wpa_supplicant bug. ?? Should I add another comment to the
bug report?
To verify that its really the scan making your driver
Alexander Sack wrote:
On Mon, Apr 20, 2009 at 03:37:20PM -0700, Howard Chu wrote:
Howard Chu wrote:
This is probably more related to the ath9k driver, but I wanted to start here
in case anyone is familiar with it. I've been seeing this for the past couple
months, and I just now rebuilt NM fresh
On Mon, Apr 20, 2009 at 03:37:20PM -0700, Howard Chu wrote:
> Howard Chu wrote:
>> This is probably more related to the ath9k driver, but I wanted to start here
>> in case anyone is familiar with it. I've been seeing this for the past couple
>> months, and I just now rebuilt NM fresh from git and i
Howard Chu wrote:
This is probably more related to the ath9k driver, but I wanted to start here
in case anyone is familiar with it. I've been seeing this for the past couple
months, and I just now rebuilt NM fresh from git and it's still happening:
I seem to have ruled out the driver; doing a k
11 matches
Mail list logo
