Hi,
Paul Zimmerman wrote:
> Well, I was very reluctant to go to the trouble of putting it back, but
> when I did the machine recognizes it again. This is getting very,
> very weird.
Just sounds like a race condition to me.
[...]
> I also found that after running 3.2 even in "recovery" mode
> I could not load the standard stable kernel without a cold restart. It
> hung when trying to load X, just like when the backported kernel itself
> tried to load X. The machine had to be physically turned off and
> restarted.
Sure, it seems plausible that initialization of the graphics card
changed in some unfortunate way between 2.6.32 and the wheezy kernel.
Ideally we would want to fix such a thing before releasing wheezy, so
if you have time to work on it then I'd be interested.
Thanks for a heads up. Please file a separate bug if you want to look
into that.
But in the meantime, I'd like to get this wireless bug understood and
fixed if you have time for it.
Is this summary of your experience with the ath5k card correct?
behavior on lenny: always worked
behavior on squeeze: broken, symptoms not described yet
behavior on wheezy: card only detected ~50% of the time
when detected, it works (?)
Thanks,
Jonathan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
