Intel Wireless-N 1000

[pjgrenyer]

I've got a new Lenovo T520 laptop with an Intel Wireless-N 1000 wireless network adapter. I've installed Line Mint 12, but I can't get the wireless to behave. It's slow, compared to Windows 7 on the same machine and right now I can't even get it to connect.

Google is failing me. I thought I'd found the problem and fixed it by turning off the adapters power management, but it turns out that's not the problem.

Can anyone help, please?

The output from:

sudo /usr/lib/linuxmint/mintWifi/mintWifi.py

is:

-------------------------
* I. scanning WIFI PCI devices...
-- Intel Corporation Centrino Wireless-N 1000
==> PCI ID = 8086:0084
-------------------------
* 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=14 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

eth0 no wireless extensions.

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr f0:de:f1:ff:2b:ac
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::f2de:f1ff:feff:2bac/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:136559 errors:0 dropped:0 overruns:0 frame:0
TX packets:77062 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:192061887 (192.0 MB) TX bytes:6771392 (6.7 MB)
Interrupt:20 Memory:f2500000-f2520000

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:2100 errors:0 dropped:0 overruns:0 frame:0
TX packets:2100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:204417 (204.4 KB) TX bytes:204417 (204.4 KB)

wlan0 Link encap:Ethernet HWaddr e0:94:67:08:1f:9e
inet6 addr: fe80::e294:67ff:fe08:1f9e/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:440 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:125628 (125.6 KB)

-------------------------
* 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: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
Name: google.com
Address: 173.194.34.70
Name: google.com
Address: 173.194.34.71
Name: google.com
Address: 173.194.34.72
Name: google.com
Address: 173.194.34.73
Name: google.com
Address: 173.194.34.78
Name: google.com
Address: 173.194.34.64
Name: google.com
Address: 173.194.34.65
Name: google.com
Address: 173.194.34.66
Name: google.com
Address: 173.194.34.67
Name: google.com
Address: 173.194.34.68
Name: google.com
Address: 173.194.34.69

[travalon]

try going to their website and looking for linux drivers. Thugh I also read somewhere (a review of your hardware) another person was having the same problem

[Oscar799]

Moved here by moderator