2

I have recently upgraded to 16.04.1. This problem did not begin immediately after upgrading, rather it showed up quite a few weeks after upgrading. The issue is that the wifi connection to any network keeps getting disconnected at random. Moreover, wifi is very slow to connect to a network to begin with. After getting interrupted, it is very difficult to connect to a network again. I've browsed through MANY threads with a similar problem, but no proposed solution seems to work. Any help would be appreciated. I am a newbie on Linux, so please suggest edits and any required details.

Result of 'lspci -knn | grep Net -A2' terminal command:

07:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290]
    DeviceName: Ralink RT3290LE  802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Ad
    Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo

Adapter [103c:18ec]

Pilot6
  • 90,100
  • 91
  • 213
  • 324
Rohan Saxena
  • 163
  • Maybe this answer can be of help. – Karsus Aug 02 '16 at 11:48
  • @Karsus Why do you think s/he has an rtl8723be device? – chili555 Aug 02 '16 at 13:36
  • @chili555 It's not about the particular device but the mindset behind how the problem got solved that really helps you fix the problem. For example he can use the commands from there to find what his device is and google the particular device to see what info he can find on Ubuntu/Linux compatibility. – Karsus Aug 02 '16 at 14:46
  • Please [edit] your question and add output of lspci -knn | grep Net -A2 terminal command. – Pilot6 Aug 03 '16 at 12:39
  • @Karsus That thread does seem to be very similar to my problem. However, I am a newbie on Linux so I don't know how to create the config file in /etc/pm/config.d/config. I went to that folder on my machine and tried right-clicking and selecting 'new empty document' but that option was not allowed. How can I do this? – Rohan Saxena Aug 15 '16 at 04:54
  • @Pilot6 I have added the output as you asked. – Rohan Saxena Aug 15 '16 at 04:55
  • @RohanSaxena Try using the terminal - it's a lot more versatile. This answer describes how to do it with nano. The reason you weren't allowed is because the /etc/ folder requires root access. From the terminal you can do cd /etc/pm/config.d and then sudo nano config. – Karsus Aug 15 '16 at 12:34
  • @Karsus Thanks for the suggestion about the terminal, I learned how to use nano and will definitely keep that in mind. I tried the method that you suggested, but that does not resolve the connectivity issue. Do you have anything else in mind? – Rohan Saxena Aug 16 '16 at 11:08
  • @RohanSaxena Does that answer help? – Karsus Aug 16 '16 at 11:34

0 Answers0