From: Pablo Sanchez <pablo@blueoakdb.com>
To: ipw3945-devel@lists.sourceforge.net
Cc: "Jens Axboe" <jens.axboe@oracle.com>,
"Ismail Dönmez" <ismail@pardus.org.tr>,
"Dan Williams" <dcbw@redhat.com>,
Stephen.Clark@seclark.us, linux-wireless@vger.kernel.org,
"Johannes Berg" <johannes@sipsolutions.net>
Subject: Re: [ipw3945-devel] iwl3945 doesn't work
Date: Thu, 15 Nov 2007 05:23:14 -0500 [thread overview]
Message-ID: <200711150523.14834.pablo@blueoakdb.com> (raw)
In-Reply-To: <20071115093921.GH638@kernel.dk>
On Thursday 15 November 2007 at 4:39 am, Jens Axboe penned
about "Re: [ipw3945-devel] iwl3945 doesn't work:
> I'll second that, using todays snap still requires me to do an
> iwlist scan before I can use the network.
Same here and for now, I've given up on using the Intel card on my
laptop. I slapped an El Cheapo 3COM card. While less mW's and
sensitivity, the MadWifi support is awesome for this atheros based
card.
Under stress, my ping times are within 100ms (unlike what I reported
previously), throughput is at 5Mbps and it works well with
KnetworkManager.
I'm not complaining about the Intel support, just noting for now the
problem isn't pressing for me. I'll happily test new drops as they
come out and address the issues I reported.
I'd appreciate even an acknowledgment though (rather than the old
/dev/null treatment).
Cheers,
--
Pablo
next prev parent reply other threads:[~2007-11-15 10:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 13:54 iwl3945 doesn't work Jens Axboe
2007-10-17 13:59 ` Jens Axboe
2007-10-17 14:07 ` John W. Linville
2007-10-17 14:08 ` Ismail Dönmez
2007-10-17 14:11 ` Jens Axboe
2007-10-17 14:15 ` Ismail Dönmez
2007-10-17 14:17 ` Jens Axboe
2007-10-17 14:18 ` Dan Williams
2007-10-17 14:22 ` Jens Axboe
2007-10-17 15:16 ` Dan Williams
2007-10-17 16:35 ` Jens Axboe
2007-10-17 20:06 ` [ipw3945-devel] " Stephen Clark
2007-10-18 6:57 ` Jens Axboe
2007-10-18 12:23 ` Stephen Clark
2007-10-18 12:33 ` Johannes Berg
2007-10-18 13:02 ` Tomas Winkler
2007-11-10 2:18 ` Ian Schram
2007-11-15 0:53 ` Ismail Dönmez
2007-11-15 9:39 ` Jens Axboe
2007-11-15 10:23 ` Pablo Sanchez [this message]
2007-11-15 10:26 ` Jens Axboe
2007-11-15 10:30 ` Pablo Sanchez
2007-11-15 11:08 ` Jens Axboe
2007-11-15 15:05 ` Mike Kershaw
2007-11-15 15:09 ` Jens Axboe
2007-11-15 18:36 ` Pablo Sanchez
2007-11-15 15:10 ` John W. Linville
2007-11-15 15:14 ` Jens Axboe
2007-11-15 17:36 ` Ian Schram
2007-10-18 12:34 ` Jens Axboe
2007-10-17 14:11 ` Dan Williams
2007-10-17 14:16 ` Jens Axboe
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=200711150523.14834.pablo@blueoakdb.com \
--to=pablo@blueoakdb.com \
--cc=Stephen.Clark@seclark.us \
--cc=dcbw@redhat.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=ismail@pardus.org.tr \
--cc=jens.axboe@oracle.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).