Arch Linux

Pasvuz

Member

Registered: 2023-04-21

Posts: 6

Stumped while starting up after Started Network Manager Script Dispatc

[SOLVED] -- I reinstall the whole arch xD
Using archlinux on a laptop, starting up, it as usual start all tasks and process, with the following syntax [ OK ] Started / Reached name of something.

But it several blocking on his own after "[ OK ] Started Network Manager Script Dispatcher Service".

Showing up no more input.

My laptop has two GPU (integrated and a RTX 2060) .
Using optimus-manager this morning was unable to find the second GPU and switching to this one. So I reinstalled the driver (thinking this was the problem, with packages like nvidia-open, nvidia-utils and also sudo pacman -Syyu. Upgrading the whole system.

It's taking too much time for booting up. Really too much

Last edited by Pasvuz (2023-05-03 12:27:43)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,076

Re: Stumped while starting up after Started Network Manager Script Dispatc

Do you actively use a dispatcher script? did you install/use some VPN that sets things up incorrectly? Post the full outputs of

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

https://wiki.archlinux.org/title/List_o … n_services

OT: Stop using optimus-manager and set up https://wiki.archlinux.org/title/PRIME# … er_offload

Pasvuz

Member

Registered: 2023-04-21

Posts: 6

Re: Stumped while starting up after Started Network Manager Script Dispatc

I do not use any VPN, and no, I dont use actively any script (neither know what they are)

The first command gives me:
sort: cannot-read: systemd-analyze: No such file or directory.

P.S I cant access my computer normaly, so I'm inside with  "ctrl + alt + f2", I manage to save freshly file into a usb drive. (Cause, as said, meanwhile booting up, it stucks after that error, and neither the login page is shown to me).

The second one (journalctl -b) the only coloured comand that I can see, (I wouldn' know what to prompt you from the thousands of line) is:
[Firmware Bug]: TSC ADJUST: CPU0: -1716961054 force to 0

Last edited by Pasvuz (2023-04-27 12:15:45)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,076

Re: Stumped while starting up after Started Network Manager Script Dispatc

I posted a link that shows you how you can paste the outputs you receive even from the terminal.

That said this sounds like you either have file corruption or your mount setup is wonky. What's in your /etc/fstab?

uname -a
pacman -Q linux

?

Pasvuz

Member

Registered: 2023-04-21

Posts: 6

Re: Stumped while starting up after Started Network Manager Script Dispatc

Yeah I saw the link, but I literally did not understood enough to make it work properly. Btw...

uname -a =>
Linux Arch-pasvuz 6.1.25-1-lts #1 SMP PREEMPT_DYNAMIC Thu, 20 April 2023 14:01:39 +0000 x86_64 GNU/Linux

pacman -Q linux =>
linux 6.2.12.arch1-1

Whats in my /etc/fstab =>
#dev/nvme0n1p3
UUID=84ff3ff7-950e-4b75-a5a0-53ead7156b28 / ext4 rw,relatime  0 1

# /dev/nvme0n1p1
UUID=2DA6-31B5     /boot/efi   vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii, shortname=mixed,utf8,errors=remount-ro.  0 2

# /dev/nvme0n1p2
UUID=a5fcf719-91ff-4915-9067-477812ad77b2  none  swap  defaults  0 0

I most feel like, that is better to reinstall the whole archlinux from 0. So just in case, can y confirm me that the main problem was me using optimus-manager? Because...man I would not screw my whole pc because I love to suffer, lol.

As said, I get to save whole important file, the rest can just be reinstall, and I have no saved backup, because, neither when I was on linux I got able to make a proper one.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,076

Re: Stumped while starting up after Started Network Manager Script Dispatc

Since you don't post the other outputs I can't confirm or deny anything, normally optimus-manager should not be an issue that could lead to this. fstab setup looks ok. Kernel is fine as well on LTS. Generally reinstalling is never necessary and prevents you from learning what caused - and how to avoid - the issue in the first place.

Regarding your accidental report:

Ok, when I will be more comfortable, I could print you out the whole output, I'll study with more effort the given link

It basically boils down to piping the end of the command to a pastebin e.g.

systemd-analyze critical-chain | curl -F 'file=@-' 0x0.st

Last edited by V1del (2023-04-27 13:24:29)