may you post the output of ‘nmcli general’ and ‘nmcli device status’ to get an overview.
I would like to post std output of nmcli to you, but each terminal i opened now to to run “nmcli” the terminals are in freeze… both terminal freezed… BUT i can still type on the terminal,… just not more respond.
Don’t know what to do already… thinking of REINSTALL OVER the existing os… will that fix whatever problem that causing the os to BREAK ?
I would still like to post my boot log… because i got “shutdown” error… that causing the system not able to shutdown.
To be frank, i didn’t mess with this desktop … not that i know of… and it just broke. And worst thing is, i will never know what is the reason it break, “because of some software ? or some update ? or kernel update ? i have no idea… as i said, i didn’t do much on this desktop… and can’t remember i have done anything major changes of it…”
hey @andrewysk 
If this issue still persist, try to disable opengl rendering and enable xrender (software renderer). Maybe there is Issue on KDE.
I won’t want to question you, but couldn’t help it to ask :
opengl and xrender… sounds like something to do with video or graphic … is it something to do with network interface card ?
- It is not an ethernet problem, but a problem with suspend which caused a problem with ethernet, as you proved:
- That could be somewhat related to the rendering with opengl instead of xrender with some low GPUs like this intel one:
What could affect this:
However… As I read from your posts, it works, except you suspend and wake up you pc. Is that correct?
If so, then I would rather say that there is Firmware Bug or Kernel Bug, or the firmware has not a proper implementation of the ACPI Specification, which the Linux Kernel follows strictly normally (but some BIOS Vendors make exceptions or workarounds for Windows, but left other OS).
Maybe have a look at this also:
I purposely powered on this desktop that have NIC issue.
It was all good at the beginning… , did a “$ systemctl suspend” and wake up, but the internet connection is still good. after around 2 hrs of idling (when i didn’t pay attention to it), i realized the internet connection is disconnected by itself and stay disconnected.
I have the "$journalctl -b -f " … But i don’t know what to look for to filter out the root cause of the internet disconnected.
which log this issue is most probably logged . Is it in kernel log ? surely not kwin log…
Which log to check when NIC not responding to “sudo nmcli monitor” ?
$ journalctl -b | grep net | less
Does this command works ? to grep “net” out ? but since too long, i pipe it to less… but this does not work.
journalctl --boot 0 --unit NetworkManager.service --no-hostname --no-pager
Use -1 for prevoius boot , here is the list:
journalctl --list-boots
If you don’t post it here, then nobody could help except you.
`journalctl --boot 0 --unit NetworkManager.service --no-hostname --no-pager`
-- Journal begins at Mon 2020-03-30 22:08:21 CEST, ends at Fri 2021-08-13 01:05:55 CEST. --
Aug 12 19:39:07 systemd[1]: Starting Network Manager...
Aug 12 19:39:12 NetworkManager[488]: <info> [1628789952.2426] NetworkManager (version 1.32.4-1) is starting... (for the first time)
Aug 12 19:39:12 NetworkManager[488]: <info> [1628789952.3325] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Aug 12 19:39:14 systemd[1]: Started Network Manager.
Aug 12 19:39:14 NetworkManager[488]: <info> [1628789954.2328] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Aug 12 19:39:14 NetworkManager[488]: <info> [1628789954.3868] manager[0x557d9d363040]: monitoring kernel firmware directory '/lib/firmware'.
Aug 12 19:39:14 NetworkManager[488]: <info> [1628789954.8233] hostname: hostname: using hostnamed
Aug 12 19:39:14 NetworkManager[488]: <info> [1628789954.8233] hostname: hostname changed from (none) to "user1-pc"
Aug 12 19:39:14 NetworkManager[488]: <info> [1628789954.8239] dns-mgr[0x557d9d31b250]: init: dns=default,systemd-resolved rc-manager=symlink
Aug 12 19:39:14 NetworkManager[488]: <info> [1628789954.8913] manager[0x557d9d363040]: rfkill: Wi-Fi hardware radio set disabled
Aug 12 19:39:14 NetworkManager[488]: <info> [1628789954.8913] manager[0x557d9d363040]: rfkill: WWAN hardware radio set disabled
Aug 12 19:39:16 NetworkManager[488]: <info> [1628789956.1741] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-wwan.so)
Aug 12 19:39:16 NetworkManager[488]: <info> [1628789956.2949] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-wifi.so)
Aug 12 19:39:16 NetworkManager[488]: <info> [1628789956.9109] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-team.so)
Aug 12 19:39:16 NetworkManager[488]: <info> [1628789956.9798] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-adsl.so)
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.1948] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-bluetooth.so)
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.3168] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.32.4-1/libnm-device-plugin-ovs.so)
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.3172] manager: rfkill: Wi-Fi enabled by radio killswitch; disabled by state file
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.3173] manager: rfkill: WWAN enabled by radio killswitch; disabled by state file
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.3173] manager: Networking is enabled by state file
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.3683] dhcp-init: Using DHCP client 'internal'
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.4073] settings: Loaded settings plugin: keyfile (internal)
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.7545] device (lo): carrier: link connected
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.7549] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.7558] manager: (enp0s25): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.8320] settings: (enp0s25): created default wired connection 'Wired connection 1'
Aug 12 19:39:17 NetworkManager[488]: <info> [1628789957.8324] device (enp0s25): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 12 19:39:18 NetworkManager[488]: <info> [1628789958.2637] manager: (enp3s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
Aug 12 19:39:18 NetworkManager[488]: <info> [1628789958.2647] settings: (enp3s0): created default wired connection 'Wired connection 2'
Aug 12 19:39:18 NetworkManager[488]: <info> [1628789958.2651] device (enp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 12 19:39:19 NetworkManager[488]: <info> [1628789959.1437] ovsdb: Could not connect: No such file or directory
Aug 12 19:39:19 NetworkManager[488]: <info> [1628789959.1439] ovsdb: disconnected from ovsdb
Aug 12 19:39:20 NetworkManager[488]: <info> [1628789960.7767] device (enp0s25): carrier: link connected
Aug 12 19:39:20 NetworkManager[488]: <info> [1628789960.7770] device (enp0s25): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Aug 12 19:39:20 NetworkManager[488]: <info> [1628789960.7776] policy: auto-activating connection 'Wired connection 1' (c48347d3-1020-3aac-b2d3-add97d4904fd)
Aug 12 19:39:20 NetworkManager[488]: <info> [1628789960.7781] device (enp0s25): Activation: starting connection 'Wired connection 1' (c48347d3-1020-3aac-b2d3-add97d4904fd)
Aug 12 19:39:20 NetworkManager[488]: <info> [1628789960.7781] device (enp0s25): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:20 NetworkManager[488]: <info> [1628789960.7784] manager: NetworkManager state is now CONNECTING
Aug 12 19:39:20 NetworkManager[488]: <info> [1628789960.7785] device (enp0s25): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:20 NetworkManager[488]: <info> [1628789960.7791] device (enp0s25): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:20 NetworkManager[488]: <info> [1628789960.8258] dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
Aug 12 19:39:20 NetworkManager[488]: <info> [1628789960.9613] dhcp4 (enp0s25): state changed unknown -> expire
Aug 12 19:39:21 NetworkManager[488]: <info> [1628789961.5487] modem-manager: ModemManager not available
Aug 12 19:39:21 NetworkManager[488]: <info> [1628789961.7286] modem-manager: ModemManager now available
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.0474] dhcp6 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.0643] dhcp6 (enp0s25): state changed unknown -> bound
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.4043] dhcp4 (enp0s25): state changed expire -> bound, address=192.168.0.137
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.4052] device (enp0s25): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.4721] device (enp0s25): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.4723] device (enp0s25): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.4729] manager: NetworkManager state is now CONNECTED_LOCAL
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.4735] manager: NetworkManager state is now CONNECTED_SITE
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.4736] policy: set 'Wired connection 1' (enp0s25) as default for IPv4 routing and DNS
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.4738] policy: set 'Wired connection 1' (enp0s25) as default for IPv6 routing and DNS
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.6642] device (enp0s25): Activation: successful, device activated.
Aug 12 19:39:23 NetworkManager[488]: <info> [1628789963.9295] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 12 19:39:24 NetworkManager[488]: <info> [1628789964.5569] manager: startup complete
Aug 12 19:39:57 NetworkManager[488]: <info> [1628789997.1213] agent-manager: agent[b4c46b489e30fb24,:1.16/org.kde.plasma.networkmanagement/1000]: agent registered
Aug 12 20:09:13 NetworkManager[488]: <info> [1628791753.8710] dhcp4 (enp0s25): state changed bound -> extended, address=192.168.0.137
Aug 12 20:39:13 NetworkManager[488]: <info> [1628793553.8629] dhcp4 (enp0s25): state changed extended -> extended, address=192.168.0.137
Aug 12 21:09:13 NetworkManager[488]: <info> [1628795353.8507] dhcp4 (enp0s25): state changed extended -> extended, address=192.168.0.137
Aug 12 21:39:13 NetworkManager[488]: <info> [1628797153.8450] dhcp4 (enp0s25): state changed extended -> extended, address=192.168.0.137
Aug 12 22:06:07 NetworkManager[488]: <info> [1628798767.8368] manager: sleep: sleep requested (sleeping: no enabled: yes)
Aug 12 22:06:07 NetworkManager[488]: <info> [1628798767.8369] manager: NetworkManager state is now ASLEEP
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8218] manager: sleep: wake requested (sleeping: yes enabled: yes)
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8219] device (enp0s25): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8220] dhcp4 (enp0s25): canceled DHCP transaction
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8220] dhcp4 (enp0s25): state changed extended -> terminated
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8222] dhcp6 (enp0s25): canceled DHCP transaction
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8222] dhcp6 (enp0s25): state changed bound -> terminated
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.9457] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 12 22:06:19 NetworkManager[488]: <info> [1628798779.1429] manager: NetworkManager state is now DISCONNECTED
Aug 12 22:06:19 NetworkManager[488]: <info> [1628798779.1437] device (enp3s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
`journalctl --boot 0 --unit ModemManager.service --no-hostname --no-pager`
-- Journal begins at Mon 2020-03-30 22:08:21 CEST, ends at Fri 2021-08-13 02:02:14 CEST. --
Aug 12 19:39:17 systemd[1]: Starting Modem Manager...
Aug 12 19:39:19 ModemManager[538]: <info> ModemManager (version 1.16.8) starting in system bus...
Aug 12 19:39:21 systemd[1]: Started Modem Manager.
Aug 12 19:39:24 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 19:39:24 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 22:06:07 ModemManager[538]: <info> [sleep-monitor] system is about to suspend
Aug 12 22:06:18 ModemManager[538]: <info> [sleep-monitor] system is resuming
Aug 12 22:06:21 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 22:06:21 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:37:13 ModemManager[538]: <info> [sleep-monitor] system is about to suspend
Aug 12 23:38:20 ModemManager[538]: <info> [sleep-monitor] system is resuming
Aug 12 23:38:23 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:38:23 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:38:28 ModemManager[538]: <info> [sleep-monitor] system is about to suspend
Aug 12 23:39:35 ModemManager[538]: <info> [sleep-monitor] system is resuming
Aug 12 23:39:37 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:39:37 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:39:40 ModemManager[538]: <info> [sleep-monitor] system is about to suspend
Aug 12 23:40:47 ModemManager[538]: <info> [sleep-monitor] system is resuming
Aug 12 23:40:50 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:40:50 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 12 23:41:06 ModemManager[538]: <info> [sleep-monitor] system is about to suspend
Aug 12 23:42:13 ModemManager[538]: <info> [sleep-monitor] system is resuming
Aug 12 23:42:15 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Aug 12 23:42:15 ModemManager[538]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0': not supported by any plugin
Aug 13 01:28:22 ModemManager[538]: <info> caught signal, shutting down...
Aug 13 01:28:22 systemd[1]: Stopping Modem Manager...
Aug 13 01:28:22 ModemManager[538]: <info> ModemManager is shut down
Aug 13 01:28:22 systemd[1]: ModemManager.service: Deactivated successfully.
Aug 13 01:28:22 systemd[1]: Stopped Modem Manager.
I have read through the whole log… but can’t really grasp what most of the log means… however according to the time of nic issue occurs… these lines of log should be written when the nic issue reoccurance
Aug 12 22:06:07 NetworkManager[488]: <info> [1628798767.8368] manager: sleep: sleep requested (sleeping: no enabled: yes)
Aug 12 22:06:07 NetworkManager[488]: <info> [1628798767.8369] manager: NetworkManager state is now ASLEEP
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8218] manager: sleep: wake requested (sleeping: yes enabled: yes)
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8219] device (enp0s25): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8220] dhcp4 (enp0s25): canceled DHCP transaction
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8220] dhcp4 (enp0s25): state changed extended -> terminated
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8222] dhcp6 (enp0s25): canceled DHCP transaction
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.8222] dhcp6 (enp0s25): state changed bound -> terminated
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.9457] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 12 22:06:19 NetworkManager[488]: <info> [1628798779.1429] manager: NetworkManager state is now DISCONNECTED
Aug 12 22:06:19 NetworkManager[488]: <info> [1628798779.1437] device (enp3s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Aug 12 22:06:18 NetworkManager[488]: <info> [1628798778.9457] manager: NetworkManager state is now CONNECTED_GLOBAL
Does this log means it is connected to internet ?
Aug 12 22:06:19 NetworkManager[488]: <info> [1628798779.1437] device (enp3s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Here is the device sleeping ?? That’s why nic down ? and not responding to “nmcli” command ?
ok…
No idea which device this is: enp0s25 but enp3s0 is the one I saw in your inxi output (maybe the same device, but only renamed?)… however, I see this here:
It could be problem with ipv6, please disable it completely.
No, i have 2 ethernet card… 1 is the used, the other one is working but not used (enp3s0) . So the one show in inxi is the NIC that is plugged in (enp0s25) .
So about “sleeping” problem… I guess it is the correct direction, but I have no idea how to awake it manually…
To see which port has which name… plugin the cable and type:
ip address show up
enp0s25 state UP ← i bet state UP means the NIC is plugged in.
enp3s0 state DOWN
ip address has same output as ip address show up
Could you also post this info:
sudo ethtool enp0s25
Yes… it means it is plugged in and connected.
[How to Disable IPv6 on Linux](Disable ipv6)
I did as in the instruction to disabled permanently ipv6 already.
Is this instruction on the website is good set of instruction ?
Apparently i don’t have this ethtool … install the package ?
$ sudo ethtool enp0s25
Settings for enp0s25:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
This must be related to Wake on LAN, since it is activated:
You can deactivate it temporary with:
sudo ethtool -s enp0s25 wol d
But this is strange:
It has established a connection with enp0s25 but then 1sec after it is disconnected 
Is there more verbose option for this log ? like… networkmanager or modemmanager -vvv verbose log which can shows most detail log ?