issue with rt5390 on current

slackartist · 05-31-2016, 08:19 PM

this is on an asus laptop x55a

Code:

Module                  Size  Used by
rt2800pci               6470  0
rt2800mmio              9596  1 rt2800pci
rt2800lib              77894  2 rt2800pci,rt2800mmio
rt2x00pci               3419  1 rt2800pci
rt2x00mmio              3687  2 rt2800pci,rt2800mmio
rt2x00lib              42189  5 rt2x00pci,rt2800lib,rt2800pci,rt2800mmio,rt2x00mmio
mac80211              609190  3 rt2x00lib,rt2x00pci,rt2800lib
cfg80211              524168  2 mac80211,rt2x00lib
eeprom_93cx6            3634  1 rt2800pci
crc_ccitt               1861  1 rt2800lib
ipv6                  334857  32
fuse                   83890  3
uvcvideo               76917  0
videobuf2_vmalloc       5260  1 uvcvideo
videobuf2_memops        2011  1 videobuf2_vmalloc
videobuf2_v4l2         19966  1 uvcvideo
videobuf2_core         23302  2 uvcvideo,videobuf2_v4l2
v4l2_common             4447  1 videobuf2_v4l2
videodev              153794  4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2
joydev                 10496  0
asus_nb_wmi            11872  0
asus_wmi               19229  1 asus_nb_wmi
i2c_dev                 6188  0
sparse_keymap           4048  1 asus_wmi
coretemp                6780  0
hwmon                   4199  2 coretemp,asus_wmi
intel_rapl             11044  0
iosf_mbi                3821  1 intel_rapl
x86_pkg_temp_thermal     5609  0
intel_powerclamp        8914  0
kvm_intel             160123  0
kvm                   501407  1 kvm_intel
irqbypass               3519  1 kvm
snd_hda_codec_hdmi     39331  1
i2c_i801               16204  0
crct10dif_pclmul        5461  0
evdev                  13220  17
crc32_pclmul            3238  0
crc32c_intel           13564  0
thermal                10076  0
battery                13400  0

Code:

psmouse        00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 7 Series Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
02:00.0 Network controller: Ralink corp. RT5390 Wireless 802.11n 1T/1R PCIe
03:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10)

there were old threads that were found but none concerning exactly this one...

suspect I could find a solution once I find a better driver module to install for the rt5390 which is using the rt2800pci in kernel 4.4.11. searching to fix unstable module.

Richard Cranium · 05-31-2016, 08:22 PM

I'm stupid.

What's the issue?

slackartist · 05-31-2016, 10:59 PM

its just way too slow. though this laptop itaking a break from it will be settled eventually . and i could just use a usb i have laying around for now that work when i do pick it up again.

Nille_kungen · 06-01-2016, 05:46 PM

That chipset has been supported by the kernel driver since early 2011 and it's actually the one first chipset that ralink upstreamed support for to rt2x00.
http://rt2x00.serialmonkey.com/piper...ry/003172.html
http://www.kroah.com/log/linux/ralink.html
History aside can you post something one can grasp like how slow and what you expect and how you came to expect it.
Has it ever worked as it should? is it a regression or has it always been a bug that never got fixed?