Modify

Opened 6 years ago

Closed 6 years ago

Last modified 4 years ago

#11134 closed defect (wontfix)

3rd antenna not selectable (AR9381 here on WZR-HP-G450H)

Reported by: Halo2 Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc:

Description

        option diversity '0'

--

        option txantenna '2'
        option rxantenna '2'

wifi

ifconfig: SIOCSIFFLAGS: Input/output error
command failed: Network is down (-127)
ifconfig: SIOCSIFFLAGS: Input/output error
ifconfig: SIOCSIFFLAGS: Input/output error
ifconfig: SIOCSIFFLAGS: Input/output error

---

Conclusion:

antenna 2 not selectable

every value other than 2 "works"

Attachments (0)

Change History (9)

comment:1 follow-up: Changed 6 years ago by jow

  • Resolution set to wontfix
  • Status changed from new to closed

Note that the value here is actually a 32bit field which selects the appropriate rx and tx chains. "2" does not mean "antenna 2" but "use no antenna port despite the 2nd (or 31th)". Depending on the hardware, eeprom, chip revision and operation mode it might be illegal - for example port 2 (or 31) is not attached leaving no usable antenna.

comment:2 in reply to: ↑ 1 Changed 6 years ago by Halo2

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Replying to jow:

Note that the value here is actually a 32bit field which selects the appropriate rx and tx chains. "2" does not mean "antenna 2" but "use no antenna port despite the 2nd (or 31th)". Depending on the hardware, eeprom, chip revision and operation mode it might be illegal - for example port 2 (or 31) is not attached leaving no usable antenna.

Sorry, but its an 3 chain device (AR9381) and the only documentation I can find says 0, 1 or 2, so any way to find out ports?

On every 2 chain device I had until now this worked this way, so I'm very unsure if there is no bug involved as, like I said, every other (more likely invalid value) works

comment:3 in reply to: ↑ description Changed 6 years ago by anonymous

Replying to Halo2:

        option diversity '0'

--

        option txantenna '2'
        option rxantenna '2'

wifi

ifconfig: SIOCSIFFLAGS: Input/output error
command failed: Network is down (-127)
ifconfig: SIOCSIFFLAGS: Input/output error
ifconfig: SIOCSIFFLAGS: Input/output error
ifconfig: SIOCSIFFLAGS: Input/output error

---

Conclusion:

antenna 2 not selectable

every value other than 2 "works"

Now the output when calling wifi with "antenna 2" is:

Could not set interface wlan0 flags: Input/output error
nl80211: Could not set interface 'wlan0' UP
Could not set interface wlan0 flags: Input/output error
nl80211 driver initialization failed.
Failed to start hostapd for phy0

Changing back to another chain does not help, so a reboot is necessary to get it up again (with any other value than 2).

comment:4 Changed 6 years ago by nbd

  • Resolution set to wontfix
  • Status changed from reopened to closed

i believe the chip does not properly support rx antenna masks with gaps. i've committed a change in r32508 that refuses such configurations to avoid accidentally crashing the chip.
if you want to use the second antenna, set rx antenna to 0x3, tx antenna to 0x2

comment:5 Changed 6 years ago by Halo2

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Should this really be the last approach?

Because:

3rd chain still not selectable (rx 0x5, tx 0x4 at least doesnt seem to crash (with validate_antenna_mask overriden) and receives whats on the 3rd antenna).

But yes rx 0x5 does something weired too as I also receive the 2nd antenna then, but I receive much more stations in general with this setting then with i.e. rx 0x3, tx 0x2! Really would like too see this receiving capabilities with rational settings!!!

So I would be really glad if a little more research is possible. I already tried all 7 chain settings (and even more absurde ones) with all antenna combinations (only a single antenna on every of the 3 chains, or one external with two internals rotating the 3 chains..) on 2 devices.

The sometimes fluctating sn value is just of little annoyance (calling wifi can help).

But the great difference in sn when you don't disconnect all other antennas but the selected one bugs much more.

And there currently is no good response - so you set:

option txantenna 3
option rxantenna 2

call wifi

Configured Antennas: TX 0x3 RX 0x3

set:

option txantenna 4
option rxantenna 2

and call wifi

Configured Antennas: TX 0x3 RX 0x3

reboot

Configured Antennas: TX 0x7 RX 0x7

So you not really know whats going on, especially before a reboot, and no messages at all.. .

The device looks so promising beside the chain problems, and I think progress will be of help for other ar938x/ar939x devices too.

Thank you

comment:6 follow-up: Changed 6 years ago by nbd

  • Resolution set to wontfix
  • Status changed from reopened to closed

Yes, I think this should be the final approach. Chainmasks with gaps are very likely to continue to attract hardware quirks in the future, because Atheros simply does not test them. I'd rather just block them completely instead of giving the impression that they work, and then stumbling on hard-to-detect quirks during runtime.

iw error messages were probably suppressed in the script because not all devices support setting the antenna. This should probably be fixed by checking the specific error code or something.

comment:7 in reply to: ↑ 6 Changed 6 years ago by Halo2

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Replying to nbd:

Yes, I think this should be the final approach. Chainmasks with gaps are very likely to continue to attract hardware quirks in the future, because Atheros simply does not test them. I'd rather just block them completely instead of giving the impression that they work, and then stumbling on hard-to-detect quirks during runtime.

iw error messages were probably suppressed in the script because not all devices support setting the antenna. This should probably be fixed by checking the specific error code or something.

:-(. Well, so no 3rd antenna for all this devices. And a somehow fancy 2nd one. Would be interesting how a ar9382 behaves with rx 0x2 and tx 0x2.. .

And that the disconnecting of the unused antennas is more or less necessary (at least to get correct sn values, and higher chance of a connection)?

comment:8 Changed 6 years ago by nbd

  • Resolution set to wontfix
  • Status changed from reopened to closed

yeah, but if the chip doesn't properly support it, there's no point in keeping this ticket open. sometimes configurations with tx-only antennas or gaps in the chainmask appear to work, but then run into really nasty calibration quirks.

comment:9 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.