Sune Mølgaard wrote: > I'm hoping for someone to say "this is a known problem - we are > working on it"
Forget it. You will also not really get any help with debugging. If you can find, and ideally prove, a regression then developers will likely look into the problem. If you perceive and can demonstrate a problem, and complain loudly, then developers will attempt to reproduce the problem in a lab, but that is of course absolutely useless. > 08:01.0 Network controller: Atheros Communications Inc. > AR922X Wireless Network Adapter (rev 01) This is quite old hardware by now. The driver is supposed to work well also with this hardware, but in practise it has never for me. I have a feeling that the AR922x PCI silicon is not so great, and that it causes some of the problems. Perhaps the driver could work around them, but I'm not sure if it does. When dealing with this kernel driver your best chances at any kind of success is to use the hardware that developers currently work on. Those code paths are actively tested, improved, and debugged. Of course there is a small complication here; since the developers work on the driver before the hardware is made available on the market. At the moment I would not use anything older than AR9380 with the ath9k driver. I would suggest that you give FreeBSD a go on your laptop. Adrian is the author of that driver, it is not a copypaste of the ath9k, so it may work better or simply differently. I believe it supports your card. You obviously have to be open to trying out FreeBSD for that. //Peter _______________________________________________ ath9k-devel mailing list [email protected] https://lists.ath9k.org/mailman/listinfo/ath9k-devel
