Thanks!
I suppose the problem is some missed re-initialization after resume.
At the moment, the following is a workaround:
rmmod ath5k
killall wpa_supplicant
modprobe ath5k
After that I see a new phy in debufs, and the network works fine.
--- "Luis R. Rodriguez" <[EMAIL PROTECTED]> wrote:
> On Jan 14, 2008 9:17 AM, Alex Eskin <[EMAIL PROTECTED]> wrote:
> >
> > I have a Thinkpad T41 laptop running Fedora 8 with the latest
> > updates. The ath5k driver works great, until I try suspend-to-ram.
> > After the resume, the driver gets into a strange state where
> > everything seems to work except that connecting to my WEP
> > encrypted AP gives a steady stream of
> >
> > WEP decrypt failed (ICV)
> >
> > messages and no packets get through. However, if encryption is
> > turned off everything works great even across a suspend/resume.
> >
> > In an attempt to track this down, I turned on ath5k and mac80211
> > debugging, but so far I could not figure out what is wrong. The
> > value of the WEP key (as viewed from debugfs) is correct even
> > in the strange state.
> >
> > Any hints on how to debug this? Everything is 100% reproducible
> > so in theory it should be easy to track down. It is clear that I do
> > not have general RX path corruption after a resume (since unencrypted
> > works). Any ideas?
>
> Although some hardware code is there to try WEP it doesn't work yet.
> I'll work on a patch to enable this as option and if not enabled use
> software encryption instead, while we correct hw encryption.
>
> Luis
>
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
