New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#691 - 5Ghz radio detected as 2.4Ghz and not-functional on Asus RP-N53 and Buffalo WHR-600D (Ralink RT5592) #5692
Comments
mkresin: Please provide always the full bootlog and the 'iw list' output for both wireless phys. Would you please try the following two images:
If you prefer to build an image on your own, you can find the commits in my [[https://git.lede-project.org/?p=lede/mkresin/staging.git;a=shortlog;h=refs/heads/ramips|staging tree]]. |
kbios: Thank you very much for the images. I was able to try on the RP-N53 as right now I don't have the WHR-600D available. |
mkresin: According to my google skills the errors:
[ 51.934086] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0000, type=4
[ 60.094043] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0065, type=4
[ 60.128242] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
seams to be a known issue. But it could be as well that 0x8000 isn't the correct offset for caldata/eeprom. Would you please paste the mac address of the PCIe wireless adapter (a dump of the factory partition would be fine as well). It is a good indicator whether the correct offset was used. Might be a silly question but have you confirmed that you are on 5GHz? According to the iw output the EEPROM of the PCIe wireless has the 2.4 and 5GHz band enabled. I've pushed another fix to my staging tree which disables the 2.4 GHz band for the PCIe wireless. The RP-N53 image is updated as well.
Can you give me a rough estimate how long it takes till you are able to test the WHR-600D fix? |
kbios: According to ifconfig the mac address is e0:3f:49:91:fe:16, you can find the factory partition attached. I can confirm it's using 5Ghz: |
mkresin: I'm still not sure which driver to blame for the rt2x00lib error. I've seen this error with another rt2x00 pci card back in the days. But in that case it turned out to be an [[https://bugzilla.kernel.org/show_bug.cgi?id=110091|issue with the systems pci driver]]. Would you please test the WHR-600D and open a new bugreport with your findings afterwards. At least the issue reported here is fixed with https://git.lede-project.org/21abb7492c217e7d9959f578a7aab98457e3820a and https://git.lede-project.org/b4be4617b5f33b47a5eb00756f939a23cf368145. Both commits are backported to the 17.01 branch and are part of the upcoming 17.01.1 bugfix release. |
psyborg: when booted initrams without nand support device could not load factory partition and eeprom
once it loaded eeprom there was a crash
had to define RF5592 in driver for proper detection
now with doubts that RF 000f is proper? could it be that change from wifi@1814,5592 to wifi@0,0 requires defining RF in driver? |
psyborg: Similar to asus and buffalo, EA2750 can also send out ssid but connecting fails with same messages about unrecognized signal and wrong frame size. Passing custom memory sizes like mentioned in bugzilla report does not help. |
kbios:
These two devices have a 2.4 Ghz radio integrated in the MT7620 SoC, and a pcie 5Ghz radio.
The 5Ghz radio is identified in dmesg as
[ 9.832680] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
[ 9.851675] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0001 detected
[ 9.866116] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
and in lspci as
01:00.0 Network controller [0280]: Ralink corp. RT3091 Wireless 802.11n 1T/2R PCIe [1814:3091]
Subsystem: Ralink corp. RT3091 Wireless 802.11n 1T/2R PCIe [1814:3091]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 80 bytes
Interrupt: pin A routed to IRQ 4
Region 0: Memory at 20000000 (32-bit, non-prefetchable) [size=65537]
Region 1: Memory at (32-bit, non-prefetchable) [size=2]
Region 2: Memory at (32-bit, non-prefetchable) [size=2]
Region 3: Memory at (32-bit, non-prefetchable) [size=2]
Region 4: Memory at (32-bit, non-prefetchable) [size=2]
Region 5: Memory at (32-bit, non-prefetchable) [size=2]
Expansion ROM at [disabled] [size=2]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0.000W
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Device Serial Number 08-68-35-ff-fe-60-a8-86
Kernel driver in use: rt2800pci
iw shows it is detected as 2.4 ghz:
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short long limit: 2
Coverage class: 0 (up to 0m)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
Band 1:
Capabilities: 0x27e
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
RX STBC 2-streams
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 2 usec (0x04)
HT RX MCS rate indexes supported: 0-15, 32
TX unequal modulation not supported
HT TX Max spatial streams: 1
HT TX MCS rate indexes supported may differ
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm)
* 2472 MHz [13] (20.0 dBm)
* 2484 MHz [14] (disabled)
valid interface combinations:
* #{ managed, AP, mesh point } <= 8,
total <= 8, #channels <= 1
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
The result is that it doesn't work neither with 2.4Ghz or 5Ghz networks.
So I think there are a couple of weird things here:
The text was updated successfully, but these errors were encountered: