I'm connected to my router just fine right now (it's actually only at 69%) but this is because my laptop is literally right next to my router (about six inches in between), however, if I so much as walk into the next room over, I lose almost all signal connection. It will drop down to around 20% - 30% and not be able to connect to the router.
I'm using a standard Comcast Xfinity router and my wireless connection works just fine if I boot up into Windows 7, so this must be a driver related issue, although I'm not entirely sure. I've searched everywhere I could for a fix, but I'm having trouble finding one.
Some of my basic info:
Any help is greatly appreciated. This issue really does make Mint on my laptop almost unusable.-------------------------
* I. scanning WIFI PCI devices...
-- Ralink corp. RT5390 Wireless 802.11n 1T/1R PCIe
==> PCI ID = 1814:5390
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
wlan0 IEEE 802.11bgn ESSID:"HOME-2D5A"
Mode:Managed Frequency:2.412 GHz Access Point: 00:1D:CD:E3:2D:58
Bit Rate=39 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=65/70 Signal level=-45 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:17 Invalid misc:37 Missed beacon:0
lo no wireless extensions.
eth1 no wireless extensions.
-------------------------
* IV. querying ifconfig...
eth1 Link encap:Ethernet HWaddr 78:e3:b5:60:98:64
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)
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:65536 Metric:1
RX packets:361 errors:0 dropped:0 overruns:0 frame:0
TX packets:361 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:36409 (36.4 KB) TX bytes:36409 (36.4 KB)
wlan0 Link encap:Ethernet HWaddr 60:d8:19:44:f5:ab
inet addr:10.0.0.11 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::62d8:19ff:fe44:f5ab/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9043 errors:0 dropped:0 overruns:0 frame:0
TX packets:7502 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9835890 (9.8 MB) TX bytes:1243900 (1.2 MB)
-------------------------
* V. querying DHCP...
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service smbd reload
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the reload(8) utility, e.g. reload smbd
RTNETLINK answers: File exists
-------------------------
* VI. querying nslookup google.com...
Server: 75.75.76.76
Address: 75.75.76.76#53
Non-authoritative answer:
Name: google.com
Address: 74.125.226.227
Name: google.com
Address: 74.125.226.228
Name: google.com
Address: 74.125.226.231
Name: google.com
Address: 74.125.226.232
Name: google.com
Address: 74.125.226.226
Name: google.com
Address: 74.125.226.224
Name: google.com
Address: 74.125.226.225
Name: google.com
Address: 74.125.226.229
Name: google.com
Address: 74.125.226.230
Name: google.com
Address: 74.125.226.238
Name: google.com
Address: 74.125.226.233
Edit: I have since narrowed this down to being an issue related to my router and my router only. It connects to any other router with ease and without any connection issue, regardless of distance (so long as the distances are within reason). After a Google search, there are some posts about this on the Comcast support forums, yet there really wasn't any answer so I'm guessing there isn't really any fix. It just seems to be a matter of Comcast's Xfinity wireless router.
If anyone knows any type of fix I'm still open for ideas.
Thanks again,
- Vinny