You are not logged in.

Pages: 1

#1 2021-10-25 17:57:36

jamess7995
Member
Registered: 2021-10-25
Posts: 41

How to make bootup faster so it's closer to 10-20 seconds

Hey all,
    I've done a recently Arch install, I'm relatively okay at linux stuff. I started on Manjaro, switched over to Fedora, and am now on Arch. I just stop watched it and found that it's something like
11 Seconds to load grub
05 Seconds to auto select grub
10 Seconds to load GUI Login
21 Seconds to load blank desktop
    This is on a m.2 nvme samsung 970 Evo, in the past, I had a windows install on this drive and it would take me 13 seconds from hitting the power button, to load a basic webpage like apple.com, that was on my laptop but at this point we've got different hardware, but I feel like I should be able to obtain something similar because I feel like at least Arch would be more slimmed down and efficient than bloody windows.
    So far I have checked out Arch's wiki on Improving performance/Boot process. I've mostly just followed where my grub has this now and that's where I'm getting the 48 seconds from:

 [james@Arch computer_backup]$ cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT
GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=2 rd.systemd.show_status=auto rd.udev.log_level=2"

    I have run systemd-analyze, I'm not sure what else is worth trying and I wouldn't really want to dive down a 5 hour rabbit hole to shave 5 seconds off. Here's the systemd output that could help, I'll gladly provide any other detail that could help.

[james@Arch computer_backup]$ sudo systemd-analyze
[sudo] password for james: 
Startup finished in 8.833s (firmware) + 5.499s (loader) + 1.477s (kernel) + 1.458s (userspace) = 17.269s 
graphical.target reached after 1.322s in userspace
[james@Arch computer_backup]$ sudo systemd-analyze blame
1.131s systemd-random-seed.service
 855ms dev-loop4.device
 853ms dev-loop1.device
 850ms dev-loop0.device
 847ms dev-loop3.device
 841ms dev-loop5.device
 838ms dev-loop2.device
 577ms dev-nvme0n1p3.device
 499ms user@1000.service
 375ms udisks2.service
 303ms carthage.service
 276ms systemd-rfkill.service
 184ms ldconfig.service
 115ms systemd-fsck@dev-disk-by\x2duuid-564b0d47\x2dfbf8\x2d4bf0\x2da17d\x2d753192a33aaf.service
 101ms boot.mount
  83ms systemd-tmpfiles-clean.service
  79ms upower.service
  77ms ufw.service
  53ms systemd-udev-trigger.service
  50ms systemd-journal-flush.service
  45ms lvm2-monitor.service
  40ms systemd-udevd.service
  39ms polkit.service
  39ms systemd-fsck@dev-disk-by\x2duuid-9C3C\x2dF041.service
  38ms systemd-tmpfiles-setup.service
  38ms systemd-logind.service
  35ms systemd-journald.service
  31ms NetworkManager.service
  28ms user-runtime-dir@1000.service
  28ms home-mounts-Nextcloud.mount
  23ms var-lib-snapd-snap-apple\x2dmusic\x2dfor\x2dlinux-38.mount
  23ms var-lib-snapd-snap-bare-5.mount
  23ms var-lib-snapd-snap-core18-2128.mount
  22ms var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-161.mount
  21ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1519.mount
  20ms var-lib-snapd-snap-snapd-13640.mount
  16ms systemd-journal-catalog-update.service
  14ms systemd-sysusers.service
  13ms systemd-tmpfiles-setup-dev.service
   8ms bluetooth.service
   8ms dev-hugepages.mount
   8ms dev-mqueue.mount
   8ms alsa-restore.service
   8ms sys-kernel-debug.mount
   7ms sys-kernel-tracing.mount
   7ms wpa_supplicant.service
   7ms kmod-static-nodes.service
   6ms modprobe@fuse.service
   6ms modprobe@configfs.service
   5ms dev-disk-by\x2duuid-7ce592f4\x2dcd3f\x2d4010\x2d9937\x2de5ba2f9ded47.swap
   5ms systemd-modules-load.service
   5ms systemd-update-utmp.service
   4ms systemd-remount-fs.service
   4ms systemd-sysctl.service
   3ms rtkit-daemon.service
   3ms sys-fs-fuse-connections.mount
   3ms systemd-user-sessions.service
   3ms systemd-update-done.service
   1ms tmp.mount
   1ms sys-kernel-config.mount
   1ms modprobe@drm.service
 302us snapd.socket
[james@Arch computer_backup]$ sudo 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 @1.322s
└─multi-user.target @1.322s
  └─systemd-logind.service @1.101s +38ms
    └─basic.target @1.096s
      └─sockets.target @1.096s
        └─snapd.socket @1.095s +302us
          └─sysinit.target @1.094s
            └─systemd-update-done.service @1.091s +3ms
              └─ldconfig.service @905ms +184ms
                └─local-fs.target @905ms
                  └─home-mounts-Nextcloud.mount @877ms +28ms
                    └─systemd-fsck@dev-disk-by\x2duuid-564b0d47\x2dfbf8\x2d4bf0\x2da17d\x2d753192a33aaf.service @760ms +115ms
                      └─dev-disk-by\x2duuid-564b0d47\x2dfbf8\x2d4bf0\x2da17d\x2d753192a33aaf.device @756ms

Offline

#2 2021-10-25 18:31:38

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,497
Website

Re: How to make bootup faster so it's closer to 10-20 seconds

Those times are long enough to suggest you don't just need to tweak things for speed but that something might be really wrong.  But the long firmware time is out of scope for these forums - perhaps others could help with that, but it'd not be an arch linux issue and it would depend on what make / model of system this was (so please describe that).

The grub time also seems unreasonably long, and that is in scope here - but I've never used grub 2.0 for the very reason that it has always been overly complex and bloated: it *should* be able to run very smoothly and quickly, but I can't say I'm surprised when it doesn't.  There are knowledgeable grub users here who can probably help, but my first suggestion would be to use a simpler boot loader / manager.

Your kernel and monitored-user-space times are great - so there's no need to do anything there.  But then from what you report of stop-watch-time your WM/DE is very slow starting up.  That can definitely be greatly improved, but to get started there you'll need to describe what you are running.  What WM or DE are you using?  How has it been configured?  How do you start it (startx, DM, etc)?

EDIT: I don't see a networking service in the critical chain output.  How is your network configured?  The fact that it's not there is good: the graphical and mutliuser targets really shouldn't depend on networking being up.  But if you are timing until you can actually open a webpage, then obviously full networking initialization is a prerequisite.

Overall, the strategies in the wiki page you linked to are not really relevant for your case.  That all addresses the userspace time which is not at all the problem on your system.

Last edited by Trilby (2021-10-25 18:52:40)

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#3 2021-10-25 19:02:02

progandy
Member
Registered: 2012-05-17
Posts: 5,321

Re: How to make bootup faster so it's closer to 10-20 seconds

I do not use grub, but the default grub timeout is 5 seconds. you can change that so it immediately boots unless Escape is held during that transition. (Edit: I think a 0 timeout and the countdown timeout style should do that)

Last edited by progandy (2021-10-25 19:28:47)

| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |

Offline

#4 2021-10-25 19:22:41

jamess7995
Member
Registered: 2021-10-25
Posts: 41

Re: How to make bootup faster so it's closer to 10-20 seconds

Thanks for the quick reply. So couple things to address.

Trilby wrote:

make / model of system this was (so please describe that).

I've got the below:

  • Mobo: ASUS ROG STRIX Z490-E GAMING

  • RAM: Trident Z RGB 4x8GB Type: DDR4 Speed: 3200 MT/s Manufacturer: G-Skill

  • CPU: Intel(R) Core(TM) i3-10100 CPU @ 3.60GHz w/ Integrated Graphics

  • Data Hard Drive(Where my home and other data is: Model Family: Seagate FireCuda 2.5 Device Model: ST2000LX001-1RG174 User Capacity:  [2.00 TB]

  • OS Drive: Model Number: Samsung SSD 970 EVO 500GB

Trilby wrote:

What WM or DE are you using?  How has it been configured?  How do you start it (startx, DM, etc)?

I'm not sure sure how to answer all the questions, are there specific conf files I can cat out for you or others. I know I'm using KDE, with xorg and startx, I'm pretty sure I just have it start using system enable startx and systemctl enable sddm.

Trilby wrote:

What WM or DE are you using?  How has it been configured?  How do you start it (startx, DM, etc)?

I believe I'm just using NetworkManager.service with Wi-Fi.

Offline

#5 2021-10-25 21:16:06

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,242

Re: How to make bootup faster so it's closer to 10-20 seconds

system enable startx

That's not a thing and a stark contrast to the idea of also using SDDM.

I believe

?
You're using the one you installed and configured.

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
sudo journalctl -b

The boot itself according to systemd-analyze is actually decently fast.
The crng sems a bit late, https://wiki.debian.org/BoottimeEntropyStarvation & https://wiki.archlinux.org/title/Haveged - but the graphical target is there in 1.322s
You're spending too much time in the UEFI and the bootloader (likely timeouts to allow you selecting a boot device/entering the BIOS and then to select a kernel in grub) and "10 Seconds to load GUI Login" must be in the greeter itself.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#6 2021-10-25 22:21:49

jamess7995
Member
Registered: 2021-10-25
Posts: 41

Re: How to make bootup faster so it's closer to 10-20 seconds

seth wrote:

That's not a thing and a stark contrast to the idea of also using SDDM.

I'm sorry, I'm not super sure what I did without going through the wiki over the course of half an hour but all I'm somewhat sure in is startx, I'm gonna go through the wiki again sometime tonight to familiarize myself with what I did. 


[james@Arch computer_backup]$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
bluetooth.service                        | bluetooth.target.wants
carthage.service                         | multi-user.target.wants
cronie.service                           | multi-user.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
NetworkManager.service                   | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-media-session.service           | pipewire.service.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
snapd.socket                             | sockets.target.wants
ufw.service                              | multi-user.target.wants
upower.service                           | graphical.target.wants
var-lib-snapd-snap-apple\x2dmusic\x2dfor\x2dlinux-38.mount | multi-user.target.wants
var-lib-snapd-snap-bare-5.mount          | multi-user.target.wants
var-lib-snapd-snap-core18-2128.mount     | multi-user.target.wants
var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-161.mount | multi-user.target.wants
var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1519.mount | multi-user.target.wants
var-lib-snapd-snap-snapd-13640.mount     | multi-user.target.wants
xdg-user-dirs-update.service             | default.target.wants

[james@Arch computer_backup]$ sudo journalctl -b
[sudo] password for james: 
-- Journal begins at Wed 2021-10-20 22:05:12 EDT, ends at Mon 2021-10-25 18:21:22 EDT. --
Oct 25 13:39:00 Arch kernel: Linux version 5.14.14-arch1-1 (linux@archlinux) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Wed, 20 Oct 2021 21:35:18 +0000
Oct 25 13:39:00 Arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=bd46640d-57cf-4f9d-8eda-f804ea9163d0 rw quiet loglevel=2 rd.systemd.show_status=auto rd.udev.log_level=2
Oct 25 13:39:00 Arch kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Oct 25 13:39:00 Arch kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Oct 25 13:39:00 Arch kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Oct 25 13:39:00 Arch kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Oct 25 13:39:00 Arch kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Oct 25 13:39:00 Arch kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Oct 25 13:39:00 Arch kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Oct 25 13:39:00 Arch kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Oct 25 13:39:00 Arch kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Oct 25 13:39:00 Arch kernel: signal: max sigframe size: 2032
Oct 25 13:39:00 Arch kernel: BIOS-provided physical RAM map:
Oct 25 13:39:00 Arch kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] reserved
Oct 25 13:39:00 Arch kernel: BIOS-e820: [mem 0x0000000000001000-0x000000000008ffff] usable
Oct 25 13:39:00 Arch kernel: BIOS-e820: [mem 0x0000000000090000-0x0000000000090fff] type 20
Oct 25 13:39:00 Arch kernel: BIOS-e820: [mem 0x0000000000091000-0x000000000009dfff] usable
Oct 25 13:39:00 Arch kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Oct 25 13:39:00 Arch kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Oct 25 13:39:00 Arch kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Oct 25 13:39:00 Arch kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable

Offline

#7 2021-10-26 06:39:16

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,242

Re: How to make bootup faster so it's closer to 10-20 seconds

I'm somewhat sure in is startx

10 Seconds to load GUI Login

No.

You only posted the head of the journal. Don't copy out of the pager.
Run

sudo journalctl -b | curl -F 'f:1=<-' ix.io

and post the returned URL.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#8 2021-10-26 12:41:02

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,279

Re: How to make bootup faster so it's closer to 10-20 seconds

 855ms dev-loop4.device
 853ms dev-loop1.device
 850ms dev-loop0.device
 847ms dev-loop3.device
 841ms dev-loop5.device
 838ms dev-loop2.device

What do those loop devices correspond with ?

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#9 2021-10-26 15:08:39

jamess7995
Member
Registered: 2021-10-25
Posts: 41

Re: How to make bootup faster so it's closer to 10-20 seconds

seth wrote:

sudo journalctl -b | curl -F 'f:1=<-' ix.io

So I ran that command, I got no output, I'll paste a tail of the last 200 lines, and a pastebin of the last 3000 lines is here

Oct 26 10:50:55 Arch audit[39206]: CRED_DISP pid=39206 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:50:55 Arch kernel: audit: type=1106 audit(1635259855.455:662): pid=39206 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:50:55 Arch kernel: audit: type=1104 audit(1635259855.455:663): pid=39206 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:02 Arch dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.425' (uid=0 pid=39209 comm="sudo journalctl -b ")
Oct 26 10:51:02 Arch dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:51:02 Arch sudo[39209]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:51:02 Arch kernel: audit: type=1101 audit(1635259862.182:664): pid=39209 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:02 Arch audit[39209]: USER_ACCT pid=39209 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:02 Arch sudo[39209]:    james : TTY=pts/1 ; PWD=/home/mounts/Nextcloud/computer_backup ; USER=root ; COMMAND=/usr/bin/journalctl -b
Oct 26 10:51:02 Arch audit[39209]: CRED_REFR pid=39209 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:02 Arch sudo[39209]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Oct 26 10:51:02 Arch audit[39209]: USER_START pid=39209 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:02 Arch kernel: audit: type=1110 audit(1635259862.185:665): pid=39209 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:02 Arch kernel: audit: type=1105 audit(1635259862.185:666): pid=39209 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:02 Arch sudo[39209]: pam_unix(sudo:session): session closed for user root
Oct 26 10:51:02 Arch audit[39209]: USER_END pid=39209 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:02 Arch audit[39209]: CRED_DISP pid=39209 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:02 Arch kernel: audit: type=1106 audit(1635259862.262:667): pid=39209 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:02 Arch kernel: audit: type=1104 audit(1635259862.262:668): pid=39209 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:06 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=27833 DF PROTO=2 
Oct 26 10:51:26 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=47217 DF PROTO=2 
Oct 26 10:51:34 Arch dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.426' (uid=0 pid=39219 comm="sudo journalctl -b ")
Oct 26 10:51:34 Arch dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:51:34 Arch sudo[39219]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:51:34 Arch audit[39219]: USER_ACCT pid=39219 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:34 Arch kernel: audit: type=1101 audit(1635259894.755:669): pid=39219 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:34 Arch sudo[39219]:    james : TTY=pts/1 ; PWD=/home/mounts/Nextcloud/computer_backup ; USER=root ; COMMAND=/usr/bin/journalctl -b
Oct 26 10:51:34 Arch audit[39219]: CRED_REFR pid=39219 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:34 Arch audit[39219]: USER_START pid=39219 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:34 Arch sudo[39219]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Oct 26 10:51:34 Arch kernel: audit: type=1110 audit(1635259894.759:670): pid=39219 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:34 Arch kernel: audit: type=1105 audit(1635259894.759:671): pid=39219 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:34 Arch sudo[39219]: pam_unix(sudo:session): session closed for user root
Oct 26 10:51:34 Arch audit[39219]: USER_END pid=39219 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:34 Arch audit[39219]: CRED_DISP pid=39219 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:34 Arch kernel: audit: type=1106 audit(1635259894.835:672): pid=39219 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:34 Arch kernel: audit: type=1104 audit(1635259894.835:673): pid=39219 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:39 Arch dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.427' (uid=0 pid=39225 comm="sudo pacman -S xclip ")
Oct 26 10:51:39 Arch dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:51:39 Arch sudo[39225]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:51:39 Arch audit[39225]: USER_ACCT pid=39225 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:39 Arch sudo[39225]:    james : TTY=pts/1 ; PWD=/home/mounts/Nextcloud/computer_backup ; USER=root ; COMMAND=/usr/bin/pacman -S xclip
Oct 26 10:51:39 Arch audit[39225]: CRED_REFR pid=39225 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:39 Arch sudo[39225]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Oct 26 10:51:39 Arch audit[39225]: USER_START pid=39225 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:39 Arch kernel: audit: type=1101 audit(1635259899.922:674): pid=39225 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:39 Arch kernel: audit: type=1110 audit(1635259899.922:675): pid=39225 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:39 Arch kernel: audit: type=1105 audit(1635259899.922:676): pid=39225 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:44 Arch sudo[39225]: pam_unix(sudo:session): session closed for user root
Oct 26 10:51:44 Arch audit[39225]: USER_END pid=39225 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:44 Arch audit[39225]: CRED_DISP pid=39225 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:44 Arch kernel: audit: type=1106 audit(1635259904.655:677): pid=39225 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:44 Arch kernel: audit: type=1104 audit(1635259904.655:678): pid=39225 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:46 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=54781 DF PROTO=2 
Oct 26 10:51:50 Arch dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.428' (uid=0 pid=39255 comm="sudo journalctl -b ")
Oct 26 10:51:50 Arch kernel: audit: type=1101 audit(1635259910.235:679): pid=39255 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:50 Arch kernel: audit: type=1110 audit(1635259910.235:680): pid=39255 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:50 Arch kernel: audit: type=1105 audit(1635259910.239:681): pid=39255 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:50 Arch audit[39255]: USER_ACCT pid=39255 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:50 Arch audit[39255]: CRED_REFR pid=39255 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:50 Arch audit[39255]: USER_START pid=39255 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:50 Arch dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:51:50 Arch sudo[39255]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:51:50 Arch sudo[39255]:    james : TTY=pts/1 ; PWD=/home/mounts/Nextcloud/computer_backup ; USER=root ; COMMAND=/usr/bin/journalctl -b
Oct 26 10:51:50 Arch sudo[39255]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Oct 26 10:51:50 Arch kwin_x11[885]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 37990, resource id: 144703489, major code: 18 (ChangeProperty), minor code: 0
Oct 26 10:51:50 Arch sudo[39255]: pam_unix(sudo:session): session closed for user root
Oct 26 10:51:50 Arch audit[39255]: USER_END pid=39255 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:50 Arch audit[39255]: CRED_DISP pid=39255 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:50 Arch kernel: audit: type=1106 audit(1635259910.322:682): pid=39255 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:51:50 Arch kernel: audit: type=1104 audit(1635259910.322:683): pid=39255 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:52:06 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=3902 DF PROTO=2 
Oct 26 10:52:12 Arch dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.429' (uid=0 pid=39264 comm="sudo journalctl -b ")
Oct 26 10:52:12 Arch dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:52:12 Arch audit[39264]: USER_ACCT pid=39264 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:52:12 Arch sudo[39264]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:52:12 Arch sudo[39264]:    james : TTY=pts/1 ; PWD=/home/mounts/Nextcloud/computer_backup ; USER=root ; COMMAND=/usr/bin/journalctl -b
Oct 26 10:52:12 Arch audit[39264]: CRED_REFR pid=39264 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:52:12 Arch sudo[39264]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Oct 26 10:52:12 Arch audit[39264]: USER_START pid=39264 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:52:12 Arch kernel: audit: type=1101 audit(1635259932.222:684): pid=39264 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:52:12 Arch kernel: audit: type=1110 audit(1635259932.222:685): pid=39264 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:52:12 Arch kernel: audit: type=1105 audit(1635259932.222:686): pid=39264 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:52:12 Arch sudo[39264]: pam_unix(sudo:session): session closed for user root
Oct 26 10:52:12 Arch audit[39264]: USER_END pid=39264 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:52:12 Arch audit[39264]: CRED_DISP pid=39264 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:52:12 Arch kernel: audit: type=1106 audit(1635259932.302:687): pid=39264 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:52:12 Arch kernel: audit: type=1104 audit(1635259932.302:688): pid=39264 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:52:26 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=17986 DF PROTO=2 
Oct 26 10:52:44 Arch NetworkManager[493]: <info>  [1635259964.1488] device (wlp7s0): set-hw-addr: set MAC address to DA:50:B2:04:12:6A (scanning)
Oct 26 10:52:44 Arch NetworkManager[493]: <info>  [1635259964.3411] device (wlp7s0): supplicant interface state: inactive -> interface_disabled
Oct 26 10:52:44 Arch NetworkManager[493]: <info>  [1635259964.3412] device (p2p-dev-wlp7s0): supplicant management interface state: inactive -> interface_disabled
Oct 26 10:52:44 Arch NetworkManager[493]: <info>  [1635259964.3771] device (wlp7s0): supplicant interface state: interface_disabled -> inactive
Oct 26 10:52:44 Arch NetworkManager[493]: <info>  [1635259964.3772] device (p2p-dev-wlp7s0): supplicant management interface state: interface_disabled -> inactive
Oct 26 10:52:46 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=31971 DF PROTO=2 
Oct 26 10:52:47 Arch wpa_supplicant[624]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Oct 26 10:53:06 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=37316 DF PROTO=2 
Oct 26 10:53:26 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=56638 DF PROTO=2 
Oct 26 10:53:31 Arch dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.430' (uid=0 pid=39298 comm="sudo journalctl -b ")
Oct 26 10:53:31 Arch dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:53:31 Arch sudo[39298]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:53:31 Arch audit[39298]: USER_ACCT pid=39298 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:53:31 Arch sudo[39298]:    james : TTY=pts/1 ; PWD=/home/mounts/Nextcloud/computer_backup ; USER=root ; COMMAND=/usr/bin/journalctl -b
Oct 26 10:53:31 Arch audit[39298]: CRED_REFR pid=39298 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:53:31 Arch sudo[39298]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Oct 26 10:53:31 Arch audit[39298]: USER_START pid=39298 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:53:31 Arch kernel: audit: type=1101 audit(1635260011.529:689): pid=39298 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:53:31 Arch kernel: audit: type=1110 audit(1635260011.529:690): pid=39298 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:53:31 Arch kernel: audit: type=1105 audit(1635260011.529:691): pid=39298 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:53:31 Arch sudo[39298]: pam_unix(sudo:session): session closed for user root
Oct 26 10:53:31 Arch audit[39298]: USER_END pid=39298 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:53:31 Arch audit[39298]: CRED_DISP pid=39298 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:53:31 Arch kernel: audit: type=1106 audit(1635260011.609:692): pid=39298 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:53:31 Arch kernel: audit: type=1104 audit(1635260011.609:693): pid=39298 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:53:46 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=60625 DF PROTO=2 
Oct 26 10:54:06 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=3586 DF PROTO=2 
Oct 26 10:54:26 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=15258 DF PROTO=2 
Oct 26 10:54:46 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=24531 DF PROTO=2 
Oct 26 10:54:46 Arch dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.431' (uid=0 pid=39318 comm="sudo journalctl -b ")
Oct 26 10:54:46 Arch dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:54:46 Arch audit[39318]: USER_ACCT pid=39318 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:46 Arch sudo[39318]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:54:46 Arch sudo[39318]:    james : TTY=pts/1 ; PWD=/home/mounts/Nextcloud/computer_backup ; USER=root ; COMMAND=/usr/bin/journalctl -b
Oct 26 10:54:46 Arch audit[39318]: CRED_REFR pid=39318 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:46 Arch sudo[39318]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Oct 26 10:54:46 Arch audit[39318]: USER_START pid=39318 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:46 Arch kernel: audit: type=1101 audit(1635260086.382:694): pid=39318 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:46 Arch kernel: audit: type=1110 audit(1635260086.382:695): pid=39318 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:46 Arch kernel: audit: type=1105 audit(1635260086.382:696): pid=39318 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:46 Arch sudo[39318]: pam_unix(sudo:session): session closed for user root
Oct 26 10:54:46 Arch audit[39318]: USER_END pid=39318 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:46 Arch audit[39318]: CRED_DISP pid=39318 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:46 Arch kernel: audit: type=1106 audit(1635260086.465:697): pid=39318 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:46 Arch kernel: audit: type=1104 audit(1635260086.465:698): pid=39318 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:57 Arch dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.432' (uid=0 pid=39321 comm="sudo journalctl -b ")
Oct 26 10:54:57 Arch dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:54:57 Arch sudo[39321]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:54:57 Arch audit[39321]: USER_ACCT pid=39321 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:57 Arch sudo[39321]:    james : TTY=pts/1 ; PWD=/home/mounts/Nextcloud/computer_backup ; USER=root ; COMMAND=/usr/bin/journalctl -b
Oct 26 10:54:57 Arch audit[39321]: CRED_REFR pid=39321 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:57 Arch sudo[39321]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Oct 26 10:54:57 Arch audit[39321]: USER_START pid=39321 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:57 Arch kernel: audit: type=1101 audit(1635260097.539:699): pid=39321 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:57 Arch kernel: audit: type=1110 audit(1635260097.539:700): pid=39321 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:57 Arch kernel: audit: type=1105 audit(1635260097.539:701): pid=39321 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:57 Arch sudo[39321]: pam_unix(sudo:session): session closed for user root
Oct 26 10:54:57 Arch audit[39321]: USER_END pid=39321 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:57 Arch audit[39321]: CRED_DISP pid=39321 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:57 Arch kernel: audit: type=1106 audit(1635260097.622:702): pid=39321 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:54:57 Arch kernel: audit: type=1104 audit(1635260097.622:703): pid=39321 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:01 Arch dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.433' (uid=0 pid=39328 comm="sudo journalctl -b ")
Oct 26 10:55:01 Arch dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:55:01 Arch sudo[39328]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:55:01 Arch audit[39328]: USER_ACCT pid=39328 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:01 Arch sudo[39328]:    james : TTY=pts/1 ; PWD=/home/mounts/Nextcloud/computer_backup ; USER=root ; COMMAND=/usr/bin/journalctl -b
Oct 26 10:55:01 Arch audit[39328]: CRED_REFR pid=39328 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:01 Arch sudo[39328]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Oct 26 10:55:01 Arch audit[39328]: USER_START pid=39328 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:01 Arch kernel: audit: type=1101 audit(1635260101.559:704): pid=39328 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:01 Arch kernel: audit: type=1110 audit(1635260101.559:705): pid=39328 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:01 Arch kernel: audit: type=1105 audit(1635260101.559:706): pid=39328 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:01 Arch sudo[39328]: pam_unix(sudo:session): session closed for user root
Oct 26 10:55:01 Arch audit[39328]: USER_END pid=39328 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:01 Arch audit[39328]: CRED_DISP pid=39328 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:01 Arch kernel: audit: type=1106 audit(1635260101.642:707): pid=39328 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:01 Arch kernel: audit: type=1104 audit(1635260101.642:708): pid=39328 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:06 Arch dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.434' (uid=0 pid=39334 comm="sudo journalctl -b ")
Oct 26 10:55:06 Arch dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:55:06 Arch sudo[39334]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:55:06 Arch audit[39334]: USER_ACCT pid=39334 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:06 Arch sudo[39334]:    james : TTY=pts/1 ; PWD=/home/mounts/Nextcloud/computer_backup ; USER=root ; COMMAND=/usr/bin/journalctl -b
Oct 26 10:55:06 Arch audit[39334]: CRED_REFR pid=39334 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:06 Arch sudo[39334]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Oct 26 10:55:06 Arch audit[39334]: USER_START pid=39334 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:06 Arch kernel: audit: type=1101 audit(1635260106.022:709): pid=39334 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:06 Arch kernel: audit: type=1110 audit(1635260106.022:710): pid=39334 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:06 Arch kernel: audit: type=1105 audit(1635260106.022:711): pid=39334 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:06 Arch sudo[39334]: pam_unix(sudo:session): session closed for user root
Oct 26 10:55:06 Arch audit[39334]: USER_END pid=39334 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:06 Arch audit[39334]: CRED_DISP pid=39334 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:06 Arch kernel: audit: type=1106 audit(1635260106.109:712): pid=39334 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:06 Arch kernel: audit: type=1104 audit(1635260106.109:713): pid=39334 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:55:06 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=30506 DF PROTO=2 
Oct 26 10:55:09 Arch kwin_x11[885]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 12116, resource id: 37749949, major code: 20 (GetProperty), minor code: 0
Oct 26 10:55:09 Arch kwin_x11[885]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 12117, resource id: 37749949, major code: 15 (QueryTree), minor code: 0
Oct 26 10:55:26 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=33655 DF PROTO=2 
Oct 26 10:55:46 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=35442 DF PROTO=2 
Oct 26 10:56:06 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=42863 DF PROTO=2 
Oct 26 10:56:26 Arch kernel: [UFW BLOCK] IN=wlo1 OUT= MAC=01:00:5e:00:00:01:d4:5d:64:a0:b9:f0:08:00 SRC=192.168.50.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=54468 DF PROTO=2 
Oct 26 10:56:34 Arch dbus-daemon[490]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.435' (uid=0 pid=39366 comm="sudo journalctl -b ")
Oct 26 10:56:34 Arch dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:56:34 Arch sudo[39366]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 26 10:56:34 Arch kernel: audit: type=1101 audit(1635260194.835:714): pid=39366 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:56:34 Arch kernel: audit: type=1110 audit(1635260194.835:715): pid=39366 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:56:34 Arch kernel: audit: type=1105 audit(1635260194.835:716): pid=39366 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:56:34 Arch audit[39366]: USER_ACCT pid=39366 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="james" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:56:34 Arch audit[39366]: CRED_REFR pid=39366 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:56:34 Arch audit[39366]: USER_START pid=39366 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Oct 26 10:56:34 Arch sudo[39366]:    james : TTY=pts/1 ; PWD=/home/mounts/Nextcloud/computer_backup ; USER=root ; COMMAND=/usr/bin/journalctl -b
Oct 26 10:56:34 Arch sudo[39366]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Lone_Wolf wrote:

What do those loop devices correspond with ?

    So I made a reddit post and that was discussed there, it sounds like it's related to snap that I could probably get away with removing. I also got form that reddit post that it's probably better for me to switch to EFIStub, I'm open to others, I thought the standard end all be all was grub because I couldn't figure why not to use it.

Offline

#10 2021-10-26 15:11:23

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,242

Re: How to make bootup faster so it's closer to 10-20 seconds

Since we're concerned about the boot, the head of the journal is more interesting than its tail… (first 3000 lines should™ suffice)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#11 2021-10-26 15:23:32

icar
Member
Registered: 2020-07-31
Posts: 562

Re: How to make bootup faster so it's closer to 10-20 seconds

Lone_Wolf wrote:
 855ms dev-loop4.device
 853ms dev-loop1.device
 850ms dev-loop0.device
 847ms dev-loop3.device
 841ms dev-loop5.device
 838ms dev-loop2.device

What do those loop devices correspond with ?

Welcome to Snaps, the worst thing that recently happened to the Linux world.

Offline

#12 2021-10-26 15:29:20

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,300

Re: How to make bootup faster so it's closer to 10-20 seconds

Do you let GRUB just timeout? You can also configure GRUB to immediately boot an entry/only show a menu if you keep Shift pressed or so: https://wiki.archlinux.org/title/GRUB/T … _held_down

Offline

#13 2021-10-26 17:08:54

jamess7995
Member
Registered: 2021-10-25
Posts: 41

Re: How to make bootup faster so it's closer to 10-20 seconds

Currently on mobile and I made a Reddit post on r/Arch Linux. Here’s a link to that post if it’s helpful. Here’s a comment I just had to leave there so now I can’t boot basically. 

Ankelbiter12 from reddit(op) wrote:

I wanted to make labels for partitions and that process erased grub so I moved on to doing efi stub. I followed the wiki and found that I could do root=LABEL=/labelname and resume=LABEL=swapPartionLabel, overall my command is

efibootmgr —-disk /dev/nvme0n1 —-part 1 —-create —-label “Arch” —-loader /vmlinuz-linux —-unicode ‘root=LABEL=Arch_Swap rw initrd=\intramfs-linux.img’ —-verbose


So I’m on mobile and that was a lot to type out but after that, I can see that currently I’m in boot 04 which lists a grub path. I see the usb live media. I see the new arch efistub one, as 0000, I set that as first with the boot order command, with the grub option second, and the usb third. I exit and reboot, and get put at my bios screen; the only boot option in the Asus rog strix 490 screen is the usb… I did try it twice.

Offline

#14 2021-10-26 17:22:38

jamess7995
Member
Registered: 2021-10-25
Posts: 41

Re: How to make bootup faster so it's closer to 10-20 seconds

UPDATE: I went into a chroot environment again, and before doing the boot loader steps I just did above, I ran pacman-S base base-devel linux linux-firmware in case the bootliader wasn’t running because maybe the didn’t get the kernel or something. That did change things. Now the arch install shows in my bios firmware. But when I click on arch, it goes to a black screen for half a second that puts me right back to the firmware. I have made sure everything is mounted in the chroot environment.

Offline

#15 2021-10-26 17:34:33

jamess7995
Member
Registered: 2021-10-25
Posts: 41

Re: How to make bootup faster so it's closer to 10-20 seconds

seth wrote:

Since we're concerned about the boot, the head of the journal is more interesting than its tail… (first 3000 lines should™ suffice)

EDIT TO THE UPDATE: I just tried to chroot, Pac-Man Linux, efistub create, Pac-Man install Linux, now I’m booting to a black screen with 3 lines, something about failed to find initrd, I can’t back to that screen though

Offline

Pages: 1

Board footer

Powered by FluxBB