All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Ketrenos <jketreno@linux.co.intel.com>
To: Jan De Luyck <lkml@kcore.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Announce] Intel PRO/Wireless 2100 802.11b driver
Date: Thu, 11 Mar 2004 01:48:18 -0600	[thread overview]
Message-ID: <405019C2.5060409@linux.co.intel.com> (raw)
In-Reply-To: <200403110723.47400.lkml@kcore.org>

Jan De Luyck wrote:
>>I can't test the actual transmitting since I've got no accesspoint handy.
>>Will do so when at home, though.
> 
> Tested this. It works, _if_ you set the AP address first, otherwise it bails 
> out with 'Fatal interrupt'.

So you're doing something like:

# modprobe ipw2100
# iwconfig eth1 ap 00:0d:88:28:2e:91
# ifconfig eth1 up

and if you skip the iwconfig step you see the fatal interrupt?

Btw, thanks for your prior post with the oops info.  There is a fix in the 
latest snapshot (0.30) on http://ipw2100.sf.net.

Thanks,
James

  reply	other threads:[~2004-03-11  7:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 20:24 [Announce] Intel PRO/Wireless 2100 802.11b driver James Ketrenos
2004-03-09 20:57 ` Arjan van de Ven
2004-03-09 22:01   ` James Ketrenos
2004-03-09 23:48     ` Marcel Holtmann
2004-03-09 21:05 ` Timothy Miller
2004-03-09 21:12 ` Dax Kelson
2004-03-10  2:46   ` James Ketrenos
2004-03-10  8:15   ` vda
2004-03-10  8:38     ` Jeff Garzik
2004-03-10 17:31       ` Timothy Miller
2004-03-10 17:26         ` Jeff Garzik
2004-03-12  0:32         ` Lincoln Dale
2004-03-11  1:07       ` Joel Jaeggli
2004-03-10 12:35     ` bert hubert
2004-03-10 18:06     ` Disconnect
2004-03-11 22:45     ` Bill Davidsen
2004-03-10  7:52 ` Jan De Luyck
2004-03-11  6:23   ` Jan De Luyck
2004-03-11  7:48     ` James Ketrenos [this message]
2004-03-11  8:05       ` Jan De Luyck
2004-03-11 18:37 ` Stephen Hemminger
2004-03-11 22:14   ` James Ketrenos
2004-03-11 22:27 ` Bill Davidsen

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=405019C2.5060409@linux.co.intel.com \
    --to=jketreno@linux.co.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@kcore.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.