Is there a quick tweak I could make, to load wicker after GDM? It hangs for a long time. Even on a decent system with a modern AMD chip it’s still really slow to load Gnome. Nearly five minutes, it feels like!
On Sat 05 Aug 2017 11:16:01 PM CDT, kiwicoder wrote:
Is there a quick tweak I could make, to load wicker after GDM? It hangs
for a long time. Even on a decent system with a modern AMD chip it’s
still really slow to load Gnome. Nearly five minutes, it feels like!
Hi
Once your at the desktop, run the following command and post back the
output to see what’s slowing it all down;
systemd-analyze critical-chain
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
The time after the unit is active or started is printed after the "@" character.The time the unit takes to start is printed after the "+" character.
graphical.target @33.990s
└─multi-user.target @33.990s
└─cron.service @33.989s
└─postfix.service @31.645s +2.325s
└─time-sync.target @31.451s
└─ntpd.service @31.065s +385ms
└─network.target @31.025s
└─wicked.service @13.385s +17.639s
└─wickedd-nanny.service @13.380s +4ms
└─wickedd.service @13.366s +12ms
└─wickedd-dhcp6.service @13.233s +106ms
└─SuSEfirewall2_init.service @10.649s +2.542s
└─basic.target @10.627s
└─sockets.target @10.627s
└─avahi-daemon.socket @10.627s
└─sysinit.target @10.626s
└─systemd-update-utmp.service @10.598s +26ms
└─systemd-tmpfiles-setup.service @10.526s +71ms
└─systemd-journal-flush.service @5.757s +4.753s
└─var-log.mount @4.972s +764ms
└─dev-disk-by\x2duuid-651b0e03\x2d21e5\x2d4555\x2d9cec\x2d24307033ad96.device @4.938s
On Sun 06 Aug 2017 12:46:02 AM CDT, kiwicoder wrote:
Code:
The time after the unit is active or started is printed after the
“@” character.The time the unit takes to start is printed after the “+”
character.
graphical.target @33.990s
└─multi-user.target @33.990s
└─cron.service @33.989s
└─postfix.service @31.645s +2.325s
└─time-sync.target @31.451s
└─ntpd.service @31.065s +385ms
└─network.target @31.025s
└─wicked.service @13.385s +17.639s
└─wickedd-nanny.service @13.380s +4ms
└─wickedd.service @13.366s +12ms
└─wickedd-dhcp6.service @13.233s +106ms
└─SuSEfirewall2_init.service @10.649s +2.542s
└─basic.target @10.627s
└─sockets.target @10.627s
└─avahi-daemon.socket @10.627s
└─sysinit.target @10.626s
└─systemd-update-utmp.service @10.598s +26ms
└─systemd-tmpfiles-setup.service @10.526s +71ms
└─systemd-journal-flush.service @5.757s +4.753s
└─var-log.mount @4.972s +764ms
└─dev-disk-by\x2duuid-651b0e03\x2d21e5\x2d4555\x2d9cec\x2d24307033ad96.device
@4.938s
HI
OK, have you considered moving to use NetworkManager since you
starting a DE, plus do you need ipv6?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I’ll move to Network Manager and disable ipv6 then. It’s easy enough to do that without breaking stuff, am I right?
Hi
Yes, fire up YaST -> Network Settings and on the global tab, in the Network Setup Method dropdown select NetworkManager, then on the same tab uncheck the Enable IPv6.
A reboot is required…
I haven’t timed it or anything but it’s probably a few seconds faster. By the way how did you remove the newline characters plus the other junk? Did you use a formatting tool or do it manually?
On Sun 06 Aug 2017 03:36:01 AM CDT, kiwicoder wrote:
I haven’t timed it or anything but it’s probably a few seconds faster.
By the way how did you remove the newline characters plus the other
junk? Did you use a formatting tool or do it manually?
Hi
That disappeared because I replied via nntp (claws-mail) rather than
the web interface 
Also look at;
systemd-analyze
systemd-analyze blame
Things happen in parallel, also if there is a check going on, purging
old kernels etc you wont see this in the critical-chain output.
Is the system single boot?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I’m running a fresh installation of OpenSUSE on my mechanical hard drive, and I have Windows 10 (bloatware) on the fast SSD
So dual-boot, but on separate drives.
Hi
Well you could wind back the time spent waiting at the grub screen (YaST Bootloader), the other thing I do is remove plymouth (a few steps for this though).