$ systemd-analyze blame
10.649s man-db.service
1.314s updatedb.service
1.184s systemd-random-seed.service
777ms lvm2-monitor.service
429ms tlp.service
350ms firewalld.service
340ms dev-sdb2.device
309ms systemd-fsck@dev-disk-by\x2duuid-c1ab3d60\x2d2563\x2d4296\x2d9f2d\x2dae38bdfdc73e.service
291ms iwd.service
232ms udisks2.service
215ms home-home-seagate.mount
137ms accounts-daemon.service
114ms upower.service
110ms polkit.service
99ms systemd-resolved.service
93ms systemd-udev-trigger.service
90ms ldconfig.service
85ms user@1000.service
74ms avahi-daemon.service
70ms systemd-tmpfiles-clean.service
66ms systemd-logind.service
65ms systemd-journald.service
62ms systemd-fsck@dev-disk-by\x2duuid-28A9\x2d696D.service
57ms systemd-networkd.service
53ms logrotate.service
52ms NetworkManager.service
48ms systemd-udevd.service
47ms modprobe@drm.service
47ms lightdm.service
42ms systemd-timesyncd.service
42ms systemd-fsck@dev-disk-by\x2duuid-6ed67ed9\x2d911d\x2d4a94\x2d99b5\x2d9942d36b032e.service
39ms systemd-tmpfiles-setup.service
36ms systemd-sysusers.service
28ms systemd-modules-load.service
27ms kmod-static-nodes.service
26ms systemd-tmpfiles-setup-dev.service
25ms modprobe@configfs.service
24ms modprobe@fuse.service
22ms boot-efi.mount
22ms dev-hugepages.mount
21ms dev-mqueue.mount
20ms sys-kernel-tracing.mount
19ms wpa_supplicant.service
17ms systemd-journal-catalog-update.service
15ms bluetooth.service
13ms systemd-remount-fs.service
12ms home.mount
11ms systemd-sysctl.service
11ms tmp.mount
10ms systemd-update-utmp.service
9ms sys-fs-fuse-connections.mount
8ms user-runtime-dir@1000.service
8ms alsa-restore.service
7ms sys-kernel-config.mount
6ms systemd-user-sessions.service
6ms systemd-journal-flush.service
5ms systemd-rfkill.service
4ms systemd-update-done.service
3ms rtkit-daemon.service
I notice in your output you donât have a driver loaded for the ethernet? Is there a reason for that?
What driver did you install for the WiFi specifically? From the AUR? Or does it load automatically as a kernel module?
I am using a 4G router (see attached image) which has no ethernet port. The only way to connect is WiFi so I have never used my ethernet so I donât know.
I didnât install any WiFi driver manually. This WiFi worked out of the box previously under LMDE & now under EndeavourOS/Arch
Thatâs fine Iâm just asking. Even though your router doesnât have an Ethernet port it does show Ethernet which would normally have a driver loaded for it. It would either use the r8168 package in EndeavourOS or the r8169 kernel module on boot. So it just seems strange that it lists no driver. But i understand you only have WiFi access.
debugging would may give more info then searching for random solutions replacing hardware or softwareâŚ
open a terminal and watch the journal:
journalctl -f > journal.log
this will start writing log to the file journal.log âŚ
now disconnect wifi and reconnect wait till it is connected and do nothing else while this time⌠then Ctrl+x to kill the logwrite in terminal and give us the log:
cat journal.log | eos-sendlog
this will pastebin it and gives a short url that links to the pastebiin.
You can try adding the following to
/etc/NetworkManager/conf.d/wifi_rand_mac.conf
add
[device]
wifi.scan-rand-mac-address=no
I must mention one thing which makes this issue even more difficult to solve. Every time I boot NM always takes a long time to connect but if I manually disconnect/reconnect the connection time is random. Sometimes its long & sometimes fast(normal).
Okay I will add that line now but to make sure it worked I must reboot. I will reply as soon as I reboot.
/etc/NetworkManager/conf.d/wifi_rand_mac.conf
This file didnât exist so I created it & added that line. Is this acceptable ?
Yes thatâs what you do.
No its not that. As I said I need to reboot to confirm if that solution worked. I am working on a Libreoffice doc. My work is almost done. I will reboot & reply withing 5 mins.
Well hopefully itâs stayâs working!
Aug 10 19:41:55 home-system audit[384]: NETFILTER_CFG table=firewalld:1;filter_INPUT_ZONES:151 family=1 entries=311 op=nft_unregister_rule pid=384 comm="firewalld"
Aug 10 19:41:55 home-system audit[384]: NETFILTER_CFG table=firewalld:1;nat_POSTROUTING_ZONES:139 family=1 entries=312 op=nft_unregister_rule pid=384 comm="firewalld"
Aug 10 19:41:55 home-system audit[384]: NETFILTER_CFG table=firewalld:1;filter_FORWARD_ZONES:162 family=1 entries=313 op=nft_unregister_rule pid=384 comm="firewalld"
Aug 10 19:41:55 home-system audit[384]: NETFILTER_CFG table=firewalld:1;nat_PREROUTING_ZONES:134 family=1 entries=314 op=nft_unregister_rule pid=384 comm="firewalld"
Aug 10 19:41:55 home-system audit[384]: NETFILTER_CFG table=firewalld:1;mangle_PREROUTING_ZONES:129 family=1 entries=315 op=nft_unregister_rule pid=384 comm="firewalld"
Aug 10 19:41:55 home-system audit[384]: NETFILTER_CFG table=?:0;?:0 family=0 entries=11 op=nft_register_gen pid=384 comm="firewalld"
Aug 10 19:41:55 home-system audit[384]: SYSCALL arch=c000003e syscall=46 success=yes exit=416 a0=6 a1=79647b6c5170 a2=0 a3=79647b6b409c items=0 ppid=1 pid=384 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="firewalld" exe="/usr/bin/python3.9" key=(null)
Aug 10 19:41:55 home-system audit: PROCTITLE proctitle=2F7573722F62696E2F707974686F6E002F7573722F62696E2F6669726577616C6C64002D2D6E6F666F726B002D2D6E6F706964
Aug 10 19:41:55 home-system kernel: audit: type=1325 audit(1628604715.032:254): table=firewalld:1;filter_INPUT_ZONES:151 family=1 entries=311 op=nft_unregister_rule pid=384 comm="firewalld"
Aug 10 19:41:55 home-system kernel: audit: type=1325 audit(1628604715.032:254): table=firewalld:1;nat_POSTROUTING_ZONES:139 family=1 entries=312 op=nft_unregister_rule pid=384 comm="firewalld"
Aug 10 19:41:55 home-system kernel: audit: type=1325 audit(1628604715.032:254): table=firewalld:1;filter_FORWARD_ZONES:162 family=1 entries=313 op=nft_unregister_rule pid=384 comm="firewalld"
Aug 10 19:41:55 home-system kernel: audit: type=1325 audit(1628604715.032:254): table=firewalld:1;nat_PREROUTING_ZONES:134 family=1 entries=314 op=nft_unregister_rule pid=384 comm="firewalld"
Aug 10 19:41:55 home-system kernel: audit: type=1325 audit(1628604715.032:254): table=firewalld:1;mangle_PREROUTING_ZONES:129 family=1 entries=315 op=nft_unregister_rule pid=384 comm="firewalld"
using local firewall?
Yes, Nfatables with the FirewallD frontend.
check firewall config then to make sure it is not causing the issue
The problem is solved using this method.
Sorry @ricklinux & everyone adding that line didnât fix the issue. Troubleshooting this is quite frustrating coz its not constant.
@joekamprad
I donât think the firewall is causing this coz I am facing this problem since a fresh install of EndeavourOS. At that point nothing other than what is included by default was installed.
Some else too was facing this issue & that too under Arch but sadly no solution was found. Please read this >> https://bbs.archlinux.org/viewtopic.php?id=131884
Itâs interesting to note that the last message in that thread suggests wicd-gtk which uses icd as a backend. Itâs pretty much the same solution I came to by installing networkmanager-icd.