You are not logged in.

Pages: 1

#1 2017-11-11 09:39:26

lamdacore
Member
Registered: 2009-11-05
Posts: 128

[Solved] Intel 6300 on 5 Ghz wifi can't connect

I am unsure when this started. I definitely could connect to 5 my router's 5 Ghz line over a month ago. (i moved and didn't have internet at the new apartment for a month)

Here is the scenario:
* Thinkpad x230 with Intel Ultimate-N 6300 3x3 AGN
* Can connect without issues to 2.4 Ghz hotspot.
* Can see 5 Ghz hotspots. Cannot connect to it.
* Configurations of the router seems correct. I can connect to the 5Ghz from my phone and my desktop also running arch (broadcom wifi card)
* The intel chip should work. I can connect to the hotspot when I reboot in windows.

wpa_supplicant errors when trying to connect to my hotspot

 
Nov 11 08:02:47 xarch wpa_supplicant[16667]: wlp3s0: Trying to associate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 11 08:02:47 xarch wpa_supplicant[16667]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=ac:9e:17:69:ee:94 status_code=18
Nov 11 08:02:47 xarch wpa_supplicant[16667]: wlp3s0: SME: Deauth request to the driver failed
Nov 11 08:02:47 xarch wpa_supplicant[16667]: wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="\xf0\x9f\x92\xa9" auth_failures=1 duration=10 reason=CONN_FAILED

dmesg

 
[20300.252188] wlp3s0: authenticate with ac:9e:17:69:ee:94
[20300.253812] wlp3s0: send auth to ac:9e:17:69:ee:94 (try 1/3)
[20300.254967] wlp3s0: authenticated
[20300.255280] wlp3s0: associate with ac:9e:17:69:ee:94 (try 1/3)
[20300.255968] wlp3s0: RX AssocResp from ac:9e:17:69:ee:94 (capab=0x1011 status=18 aid=0)
[20300.255971] wlp3s0: ac:9e:17:69:ee:94 denied association (code=18)

lspci

03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 3e)
	Subsystem: Intel Corporation Centrino Ultimate-N 6300 3x3 AGN
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

Any pointers on how to debug this would be helpful. Thanks.

Last edited by lamdacore (2017-11-12 15:41:15)

Offline

#2 2017-11-11 21:39:57

seth
Member
Registered: 2012-09-03
Posts: 51,213

Re: [Solved] Intel 6300 on 5 Ghz wifi can't connect

Nov 11 08:02:47 xarch wpa_supplicant[16667]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=ac:9e:17:69:ee:94 status_code=18

https://supportforums.cisco.com/t5/wire … -p/3148055

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2017-11-12 06:44:54

lamdacore
Member
Registered: 2009-11-05
Posts: 128

Re: [Solved] Intel 6300 on 5 Ghz wifi can't connect

Thanks for the reply. I have seen that page. I'm unsure what to do with this information though. What are you suggesting?

The router settings should be correct as I mentioned and I'm able to connect on to the ssid using the same hardware on windows.

Offline

#4 2017-11-12 08:05:34

seth
Member
Registered: 2012-09-03
Posts: 51,213

Re: [Solved] Intel 6300 on 5 Ghz wifi can't connect

Unless there's a bug in the driver/firmware this is from an attempt to eg. using 802.11a to access 802.11n or so (5GHz is used by many protocols)
Is this from a manual connection approach or networkmanager?

Also what does the entire wpa_supplicant output look like? And your configuration/connection steps?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2017-11-12 09:58:29

lamdacore
Member
Registered: 2009-11-05
Posts: 128

Re: [Solved] Intel 6300 on 5 Ghz wifi can't connect

I do not use a network manager. I am using systemd-networkd + wpa_supplicant.

My wpa_supplicant configuration is basically a list of ssid and passwords in /etc/wpa_supplicant/wpa_supplicant-wlp3s0.conf:

ctrl_interface=/run/wpa_supplicant
ctrl_interface_group=wheel
update_config=1

# normal wifi
network={
     ssid="LAN Before Time"
     psk="password"
}

My network configurations are as follows @ /etc/systemd/networkd/wlp3s0:

[Match]
Name=wlp3s0

[Network]
DHCP=yes

[DHCP]
RouteMetric=20
UseDNS=no

And so I start my networking by starting the following services: systemctl start wpa_supplicant@wlp3s0.service systemd-networkd.service


Output of  journalctl -u wpa_supplicant@wlp3s0.service -f after I restart wpa_supplicant service:

Nov 12 10:47:14 xarch systemd[1]: Started WPA supplicant daemon (interface-specific version).
Nov 12 10:47:14 xarch wpa_supplicant[10943]: Successfully initialized wpa_supplicant
Nov 12 10:47:17 xarch wpa_supplicant[10943]: wlp3s0: SME: Trying to authenticate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:47:17 xarch wpa_supplicant[10943]: wlp3s0: Trying to associate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:47:17 xarch wpa_supplicant[10943]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=ac:9e:17:69:ee:94 status_code=18
Nov 12 10:47:17 xarch wpa_supplicant[10943]: wlp3s0: SME: Deauth request to the driver failed
Nov 12 10:47:20 xarch wpa_supplicant[10943]: wlp3s0: SME: Trying to authenticate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:47:20 xarch wpa_supplicant[10943]: wlp3s0: Trying to associate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:47:20 xarch wpa_supplicant[10943]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=ac:9e:17:69:ee:94 status_code=18
Nov 12 10:47:20 xarch wpa_supplicant[10943]: wlp3s0: SME: Deauth request to the driver failed
Nov 12 10:47:24 xarch wpa_supplicant[10943]: wlp3s0: SME: Trying to authenticate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:47:24 xarch wpa_supplicant[10943]: wlp3s0: Trying to associate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:47:24 xarch wpa_supplicant[10943]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=ac:9e:17:69:ee:94 status_code=18
Nov 12 10:47:24 xarch wpa_supplicant[10943]: wlp3s0: SME: Deauth request to the driver failed
Nov 12 10:47:28 xarch wpa_supplicant[10943]: wlp3s0: SME: Trying to authenticate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:47:28 xarch wpa_supplicant[10943]: wlp3s0: Trying to associate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:47:28 xarch wpa_supplicant[10943]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=ac:9e:17:69:ee:94 status_code=18
Nov 12 10:47:28 xarch wpa_supplicant[10943]: wlp3s0: SME: Deauth request to the driver failed
Nov 12 10:47:28 xarch wpa_supplicant[10943]: wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="\xf0\x9f\x92\xa9" auth_failures=1 duration=10 reason=CONN_FAILED
Nov 12 10:47:44 xarch wpa_supplicant[10943]: wlp3s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="\xf0\x9f\x92\xa9"
Nov 12 10:47:44 xarch wpa_supplicant[10943]: wlp3s0: SME: Trying to authenticate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:47:44 xarch wpa_supplicant[10943]: wlp3s0: Trying to associate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:47:44 xarch wpa_supplicant[10943]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=ac:9e:17:69:ee:94 status_code=18
Nov 12 10:47:44 xarch wpa_supplicant[10943]: wlp3s0: SME: Deauth request to the driver failed
Nov 12 10:47:44 xarch wpa_supplicant[10943]: wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="\xf0\x9f\x92\xa9" auth_failures=2 duration=23 reason=CONN_FAILED
Nov 12 10:48:13 xarch wpa_supplicant[10943]: wlp3s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="\xf0\x9f\x92\xa9"
Nov 12 10:48:13 xarch wpa_supplicant[10943]: wlp3s0: SME: Trying to authenticate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:48:13 xarch wpa_supplicant[10943]: wlp3s0: Trying to associate with ac:9e:17:69:ee:94 (SSID='\xf0\x9f\x92\xa9' freq=5180 MHz)
Nov 12 10:48:13 xarch wpa_supplicant[10943]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=ac:9e:17:69:ee:94 status_code=18
Nov 12 10:48:13 xarch wpa_supplicant[10943]: wlp3s0: SME: Deauth request to the driver failed
Nov 12 10:48:13 xarch wpa_supplicant[10943]: wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="\xf0\x9f\x92\xa9" auth_failures=3 duration=46 reason=CONN_FAILED

For control, output when I am able to successfully connect to a 2.4 GHz hotspot:

Nov 12 10:50:22 xarch systemd[1]: Stopped WPA supplicant daemon (interface-specific version).
Nov 12 10:50:22 xarch systemd[1]: Started WPA supplicant daemon (interface-specific version).
Nov 12 10:50:22 xarch wpa_supplicant[14423]: Successfully initialized wpa_supplicant
Nov 12 10:50:25 xarch wpa_supplicant[14423]: wlp3s0: SME: Trying to authenticate with ac:9e:17:69:ee:90 (SSID='LAN Before Time' freq=2447 MHz)
Nov 12 10:50:25 xarch wpa_supplicant[14423]: wlp3s0: Trying to associate with ac:9e:17:69:ee:90 (SSID='LAN Before Time' freq=2447 MHz)
Nov 12 10:50:25 xarch wpa_supplicant[14423]: wlp3s0: Associated with ac:9e:17:69:ee:90
Nov 12 10:50:25 xarch wpa_supplicant[14423]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Nov 12 10:50:25 xarch wpa_supplicant[14423]: wlp3s0: WPA: Key negotiation completed with ac:9e:17:69:ee:90 [PTK=CCMP GTK=CCMP]
Nov 12 10:50:25 xarch wpa_supplicant[14423]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to ac:9e:17:69:ee:90 completed [id=0 id_str=]

Offline

#6 2017-11-12 13:24:26

seth
Member
Registered: 2012-09-03
Posts: 51,213

Re: [Solved] Intel 6300 on 5 Ghz wifi can't connect

Assuming wlp3s0 is phy0, compare the outputs of

iw phy0 info
sudo iw wlp3s0 scan

For the scan, oc. the malfunctioning AP is relevant.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2017-11-12 13:47:11

lamdacore
Member
Registered: 2009-11-05
Posts: 128

Re: [Solved] Intel 6300 on 5 Ghz wifi can't connect

The following are the outputs. What should I be looking for/comparing specifically

iw phy0 info:

Wiphy phy0
	max # scan SSIDs: 20
	max scan IEs length: 123 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports RSN-IBSS.
	Supported Ciphers:
		* WEP40 (00-0f-ac:1)
		* WEP104 (00-0f-ac:5)
		* TKIP (00-0f-ac:2)
		* CCMP-128 (00-0f-ac:4)
		* CCMP-256 (00-0f-ac:10)
		* GCMP-128 (00-0f-ac:8)
		* GCMP-256 (00-0f-ac:9)
	Available Antennas: TX 0 RX 0
	Supported interface modes:
		 * IBSS
		 * managed
		 * monitor
	Band 1:
		Bitrates (non-HT):
			* 1.0 Mbps
			* 2.0 Mbps (short preamble supported)
			* 5.5 Mbps (short preamble supported)
			* 11.0 Mbps (short preamble supported)
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 2412 MHz [1] (15.0 dBm)
			* 2417 MHz [2] (15.0 dBm)
			* 2422 MHz [3] (15.0 dBm)
			* 2427 MHz [4] (15.0 dBm)
			* 2432 MHz [5] (15.0 dBm)
			* 2437 MHz [6] (15.0 dBm)
			* 2442 MHz [7] (15.0 dBm)
			* 2447 MHz [8] (15.0 dBm)
			* 2452 MHz [9] (15.0 dBm)
			* 2457 MHz [10] (15.0 dBm)
			* 2462 MHz [11] (15.0 dBm)
			* 2467 MHz [12] (15.0 dBm) (no IR)
			* 2472 MHz [13] (15.0 dBm) (no IR)
	Band 2:
		Bitrates (non-HT):
			* 6.0 Mbps
			* 9.0 Mbps
			* 12.0 Mbps
			* 18.0 Mbps
			* 24.0 Mbps
			* 36.0 Mbps
			* 48.0 Mbps
			* 54.0 Mbps
		Frequencies:
			* 5180 MHz [36] (15.0 dBm) (no IR)
			* 5200 MHz [40] (15.0 dBm) (no IR)
			* 5220 MHz [44] (15.0 dBm) (no IR)
			* 5240 MHz [48] (15.0 dBm) (no IR)
			* 5260 MHz [52] (15.0 dBm) (no IR, radar detection)
			* 5280 MHz [56] (15.0 dBm) (no IR, radar detection)
			* 5300 MHz [60] (15.0 dBm) (no IR, radar detection)
			* 5320 MHz [64] (15.0 dBm) (no IR, radar detection)
			* 5500 MHz [100] (15.0 dBm) (no IR, radar detection)
			* 5520 MHz [104] (15.0 dBm) (no IR, radar detection)
			* 5540 MHz [108] (15.0 dBm) (no IR, radar detection)
			* 5560 MHz [112] (15.0 dBm) (no IR, radar detection)
			* 5580 MHz [116] (15.0 dBm) (no IR, radar detection)
			* 5600 MHz [120] (15.0 dBm) (no IR, radar detection)
			* 5620 MHz [124] (15.0 dBm) (no IR, radar detection)
			* 5640 MHz [128] (15.0 dBm) (no IR, radar detection)
			* 5660 MHz [132] (15.0 dBm) (no IR, radar detection)
			* 5680 MHz [136] (15.0 dBm) (no IR, radar detection)
			* 5700 MHz [140] (15.0 dBm) (no IR, radar detection)
			* 5745 MHz [149] (13.0 dBm) (no IR)
			* 5765 MHz [153] (13.0 dBm) (no IR)
			* 5785 MHz [157] (13.0 dBm) (no IR)
			* 5805 MHz [161] (13.0 dBm) (no IR)
			* 5825 MHz [165] (13.0 dBm) (no IR)
	Supported commands:
		 * new_interface
		 * set_interface
		 * new_key
		 * start_ap
		 * new_station
		 * new_mpath
		 * set_mesh_config
		 * set_bss
		 * authenticate
		 * associate
		 * deauthenticate
		 * disassociate
		 * join_ibss
		 * join_mesh
		 * set_tx_bitrate_mask
		 * frame
		 * frame_wait_cancel
		 * set_wiphy_netns
		 * set_channel
		 * set_wds_peer
		 * probe_client
		 * set_noack_map
		 * register_beacons
		 * start_p2p_device
		 * set_mcast_rate
		 * connect
		 * disconnect
		 * set_qos_map
		 * Unknown command (121)
	Supported TX frame types:
		 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
		 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
	Supported RX frame types:
		 * IBSS: 0x40 0xb0 0xc0 0xd0
		 * managed: 0x40 0xd0
		 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * mesh point: 0xb0 0xc0 0xd0
		 * P2P-client: 0x40 0xd0
		 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
		 * P2P-device: 0x40 0xd0
	software interface modes (can always be added):
		 * monitor
	interface combinations are not supported
	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	Device supports TX status socket option.
	Device supports HT-IBSS.
	Device supports SAE with AUTHENTICATE command
	Device supports scan flush.
	Device supports per-vif TX power setting
	Driver supports full state transitions for AP/GO clients
	Driver supports a userspace MPM
	Device supports configuring vdev MAC-addr on create.

iw wlp3s0 scan:

BSS ac:9e:17:69:ee:94(on wlp3s0)
	TSF: 100716851869 usec (1d, 03:58:36)
	freq: 5180
	beacon interval: 100 TUs
	capability: ESS Privacy SpectrumMgmt RadioMeasure (0x1111)
	signal: -46.00 dBm
	last seen: 3560 ms ago
	Information elements from Probe Response frame:
	SSID: \xf0\x9f\x92\xa9
	Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0 
	Country: DE	Environment: Indoor/Outdoor
		Channels [36 - 36] @ 23 dBm
		Channels [40 - 40] @ 23 dBm
		Channels [44 - 44] @ 23 dBm
		Channels [48 - 48] @ 23 dBm
		Channels [52 - 52] @ 23 dBm
		Channels [56 - 56] @ 23 dBm
		Channels [60 - 60] @ 23 dBm
		Channels [64 - 64] @ 23 dBm
		Channels [100 - 100] @ 30 dBm
		Channels [104 - 104] @ 30 dBm
		Channels [108 - 108] @ 30 dBm
		Channels [112 - 112] @ 30 dBm
		Channels [116 - 116] @ 30 dBm
		Channels [132 - 132] @ 30 dBm
		Channels [136 - 136] @ 30 dBm
		Channels [140 - 140] @ 30 dBm
	Power constraint: 0 dB
	TPC report: TX power: 14 dBm
	RSN:	 * Version: 1
		 * Group cipher: CCMP
		 * Pairwise ciphers: CCMP
		 * Authentication suites: PSK
		 * Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
	BSS Load:
		 * station count: 2
		 * channel utilisation: 3/255
		 * available admission capacity: 0 [*32us]
	HT capabilities:
		Capabilities: 0x9ef
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 7935 bytes
			No DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 4 usec (0x05)
		HT RX MCS rate indexes supported: 0-23
		HT TX MCS rate indexes are undefined
	HT operation:
		 * primary channel: 36
		 * secondary channel offset: above
		 * STA channel width: any
		 * RIFS: 1
		 * HT protection: no
		 * non-GF present: 1
		 * OBSS non-GF present: 0
		 * dual beacon: 0
		 * dual CTS protection: 0
		 * STBC beacon: 0
		 * L-SIG TXOP Prot: 0
		 * PCO active: 0
		 * PCO phase: 0
	Extended capabilities: Extended Channel Switching, BSS Transition, 6
	VHT capabilities:
		VHT Capabilities (0x0f8259b2):
			Max MPDU length: 11454
			Supported Channel Width: neither 160 nor 80+80
			RX LDPC
			short GI (80 MHz)
			TX STBC
			SU Beamformer
			SU Beamformee
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: MCS 0-9
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 0 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: MCS 0-9
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 0 Mbps
	VHT operation:
		 * channel width: 1 (80 MHz)
		 * center freq segment 1: 42
		 * center freq segment 2: 0
		 * VHT basic MCS set: 0x0000
	WMM:	 * Parameter version 1
		 * u-APSD
		 * BE: CW 15-1023, AIFSN 3
		 * BK: CW 15-1023, AIFSN 7
		 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
		 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec

Offline

#8 2017-11-12 15:08:49

seth
Member
Registered: 2012-09-03
Posts: 51,213

Re: [Solved] Intel 6300 on 5 Ghz wifi can't connect

The data rates, but they match.
Try passing 

11n_disable=2 swcrypto=1 disable_11ac=true

and if thet doesn't get you anywhere (and since you said it worked before) to downgrade the firmware by moving away newer iwlwifi-6000* files from /usr/lib/firmware
This is voodoo-esque poking around, I don't see why this should fail on that status.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2017-11-12 15:40:51

lamdacore
Member
Registered: 2009-11-05
Posts: 128

Re: [Solved] Intel 6300 on 5 Ghz wifi can't connect

holy crap. Playing with the "11n_disable" parameter fixes the issue. Turns out, the module was defaulting to "11n_disable=1" for some reason. I just made a file to explicitly set the parameter to 0 and I am able to use 5 Ghz at maximum throughput.

I'll investigate further why this was the default parameter though...

Thanks for your time and help!

Offline

Pages: 1

Board footer

Powered by FluxBB