[rt2x00-users] RT5390, WOL and bitrate
helmut.schaa at googlemail.com
Mon Oct 17 18:56:16 EST 2011
On Sun, Oct 16, 2011 at 9:39 PM, pol kh <kh3095 at yandex.ru> wrote:
> I have some questions about RT5390 under Linux (using Debian GNU/Linux testing+unstable).
> $ lspci | grep Ralink
> 04:00.0 Network controller: Ralink corp. RT5390 [802.11 b/g/n 1T1R G-band PCI Express Single Chip]
> Is it possible somehow to turn off Wake-on-LAN on RT5390? Tried to use ethtool, but it says that my card
> doesn't support WOL. I'm using notebook and managing of WOL option in BIOS is blocked by vendor, so I
> have to find way to manage it in OS.
I didn't even know that Ralink devices are WOW capable ... So, the
driver doesn't implement
anything in this context.
> Another question concerns bitrate. I got this:
> # iwconfig
> lo no wireless extensions.
> eth0 no wireless extensions.
> wlan0 IEEE 802.11bgn ESSID:"TP-LINK"
> Mode:Managed Frequency:2.437 GHz Access Point: F4:EC:38:A5:7A:18
> Bit Rate=58.5 Mb/s Tx-Power=20 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality=70/70 Signal level=-33 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:114 Invalid misc:732 Missed beacon:0
> Sometimes bitrate is 57 Mb/s. Well, I cannot change it to bigger values. How to do this?
The bitrate is chosen dynamically. So it is recalculated for each tx frame.
Setting it to a fixed MCS rate is not possible at the moment and shouldn't
be necessary either.
> Also I got this when boot:
> # dmesg | grep rt2
> [ 3.672035] rt2800pci 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> [ 3.672045] rt2800pci 0000:04:00.0: setting latency timer to 64
> [ 3.867300] Registered led device: rt2800pci-phy0::radio
> [ 3.867335] Registered led device: rt2800pci-phy0::assoc
> [ 3.867349] Registered led device: rt2800pci-phy0::quality
> [ 17.191553] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
> What's wrong with MCU?
Not sure but since it seems to not have any side effect you can just
ignore it for
now I guess. Your hw is _not_ broken, it's a driver/hw interaction issue ...
More information about the users