From: Mario Limonciello <mario_limonciello@dell.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Dell-laptop is not working without wireless
Date: Thu, 03 Sep 2009 11:42:35 -0500 [thread overview]
Message-ID: <4A9FF1FB.5090507@dell.com> (raw)
In-Reply-To: <20090903153215.E51F8526EA5@mailhub.coreip.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]
Hi Dmitry:
Dmitry Torokhov wrote:
> On Tue, Aug 18, 2009 at 01:10:49PM +0100, Matthew Garrett wrote:
>
>
> Admittedly I have not spend much time on it but it looks like my box
> _really_ wants wifi interface to be fully operational before
> dcsbas_smi_request() starts returning proper data. I wonder if iwl3945's
> rfkill support interferes somehow here...
>
> Maybe Mario (being a Dell guy) has an idea why this might be happening?
>
>
I'm on 2.6.31-rc8 or so. I can't actually reproduce this on a d630. I
get all of the rfkill devices populated.
$ rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
$ sudo rmmod iwl3945 iwlcore dell-laptop
$ rfkill list
$ sudo modprobe dell-laptop
$ rfkill list
3: dell-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
4: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
<hit the hardware killswitch>
$ rfkill list
3: dell-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
4: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
5: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
$ sudo modprobe iwl3945
$ rfkill list
3: dell-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
4: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
5: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
6: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
There *is* a problem here that the hardware killswitch status doesn't
get updated, but Matthew is aware of that. Make sure you're not getting
false data because of it.
--
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@dell.com
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2009-09-03 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 5:32 Dell-laptop is not working without wireless Dmitry Torokhov
2009-08-18 12:10 ` Matthew Garrett
2009-09-03 14:59 ` Dmitry Torokhov
2009-09-03 16:42 ` Mario Limonciello [this message]
2009-09-03 17:15 ` Dmitry Torokhov
2009-09-03 17:20 ` Mario Limonciello
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=4A9FF1FB.5090507@dell.com \
--to=mario_limonciello@dell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
/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