Need to reboot for wifi to connect

Message

reformedhatter · #1 Post by **reformedhatter** » 2024-10-03 08:04

Hi there,

When I boot up my wifi does not connect, but if I reboot it does. My network controller is an Intel Corporation Wireless 8260 (rev 3a) and from Googling I see folk using it on Linux Mint and Ubuntu have issues with it, but not the same issue I have. Any help appreciated.

kc1di · #2 Post by **kc1di** » 2024-10-03 09:02

what is the setting in network manager for auto connect? is that box checked?

reformedhatter · #3 Post by **reformedhatter** » 2024-10-03 09:25

thanks for the reply. In Advanced Network Manager, under the General Tab the 'Connect automatically with priority 0' is checked

kc1di · #4 Post by **kc1di** » 2024-10-03 16:23

Next time to boot up and it does not connect try restarting network manager with this command
systemctl restart NetworkManager
see if that works , at least you will not have to reboot if it does. If it does not work it should give an error message.

#5 Post by **Aki** » 2024-10-03 18:29

Hello

reformedhatter wrote: 2024-10-03 08:04 When I boot up my wifi does not connect, but if I reboot it does. My network controller is an Intel Corporation Wireless 8260 (rev 3a)

Do you dual boot the computer with other operating systems ?

reformedhatter · #6 Post by **reformedhatter** » 2024-10-04 08:07

kc1di wrote: 2024-10-03 16:23 Next time to boot up and it does not connect try restarting network manager with this command
systemctl restart NetworkManager
see if that works , at least you will not have to reboot if it does. If it does not work it should give an error message.

Thanks for the advice. I will check it out next time it happens and report back.

reformedhatter · #7 Post by **reformedhatter** » 2024-10-04 08:09

Aki wrote: 2024-10-03 18:29 Hello
reformedhatter wrote: 2024-10-03 08:04 When I boot up my wifi does not connect, but if I reboot it does. My network controller is an Intel Corporation Wireless 8260 (rev 3a)
Do you dual boot the computer with other operating systems ?

Thanks for the reply. I don't dual boot, the last time I did that was when I was ditthering about turning to Linux full-time lol

#8 Post by **Aki** » 2024-10-04 15:23

Hello,

Are there any relevant messages in the system logs ? You can replicate the issue and then use with the following command to collect logs of the current and previous boot (root password is required twice):

Code: Select all

script log.txt
su -l -c "journal -b 1 --no-pager"
su -l -c "journal -b --no-pager"
exit

The log will be store in the file named log.txt .

Then, you can report logs in one of the following ways:

paste them into the Debian Pastezone service (https://paste.debian.net) and report the URL/link of the paste in a follow-up message

attaching the logs to a follow-up forum message as a compressed zip or gz file

paste logs into the body of a follow-up message between code tags (if they fit the size of a forum message)

reformedhatter · #9 Post by **reformedhatter** » 2024-10-04 15:42

root@LAPTOP:/home/charlie# su -l -c "journal -b 1 --no-pager"
-bash: line 1: journal: command not found

this is what I get when I enter root and ad those commands

#10 Post by **Aki** » 2024-10-04 15:44

Sorry:

Code: Select all

script log.txt
su -l -c "journalctl -b 1 --no-pager"
su -l -c "journalctl -b --no-pager"
exit

reformedhatter · #11 Post by **reformedhatter** » 2024-10-04 16:02

Hope you get this okay. It is the first time I have zipped a file using Peazip on Linux.

#12 Post by **Aki** » 2024-10-04 16:38

The previous log seems to be only from the second (working) boot.

#13 Post by **sunrat** » 2024-10-04 22:51

Aki wrote: 2024-10-04 16:38 The previous log seems to be only from the second (working) boot.

It should be "-b -1" for previous boot, ie.:

Code: Select all

script log.txt
su -l -c "journalctl -b -1 --no-pager"
su -l -c "journalctl -b --no-pager"
exit

#14 Post by **Aki** » 2024-10-05 06:46

Hello @sunrat,

sunrat wrote: 2024-10-04 22:51
Aki wrote: 2024-10-04 16:38 The previous log seems to be only from the second (working) boot.
It should be "-b -1" for previous boot, ie.:
Code: Select all
script log.txt
su -l -c "journalctl -b -1 --no-pager"
su -l -c "journalctl -b --no-pager"
exit

Thanks for point it out, my bad.

@reformedhatter:
Sorry for the misinterpretation. The correct commands to gather the last and last-1 system logs are quoted above.

reformedhatter · #15 Post by **reformedhatter** » 2024-10-05 07:12

Aki wrote: 2024-10-05 06:46 Hello @sunrat,
sunrat wrote: 2024-10-04 22:51
Aki wrote: 2024-10-04 16:38 The previous log seems to be only from the second (working) boot.
It should be "-b -1" for previous boot, ie.:
Code: Select all
script log.txt
su -l -c "journalctl -b -1 --no-pager"
su -l -c "journalctl -b --no-pager"
exit
Thanks for point it out, my bad.

@reformedhatter:
Sorry for the misinterpretation. The correct commands to gather the last and last-1 systems logs are quoted above.

No problem.I'm still waiting for it to not connect when I boot up. Typical, once I report it on hear it stops doing it.

reformedhatter · #16 Post by **reformedhatter** » 2024-10-05 07:17

When I run su -l -c "journalctl -b -1 --no-pager" I get "Specifying boot ID or boot offset has no effect, no persistent journal was found".

#17 Post by **Aki** » 2024-10-05 07:37

Hello,

reformedhatter wrote: 2024-10-05 07:17 When I run su -l -c "journalctl -b -1 --no-pager" I get "Specifying boot ID or boot offset has no effect, no persistent journal was found".

Well, then you can simply collect the logs after the first boot (when the network interface does not connect).

reformedhatter · #18 Post by **reformedhatter** » 2024-10-06 07:00

Here you go. The laptop didn't close down properly last night [screen goes black, power button light stayed on - had to press and hold power button to turn it off] and the wifi didn't connect first time, but did after reboot

#19 Post by **Aki** » 2024-10-06 15:24

Hello,

In the log from last message, the wireless network adapter is correctly configured:

Code: Select all

$ grep -e "iwlwifi\|wlp3s0" log.txt 
Oct 06 07:52:50 LAPTOP kernel: iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
Oct 06 07:52:50 LAPTOP kernel: iwlwifi 0000:03:00.0: firmware: direct-loading firmware iwlwifi-8000C-36.ucode
Oct 06 07:52:50 LAPTOP kernel: iwlwifi 0000:03:00.0: loaded firmware version 36.ca7b901d.0 8000C-36.ucode op_mode iwlmvm
Oct 06 07:52:50 LAPTOP kernel: iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x201
Oct 06 07:52:50 LAPTOP kernel: iwlwifi 0000:03:00.0: base HW address: [MAC REMOVED], OTP minor version: 0x4
Oct 06 07:52:50 LAPTOP NetworkManager[811]: <info>  [1728197570.4740] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
Oct 06 07:52:50 LAPTOP kernel: iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
Oct 06 07:52:50 LAPTOP NetworkManager[811]: <info>  [1728197570.7490] device (wlp3s0): driver supports Access Point (AP) mode
Oct 06 07:52:50 LAPTOP NetworkManager[811]: <info>  [1728197570.7497] manager: (wlp3s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Oct 06 07:52:50 LAPTOP NetworkManager[811]: <info>  [1728197570.7616] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 06 07:52:51 LAPTOP NetworkManager[811]: <info>  [1728197571.0568] device (wlp3s0): set-hw-addr: set MAC address to CA:27:28:13:E4:D4 (scanning)
Oct 06 07:52:51 LAPTOP NetworkManager[811]: <info>  [1728197571.5811] device (wlp3s0): supplicant interface state: internal-starting -> disconnected
Oct 06 07:52:51 LAPTOP NetworkManager[811]: <info>  [1728197571.5812] Wi-Fi P2P device controlled by interface wlp3s0 created
Oct 06 07:52:51 LAPTOP NetworkManager[811]: <info>  [1728197571.5814] manager: (p2p-dev-wlp3s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Oct 06 07:52:51 LAPTOP NetworkManager[811]: <info>  [1728197571.5815] device (p2p-dev-wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 06 07:52:51 LAPTOP NetworkManager[811]: <info>  [1728197571.5818] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Oct 06 07:52:51 LAPTOP NetworkManager[811]: <info>  [1728197571.5821] device (p2p-dev-wlp3s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 06 07:52:54 LAPTOP wpa_supplicant[812]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=GB
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.8732] device (wlp3s0): Activation: starting connection 'VM1689' (02028450-3161-466d-be1d-68cb1ffd6dc4)
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.8733] device (wlp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.8947] device (wlp3s0): set-hw-addr: reset MAC address to [MAC REMOVED] (preserve)
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.8992] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.8994] device (wlp3s0): Activation: (wifi) access point 'VM1689' has security, but secrets are required.
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.8994] device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.8996] sup-iface[21878855ef1c9a44,0,wlp3s0]: wps: type pbc start...
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.9003] device (wlp3s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.9006] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.9008] device (wlp3s0): Activation: (wifi) connection 'VM1689' has security, and secrets exist.  No new secrets needed.
Oct 06 07:52:54 LAPTOP wpa_supplicant[812]: wlp3s0: WPS-CANCEL
Oct 06 07:52:54 LAPTOP wpa_supplicant[812]: wlp3s0: SME: Trying to authenticate with [MAC REMOVED] (SSID='VM1689' freq=5220 MHz)
Oct 06 07:52:54 LAPTOP kernel: wlp3s0: authenticate with [MAC REMOVED]
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.9590] device (wlp3s0): supplicant interface state: disconnected -> authenticating
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.9590] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> authenticating
Oct 06 07:52:54 LAPTOP kernel: wlp3s0: send auth to [MAC REMOVED] (try 1/3)
Oct 06 07:52:54 LAPTOP wpa_supplicant[812]: wlp3s0: Trying to associate with [MAC REMOVED] (SSID='VM1689' freq=5220 MHz)
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.9653] device (wlp3s0): supplicant interface state: authenticating -> associating
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.9653] device (p2p-dev-wlp3s0): supplicant management interface state: authenticating -> associating
Oct 06 07:52:54 LAPTOP kernel: wlp3s0: authenticated
Oct 06 07:52:54 LAPTOP kernel: wlp3s0: associate with [MAC REMOVED] (try 1/3)
Oct 06 07:52:54 LAPTOP kernel: wlp3s0: RX AssocResp from [MAC REMOVED] (capab=0x1511 status=0 aid=5)
Oct 06 07:52:54 LAPTOP wpa_supplicant[812]: wlp3s0: Associated with [MAC REMOVED]
Oct 06 07:52:54 LAPTOP wpa_supplicant[812]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Oct 06 07:52:54 LAPTOP kernel: wlp3s0: associated
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.9805] device (wlp3s0): supplicant interface state: associating -> associated
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.9806] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> associated
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.9914] device (wlp3s0): supplicant interface state: associated -> 4way_handshake
Oct 06 07:52:54 LAPTOP NetworkManager[811]: <info>  [1728197574.9914] device (p2p-dev-wlp3s0): supplicant management interface state: associated -> 4way_handshake
Oct 06 07:52:55 LAPTOP wpa_supplicant[812]: wlp3s0: WPA: Key negotiation completed with [MAC REMOVED] [PTK=CCMP GTK=CCMP]
Oct 06 07:52:55 LAPTOP wpa_supplicant[812]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to [MAC REMOVED] completed [id=0 id_str=]
Oct 06 07:52:55 LAPTOP kernel: wlp3s0: Limiting TX power to 23 (23 - 0) dBm as advertised by [MAC REMOVED]
Oct 06 07:52:55 LAPTOP kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Oct 06 07:52:55 LAPTOP NetworkManager[811]: <info>  [1728197575.0925] device (wlp3s0): supplicant interface state: 4way_handshake -> completed
Oct 06 07:52:55 LAPTOP NetworkManager[811]: <info>  [1728197575.0926] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "VM1689"
Oct 06 07:52:55 LAPTOP NetworkManager[811]: <info>  [1728197575.0926] device (p2p-dev-wlp3s0): supplicant management interface state: 4way_handshake -> completed
Oct 06 07:52:55 LAPTOP NetworkManager[811]: <info>  [1728197575.0927] device (wlp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 06 07:52:55 LAPTOP wpa_supplicant[812]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-60 noise=9999 txrate=6000
Oct 06 07:52:55 LAPTOP NetworkManager[811]: <info>  [1728197575.0932] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
Oct 06 07:52:55 LAPTOP avahi-daemon[711]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::bea8:a6ff:fe7d:743b.
Oct 06 07:52:55 LAPTOP avahi-daemon[711]: New relevant interface wlp3s0.IPv6 for mDNS.
Oct 06 07:52:55 LAPTOP avahi-daemon[711]: Registering new address record for fe80::bea8:a6ff:fe7d:743b on wlp3s0.*.
Oct 06 07:52:55 LAPTOP NetworkManager[811]: <info>  [1728197575.1439] dhcp4 (wlp3s0): state changed new lease, address=192.168.0.14
Oct 06 07:52:55 LAPTOP NetworkManager[811]: <info>  [1728197575.1444] policy: set 'VM1689' (wlp3s0) as default for IPv4 routing and DNS
Oct 06 07:52:55 LAPTOP avahi-daemon[711]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.0.14.
Oct 06 07:52:55 LAPTOP avahi-daemon[711]: New relevant interface wlp3s0.IPv4 for mDNS.
Oct 06 07:52:55 LAPTOP avahi-daemon[711]: Registering new address record for 192.168.0.14 on wlp3s0.IPv4.
Oct 06 07:52:55 LAPTOP NetworkManager[811]: <info>  [1728197575.1675] device (wlp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Oct 06 07:52:55 LAPTOP NetworkManager[811]: <info>  [1728197575.1700] device (wlp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Oct 06 07:52:55 LAPTOP NetworkManager[811]: <info>  [1728197575.1702] device (wlp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Oct 06 07:52:55 LAPTOP NetworkManager[811]: <info>  [1728197575.1711] device (wlp3s0): Activation: successful, device activated.
Oct 06 07:53:49 LAPTOP wpa_supplicant[812]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-61 noise=9999 txrate=585100

Debian User Forums

Need to reboot for wifi to connect

Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect

Re: Need to reboot for wifi to connect