From: Jan De Luyck <lkml@kcore.org>
To: James Ketrenos <jketreno@linux.co.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Announce] Intel PRO/Wireless 2100 802.11b driver
Date: Thu, 11 Mar 2004 09:05:39 +0100 [thread overview]
Message-ID: <200403110905.42588.lkml@kcore.org> (raw)
In-Reply-To: <405019C2.5060409@linux.co.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 11 March 2004 08:48, James Ketrenos wrote:
> 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
I believe I wasn't awake when I typed that mail ;p
The problem is that if you try to set an IP using DHCP (in my case ISC dhcpcd
version 1.3.22pl4) without first enabling your interface, you get a fatal
interrupt.
If you enable your interface, then do a dhcp request, it works.
Why I got mixed up with the ap setting is that I first thought that was the
problem (since iwconfig eth1 showed 00:00:00:00:00:00 instead of the mac
address of the AP. It was shown in /proc/iwp2100/eth1/bssconfig though)
> 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.
Yup, I'm compiling that one (together with 2.6.4) right now.
Maybe this should be cc-ed to the devel mailing list too?
Jan
- --
You see but you do not observe.
Sir Arthur Conan Doyle, in "The Memoirs of Sherlock Holmes"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAUB3VUQQOfidJUwQRAix/AJ9GdhYEH/MlK8AToIgnHVpdIuekywCfYQ9V
SqTUbdIeZVEDrhoSt+HJ9z0=
=Nej6
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-03-11 8:05 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
2004-03-11 8:05 ` Jan De Luyck [this message]
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=200403110905.42588.lkml@kcore.org \
--to=lkml@kcore.org \
--cc=jketreno@linux.co.intel.com \
--cc=linux-kernel@vger.kernel.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