Hello,
I have been searching around and can't seem to find a simple solution for this. So here goes.
I had no problems setting up and connecting to my wifi until a couple of updates ago. Now I cannot connect at all. Just goes into an endless cycle of asking me for my network password and never logging on. I have no problems using a wired network connection.
Here's the particulars and thank you for helping with this!
Computer:
Asus x54c Laptop
Router
Cisco Linksys e2000
Wireless card from lshw
*-network
description: Wireless interface
product: RT5390 Wireless 802.11n 1T/1R PCIe
vendor: Ralink corp.
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlan0
version: 00
serial: 84:4b:f5:1c:54:6a
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=rt2800pci driverversion=3.2.0-23-generic firmware=0.34 latency=0 link=no multicast=yes wireless=IEEE 802.11bgn
resources: irq:17 memory:de800000-de80ffff
Info from mintwifi
-------------------------
* I. scanning WIFI PCI devices...
-- Ralink corp. RT5390 Wireless 802.11n 1T/1R PCIe
==> PCI ID = 1814:5390
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
lo no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
eth0 no wireless extensions.
-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 30:85:a9:09:ac:4b
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1258 errors:0 dropped:0 overruns:0 frame:0
TX packets:1085 errors:0 dropped:0 overruns:0 carrier:6
collisions:0 txqueuelen:1000
RX bytes:1452209 (1.4 MB) TX bytes:114754 (114.7 KB)
Interrupt:51
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:188 errors:0 dropped:0 overruns:0 frame:0
TX packets:188 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19220 (19.2 KB) TX bytes:19220 (19.2 KB)
wlan0 Link encap:Ethernet HWaddr 84:4b:f5:1c:54:6a
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
-------------------------
* V. querying DHCP...
SOLVED Can no longer connect to WiFi
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
SOLVED Can no longer connect to WiFi
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Can no longer connect to WiFi
Solved it.
Installed Wicd from the repositories, removed Network Manager and I can now connect. Evidently Wicd doesn't depend on Gnome, so the issues with the updates don't affect its function. So far so good.
Installed Wicd from the repositories, removed Network Manager and I can now connect. Evidently Wicd doesn't depend on Gnome, so the issues with the updates don't affect its function. So far so good.