From: Inaky Perez-Gonzalez <firstname.lastname@example.org>
To: Dan Williams <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>,
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card
Date: Wed, 28 Jul 2010 13:21:43 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Wed, 2010-07-28 at 14:14 -0700, Dan Williams wrote:
> > ...
> > kernel: iwlagn 0000:02:00.0: RF_KILL bit toggled to enable radio.
> > NetworkManager: <info> WiFi now disabled by radio killswitch
> > kernel: i2400m_usb 2-1.3:1.0: 'RF Control' (0x4602) command failed: -84 - invalid state (3)
> > NetworkManager: <info> (wlan0): bringing up device.
> > kernel: iwlagn 0000:02:00.0: Microcode SW error detected. Restarting
> > ...
> > I say seemingly because I don't remember NetworkManager actually doing
> > that on WiMAX devices, but I could be wrong, as they expose an RFKILL
> > interface.
> NM doesn't do anything yet with wimax devices, though it'll look for
> wimax killswitches. But nothing is done with them yet upstream.
> So I guess my question here is whether Alexey is using a stock NM or a
> distro-patched one. Ubuntu used to patch NM to actually poke the rfkill
> bits, not sure if they still do that or not. Fedora does not, and I
> don't think Novell/SUSE does either.
Thanks for the clarification Dan, that eliminates a variable :)
next prev parent reply other threads:[~2010-07-28 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
2010-07-27 22:38 ` [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card Inaky Perez-Gonzalez
2010-07-28 0:04 ` Guy, Wey-Yi
2010-07-28 17:53 ` Alexey Shvetsov
2010-07-28 18:09 ` Inaky Perez-Gonzalez
2010-07-28 18:23 ` Inaky Perez-Gonzalez
2010-07-28 21:14 ` Dan Williams
2010-07-28 20:21 ` Inaky Perez-Gonzalez [this message]
2010-07-30 14:48 ` Alexey Shvetsov
2010-08-04 16:36 ` Inaky Perez-Gonzalez
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).