Hi,
I bought a new hardware; ASRock B550M Steel Legend Mobo, AMD Ryzen 5600G, 2x8 GB RAM, Samsung 1TB nvme SSD.
I just installed Opensuse 15.3 MATE and need help.
Boot process takes long. Look at 14:53:25 then 14:53:49. Something in the network takes long, desktop or router? IPV6 (I don’t use it)?
Mar 15 14:53:24 ASR5600G systemd[1]: Starting System Logging Service...
Mar 15 14:53:24 ASR5600G rsyslogd[1745]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2106.0]
Mar 15 14:53:24 ASR5600G rsyslogd[1745]: [origin software="rsyslogd" swVersion="8.2106.0" x-pid="1745" x-info="https://www.rsyslog.com"] start
Mar 15 14:53:24 ASR5600G systemd[1]: Started System Logging Service.
Mar 15 14:53:25 ASR5600G avahi-daemon[1125]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::7285:c2ff:fe94:4da7.
Mar 15 14:53:25 ASR5600G avahi-daemon[1125]: New relevant interface eth0.IPv6 for mDNS.
Mar 15 14:53:25 ASR5600G avahi-daemon[1125]: Registering new address record for fe80::7285:c2ff:fe94:4da7 on eth0.*.
Mar 15 14:53:49 ASR5600G wicked[1261]: lo up
Mar 15 14:53:49 ASR5600G wicked[1261]: eth0 setup-in-progress
Mar 15 14:53:49 ASR5600G systemd[1]: Finished wicked managed network interfaces.
Mar 15 14:53:49 ASR5600G systemd[1]: Reached target Network.
Mar 15 14:53:49 ASR5600G systemd[1]: Reached target Network is Online.
Mar 15 14:53:49 ASR5600G systemd[1]: Starting Automounts filesystems on demand...
Mar 15 14:53:49 ASR5600G systemd[1]: Starting NTP client/server...
Mar 15 14:53:49 ASR5600G systemd[1]: Starting Permit User Sessions...
Mar 15 14:53:49 ASR5600G systemd[1]: Finished Permit User Sessions.
Mar 15 14:53:49 ASR5600G systemd[1]: Starting Hold until boot process finishes up...
Mar 15 14:53:49 ASR5600G chronyd[1759]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG)
Mar 15 14:53:49 ASR5600G chronyd[1759]: Frequency 5.602 +/- 1.218 ppm read from /var/lib/chrony/drift
Mar 15 14:53:49 ASR5600G systemd[1]: tmp-autoF3BipS.mount: Succeeded.
Mar 15 14:53:49 ASR5600G systemd[1]: tmp-autoqvnlCT.mount: Succeeded.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Automounts filesystems on demand.
Mar 15 14:53:49 ASR5600G systemd[1]: Starting User Login Management...
Mar 15 14:53:49 ASR5600G systemd[1]: Started NTP client/server.
Mar 15 14:53:49 ASR5600G systemd[1]: Reached target System Time Synchronized.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Backup of RPM database.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Backup of /etc/sysconfig.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Balance block groups on a btrfs filesystem.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Defragment file data and/or directory metadata.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Scrub btrfs filesystem, verify block checksums.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Discard unused blocks on a mounted filesystem.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Check if mainboard battery is Ok.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Discard unused blocks once a week.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Daily rotation of log files.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Do daily mandb update.
Mar 15 14:53:49 ASR5600G systemd[1]: Started Timeline of Snapper Snapshots.
Mar 15 14:53:49 ASR5600G systemd[1]: Reached target Timers.
Mar 15 14:53:49 ASR5600G systemd[1]: Starting Postfix Mail Transport Agent...
Mar 15 14:53:49 ASR5600G echo[1791]: Starting mail service (Postfix)
Mar 15 14:53:49 ASR5600G systemd-logind[1769]: New seat seat0.
Mar 15 14:53:49 ASR5600G systemd-logind[1769]: Watching system buttons on /dev/input/event5 (Power Button)
Mar 15 14:53:49 ASR5600G systemd-logind[1769]: Watching system buttons on /dev/input/event4 (Power Button)
Mar 15 14:53:49 ASR5600G systemd-logind[1769]: Watching system buttons on /dev/input/event2 (ASRock LED Controller)
Mar 15 14:53:49 ASR5600G systemd-logind[1769]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard)
Mar 15 14:53:49 ASR5600G systemd[1]: Started User Login Management.
Mar 15 14:53:49 ASR5600G systemd[1]: Starting X Display Manager...
Mar 15 14:53:49 ASR5600G display-manager[1830]: /etc/vconsole.conf available
Mar 15 14:53:49 ASR5600G display-manager[1830]: KEYMAP: uk
Mar 15 14:53:49 ASR5600G display-manager[1830]: Command: localectl set-keymap uk
Mar 15 14:53:49 ASR5600G display-manager[1830]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Mar 15 14:53:49 ASR5600G dbus-daemon[1127]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by '>
Mar 15 14:53:49 ASR5600G systemd[1]: Starting Locale Service...
Mar 15 14:53:49 ASR5600G dbus-daemon[1127]: [system] Successfully activated service 'org.freedesktop.locale1'
Wicked will correctly wait until the IPv6 address has been correctly resolved – takes time because, the DHCP Server (for private human beings, usually the Router to your ISP) needs some time to confirm the IPv6 address of the host being booted.
Network Manager actually does the same but, it’s not so noticeable …
The other thing which may take some time to settle down is, the synchronisation of the system’s clock to the (stable) clocks out there in the network –
Examples here with a 55 Mb/s DSL connection and 1 Gb/s LAN –
# journalctl -b 0 --output=short-monotonic --no-hostname | grep -Ei 'r8169|8168h|8111h|eth0|wicked|network|DHCP|chrony|nfs|dns|ntp'
0.320339] kernel: Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
1.689627] kernel: drop_monitor: Initializing network drop monitor service
1.923505] systemd-udevd[281]: Network interface NamePolicy= disabled by default.
5.914704] systemd[1]: Mounting NFSD configuration filesystem...
5.968912] kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
5.846773] systemd-udevd[536]: Network interface NamePolicy= disabled by default.
5.859372] systemd[1]: Mounted NFSD configuration filesystem.
6.022334] kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
6.388559] kernel: libphy: r8169: probed
6.388719] kernel: r8169 0000:03:00.0 eth0: RTL8168h/8111h, d4:5d:64:a5:f5:0e, XID 541, IRQ 70
6.388721] kernel: r8169 0000:03:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
9.165166] udevadm[548]: systemd-udev-settle.service is deprecated. Please fix wickedd.service, tpm2-abrmd.service not to pull it in.
9.358946] systemd[1]: Starting NFSv4 ID-name mapping service...
9.359151] systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
9.359276] systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
9.359393] systemd[1]: Reached target NFS client services.
9.359647] systemd[1]: Started NFSv4 ID-name mapping service.
9.399904] systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
9.404184] systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
9.415141] systemd[1]: Starting Alias for NFS client...
9.433170] systemd[1]: Finished Alias for NFS client.
9.457145] systemd[1]: Reached target Host and Network Name Lookups.
9.499074] systemd[1]: Started Avahi mDNS/DNS-SD Stack.
9.500996] avahi-daemon[1184]: Network interface enumeration completed.
9.977944] systemd[1]: Reached target Network (Pre).
9.979181] systemd[1]: Starting wicked AutoIPv4 supplicant service...
9.979998] systemd[1]: Starting wicked DHCPv4 supplicant service...
9.980841] systemd[1]: Starting wicked DHCPv6 supplicant service...
10.013029] systemd[1]: Started wicked DHCPv6 supplicant service.
10.014256] systemd[1]: Started wicked DHCPv4 supplicant service.
10.014490] systemd[1]: Started wicked AutoIPv4 supplicant service.
10.015372] systemd[1]: Starting wicked network management service daemon...
10.032710] systemd[1]: Started wicked network management service daemon.
10.033615] systemd[1]: Starting wicked network nanny service...
10.048318] systemd[1]: Started wicked network nanny service.
10.049165] systemd[1]: Starting wicked managed network interfaces...
11.406299] kernel: Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
11.582702] kernel: r8169 0000:03:00.0 eth0: Link is Down
14.679917] kernel: r8169 0000:03:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
14.679935] kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
14.526135] wickedd-dhcp4[1317]: eth0: Request to acquire DHCPv4 lease with UUID c13d3062-0b66-0400-2c05-000005000000
14.528243] wickedd-dhcp6[1318]: eth0: Request to acquire DHCPv6 lease with UUID c13d3062-0b66-0400-2c05-000006000000 in mode auto
15.550463] avahi-daemon[1184]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::d65d:64ff:fea5:f50e.
15.551082] avahi-daemon[1184]: New relevant interface eth0.IPv6 for mDNS.
15.551189] avahi-daemon[1184]: Registering new address record for fe80::d65d:64ff:fea5:f50e on eth0.*.
19.930428] wickedd-dhcp4[1317]: eth0: Committed DHCPv4 lease with address 192.168.178.27 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
20.046333] avahi-daemon[1184]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.27.
20.046913] avahi-daemon[1184]: New relevant interface eth0.IPv4 for mDNS.
20.047027] avahi-daemon[1184]: Registering new address record for 192.168.178.27 on eth0.IPv4.
21.438489] avahi-daemon[1184]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::d65d:64ff:fea5:f50e.
21.439082] avahi-daemon[1184]: Joining mDNS multicast group on interface eth0.IPv6 with address 2001:9e8:34b9:e800:c4f4:a437:57a1:8bd2.
21.439187] avahi-daemon[1184]: Registering new address record for 2001:9e8:34b9:e800:c4f4:a437:57a1:8bd2 on eth0.*.
21.439290] avahi-daemon[1184]: Withdrawing address record for fe80::d65d:64ff:fea5:f50e on eth0.
21.558092] wickedd-dhcp6[1318]: eth0: Committing empty DHCPv6 lease
21.566472] avahi-daemon[1184]: Registering new address record for 2001:9e8:34b9:e800:d65d:64ff:fea5:f50e on eth0.*.
21.782201] wicked[1338]: lo up
21.782201] wicked[1338]: eth0 up
21.782763] systemd[1]: Finished wicked managed network interfaces.
21.783078] systemd[1]: Reached target Network.
21.783172] systemd[1]: Reached target Network is Online.
21.783847] systemd[1]: Starting NTP client/server...
21.785510] systemd[1]: Starting NFS Mount Daemon...
21.786279] systemd[1]: Starting NFS status monitor for NFSv2/3 locking....
21.799576] chronyd[2033]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG)
21.802015] systemd[1]: Started NFS Mount Daemon.
21.810048] chronyd[2033]: Frequency 5.430 +/- 1.479 ppm read from /var/lib/chrony/drift
21.834343] systemd[1]: Started NFS status monitor for NFSv2/3 locking..
21.835494] systemd[1]: Starting NFS server and services...
21.842602] systemd[1]: Started NTP client/server.
21.843359] systemd[1]: Starting Wait for chrony to synchronize system clock...
23.112677] kernel: NFSD: Using UMH upcall client tracking operations.
23.112681] kernel: NFSD: starting 90-second grace period (net f0000098)
22.949470] systemd[1]: Finished NFS server and services.
22.951685] systemd[1]: Starting Notify NFS peers of a restart...
22.957312] systemd[1]: Started Notify NFS peers of a restart.
34.234750] chronyd[2033]: Selected source 195.186.1.101
44.164220] systemd[1]: Finished Wait for chrony to synchronize system clock.
164.149662] chronyd[2033]: Selected source 131.188.3.223
Please be aware that, I prefer to have accurate time-keeping –
My ISP supplies only IPv6 on the DSL stream, which also carries our VoIP telephone traffic – IPv4 runs via a DS-Lite-Tunnel –
AFAICS, my IPv4 address is shared with other customers of our ISP – it’s geolocation is quite different to the geolocation of my Router’s IPv6 address …
Operating System: openSUSE Leap 15.3
KDE Plasma Version: 5.18.6
KDE Frameworks Version: 5.76.0
Qt Version: 5.12.7
Kernel Version: 5.3.18-150300.59.54-default
OS Type: 64-bit
Processors: 8 × AMD Ryzen 5 3400G with Radeon Vega Graphics
Memory: 13,6 GiB
[HR][/HR]Please be aware that, I am an IPv6 advocate –
This planet has limited resources and, IPv4 address space is one of the (very) limited resources … >:)
**erlangen:~ #** systemd-analyze critical-chain network.target
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
network.target @791ms
└─**systemd-resolved.service @710ms +80ms**
└─**systemd-tmpfiles-setup.service @674ms +31ms**
└─**systemd-journal-flush.service @410ms +263ms**
└─**var.mount @403ms +5ms**
└─local-fs-pre.target @394ms
└─**systemd-tmpfiles-setup-dev.service @380ms +13ms**
└─**kmod-static-nodes.service @364ms +8ms**
└─systemd-journald.socket
└─system.slice
└─-.slice
**erlangen:~ #**
**erlangen:~ #** journalctl -b -u systemd-networkd.service -u systemd-resolved.service -o short-monotonic
3.224420] erlangen systemd[1]: Starting Network Configuration...
3.224481] erlangen systemd-networkd[689]: lo: Link UP
3.245255] erlangen systemd-networkd[689]: lo: Gained carrier
3.245404] erlangen systemd-networkd[689]: Enumeration completed
3.245453] erlangen systemd[1]: Started Network Configuration.
3.263263] erlangen systemd[1]: Starting Network Name Resolution...
3.328841] erlangen systemd-resolved[731]: Positive Trust Anchors:
3.335984] erlangen systemd-resolved[731]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
3.336047] erlangen systemd-resolved[731]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.>
3.342630] erlangen systemd-resolved[731]: Using system hostname 'erlangen'.
3.343677] erlangen systemd[1]: Started Network Name Resolution.
4.009930] erlangen systemd-networkd[689]: eth0: Link UP
6.632616] erlangen systemd-networkd[689]: eth0: Gained carrier
8.045945] erlangen systemd-networkd[689]: eth0: Gained IPv6LL
12.441858] erlangen systemd-networkd[689]: eth0: DHCPv4 address 192.168.178.30/24 via 192.168.178.1
**erlangen:~ #**
It seems that, somehow, the news that, there ain’t no more IPv4 addresses available, hasn’t reached some of the human beings on this planet – yet … >:)
Hi
That’s why RTC is there for that time period My RPi acting as the time server has a pps gps and RTC present. But as shown it’s a process that takes place elsewhere and does not affect the booting of the system as such.
Hi
If not using ipv6, sure However, you need to edit /etc/postfix/main.cf file as well… Change line ~706 intet_protocols = all to inet_protocols = ipv4 and save.
Before doing a big mistake, please could you confirm with the following info, that IPv6 is not used.
I have a Linksys WRT32X modem/router firmware OpenWRT. ISP is from a wireless aerial on the roof with PoE.
There is a network between the router and aerial (255.255.255.252). Another network for home LAN.
I have 2 interfaces for WAN, 1 for IPv4 1 for IPv6. IPv6 is “not started on boot” and all IPv6 setting a empty.
In IPv4, IPv6 assignment length is disabled.
I thing I could delete the IPv6 interface but it’s working, I leave it. Don’t touch it!
So with that I guess IPv6 is not used.
Do you agree?
If yes, I’ll change Leap in the GUI and the file as you explained.
You need to check the link via the aerial on the roof to your ISP –
That link may be using IPv6 because, that’s the way you ISP possibly/probably wants it.
You’ll also have to check if, there’s an IPv4 tunnel to your ISP.
Then, you need to check if, your modem/router supports IPv4 only on the LAN/WLAN interfaces given that, your ISP probably/possibly wants to use IPv6 on the interface supporting the link via the wireless aerial on your roof …
Hi
How does network infrastructure affect a computer that is getting a valid ipv4 address, routing etc… I think you need to stay focused on the users computer and end use.
Please set your system’s local host name to something other than “localhost”.
Either set it via YaST or, set it in ‘/etc/hostname’ …
N.B.: ‘/etc/HOSTNAME’ is a link to ‘/etc/hostname’ – both the file and the link are provided by the RPM package “netcfg”.
If you really want to disable IPv6 on your LAN/WLAN then, you need to disable (and, possibly, mask) the “wickedd-dhcp6.service”.
My RPi acting as the time server has a pps gps and RTC present. But as shown it’s a process that takes place elsewhere and does not affect the booting of the system as such.