Again please be more considerate towards others, because $20 can be a LOT of money in another country…
Not everyone lives in the USA…
Anyhow guys, lets keep focusing on the problem
Again please be more considerate towards others, because $20 can be a LOT of money in another country…
Not everyone lives in the USA…
Anyhow guys, lets keep focusing on the problem
Thank you, I misunderstood completely then. So the correct command would then be:
journalctl --priority=4 --boot=0 --no-pager
Well, I did not come here for an arguement, especially one I have no idea what you are talking about. Mirdarthos I always disable bluetooth and remove it from autostart. Is that correct?
journalctl --priority=4 --boot=0 --no-pager
Dec 02 16:03:26 470g3 kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Dec 02 16:03:26 470g3 kernel: x86/cpu: SGX disabled by BIOS.
Dec 02 16:03:26 470g3 kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Dec 02 16:03:26 470g3 kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
Dec 02 16:03:26 470g3 kernel: #3
Dec 02 16:03:26 470g3 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Dec 02 16:03:26 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:03:26 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:03:27 470g3 kernel: usb: port power management may be unreliable
Dec 02 16:03:49 470g3 kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Dec 02 16:03:49 470g3 kernel: hp_wmi: query 0x4 returned error 0x5
Dec 02 16:03:49 470g3 kernel: hp_wmi: query 0xd returned error 0x5
Dec 02 16:03:49 470g3 kernel: hp_wmi: query 0x1b returned error 0x5
Dec 02 16:03:49 470g3 kernel: at24 0-0050: supply vcc not found, using dummy regulator
Dec 02 16:03:49 470g3 kernel: r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
Dec 02 16:03:49 470g3 kernel: ATPX version 1, functions 0x00000003
Dec 02 16:03:49 470g3 kernel: ATPX Hybrid Graphics
Dec 02 16:03:49 470g3 kernel: kfd kfd: amdgpu: TOPAZ not supported in kfd
Dec 02 16:03:49 470g3 kernel: kauditd_printk_skb: 160 callbacks suppressed
Dec 02 16:03:49 470g3 kernel: thermal thermal_zone8: failed to read out thermal zone (-61)
Dec 02 16:03:49 470g3 kernel: amdgpu: can't get the mac of 5
Dec 02 16:03:49 470g3 kernel: Bluetooth: hci0: Reading supported features failed (-16)
Dec 02 16:03:49 470g3 kernel: amdgpu: VI should always have 2 performance levels
Dec 02 16:03:49 470g3 kernel: amdgpu: can't get the mac of 5
Dec 02 16:03:49 470g3 kernel: amdgpu: VI should always have 2 performance levels
Dec 02 16:03:50 470g3 systemd[704]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Dec 02 16:03:54 470g3 bluetoothd[704]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Dec 02 16:03:54 470g3 bluetoothd[704]: src/plugin.c:plugin_init() Failed to init vcp plugin
Dec 02 16:03:55 470g3 kernel: kauditd_printk_skb: 6 callbacks suppressed
Dec 02 16:03:54 470g3 bluetoothd[704]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Dec 02 16:03:54 470g3 bluetoothd[704]: src/plugin.c:plugin_init() Failed to init mcp plugin
Dec 02 16:03:54 470g3 bluetoothd[704]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Dec 02 16:03:54 470g3 bluetoothd[704]: src/plugin.c:plugin_init() Failed to init bap plugin
Dec 02 16:04:01 470g3 kernel: amdgpu: can't get the mac of 5
Dec 02 16:04:08 470g3 kernel: kauditd_printk_skb: 1 callbacks suppressed
Dec 02 16:04:10 470g3 kernel: amdgpu: VI should always have 2 performance levels
Dec 02 16:04:12 470g3 kernel: amdgpu: can't get the mac of 5
Dec 02 16:04:16 470g3 lightdm[1049]: gkr-pam: no password is available for user
Dec 02 16:04:17 470g3 systemd-xdg-autostart-generator[1060]: Configuration file /home/bugster/.config/autostart/xfce-panel-workaround.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Dec 02 16:04:17 470g3 systemd-xdg-autostart-generator[1060]: Configuration file /home/bugster/.config/autostart/xfce-pbw.sh is marked executable. Please remove executable permission bits. Proceeding anyway.
Dec 02 16:04:17 470g3 systemd-xdg-autostart-generator[1060]: /home/bugster/.config/autostart/xfce-pbw.sh:2: Assignment outside of section. Ignoring.
Dec 02 16:04:17 470g3 systemd-xdg-autostart-generator[1060]: /home/bugster/.config/autostart/xfce-pbw.sh:3: Assignment outside of section. Ignoring.
Dec 02 16:04:17 470g3 systemd-xdg-autostart-generator[1060]: /home/bugster/.config/autostart/xfce-pbw.sh:4: Assignment outside of section. Ignoring.
Dec 02 16:04:17 470g3 systemd-xdg-autostart-generator[1060]: /home/bugster/.config/autostart/xfce-pbw.sh:5: Assignment outside of section. Ignoring.
Dec 02 16:04:17 470g3 systemd-xdg-autostart-generator[1060]: /home/bugster/.config/autostart/xfce-pbw.sh:6: Assignment outside of section. Ignoring.
Dec 02 16:04:17 470g3 systemd-xdg-autostart-generator[1060]: /home/bugster/.config/autostart/xfce-pbw.sh:7: Assignment outside of section. Ignoring.
Dec 02 16:04:17 470g3 systemd-xdg-autostart-generator[1060]: /home/bugster/.config/autostart/xcape.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
Dec 02 16:04:19 470g3 kernel: amdgpu: VI should always have 2 performance levels
Dec 02 16:04:20 470g3 lightdm[1049]: gkr-pam: couldn't unlock the login keyring.
Dec 02 16:04:20 470g3 kernel: kauditd_printk_skb: 9 callbacks suppressed
Dec 02 16:04:41 470g3 pulseaudio[1189]: stat('/etc/pulse/default.pa.d'): No such file or directory
Dec 02 16:04:46 470g3 tumblerd[1219]: Failed to load plugin "tumbler-gepub-thumbnailer.so": libgepub-0.7.so.0: cannot open shared object file: No such file or directory
Dec 02 16:04:58 470g3 pipewire[1486]: mod.rt: Can't find xdg-portal: (null)
Dec 02 16:04:58 470g3 pipewire[1486]: mod.rt: found session bus but no portal
Dec 02 16:07:15 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:07:15 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:07:47 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:07:47 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:08:19 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:08:19 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:09:26 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:09:26 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:09:58 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:09:58 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:10:35 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:10:35 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:11:07 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:11:07 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:11:39 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:11:39 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:12:11 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:12:11 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:12:43 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:12:43 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 16:48:54 470g3 wpa_supplicant[943]: wlp3s0: Failed to initiate AP scan
Dec 02 16:48:55 470g3 wpa_supplicant[943]: wlp3s0: Failed to initiate AP scan
Dec 02 16:49:25 470g3 NetworkManager[740]: <warn> [1669960165.1202] device (wlp3s0): link timed out.
Dec 02 16:49:25 470g3 NetworkManager[740]: <warn> [1669960165.1605] device (wlp3s0): Activation: failed for connection 'BLINK-16F6'
Dec 02 17:15:29 470g3 kernel: xhci_hcd 0000:00:14.0: xHC error in resume, USBSTS 0x411, Reinit
Dec 02 17:15:29 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 17:15:29 470g3 kernel: ata1.00: LPM support broken, forcing max_power
Dec 02 17:15:29 470g3 kernel: done.
Dec 02 17:15:29 470g3 kernel: amdgpu: can't get the mac of 5
Dec 02 17:15:30 470g3 kernel: Bluetooth: hci0: Failed to send firmware data (-38)
Dec 02 17:15:36 470g3 kernel: amdgpu: VI should always have 2 performance levels
Dec 02 17:15:39 470g3 kernel: Bluetooth: hci0: Reading supported features failed (-16)
Dec 02 18:20:59 470g3 kernel: amdgpu: can't get the mac of 5
Dec 02 18:46:12 470g3 gnome-keyring-daemon[1064]: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/1, but it's already registered
Dec 02 18:46:12 470g3 gnome-keyring-d[1064]: asked to register item /org/freedesktop/secrets/collection/Default_5fkeyring/1, but it's already registered
Dec 02 19:20:39 470g3 kernel: sd 3:0:0:0: [sdb] No Caching mode page found
Dec 02 19:20:39 470g3 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
Dec 02 19:22:52 470g3 tumblerd[11721]: Failed to load plugin "tumbler-gepub-thumbnailer.so": libgepub-0.7.so.0: cannot open shared object file: No such file or directory
Dec 02 19:29:56 470g3 tumblerd[11833]: Failed to load plugin "tumbler-gepub-thumbnailer.so": libgepub-0.7.so.0: cannot open shared object file: No such file or directory
Dec 02 19:30:51 470g3 kernel: sd 3:0:0:0: [sdb] No Caching mode page found
Dec 02 19:30:51 470g3 kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
Should I follow your previous advice and remove Snap and Flatpak?
Who knows; thread’s become a social-justice thing and as such auto-moderated into uselessness.
Still no followup on that very first reaction as to /etc/fstab – but I’ll then butt out.
Who’s? Mine?
I never adviced removing them, i just pointed-out the presence of it.
I have it also on my machine and i have no such delay on my desktop, so was just wondering if any snap package would be the cause for the delay…
Could you remind or point us to it, in case we missed it?
And no reason to stay out, more eyes and brains is always better like CPU cores…
(not going to reply to the rest of your comment to keep the topic clean)
AFAIK yes.
You are more than welcome. I have no idea what difference it’ll make, but If you’re sure you don’t use 'em, you’re welcome to do so.
Ok, as I have said, I do not have Snap or Flatpak enabled. Why would removing them make a difference?
@Cencar44 might be interesting to also see the output of:
journalctl --disk-usage
Just to eliminate the possibility of huge log files that needed tobe written to disk…
journalctl --disk-usage
Archived and active journals take up 120.0M in the file system.
Hmm okay that looks perfectly innocent then
WRT the logs you posted:
Looks like it has several problems, eg. the ata1.00
and Bluetooth
driver initializations.
No idea if those are related to a slow startup, or how to fix those though…
Maybe the other brains know
And also some autostart entries that seem to have some minor problems:
Thanks maybe some body else could shed some light on the problem? As I said starting the post. This slow boot is worse on my Hp but my Asus has exactly the same issue.
Every boot
/dev/sda2: clean, 463926/61030400 files, 9210624/244112696, blocks”.
HP 2 minutes 20 seconds.
Asus 1 minute 30 seconds.
One more info that could shed some light is the output of:
systemd-analyze critical-chain
systemd-analyze critical-chain
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.
graphical.target @46.632s
└─lightdm.service @41.479s +5.150s
└─systemd-user-sessions.service @41.412s +59ms
└─nss-user-lookup.target @42.026s
Oops refering to this:
We should ofcourse check relative to that unit
systemd-analyze critical-chain systemd-journal-flush.service
At least i hope that will provide the info we need
systemd-analyze critical-chain systemd-journal-flush.service
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.
systemd-journal-flush.service +22.688s
└─systemd-journald.service @11.715s +127ms
└─systemd-journald.socket @9.505s
└─system.slice @9.233s
└─-.slice @9.233s
ok i give up, as my mind seems to be officially burned-out at this moment
There is obviously a gap of ~10.973s
before that service is started, but why
Reasons for your slow boot
Swap is always needed :
I made a french tutorial on systemd-swap setup (easily translatable):
~]$ sudo inxi -mj
Memory:
RAM: total: 14.97 GiB used: 11.13 GiB (74.4%)
Array-1: capacity: 32 GiB slots: 2 EC: None
Device-1: Bottom - Slot 1 (left) type: DDR4 size: 8 GiB speed: 3200 MT/s
Device-2: Bottom - Slot 2 (right) type: DDR4 size: 8 GiB speed: 3200 MT/s
Swap:
ID-1: swap-1 type: file size: 16 GiB used: 552.8 MiB (3.4%) file: /swapfile