From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Stanislaw Gruszka <sgruszka@redhat.com>
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: Wed, 04 Jan 2012 02:22:28 +0100 [thread overview]
Message-ID: <1325640148.3359.142.camel@fermat.scientia.net> (raw)
In-Reply-To: <20120103105107.GB3391@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
On Tue, 2012-01-03 at 11:51 +0100, Stanislaw Gruszka wrote:
> Hmm, on my experience, software sucks much more than hardware, but we
> never can exclude hardware problem. I'm not sure if there are divergence
> between iwl4965 chipsets. Also I'm not sure if there are more than one
> chipsets revision at all.
Me neither unfortunately...
> 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).
> 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.
> Does adapter sits
> tight in the mini PCIe slot?
yep
> No, that's not needed if there are no good logs for compare. If possible
> try on some very old kernel, first kernel with iwl4965 support was 2.6.24.
I'll have a look...
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5677 bytes --]
next prev parent reply other threads:[~2012-01-04 1:22 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 ` 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 [this message]
2012-01-05 10:14 ` Stanislaw Gruszka
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=1325640148.3359.142.camel@fermat.scientia.net \
--to=calestyo@scientia.net \
--cc=Gregory.Dietsche@cuw.edu \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.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
Powered by JetHome