From: Ian Schram <ischram@telenet.be>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Ismail Dönmez" <ismail@pardus.org.tr>,
"Dan Williams" <dcbw@redhat.com>,
Stephen.Clark@seclark.us, linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] iwl3945 doesn't work
Date: Thu, 15 Nov 2007 18:36:57 +0100 [thread overview]
Message-ID: <473C83B9.3010207@telenet.be> (raw)
In-Reply-To: <20071115151425.GF5035@kernel.dk>
I believe that a main problem is that people have trouble reproducing i=
t.
and despite my -somewhat- implicit question there is not more informati=
on
in this thread now. Other than some symptoms. It would probably help if=
you
posted system/software specifications and debug info to a (new) bug ove=
r at
bughost.org. (modprobe iwl3945 debug=3D0x43fff) to allow for it to be t=
racked better?
Because now imho we are just poking at it with a medium length stick.
With the information here, I honestly have no idea where to look, other=
s might
have the same problem.
ian
Jens Axboe wrote:
> On Thu, Nov 15 2007, John W. Linville wrote:
>> On Thu, Nov 15, 2007 at 10:39:22AM +0100, Jens Axboe wrote:
>>> On Thu, Nov 15 2007, Ismail D=F6nmez wrote:
>>>> Saturday 10 November 2007 Tarihinde 04:18:27 yazm????t??:
>>>>> I wonder if anybody knows something more about this issue by now,
>>>>> as it appears to occur to a few people.
>>>>>
>>>>> I reread the thread (rather quickly) but I do not see many specif=
ications
>>>>> of driver/mac80211/kernel. The few cases that do contain specs al=
l appear
>>>>> to be using fedora (don't want to jump to conclusions). But just =
wondering
>>>>> if anybody experienced this on any other kernel?
>>>> Btw this is still not fixed in latest git (post rc2).
>>> I'll second that, using todays snap still requires me to do an iwli=
st
>>> scan before I can use the network.
>>>
>>> Is anyone working on this at all? This was reported a month ago, ye=
t no
>>> progress or real developer interest in fixing this is apparent.
>> I don't see any pending patches that seem relevant. FWIW I'll proba=
bly
>> round-up what I do have and make them available today (and probably
>> in a Fedora kernel too).
>>
>> Does the disable_hw_scan=3D1 still work for you? Perhaps we should
>> consider making that the default...
>=20
> disable_hw_scan=3D1 never worked for me - I tried it, and it made no
> difference. I _have_ to do an iwlist wlan0 scan before it links with =
my
> access point, otherwise it doesn't work.
>=20
-
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
next prev parent reply other threads:[~2007-11-15 17:37 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
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 [this message]
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=473C83B9.3010207@telenet.be \
--to=ischram@telenet.be \
--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=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).