No I have run it with # .. same thing, but dbus is running, it is not like it isn't.
If dbus wasn't running should I or should I not have had network on console. The problem was at the start of stage 2, not on desktop.
Here is some sv status now, when the problem is not there anymore, but what fixed it I am still trying to find out
# sv status /etc/runit/runsvdir/default/*
run: /etc/runit/runsvdir/default/acpid: (pid 602) 15668s
run: /etc/runit/runsvdir/default/agetty-tty1: (pid 595) 15669s
run: /etc/runit/runsvdir/default/agetty-tty2: (pid 581) 15669s
run: /etc/runit/runsvdir/default/agetty-tty3: (pid 584) 15669s
run: /etc/runit/runsvdir/default/agetty-tty4: (pid 582) 15669s
run: /etc/runit/runsvdir/default/agetty-tty5: (pid 585) 15669s
run: /etc/runit/runsvdir/default/agetty-tty6: (pid 583) 15669s
run: /etc/runit/runsvdir/default/alsa: (pid 658) 15666s
down: /etc/runit/runsvdir/default/avahi-daemon: 0s, normally up, want up
run: /etc/runit/runsvdir/default/cronie: (pid 605) 15668s
fail: /etc/runit/runsvdir/default/dbus: unable to change to service directory: file does not exist
down: /etc/runit/runsvdir/default/dhclient: 1s, normally up, want up
fail: /etc/runit/runsvdir/default/dhcp: unable to change to service directory: file does not exist
run: /etc/runit/runsvdir/default/dhcpcd: (pid 603) 15668s
fail: /etc/runit/runsvdir/default/dhcpd: unable to change to service directory: file does not exist
down: /etc/runit/runsvdir/default/dhcpd4: 1s, normally up, want up
down: /etc/runit/runsvdir/default/dhcpd6: 1s, normally up, want up
run: /etc/runit/runsvdir/default/dmeventd: (pid 32448) 1268s
down: /etc/runit/runsvdir/default/elogind: 0s, normally up, want up
run: /etc/runit/runsvdir/default/haveged: (pid 645) 15667s
down: /etc/runit/runsvdir/default/ip6tables: 1s, normally up, want up
down: /etc/runit/runsvdir/default/iptables: 1s, normally up, want up
down: /etc/runit/runsvdir/default/lm_sensors: 1s, normally up, want up
fail: /etc/runit/runsvdir/default/lvm: unable to change to service directory: file does not exist
fail: /etc/runit/runsvdir/default/lvm2: unable to change to service directory: file does not exist
run: /etc/runit/runsvdir/default/lvmetad: (pid 654) 15666s
run: /etc/runit/runsvdir/default/mdadm: (pid 642) 15667s
run: /etc/runit/runsvdir/default/nfs-server: (pid 609) 15668s
down: /etc/runit/runsvdir/default/ntpd: 1s, normally up, want up
run: /etc/runit/runsvdir/default/rpcbind: (pid 601) 15668s
run: /etc/runit/runsvdir/default/rsyncd: (pid 631) 15667s
down: /etc/runit/runsvdir/default/sddm: 1s, normally up, want up
run: /etc/runit/runsvdir/default/sshd: (pid 596) 15669s
run: /etc/runit/runsvdir/default/statd: (pid 666) 15666s
If you really symlinked all directories in /etc/runit/sv to /run/runit/service, then you didn't install dbus-runit and NetworkManager-runit, plain and simple.
If you have both dbus and NetworkManager service running (and by running I meant properly in a runsv process) you should have something like this in your pstree -a output.
runit,1
|-compton,1254
|-dbus-daemon,1274 --syslog-only --fork --print-pid 5 --print-address 7 --session
|-dbus-launch,1271 --autolaunch=c22ecdc4b8715fda2bdd99c05a7e7132 --binary-syntax --close-stderr
|-elogind,1037 --daemon
|-runsvdir,772 -P /run/runit/service...
| |-runsv,778 alsa
| | `-pause,802
| |-runsv,779 acpid
| | |-acpid,864 -f
| | `-svlogd,801 -tt /var/log/acpid
| |-runsv,780 agetty-tty5
| | `-agetty,804 tty5 38400 linux
| |-runsv,781 openntpd
| | |-logger,797 -t openntpd -p daemon notice
| | `-ntpd,863 -d -s
| | `-ntpd,947
| | `-ntpd,950
| |-runsv,782 socklog
| | |-socklog,862 unix /dev/log
| | `-svlogd,799 /var/log/socklog/cron /var/log/socklog/daemon /var/log/socklog/debug /var/log/socklog/errors ...
| |-runsv,783 NetworkManager
| | `-NetworkManager,800 -n
| | |-{NetworkManager},1018
| | `-{NetworkManager},1020
| |-runsv,784 agetty-tty1
| | `-login,803
| |-runsv,785 tlp
| | `-pause,796
| |-runsv,786 agetty-tty3
| | `-agetty,793 tty3 38400 linux
| |-runsv,787 agetty-tty4
| | `-agetty,792 tty4 38400 linux
| |-runsv,788 dbus
| | `-dbus-daemon,798 --system --nofork --nopidfile
| |-runsv,789 dnscrypt-proxy
| | | `-{dnscrypt-proxy},1528
| | `-svlogd,805 -t /var/log/dnscrypt-proxy
| |-runsv,790 agetty-tty6
| | `-agetty,794 tty6 38400 linux
| `-runsv,791 agetty-tty2
| `-agetty,795 tty2 38400 linux
|-udevd,291 --daemon
`-wpa_supplicant,1043 -u
Note that there are two different dbus processes. One is a child process of a runsv process (PID 798) and one is a direct child of runit (PID 1274). The dbus process with PID 1274 are launched (in this case) by Firefox (and Firefox immediately closed after I manually killed the dbus process), this means that your "running" dbus process will listen to Firefox and only Firefox, and will not work with any other processes (elogind, NetworkManager, wicd, etc.)
So no. In your case, dbus is not running as a proper service. It is likely that you're not installing both dbus-runit and networkmanager-runit and you didn't enable both services (because the service doesn't even exist).
fail: /etc/runit/runsvdir/default/dbus: unable to change to service directory: file does not exist
Also, the problem is likely fixed by enabling the dhcpcd runit service.