<html dir="ltr"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style> </head> <body ocsi="0" fpstyle="1"> <div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hello, I am running systemd on imx-53 eval board with kernel version 2.6.38. I am not getting login prompt. Following are systemd messages while booting Can anybody tell what is going wrong? Regards, devendra <30>systemd[1]: systemd 37 running in system mode. (-PAM -LIBWRAP -AUDIT -SELINUX +SYSVINIT -LIBCRYPTSETUP; debian) Welcome to Linux! <28>systemd[1]: /sbin/modprobe failed with error code 1. <30>systemd[1]: Set hostname to <KPITiMX-53>. <28>systemd[1]: /etc/mtab is not a symlink or not pointing to /proc/self/mounts. This is not supported anymore. Please make sure to replace this file by a s. Started POSIX Message Queue File System. Starting Security File System... Started Set Up Additional Binary Formats. Starting Setup Virtual Console... Started Apply Kernel Variables. Started Huge Pages File System. Started Load Kernel Modules. <28>systemd-vconsole-setup[35]: /bin/loadkeys failed with error code 1. <28>systemd-vconsole-setup[35]: /bin/setfont failed with error code 1. Started Configuration File System. Starting FUSE Control File System... Starting Runtime Directory... Starting Lock Directory... Starting Remount API VFS... Starting Media Directory... Starting File System Check on Root Device... Starting udev Coldplug all Devices... <30>systemd-fsck[51]: Root directory is writable, skipping check. Starting udev Kernel Device Manager... Starting Syslog Kernel Log Buffer Bridge... Started Syslog Kernel Log Buffer Bridge. Starting Debug File System... Started Security File System. <30>udevd[55]: starting version 172 Started udev Kernel Device Manager. <27>udevd[55]: specified group 'dialout' unknown Started Setup Virtual Console. <27>udevd[55]: specified group 'kmem' unknown <27>udevd[55]: specified group 'video' unknown <27>udevd[55]: specified group 'audio' unknown Started FUSE Control File System.<27> udevd[55]: specified group 'lp' unknown <27>udevd[55]: specified group 'floppy' unknown Started Runtime Directory.<27> udevd[55]: specified group 'cdrom' unknown Started Lock Directory.<27> udevd[55]: specified group 'tape' unknown Started Remount API VFS. Started Media Directory. Started File System Check on Root Device. Started Debug File System. Starting Remount Root FS... Starting STDOUT Syslog Bridge... Started STDOUT Syslog Bridge. Started udev Coldplug all Devices. <30>systemd-stdout-syslog-bridge[78]: Failed to accept new connection: Function not implemented <29>systemd[1]: systemd-stdout-syslog-bridge.service: main process exited, code=exited, status=1 <29>systemd[1]: Unit systemd-stdout-syslog-bridge.service entered failed state. Starting STDOUT Syslog Bridge... Started STDOUT Syslog Bridge. <30>systemd-stdout-syslog-bridge[161]: Failed to accept new connection: Function not implemented Starting STDOUT Syslog Bridge... <29>systemd[1]: systemd-stdout-syslog-bridge.service: main process exited, code=exited, status=1 Started STDOUT Syslog Bridge. Starting STDOUT Syslog Bridge... <29>systemd[1]: Unit systemd-stdout-syslog-bridge.service entered failed state. Started STDOUT Syslog Bridge. <30>systemd-stdout-syslog-bridge[164]: Failed to accept new connection: Function not implemented <29>systemd[1]: systemd-stdout-syslog-bridge.service: main process exited, code=exited, status=1 Starting STDOUT Syslog Bridge... <29>systemd[1]: Unit systemd-stdout-syslog-bridge.service entered failed state. <30>systemd-stdout-syslog-bridge[169]: Failed to accept new connection: Function not implemented Started STDOUT Syslog Bridge. Starting STDOUT Syslog Bridge... Started STDOUT Syslog Bridge. <29>systemd[1]: systemd-stdout-syslog-bridge.service: main process exited, code=exited, status=1 Starting STDOUT Syslog Bridge...<29> systemd[1]: Unit systemd-stdout-syslog-bridge.service entered failed state. Starting STDOUT Syslog Bridge failed, see 'systemctl status systemd-stdout-syslog-bridge.service' for details. <30>systemd-stdout-syslog-bridge[172]: Failed to accept new connection: Function not implemented <29>systemd[1]: systemd-stdout-syslog-bridge.service: main process exited, code=exited, status=1 <29>systemd[1]: Unit systemd-stdout-syslog-bridge.service entered failed state. <30>systemd-stdout-syslog-bridge[175]: Failed to accept new connection: Function not implemented <29>systemd[1]: systemd-stdout-syslog-bridge.service: main process exited, code=exited, status=1 <29>systemd[1]: Unit systemd-stdout-syslog-bridge.service entered failed state. <28>systemd[1]: systemd-stdout-syslog-bridge.service start request repeated too quickly, refusing to start. Started Remount Root FS. Started Machine ID first boot configure. Starting /tmp... Started Opkg first boot configure. Started /tmp. Starting Recreate Volatile Files and Directories... Starting Load Random Seed... <27>systemd-tmpfiles[189]: [/usr/lib/tmpfiles.d/legacy.conf:22] Unknown group 'lock'. Starting Recreate Volatile Files <29>and Directories failedsystemd, see 'systemctl status systemd-t[1]: mpfiles-setup.service' for detailsystemd-tmpfiles-se. Started Load Random Seed. <29>systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state. Starting Login Service... Starting Permit User Sessions... Starting D-Bus System Message Bus... Started Permit User Sessions. Starting Getty on tty1... Started Getty on tty1. Starting Serial Getty on ttymxc0... Started Serial Getty on ttymxc0. <30>systemd[1]: serial-getty@ttymxc0.service holdoff time over, scheduling restart. Starting Serial Getty on ttymxc0... Started Serial Getty on ttymxc0. Started D-Bus System Message Bus. <30>systemd-logind[195]: New seat seat0. Started Login Service. <30>systemd[1]: serial-getty@ttymxc0.service holdoff time over, scheduling restart. <30>systemd[1]: serial-getty@ttymxc0.service holdoff time over, scheduling restart. <30>systemd[1]: serial-getty@ttymxc0.service holdoff time over, scheduling restart. <30>systemd[1]: Startup finished in 3s 760ms 287us (kernel) + 3s 378ms 763us (userspace) = 7s 139ms 50us. <30>systemd[1]: serial-getty@ttymxc0.service holdoff time over, scheduling restart. <30>systemd[1]: serial-getty@ttymxc0.service holdoff time over, scheduling restart. <28>systemd[1]: serial-getty@ttymxc0.service start request repeated too quickly, refusing to start. </div> This message contains information that may be privileged or confidential and is the property of the KPIT Cummins Infosystems Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Cummins Infosystems Ltd. does not accept any liability for virus infected mails. </body> </html>