From: Dan Williams <dcbw@redhat.com>
To: Chr <chunkeey@web.de>
Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
linux-wireless@vger.kernel.org
Subject: Re: prism54 stopped working after upgrade from kernel 2.6.25.14-69.fc8 to 2.6.26.3-14.fc8
Date: Sat, 20 Sep 2008 17:08:29 -0400 [thread overview]
Message-ID: <1221944909.11865.9.camel@localhost.localdomain> (raw)
In-Reply-To: <200809222205.28754.chunkeey@web.de>
On Mon, 2008-09-22 at 22:05 +0200, Chr wrote:
> On Monday 22 September 2008 20:38:04 Philippe Waroquiers wrote:
> > With the new kernel 2.6.26.3-14.fc8, I see that the prism54 card looks in a
> > correct working mode (e.g. /sbin/iwlist wlan0 scan shows good scan
> > results).
> > But after that, wpa_supplicant cannot associate (gets a timeout)
> > (while it works ok with 2.6.25.14-69.fc8)
> > I have put below the output of wpa_supplicant for the bad case
> > and for the good case.
> >
> > What can I do to further see what is going wrong ?
> >
>
> Well, you can blame the fedora people if you want.
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=aaa1553512b9105699113ea7e2ea726f3d9d4de2
Is that commit not in stable 2.6.26 yet or something?
I also had to make sure that only one driver got bound to my card, both
p54 and prism54 fought for it.
Dan
next prev parent reply other threads:[~2008-09-22 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 18:38 prism54 stopped working after upgrade from kernel 2.6.25.14-69.fc8 to 2.6.26.3-14.fc8 Philippe Waroquiers
2008-09-22 18:42 ` Luis R. Rodriguez
2008-09-22 19:22 ` Philippe Waroquiers
2008-09-22 20:05 ` Chr
2008-09-20 21:08 ` Dan Williams [this message]
2008-09-22 21:32 ` Chr
2008-09-20 21:44 ` Dan Williams
2008-09-22 21:59 ` Chr
2008-09-22 22:13 ` John W. Linville
2008-09-23 17:30 ` Kyle McMartin
2008-10-03 19:37 ` Philippe Waroquiers
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=1221944909.11865.9.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=chunkeey@web.de \
--cc=linux-wireless@vger.kernel.org \
--cc=philippe.waroquiers@skynet.be \
/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