Not sure why but I'm still digging around trying to find out. Total noob but the rules and regs state I need to make a first post and I figured this one would be the best one :-)

Reboot then check logs in /var/log and/or reboot and check the output of systemctl status NetworkManager (or whatever is managing your WiFi connection)

Try the systemctl command first so you don’t have to sift through logs.

It should show errors if it’s enabled to start at boot but can’t for some reason.

Please describe difference between reboot and hard boot.

Rebooting via the GUI/issuing reboot command is reboot.

Hard reboot is holding down the power button to force a reboot.

(I’m assuming?)

i hope his meaning of hard boot is not "slam on the hard drive with a baseball bat". i have heard that "hard boot" is like pressing the reset button or holding the power off button until the computer really powers of then power it back on.

No, I don't have any plans to "slam on the hard drive with a baseball bat." I'm new but I'm not *that* new :-/

Yes, as permaroot said: "Rebooting via the GUI/issuing reboot command is reboot. Hard reboot is holding down the power button to force a reboot."

So, I'll try permaroot's suggestion and see what i can find out :-)

Question is: WHY are you even doing that? (hint: you shouldn't)

Ok, lemme rephrase that:

I'm not holding down the power button to force a reboot. I have two choices as far as rebooting goes. I can reboot from either the command line or gui (not shut down and hard boot, just reboot). When I *reboot* from either the command line or gui, I end up with no wifi. As far as ubuntu is concerned, I have no networks, nor wifi card. When I *shut down* from either the command line or gui and boot back up (which is what I've always read as hard boot or thought so anyway, lol) my wifi is present and accounted for and works just fine. Once again...sorry for the confusion :-)

Did you try issuing reboot and then checking the systemctl status NetworkManager yet?

This may be a problem solvable with a WiFi card or motherboard firmware update, restart not flushing all RAM except via powerdown, or not retaining or refreshing NV RAM that it should for an un-powered down "startup".

I have. I ran it before I rebooted it and saved it to a file. I also ran it after I rebooted it and saved it to a file. This is what it said before I rebooted:


NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-08-20 10:11:47 CDT; 4 days ago
Docs: man:NetworkManager(8)
Main PID: 1054 (NetworkManager)
Tasks: 5 (limit: 4915)
Memory: 11.7M
CGroup: /system.slice/NetworkManager.service
├─1054 /usr/sbin/NetworkManager --no-daemon
└─1342 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/dhclient-wlp3s0.pid -lf /var/lib/NetworkManager/dhclient-9cc4db62-5e11-4665-b9af-329eb7b19a71-wlp3s0.lease -cf /var/lib/NetworkManager/dhclient-wlp3s0.conf wlp3s0

Aug 23 02:46:52 aces-box NetworkManager[1054]: <info> [1566546412.0687] dhcp4 (wlp3s0): plen 24 (255.255.255.0)
Aug 23 02:46:52 aces-box NetworkManager[1054]: <info> [1566546412.0688] dhcp4 (wlp3s0): gateway 192.168.1.1
Aug 23 02:46:52 aces-box NetworkManager[1054]: <info> [1566546412.0688] dhcp4 (wlp3s0): lease time 604800
Aug 23 02:46:52 aces-box NetworkManager[1054]: <info> [1566546412.0688] dhcp4 (wlp3s0): hostname 'aces-box'
Aug 23 02:46:52 aces-box NetworkManager[1054]: <info> [1566546412.0689] dhcp4 (wlp3s0): nameserver '192.168.1.1'
Aug 23 02:46:52 aces-box NetworkManager[1054]: <info> [1566546412.0689] dhcp4 (wlp3s0): domain name 'lan1'
Aug 23 02:46:52 aces-box NetworkManager[1054]: <info> [1566546412.0689] dhcp4 (wlp3s0): state changed unknown -> bound
Aug 23 02:46:52 aces-box dhclient[1342]: bound to 192.168.1.249 -- renewal in 260041 seconds.
Aug 24 10:09:19 aces-box NetworkManager[1054]: <info> [1566659359.2484] manager: NetworkManager state is now CONNECTED_SITE
Aug 24 11:11:30 aces-box NetworkManager[1054]: <info> [1566663090.1850] manager: NetworkManager state is now CONNECTED_GLOBAL


----------------------------------------------------------------------------------------------------


This is what it gave me after I rebooted:


NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2019-08-24 17:45:53 CDT; 22min ago
Docs: man:NetworkManager(8)
Main PID: 1050 (NetworkManager)
Tasks: 3 (limit: 4915)
Memory: 14.6M
CGroup: /system.slice/NetworkManager.service
└─1050 /usr/sbin/NetworkManager --no-daemon

Aug 24 17:46:52 aces-box NetworkManager[1050]: <warn> [1566686812.2562] device (wlp3s0): re-acquiring supplicant interface (#3).
Aug 24 17:47:00 aces-box NetworkManager[1050]: <error> [1566686820.3128] sup-iface[0x55a2c5c8d3d0,wlp3s0]: error adding interface: wpa_supplicant couldn't grab this interface.
Aug 24 17:47:00 aces-box NetworkManager[1050]: <info> [1566686820.3129] device (wlp3s0): supplicant interface state: starting -> down
Aug 24 17:47:10 aces-box NetworkManager[1050]: <warn> [1566686830.2481] device (wlp3s0): re-acquiring supplicant interface (#4).
Aug 24 17:47:18 aces-box NetworkManager[1050]: <error> [1566686838.4889] sup-iface[0x55a2c5c8d4b0,wlp3s0]: error adding interface: wpa_supplicant couldn't grab this interface.
Aug 24 17:47:18 aces-box NetworkManager[1050]: <info> [1566686838.4890] device (wlp3s0): supplicant interface state: starting -> down
Aug 24 17:47:28 aces-box NetworkManager[1050]: <warn> [1566686848.2560] device (wlp3s0): re-acquiring supplicant interface (#5).
Aug 24 17:47:36 aces-box NetworkManager[1050]: <error> [1566686856.3289] sup-iface[0x55a2c5c8d590,wlp3s0]: error adding interface: wpa_supplicant couldn't grab this interface.
Aug 24 17:47:36 aces-box NetworkManager[1050]: <info> [1566686856.3290] device (wlp3s0): supplicant interface state: starting -> down
Aug 24 17:47:36 aces-box NetworkManager[1050]: <info> [1566686856.3290] device (wlp3s0): supplicant interface keeps failing, giving up


And that's all I know :-/

After reboot (when it’s not working) try systemctl restart NetworkManager and see if it starts working.

I'm almost positive I tried that but I'll give it a shot. Needless to say, I'm knee deep in a boatload of stuff I don't understand but I'm tryin, lol :-)

Unfortunately, that was a no go.

When you reboot and issue the ifconfig -a command, do any of your network interfaces show up? It would be nice to know if they are recognized and NetworkManager can't get them working or if they are not being recognized at all.