Re: ath and ipad
On Thu, Jul 04, 2013 at 01:17:14AM -0700, Adrian Chadd wrote: Sorry, try: interface=wlan0 driver=bsd ssid=CACHEBOY_11N_1 wpa=3 wpa_key_mgmt=WPA-PSK wpa_passphrase=PASSPHRASE wpa_pairwise=CCMP ctrl_interface=/var/run/hostapd working ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: ath and ipad
On Thu, Jul 04, 2013 at 01:25:20AM -0700, Adrian Chadd wrote: Ok! CAn you go and tinker with this? See what seems to break it? I can then go debug why it's breaking. I can play with this setup some hours. After this I restore previos setup and can play again next day, 06-11 GMT. ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: ath and ipad
On Wed, Jul 03, 2013 at 01:44:55PM -0700, Adrian Chadd wrote: Hi! I don't quite know what's going on there. I know the latest ipad works fine. But I don't have an ipad 1 to test with. Does the ipad 1 get an IP address? No, I don't see DHCP DISCOVER and ipad don't get DHCP OFFER. How I can test ipad don't send any packets or packets from ipad droped in the ath hardware or in the ath driver? -adrian On 3 July 2013 13:17, Slawa Olhovchenkov s...@zxy.spb.ru wrote: I am try to connect iPad (iPad 1) to FreeBSD AP (ath0: Atheros 9220 mem 0xb020-0xb020 irq 18 at device 5.0 on pci6). Association is OK (WPA2-EAP (PEAP)), but I don't see any packets from iPad (by tcpdump). FreeBSD is 10.0-CURRENT from Jun 8. With this system this iPad workin year ago (I don't remember exactly verion OS on that moment) iPhone 5 working with this system OK. This is iPad working nice with other FreeBSD 10.0-CURRENT from Aug 31 2012 (ath0: Atheros 5212 mem 0xe300-0xe300 irq 11 at device 20.0 on pci0). I am don't know how to deep debuging this issuse. ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: ath and ipad
On Wed, Jul 03, 2013 at 03:04:20PM -0700, Adrian Chadd wrote: On 3 July 2013 15:04, Slawa Olhovchenkov s...@zxy.spb.ru wrote: How I can test ipad don't send any packets or packets from ipad droped in the ath hardware or in the ath driver? You could try turning on wlan debugging: wlandebug +input +output +crypto See if it logs anything crypto drop related. I see only this: Jul 4 02:09:03 notebook kernel: [339639] ap0: ieee80211_crypto_newkey: cipher 3 flags 0x3 keyix 65535 Jul 4 02:09:03 notebook kernel: [339639] ap0: ieee80211_crypto_setkey: AES-CCM keyix 6 flags 0x103 mac d8:a2:5e:01:58:55 rsc 0 tsc 0 len 16 Jul 4 02:09:03 notebook kernel: [339639] ap0: [d8:a2:5e:01:58:55] recv probe req Jul 4 02:09:03 notebook last message repeated 3 times Jul 4 02:09:08 notebook kernel: [339643] ap0: [d8:a2:5e:01:58:55] recv probe req ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: ath and ipad
On Wed, Jul 03, 2013 at 03:25:58PM -0700, Adrian Chadd wrote: Ok, well. Try disconnecting everything, then run 'athstats 1' and see if any crypto errors occur. I don't see any crypto errors occur in 'athstats 1' (but I don't disconnecting everything). If I do 'athdebug +recv +recv_proc' I see in log Jul 4 02:33:04 notebook kernel: [341079] TODS d8:a2:5e:01:58:55-f4:ec:38:a3:10:dc(f4:ec:38:a3:10:dc) data 67M +65 Jul 4 02:33:04 notebook kernel: [341079] 4801 2c00 f4ec 38a3 10dc d8a2 5e01 5855 f4ec 38a3 10dc 201b 5cbd 1653 Jul 4 02:33:04 notebook kernel: [341080] ath0: ath_legacy_rx_tasklet: pending 1 Jul 4 02:33:04 notebook kernel: [341080] ath0: ath_rx_proc: called and don't see this in tcpdump. On 3 July 2013 15:24, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Wed, Jul 03, 2013 at 03:04:20PM -0700, Adrian Chadd wrote: On 3 July 2013 15:04, Slawa Olhovchenkov s...@zxy.spb.ru wrote: How I can test ipad don't send any packets or packets from ipad droped in the ath hardware or in the ath driver? You could try turning on wlan debugging: wlandebug +input +output +crypto See if it logs anything crypto drop related. I see only this: Jul 4 02:09:03 notebook kernel: [339639] ap0: ieee80211_crypto_newkey: cipher 3 flags 0x3 keyix 65535 Jul 4 02:09:03 notebook kernel: [339639] ap0: ieee80211_crypto_setkey: AES-CCM keyix 6 flags 0x103 mac d8:a2:5e:01:58:55 rsc 0 tsc 0 len 16 Jul 4 02:09:03 notebook kernel: [339639] ap0: [d8:a2:5e:01:58:55] recv probe req Jul 4 02:09:03 notebook last message repeated 3 times Jul 4 02:09:08 notebook kernel: [339643] ap0: [d8:a2:5e:01:58:55] recv probe req ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: ath and ipad
On Wed, Jul 03, 2013 at 03:39:07PM -0700, Adrian Chadd wrote: On 3 July 2013 15:38, Slawa Olhovchenkov s...@zxy.spb.ru wrote: I don't see any crypto errors occur in 'athstats 1' (but I don't disconnecting everything). ok, good starting point. If I do 'athdebug +recv +recv_proc' I see in log Jul 4 02:33:04 notebook kernel: [341079] TODS d8:a2:5e:01:58:55-f4:ec:38:a3:10:dc(f4:ec:38:a3:10:dc) data 67M +65 Jul 4 02:33:04 notebook kernel: [341079] 4801 2c00 f4ec 38a3 10dc d8a2 5e01 5855 f4ec 38a3 10dc 201b 5cbd 1653 Jul 4 02:33:04 notebook kernel: [341080] ath0: ath_legacy_rx_tasklet: pending 1 Jul 4 02:33:04 notebook kernel: [341080] ath0: ath_rx_proc: called Interesting. And that's the MAC address of your ipad? d8:a2:5e:01:58:55 (f4:ec:38:a3:10:dc is my ath) ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: ath and ipad
On Wed, Jul 03, 2013 at 03:46:55PM -0700, Adrian Chadd wrote: On 3 July 2013 15:45, Slawa Olhovchenkov s...@zxy.spb.ru wrote: ok, good starting point. If I do 'athdebug +recv +recv_proc' I see in log Jul 4 02:33:04 notebook kernel: [341079] TODS d8:a2:5e:01:58:55-f4:ec:38:a3:10:dc(f4:ec:38:a3:10:dc) data 67M +65 Jul 4 02:33:04 notebook kernel: [341079] 4801 2c00 f4ec 38a3 10dc d8a2 5e01 5855 f4ec 38a3 10dc 201b 5cbd 1653 Jul 4 02:33:04 notebook kernel: [341080] ath0: ath_legacy_rx_tasklet: pending 1 Jul 4 02:33:04 notebook kernel: [341080] ath0: ath_rx_proc: called Interesting. And that's the MAC address of your ipad? d8:a2:5e:01:58:55 (f4:ec:38:a3:10:dc is my ath) Ok. So next is figuring out why it's dying. How about running 'athstats 1' whilst this is going on, see whether you're seeing crypto/crc/etc errors show up? Can you copy/paste the output of athstats whilst you're trying to have your ipad associate? ipad succesufull associate (i see this association by ifconfig list sta). i don't see any packets from ipad after associate. I run athstats, turn off wifi on ipad, turn it on and wait 169.254.x.x instead of DHCP leased address. (except ipad associated and working iphone and n9) input output altrate shortlong xretry crcerr crypt phyerr rssi rate 911909 396162 733 37635 32000 4302 1168313 07 MCS2 200 0 0 0 0 0 0 08 MCS2 221 0 0 0 0 0 0 0 10 MCS2 221 0 0 0 0 0 0 09 MCS2 252 0 0 0 0 0 0 0 15 MCS2 238 0 0 0 0 0 0 0 171M 200 0 0 0 0 0 0 0 101M 200 0 0 0 0 0 0 091M 289 0 0 0 0 0 0 0 261M 290 0 0 0 0 0 0 0 221M 270 0 0 0 0 0 0 0 241M 290 0 0 0 0 0 0 0 251M 250 0 0 0 0 0 0 0 231M 210 0 0 0 0 0 0 0 111M 200 0 0 0 0 0 0 091M 200 0 0 0 0 0 0 081M 200 0 0 0 0 0 0 081M 180 0 0 0 0 0 0 081M 200 0 0 0 0 0 0 081M 200 0 0 0 0 0 0 081M 267 0 0 4 1 1 0 0 201M input output altrate shortlong xretry crcerr crypt phyerr rssi rate 912391 396198 733 37635 32004 4303 1168413 0 141M 190 0 0 0 0 0 0 091M 190 0 0 0 0 0 0 081M 289 0 0 0 0 1 0 0 341M 301 0 0 0 0 0 0 0 27 MCS2 270 0 0 0 0 0 0 0 20 MCS2 300 0 0 0 0 0 0 0 25 MCS2 280 0 0 0 0 0 0 0 23 MCS2 170 0 0 0 0 2 0 0 11 MCS2 190 0 0 0 0 0 0 08 MCS2 210 0 0 0 0 0 0 0 10 MCS2 231 0 0 0 0 0 0 0 11 MCS2 231 0 0 0 0 0 0 0 15 MCS2 220 0 0 0 0 0 0 0 14 MCS2 200 0 0 0 0 0 0 09 MCS2 180 0 0 0 0 0 0 08 MCS2 200 0 0 0 0 0 0 08 MCS2 221 0 0 0 0 0 0 0 13 MCS0 200 0 0 0 0 0 0 09 MCS0 200 0 0 0 0 0 0 09 MCS0 241 0 0 0 0 1 0 0 22 MCS7 input output altrate shortlong xretry crcerr crypt phyerr rssi rate 912865 396212 733 37635 32004 4303 1168813 0 20 MCS7
Re: ath and ipad
On Wed, Jul 03, 2013 at 04:02:13PM -0700, Adrian Chadd wrote: Ok, can you set the network up (briefly!) as a totally open (no encryption) network, and verify that the ipad works? Not now, i can try this after some hours. Also, what's your hostapd.conf file look like? interface=ap0 driver=bsd logger_syslog=-1 logger_syslog_level=2 logger_stdout=-1 logger_stdout_level=2 debug=4 dump_file=/tmp/hostapd.dump ctrl_interface=/var/run/hostapd ctrl_interface_group=wheel ssid=notebook country_code=RU ieee80211d=1 channel=6 beacon_int=100 dtim_period=2 max_num_sta=255 rts_threshold=2347 fragm_threshold=2346 macaddr_acl=0 auth_algs=1 ignore_broadcast_ssid=0 wme_enabled=0 wme_ac_bk_cwmin=4 wme_ac_bk_cwmax=10 wme_ac_bk_aifs=7 wme_ac_bk_txop_limit=0 wme_ac_bk_acm=0 wme_ac_be_aifs=3 wme_ac_be_cwmin=4 wme_ac_be_cwmax=10 wme_ac_be_txop_limit=0 wme_ac_be_acm=0 wme_ac_vi_aifs=2 wme_ac_vi_cwmin=3 wme_ac_vi_cwmax=4 wme_ac_vi_txop_limit=94 wme_ac_vi_acm=0 wme_ac_vo_aifs=2 wme_ac_vo_cwmin=2 wme_ac_vo_cwmax=3 wme_ac_vo_txop_limit=47 wme_ac_vo_acm=0 wmm_enabled=1 ieee80211n=1 ieee8021x=1 eapol_version=2 eapol_key_index_workaround=1 eap_server=1 eap_user_file=/etc/hostapd.eap_user ca_cert=/usr/local/etc/raddb/certs/ca.pem server_cert=/usr/local/etc/raddb/certs/server.pem private_key=/usr/local/etc/raddb/certs/server.pem private_key_passwd=whatever wpa=3 wpa_key_mgmt=WPA-EAP wpa_pairwise=TKIP CCMP Also, what's the output of 'athkey' look like? usage: athkey [-i device] keyix cipher keyval [mac] ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Atheros 9220 don't return from S3 state
On Mon, Jan 14, 2013 at 06:21:54AM +1100, Ian Smith wrote: On Sat, 12 Jan 2013 09:05:37 -0800, Adrian Chadd wrote: We can't patch pci space if they're all 0x, that means nothing is there. That's the point; the card hasn't come back on from suspend. So we need to do something _before_ it suspends. We can't do anything to the card after it resumes; we can only do stuff to the PCI bus. Adrian On 12 January 2013 09:07, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Jan 12, 2013 at 08:50:58AM -0800, Adrian Chadd wrote: I don't know the first thing about ACPI, I'm sorry. And here was me thinking you were across The Whole Thing :) OK, what about patching pci config space? Remove indication of support D3 state? or system don't suspend after this complete? (sorry for dumb question). Not dumb .. I don't know but suspect suspend would proceed regardless with perhaps some noise. Maybe worth doing that acpidump per recipe? Perhaps ask on the freebsd acpi list? Good idea, or perhaps current@ ? Somewhere both bus and ACPI people congregate anyway. One could point to this thread or compact its This is not new problem, this card in this notebook never resume. With old freebsd resume work badly with other devices. Now resume work nice (exclude this card) contents into a new message, but there may be something Slawa could do before the whole acpi debug palava, which is just to: a) boot verbose, maybe with kern.msgbufsize=98304 (say) in loader.conf b) suspend then resume c) dmesg # head to post somewhere, tail for the susp/res bit. I am attach this dmesg to first message to Adrian (not to list). Even without any ACPI debugging enabled, there should be clues as to acpi powering down then later (trying to) resume all devices, which might indicate whether that tunnel is worth diving deeper into .. Since I'm so pleased that suspend/resume finally works without drama out of the box on my T23 at 9.1-R, I include below one such cycle from /var/log/messages. There are logged ACPI errors I don't understand about \_SB_.PCI0.PCI1.CBS[01] that don't seem to affect functionality, but you can see the ACPI and PCI view of things, and it's old and small enough a box (single CPU, with no wireless :) If it helps, Ian Adrian On 12 January 2013 08:52, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote: On 12 January 2013 08:37, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Jan 12, 2013 at 08:25:22AM -0800, Adrian Chadd wrote: .. right, try flipping the rf kill switch off/on after suspend, dump the config registers. don't react -- 255 times 'ff' Okay. Well, I'll see if there's anything that I can do with the PCI glue inside the AR9220, but if it's broken under Windows... Perhaps if ACPI not found vendor wifi card (intel) not powered slot on resume? I am don't know how chek this is acpidump... === Jan 3 04:42:05 t234ma-s2 acpi: suspend at 20130103 04:42:05 Jan 3 04:42:05 t234ma-s2 kernel: acpi_button0: sleep button pressed Jan 3 04:42:10 t234ma-s2 kernel: (ada0:ata0:0:0:0): spin-down Jan 5 00:57:52 t234ma-s2 kernel: acpi_lid0: wake_prep enabled for \_SB_.LID_ (S3) Jan 5 00:57:52 t234ma-s2 kernel: acpi_button0: wake_prep enabled for \_SB_.SLPB (S3) Jan 5 00:57:52 t234ma-s2 kernel: vga0: saving 3780 bytes of video state Jan 5 00:57:52 t234ma-s2 kernel: vga0: saving color palette Jan 5 00:57:52 t234ma-s2 kernel: pci0:1:0:0: Transition from D0 to D3 Jan 5 00:57:52 t234ma-s2 kernel: pci1: set ACPI power state D3 on \_SB_.PCI0.AGP_.VID_ Jan 5 00:57:52 t234ma-s2 kernel: uhub2: at usbus0, port 1, addr 1 (disconnected) Jan 5 00:57:52 t234ma-s2 kernel: uhub0: at usbus1, port 1, addr 1 (disconnected) Jan 5 00:57:52 t234ma-s2 kernel: uhub1: at usbus2, port 1, addr 1 (disconnected) Jan 5 00:57:52 t234ma-s2 kernel: fxp0: link state changed to DOWN Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:0:0: Transition from D0 to D2 Jan 5 00:57:52 t234ma-s2 kernel: pci2: failed to set ACPI power state D2 on \_SB_.PCI0.PCI1.CBS0: AE_BAD_PARAMETER Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:0:1: Transition from D0 to D2 Jan 5 00:57:52 t234ma-s2 kernel: pci2: failed to set ACPI power state D2 on \_SB_.PCI0.PCI1.CBS1: AE_BAD_PARAMETER Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:8:0: Transition from D0 to D2 (resume, above kept for logging after resume despite timestamp) Jan 5 00:57:52 t234ma-s2 kernel: acpi_lid0: run_prep cleaned up for \_SB_.LID_ Jan 5 00:57:52 t234ma-s2 kernel: acpi_button0: run_prep cleaned up for \_SB_.SLPB Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.AGP_ Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.USB0 Jan 5 00:57:52
Re: Atheros 9220 don't return from S3 state
On Sun, Jan 13, 2013 at 12:19:22PM -0800, Adrian Chadd wrote: On 13 January 2013 12:07, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sun, Jan 13, 2013 at 11:43:55AM -0800, Adrian Chadd wrote: Right. That should be a good indication. After 10 min card still hot. Ok, so that means the basic power lines are up and working. Ah, I did add in the force-wakeup hack code; it's just not enabled by default. Try editing sys/dev/ath/if_ath_pci.c ; look for: #ifdef ATH_PCI_WAKEUP_WAR .. and change that to #if 1 Then recompile if_ath_pci and try that. After reboot not working: [228] ath0: device timeout [236] ath0: device timeout [245] ath0: device timeout PS: card more hot. ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Atheros 9220 don't return from S3 state
On Sun, Jan 13, 2013 at 04:32:16PM -0500, Adrian Chadd wrote: Ok. So don't use that :) I'll dig up the pci hostif registers and see what I can find. But, hm. We should dump and compare the pci conf registers for the bridge that device is on.nbsp; If it is pcib3@pci0:0:30:0: class=0x060401 card=0x12e310cf chip=0x24488086 rev=0xd4 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Mobile PCI Bridge' class = bridge subclass = PCI-PCI (other bridge is PCI Express) -- I don't find difference between 'boot' and 'resume'. Adrian Adrian Sent from my Palm Pre on ATamp;T On Jan 13, 2013 4:25 PM, Slawa Olhovchenkov lt;s...@zxy.spb.rugt; wrote: On Sun, Jan 13, 2013 at 12:19:22PM -0800, Adrian Chadd wrote: gt; On 13 January 2013 12:07, Slawa Olhovchenkov lt;s...@zxy.spb.rugt; wrote: gt; gt; On Sun, Jan 13, 2013 at 11:43:55AM -0800, Adrian Chadd wrote: gt; gt; gt; gt;gt; Right. That should be a good indication. gt; gt; gt; gt; After 10 min card still hot. gt; gt; Ok, so that means the basic power lines are up and working. gt; gt; Ah, I did add in the force-wakeup hack code; it's just not enabled by default. gt; gt; Try editing sys/dev/ath/if_ath_pci.c ; look for: gt; gt; #ifdef ATH_PCI_WAKEUP_WAR gt; gt; .. and change that to gt; gt; #if 1 gt; gt; Then recompile if_ath_pci and try that. After reboot not working: [228] ath0: device timeout [236] ath0: device timeout [245] ath0: device timeout PS: card more hot. ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Atheros 9220 don't return from S3 state
On Sat, Jan 12, 2013 at 07:27:02AM -0800, Adrian Chadd wrote: Hi, There's no firmware for the AR9220 .. it's all in the driver/HAL. If XP restore isn't working; maybe there's something in the ACPI/BIOS that's screwing things up? I am use last available BIOS. After restore don't working only this card and this card don't have tab 'Power manager' in windows device manager. I found in the internet information about other issuse with this wn861n (and windows) (for example -- http://www.nothingbuttablets.com/forum/showthread.php?p=80851), but using last driver don't help for me. ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Atheros 9220 don't return from S3 state
On Sat, Jan 12, 2013 at 07:52:19AM -0800, Adrian Chadd wrote: Ah, is it perhaps rfkill related? I've seen issues with rfkill before, where it is implemented as disable the power to the entire slot rather than assert the RF kill line to the device. It's possible this is how it has to happen with the intel NICs? do you have an rfkill button on the keyboard to enable/disable wireless? Try toggling that, then do pciconf -lv again? You can read the entire set of pci configuration registers: pciconf -rb pciX.X.X.X 0:255 If they show up as 0x then the NIC is disconnected/powered off/hung. Try toggling the RF kill key on your keyboard, then re-read those config registers. No rfkill button on the keyboard, but have hardware rf switch. This switch now work only for bluetooth (switching off don't relay to atheros card). Fresh boot, driver working Switch off: # pciconf -rb pci0:6:5:0 0:255 8c 16 29 00 16 01 b0 02 01 00 80 02 08 a8 00 00 00 00 20 b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8c 16 91 20 00 00 00 00 44 00 00 00 00 00 00 00 12 01 00 00 80 00 00 00 01 00 82 48 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Switch on: # pciconf -rb pci0:6:5:0 0:255 8c 16 29 00 16 01 b0 02 01 00 80 02 08 a8 00 00 00 00 20 b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8c 16 91 20 00 00 00 00 44 00 00 00 00 00 00 00 12 01 00 00 80 00 00 00 01 00 82 48 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 go to sleep, resume (switch still on): # pciconf -rb pci0:6:5:0 0:255 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Adrian On 12 January 2013 07:44, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Jan 12, 2013 at 07:27:02AM -0800, Adrian Chadd wrote: Hi, There's no firmware for the AR9220 .. it's all in the driver/HAL. If XP restore isn't working; maybe there's something in the ACPI/BIOS that's screwing things up? I am use last available BIOS. After restore don't working only this card and this card don't have tab 'Power manager' in windows device manager. I found in the internet information about other issuse with this wn861n (and windows) (for example -- http://www.nothingbuttablets.com/forum/showthread.php?p=80851), but using last driver don't help for me. ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Atheros 9220 don't return from S3 state
On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote: On 12 January 2013 08:37, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Jan 12, 2013 at 08:25:22AM -0800, Adrian Chadd wrote: .. right, try flipping the rf kill switch off/on after suspend, dump the config registers. don't react -- 255 times 'ff' Okay. Well, I'll see if there's anything that I can do with the PCI glue inside the AR9220, but if it's broken under Windows... Perhaps if ACPI not found vendor wifi card (intel) not powered slot on resume? I am don't know how chek this is acpidump... ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Atheros 9220 don't return from S3 state
On Sat, Jan 12, 2013 at 08:50:58AM -0800, Adrian Chadd wrote: I don't know the first thing about ACPI, I'm sorry. OK, what about patching pci config space? Remove indication of support D3 state? or system don't suspend after this complete? (sorry for dumb question). Perhaps ask on the freebsd acpi list? Adrian On 12 January 2013 08:52, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote: On 12 January 2013 08:37, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Jan 12, 2013 at 08:25:22AM -0800, Adrian Chadd wrote: .. right, try flipping the rf kill switch off/on after suspend, dump the config registers. don't react -- 255 times 'ff' Okay. Well, I'll see if there's anything that I can do with the PCI glue inside the AR9220, but if it's broken under Windows... Perhaps if ACPI not found vendor wifi card (intel) not powered slot on resume? I am don't know how chek this is acpidump... ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Atheros 9220 don't return from S3 state
On Sat, Jan 12, 2013 at 09:05:37AM -0800, Adrian Chadd wrote: We can't patch pci space if they're all 0x, that means nothing is there. That's the point; the card hasn't come back on from suspend. So we need to do something _before_ it suspends. We can't do anything to the card after it resumes; we can only do stuff to the PCI bus. No, patch before suspend. If card don't report support D3 state -- on sleep card not lost power? Or after resume got full reset? Adrian On 12 January 2013 09:07, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Jan 12, 2013 at 08:50:58AM -0800, Adrian Chadd wrote: I don't know the first thing about ACPI, I'm sorry. OK, what about patching pci config space? Remove indication of support D3 state? or system don't suspend after this complete? (sorry for dumb question). Perhaps ask on the freebsd acpi list? Adrian On 12 January 2013 08:52, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote: On 12 January 2013 08:37, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Sat, Jan 12, 2013 at 08:25:22AM -0800, Adrian Chadd wrote: .. right, try flipping the rf kill switch off/on after suspend, dump the config registers. don't react -- 255 times 'ff' Okay. Well, I'll see if there's anything that I can do with the PCI glue inside the AR9220, but if it's broken under Windows... Perhaps if ACPI not found vendor wifi card (intel) not powered slot on resume? I am don't know how chek this is acpidump... ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Atheros 9220 don't return from S3 state
On Thu, Jan 10, 2013 at 08:08:07PM -0800, Adrian Chadd wrote: .. odd. Is anything else behind that PCI bridge? bge0@pci0:2:0:0 work fine (work after resume). fwohci0@pci0:6:6:0 report working I can do some digging in a couple weeks; I don't have any AR9220's on me at the moment. Adrian On 10 January 2013 00:07, Slawa Olhovchenkov s...@zxy.spb.ru wrote: On Wed, Jan 09, 2013 at 06:00:21PM -0500, Adrian Chadd wrote: Does it happen every time? Yes. Which version of freebsd is it? Last -current Adrian Sent from my Palm Pre on ATamp;T On Jan 9, 2013 7:11 AM, Slawa Olhovchenkov lt;s...@zxy.spb.rugt; wrote: I am try play with suspend resume and see Atheros 9220 don't return from s3 state: [833] ath0: unable to reset hardware; hal status 3 try to unload/load module: [873] ath0: detached [873] pci6: lt;networkgt; at device 5.0 (no driver attached) [882] pci0: driver added [882] found-gt; vendor=0x8086, dev=0x266a, revid=0x04 [882] domain=0, bus=0, slot=31, func=3 [882] class=0c-05-00, hdrtype=0x00, mfdev=0 [882] cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) [882] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) [882] intpin=b, irq=19 [882] pci0:0:31:3: reprobing on driver added [882] pci2: driver added [882] found-gt; vendor=0x14e4, dev=0x167d, revid=0x21 [882] domain=0, bus=2, slot=0, func=0 [882] class=02-00-00, hdrtype=0x00, mfdev=0 [882] cmdreg=0x0106, statreg=0x0010, cachelnsz=8 (dwords) [882] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) [882] intpin=a, irq=16 [882] powerspec 2 supports D0 D3 current D0 [882] MSI supports 8 messages, 64 bit [882] pci0:2:0:0: reprobing on driver added [882] pci3: driver added [882] pci6: driver added [882] found-gt; vendor=0x, dev=0x, revid=0xff [882] domain=0, bus=6, slot=5, func=0 [882] class=ff-ff-ff, hdrtype=0x00, mfdev=0 [882] cmdreg=0x, statreg=0x02b0, cachelnsz=255 (dwords) [882] lattimer=0xff (7650 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) [882] intpin=_, irq=255 [882] powerspec 2 supports D0 D3 current D3 [882] pci0:6:5:0: reprobing on driver added [882] pci0:6:5:0: Transition from D3 to D0 [965] pci0: driver added [965] found-gt; vendor=0x8086, dev=0x266a, revid=0x04 [965] domain=0, bus=0, slot=31, func=3 [965] class=0c-05-00, hdrtype=0x00, mfdev=0 [965] cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) [965] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) [965] intpin=b, irq=19 [965] pci0:0:31:3: reprobing on driver added [965] pci2: driver added [965] found-gt; vendor=0x14e4, dev=0x167d, revid=0x21 [965] domain=0, bus=2, slot=0, func=0 [965] class=02-00-00, hdrtype=0x00, mfdev=0 [965] cmdreg=0x0106, statreg=0x0010, cachelnsz=8 (dwords) [965] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) [965] intpin=a, irq=16 [965] powerspec 2 supports D0 D3 current D0 [965] MSI supports 8 messages, 64 bit [965] pci0:2:0:0: reprobing on driver added [965] pci3: driver added [965] pci6: driver added [965] found-gt; vendor=0x, dev=0x, revid=0xff [965] domain=0, bus=6, slot=5, func=0 [965] class=ff-ff-ff, hdrtype=0x00, mfdev=0 [965] cmdreg=0x, statreg=0x02b0, cachelnsz=255 (dwords) [965] lattimer=0xff (7650 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) [965] intpin=_, irq=255 [965] powerspec 2 supports D0 D3 current D3 [965] pci0:6:5:0: reprobing on driver added [965] pci0:6:5:0: Transition from D3 to D0 driver don't attached card detected after boot as pci0:6:5:0 ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
