From: Valdis.Kletnieks@vt.edu
To: Zhu Yi <yi.zhu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"John W. Linville" <linville@tuxdriver.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: mmotm 2009-10-09-01-07 - iwl3945 fails to do firmware load request
Date: Sat, 10 Oct 2009 01:22:24 -0400 [thread overview]
Message-ID: <252795.1255152144@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 10 Oct 2009 08:42:35 +0800." <1255135355.3719.22.camel@debian>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
On Sat, 10 Oct 2009 08:42:35 +0800, Zhu Yi said:
> The firmware loading happens when the user space brings the interface
> up. Can you check NM is running for the bad case?
I'm not using NM, because I've never figured out how to get it to DTRT for
my network config, so I run wpa_supplicant directly. It's looking like
a bad update to dbus was the actual root cause.
(Did I mention how I loath dbus? Or at least the fact that if it breaks,
everything from wireless to pulseaudio immediately craps out too. That and
'hald' are my two favorite "only on this laptop because stuff refuses to
work without them"....)
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2009-10-10 5:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200910090830.n998Ubvv020464@imap1.linux-foundation.org>
2009-10-09 22:47 ` mmotm 2009-10-09-01-07 uploaded (b43) Randy Dunlap
2009-10-10 3:55 ` Larry Finger
2009-10-10 0:12 ` mmotm 2009-10-09-01-07 - iwl3945 fails to do firmware load request Valdis.Kletnieks
2009-10-10 0:42 ` Zhu Yi
2009-10-10 5:22 ` Valdis.Kletnieks [this message]
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=252795.1255152144@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=yi.zhu@intel.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).