You are not logged in.

Pages: 1 2

#1 2023-02-17 17:17:04

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Very slow boot, unable to use sudo

Hello, i have just updated my system with sudo pacman -Syu. However when i rebooted the system it was booting very slowly. After 15 minutes i was in the login screen and after waiting 10 more minutes my usual system was back up. Terminals work, normal commands work but sudo commands, anything with sudo just freezes the terminal and all programs are very slow.

Offline

#2 2023-02-17 17:19:18

d.ALT
Member
Registered: 2019-05-10
Posts: 959

Re: Very slow boot, unable to use sudo

# systemd-analyze blame
# journalctl -b | curl -F 'file=@-' 0x0.st

<49,17,III,I>    Fama di loro il mondo esser non lassa;
<50,17,III,I>    misericordia e giustizia li sdegna:
<51,17,III,I>    non ragioniam di lor, ma guarda e passa.

Offline

#3 2023-02-17 17:23:14

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

d.ALT wrote:
# systemd-analyze blame
# journalctl -b | curl -F 'file=@-' 0x0.st

I cant connect to internet i think it is disabled
The systemd command showed 31s geoclue.service 30s systemd-hostnamed.service, systemd-localed.service,accounts-daemon.service with anything else being normal

Offline

#4 2023-02-17 17:26:24

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

It also shows no applications

Offline

#5 2023-02-17 18:19:32

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,653

Re: Very slow boot, unable to use sudo

DaysSky wrote:

It also shows no applications

Define "It"

I cant connect to internet i think it is disabled

Wired or wireless internet?

What are the versions reported by uname -a and by pacman -Q linux  (assuming you aare using stock kernel)?

What is the output of hostname   ?

Last edited by ewaller (2023-02-17 18:19:49)

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#6 2023-02-18 01:29:38

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

ewaller wrote:
DaysSky wrote:

It also shows no applications

Define "It"

I cant connect to internet i think it is disabled

Wired or wireless internet?

What are the versions reported by uname -a and by pacman -Q linux  (assuming you aare using stock kernel)?

What is the output of hostname   ?

Wired
linux 6.1.12.arch1-1
it says theres no command named hostname

Offline

#7 2023-02-18 02:01:11

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

i have managed to be root by command su, however i cannot connect to the internet and ip link freezes the terminal.

Offline

#8 2023-02-18 02:13:10

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,653

Re: Very slow boot, unable to use sudo

Do you have installation media from which you can boot?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#9 2023-02-18 02:15:20

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

ewaller wrote:

Do you have installation media from which you can boot?

No i do not, but i can make one

Last edited by DaysSky (2023-02-18 02:15:34)

Offline

#10 2023-02-18 02:25:54

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,653

Re: Very slow boot, unable to use sudo

I think we are to that point.  Let's see if we can get your network working from the install media, then we can look into fixing the install.

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#11 2023-02-18 02:30:15

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

ewaller wrote:

I think we are to that point.  Let's see if we can get your network working from the install media, then we can look into fixing the install.

I made one, what do i do now?

Offline

#12 2023-02-18 03:50:08

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

edit: now i cannot open my system and can only get in via chroot

Offline

#13 2023-02-18 04:57:30

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: Very slow boot, unable to use sudo

From the chroot, paste the journal from the failed boot, and a full pacman log.

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#14 2023-02-18 07:38:03

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

jasonwryan wrote:

From the chroot, paste the journal from the failed boot, and a full pacman log.

http://0x0.st/HssV.txt
I dont know pacman logs

Last edited by DaysSky (2023-02-18 07:45:34)

Offline

#15 2023-02-18 07:48:58

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

Found pacman logs
http://0x0.st/HssJ.txt

Offline

#16 2023-02-18 07:51:29

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: Very slow boot, unable to use sudo

You are doing partial upgrades: they break things.

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#17 2023-02-18 07:53:16

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

jasonwryan wrote:

You are doing partial upgrades: they break things.

How do i fix it?

Offline

#18 2023-02-18 07:54:20

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: Very slow boot, unable to use sudo

1. Stop doing it.

2. Fully update your system.

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#19 2023-02-18 07:54:53

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

jasonwryan wrote:

2. Fully update your system.

How?
Pacman -Syu says nothing to upgrade

Last edited by DaysSky (2023-02-18 07:58:23)

Offline

#20 2023-02-18 08:14:23

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

Re: Very slow boot, unable to use sudo

Feb 18 12:44:50 ArchLinux systemd[1]: systemd-rfkill.service: Deactivated successfully.
Feb 18 12:46:14 ArchLinux systemd[1]: sys-subsystem-net-devices-eth0.device: Job sys-subsystem-net-devices-eth0.device/start timed out.
Feb 18 12:44:45 ArchLinux kernel: r8152 2-2:1.0 enp5s0f3u2: renamed from eth0
Feb 18 12:44:45 ArchLinux systemd-networkd[449]: eth0: Interface name change detected, renamed to enp5s0f3u2.

https://wiki.archlinux.org/title/Networ … face_names

Also you have at least NM, systemd-networkd and dhcpcd enabled
Pick one, disable the others and post

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

Edit: there's also an issue w/ the wifi NIC

Feb 18 12:44:45 ArchLinux kernel: RIP: 0010:rtw89_pci_enable_intr+0x18/0x70 [rtw89pci]
Feb 18 12:44:45 ArchLinux kernel: Code: 5d 41 5c c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 0f 1f 44 00 00 55 48 89 f5 53 48 8b 87 60 02 00 00 48 89 fb <8b> 96 cc 99 06 00 be a0 01 00 00 48 8b 40 70 e8 74 c9 2a e1 8b 95
Feb 18 12:44:45 ArchLinux kernel: RSP: 0018:ffffa4a3416cfb40 EFLAGS: 00010246
Feb 18 12:44:45 ArchLinux kernel: RAX: ffffffffc555dca0 RBX: ffff8e9801802080 RCX: ffffa4a3416cfb58
Feb 18 12:44:45 ArchLinux kernel: RDX: ffffa4a3416cfb18 RSI: 0000000000000000 RDI: ffff8e9801802080
Feb 18 12:44:45 ArchLinux kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000010
Feb 18 12:44:45 ArchLinux kernel: R10: ffffffffffffffff R11: 0000000000000000 R12: ffffffffc50a00a0
Feb 18 12:44:45 ArchLinux kernel: R13: ffff8e9801c95000 R14: 00000000000000ff R15: ffff8e9805ea4040
Feb 18 12:44:45 ArchLinux kernel: FS:  00007f277bc51500(0000) GS:ffff8e9a9ff00000(0000) knlGS:0000000000000000
Feb 18 12:44:45 ArchLinux kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 18 12:44:45 ArchLinux kernel: CR2: 00000000000699cc CR3: 000000010ac70000 CR4: 0000000000750ee0
Feb 18 12:44:45 ArchLinux kernel: PKRU: 55555554
Feb 18 12:44:45 ArchLinux kernel: Call Trace:
Feb 18 12:44:45 ArchLinux kernel:  <TASK>
Feb 18 12:44:45 ArchLinux kernel:  rtw89_pci_probe+0x8ef/0x94b [rtw89pci f43541fccd59ff45188ff8e9b0372be940255774]
Feb 18 12:44:45 ArchLinux kernel:  local_pci_probe+0x45/0x80
Feb 18 12:44:45 ArchLinux kernel:  pci_device_probe+0xc1/0x250
Feb 18 12:44:45 ArchLinux kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
Feb 18 12:44:45 ArchLinux kernel:  really_probe+0xde/0x380
Feb 18 12:44:45 ArchLinux kernel:  ? pm_runtime_barrier+0x54/0x90
Feb 18 12:44:45 ArchLinux kernel:  __driver_probe_device+0x78/0x170
Feb 18 12:44:45 ArchLinux kernel:  driver_probe_device+0x1f/0x90
Feb 18 12:44:45 ArchLinux kernel:  __driver_attach+0xd2/0x1c0
Feb 18 12:44:45 ArchLinux kernel:  ? __device_attach_driver+0x110/0x110
Feb 18 12:44:45 ArchLinux kernel:  bus_for_each_dev+0x8b/0xd0
Feb 18 12:44:45 ArchLinux kernel:  bus_add_driver+0x1b2/0x200
Feb 18 12:44:45 ArchLinux kernel:  driver_register+0x8d/0xe0
Feb 18 12:44:45 ArchLinux kernel:  ? 0xffffffffc3f22000
Feb 18 12:44:45 ArchLinux kernel:  do_one_initcall+0x5d/0x220
Feb 18 12:44:45 ArchLinux kernel:  do_init_module+0x4a/0x1e0
Feb 18 12:44:45 ArchLinux kernel:  __do_sys_init_module+0x17f/0x1b0
Feb 18 12:44:45 ArchLinux kernel:  ? ksys_read+0x6f/0xf0
Feb 18 12:44:45 ArchLinux kernel:  do_syscall_64+0x5f/0x90
Feb 18 12:44:45 ArchLinux kernel:  ? __flush_smp_call_function_queue+0x11a/0x1a0
Feb 18 12:44:45 ArchLinux kernel:  ? __irq_exit_rcu+0x4b/0xe0
Feb 18 12:44:45 ArchLinux kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
Feb 18 12:44:45 ArchLinux kernel: RIP: 0033:0x7f277c0c8eee
rfkill

and in case you've a parallel windows installation, 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Edit #2: why are we using rtw89-dkms-git ?

Last edited by seth (2023-02-18 08:21:04)

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

Offline

#21 2023-02-18 08:21:49

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

seth wrote:
Feb 18 12:44:50 ArchLinux systemd[1]: systemd-rfkill.service: Deactivated successfully.
Feb 18 12:46:14 ArchLinux systemd[1]: sys-subsystem-net-devices-eth0.device: Job sys-subsystem-net-devices-eth0.device/start timed out.
Feb 18 12:44:45 ArchLinux kernel: r8152 2-2:1.0 enp5s0f3u2: renamed from eth0
Feb 18 12:44:45 ArchLinux systemd-networkd[449]: eth0: Interface name change detected, renamed to enp5s0f3u2.

https://wiki.archlinux.org/title/Networ … face_names

Also you have at least NM, systemd-networkd and dhcpcd enabled
Pick one, disable the others and post

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

Edit: there's also an issue w/ the wifi NIC

Feb 18 12:44:45 ArchLinux kernel: RIP: 0010:rtw89_pci_enable_intr+0x18/0x70 [rtw89pci]
Feb 18 12:44:45 ArchLinux kernel: Code: 5d 41 5c c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 0f 1f 44 00 00 55 48 89 f5 53 48 8b 87 60 02 00 00 48 89 fb <8b> 96 cc 99 06 00 be a0 01 00 00 48 8b 40 70 e8 74 c9 2a e1 8b 95
Feb 18 12:44:45 ArchLinux kernel: RSP: 0018:ffffa4a3416cfb40 EFLAGS: 00010246
Feb 18 12:44:45 ArchLinux kernel: RAX: ffffffffc555dca0 RBX: ffff8e9801802080 RCX: ffffa4a3416cfb58
Feb 18 12:44:45 ArchLinux kernel: RDX: ffffa4a3416cfb18 RSI: 0000000000000000 RDI: ffff8e9801802080
Feb 18 12:44:45 ArchLinux kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000010
Feb 18 12:44:45 ArchLinux kernel: R10: ffffffffffffffff R11: 0000000000000000 R12: ffffffffc50a00a0
Feb 18 12:44:45 ArchLinux kernel: R13: ffff8e9801c95000 R14: 00000000000000ff R15: ffff8e9805ea4040
Feb 18 12:44:45 ArchLinux kernel: FS:  00007f277bc51500(0000) GS:ffff8e9a9ff00000(0000) knlGS:0000000000000000
Feb 18 12:44:45 ArchLinux kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 18 12:44:45 ArchLinux kernel: CR2: 00000000000699cc CR3: 000000010ac70000 CR4: 0000000000750ee0
Feb 18 12:44:45 ArchLinux kernel: PKRU: 55555554
Feb 18 12:44:45 ArchLinux kernel: Call Trace:
Feb 18 12:44:45 ArchLinux kernel:  <TASK>
Feb 18 12:44:45 ArchLinux kernel:  rtw89_pci_probe+0x8ef/0x94b [rtw89pci f43541fccd59ff45188ff8e9b0372be940255774]
Feb 18 12:44:45 ArchLinux kernel:  local_pci_probe+0x45/0x80
Feb 18 12:44:45 ArchLinux kernel:  pci_device_probe+0xc1/0x250
Feb 18 12:44:45 ArchLinux kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
Feb 18 12:44:45 ArchLinux kernel:  really_probe+0xde/0x380
Feb 18 12:44:45 ArchLinux kernel:  ? pm_runtime_barrier+0x54/0x90
Feb 18 12:44:45 ArchLinux kernel:  __driver_probe_device+0x78/0x170
Feb 18 12:44:45 ArchLinux kernel:  driver_probe_device+0x1f/0x90
Feb 18 12:44:45 ArchLinux kernel:  __driver_attach+0xd2/0x1c0
Feb 18 12:44:45 ArchLinux kernel:  ? __device_attach_driver+0x110/0x110
Feb 18 12:44:45 ArchLinux kernel:  bus_for_each_dev+0x8b/0xd0
Feb 18 12:44:45 ArchLinux kernel:  bus_add_driver+0x1b2/0x200
Feb 18 12:44:45 ArchLinux kernel:  driver_register+0x8d/0xe0
Feb 18 12:44:45 ArchLinux kernel:  ? 0xffffffffc3f22000
Feb 18 12:44:45 ArchLinux kernel:  do_one_initcall+0x5d/0x220
Feb 18 12:44:45 ArchLinux kernel:  do_init_module+0x4a/0x1e0
Feb 18 12:44:45 ArchLinux kernel:  __do_sys_init_module+0x17f/0x1b0
Feb 18 12:44:45 ArchLinux kernel:  ? ksys_read+0x6f/0xf0
Feb 18 12:44:45 ArchLinux kernel:  do_syscall_64+0x5f/0x90
Feb 18 12:44:45 ArchLinux kernel:  ? __flush_smp_call_function_queue+0x11a/0x1a0
Feb 18 12:44:45 ArchLinux kernel:  ? __irq_exit_rcu+0x4b/0xe0
Feb 18 12:44:45 ArchLinux kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
Feb 18 12:44:45 ArchLinux kernel: RIP: 0033:0x7f277c0c8eee
rfkill

and in case you've a parallel windows installation, 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

http://0x0.st/HssG.txt
http://0x0.st/Hssd.txt

Offline

#22 2023-02-18 08:25:31

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

Re: Very slow boot, unable to use sudo

You still have dhcpcd@eth0.service and systemd-networkd enabled.

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

Offline

#23 2023-02-18 08:29:57

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

seth wrote:

Edit #2: why are we using rtw89-dkms-git ?

I installed it trying to find a wifi driver.

Offline

#24 2023-02-18 08:30:27

DaysSky
Member
Registered: 2022-12-30
Posts: 35

Re: Very slow boot, unable to use sudo

seth wrote:

You still have dhcpcd@eth0.service and systemd-networkd enabled.

I disable one of them?
http://0x0.st/Hssh.txt

Last edited by DaysSky (2023-02-18 08:31:48)

Offline

#25 2023-02-18 08:32:07

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

Re: Very slow boot, unable to use sudo

seth wrote:

Pick one, disable the others

Edit: so how's the system behaving now?

Last edited by seth (2023-02-18 08:32:39)

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

Offline

Pages: 1 2

Board footer

Powered by FluxBB