Linux Mint 18.3 on CF-19 wi-fi connecting issue

[longknives]

I have installed LM 18.3 on the cf-19 mk4 and I have to cycle the wireless on & off in order for cf-19 to connect. The connection when completed works great however it does take 2 or 3 authentication prompts to complete, a bit of a PITA but do-able.

I have checked in Driver Manager and see an update of intel-microcode to version 3.20180807a.0ubunto.16.04.1, I'm leaning towards updating the microcode just might not be a good idea.

[SHEEPMAN!]

Did you run non-free drivers?....not sure how Mint does that now. Also codecs however that is handled.

Intel may be blacklisted. Read about that.

Is this a 8260 wireless card? Found to be problematic in my CF-54 MK2.

Code: Select all

$ dmesg | grep Intel
[    0.000000] Reserving Intel graphics memory at 0x00000000be000000-0x00000000bfffffff
[    0.014075] smpboot: CPU0: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz (family: 0x6, model: 0x4e, stepping: 0x3)
[    0.014119] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
[    0.932291] intel_pstate: Intel P-state driver initializing
[    1.419800] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    1.419800] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.650626] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[    3.017763] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[    3.017911] iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400)
[    3.103317] Intel(R) Wireless WiFi driver for Linux
[    3.103318] Copyright(c) 2003- 2015 Intel Corporation
[    3.184203] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
[    3.259681] input: HDA Intel PCH Headset Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
[    3.259754] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
[    3.259824] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
[    3.260845] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
[    3.260929] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
[    3.261026] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
[    3.261105] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
[    5.790025] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[    5.793633] Bluetooth: hci0: Applying Intel DDC parameters completed

This works in MX17 after deleting Network Manager. It was shutting down every so often.

[longknives]

Mine is an Intel Advanced-N 6235

[SHEEPMAN!]

Code: Select all

rfkill list

[longknives]

chris@CF-19 ~ $ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
chris@CF-19 ~ $

[SHEEPMAN!]

Did you set bios to defaults?

[longknives]

Sorry for late reply, my copy of the Linux Command Line arrived yesterday and I got a bit sidetracked.

No, I did not change the BIOS to defaults, I did install the Intel microcode update but nothing changed there. I can still connect by cycling the wireless radio switch. My Lenovo T420 connects on boot without drama.

[SHEEPMAN!]

Yeah I looked around a bit and one of the Mint guys said setting bios to defaults worked for him.

It's something I always do when installing new cards/ OS.

If ya have access to bios you can always change it back after the wireless wakes up.

[longknives]

Ok, I gave re-setting the bios to it's default state a go and that failed to alleviate the issue.

Just for giggles, I'll swap drives and see if W7 still connects normally.

edit: The W7 drive works fine. It seems like the LM 18.3 just gets confused and keeps forgetting the authentication.

[SHEEPMAN!]

On one of these machines I have some info...when I find it I will send it. It was on a version of LMDE....hmmmmm....

I have had this happen and self repair itself after several cycles. Don't hold your breath.

A battery pull reset won't hurt anything. Pull power and battery...hold on switch on for several cycles to drain stupid from mobo...plug in power only and boot to bios. F9 F10. (set to default/save)

On my CF-54 I deleted Network Manager and cured it shutting down when it felt like it.

Here's one:
lsmod | grep wl -i

$ lsmod | grep wl -i
iwldvm 155648 0
mac80211 798720 1 iwldvm
wl 6459392 0
iwlwifi 212992 1 iwldvm
cfg80211 716800 4 wl,iwlwifi,mac80211,iwldvm

wl has a bug with some cards. My CF-54 has wl blacklisted. Do a search for wl.