Date: Tue, 2 Apr 2013 20:06:54 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Joshua Isom <jrisom@gmail.com> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: ath not working after a motherboard and ram upgrade Message-ID: <CAJ-VmokpdvgDj2%2BcW4ZfoP0-YCDGqZMBpwvZ_tRb=NE4GeNWPg@mail.gmail.com> In-Reply-To: <515B8914.8030303@gmail.com> References: <515892C4.1060002@gmail.com> <CAJ-VmomxTm3RN6XDyRwX9SuSaiK3tqOQAJHK0rHM=j_T-vXDnA@mail.gmail.com> <5159F66B.2040600@gmail.com> <CAJ-Vmonv3GfwVKGyHruF%2BnADtKnZQpvOJH-cB4uCmK0TmbMypg@mail.gmail.com> <5159FF12.8030702@gmail.com> <CAJ-Vmok-A%2BBPTZrwWM4PT692B9qTCHzoOCAioah%2BGopL8n4JbQ@mail.gmail.com> <CAJ-VmonO1X7x6h=9pFB-sENsYSXsemA8-tjVRRWgpC607D3z4w@mail.gmail.com> <CAJ-VmomAC-KPkCjcHWUZ4EfvOZYw7p0iGi6RkAazDz6c2m4gUw@mail.gmail.com> <CAJ-Vmok%2BC%2Bet_b-8ZWQyDTebFBVwidQrn6U0J1eyB%2B%2BwyxDAWA@mail.gmail.com> <515B4E16.3050901@gmail.com> <CAJ-VmonrJNAm55zMY2DifygAW8x4iGfPV_WntMXyQVbmRVbOmg@mail.gmail.com> <CAJ-VmokwtNiZtN7t96wc9E-fv-0j%2Byhd0jcJO4ZWjC0HCM%2BwPg@mail.gmail.com> <515B76A6.7080804@gmail.com> <CAJ-Vmon0S2Xm4tnkYPNAHRvODe_Mp=M5CvRrQH0Nt-W_PbEVew@mail.gmail.com> <515B78C2.20609@gmail.com> <CAJ-VmonSzyxfY0J8V4-LWaQneOeh7SD=EvHxxKE-yTXbhoBN_g@mail.gmail.com> <515B8233.9000603@gmail.com> <CAJ-Vmok_xdR4RrWv6RR1c2D4TYPHeoxsJi60m5kAjLUhLNVBzg@mail.gmail.com> <515B8914.8030303@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
So, can you test end-to-end pings? With full memory booted up? What I'd like to try and do is narrow down whether it's a TX or RX (or both.) Do you have control over something on the other end? Can you tcpdump the wifi interface and see if it's pings, pongs, or both being disabled? Also, can you disable 11n and see if you end up with the same behaviour? ifconfig wlan0 -ampdu, before you run wpa_supplicant. Thanks, Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokpdvgDj2%2BcW4ZfoP0-YCDGqZMBpwvZ_tRb=NE4GeNWPg>