Date: Wed, 03 Apr 2013 19:22:27 -0500 From: Joshua Isom <jrisom@gmail.com> To: Adrian Chadd <adrian@freebsd.org> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: ath not working after a motherboard and ram upgrade Message-ID: <515CC7C3.3070608@gmail.com> In-Reply-To: <CAJ-Vmok8%2BOiYtciugqFFzdzSm%2BayT9a1SXkuM-2iAj2AEbhLFg@mail.gmail.com> References: <515892C4.1060002@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> <CAJ-VmokpdvgDj2%2BcW4ZfoP0-YCDGqZMBpwvZ_tRb=NE4GeNWPg@mail.gmail.com> <CAJ-VmomDUGyuNS2kjHWS_NJZdUXb5ki1-ueAh_%2Biv67q1bccXQ@mail.gmail.com> <515CAA36.70002@gmail.com> <CAJ-Vmok8%2BOiYtciugqFFzdzSm%2BayT9a1SXkuM-2iAj2AEbhLFg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I added -ampdu to rc.conf and it connected to the network, but still dropped packets. I'm not getting the network to work when I try it manually after boot. It could be me though, or something else wrong or not working properly. It's the same kernel as before except the patch, and that was the only time I was getting those messages. I checked hw.ath before, and after, there's no difference. hw.ath.longcal: 30 hw.ath.shortcal: 100 hw.ath.resetcal: 1200 hw.ath.anical: 100 hw.ath.rxbuf: 512 hw.ath.txbuf: 512 hw.ath.txbuf_mgmt: 32 hw.ath.bstuck: 4 hw.ath.debug: 0 hw.ath.hal.debug: 0 On 4/3/2013 6:16 PM, Adrian Chadd wrote: > Hi, > > Please try again, but tell me what the output of : > > sysctl hw.ath > > is. LEave ampdu on for now. > > The allocation failures are a bit odd; that only happens when you've > compiled it without the 11n option enabled. > > > > Adrian >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?515CC7C3.3070608>