Hi, Just wanted to say that I have the exact same issue with a Packard-Bell dot m/a 134, and I reported it before too.
2011/6/5 Adrian Chadd <[email protected]> > On 5 June 2011 01:08, Tony Houghton <[email protected]> wrote: > > > I'm puzzled about why the driver works without the changes that > > supposedly introduced support for AR9285. Does the older version use a > > sort of generic 9k driver and the later version introduces specific > > support for certain features of the AR9285? Is there any way I can force > > an up-to-date kernel to use this generic mode? > > It wouldn't have worked without AR9285-specific stuff, because the > radio setup code is specific to the EEPROM version and the AR9285 has > a different radio to the previous members of the AR9002 family (AR9280 > in particular.) > > I suggest just doing the standard bisect trick to figure out where > things stopped working for you. > > It could be hanging the computer for a variety of reasons which may be > related to ath9k (eg changes to the chip power on/off logic), power > saving mode config, or maybe non-ath9k reasons (eg generic PCI(e) bus > attach/detach handling.) > > > > Adrian > _______________________________________________ > ath9k-devel mailing list > [email protected] > https://lists.ath9k.org/mailman/listinfo/ath9k-devel > -- *Adrià Cereto Massagué* Biotechnology student Universitat Rovira i Virgili Languages: Català, Español, English, Français, Deutsch, Português, Esperanto Nota importante <http://www.gnu.org/philosophy/no-word-attachments.es.html>| Important Notice <http://www.gnu.org/philosophy/no-word-attachments.html>
_______________________________________________ ath9k-devel mailing list [email protected] https://lists.ath9k.org/mailman/listinfo/ath9k-devel
