Wireless not turning on after reboot.

[tek3195]

Hi, I'm running Ulyana 64bit on a newish custom build and have to toggle wireless on after each reboot. Network connections is set to automatically connect and it connects immediately upon toggling wireless switch in tray applet. I am not understanding why it is not turned on or enabled at boot. I included termbin and inxi output if helpful. I could really use the assistance with this as it is the only thing on new PC that is not working, and of course the wife is looking at me like I did something wrong in building.

Code: Select all

https://termbin.com/r969p

Code: Select all

@micro-mini:~$ inxi -Fxxxrz
System:    Kernel: 5.4.0-72-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.6.7 wm: muffin 4.6.3 
           dm: GDM3 3.36.3, LightDM 1.30.0 Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal 
Machine:   Type: Desktop Mobo: ASRock model: B365M Phantom Gaming 4 serial: <filter> UEFI: American Megatrends v: P4.30 
           date: 05/14/2020 
Battery:   Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech MX Ergo Multi-Device Trackball serial: <filter> 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: 8-Core model: Intel Core i7-9700 bits: 64 type: MCP arch: Kaby Lake rev: D L2 cache: 12.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 48000 
           Speed: 4504 MHz max: 4700 MHz Core speeds (MHz): 1: 4500 2: 4505 3: 4546 4: 4507 5: 4500 6: 4505 7: 4505 8: 4551 
Graphics:  Device-1: Intel UHD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3e98 
           Device-2: NVIDIA GM204 [GeForce GTX 970] vendor: Micro-Star MSI driver: nvidia v: 460.73.01 bus ID: 01:00.0 
           chip ID: 10de:13c2 
           Display: x11 server: X.Org 1.20.9 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 460.73.01 direct render: Yes 
Audio:     Device-1: Intel 200 Series PCH HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:a2f0 
           Device-2: NVIDIA GM204 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           chip ID: 10de:0fbb 
           Sound Server: ALSA v: k5.4.0-72-generic 
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 
           chip ID: 8086:15b8 
           IF: eno1 state: down mac: <filter> 
           Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel port: e000 bus ID: 04:00.0 
           chip ID: 8086:24fb 
           IF: wlp4s0 state: up mac: <filter> 
Drives:    Local Storage: total: 1.41 TiB used: 344.80 GiB (23.9%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 500GB size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 
           serial: <filter> rev: 2B2QEXE7 scheme: GPT 
           ID-2: /dev/sda vendor: Smart Modular Tech. model: SHGS31-1000GS-2 size: 931.51 GiB speed: 6.0 Gb/s serial: <filter> 
           rev: 0Q00 scheme: GPT 
           ID-3: /dev/sdb type: USB model: Mass Storage Device size: 29.81 GiB serial: <filter> scheme: MBR 
           ID-4: /dev/sdc type: USB vendor: Generic model: SD MMC size: 14.84 GiB serial: <filter> rev: 1.00 
Partition: ID-1: / size: 456.83 GiB used: 18.56 GiB (4.1%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: /home size: 888.20 GiB used: 326.24 GiB (36.7%) fs: ext4 dev: /dev/sda1 
           ID-3: swap-1 size: 28.13 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 29.0 C mobo: 27.0 C gpu: nvidia temp: 32 C 
           Fan Speeds (RPM): fan-1: 1885 fan-2: 0 fan-3: 1893 fan-4: 3117 fan-5: 0 gpu: nvidia fan: 0% 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.34 vbat: 3.07 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http://mirrors.evowise.com/linuxmint/packages ulyana main upstream import backport
           2: deb http://la-mirrors.evowise.com/ubuntu focal main restricted universe multiverse
           3: deb http://la-mirrors.evowise.com/ubuntu focal-updates main restricted universe multiverse
           4: deb http://la-mirrors.evowise.com/ubuntu focal-backports main restricted universe multiverse
           5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
           6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:      Processes: 339 Uptime: 56m Memory: 30.31 GiB used: 3.95 GiB (13.0%) Init: systemd v: 245 runlevel: 5 Compilers: 
           gcc: 9.3.0 alt: 9 Shell: bash v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

[hglee]

Hi, I'm running Ulyana 64bit on a newish custom build and have to toggle wireless on after each reboot. Network connections is set to automatically connect and it connects immediately upon toggling wireless switch in tray applet. I am not understanding why it is not turned on or enabled at boot. I included termbin and inxi output if helpful. I could really use the assistance with this as it is the only thing on new PC that is not working, and of course the wife is looking at me like I did something wrong in building.

Network: Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel port: e000 bus ID: 04:00.0
chip ID: 8086:24fb
IF: wlp4s0 state: up mac: <filter>

Let's try some wifi driver reconfiguration:


Open a Terminal window (Ctrl-Alt-T), then copy-and-paste the following 2 command-lines, one by one...

Code: Select all

sudo tee /etc/modprobe.d/iwlwifi_opt.conf<<<"options iwlwifi 11n_disable=8 swcrypto=1"
sudo tee /etc/modprobe.d/iwlmvm_opt.conf<<<"options iwlmvm power_scheme=1"

Reboot.



If you later wish to undo the above actions:

Open a Terminal window (Ctrl-Alt-T), then copy-and-paste the following command...

Code: Select all

sudo rm /etc/modprobe.d/{iwlwifi,iwlmvm}_opt.conf

[tek3195]

Hi, I'm running Ulyana 64bit on a newish custom build and have to toggle wireless on after each reboot. Network connections is set to automatically connect and it connects immediately upon toggling wireless switch in tray applet. I am not understanding why it is not turned on or enabled at boot. I included termbin and inxi output if helpful. I could really use the assistance with this as it is the only thing on new PC that is not working, and of course the wife is looking at me like I did something wrong in building.

Network: Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel port: e000 bus ID: 04:00.0
chip ID: 8086:24fb
IF: wlp4s0 state: up mac: <filter>

Let's try some wifi driver reconfiguration:


Open a Terminal window (Ctrl-Alt-T), then copy-and-paste the following 2 command-lines, one by one...

Code: Select all

sudo tee /etc/modprobe.d/iwlwifi_opt.conf<<<"options iwlwifi 11n_disable=8 swcrypto=1"
sudo tee /etc/modprobe.d/iwlmvm_opt.conf<<<"options iwlmvm power_scheme=1"

Reboot.



If you later wish to undo the above actions:

Open a Terminal window (Ctrl-Alt-T), then copy-and-paste the following command...

Code: Select all

sudo rm /etc/modprobe.d/{iwlwifi,iwlmvm}_opt.conf

Dang, I was really hoping that would work, it didn't. What should priority value be for auto connect in network connection ? Seems like it used to be a crazy high number and now it maxes out at 999.

[hglee]

Dang, I was really hoping that would work, it didn't. What should priority value be for auto connect in network connection ? Seems like it used to be a crazy high number and now it maxes out at 999.

The NetworkManager "Connect automatically with priority" option should be checkmarked with priority zero.

[tek3195]

Dang, I was really hoping that would work, it didn't. What should priority value be for auto connect in network connection ? Seems like it used to be a crazy high number and now it maxes out at 999.

The NetworkManager "Connect automatically with priority" option should be checkmarked with priority zero.

It doesn't connect on boot with 0 or any other number I've tried so far. What should I try next ?

[hglee]

What should I try next ?

Other miscellaneous NetworkManager settings:

General

All users may connect to this network: Off.
Metered connection: Automatic.

Wi-Fi

Mode: Client.
Band: Automatic.
Channel: default.
MTU: automatic.

Alternatively, you can set Wi-Fi > Band to either 5GHz or 2.4GHz, whichever you favour.

Also, while connected, click Wi-Fi > BSSID and select the IP address listed. This tells NetworkManager to not scan for any other access points.


Miscellaneous reports of problems with the Wireless-AC 3168NGW were resolved by a kernel upgrade:

Launch Update Manager, there click View > Linux Kernels > Continue. Select 5.8 and install the top version listed. Reboot.

[tek3195]

What should I try next ?

Other miscellaneous NetworkManager settings:

General

All users may connect to this network: Off.
Metered connection: Automatic.

Wi-Fi

Mode: Client.
Band: Automatic.
Channel: default.
MTU: automatic.

Alternatively, you can set Wi-Fi > Band to either 5GHz or 2.4GHz, whichever you favour.

Also, while connected, click Wi-Fi > BSSID and select the IP address listed. This tells NetworkManager to not scan for any other access points.


Miscellaneous reports of problems with the Wireless-AC 3168NGW were resolved by a kernel upgrade:

Launch Update Manager, there click View > Linux Kernels > Continue. Select 5.8 and install the top version listed. Reboot.

I had NetworkManager settings already set like you said. I have tried with Band set to 5GHz, 2.4GHz and auto, all with same results. I tried kernel update with 5.8.0-50 and 5.8.0-50-lowlatency just now and neither one solved problem. I tried 5.8.??-hwe last night and had black screen, also right now with 5.8.0-50 I am getting intermittent cursor freezing. Don't know if it is from wireless trackball or kernel but do not normally have issue. Battery is good and antenna is where it should be. Ok, not antenna but logitech dongle hangs from an extension cable and peeks out just under bottom edge of monitor always keeping line of sight with peripherals.

[hglee]

I'm running Ulyana 64bit on a newish custom build and have to toggle wireless on after each reboot. Network connections is set to automatically connect and it connects immediately upon toggling wireless switch in tray applet. I am not understanding why it is not turned on or enabled at boot.

As I understand it, your wifi is functional except for not connecting automatically at boot-up -- so you must manually click the NetworkManager icon and select the SSID of your Access Point (wifi router)?

I've been pondering an immediate solution, even if it isn't elegant. I put together a script that commands NetworkManager to connect. When the script is added to StartUp Applications, it runs automatically at every login.

Open a Terminal window (Ctrl-Alt-T), then copy-and-paste the following command-line...

Code: Select all

I=/usr/bin;echo -e '#!/bin/bash\nnmcli connection up $1 ifname $2\nexit'|sudo dd of=$I/wf-me;sudo chmod +x $I/wf-me

This creates a script named wf-me in your command path -- specifically /usr/bin/wf-me -- so it can be invoked from anywhere on your system.

To make it generic, wf-me needs two parameters: Your ESSID and wifi device name. In your case it's Tony5 and wlp4s0, respectively. This info can be found using the iwconfig command. For this to work you must have previously logged into that ESSID, so NetworkManager will already know the password.

So, the following Terminal command should cause your wifi to connect:

Code: Select all

wf-me Tony5 wlp4s0

As a proper test, reboot, then instead of clicking the NetworkManager icon, open a Terminal and run the above wf-me command. Your system should connect.


Then all you need to do is put the command /usr/bin/wf-me Tony5 wlp4s0 in your StartUp Applications. For testing, I set it for a 15-second delay, to give my laptop time to fully wake up from a cold boot. Yours could do with a shorter or longer pause (start long then shave it back).

Reboot and see if a miracle happens. If so, it can be a bandaid until something more elegant comes along -- but tell dear wife that it's fixed!

[tek3195]

[/code]

I'm running Ulyana 64bit on a newish custom build and have to toggle wireless on after each reboot. Network connections is set to automatically connect and it connects immediately upon toggling wireless switch in tray applet. I am not understanding why it is not turned on or enabled at boot.

As I understand it, your wifi is functional except for not connecting automatically at boot-up -- so you must manually click the NetworkManager icon and select the SSID of your Access Point (wifi router)?

I've been pondering an immediate solution, even if it isn't elegant. I put together a script that commands NetworkManager to connect. When the script is added to StartUp Applications, it runs automatically at every login.

Open a Terminal (Ctrl-Alt-T), then copy-and-paste the following command-line...

Code: Select all

I=/usr/bin;echo -e '#!/bin/bash\nnmcli connection up $1 ifname $2\nexit'|sudo dd of=$I/wf-me;sudo chmod +x $I/wf-me

This creates a script named wf-me in your command path -- specifically /usr/bin/wf-me -- so it can be invoked from anywhere on your system.

To make it generic, wf-me needs two parameters: Your ESSID and wifi device name. In your case it's Tony5 and wlp4s0, respectively. This info can be found using the iwconfig command. For this to work you must have previously logged into that ESSID, so NetworkManager will already know the password.

So, the following Terminal command should cause your wifi to connect:

Code: Select all

wf-me Tony5 wlp4s0

As a proper test, reboot, then instead of clicking the NetworkManager icon, open a Terminal and run the above wf-me command. Your system should connect.


Then all you need to do is add the command /usr/bin/wf-me Tony5 wlp4s0 in your StartUp Applications. For testing, I set it for a 15-second delay, to give my laptop time to fully wake up from a cold boot. Yours could do with a shorter or longer pause (start long then shave it back).

Reboot and see if a miracle happens. If so, it can be a bandaid until something more elegant comes along -- but tell dear wife that it's fixed!

I hate to be the bearer of bad news, but, no miracles today. After it failed and I toggled wifi on it's connected Tony5 on wlp4s0. Why would it say not available ?

Code: Select all

tek3195@micro-mini:~$ wf-me Tony5 wlp4s0
Error: Connection activation failed: Connection 'Tony5' is not available on device wlp4s0 because device is not available

[hglee]

I hate to be the bearer of bad news, but, no miracles today. After it failed and I toggled wifi on it's connected Tony5 on wlp4s0. Why would it say not available ?

Code: Select all

tek3195@micro-mini:~$ wf-me Tony5 wlp4s0
Error: Connection activation failed: Connection 'Tony5' is not available on device wlp4s0 because device is not available

It may need a longer delay in wf-me's StartUp Applications entry, to give the wifi adapter time to be initialized by the OS.

[tek3195]

It may need a longer delay in wf-me's StartUp Applications entry, to give the wifi adapter time to be initialized by the OS.

I'll try 30 and see what happens.

[tek3195]

It may need a longer delay in wf-me's StartUp Applications entry, to give the wifi adapter time to be initialized by the OS.

30 didn't do it either. I don't know if this will tell you anything, but, in Network Settings if I reset the connection it automatically reconnects in 3~5 seconds without entering password. I am assuming that is your script working on reset. But still will not connect at boot.

[hglee]

30 didn't do it either. I don't know if this will tell you anything, but, in Network Settings if I reset the connection it automatically reconnects in 3~5 seconds without entering password. I am assuming that is your script working on reset. But still will not connect at boot.

That might be another symptom of whatever has been causing your auto-connect fails.

Wifi is not my forté, but I'll look into this further. A solution that makes wf-me work at boot may also fix your auto-connect without wf-me.

[tek3195]

That might be another symptom of whatever has been causing your auto-connect fails.
Wifi is not my forté, but I'll look into this further. A solution that makes wf-me work at boot may also fix your auto-connect without wf-me.

I was thinking along the same lines. I don't believe there would be multiple issues with wifi that were unrelated, gotta be connected.

I still have internet access, just the minor annoyance of turning it on. If it wasn't a fresh $1800.00 I had just spent I wouldn't worry about it. With it being brand new I just wanted it all working. I have ethernet connection with decent service, just had it unplugged trying to get wifi sorted out.

I appreciate all the effort you've put into this, but you don't have to keep messing with it, totally up to you though. If you write it I'll try it. If you don't, I'll completely understand.