Yes, the one I have is a TP-Link model. I was getting total pc
freezes as per the original issue. I added the changes you suggested
and compiled the kernel and modules for 3.0.9. It now works without
issue.
If you have other questions please ask away.
Malcolm Haak
On Tue, Dec 27, 2011 at 2:43 P
Do you have an AR9227 (ie a PCI version of an AR9287) ?
Adrian
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>Oh wait. I wonder if this would be a side-effect of "PCI MAC and SMP
>is painful".
>
>Try editing drivers/net/wireless/ath/ath9k/hw.c:__ath9k_hw_init():
>
>if (ah->config.serialize_regmode == SER_REG_MODE_AUTO) {
>if (ah->hw_version.macVersion == AR_SREV_VERSION_5416_PCI ||
Oh wait. I wonder if this would be a side-effect of "PCI MAC and SMP
is painful".
Try editing drivers/net/wireless/ath/ath9k/hw.c:__ath9k_hw_init():
if (ah->config.serialize_regmode == SER_REG_MODE_AUTO) {
if (ah->hw_version.macVersion == AR_SREV_VERSION_5416_PCI ||
On Thu, Oct 13, 2011 at 9:32 PM, Philipp Raich wrote:
> On Thu, Oct 13, 2011 at 7:04 PM, Ben Greear wrote:
>> On 10/13/2011 09:26 AM, Philipp Raich wrote:
>>>
>>> On Wed, Oct 12, 2011 at 9:35 PM, Ben Greear
>>> wrote:
Or can you put your existing NIC into a different computer
and
On 14 October 2011 18:23, Philipp Raich wrote:
> Apparently you are right, ar9227 is PCI and ar9287 is PCIe, according to a
> page related to "athn" in openBSD... GRR, just why do manufacturers have to
> be so close-fisted with their info on wireless adapters, it took me hours to
> find this info
On 10/14/2011 03:23 AM, Adrian Chadd wrote:
Right, I must've missed that. Then you have an AR9227, not an AR9287. :-)
At this point I'm tempted to say "Try PCBsd 9.0 Beta3" (freebsd +
desktop environment) - I believe the DVD image comes with a live
system, so you can test things out. The ath/hal
Right, I must've missed that. Then you have an AR9227, not an AR9287. :-)
At this point I'm tempted to say "Try PCBsd 9.0 Beta3" (freebsd +
desktop environment) - I believe the DVD image comes with a live
system, so you can test things out. The ath/hal driver code is
included by default in their s
On Thu, Oct 13, 2011 at 7:04 PM, Ben Greear wrote:
> On 10/13/2011 09:26 AM, Philipp Raich wrote:
>>
>> On Wed, Oct 12, 2011 at 9:35 PM, Ben Greear
>> wrote:
>>>
>>> On 10/12/2011 12:19 PM, Philipp Raich wrote:
Sadly, the provided patch did not help (I applied it to to the
compat-w
On 10/13/2011 09:26 AM, Philipp Raich wrote:
> On Wed, Oct 12, 2011 at 9:35 PM, Ben Greear wrote:
>> On 10/12/2011 12:19 PM, Philipp Raich wrote:
>>>
>>> Sadly, the provided patch did not help (I applied it to to the
>>> compat-wireless tarball '2011-10-10', hopefully this was right). I did
>>> no
On Wed, Oct 12, 2011 at 9:35 PM, Ben Greear wrote:
> On 10/12/2011 12:19 PM, Philipp Raich wrote:
>>
>> Sadly, the provided patch did not help (I applied it to to the
>> compat-wireless tarball '2011-10-10', hopefully this was right). I did
>> not encounter any warnings so far.
>>
>> I just realiz
On Thu, Oct 13, 2011 at 2:44 AM, Adrian Chadd wrote:
> Hi Philipp,
>
> Can you please check:
>
> * whether you have power saving enabled or not;
> * whether your bios has APSM enabled or not;
> * whether your kernel is overriding it and enabling APSM.
>
> There have been bugs in the past (notably
Hi Philipp,
Can you please check:
* whether you have power saving enabled or not;
* whether your bios has APSM enabled or not;
* whether your kernel is overriding it and enabling APSM.
There have been bugs in the past (notably the AR9285) where random
crap like this would happen. It turns out th
[snip]
for what it's worth, this is exactly how I got my leg up. And Felix
knows, he was the poor guy who I pestered. On the upside, we found
quite a few annoying corner cases (noise floor handling, calibration
issues) whilst digging into my own issues, so it all worked out great
in the end.
Pete
On 10/12/2011 12:19 PM, Philipp Raich wrote:
> Sadly, the provided patch did not help (I applied it to to the
> compat-wireless tarball '2011-10-10', hopefully this was right). I did
> not encounter any warnings so far.
>
> I just realized, that cfg80211 is initialized with the country code
> for C
Al 12/10/11 18:01, En/na Peter Stuge ha escrit:
>
> I got nothing. I didn't even get told that I also wouldn't get
> anything unless I really bitched and moaned a lot.
Happened to me too, maybe I didn't ask the right questions.
I didn't really bitch & moan though, not a lot at least ;-)
Bye
--
On 2011-10-12 7:23 PM, Peter Stuge wrote:
>> Having detailed information about the inner workings of the
>> hardware is useless if you don't have a basic understanding of how
>> the driver works.
>
> The two obviously go very tightly together. The more information
> about both you have, the easi
Felix Fietkau wrote:
> If I understand the point you're trying to make here correctly, it
> sounds like complete BS to me. Let me get this straight: from Luis
> asking people not to refer to internal codenames of Atheros
> codebases you extrapolate that detailed technical discussion on the
> public
On 2011-10-12 5:35 PM, Peter Stuge wrote:
>> >> would you please stop complaining and provide some help ?
>> >
>> > It took me many months time to get an idea of the ath9k community,
>> > and I would have appreciated tremendously if someone had explained
>> > to me how things worked and wh
Adrian Chadd wrote:
> Oh, don't think it's a FreeBSD related thing.
Certainly didn't mean to say that. It just happens to be that fbsd is
the stuff around your code.
> It's likely more a "what people are comfortable doing" thing.
Yep.
> I think it's a difficult call for any company to offer f
Mohammed Shafi wrote:
> >> i accept that there may be few issues which may not be fixed.
> >
> > I know. I don't. I was actually shocked to meet this attitude when
> > coming into the ath9k community. I didn't think anyone would work on
> > open source without the desire to make it perfect. I was t
Oh, don't think it's a FreeBSD related thing. It's likely more a "what
people are comfortable doing" thing.
I think it's a difficult call for any company to offer free support to
open source users. To developers, sure, they're likely their own "clue
filter" and will (quickly enough) learn how/what
On Wed, Oct 12, 2011 at 8:26 PM, Peter Stuge wrote:
> Mohammed Shafi wrote:
>> > From experience I know that Atheros does not like to work with end
>> > users on debugging issues like this, even if end users happen to be
>> > competent. The prefered modus operandi is to attempt to reproduce
>> > i
Mohammed Shafi wrote:
> > From experience I know that Atheros does not like to work with end
> > users on debugging issues like this, even if end users happen to be
> > competent. The prefered modus operandi is to attempt to reproduce
> > issues internally, and if that is successful then some time
On Wed, Oct 12, 2011 at 7:23 PM, Peter Stuge wrote:
> Philipp Raich wrote:
>> I would really like to improve the situation for me and everyone
>> else, or at least help as much as I can, and I think I need a hint.
>
> From experience I know that Atheros does not like to work with end
> users on de
Philipp Raich wrote:
> I would really like to improve the situation for me and everyone
> else, or at least help as much as I can, and I think I need a hint.
>From experience I know that Atheros does not like to work with end
users on debugging issues like this, even if end users happen to be
comp
On Wed, Oct 12, 2011 at 12:08 AM, Philipp Raich wrote:
> Hi.
>
> When using the ath9k module my system freezes in less than a few minutes, and
> I'm not able to find out why. Could someone help me by telling me where to
> find useful information on where or why this happens? (Or should i begin t
Hi.
When using the ath9k module my system freezes in less than a few minutes, and
I'm not able to find out why. Could someone help me by telling me where to find
useful information on where or why this happens? (Or should i begin to insert
my own debugging-output in the code???)
The crashes al
28 matches
Mail list logo
