* Re: Ralink RT5592 5Ghz capability not working
@ 2015-11-03 13:41 Xose Vazquez Perez
2015-11-03 18:10 ` Alberto Mattea
0 siblings, 1 reply; 13+ messages in thread
From: Xose Vazquez Perez @ 2015-11-03 13:41 UTC (permalink / raw)
To: Alberto Mattea, linux-wireless, Stanislaw Gruszka
Alberto Mattea wrote:
> this is about the mini-pcie version used in some embedded products
> (for example the Buffalo WHR-600D and the Asus RP-N53).
> It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz
> (5Ghz works with the proprietary driver supplied with the devices),
> but rt2800pci seems to see only the 2.4 Ghz capability.
As far as I know, RT5592 PCIe devices are unsupported by rt2800pci.
> dmesg:
>
> [ 14.070000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
> [ 14.080000] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0001 detected
> [ 14.100000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
> [ 134.420000] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
> [ 134.460000] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34
Here is the output of a real RT5592 PCIe device with rt2800pci driver(Feb 2013):
phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 5592, rf: 000f, rev: 0222.
phy1 -> rt2800_init_eeprom: Error - Invalid RT chipset 0x5592 detected.
phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
> The weird thing is that in lspci it is reported as an RT3091, due to the 0x3091 pci device id:
>
> 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]
> [...]
06:00.0 Network controller [0280]: Ralink corp. Device [1814:5592]
Subsystem: ASUSTeK Computer Inc. Device [1043:851a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fe500000 (32-bit, non-prefetchable) [size=64K]
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 <512ns, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- 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+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
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 c1-a5-f3-ff-fe-a9-85-30
> So maybe due to this (i'm not sure), rt2800pci only enables the 2.4 Ghz band support:
Your device does not look like a real RT5592 chip.
> All this with kernel 3.18 (openwrt 15.05 Chaos Calmer).
> Any ideas?
OpenWrt brings _a lot of_ code out upstream kernel.
Who knows what is running.
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: Ralink RT5592 5Ghz capability not working
2015-11-03 13:41 Ralink RT5592 5Ghz capability not working Xose Vazquez Perez
@ 2015-11-03 18:10 ` Alberto Mattea
2015-11-03 18:32 ` Alexis Green
2015-11-03 20:39 ` Xose Vazquez Perez
0 siblings, 2 replies; 13+ messages in thread
From: Alberto Mattea @ 2015-11-03 18:10 UTC (permalink / raw)
To: Xose Vazquez Perez, linux-wireless; +Cc: Stanislaw Gruszka
Hey, thanks for your answer. The device definitely isn't a RT3091, so do you
think it's some sort of an OEM hybrid? Do you think it would be better to
report this to the openwrt bugzilla?
Thanks
In data mar 3 novembre 2015 14:41:35, Xose Vazquez Perez ha scritto:
> Alberto Mattea wrote:
> > this is about the mini-pcie version used in some embedded products
> > (for example the Buffalo WHR-600D and the Asus RP-N53).
> > It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz
> > (5Ghz works with the proprietary driver supplied with the devices),
> > but rt2800pci seems to see only the 2.4 Ghz capability.
>
> As far as I know, RT5592 PCIe devices are unsupported by rt2800pci.
>
> > dmesg:
> >
> > [ 14.070000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5592, rev
> > 0222 detected [ 14.080000] ieee80211 phy0: rt2x00_set_rf: Info - RF
> > chipset 0001 detected [ 14.100000] ieee80211 phy0: Selected rate
> > control algorithm 'minstrel_ht' [ 134.420000] ieee80211 phy0:
> > rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin' [
> > 134.460000] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware
> > detected - version: 0.34
> Here is the output of a real RT5592 PCIe device with rt2800pci driver(Feb
> 2013):
>
> phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 5592, rf: 000f, rev:
> 0222. phy1 -> rt2800_init_eeprom: Error - Invalid RT chipset 0x5592
> detected. phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
>
> > The weird thing is that in lspci it is reported as an RT3091, due to the
> > 0x3091 pci device id:
> >
> > 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]
> >
> > [...]
>
> 06:00.0 Network controller [0280]: Ralink corp. Device [1814:5592]
> Subsystem: ASUSTeK Computer Inc. Device [1043:851a]
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr-
> DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0,
> Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 11
> Region 0: Memory at fe500000 (32-bit, non-prefetchable) [size=64K]
> 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
> <512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd-
> ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128
> bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns,
> L1 <64us ClockPM+ Surprise- LLActRep- BwNot-
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
> 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+ DevCtl2: Completion
> Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 2.5GT/s,
> EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB 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 c1-a5-f3-ff-fe-a9-85-30
> > So maybe due to this (i'm not sure), rt2800pci only enables the 2.4 Ghz
band support:
> Your device does not look like a real RT5592 chip.
>
> > All this with kernel 3.18 (openwrt 15.05 Chaos Calmer).
> > Any ideas?
>
> OpenWrt brings _a lot of_ code out upstream kernel.
> Who knows what is running.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Ralink RT5592 5Ghz capability not working
2015-11-03 18:10 ` Alberto Mattea
@ 2015-11-03 18:32 ` Alexis Green
2015-11-03 19:09 ` Alberto Mattea
2015-11-03 20:39 ` Xose Vazquez Perez
1 sibling, 1 reply; 13+ messages in thread
From: Alexis Green @ 2015-11-03 18:32 UTC (permalink / raw)
To: Alberto Mattea; +Cc: linux-wireless
This is so strange. Asus RT-N56U you mentioned earlier as one of the
examples actually has two separate chips for each band (and one of
them is RT3091) - https://wikidevi.com/wiki/ASUS_RT-N56U
Are you able to take a picture of the chip?
On Tue, Nov 3, 2015 at 10:10 AM, Alberto Mattea <alberto@mattea.info> wrote:
> Hey, thanks for your answer. The device definitely isn't a RT3091, so do you
> think it's some sort of an OEM hybrid? Do you think it would be better to
> report this to the openwrt bugzilla?
>
> Thanks
>
> In data mar 3 novembre 2015 14:41:35, Xose Vazquez Perez ha scritto:
>> Alberto Mattea wrote:
>> > this is about the mini-pcie version used in some embedded products
>> > (for example the Buffalo WHR-600D and the Asus RP-N53).
>> > It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz
>> > (5Ghz works with the proprietary driver supplied with the devices),
>> > but rt2800pci seems to see only the 2.4 Ghz capability.
>>
>> As far as I know, RT5592 PCIe devices are unsupported by rt2800pci.
>>
>> > dmesg:
>> >
>> > [ 14.070000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5592, rev
>> > 0222 detected [ 14.080000] ieee80211 phy0: rt2x00_set_rf: Info - RF
>> > chipset 0001 detected [ 14.100000] ieee80211 phy0: Selected rate
>> > control algorithm 'minstrel_ht' [ 134.420000] ieee80211 phy0:
>> > rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin' [
>> > 134.460000] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware
>> > detected - version: 0.34
>> Here is the output of a real RT5592 PCIe device with rt2800pci driver(Feb
>> 2013):
>>
>> phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 5592, rf: 000f, rev:
>> 0222. phy1 -> rt2800_init_eeprom: Error - Invalid RT chipset 0x5592
>> detected. phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
>>
>> > The weird thing is that in lspci it is reported as an RT3091, due to the
>> > 0x3091 pci device id:
>> >
>> > 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]
>> >
>> > [...]
>>
>> 06:00.0 Network controller [0280]: Ralink corp. Device [1814:5592]
>> Subsystem: ASUSTeK Computer Inc. Device [1043:851a]
>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>> Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr-
>> DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0,
>> Cache Line Size: 64 bytes
>> Interrupt: pin A routed to IRQ 11
>> Region 0: Memory at fe500000 (32-bit, non-prefetchable) [size=64K]
>> 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
>> <512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
>> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd-
>> ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128
>> bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
>> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns,
>> L1 <64us ClockPM+ Surprise- LLActRep- BwNot-
>> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
>> 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+ DevCtl2: Completion
>> Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 2.5GT/s,
>> EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB 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 c1-a5-f3-ff-fe-a9-85-30
>> > So maybe due to this (i'm not sure), rt2800pci only enables the 2.4 Ghz
> band support:
>> Your device does not look like a real RT5592 chip.
>>
>> > All this with kernel 3.18 (openwrt 15.05 Chaos Calmer).
>> > Any ideas?
>>
>> OpenWrt brings _a lot of_ code out upstream kernel.
>> Who knows what is running.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Ralink RT5592 5Ghz capability not working
2015-11-03 18:32 ` Alexis Green
@ 2015-11-03 19:09 ` Alberto Mattea
2015-11-03 19:31 ` Alexis Green
0 siblings, 1 reply; 13+ messages in thread
From: Alberto Mattea @ 2015-11-03 19:09 UTC (permalink / raw)
To: Alexis Green, linux-wireless
My device (the RP-N53) has 2 chips too: the other is integrated in the mt7620 soc and reports itself as
[ 14.120000] ieee80211 phy1: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'soc_wmac.eeprom'.
[ 14.140000] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 5390, rev 0500 detected
[ 14.150000] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620 detected
[ 14.170000] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
it is used for 2.4Ghz only (https://wikidevi.com/wiki/ASUS_RP-N53)
Unfortunately opening the RP-N53 appears impossible without voiding the warranty :(
In data mar 3 novembre 2015 10:32:29, hai scritto:
> This is so strange. Asus RT-N56U you mentioned earlier as one of the
> examples actually has two separate chips for each band (and one of
> them is RT3091) - https://wikidevi.com/wiki/ASUS_RT-N56U
> Are you able to take a picture of the chip?
>
> On Tue, Nov 3, 2015 at 10:10 AM, Alberto Mattea <alberto@mattea.info> wrote:
> > Hey, thanks for your answer. The device definitely isn't a RT3091, so do
> > you think it's some sort of an OEM hybrid? Do you think it would be
> > better to report this to the openwrt bugzilla?
> >
> > Thanks
> >
> > In data mar 3 novembre 2015 14:41:35, Xose Vazquez Perez ha scritto:
> >> Alberto Mattea wrote:
> >> > this is about the mini-pcie version used in some embedded products
> >> > (for example the Buffalo WHR-600D and the Asus RP-N53).
> >> > It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz
> >> > (5Ghz works with the proprietary driver supplied with the devices),
> >> > but rt2800pci seems to see only the 2.4 Ghz capability.
> >>
> >> As far as I know, RT5592 PCIe devices are unsupported by rt2800pci.
> >>
> >> > dmesg:
> >> >
> >> > [ 14.070000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5592,
> >> > rev
> >> > 0222 detected [ 14.080000] ieee80211 phy0: rt2x00_set_rf: Info - RF
> >> > chipset 0001 detected [ 14.100000] ieee80211 phy0: Selected rate
> >> > control algorithm 'minstrel_ht' [ 134.420000] ieee80211 phy0:
> >> > rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin' [
> >> > 134.460000] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware
> >> > detected - version: 0.34
> >>
> >> Here is the output of a real RT5592 PCIe device with rt2800pci driver(Feb
> >> 2013):
> >>
> >> phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 5592, rf: 000f,
> >> rev:
> >> 0222. phy1 -> rt2800_init_eeprom: Error - Invalid RT chipset 0x5592
> >> detected. phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
> >>
> >> > The weird thing is that in lspci it is reported as an RT3091, due to
> >> > the
> >> > 0x3091 pci device id:
> >> >
> >> > 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]
> >> >
> >> > [...]
> >>
> >> 06:00.0 Network controller [0280]: Ralink corp. Device [1814:5592]
> >>
> >> Subsystem: ASUSTeK Computer Inc. Device [1043:851a]
> >> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> >> ParErr-
> >>
> >> Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B-
> >> ParErr-
> >> DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0,
> >> Cache Line Size: 64 bytes
> >>
> >> Interrupt: pin A routed to IRQ 11
> >> Region 0: Memory at fe500000 (32-bit, non-prefetchable)
> >> [size=64K]
> >> 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
> >>
> >> <512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> >> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
> >> RlxdOrd-
> >> ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128
> >> bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
> >> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns,
> >> L1 <64us ClockPM+ Surprise- LLActRep- BwNot-
> >>
> >> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
> >>
> >> 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+ DevCtl2:
> >> Completion
> >> Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 2.5GT/s,
> >> EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB 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
> >> c1-a5-f3-ff-fe-a9-85-30
> >>
> >> > So maybe due to this (i'm not sure), rt2800pci only enables the 2.4 Ghz
> >
> > band support:
> >> Your device does not look like a real RT5592 chip.
> >>
> >> > All this with kernel 3.18 (openwrt 15.05 Chaos Calmer).
> >> > Any ideas?
> >>
> >> OpenWrt brings _a lot of_ code out upstream kernel.
> >> Who knows what is running.
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-wireless"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Ralink RT5592 5Ghz capability not working
2015-11-03 19:09 ` Alberto Mattea
@ 2015-11-03 19:31 ` Alexis Green
2015-11-03 21:07 ` Alberto Mattea
0 siblings, 1 reply; 13+ messages in thread
From: Alexis Green @ 2015-11-03 19:31 UTC (permalink / raw)
To: Alberto Mattea; +Cc: linux-wireless
All signs point to RT5592 not supported by rt2x00 driver... I'm
guessing they fudged pci id for some internal reasons (maybe even to
mess with OpenWRT people).
On Tue, Nov 3, 2015 at 11:09 AM, Alberto Mattea <alberto@mattea.info> wrote:
> My device (the RP-N53) has 2 chips too: the other is integrated in the mt7620 soc and reports itself as
>
> [ 14.120000] ieee80211 phy1: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'soc_wmac.eeprom'.
> [ 14.140000] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 5390, rev 0500 detected
> [ 14.150000] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620 detected
> [ 14.170000] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
>
> it is used for 2.4Ghz only (https://wikidevi.com/wiki/ASUS_RP-N53)
> Unfortunately opening the RP-N53 appears impossible without voiding the warranty :(
>
> In data mar 3 novembre 2015 10:32:29, hai scritto:
>> This is so strange. Asus RT-N56U you mentioned earlier as one of the
>> examples actually has two separate chips for each band (and one of
>> them is RT3091) - https://wikidevi.com/wiki/ASUS_RT-N56U
>> Are you able to take a picture of the chip?
>>
>> On Tue, Nov 3, 2015 at 10:10 AM, Alberto Mattea <alberto@mattea.info> wrote:
>> > Hey, thanks for your answer. The device definitely isn't a RT3091, so do
>> > you think it's some sort of an OEM hybrid? Do you think it would be
>> > better to report this to the openwrt bugzilla?
>> >
>> > Thanks
>> >
>> > In data mar 3 novembre 2015 14:41:35, Xose Vazquez Perez ha scritto:
>> >> Alberto Mattea wrote:
>> >> > this is about the mini-pcie version used in some embedded products
>> >> > (for example the Buffalo WHR-600D and the Asus RP-N53).
>> >> > It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz
>> >> > (5Ghz works with the proprietary driver supplied with the devices),
>> >> > but rt2800pci seems to see only the 2.4 Ghz capability.
>> >>
>> >> As far as I know, RT5592 PCIe devices are unsupported by rt2800pci.
>> >>
>> >> > dmesg:
>> >> >
>> >> > [ 14.070000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5592,
>> >> > rev
>> >> > 0222 detected [ 14.080000] ieee80211 phy0: rt2x00_set_rf: Info - RF
>> >> > chipset 0001 detected [ 14.100000] ieee80211 phy0: Selected rate
>> >> > control algorithm 'minstrel_ht' [ 134.420000] ieee80211 phy0:
>> >> > rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin' [
>> >> > 134.460000] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware
>> >> > detected - version: 0.34
>> >>
>> >> Here is the output of a real RT5592 PCIe device with rt2800pci driver(Feb
>> >> 2013):
>> >>
>> >> phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 5592, rf: 000f,
>> >> rev:
>> >> 0222. phy1 -> rt2800_init_eeprom: Error - Invalid RT chipset 0x5592
>> >> detected. phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
>> >>
>> >> > The weird thing is that in lspci it is reported as an RT3091, due to
>> >> > the
>> >> > 0x3091 pci device id:
>> >> >
>> >> > 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]
>> >> >
>> >> > [...]
>> >>
>> >> 06:00.0 Network controller [0280]: Ralink corp. Device [1814:5592]
>> >>
>> >> Subsystem: ASUSTeK Computer Inc. Device [1043:851a]
>> >> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>> >> ParErr-
>> >>
>> >> Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B-
>> >> ParErr-
>> >> DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0,
>> >> Cache Line Size: 64 bytes
>> >>
>> >> Interrupt: pin A routed to IRQ 11
>> >> Region 0: Memory at fe500000 (32-bit, non-prefetchable)
>> >> [size=64K]
>> >> 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
>> >>
>> >> <512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
>> >> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
>> >> RlxdOrd-
>> >> ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128
>> >> bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
>> >> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns,
>> >> L1 <64us ClockPM+ Surprise- LLActRep- BwNot-
>> >>
>> >> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
>> >>
>> >> 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+ DevCtl2:
>> >> Completion
>> >> Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 2.5GT/s,
>> >> EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB 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
>> >> c1-a5-f3-ff-fe-a9-85-30
>> >>
>> >> > So maybe due to this (i'm not sure), rt2800pci only enables the 2.4 Ghz
>> >
>> > band support:
>> >> Your device does not look like a real RT5592 chip.
>> >>
>> >> > All this with kernel 3.18 (openwrt 15.05 Chaos Calmer).
>> >> > Any ideas?
>> >>
>> >> OpenWrt brings _a lot of_ code out upstream kernel.
>> >> Who knows what is running.
>> >
>> > --
>> > To unsubscribe from this list: send the line "unsubscribe linux-wireless"
>> > in the body of a message to majordomo@vger.kernel.org
>> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Ralink RT5592 5Ghz capability not working
2015-11-03 19:31 ` Alexis Green
@ 2015-11-03 21:07 ` Alberto Mattea
2015-11-03 21:33 ` Gertjan van Wingerde
0 siblings, 1 reply; 13+ messages in thread
From: Alberto Mattea @ 2015-11-03 21:07 UTC (permalink / raw)
To: Alexis Green, linux-wireless
I found the FCC photos for the RP-N53:
https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=2001985
On page 9 there is a photo of the ralink chip, unfortunately very blurred. But
I also found the photos for the Buffalo WHR-600D (which exhibits the same
behaviour):
https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=1950610
Here (page 12) we can clearly read "RT5692N", and if we look closer that's the
same number you can see on the RP-N53. That's a model I cannot find anywhere.
So it seems some kind of OEM specific chip.
In data mar 3 novembre 2015 11:31:42, hai scritto:
> All signs point to RT5592 not supported by rt2x00 driver... I'm
> guessing they fudged pci id for some internal reasons (maybe even to
> mess with OpenWRT people).
>
> On Tue, Nov 3, 2015 at 11:09 AM, Alberto Mattea <alberto@mattea.info> wrote:
> > My device (the RP-N53) has 2 chips too: the other is integrated in the
> > mt7620 soc and reports itself as
> >
> > [ 14.120000] ieee80211 phy1: rt2x00lib_request_eeprom_file: Info -
> > Loading EEPROM data from 'soc_wmac.eeprom'. [ 14.140000] ieee80211
> > phy1: rt2x00_set_rt: Info - RT chipset 5390, rev 0500 detected [
> > 14.150000] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620 detected
> > [ 14.170000] ieee80211 phy1: Selected rate control algorithm
> > 'minstrel_ht'
> >
> > it is used for 2.4Ghz only (https://wikidevi.com/wiki/ASUS_RP-N53)
> > Unfortunately opening the RP-N53 appears impossible without voiding the
> > warranty :(>
> > In data mar 3 novembre 2015 10:32:29, hai scritto:
> >> This is so strange. Asus RT-N56U you mentioned earlier as one of the
> >> examples actually has two separate chips for each band (and one of
> >> them is RT3091) - https://wikidevi.com/wiki/ASUS_RT-N56U
> >> Are you able to take a picture of the chip?
> >>
> >> On Tue, Nov 3, 2015 at 10:10 AM, Alberto Mattea <alberto@mattea.info>
wrote:
> >> > Hey, thanks for your answer. The device definitely isn't a RT3091, so
> >> > do
> >> > you think it's some sort of an OEM hybrid? Do you think it would be
> >> > better to report this to the openwrt bugzilla?
> >> >
> >> > Thanks
> >> >
> >> > In data mar 3 novembre 2015 14:41:35, Xose Vazquez Perez ha scritto:
> >> >> Alberto Mattea wrote:
> >> >> > this is about the mini-pcie version used in some embedded products
> >> >> > (for example the Buffalo WHR-600D and the Asus RP-N53).
> >> >> > It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz
> >> >> > (5Ghz works with the proprietary driver supplied with the devices),
> >> >> > but rt2800pci seems to see only the 2.4 Ghz capability.
> >> >>
> >> >> As far as I know, RT5592 PCIe devices are unsupported by rt2800pci.
> >> >>
> >> >> > dmesg:
> >> >> >
> >> >> > [ 14.070000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset
> >> >> > 5592,
> >> >> > rev
> >> >> > 0222 detected [ 14.080000] ieee80211 phy0: rt2x00_set_rf: Info -
> >> >> > RF
> >> >> > chipset 0001 detected [ 14.100000] ieee80211 phy0: Selected rate
> >> >> > control algorithm 'minstrel_ht' [ 134.420000] ieee80211 phy0:
> >> >> > rt2x00lib_request_firmware: Info - Loading firmware file
> >> >> > 'rt2860.bin' [
> >> >> > 134.460000] ieee80211 phy0: rt2x00lib_request_firmware: Info -
> >> >> > Firmware
> >> >> > detected - version: 0.34
> >> >>
> >> >> Here is the output of a real RT5592 PCIe device with rt2800pci
> >> >> driver(Feb
> >> >> 2013):
> >> >>
> >> >> phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 5592, rf: 000f,
> >> >> rev:
> >> >> 0222. phy1 -> rt2800_init_eeprom: Error - Invalid RT chipset 0x5592
> >> >> detected. phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate
> >> >> device.
> >> >>
> >> >> > The weird thing is that in lspci it is reported as an RT3091, due to
> >> >> > the
> >> >> > 0x3091 pci device id:
> >> >> >
> >> >> > 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]
> >> >> >
> >> >> > [...]
> >> >>
> >> >> 06:00.0 Network controller [0280]: Ralink corp. Device [1814:5592]
> >> >>
> >> >> Subsystem: ASUSTeK Computer Inc. Device [1043:851a]
> >> >> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> >> >> ParErr-
> >> >>
> >> >> Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B-
> >> >> ParErr-
> >> >> DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0,
> >> >> Cache Line Size: 64 bytes
> >> >>
> >> >> Interrupt: pin A routed to IRQ 11
> >> >> Region 0: Memory at fe500000 (32-bit, non-prefetchable)
> >> >> [size=64K]
> >> >> 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
> >> >>
> >> >> <512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> >> >> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
> >> >> RlxdOrd-
> >> >> ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq
> >> >> 128
> >> >> bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
> >> >> TransPend-
> >> >> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
> >> >> <512ns,
> >> >> L1 <64us ClockPM+ Surprise- LLActRep- BwNot-
> >> >>
> >> >> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
> >> >>
> >> >> 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+ DevCtl2:
> >> >> Completion
> >> >> Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed:
> >> >> 2.5GT/s,
> >> >> EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB 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
> >> >> c1-a5-f3-ff-fe-a9-85-30
> >> >>
> >> >> > So maybe due to this (i'm not sure), rt2800pci only enables the 2.4
> >> >> > Ghz
> >> >
> >> > band support:
> >> >> Your device does not look like a real RT5592 chip.
> >> >>
> >> >> > All this with kernel 3.18 (openwrt 15.05 Chaos Calmer).
> >> >> > Any ideas?
> >> >>
> >> >> OpenWrt brings _a lot of_ code out upstream kernel.
> >> >> Who knows what is running.
> >> >
> >> > --
> >> > To unsubscribe from this list: send the line "unsubscribe
> >> > linux-wireless"
> >> > in the body of a message to majordomo@vger.kernel.org
> >> > More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Ralink RT5592 5Ghz capability not working
2015-11-03 21:07 ` Alberto Mattea
@ 2015-11-03 21:33 ` Gertjan van Wingerde
2015-11-03 21:44 ` Alberto Mattea
0 siblings, 1 reply; 13+ messages in thread
From: Gertjan van Wingerde @ 2015-11-03 21:33 UTC (permalink / raw)
To: Alberto Mattea, Alexis Green, linux-wireless
Did you have to install an eeprom file for the RT5592 PCI device?
If yes, this eeprom file could be the problem. As far as I can tell the
rt2x00 driver only enables the 2.4 GHz band because it determines that
the RF chip doesn't support the 5GHz band. The RF chip is determined
from the EEPROM, and is currently read as an RF2820 chip (the message
rt2x00_set_rf: Info - RF chipset 0001 detected)
---
Gertjan.
On 11/03/15 22:07, Alberto Mattea wrote:
> I found the FCC photos for the RP-N53:
> https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=2001985
>
> On page 9 there is a photo of the ralink chip, unfortunately very blurred. But
> I also found the photos for the Buffalo WHR-600D (which exhibits the same
> behaviour):
> https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=1950610
> Here (page 12) we can clearly read "RT5692N", and if we look closer that's the
> same number you can see on the RP-N53. That's a model I cannot find anywhere.
> So it seems some kind of OEM specific chip.
>
> In data mar 3 novembre 2015 11:31:42, hai scritto:
>> All signs point to RT5592 not supported by rt2x00 driver... I'm
>> guessing they fudged pci id for some internal reasons (maybe even to
>> mess with OpenWRT people).
>>
>> On Tue, Nov 3, 2015 at 11:09 AM, Alberto Mattea <alberto@mattea.info> wrote:
>>> My device (the RP-N53) has 2 chips too: the other is integrated in the
>>> mt7620 soc and reports itself as
>>>
>>> [ 14.120000] ieee80211 phy1: rt2x00lib_request_eeprom_file: Info -
>>> Loading EEPROM data from 'soc_wmac.eeprom'. [ 14.140000] ieee80211
>>> phy1: rt2x00_set_rt: Info - RT chipset 5390, rev 0500 detected [
>>> 14.150000] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620 detected
>>> [ 14.170000] ieee80211 phy1: Selected rate control algorithm
>>> 'minstrel_ht'
>>>
>>> it is used for 2.4Ghz only (https://wikidevi.com/wiki/ASUS_RP-N53)
>>> Unfortunately opening the RP-N53 appears impossible without voiding the
>>> warranty :(>
>>> In data mar 3 novembre 2015 10:32:29, hai scritto:
>>>> This is so strange. Asus RT-N56U you mentioned earlier as one of the
>>>> examples actually has two separate chips for each band (and one of
>>>> them is RT3091) - https://wikidevi.com/wiki/ASUS_RT-N56U
>>>> Are you able to take a picture of the chip?
>>>>
>>>> On Tue, Nov 3, 2015 at 10:10 AM, Alberto Mattea <alberto@mattea.info>
> wrote:
>>>>> Hey, thanks for your answer. The device definitely isn't a RT3091, so
>>>>> do
>>>>> you think it's some sort of an OEM hybrid? Do you think it would be
>>>>> better to report this to the openwrt bugzilla?
>>>>>
>>>>> Thanks
>>>>>
>>>>> In data mar 3 novembre 2015 14:41:35, Xose Vazquez Perez ha scritto:
>>>>>> Alberto Mattea wrote:
>>>>>>> this is about the mini-pcie version used in some embedded products
>>>>>>> (for example the Buffalo WHR-600D and the Asus RP-N53).
>>>>>>> It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz
>>>>>>> (5Ghz works with the proprietary driver supplied with the devices),
>>>>>>> but rt2800pci seems to see only the 2.4 Ghz capability.
>>>>>>
>>>>>> As far as I know, RT5592 PCIe devices are unsupported by rt2800pci.
>>>>>>
>>>>>>> dmesg:
>>>>>>>
>>>>>>> [ 14.070000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset
>>>>>>> 5592,
>>>>>>> rev
>>>>>>> 0222 detected [ 14.080000] ieee80211 phy0: rt2x00_set_rf: Info -
>>>>>>> RF
>>>>>>> chipset 0001 detected [ 14.100000] ieee80211 phy0: Selected rate
>>>>>>> control algorithm 'minstrel_ht' [ 134.420000] ieee80211 phy0:
>>>>>>> rt2x00lib_request_firmware: Info - Loading firmware file
>>>>>>> 'rt2860.bin' [
>>>>>>> 134.460000] ieee80211 phy0: rt2x00lib_request_firmware: Info -
>>>>>>> Firmware
>>>>>>> detected - version: 0.34
>>>>>>
>>>>>> Here is the output of a real RT5592 PCIe device with rt2800pci
>>>>>> driver(Feb
>>>>>> 2013):
>>>>>>
>>>>>> phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 5592, rf: 000f,
>>>>>> rev:
>>>>>> 0222. phy1 -> rt2800_init_eeprom: Error - Invalid RT chipset 0x5592
>>>>>> detected. phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate
>>>>>> device.
>>>>>>
>>>>>>> The weird thing is that in lspci it is reported as an RT3091, due to
>>>>>>> the
>>>>>>> 0x3091 pci device id:
>>>>>>>
>>>>>>> 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]
>>>>>>>
>>>>>>> [...]
>>>>>>
>>>>>> 06:00.0 Network controller [0280]: Ralink corp. Device [1814:5592]
>>>>>>
>>>>>> Subsystem: ASUSTeK Computer Inc. Device [1043:851a]
>>>>>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>>>>>> ParErr-
>>>>>>
>>>>>> Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B-
>>>>>> ParErr-
>>>>>> DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0,
>>>>>> Cache Line Size: 64 bytes
>>>>>>
>>>>>> Interrupt: pin A routed to IRQ 11
>>>>>> Region 0: Memory at fe500000 (32-bit, non-prefetchable)
>>>>>> [size=64K]
>>>>>> 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
>>>>>>
>>>>>> <512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
>>>>>> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
>>>>>> RlxdOrd-
>>>>>> ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq
>>>>>> 128
>>>>>> bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
>>>>>> TransPend-
>>>>>> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
>>>>>> <512ns,
>>>>>> L1 <64us ClockPM+ Surprise- LLActRep- BwNot-
>>>>>>
>>>>>> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
>>>>>>
>>>>>> 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+ DevCtl2:
>>>>>> Completion
>>>>>> Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed:
>>>>>> 2.5GT/s,
>>>>>> EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB 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
>>>>>> c1-a5-f3-ff-fe-a9-85-30
>>>>>>
>>>>>>> So maybe due to this (i'm not sure), rt2800pci only enables the 2.4
>>>>>>> Ghz
>>>>>
>>>>> band support:
>>>>>> Your device does not look like a real RT5592 chip.
>>>>>>
>>>>>>> All this with kernel 3.18 (openwrt 15.05 Chaos Calmer).
>>>>>>> Any ideas?
>>>>>>
>>>>>> OpenWrt brings _a lot of_ code out upstream kernel.
>>>>>> Who knows what is running.
>>>>>
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe
>>>>> linux-wireless"
>>>>> in the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
---
Gertjan
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Ralink RT5592 5Ghz capability not working
2015-11-03 21:33 ` Gertjan van Wingerde
@ 2015-11-03 21:44 ` Alberto Mattea
2015-11-03 21:49 ` Alberto Mattea
2015-11-03 21:50 ` Gertjan van Wingerde
0 siblings, 2 replies; 13+ messages in thread
From: Alberto Mattea @ 2015-11-03 21:44 UTC (permalink / raw)
To: Gertjan van Wingerde; +Cc: Alexis Green, linux-wireless
Hey,
I didn't have to, it was recognized this way out of the box.
I had to install an eeprom for the other onboard chip though (5390).
In data mar 3 novembre 2015 22:33:19, Gertjan van Wingerde ha scritto:
> Did you have to install an eeprom file for the RT5592 PCI device?
>
> If yes, this eeprom file could be the problem. As far as I can tell the
> rt2x00 driver only enables the 2.4 GHz band because it determines that
> the RF chip doesn't support the 5GHz band. The RF chip is determined
> from the EEPROM, and is currently read as an RF2820 chip (the message
> rt2x00_set_rf: Info - RF chipset 0001 detected)
>
> ---
> Gertjan.
>
> On 11/03/15 22:07, Alberto Mattea wrote:
> > I found the FCC photos for the RP-N53:
> > https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=2001985
> >
> > On page 9 there is a photo of the ralink chip, unfortunately very blurred.
> > But I also found the photos for the Buffalo WHR-600D (which exhibits the
> > same behaviour):
> > https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=1950610
> > Here (page 12) we can clearly read "RT5692N", and if we look closer that's
> > the same number you can see on the RP-N53. That's a model I cannot find
> > anywhere. So it seems some kind of OEM specific chip.
> >
> > In data mar 3 novembre 2015 11:31:42, hai scritto:
> >> All signs point to RT5592 not supported by rt2x00 driver... I'm
> >> guessing they fudged pci id for some internal reasons (maybe even to
> >> mess with OpenWRT people).
> >>
> >> On Tue, Nov 3, 2015 at 11:09 AM, Alberto Mattea <alberto@mattea.info>
wrote:
> >>> My device (the RP-N53) has 2 chips too: the other is integrated in the
> >>> mt7620 soc and reports itself as
> >>>
> >>> [ 14.120000] ieee80211 phy1: rt2x00lib_request_eeprom_file: Info -
> >>> Loading EEPROM data from 'soc_wmac.eeprom'. [ 14.140000] ieee80211
> >>> phy1: rt2x00_set_rt: Info - RT chipset 5390, rev 0500 detected [
> >>> 14.150000] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620
> >>> detected
> >>> [ 14.170000] ieee80211 phy1: Selected rate control algorithm
> >>> 'minstrel_ht'
> >>>
> >>> it is used for 2.4Ghz only (https://wikidevi.com/wiki/ASUS_RP-N53)
> >>> Unfortunately opening the RP-N53 appears impossible without voiding the
> >>> warranty :(>
> >>>
> >>> In data mar 3 novembre 2015 10:32:29, hai scritto:
> >>>> This is so strange. Asus RT-N56U you mentioned earlier as one of the
> >>>> examples actually has two separate chips for each band (and one of
> >>>> them is RT3091) - https://wikidevi.com/wiki/ASUS_RT-N56U
> >>>> Are you able to take a picture of the chip?
> >>>>
> >>>> On Tue, Nov 3, 2015 at 10:10 AM, Alberto Mattea <alberto@mattea.info>
> >
> > wrote:
> >>>>> Hey, thanks for your answer. The device definitely isn't a RT3091, so
> >>>>> do
> >>>>> you think it's some sort of an OEM hybrid? Do you think it would be
> >>>>> better to report this to the openwrt bugzilla?
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> In data mar 3 novembre 2015 14:41:35, Xose Vazquez Perez ha scritto:
> >>>>>> Alberto Mattea wrote:
> >>>>>>> this is about the mini-pcie version used in some embedded products
> >>>>>>> (for example the Buffalo WHR-600D and the Asus RP-N53).
> >>>>>>> It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz
> >>>>>>> (5Ghz works with the proprietary driver supplied with the devices),
> >>>>>>> but rt2800pci seems to see only the 2.4 Ghz capability.
> >>>>>>
> >>>>>> As far as I know, RT5592 PCIe devices are unsupported by rt2800pci.
> >>>>>>
> >>>>>>> dmesg:
> >>>>>>>
> >>>>>>> [ 14.070000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset
> >>>>>>> 5592,
> >>>>>>> rev
> >>>>>>> 0222 detected [ 14.080000] ieee80211 phy0: rt2x00_set_rf: Info -
> >>>>>>> RF
> >>>>>>> chipset 0001 detected [ 14.100000] ieee80211 phy0: Selected rate
> >>>>>>> control algorithm 'minstrel_ht' [ 134.420000] ieee80211 phy0:
> >>>>>>> rt2x00lib_request_firmware: Info - Loading firmware file
> >>>>>>> 'rt2860.bin' [
> >>>>>>> 134.460000] ieee80211 phy0: rt2x00lib_request_firmware: Info -
> >>>>>>> Firmware
> >>>>>>> detected - version: 0.34
> >>>>>>
> >>>>>> Here is the output of a real RT5592 PCIe device with rt2800pci
> >>>>>> driver(Feb
> >>>>>> 2013):
> >>>>>>
> >>>>>> phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 5592, rf:
> >>>>>> 000f,
> >>>>>> rev:
> >>>>>> 0222. phy1 -> rt2800_init_eeprom: Error - Invalid RT chipset 0x5592
> >>>>>> detected. phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate
> >>>>>> device.
> >>>>>>
> >>>>>>> The weird thing is that in lspci it is reported as an RT3091, due to
> >>>>>>> the
> >>>>>>> 0x3091 pci device id:
> >>>>>>>
> >>>>>>> 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]
> >>>>>>>
> >>>>>>> [...]
> >>>>>>
> >>>>>> 06:00.0 Network controller [0280]: Ralink corp. Device [1814:5592]
> >>>>>>
> >>>>>> Subsystem: ASUSTeK Computer Inc. Device [1043:851a]
> >>>>>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> >>>>>> ParErr-
> >>>>>>
> >>>>>> Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B-
> >>>>>> ParErr-
> >>>>>> DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency:
> >>>>>> 0,
> >>>>>> Cache Line Size: 64 bytes
> >>>>>>
> >>>>>> Interrupt: pin A routed to IRQ 11
> >>>>>> Region 0: Memory at fe500000 (32-bit, non-prefetchable)
> >>>>>> [size=64K]
> >>>>>> 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
> >>>>>>
> >>>>>> <512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> >>>>>> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
> >>>>>> RlxdOrd-
> >>>>>> ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq
> >>>>>> 128
> >>>>>> bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
> >>>>>> TransPend-
> >>>>>> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
> >>>>>> <512ns,
> >>>>>> L1 <64us ClockPM+ Surprise- LLActRep- BwNot-
> >>>>>>
> >>>>>> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled-
> >>>>>> Retrain-
> >>>>>>
> >>>>>> 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+ DevCtl2:
> >>>>>> Completion
> >>>>>> Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed:
> >>>>>> 2.5GT/s,
> >>>>>> EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB 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
> >>>>>> c1-a5-f3-ff-fe-a9-85-30
> >>>>>>
> >>>>>>> So maybe due to this (i'm not sure), rt2800pci only enables the 2.4
> >>>>>>> Ghz
> >>>>>
> >>>>> band support:
> >>>>>> Your device does not look like a real RT5592 chip.
> >>>>>>
> >>>>>>> All this with kernel 3.18 (openwrt 15.05 Chaos Calmer).
> >>>>>>> Any ideas?
> >>>>>>
> >>>>>> OpenWrt brings _a lot of_ code out upstream kernel.
> >>>>>> Who knows what is running.
> >>>>>
> >>>>> --
> >>>>> To unsubscribe from this list: send the line "unsubscribe
> >>>>> linux-wireless"
> >>>>> in the body of a message to majordomo@vger.kernel.org
> >>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-wireless"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Ralink RT5592 5Ghz capability not working
2015-11-03 21:44 ` Alberto Mattea
@ 2015-11-03 21:49 ` Alberto Mattea
2015-11-03 21:50 ` Gertjan van Wingerde
1 sibling, 0 replies; 13+ messages in thread
From: Alberto Mattea @ 2015-11-03 21:49 UTC (permalink / raw)
To: Gertjan van Wingerde; +Cc: Alexis Green, linux-wireless
In data mar 3 novembre 2015 22:44:00, Alberto Mattea ha scritto:
> Hey,
>
> I didn't have to, it was recognized this way out of the box.
> I had to install an eeprom for the other onboard chip though (5390).
Oh and I just found this in lsmod:
eeprom_93cx6 1616 1 rt2800pci
So it seems it's getting the eeprom by itself
>
> In data mar 3 novembre 2015 22:33:19, Gertjan van Wingerde ha scritto:
> > Did you have to install an eeprom file for the RT5592 PCI device?
> >
> > If yes, this eeprom file could be the problem. As far as I can tell the
> > rt2x00 driver only enables the 2.4 GHz band because it determines that
> > the RF chip doesn't support the 5GHz band. The RF chip is determined
> > from the EEPROM, and is currently read as an RF2820 chip (the message
> > rt2x00_set_rf: Info - RF chipset 0001 detected)
> >
> > ---
> > Gertjan.
> >
> > On 11/03/15 22:07, Alberto Mattea wrote:
> > > I found the FCC photos for the RP-N53:
> > > https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=2001985
> > >
> > > On page 9 there is a photo of the ralink chip, unfortunately very
> > > blurred.
> > > But I also found the photos for the Buffalo WHR-600D (which exhibits the
> > > same behaviour):
> > > https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=1950610
> > > Here (page 12) we can clearly read "RT5692N", and if we look closer
> > > that's
> > > the same number you can see on the RP-N53. That's a model I cannot find
> > > anywhere. So it seems some kind of OEM specific chip.
> > >
> > > In data mar 3 novembre 2015 11:31:42, hai scritto:
> > >> All signs point to RT5592 not supported by rt2x00 driver... I'm
> > >> guessing they fudged pci id for some internal reasons (maybe even to
> > >> mess with OpenWRT people).
> > >>
> > >> On Tue, Nov 3, 2015 at 11:09 AM, Alberto Mattea <alberto@mattea.info>
>
> wrote:
> > >>> My device (the RP-N53) has 2 chips too: the other is integrated in the
> > >>> mt7620 soc and reports itself as
> > >>>
> > >>> [ 14.120000] ieee80211 phy1: rt2x00lib_request_eeprom_file: Info -
> > >>> Loading EEPROM data from 'soc_wmac.eeprom'. [ 14.140000] ieee80211
> > >>> phy1: rt2x00_set_rt: Info - RT chipset 5390, rev 0500 detected [
> > >>> 14.150000] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620
> > >>> detected
> > >>> [ 14.170000] ieee80211 phy1: Selected rate control algorithm
> > >>> 'minstrel_ht'
> > >>>
> > >>> it is used for 2.4Ghz only (https://wikidevi.com/wiki/ASUS_RP-N53)
> > >>> Unfortunately opening the RP-N53 appears impossible without voiding
> > >>> the
> > >>> warranty :(>
> > >>>
> > >>> In data mar 3 novembre 2015 10:32:29, hai scritto:
> > >>>> This is so strange. Asus RT-N56U you mentioned earlier as one of the
> > >>>> examples actually has two separate chips for each band (and one of
> > >>>> them is RT3091) - https://wikidevi.com/wiki/ASUS_RT-N56U
> > >>>> Are you able to take a picture of the chip?
> > >>>>
> > >>>> On Tue, Nov 3, 2015 at 10:10 AM, Alberto Mattea <alberto@mattea.info>
> > >
> > > wrote:
> > >>>>> Hey, thanks for your answer. The device definitely isn't a RT3091,
> > >>>>> so
> > >>>>> do
> > >>>>> you think it's some sort of an OEM hybrid? Do you think it would be
> > >>>>> better to report this to the openwrt bugzilla?
> > >>>>>
> > >>>>> Thanks
> > >>>>>
> > >>>>> In data mar 3 novembre 2015 14:41:35, Xose Vazquez Perez ha scritto:
> > >>>>>> Alberto Mattea wrote:
> > >>>>>>> this is about the mini-pcie version used in some embedded products
> > >>>>>>> (for example the Buffalo WHR-600D and the Asus RP-N53).
> > >>>>>>> It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz
> > >>>>>>> (5Ghz works with the proprietary driver supplied with the
> > >>>>>>> devices),
> > >>>>>>> but rt2800pci seems to see only the 2.4 Ghz capability.
> > >>>>>>
> > >>>>>> As far as I know, RT5592 PCIe devices are unsupported by rt2800pci.
> > >>>>>>
> > >>>>>>> dmesg:
> > >>>>>>>
> > >>>>>>> [ 14.070000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset
> > >>>>>>> 5592,
> > >>>>>>> rev
> > >>>>>>> 0222 detected [ 14.080000] ieee80211 phy0: rt2x00_set_rf: Info -
> > >>>>>>> RF
> > >>>>>>> chipset 0001 detected [ 14.100000] ieee80211 phy0: Selected rate
> > >>>>>>> control algorithm 'minstrel_ht' [ 134.420000] ieee80211 phy0:
> > >>>>>>> rt2x00lib_request_firmware: Info - Loading firmware file
> > >>>>>>> 'rt2860.bin' [
> > >>>>>>> 134.460000] ieee80211 phy0: rt2x00lib_request_firmware: Info -
> > >>>>>>> Firmware
> > >>>>>>> detected - version: 0.34
> > >>>>>>
> > >>>>>> Here is the output of a real RT5592 PCIe device with rt2800pci
> > >>>>>> driver(Feb
> > >>>>>> 2013):
> > >>>>>>
> > >>>>>> phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 5592, rf:
> > >>>>>> 000f,
> > >>>>>> rev:
> > >>>>>> 0222. phy1 -> rt2800_init_eeprom: Error - Invalid RT chipset 0x5592
> > >>>>>> detected. phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate
> > >>>>>> device.
> > >>>>>>
> > >>>>>>> The weird thing is that in lspci it is reported as an RT3091, due
> > >>>>>>> to
> > >>>>>>> the
> > >>>>>>> 0x3091 pci device id:
> > >>>>>>>
> > >>>>>>> 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]
> > >>>>>>>
> > >>>>>>> [...]
> > >>>>>>
> > >>>>>> 06:00.0 Network controller [0280]: Ralink corp. Device [1814:5592]
> > >>>>>>
> > >>>>>> Subsystem: ASUSTeK Computer Inc. Device [1043:851a]
> > >>>>>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > >>>>>> ParErr-
> > >>>>>>
> > >>>>>> Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B-
> > >>>>>> ParErr-
> > >>>>>> DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency:
> > >>>>>> 0,
> > >>>>>> Cache Line Size: 64 bytes
> > >>>>>>
> > >>>>>> Interrupt: pin A routed to IRQ 11
> > >>>>>> Region 0: Memory at fe500000 (32-bit, non-prefetchable)
> > >>>>>> [size=64K]
> > >>>>>> 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
> > >>>>>>
> > >>>>>> <512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+
> > >>>>>> FLReset-
> > >>>>>> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
> > >>>>>> RlxdOrd-
> > >>>>>> ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes,
> > >>>>>> MaxReadReq
> > >>>>>> 128
> > >>>>>> bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
> > >>>>>> TransPend-
> > >>>>>> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
> > >>>>>> <512ns,
> > >>>>>> L1 <64us ClockPM+ Surprise- LLActRep- BwNot-
> > >>>>>>
> > >>>>>> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled-
> > >>>>>> Retrain-
> > >>>>>>
> > >>>>>> 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+ DevCtl2:
> > >>>>>> Completion
> > >>>>>> Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed:
> > >>>>>> 2.5GT/s,
> > >>>>>> EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB 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
> > >>>>>> c1-a5-f3-ff-fe-a9-85-30
> > >>>>>>
> > >>>>>>> So maybe due to this (i'm not sure), rt2800pci only enables the
> > >>>>>>> 2.4
> > >>>>>>> Ghz
> > >>>>>
> > >>>>> band support:
> > >>>>>> Your device does not look like a real RT5592 chip.
> > >>>>>>
> > >>>>>>> All this with kernel 3.18 (openwrt 15.05 Chaos Calmer).
> > >>>>>>> Any ideas?
> > >>>>>>
> > >>>>>> OpenWrt brings _a lot of_ code out upstream kernel.
> > >>>>>> Who knows what is running.
> > >>>>>
> > >>>>> --
> > >>>>> To unsubscribe from this list: send the line "unsubscribe
> > >>>>> linux-wireless"
> > >>>>> in the body of a message to majordomo@vger.kernel.org
> > >>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> > >
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe
> > > linux-wireless"
> > > in the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Ralink RT5592 5Ghz capability not working
2015-11-03 21:44 ` Alberto Mattea
2015-11-03 21:49 ` Alberto Mattea
@ 2015-11-03 21:50 ` Gertjan van Wingerde
1 sibling, 0 replies; 13+ messages in thread
From: Gertjan van Wingerde @ 2015-11-03 21:50 UTC (permalink / raw)
To: Alberto Mattea; +Cc: Alexis Green, linux-wireless
OK. Too bad.
Anyway, this EEPROM RF chipset detection is the part where needs to be
looked at. At least that's where rt2x00 is deciding that the HW doesn't
support 5GHz.
On 11/03/15 22:44, Alberto Mattea wrote:
> Hey,
>
> I didn't have to, it was recognized this way out of the box.
> I had to install an eeprom for the other onboard chip though (5390).
>
> In data mar 3 novembre 2015 22:33:19, Gertjan van Wingerde ha scritto:
>> Did you have to install an eeprom file for the RT5592 PCI device?
>>
>> If yes, this eeprom file could be the problem. As far as I can tell the
>> rt2x00 driver only enables the 2.4 GHz band because it determines that
>> the RF chip doesn't support the 5GHz band. The RF chip is determined
>> from the EEPROM, and is currently read as an RF2820 chip (the message
>> rt2x00_set_rf: Info - RF chipset 0001 detected)
>>
>> ---
>> Gertjan.
>>
>> On 11/03/15 22:07, Alberto Mattea wrote:
>>> I found the FCC photos for the RP-N53:
>>> https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=2001985
>>>
>>> On page 9 there is a photo of the ralink chip, unfortunately very blurred.
>>> But I also found the photos for the Buffalo WHR-600D (which exhibits the
>>> same behaviour):
>>> https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=1950610
>>> Here (page 12) we can clearly read "RT5692N", and if we look closer that's
>>> the same number you can see on the RP-N53. That's a model I cannot find
>>> anywhere. So it seems some kind of OEM specific chip.
>>>
>>> In data mar 3 novembre 2015 11:31:42, hai scritto:
>>>> All signs point to RT5592 not supported by rt2x00 driver... I'm
>>>> guessing they fudged pci id for some internal reasons (maybe even to
>>>> mess with OpenWRT people).
>>>>
>>>> On Tue, Nov 3, 2015 at 11:09 AM, Alberto Mattea <alberto@mattea.info>
> wrote:
>>>>> My device (the RP-N53) has 2 chips too: the other is integrated in the
>>>>> mt7620 soc and reports itself as
>>>>>
>>>>> [ 14.120000] ieee80211 phy1: rt2x00lib_request_eeprom_file: Info -
>>>>> Loading EEPROM data from 'soc_wmac.eeprom'. [ 14.140000] ieee80211
>>>>> phy1: rt2x00_set_rt: Info - RT chipset 5390, rev 0500 detected [
>>>>> 14.150000] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620
>>>>> detected
>>>>> [ 14.170000] ieee80211 phy1: Selected rate control algorithm
>>>>> 'minstrel_ht'
>>>>>
>>>>> it is used for 2.4Ghz only (https://wikidevi.com/wiki/ASUS_RP-N53)
>>>>> Unfortunately opening the RP-N53 appears impossible without voiding the
>>>>> warranty :(>
>>>>>
>>>>> In data mar 3 novembre 2015 10:32:29, hai scritto:
>>>>>> This is so strange. Asus RT-N56U you mentioned earlier as one of the
>>>>>> examples actually has two separate chips for each band (and one of
>>>>>> them is RT3091) - https://wikidevi.com/wiki/ASUS_RT-N56U
>>>>>> Are you able to take a picture of the chip?
>>>>>>
>>>>>> On Tue, Nov 3, 2015 at 10:10 AM, Alberto Mattea <alberto@mattea.info>
>>>
>>> wrote:
>>>>>>> Hey, thanks for your answer. The device definitely isn't a RT3091, so
>>>>>>> do
>>>>>>> you think it's some sort of an OEM hybrid? Do you think it would be
>>>>>>> better to report this to the openwrt bugzilla?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> In data mar 3 novembre 2015 14:41:35, Xose Vazquez Perez ha scritto:
>>>>>>>> Alberto Mattea wrote:
>>>>>>>>> this is about the mini-pcie version used in some embedded products
>>>>>>>>> (for example the Buffalo WHR-600D and the Asus RP-N53).
>>>>>>>>> It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz
>>>>>>>>> (5Ghz works with the proprietary driver supplied with the devices),
>>>>>>>>> but rt2800pci seems to see only the 2.4 Ghz capability.
>>>>>>>>
>>>>>>>> As far as I know, RT5592 PCIe devices are unsupported by rt2800pci.
>>>>>>>>
>>>>>>>>> dmesg:
>>>>>>>>>
>>>>>>>>> [ 14.070000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset
>>>>>>>>> 5592,
>>>>>>>>> rev
>>>>>>>>> 0222 detected [ 14.080000] ieee80211 phy0: rt2x00_set_rf: Info -
>>>>>>>>> RF
>>>>>>>>> chipset 0001 detected [ 14.100000] ieee80211 phy0: Selected rate
>>>>>>>>> control algorithm 'minstrel_ht' [ 134.420000] ieee80211 phy0:
>>>>>>>>> rt2x00lib_request_firmware: Info - Loading firmware file
>>>>>>>>> 'rt2860.bin' [
>>>>>>>>> 134.460000] ieee80211 phy0: rt2x00lib_request_firmware: Info -
>>>>>>>>> Firmware
>>>>>>>>> detected - version: 0.34
>>>>>>>>
>>>>>>>> Here is the output of a real RT5592 PCIe device with rt2800pci
>>>>>>>> driver(Feb
>>>>>>>> 2013):
>>>>>>>>
>>>>>>>> phy1 -> rt2x00_set_chip: Info - Chipset detected - rt: 5592, rf:
>>>>>>>> 000f,
>>>>>>>> rev:
>>>>>>>> 0222. phy1 -> rt2800_init_eeprom: Error - Invalid RT chipset 0x5592
>>>>>>>> detected. phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate
>>>>>>>> device.
>>>>>>>>
>>>>>>>>> The weird thing is that in lspci it is reported as an RT3091, due to
>>>>>>>>> the
>>>>>>>>> 0x3091 pci device id:
>>>>>>>>>
>>>>>>>>> 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]
>>>>>>>>>
>>>>>>>>> [...]
>>>>>>>>
>>>>>>>> 06:00.0 Network controller [0280]: Ralink corp. Device [1814:5592]
>>>>>>>>
>>>>>>>> Subsystem: ASUSTeK Computer Inc. Device [1043:851a]
>>>>>>>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
>>>>>>>> ParErr-
>>>>>>>>
>>>>>>>> Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B-
>>>>>>>> ParErr-
>>>>>>>> DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency:
>>>>>>>> 0,
>>>>>>>> Cache Line Size: 64 bytes
>>>>>>>>
>>>>>>>> Interrupt: pin A routed to IRQ 11
>>>>>>>> Region 0: Memory at fe500000 (32-bit, non-prefetchable)
>>>>>>>> [size=64K]
>>>>>>>> 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
>>>>>>>>
>>>>>>>> <512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
>>>>>>>> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
>>>>>>>> RlxdOrd-
>>>>>>>> ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq
>>>>>>>> 128
>>>>>>>> bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr-
>>>>>>>> TransPend-
>>>>>>>> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
>>>>>>>> <512ns,
>>>>>>>> L1 <64us ClockPM+ Surprise- LLActRep- BwNot-
>>>>>>>>
>>>>>>>> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled-
>>>>>>>> Retrain-
>>>>>>>>
>>>>>>>> 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+ DevCtl2:
>>>>>>>> Completion
>>>>>>>> Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed:
>>>>>>>> 2.5GT/s,
>>>>>>>> EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB 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
>>>>>>>> c1-a5-f3-ff-fe-a9-85-30
>>>>>>>>
>>>>>>>>> So maybe due to this (i'm not sure), rt2800pci only enables the 2.4
>>>>>>>>> Ghz
>>>>>>>
>>>>>>> band support:
>>>>>>>> Your device does not look like a real RT5592 chip.
>>>>>>>>
>>>>>>>>> All this with kernel 3.18 (openwrt 15.05 Chaos Calmer).
>>>>>>>>> Any ideas?
>>>>>>>>
>>>>>>>> OpenWrt brings _a lot of_ code out upstream kernel.
>>>>>>>> Who knows what is running.
>>>>>>>
>>>>>>> --
>>>>>>> To unsubscribe from this list: send the line "unsubscribe
>>>>>>> linux-wireless"
>>>>>>> in the body of a message to majordomo@vger.kernel.org
>>>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless"
>>> in the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
---
Gertjan
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Ralink RT5592 5Ghz capability not working
2015-11-03 18:10 ` Alberto Mattea
2015-11-03 18:32 ` Alexis Green
@ 2015-11-03 20:39 ` Xose Vazquez Perez
1 sibling, 0 replies; 13+ messages in thread
From: Xose Vazquez Perez @ 2015-11-03 20:39 UTC (permalink / raw)
To: Alberto Mattea, linux-wireless; +Cc: Stanislaw Gruszka
On 11/03/2015 07:10 PM, Alberto Mattea wrote:
> Hey, thanks for your answer. The device definitely isn't a RT3091, so do you
> think it's some sort of an OEM hybrid?
I don't know. Open the device or look for photos at FCC site.
wikidevi.com usually has links to it.
> Do you think it would be better to report this to the openwrt bugzilla?
Yes.
As you can see, *OpenWrt doesn't run a standard Linux kernel* :
-rw------- 1 xose xose 633 Nov 3 21:10 000-fix_kconfig.patch
-rw------- 1 xose xose 5634 Nov 3 21:10 001-fix_build.patch
-rw------- 1 xose xose 1651 Nov 3 21:10 002-change_allconfig.patch
-rw------- 1 xose xose 1188 Nov 3 21:10 003-remove_bogus_modparams.patch
-rw------- 1 xose xose 319 Nov 3 21:10 010-disable_rfkill.patch
-rw------- 1 xose xose 875 Nov 3 21:10 030-rt2x00_options.patch
-rw------- 1 xose xose 222 Nov 3 21:10 040-brcmutil_option.patch
-rw------- 1 xose xose 622 Nov 3 21:10 050-lib80211_option.patch
-rw------- 1 xose xose 3766 Nov 3 21:10 060-no_local_ssb_bcma.patch
-rw------- 1 xose xose 391 Nov 3 21:10 070-ath_common_config.patch
-rw------- 1 xose xose 390 Nov 3 21:10 080-disable_clk_backport.patch
-rw------- 1 xose xose 10948 Nov 3 21:10 100-remove-cryptoapi-dependencies.patch
-rw------- 1 xose xose 400 Nov 3 21:10 110-mac80211_keep_keys_on_stop_ap.patch
-rw------- 1 xose xose 1292 Nov 3 21:10 120-cfg80211_allow_perm_addr_change.patch
-rw------- 1 xose xose 1906 Nov 3 21:10 150-disable_addr_notifier.patch
-rw------- 1 xose xose 1309 Nov 3 21:10 201-ath5k-WAR-for-AR71xx-PCI-bug.patch
-rw------- 1 xose xose 385 Nov 3 21:10 210-ap_scan.patch
-rw------- 1 xose xose 972 Nov 3 21:10 300-ath9k-force-rx_clear-when-disabling-rx.patch
-rw------- 1 xose xose 3643 Nov 3 21:10 301-ath9k-limit-retries-for-powersave-response-frames.patch
-rw------- 1 xose xose 4122 Nov 3 21:10 302-ath9k-fix-phyerror-codes.patch
-rw------- 1 xose xose 8493 Nov 3 21:10 303-ath10k-enable-adaptive-CCA.patch
-rw------- 1 xose xose 9188 Nov 3 21:10 304-ath10k-add-FW-API-support-to-test-mode.patch
-rw------- 1 xose xose 14220 Nov 3 21:10 305-ath10k-add-fw_stats-support-to-10.4-firmware.patch
-rw------- 1 xose xose 2173 Nov 3 21:10 306-ath10k-use-local-memory-instead-of-shadow-descriptor.patch
-rw------- 1 xose xose 1195 Nov 3 21:10 307-ath10k-remove-send-completion-validation-in-diag-rea.patch
-rw------- 1 xose xose 5688 Nov 3 21:10 308-ath10k-cleanup-copy-engine-send-completion.patch
-rw------- 1 xose xose 2829 Nov 3 21:10 309-ath10k-remove-shadow-copy-of-CE-descriptors-for-sour.patch
-rw------- 1 xose xose 2474 Nov 3 21:10 310-ath10k-remove-supported-chain-mask.patch
-rw------- 1 xose xose 1305 Nov 3 21:10 311-ath10k-fill-HT-VHT-MCS-rateset-only-for-configured-c.patch
-rw------- 1 xose xose 8563 Nov 3 21:10 312-ath10k-move-static-HT-VHT-capability-setup-functions.patch
-rw------- 1 xose xose 1337 Nov 3 21:10 313-mac80211-fix-crash-on-mesh-local-link-ID-generation-.patch
-rw------- 1 xose xose 795 Nov 3 21:10 400-ath_move_debug_code.patch
-rw------- 1 xose xose 432 Nov 3 21:10 401-ath9k_blink_default.patch
-rw------- 1 xose xose 1562 Nov 3 21:10 402-ath_regd_optional.patch
-rw------- 1 xose xose 2131 Nov 3 21:10 403-world_regd_fixup.patch
-rw------- 1 xose xose 551 Nov 3 21:10 404-regd_no_assoc_hints.patch
-rw------- 1 xose xose 976 Nov 3 21:10 405-ath_regd_us.patch
-rw------- 1 xose xose 1171 Nov 3 21:10 406-ath_relax_default_regd.patch
-rw------- 1 xose xose 391 Nov 3 21:10 410-ath9k_allow_adhoc_and_ap.patch
-rw------- 1 xose xose 1836 Nov 3 21:10 411-ath5k_allow_adhoc_and_ap.patch
-rw------- 1 xose xose 476 Nov 3 21:10 420-ath5k_disable_fast_cc.patch
-rw------- 1 xose xose 1263 Nov 3 21:10 430-add_ath5k_platform.patch
-rw------- 1 xose xose 1398 Nov 3 21:10 431-add_platform_eeprom_support_to_ath5k.patch
-rw------- 1 xose xose 514 Nov 3 21:10 432-ath5k_add_pciids.patch
-rw------- 1 xose xose 4024 Nov 3 21:10 440-ath5k_channel_bw_debugfs.patch
-rw------- 1 xose xose 1718 Nov 3 21:10 500-ath9k_eeprom_debugfs.patch
-rw------- 1 xose xose 650 Nov 3 21:10 501-ath9k_ahb_init.patch
-rw------- 1 xose xose 507 Nov 3 21:10 510-ath9k_intr_mitigation_tweak.patch
-rw------- 1 xose xose 407 Nov 3 21:10 511-ath9k_reduce_rxbuf.patch
-rw------- 1 xose xose 3555 Nov 3 21:10 512-ath9k_channelbw_debugfs.patch
-rw------- 1 xose xose 932 Nov 3 21:10 513-ath9k_add_pci_ids.patch
-rw------- 1 xose xose 5378 Nov 3 21:10 522-mac80211_configure_antenna_gain.patch
-rw------- 1 xose xose 6653 Nov 3 21:10 530-ath9k_extra_leds.patch
-rw------- 1 xose xose 1564 Nov 3 21:10 531-ath9k_extra_platform_leds.patch
-rw------- 1 xose xose 354 Nov 3 21:10 540-ath9k_reduce_ani_interval.patch
-rw------- 1 xose xose 819 Nov 3 21:10 541-ath9k_rx_dma_stop_check.patch
-rw------- 1 xose xose 3967 Nov 3 21:10 542-ath9k_debugfs_diag.patch
-rw------- 1 xose xose 6001 Nov 3 21:10 543-ath9k_entropy_from_adc.patch
-rw------- 1 xose xose 2115 Nov 3 21:10 544-ath9k-ar933x-usb-hang-workaround.patch
-rw------- 1 xose xose 5452 Nov 3 21:10 545-ath9k_ani_ws_detect.patch
-rw------- 1 xose xose 1826 Nov 3 21:10 600-0001-rt2x00-rt2800lib-move-rt2800_drv_data-declaration-in.patch
-rw------- 1 xose xose 2297 Nov 3 21:10 600-0002-rt2x00-rt2800lib-introduce-RT2800_HAS_HIGH_SHARED_ME.patch
-rw------- 1 xose xose 17759 Nov 3 21:10 600-0003-rt2x00-rt2800-serialize-shared-memory-access.patch
-rw------- 1 xose xose 4113 Nov 3 21:10 600-0004-rt2x00-rt2800lib-fix-beacon-generation-on-RT3593.patch
-rw------- 1 xose xose 1967 Nov 3 21:10 600-0005-rt2x00-rt2800lib-add-hw_beacon_count-field-to-struct.patch
-rw------- 1 xose xose 2455 Nov 3 21:10 600-0006-rt2x00-rt2800lib-init-additional-beacon-offset-regis.patch
-rw------- 1 xose xose 821 Nov 3 21:10 600-0007-rt2x00-rt2800lib-fix-max-supported-beacon-count-for-.patch
-rw------- 1 xose xose 933 Nov 3 21:10 600-0008-rt2x00-allow-to-build-rt2800soc-module-for-RT3883.patch
-rw------- 1 xose xose 606 Nov 3 21:10 600-0009-rt2x00-rt2800lib-enable-support-for-RT3883.patch
-rw------- 1 xose xose 2885 Nov 3 21:10 600-0010-rt2x00-rt2800lib-add-rf_vals-for-RF3853.patch
-rw------- 1 xose xose 783 Nov 3 21:10 600-0011-rt2x00-rt2800lib-enable-VCO-calibration-for-RF3853.patch
-rw------- 1 xose xose 6225 Nov 3 21:10 600-0012-rt2x00-rt2800lib-add-channel-configuration-function-.patch
-rw------- 1 xose xose 601 Nov 3 21:10 600-0013-rt2x00-rt2800lib-enable-RF3853-support.patch
-rw------- 1 xose xose 2906 Nov 3 21:10 600-0014-rt2x00-rt2800lib-add-MAC-register-initialization-for.patch
-rw------- 1 xose xose 1000 Nov 3 21:10 600-0015-rt2x00-rt2800soc-fix-rt2800soc_disable_radio-for-RT3.patch
-rw------- 1 xose xose 2302 Nov 3 21:10 600-0016-rt2x00-rt2800lib-add-BBP-register-initialization-for.patch
-rw------- 1 xose xose 6052 Nov 3 21:10 600-0017-rt2x00-rt2800lib-add-RFCSR-initialization-for-RT3883.patch
-rw------- 1 xose xose 771 Nov 3 21:10 600-0018-rt2x00-rt2800lib-use-the-extended-EEPROM-map-for-RT3.patch
-rw------- 1 xose xose 767 Nov 3 21:10 600-0019-rt2x00-rt2800lib-force-rf-type-to-RF3853-on-RT3883.patch
-rw------- 1 xose xose 4325 Nov 3 21:10 600-0020-rt2x00-rt2800lib-add-channel-configuration-code-for-.patch
-rw------- 1 xose xose 1053 Nov 3 21:10 600-0021-rt2x00-rt2800lib-fix-txpower_to_dev-function-for-RT3.patch
-rw------- 1 xose xose 855 Nov 3 21:10 600-0022-rt2x00-rt2800lib-use-correct-txpower-calculation-fun.patch
-rw------- 1 xose xose 1020 Nov 3 21:10 600-0023-rt2x00-rt2800lib-hardcode-txmixer-gain-values-to-zer.patch
-rw------- 1 xose xose 662 Nov 3 21:10 600-0024-rt2x00-rt2800lib-use-correct-RT-XWI-size-for-RT3883.patch
-rw------- 1 xose xose 811 Nov 3 21:10 600-0025-rt2x00-rt2800lib-use-correct-beacon-base-for-RT3883.patch
-rw------- 1 xose xose 820 Nov 3 21:10 600-0026-rt2x00-rt2800lib-use-correct-beacon-count-for-RT3883.patch
-rw------- 1 xose xose 804 Nov 3 21:10 600-0027-rt2x00-rt2800lib-fix-antenna-configuration-for-RT388.patch
-rw------- 1 xose xose 1315 Nov 3 21:10 600-0028-rt2x00-rt2800lib-fix-LNA-gain-configuration-for-RT38.patch
-rw------- 1 xose xose 1434 Nov 3 21:10 600-0029-rt2x00-rt2800lib-fix-VGC-setup-for-RT3883.patch
-rw------- 1 xose xose 1984 Nov 3 21:10 600-0030-rt2x00-rt2800lib-fix-EEPROM-LNA-validation-for-RT388.patch
-rw------- 1 xose xose 762 Nov 3 21:10 600-0031-rt2x00-rt2800lib-fix-txpower-compensation-for-RT3883.patch
-rw------- 1 xose xose 790 Nov 3 21:10 600-0032-rt2x00-rt2800lib-enable-RT2800_HAS_HIGH_SHARED_MEM-f.patch
-rw------- 1 xose xose 754 Nov 3 21:10 600-0033-rt2x00-rt2800lib-use-high-memory-for-beacons-on-RT38.patch
-rw------- 1 xose xose 4107 Nov 3 21:10 600-0034-rt2x00-rt2800mmio-add-a-workaround-for-spurious-TX_F.patch
-rw------- 1 xose xose 395 Nov 3 21:10 601-rt2x00-set_pci_mwi.patch
-rw------- 1 xose xose 796 Nov 3 21:10 602-rt2x00-introduce-rt2x00_platform_h.patch
-rw------- 1 xose xose 8259 Nov 3 21:10 603-rt2x00-introduce-rt2x00eeprom.patch
-rw------- 1 xose xose 820 Nov 3 21:10 604-rt2x00-of_load_eeprom_filename.patch
-rw------- 1 xose xose 2754 Nov 3 21:10 605-rt2x00-load-eeprom-on-SoC-from-a-mtd-device-defines-.patch
-rw------- 1 xose xose 1309 Nov 3 21:10 607-rt2x00-allow_disabling_bands_through_platform_data.patch
-rw------- 1 xose xose 1827 Nov 3 21:10 608-add_platform_data_mac_addr.patch
-rw------- 1 xose xose 915 Nov 3 21:10 609-rt2x00-allow_disabling_bands_through_dts.patch
-rw------- 1 xose xose 7328 Nov 3 21:10 610-rt2x00-fix-rt3352-ext-pa.patch
-rw------- 1 xose xose 2826 Nov 3 21:10 611-rt2x00-rf_vals-rt3352-xtal20.patch
-rw------- 1 xose xose 1049 Nov 3 21:10 612-rt2x00-make-wmac-loadable-via-OF-on-rt288x-305x-SoC.patch
-rw------- 1 xose xose 756 Nov 3 21:10 615-rt2x00-fix_20mhz_clk.patch
-rw------- 1 xose xose 9306 Nov 3 21:10 616-rt2x00-support-rt5350.patch
-rw------- 1 xose xose 1282 Nov 3 21:10 619-rt2x00-change-led-polarity-from-OF.patch
-rw------- 1 xose xose 455 Nov 3 21:10 620-rt2x00-add-AP+STA-support.patch
-rw------- 1 xose xose 570 Nov 3 21:10 620-rt2x00-rt3352-rf-id.patch
-rw------- 1 xose xose 1179 Nov 3 21:10 621-rt2x00-ht20_40_fix.patch
-rw------- 1 xose xose 497 Nov 3 21:10 700-mwl8k-missing-pci-id-for-WNR854T.patch
-rw------- 1 xose xose 565 Nov 3 21:10 801-libertas-configure-sysfs-links.patch
-rw------- 1 xose xose 419 Nov 3 21:10 802-libertas-set-wireless-macaddr.patch
-rw------- 1 xose xose 1369 Nov 3 21:10 805-b43-gpio-mask-module-option.patch
-rw------- 1 xose xose 2201 Nov 3 21:10 810-b43_no_pio.patch
-rw------- 1 xose xose 4105 Nov 3 21:10 820-b43-add-antenna-control.patch
-rw------- 1 xose xose 418 Nov 3 21:10 841-b43-reduce-number-of-RX-slots.patch
-rw------- 1 xose xose 677 Nov 3 21:10 845-b43-only-use-gpio-0-1-for-led.patch
-rw------- 1 xose xose 546 Nov 3 21:10 847-b43-always-take-overlapping-devs.patch
-rw------- 1 xose xose 1199 Nov 3 21:10 850-brcmsmac-remove-extra-regulation-restriction.patch
-rw------- 1 xose xose 2907 Nov 3 21:10 861-brcmfmac-register-wiphy-s-during-module_init.patch
-rw------- 1 xose xose 1832 Nov 3 21:10 862-brcmfmac-workaround-bug-with-some-inconsistent-BSSes.patch
-rw------- 1 xose xose 625 Nov 3 21:10 910-00-rt2x00-enable-rt2800soc-for-mt7620.patch
-rw------- 1 xose xose 43738 Nov 3 21:10 910-01-add-support-for-mt7620.patch
-rw------- 1 xose xose 1226 Nov 3 21:10 921-ath10k_init_devices_synchronously.patch
-rw------- 1 xose xose 1330 Nov 3 21:10 930-ath10k_add_tpt_led_trigger.patch
-rw------- 1 xose xose 493 Nov 3 21:10 940-mwl8k_init_devices_synchronously.patch
and this is _only_ openwrt/package/kernel/mac80211/patches/*
There are a lot of patches missing at upstream.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Ralink RT5592 5Ghz capability not working
@ 2015-11-02 21:39 Alberto Mattea
[not found] ` <CAAnMG+OrVa8VBQjAeaNDSo42e+KeYr2AidnCT2z2Hf69ZLgoVQ@mail.gmail.com>
0 siblings, 1 reply; 13+ messages in thread
From: Alberto Mattea @ 2015-11-02 21:39 UTC (permalink / raw)
To: linux-wireless
Hello,
this is about the mini-pcie version used in some embedded products (for example the Buffalo WHR-600D and the Asus RP-N53).
It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz (5Ghz works with the proprietary driver supplied with the devices), but rt2800pci seems to see only the 2.4 Ghz capability.
dmesg:
[ 14.070000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
[ 14.080000] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0001 detected
[ 14.100000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 134.420000] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
[ 134.460000] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34
The weird thing is that in lspci it is reported as an RT3091, due to the 0x3091 pci device id:
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- <MAbort- >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=64K]
Region 1: Memory at <unassigned> (32-bit, non-prefetchable) [size=2]
Region 2: Memory at <unassigned> (32-bit, non-prefetchable) [size=2]
Region 3: Memory at <unassigned> (32-bit, non-prefetchable) [size=2]
Region 4: Memory at <unassigned> (32-bit, non-prefetchable) [size=2]
Region 5: Memory at <unassigned> (32-bit, non-prefetchable) [size=2]
Expansion ROM at <unassigned> [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-
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
So maybe due to this (i'm not sure), rt2800pci only enables the 2.4 Ghz band support:
# iw phy0 info
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* WDS
* monitor
* mesh point
Band 1:
Capabilities: 0x272
HT20/HT40
Static SM Power Save
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
All this with kernel 3.18 (openwrt 15.05 Chaos Calmer).
Any ideas?
Thanks
Alberto Mattea
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2015-11-03 21:50 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-03 13:41 Ralink RT5592 5Ghz capability not working Xose Vazquez Perez
2015-11-03 18:10 ` Alberto Mattea
2015-11-03 18:32 ` Alexis Green
2015-11-03 19:09 ` Alberto Mattea
2015-11-03 19:31 ` Alexis Green
2015-11-03 21:07 ` Alberto Mattea
2015-11-03 21:33 ` Gertjan van Wingerde
2015-11-03 21:44 ` Alberto Mattea
2015-11-03 21:49 ` Alberto Mattea
2015-11-03 21:50 ` Gertjan van Wingerde
2015-11-03 20:39 ` Xose Vazquez Perez
-- strict thread matches above, loose matches on Subject: below --
2015-11-02 21:39 Alberto Mattea
[not found] ` <CAAnMG+OrVa8VBQjAeaNDSo42e+KeYr2AidnCT2z2Hf69ZLgoVQ@mail.gmail.com>
2015-11-03 11:51 ` Alberto Mattea
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).