Hi ! I've managed to solve some problems appearing during boot but some persist. The current setup makes the system freeze in the current step :
[ 10.230000] systemd[1]: systemd 8 running in system mode. (+PAM +LIBWRAP -AUDIT -SELINUX -IPV6 -SYSVINIT) [ 10.250000] systemd[1]: No hostname configured. [ 10.260000] systemd[1]: Set hostname to <localhost>. [ 10.290000] systemd[1]: Failed to fully start up daemon: No such file or directory [ 10.370000] systemd[1]: Failed to initialize automounter: No such file or directory [ 10.380000] systemd[1]: Unit proc-sys-fs-binfmt_misc.automount entered maintenance state. Starting /etc/rc.local Compatibility... Regarding the automounter, I have used autofs v5 and not autofs4, should this make a difference ? Any ideas of those return messages when automounter enters the waiting state (Failed to initialize automounter: No such file or directory) and themanager startup problem ( Failed to fully start up daemon: No such file or directory) ? Best ! On Tue, Sep 14, 2010 at 5:58 PM, Gustavo Sverzut Barbieri < barbi...@profusion.mobi> wrote: > On Tue, Sep 14, 2010 at 10:47 AM, Cristian Axenie > <cristian.axe...@gmail.com> wrote: > > Hi ! > > I've managed to patch the source code to eliminate the sysvinit and ipv6 > > problems during bootup but now I encountered some error messages that > refer > > to other issues. > > > > Here is each line of the output and my ideas : > > > > [ 18.760000] Freeing init memory: 152K > > [ 19.410000] systemd[1]: systemd 8 running in system mode. (+PAM > +LIBWRAP > > -AUDIT -SELINUX -IPV6 -SYSVINIT) > > [ 19.450000] systemd[1]: /sbin/modprobe failed with error code 1. > > > > > > Here it seems that the kmod_setup() returns erroneously due to the fact > that > > some modules aren't present, or the modprobe parameters aren't valid. > > > > > > [ 19.500000] systemd[1]: Failed to fully start up daemon: No such file > or > > directory > > [ 19.590000] systemd[1]: Failed to open /dev/autofs: No such file or > > directory > > [ 19.600000] systemd[1]: Failed to initialize automounter: No such file > or > > directory > > [ 19.610000] systemd[1]: Unit dev-hugepages.automount entered > maintenance > > state. > > [ 19.630000] systemd[1]: Failed to open /dev/autofs: No such file or > > directory > > [ 19.640000] systemd[1]: Failed to initialize automounter: No such file > or > > directory > > [ 19.660000] systemd[1]: Unit dev-mqueue.automount entered maintenance > > state. > > [ 19.670000] systemd[1]: Failed to open /dev/autofs: No such file or > > directory > > [ 19.690000] systemd[1]: Failed to initialize automounter: No such file > or > > directory > > [ 19.700000] systemd[1]: Unit proc-sys-fs-binfmt_misc.automount entered > > maintenance state. > > [ 19.720000] systemd[1]: Failed to open /dev/autofs: No such file or > > directory > > [ 19.730000] systemd[1]: Failed to initialize automounter: No such file > or > > directory > > [ 19.750000] systemd[1]: Unit sys-kernel-debug.automount entered > > maintenance state. > > [ 19.760000] systemd[1]: Failed to open /dev/autofs: No such file or > > directory > > [ 19.780000] systemd[1]: Failed to initialize automounter: No such file > or > > directory > > [ 19.790000] systemd[1]: Unit sys-kernel-security.automount entered > > maintenance state. > > > > > > Here the manager cannot be properly started due to the fact that > > m->mount_auto = arg_mount_auto; doesn't have a proper value and the > > automounter functionality seems to be missing. > > > > [ 79.580000] systemd[1]: Job dev-tty3.device/start timed out. > > Starting Getty on tty3 failed. > > [ 79.620000] systemd[1]: Job dev-tty2.device/start timed out. > > Starting Getty on tty2 failed. > > [ 79.650000] systemd[1]: Job dev-tty6.device/start timed out. > > Starting Getty on tty6 failed. > > [ 79.680000] systemd[1]: Job dev-tty4.device/start timed out. > > Starting Getty on tty4 failed. > > [ 79.710000] systemd[1]: Job dev-tty5.device/start timed out. > > Starting Getty on tty5 failed. > > [ 80.160000] systemd[1]: Job dev-ttyS0.device/start timed out. > > Starting Serial Getty on ttyS0 failed. > > > > And finally, the control cannot be passed to a console. > > > > > > Any corrections and suggestions are appreciated. > > Likely you don't have autofs4 compiled, do you? It is required to work. > > Lennart, maybe we should make the kmod-setup take another flag "MUST" > and "OPTIONAL", do modprobe for each module in separate and fail if > "MUST" are not present? Right now it is confusing for users. > > > -- > Gustavo Sverzut Barbieri > http://profusion.mobi embedded systems > -------------------------------------- > MSN: barbi...@gmail.com > Skype: gsbarbieri > Mobile: +55 (19) 9225-2202 >
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
