Dear maintainers, I tested a little bit, and here are some more informations. Maybe it helps:
1. The described behaviour appears EVERY TIME, when I started Windows 7 on this system, and rebooted to linux again. Conclusion: it seems, windows is setting some bit, that linux does not. 2. This behaviour MAY appear, when power was complete taken off (power supply and accumulator). It MAY also appear, when power was taken off for a long time (several hours) Conclusion: At boot there is a missing intialisation thing for this card or for the pci-bus. 3. This behaviour NEVER appears at normal running time. Once the wireless-card is running, this bug never appears until next boot. Even by unloading and reloading the module ath5k it NEVER appears. Conclusion: It is a problem at boot time. 4. rfkill is showing me, the device is unblocked (soft-block and hard-block), even if the bug appears. Conclusion: Seems to be a hard-block, which cannot be reset by rfkill. I hope, this may help a little bit. Best regards Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org