You are not logged in.
virus@Virus:~$ journalctl -u NetworkManager -b
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
virus@Virus:~$
Offline
@Zeno You are being asked again to use [ code ] tags when posting terminal output. I have edited your long post above to demonstrate the difference it makes.
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
virus@Virus:~$ journalctl -u NetworkManager -b
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
virus@Virus:~$
You need to use 'sudo' to see the full output.
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
virus@Virus:~$ dmesg|grep -Ei 'wlan|firmw|dhc'
dmesg: read kernel buffer failed: Operation not permitted
virus@Virus:~$
Yes. You ned to be root top run dmesg, or preeced command with "sudo".
// Regards rbh
Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu
Offline
virus@Virus:~$ systemctl status NetworkManager
Probably you will get some more info if you issue the command with root rights.
// Regards rbh
Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu
Offline
Zeno wrote:virus@Virus:~$ systemctl status NetworkManager
Probably you will get some more info if you issue the command with root rights.
Maybe you also must increase logging verbosity.
Change /etc/NetworkManager/NetworkManager.conf as:
[logging]
level=DEBUG
// Regards rbh
Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu
Offline
@Zeno: Yes, please repeat these commands with superuser privileges:
sudo dmesg | grep -Ei 'wlan|firmw|dhc'
sudo apt update
And please use CODE tags for dog's sake.
Your syslog output, the relevant bit (I removed the timestamp):
NetworkManager[375]: <info> [1579458674.7704] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
NetworkManager[375]: <info> [1579458674.7821] (wlx502b73c86f2b): using nl80211 for WiFi device control
NetworkManager[375]: <info> [1579458674.7868] manager: (wlx502b73c86f2b): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/2)
NetworkManager[375]: <info> [1579458674.7930] device (wlx502b73c86f2b): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
kernel: [ 16.202584] IPv6: ADDRCONF(NETDEV_UP): wlx502b73c86f2b: link is not ready
kernel: [ 16.219566] IPv6: ADDRCONF(NETDEV_UP): wlx502b73c86f2b: link is not ready
NetworkManager[375]: <info> [1579458674.8897] device (wlx502b73c86f2b): set-hw-addr: set MAC address to 6E:E0:29:C8:6D:5B (scanning)
kernel: [ 16.313949] IPv6: ADDRCONF(NETDEV_UP): wlx502b73c86f2b: link is not ready
dbus[371]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
NetworkManager[375]: <info> [1579458674.9604] ModemManager available in the bus
systemd[1]: Starting WPA supplicant...
dbus[371]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
systemd[1]: Started WPA supplicant.
wpa_supplicant[496]: Successfully initialized wpa_supplicant
NetworkManager[375]: <info> [1579458675.3571] supplicant: wpa_supplicant running
NetworkManager[375]: <info> [1579458675.3574] device (wlx502b73c86f2b): supplicant interface state: init -> starting
NetworkManager[375]: <info> [1579458675.7213] sup-iface[0x561a9f133e70,wlx502b73c86f2b]: supports 4 scan SSIDs
NetworkManager[375]: <info> [1579458675.7242] device (wlx502b73c86f2b): supplicant interface state: starting -> ready
NetworkManager[375]: <info> [1579458675.7244] device (wlx502b73c86f2b): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
kernel: [ 17.132281] IPv6: ADDRCONF(NETDEV_UP): wlx502b73c86f2b: link is not ready
NetworkManager[375]: <info> [1579458676.9050] device (wlx502b73c86f2b): supplicant interface state: ready -> inactive
NetworkManager[375]: <info> [1579458676.9267] manager: startup complete
systemd[1]: Started Network Manager Wait Online.
systemd[1]: Reached target Network is Online.
systemd[530]: Listening on GnuPG network certificate management daemon.
systemd[567]: Listening on GnuPG network certificate management daemon.
NetworkManager[375]: <info> [1579458694.4891] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
Can someone read network manager log output better than me?
All I can see is that it gives up on the wlan interface (wlx502b73c86f2b) for no apparent reason and goes back to wired.
@Zeno: while testing wireless please unplug your computer from wired.
BTW, is your wired internet also a USB device?
Offline