linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	Greg Dietsche <Gregory.Dietsche@cuw.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: iwl4965: "MAC is in deep sleep!" freezes
Date: Thu, 5 Jan 2012 11:14:13 +0100	[thread overview]
Message-ID: <20120105101412.GB2103@redhat.com> (raw)
In-Reply-To: <1325640148.3359.142.camel@fermat.scientia.net>

On Wed, Jan 04, 2012 at 02:22:28AM +0100, Christoph Anton Mitterer wrote:
> > Christoph, you mentioned that you replaced you 
> > motherboard. Did the problem start to happen after that?
> Yep,... the old board broke (and the system didn't bot anymore at
> all)... it was replaced with a new one by the manufacturer... and
> starting with that (with no software change on the disk in the meantime)
> the wifi didn't work anymore (as described).
Hmm, perhaps iwl4965 device does not work well with the new PCIe chipset.

Does any of fallowing workaround the problem?

kernel boot parameter:
pcie_aspm=off
pci_aspm=force
pci=nocrs
pci=use_crs

iwlegacy module parameter:
bt_coex_active=0

iwl4965 module parameters
11n_disable=1

> > Did you
> > correctly connect antennas cables to adapter.
> yep... at first (when they sent it back to me) it was not connected at
> all... I connected it... the problem persists in both states, connected
> and unconnected.
There should be 3 or 2 antennas: 1 - white, 3 - grey, 2 - black,
connection on adapter should match cable color (ok, I don't know if
it does any difference, but it worth to try). If there is only one
antenna available, perhaps there is somewhere another miniPCIe slot
where are more antenna cables available. But, if there is really
only one antenna cable, it should be connected to number 1 (white)
adapter connector.

Stanislaw


  reply	other threads:[~2012-01-05 10:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bbdbd01d4965ae789384bc1f9d0a2426@imap.dd24.net>
2011-09-02 23:38 ` iwl4965: "MAC is in deep sleep!" freezes Jonathan Nieder
2011-09-03 12:45   ` Christoph Anton Mitterer
2011-09-05  9:24     ` Stanislaw Gruszka
2011-09-05  9:19   ` Stanislaw Gruszka
2011-09-05  9:42     ` Christoph Anton Mitterer
2011-09-08  8:49       ` Stanislaw Gruszka
2011-09-08 16:19         ` Stanislaw Gruszka
2011-09-24 16:50           ` Stanislaw Gruszka
2011-11-14  0:02         ` Christoph Anton Mitterer
2011-11-14  1:46           ` Jonathan Nieder
2011-11-16 18:08             ` Christoph Anton Mitterer
2011-11-18  7:45               ` Stanislaw Gruszka
2011-12-29 15:17                 ` Christoph Anton Mitterer
2011-12-29 20:11                   ` Jonathan Nieder
2012-01-03 10:51                     ` Stanislaw Gruszka
2012-01-04  1:22                       ` Christoph Anton Mitterer
2012-01-05 10:14                         ` Stanislaw Gruszka [this message]
2012-01-16 22:08                           ` Christoph Anton Mitterer

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=20120105101412.GB2103@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=Gregory.Dietsche@cuw.edu \
    --cc=calestyo@scientia.net \
    --cc=jrnieder@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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;
as well as URLs for NNTP newsgroup(s).