All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: "Hesse, Christian" <mail@earthworm.de>
Cc: James Ketrenos <jketreno@linux.intel.com>,
	linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG
Date: Sat, 10 Feb 2007 19:55:23 -0500	[thread overview]
Message-ID: <1171155323.5573.7.camel@dv> (raw)
In-Reply-To: <200702101424.00156.mail@earthworm.de>

Hello!

[I'm trimming the cc: a little bit]

On Sat, 2007-02-10 at 14:23 +0100, Hesse, Christian wrote:
> On Friday 09 February 2007 22:12, James Ketrenos wrote:
> > We are pleased to announce the availability of a new driver for the
> > Intel PRO/Wireless 3945ABG Network Connection adapter.
> 
> Wow, great news on this rainy saturday! ;-)
> 
> The driver works perfectly, I'm writing this mail via wireless link. However 
> there are two things to note:
> 
> The driver generates two network devices. The second one is for promicious 
> mode? Is there any chance to disable the interface? ifrename renamed the 
> wrong one to wlan0 and I had to tell my system to use eth1 for the wireless 
> connection.

I think one of the devices is wmaster0.  It's better that you just
ignore it.  The effort is already underway to make that interface
hidden.

In the meantime, you can use the "arp" condition in /etc/iftab.
Ethernet is 1 (that includes the original wlan0), IEEE 802.11 is 801
(that's the master devices and devices in monitor mode).  For example:

wifi* arp 801
eth* arp 1

> Second problem is that I can't unload the module. I get the message "FATAL: 
> Module iwlwifi is in use." even if both interfaces are down.

I cannot reproduce this problem.  Please see the output of "lsmod" and
the kernel log for possible oopses.

-- 
Regards,
Pavel Roskin


  parent reply	other threads:[~2007-02-11  0:55 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 21:12 [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG James Ketrenos
2007-02-09 22:14 ` Alon Bar-Lev
2007-02-09 22:26 ` Neil Brown
2007-02-09 21:52   ` James Ketrenos
2007-02-10  3:26     ` Nick Kossifidis
2007-02-09 22:37   ` Stefan Schmidt
2007-02-09 22:43 ` Pavel Roskin
2007-02-09 22:18   ` James Ketrenos
2007-02-09 23:17     ` Pavel Roskin
2007-02-09 22:45       ` James Ketrenos
2007-02-10  0:46 ` [ipw3945-devel] " Norbert Preining
2007-02-10  0:46   ` Norbert Preining
2007-02-13 23:23   ` James Ketrenos
2007-02-13 23:23     ` James Ketrenos
2007-02-10 13:23 ` Hesse, Christian
2007-02-10 14:25   ` Hesse, Christian
2007-02-12 16:32     ` [ipw3945-devel] " dragoran
2007-02-12 16:32       ` dragoran
2007-02-12 18:35     ` James Ketrenos
2007-02-13 12:18       ` Hesse, Christian
2007-02-11  0:55   ` Pavel Roskin [this message]
2007-02-11 13:17     ` Hesse, Christian
2007-02-13  6:47       ` Pavel Roskin
2007-02-13 10:41         ` Hesse, Christian
2007-02-11 13:19   ` Johannes Berg
2007-02-10 16:22 ` Theodore Tso
2007-02-10 16:39   ` John W. Linville
2007-02-10 17:53     ` [ipw3945-devel] " Pavel Roskin
2007-02-10 17:53       ` Pavel Roskin
2007-02-10 22:41       ` John W. Linville
2007-02-10 18:42   ` Michael Buesch
2007-02-13 13:58 ` Ismail Dönmez
2007-02-13 15:10   ` Jeff Chua
2007-02-13 15:10     ` Jeff Chua
2007-02-13 16:57     ` Ismail Dönmez
2007-02-13 16:57       ` Ismail Dönmez
2007-02-13 22:55       ` James Ketrenos
2007-02-13 22:55         ` James Ketrenos
2007-02-13 18:13 ` Pavel Machek
2007-02-13 18:36   ` Johannes Berg
2007-02-13 23:18     ` James Ketrenos
2007-02-14  0:16   ` [ipw3945-devel] " James Ketrenos
2007-02-14  0:16     ` James Ketrenos
2007-02-19 22:44     ` Pavel Machek
2007-02-19 22:44       ` Pavel Machek
2007-02-21  6:23       ` iwlwifi warnings Stephen Hemminger
2007-02-21  6:23         ` Stephen Hemminger
2007-02-21  7:32         ` Randy Dunlap
2007-02-21 19:38         ` Pavel Machek
2007-02-23  5:44           ` Pavel Roskin

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=1171155323.5573.7.camel@dv \
    --to=proski@gnu.org \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=jketreno@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mail@earthworm.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.