On Wed, Apr 25, 2012 at 09:23, Sedat Dilek <sedat.dilek@xxxxxxxxxxxxxx> wrote: > On Tue, Apr 24, 2012 at 5:34 PM, Emmanuel Grumbach <egrumbach@xxxxxxxxx> wrote: >> On Tue, Apr 24, 2012 at 15:45, Sedat Dilek <sedat.dilek@xxxxxxxxxxxxxx> wrote: >>> On Tue, Apr 24, 2012 at 2:29 PM, Dominik Feser >>> <dominik.feser@xxxxxxxxxxxxxx> wrote: >>>> What does that mean? >>>> >>> >>> Pickup the patch from [2], apply it against a recent compat-wireless >>> version, build and test. >>> Report here again. >>> >> >> Pretty sure it won't help. True, we were trying to request the wrong >> fw, but then we requested (and got) the good one, so that the only >> effect was that load time was longer that it could be. But here, we >> can't even get anything working. And the prints don't made it to >> kernel log properly >> > > Originally I answered Pat as he asked what's the status with the patch > concerning the firmware-issue. > So, my post was about applying this one (so I understood the open question). > I didn't care about the original concern of the reporter. > BTW, the mentioned patch is now in wireless.git (master-2012-04-24-2). fair enough :-) > > Currently, I have an issue myself on iwlwifi (6230) with Ubuntu > precise, but it looks like a bug in network-manager with 3.4-rc4+ (see > [1]). > > - Sedat - > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=785772 > Thanks for that pointer. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
