I’m thinking anyone coming close to my time might freely share how they did it (averages seem to be 20s)
My hw-probe seemingly has blame though! It also has hints to everything else (grub shows my kernel parameters, modprobe.d on the main page has fun stuff)
Each step needs to be looked at, for example firmware is pretty much it aside from BIOS options set, loader, hide it if single boot… Your kernel and Initd can for sure be tweaked to omit many more devices these days. User space is very DE dependent.
I can knock a few seconds off with dracut tweaks, but meh, is it worth the effort. I just want the system to be up and running when I come back with a coffee
However it’s a good indicator along with blame to see what is what, especially for maintenance or relabel going on.
HP Z440 (Tumbleweed) (NVMe) (grub-efi);
systemd-analyze
Startup finished in 1.545s (kernel) + 2.666s (initrd) + 5.256s (userspace) = 9.468s
graphical.target reached after 5.227s in userspace.
tw2026:~ # journalctl --output short-monotonic --boot 0 --unit init.scope --grep Started
[ 0.997123] tw2026 systemd[1]: Started Rule-based Manager for Device Events and Files.
[ 1.106849] tw2026 systemd[1]: Started Show Plymouth Boot Screen.
[ 1.107384] tw2026 systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
[ 3.377649] tw2026 systemd[1]: Started Rule-based Manager for Device Events and Files.
[ 3.923365] tw2026 systemd[1]: Started Show Plymouth Boot Screen.
[ 4.244554] tw2026 systemd[1]: Started Load/Save RF Kill Switch Status.
[ 5.280573] tw2026 systemd[1]: Started Security Audit Logging Service.
[ 5.280893] tw2026 systemd[1]: Started Watch /etc/sysconfig/btrfsmaintenance.
[ 5.281355] tw2026 systemd[1]: Started Watch for changes in CA certificates.
[ 5.282251] tw2026 systemd[1]: Started CUPS Scheduler.
[ 5.282309] tw2026 systemd[1]: Started Watch for changes in smartmontools sysconfig file.
[ 5.282358] tw2026 systemd[1]: Started Hourly Cleanup of Snapper Snapshots.
[ 5.282392] tw2026 systemd[1]: Started Daily Cleanup of Temporary Directories.
[ 5.314386] tw2026 systemd[1]: Started D-Bus System Message Bus.
[ 5.328091] tw2026 systemd[1]: Started irqbalance daemon.
[ 5.388585] tw2026 systemd[1]: Started Machine Check Exception Logging Daemon.
[ 5.438566] tw2026 systemd[1]: Started Bluetooth service.
[ 5.438976] tw2026 systemd[1]: Started Avahi mDNS/DNS-SD Stack.
[ 5.485286] tw2026 systemd[1]: Started Self Monitoring and Reporting Technology (SMART) Daemon.
[ 5.508739] tw2026 systemd[1]: Started User Login Management.
[ 5.512895] tw2026 systemd[1]: Started Switcheroo Control Proxy service.
[ 5.519298] tw2026 systemd[1]: Started wtmpdb daemon.
[ 5.545874] tw2026 systemd[1]: Started Authorization Manager.
[ 5.561340] tw2026 systemd[1]: Started Hostname Service.
[ 5.613570] tw2026 systemd[1]: Started Network Manager Script Dispatcher Service.
[ 5.622758] tw2026 systemd[1]: Started Modem Manager.
[ 6.168310] tw2026 systemd[1]: Started Network Manager.
[ 6.268028] tw2026 systemd[1]: Started WPA Supplicant daemon.
[ 6.327336] tw2026 systemd[1]: Started Getty on tty1.
[ 6.372903] tw2026 systemd[1]: Started CUPS Scheduler.
[ 6.373594] tw2026 systemd[1]: Started NTP client/server.
[ 6.374407] tw2026 systemd[1]: Started Backup of RPM database.
[ 6.374610] tw2026 systemd[1]: Started Backup of /etc/sysconfig.
[ 6.374838] tw2026 systemd[1]: Started Balance block groups on a btrfs filesystem.
[ 6.375054] tw2026 systemd[1]: Started Defragment file data and/or directory metadata.
[ 6.375261] tw2026 systemd[1]: Started Scrub btrfs filesystem, verify block checksums.
[ 6.375465] tw2026 systemd[1]: Started Discard unused blocks on a mounted filesystem.
[ 6.375670] tw2026 systemd[1]: Started Check if mainboard battery is Ok.
[ 6.375911] tw2026 systemd[1]: Started Discard unused filesystem blocks once a week.
[ 6.376133] tw2026 systemd[1]: Started Daily rotation of log files.
[ 6.376332] tw2026 systemd[1]: Started Daily man-db regeneration.
[ 6.376537] tw2026 systemd[1]: Started Timeline of Snapper Snapshots.
[ 6.376740] tw2026 systemd[1]: Started Monthly rotation of wtmpdb.
[ 6.514616] tw2026 systemd[1]: Started OpenSSH Daemon.
[ 6.839105] tw2026 systemd[1]: Started X Display Manager.
[ 7.044265] tw2026 systemd[1]: Started Postfix Mail Transport Agent.
[ 7.046057] tw2026 systemd[1]: Started Command Scheduler.
[ 7.658318] tw2026 systemd[1]: Started User Manager for UID 462.
[ 7.659233] tw2026 systemd[1]: Started Session 1 of User sddm.
tw2026:~ #
The KDE user session takes 5 seconds:
karl@tw2026:~> journalctl --output short-monotonic --user --boot 0 --unit init.scope -g Started
[ 5613.619644] tw2026 systemd[2125]: Started Submitting pending crash events (file monitor).
[ 5613.619780] tw2026 systemd[2125]: Started Cleanup lingering KCrash metadata.
[ 5613.619825] tw2026 systemd[2125]: Started Daily Cleanup of User's Temporary Directories.
[ 5613.631233] tw2026 systemd[2125]: Started Cleanup lingering KCrash metadata.
[ 5613.942488] tw2026 systemd[2125]: Started D-Bus User Message Bus.
[ 5614.086056] tw2026 systemd[2125]: Started dbus-:1.2-org.kde.KSplash@0.service.
[ 5614.129692] tw2026 systemd[2125]: Started KDE Window Manager.
[ 5614.165318] tw2026 systemd[2125]: Started KDE Global Shortcuts Server.
[ 5614.168173] tw2026 systemd[2125]: Started Baloo File Indexer Daemon.
[ 5614.203125] tw2026 systemd[2125]: Started sandboxed app permission store.
[ 5614.228658] tw2026 systemd[2125]: Started flatpak document portal service.
[ 5614.678949] tw2026 systemd[2125]: Started PipeWire Multimedia Service.
[ 5614.681015] tw2026 systemd[2125]: Started Multimedia Service Session Manager.
[ 5615.140423] tw2026 systemd[2125]: Started KDE Config Module Initialization.
[ 5615.145203] tw2026 systemd[2125]: Started Unlock kwallet from pam credentials.
[ 5615.377040] tw2026 systemd[2125]: Started KDE Session Management Server.
[ 5615.389395] tw2026 systemd[2125]: Started KDE Daemon 6.
[ 5615.424269] tw2026 systemd[2125]: Started User preferences database.
[ 5615.551393] tw2026 systemd[2125]: Started PipeWire PulseAudio.
[ 5615.830878] tw2026 systemd[2125]: Started Bluetooth OBEX service.
[ 5616.005723] tw2026 systemd[2125]: Started KDE Plasma Workspace.
[ 5616.007322] tw2026 systemd[2125]: Started Consume pending crashes using DrKonqi.
[ 5616.008881] tw2026 systemd[2125]: Started Proxies GTK DBus menus to a Plasma readable format.
[ 5616.012436] tw2026 systemd[2125]: Started KAccess.
[ 5616.029400] tw2026 systemd[2125]: Started Handle legacy xembed system tray icons.
[ 5616.066324] tw2026 systemd[2125]: Started KActivityManager Activity manager Service.
[ 5616.293493] tw2026 systemd[2125]: Started KDE PolicyKit Authentication Agent.
[ 5616.380605] tw2026 systemd[2125]: Started Xdg Desktop Portal For KDE.
[ 5618.009844] tw2026 systemd[2125]: Started Powerdevil.
[ 5618.057790] tw2026 systemd[2125]: Started Welcome launcher.
[ 5618.075178] tw2026 systemd[2125]: Started Plasma Session Restore.
[ 5618.076284] tw2026 systemd[2125]: Started Calendar Reminders.
karl@tw2026:~>
-y222 for inxi means after clicking the enlarge perimeter button on the code block I must unzoom 3 times (smaller text than normal) to get all 222 columns onto the screen at once, along with about 20rem of whitespace on both sides. Of course, unzooming 3 times makes it illegible.
That’s exactly what “the enlarge perimeter button on the code block” meant. Hovering it does not tell me that the icon means view code, nor the one next to it, unlike icons at the bottom of each post. Whether or not I click it, I’m viewing the page, including code blocks within.
Fine for your own use, not here where line length is constrained by the forum page’s CSS. Your screenshot shows what your browser does is just like what mine does here, but with the big difference that I can’t read mousetype, so fonts here must be 3-4 times as big, and can’t fit the available space.
pavin@suse-pc:~> systemd-analyze time
Startup finished in 17.440s (firmware) + 20.984s (loader) + 728ms (kernel) + 7.005s (initrd) + 41.836s (userspace) = 1min 27.995s
graphical.target reached after 41.836s in userspace.
Here’s mine, don’t think it paints the full picture.
My firmware is slow but I do kexec reboots so the firmware and loader parts don’t count 99% of the time. I do firmware boots once every few months only.
The userspace time is also misleading, my vanilla Gnome desktop is up and usable long before some of the slower services I have like an LVM RAID on top of a bunch of USB drives and containers become online.
Offtopic edit: why is discourse changing my 4 leaf clover emoji to 3 leaf
Mom (98) suffers from Macular degeneration. She switched from a 16" notebook to an ASUS NUC 14 Essential mounted to the back of an 32" external display. She uses Scale 300% and Font size 15pt. Viewing distance is 10". She uses the mouse wheel for vertical scroll and shift+mouse wheel for horizontal scroll.
That it does. My browsers are set to default sizes to match my environment, not the tiny sizes web page sizes designers have traditionally preferred, and the small sizes web browsers I’m familiar with still get provided as defaults.
With preformatted text boxes, the upper right hand corner has an icon you can click (when you hover over it) to expand the size of the text window so you don’t have to scroll horizontally. It will use - as far as I can tell - the entire width of your screen (I just tried it on my ultra-wide monitor, and it extended almost the full width).
Except as I explained to Karl, that’s not how it works here. That button does what it’s supposed to do, except that it cannot go far enough to fit 222 columns without scrolling and at the same time keep text legible. To exacerbate the issue, the forum formatting wastes much space at the sides even with code block expanded. Only during post composition is the side waste reduced to negligible. Web page constructors universally fail to show any understanding that while browser windows can be narrowed when reducing line length is desired by the reader, the opposite is impossible when the browser text size is custom (enlarged) and/or its window already fullscreen, which here, and I’ve often seen elsewhere, they virtually always are. Good, comfortable text size to line length ratio is often very difficult to get from the web, though it has improved noticeably since constructors began favoring needs of mobile device users. Discourse formatting isn’t so bad either, but its variable output length pages, like Facebook’s, by whatever their W3C name, are horribly annoying to scroll through on any but shorter threads.
Why almost? Why not entire? That’s an example of the excess whitespace.