Alex Williams wrote: > Thank you for reply! > Please, tell me: did you saw working card on ar9160 ever??? May be > with other interfaces, such as PCI or USB? Is support for ar9160 > finished? Or it's now unusable?
No idea. But I found a mini-PCI AR9160 card and it works fine here. > insmod ath9k.ko debug=0x2000 > [ 121.839737] ath9k 0000:00:05.0: PCI INT A -> Link[LN_B] -> GSI 10 > (level, low) -> IRQ 10 > modprobe: FATAL: Could not load > /lib/modules/2.6.29-rc4-wl/modules.dep: No such file or directory > [ 123.479199] cfg80211: Calling CRDA for country: US > [ 123.507201] udev: renamed network interface wlan0 to wlan1 > [ 123.512965] Registered led device: ath9k-phy0::radio > [ 123.546520] Registered led device: ath9k-phy0::assoc > [ 123.589623] Registered led device: ath9k-phy0::tx > [ 123.614561] cfg80211: Regulatory domain changed to country: US > [ 123.620474] (start_freq - end_freq @ bandwidth), > (max_antenna_gain, max_eirp) > [ 123.628382] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) > [ 123.635228] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) > [ 123.642074] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) > [ 123.648921] (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) > [ 123.655907] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) > [ 123.685508] Registered led device: ath9k-phy0::rx > [ 123.727397] phy0: Atheros AR9160 MAC/BB Rev:1 AR5133 RF Rev:b0: > mem=0xcf520000, irq=10 > insert ath9k.ko > [ 124.070622] ADDRCONF(NETDEV_UP): wlan1: link is not ready CONFIG_ATH9K_DEBUG should be enabled in your kernel .config to enable debugging. See: http://wireless.kernel.org/en/users/Drivers/ath9k > > Are you able to at least scan, before trying to associate with an AP ? > > If so, then switch to a VT and try to associate and see if the kernel > > panics. > > A digital photograph of the panic (if one occurs) would be great. > > To perform scan, we need to "up" interface. Strange, but now, after > ifconfig wlan1 up - system hang deadly without any explanations! T_T > But sometimes it continue work after module load... Did you switch to a VT to see if a panic happens on bringing up the interface ? > Really??? ^_^ It's impossible! Is there some datasheet on ar9160??? > How about register addresses and their purpose? How can you write > driver for device if you do not know how it actually works? Writing > drivers it's like an embedded programming on microcontrolles without > OS - you should know every register and it's purpose. And even this > knowledge not guarantee errors proof... Sorry, I'm just wondering how > this possible... I heards that for ath9k Atheros released > specifications, or they writing in-house driver?.. Please, more info, > how it's really developing... =) > AR9160 is supported by ath9k, so no worries here. > How to enable additional debug info? Can I use KDBG + /dev/ttyS0 to > search for the problem? :) Search for serial console / netconsole debugging guides on the net. > Please, give me a link to git tutorial. I want to modifi some wireless > files, but keep ability to update them by "git pull"... Sorry, I'm > newbie... http://wireless.kernel.org/en/developers/Documentation/git-guide Sujith -- http://sujith-m.blogspot.com _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel