Seeing wireless card but not the network

[terminus]

I have this little netbook that I've been running Mint on for a few months now and have been so impressed that when I got this new Thinkpad Edge, I decided straight away to load Mint on it. Problem is, I can't seem to it to pick up the wireless signal. The wired connection is working just fine. I'm not the most linux savvy person so I know that there must be something I'm not doing or at least not doing correctly. Well I hope so at least... Well i typed this "sudo /usr/lib/linuxmint/mintWifi/mintWifi.py" command into the command line and here is what I got.

* I. scanning WIFI PCI devices...
-- Realtek Semiconductor Co., Ltd. Device 8172 (rev 10)
==> PCI ID = 10ec:8172 (rev 10)
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 802.11bgn Nickname:"rtl8191SEVA2"
Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Bit Rate:300 Mb/s
Retry:on RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=10/100 Signal level=0 dBm Noise level=-100 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 60:eb:69:0b:d9:dd
inet addr:192.168.1.8 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::62eb:69ff:fe0b:d9dd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26965 errors:0 dropped:0 overruns:0 frame:0
TX packets:5813 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11149761 (11.1 MB) TX bytes:749472 (749.4 KB)
Interrupt:28 Base address:0x4000

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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:480 (480.0 B) TX bytes:480 (480.0 B)

wlan0 Link encap:Ethernet HWaddr f0:7b:cb:9e:77:b2
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)
Interrupt:18 Memory:ffffc900010f0000-ffffc900010f0100

-------------------------
* V. querying DHCP...
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/f0:7b:cb:9e:77:b2
Sending on LPF/wlan0/f0:7b:cb:9e:77:b2
Listening on LPF/eth0/60:eb:69:0b:d9:dd
Sending on LPF/eth0/60:eb:69:0b:d9:dd
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER of 192.168.1.8 from 192.168.1.1
DHCPREQUEST of 192.168.1.8 on eth0 to 255.255.255.255 port 67
DHCPREQUEST of 192.168.1.8 on eth0 to 255.255.255.255 port 67
DHCPREQUEST of 192.168.1.8 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.8 from 192.168.1.1
bound to 192.168.1.8 -- renewal in 42696 seconds.
-------------------------
* VI. querying nslookup google.com...
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
Name: google.com
Address: 74.125.47.105
Name: google.com
Address: 74.125.47.104
Name: google.com
Address: 74.125.47.147
Name: google.com
Address: 74.125.47.103
Name: google.com
Address: 74.125.47.106
Name: google.com
Address: 74.125.47.99

I would very much appreciate any help you guys can give me. Thanks!

[richyrich]

Access Point: Not-Associated

Link Quality=10/100 Signal level=0 dBm Noise level=-100 dBm

[DrHu]

wlan0 802.11bgn Nickname:"rtl8191SEVA2"
Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Bit Rate:300 Mb/s

That is also a strange bit rate
--of course if you have a special high speed ISP router that you control, it is possible, maybe a fiber system etc..


In any case, a choice you can make

• Disable ethenet in bios, see if wireless picks up
  --if it does, check your networking setup to determine priority of devices, wired and wirless
• Troubleshoot or check Linux networking to determine how to check in ternet/wired/IP/wireless connections
  --internet search wil be quickest method..

Search query: "Linux home networking.."
http://michaelminn.com/linux/home_network/