All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Sokol <el.es.cr@googlemail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Rfkill buttons : bi-stable, mono-stable, tactile
Date: Fri, 18 Dec 2009 08:52:06 +0000	[thread overview]
Message-ID: <4B2B42B6.1010501@gmail.com> (raw)
In-Reply-To: <20091217195231.GA11747@srcf.ucam.org>

Matthew Garrett wrote:
> (Please keep me Cc:ed - linux-kernel is high enough traffic that it's 

Ok, sorry, I was posting through gmane's web interface, I like it quite, but it is stupid
in the sense that it does not keep cc:s...

>> i.e. the rfkill does not know, and the 'problem' is only noticed when the wifi
>> disassociates (but Network Manager tries on to reconnect). On the other hand,
>> invoking /sbin/rfkill [un]block wifi blocks/unblocks wifi comfortably.
> 
> What does ls -l /sys/class/rfkill look like? What driver are you using 
> for your wireless card?
> 

lrwxrwxrwx 1 root root 0 2009-12-17 20:30 rfkill0 -> ../../devices/pci0000:00/0000:00:1c.2/0000:03:00.0/ieee80211/phy0/rfkill0

lukasz@workhorse:~$ lsmod |grep 802
mac80211              181140  1 ath5k
cfg80211               93052  3 ath5k,mac80211,ath

rfkill is built in (i.e. not a module) in this kernel, I heard somewhere.

Lukasz

  reply	other threads:[~2009-12-18  8:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 11:47 Rfkill buttons : bi-stable, mono-stable, tactile Lukasz Sokol
2009-12-17 12:08 ` Lukasz Sokol
2009-12-17 15:07 ` Matthew Garrett
2009-12-17 15:17   ` Lukasz Sokol
2009-12-17 19:52     ` Matthew Garrett
2009-12-18  8:52       ` Lukasz Sokol [this message]
2009-12-18 14:15         ` Matthew Garrett
2009-12-18 14:28           ` Lukasz Sokol
2009-12-18 14:35             ` Matthew Garrett
2009-12-18 14:41               ` Lukasz Sokol

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=4B2B42B6.1010501@gmail.com \
    --to=el.es.cr@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.