Sager 8120 Intel Centrino N-6300 not connecting

Hello everyone,

Alright this is my first post on here and I hope I got sufficient Information for you available. I am not a complete newbie to Linux. I ran Ubuntu based Distros before but this is the first time under a Debian based Distro for me. I got a newlaptop and this one does not seem to let me get my wireless to work after multiple efforts so I hope I can find help here.

My problem: My Intel Centrino N-6300 (](http://www.intel.com/products/wireless/adapters/6300/index.htm)) does not seem to find any network connections.

My previous attempts: (Some of which required me to reinstall Suse)

  1. I installed new kernels as my first assumption was that the kernel was not supporting it. I know now that it is supported.
  2. I installed drivers from http://intellinuxwireless.org/ which was pointless.
  3. I installed backports (THat was still under Linux Mint. Same problem there.)
  4. I tried NDiswrapper without success.
  5. I checked rfkill as you can see further down below.

Alright here are some of my info’s I have collected so far. Let me know if anything is missing.

RFkill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

lspci
04:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)

lspci -n
04:00.0 0280: 8086:422b (rev 35)

dmesg | less
9.932002] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d
9.932006] iwlagn: Copyright(c) 2003-2010 Intel Corporation
9.932059] iwlagn 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
9.932067] iwlagn 0000:04:00.0: setting latency timer to 64
9.932138] iwlagn 0000:04:00.0: Detected Intel Wireless WiFi Link 6000 Series 3x3 AGN REV=0x74
9.935256] HDA Intel 0000:02:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
9.935335] alloc irq_desc for 39 on node -1
9.935339] alloc kstat_irqs on node -1
9.935352] HDA Intel 0000:02:00.1: irq 39 for MSI/MSI-X
9.935382] HDA Intel 0000:02:00.1: setting latency timer to 64
9.958127] iwlagn 0000:04:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
9.958188] alloc irq_desc for 40 on node -1
9.958191] alloc kstat_irqs on node -1
9.958211] iwlagn 0000:04:00.0: irq 40 for MSI/MSI-X
9.958439] iwlagn 0000:04:00.0: firmware: requesting iwlwifi-6000-4.ucode
9.960468] iwlagn 0000:04:00.0: loaded firmware version 9.193.4.1
10.006976] HDA Intel 0000:03:00.1: enabling device (0000 -> 0002)
10.006984] HDA Intel 0000:03:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
10.007043] alloc irq_desc for 41 on node -1
10.007045] alloc kstat_irqs on node -1
10.007053] HDA Intel 0000:03:00.1: irq 41 for MSI/MSI-X
10.007075] HDA Intel 0000:03:00.1: setting latency timer to 64

Iwconfig

wlan0
IEEE 802.11abgn ESSID off/any
Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm
Retry long limit 7 RTS thr off Fragment thr off
Encryption key off
Power Management off

IWList:
wlan0 Interface doesn’t support scanning : Network is down

Iwconfig

wlan0
IEEE 802.11abgn ESSID off/any
Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm
Retry long limit 7 RTS thr off Fragment thr off
Encryption key off
Power Management off

IWList:
wlan0 Interface doesn’t support scanning : Network is down

Hi,

That is weird, it seems that the iwlagn is well supported… maybe I am wrong.

Could you go to YaST =>Network Devices => Network Settings. Under the “Global Options” tab, click on the “User Controlled with Network Manager” button.

If it is, can you post the result of :

hwinfo --network

Thankyou for the fast response. It is turned on and this is what I get:

hwinfo --network
57: None 00.0: 10700 Loopback
[Created at net.124]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: “Loopback network interface”
Device File: lo
Link detected: yes
Config Status: cfg=no, avail=yes, need=no, active=unknown

58: None 00.0: 10701 Ethernet
[Created at net.124]
Unique ID: usDW.ndpeucax6V1
Parent ID: rBUF.q7j31i_8dj1
SysFS ID: /class/net/eth0
SysFS Device Link: /devices/pci0000:00/0000:00:1c.3/0000:08:00.0
Hardware Class: network interface
Model: “Ethernet network interface”
Driver: “r8169”
Driver Modules: “r8169”
Device File: eth0
HW Address: 00:90:f5:a8:99:55
Link detected: yes
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #28 (Ethernet controller)

59: None 00.0: 1070a WLAN
[Created at net.124]
Unique ID: AYEt.QXn1l67RSa1
Parent ID: y9sn.UbjbAl3PW1B
SysFS ID: /class/net/wlan0
SysFS Device Link: /devices/pci0000:00/0000:00:1c.0/0000:04:00.0
Hardware Class: network interface
Model: “WLAN network interface”
Driver: “iwlagn”
Driver Modules: “iwlagn”
Device File: wlan0
HW Address: 00:24:d7:03:50:70
Link detected: yes
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #26 (Network controller)

Ok, the driver seems to be loaded. So, it is not a driver problem.

Since knetwork manager is working, when you click on it on the tray, you click on your ssid on did you entered the encryption key correctly ?

In root, can you post the result of this :

iwlist scan

Another note. The odd thing is that it gives me the option to Create a Wireless connection but even if I do that with the correct information it won’t connect. Nor does it show any networks when I scan for them. Thank you already for all the effort you put into this. I spend the past weeks trying to fiddle around with this on multiple distros. I truely wouldlike opensuse to run as it seems to be a fascinating distro. I also speak german if that helps any of you.

It won’t even show any SSID’s for me. Not even if I scan for them. I can manually create a connection but that doesn’t work.

linux-55zh:~ # iwlist scan
lo Interface doesn’t support scanning.

eth0 Interface doesn’t support scanning.

wlan0 Interface doesn’t support scanning : Network is down

hummm…

And what give in root :

iwconfig

Sorry, no german for me… :wink:

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11abgn ESSIDoff/any
Mode:Managed Access Point Not-Associated Tx-Power=15 dBm
Retry long limit7 RTS thr off Fragment thr:off
Encryption key:off
Power Management:off

That’s no problem, I just thought I offer the additional language option. :slight_smile: Thank you for all your effort.

Are you sure the wireless is turned on on the router ? It looks like your card have no association with the wireless device…

Yes it is all turned on. My wife is even connected to it right now on her windows machine. I double checked SSid, password, security type. Everything. it’s very confusing. This is the very first time for me that I had struggled so much with Linux. Windows 7 works just fine.

Post the result please :

dmesg | grep firmware

dmesg | grep firmware
10.224423] iwlagn 0000:04:00.0: firmware: requesting iwlwifi-6000-4.ucode
10.226866] iwlagn 0000:04:00.0: loaded firmware version 9.193.4.1

Darn! The driver is loaded…

I don’t know… if you go in your admin config of your router, do you see the ip adress of another computer other than your wife’s win 7 ?

Nope. I know it is very confusing and I have absolutely nothing left I can come up with. In either case, thank you for all the effort you put into this already.

Sorry,

I’ll let experts pronounce themselves on this one. It is out of my expertise now… there are some better than me in this area.

Good luck. :slight_smile:

Thank you for all your help. Well you heard it folks, anyone has some more suggestions?

bump Anyone has any suggestions?

bump again

I checked now on multiple locations and nothing. I tried on Wep, on Wpa/Wpa2 and even on unprotected connections and nothing happens. It just seems to not be able to connect to anything although all the settings are correct. I would love to be able to replace my windows partitions with a Linux distro but without my wireless it is useless to me.
Any suggestions?

Hmm, no suggestions anyone?

I upgraded to Opensuse 11.4, nothing changed. I tried with KDE, With Gnome, x32 Bits and x64 Bits, I used Yast to manually configure it and I tried Kde Network manager as well. Nothing changed.

I out of ideas what to do. I am willing to try anything at this point. if you think you need to remote desktop to see whats off. Feel free.