b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: b43-dev@lists.infradead.org
Subject: [14e4:4315] Dell Studio 1735, rfkill problem
Date: Sat, 24 Apr 2010 02:03:42 +0200	[thread overview]
Message-ID: <o2z69e28c911004231703qa7012741p369f64b1723458e2@mail.gmail.com> (raw)
In-Reply-To: <y2ob7f967271004231630qf700e479p5659fc5fc39a1e83@mail.gmail.com>

On Sat, Apr 24, 2010 at 1:30 AM, Grygoriy Fuchedzhy
<grygoriy.fuchedzhy@gmail.com> wrote:
> 2010/4/24 G?bor Stefanik <netrolller.3d@gmail.com>
>> Check compat-wireless; IIRC LP-PHY rfkill support has been updated in 2.6.34.
>>
>> BTW, does software-rfkill (using the rfkill command-line utility) work
>> correctly?
>> Specifically, the following scenarios are interesting:
>> -With the hardware-rfkill switch ON (i.e. radio enabled), try to bring
>> down the card using the rfkill utility. Does the card actually stop
>> transmitting?
>> -Try to turn it back on. Is the interface usable again?
>> -Turn the hardware switch OFF, and back ON. Then, use rfkill to
>> soft-disable and re-enable the card. Does this make it work again?
>>
>> --
>> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>
> So, here is what I have:
>> ?~ $ sudo rfkill list
>> ?0: phy0: Wireless LAN
>> ? ? ? Soft blocked: no
>> ? ? ? Hard blocked: no
>
>> ~ $ sudo rfkill block 0
> Wifi immediately loses connection, wifi led turns off and dmesg reports:
>> wlan0: deauthenticating from 00:23:69:2f:3f:01 by local choice (reason=3)
>
> Now I have:
>> ~ $ sudo rfkill list
>> 0: phy0: Wireless LAN
>> ? ? ? Soft blocked: yes
>> ? ? ? Hard blocked: no
>
> Unblocking:
>> ~ $ sudo rfkill unblock 0
>> ~ $ sudo rfkill list
>> 0: phy0: Wireless LAN
>> ? ? ? Soft blocked: no
>> ? ? ? Hard blocked: no
>
> But wifi is not functional, wifi led remains turned off, dmesg tells nothing.
>
> If I turn hardware switch off and on, and then software off/on nothing changes.
>
> Then I compiled 2.6.34_rc5 kernel and get same behavior. Also I have
> got additional
> entry in dmesg when turning wifi off with rfkill utility or with
> hardware switch:
>> cfg80211: Calling CRDA to update world regulatory domain
>
> Thanks for quick response!
>
> --
> Grygoriy Fuchedzhy

Looks like I got lpphy_op_software_rfkill wrong then.

Larry, is the spec up to date on this matter?

-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

  reply	other threads:[~2010-04-24  0:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 22:05 [14e4:4315] Dell Studio 1735, rfkill problem Григорий Фучеджи
2010-04-23 22:21 ` Gábor Stefanik
     [not found]   ` <w2rb7f967271004231625pf533c5f9l82a5bd19f31c7355@mail.gmail.com>
2010-04-23 23:30     ` Grygoriy Fuchedzhy
2010-04-24  0:03       ` Gábor Stefanik [this message]
2010-04-24  2:54         ` Larry Finger
2010-04-24  3:09           ` Gábor Stefanik
     [not found] ` <20100424110940.2b908933@laptop.homenet>
     [not found]   ` <20100424112652.28e5735a@laptop.homenet>
2010-04-24 11:35     ` Grygoriy Fuchedzhy
2010-04-24 14:05       ` Larry Finger
2010-04-24 16:22         ` Chris Vine
2010-04-26 21:03         ` Grygoriy Fuchedzhy

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=o2z69e28c911004231703qa7012741p369f64b1723458e2@mail.gmail.com \
    --to=netrolller.3d@gmail.com \
    --cc=b43-dev@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).