All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org, Michael Buesch <mb@bu3sch.de>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	John Linville <linville@tuxdriver.com>,
	Bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH] b43: Output message at startup if hardware switch for radio is off
Date: Tue, 13 Nov 2007 10:22:29 -0500	[thread overview]
Message-ID: <1194967349.2955.25.camel@localhost.localdomain> (raw)
In-Reply-To: <200711121336.42389.hs4233@mail.mn-solutions.de>

On Mon, 2007-11-12 at 13:36 +0100, Holger Schurig wrote:
> > Well... Pressing the rfkill button is the _FIRST_ thing that I
> > would do, if the device does not work. I'm wondering why
> > people have a problem with that. On other operating systems
> > it's the very same. On Windows there is no dmesg.
>=20
> On Windows, the "Wireless Network Connection" wizard displays
>=20
> -----------------------------------------------------
> No wireless networks were found in range
>=20
> Make sure the wireless switch on your computer is on.
> To see an updated list, click "Refresh network list".
> -----------------------------------------------------
>=20
> The Linux =C3=A4quivalent would be NetworkManager or the KDE tools fo=
r=20
> this job.
>=20
>=20
> That's at least displayed on the WinXP Embedded device that I=20
> just created :-)

Good thought; NM should probably replace the "You're disconnected"
notification dialog at startup with text that reads similar to remind
the user that the killswitch is on.

Dan


-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2007-11-13 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 22:47 [PATCH] b43: Output message at startup if hardware switch for radio is off Larry Finger
2007-11-10 15:24 ` Michael Buesch
2007-11-12 12:36   ` Holger Schurig
2007-11-13 15:22     ` Dan Williams [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=1194967349.2955.25.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    /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.