Sun, 13 May 2018 11:07:19 +0500 Артур Истомин <art.is...@yandex.ru> > On Sat, May 12, 2018 at 10:53:29PM +1000, tomr wrote: > > > > I've been playing with an apu2 and an AR9280, which is supported by athn(4). > > > > It seems to perform terribly when I connect a second antenna. Is this > > the expected behaviour currently? Is there some MIMO magic that isn't > > yet implemented? Or do I just need to get the antenna spacing right? > > > > I see a foreboding "No Tx aggregation" in the commit message... > > I have the same problems with the same hardware. Not only with n-mode, with > g-mode too. > If I remember correctly there was no problems with g-mode circa 5.0-5.3 > releases OpenBSD. > > I thought it is a hardware problem and planed to test it with linux. > > If you find solution, please post it here. >
Hi Artur, I have a late 2010 laptop with a SISO (not MIMO) athn(4) AR9285 device: athn0 at pci2 dev 0 function 0 "Atheros AR9285" rev 0x01: apic 2 int 17 athn0: AR9285 rev 2 (1T1R), ROM rev 13, address 00:25:d3:xx:xx:xx athn(4) - Atheros IEEE 802.11a/b/g/n wireless network device http://man.openbsd.org/athn The maker put only 1 cable for an antenna, despite the card being B/G/N and I found similar problems which I could not sort with another cable. So, in my particular case the device defaulted to N mode (at one point) and I had to find the hard way the now obvious solution to run it as G: media autoselect mode 11g mediaopt hostap You could put this line in /etc/hostname.athn0 or skip mediaopt hostap. Hope the tip is for SISO devices with only 1 antenna, or prefer G mode. https://en.wikipedia.org/wiki/Single-input_single-output_system https://en.wikipedia.org/wiki/MIMO#Forms Kind regards, Anton Lazarov
