On 15 June 2018 at 19:23, <mgreger@xxxxxxxxxxxx> wrote: > ---- mgreger@xxxxxxxxxxxx wrote: >> ---- "Michał Kazior" <kazikcz@xxxxxxxxx> wrote: >> > Your noise floor readout in survey dump is terribly bad for 5GHz. It >> > ain't stellar for 2.4GHz either but within reason nonetheless. >> > >> > Did you try using the card in a different device? I wonder if the >> > device you're trying to use it in has some sort of internal noise on >> > those frequencies and/or ath9k's ANI isn't able to deal with it. >> > >> > >> > Michał >> > >> > On 15 June 2018 at 15:31, <mgreger@xxxxxxxxxxxx> wrote: >> >> I did. >> I took it out of the Penguin-Z notebook and put it in a Dell XPS15 9560 running Windows 10. Only 2.4Ghz networks were visible from there as well. Not exactly apples-to-apples, but consistent results. This reduces likeliness this is tied to a os/driver issue. Maybe calibration data on the device eeprom is broken? Or maybe it's a hardware defect? > Could it be antenna related (in multiple devices)? Antennas can be designed to work better on certain frequency ranges. I wouldn't expect such a dramatic effect though. > On wikidevi.com I see some M.2 cards listed with an antenna connector of U.FL and others with MHF4. I can't find anything describing the difference, if any. The connectors seemed to fit OK. Also, what's the deal with 'main' and 'aux' antenna connectors? I've seen people suggest swapping them has helped in some cases with poor signal, while others insist that it makes no difference. I have not tried swapping the connectors. I think it's not a connector problem because 2.4GHz scan results report reasonable signal strength for found APs (-60dBm). My experience is that if you use a wrong (but seemingly fitting) connector you'd get near 0 results or below -90dBm across the board. Michał
