Any help? On Mon, Feb 4, 2013 at 3:25 PM, abhishek tejaswi <[email protected] > wrote:
> Hi Ning, > Thanks for your response. > I used init=/bin/bash and could able to get the bash shell. From there I > am trying to enable the systemd services. > I am following the link below and tried almost all of the methods they > have mentioned in order to get the shell. > http://freedesktop.org/wiki/Software/systemd/Debugging > > Please let me know which minimum services need to be enable in order to > boot through systemd successfully. I am making changes in > /usr/lib/systemd/system where all the services of systemd are stored. > > Regards > > On Mon, Feb 4, 2013 at 10:41 AM, Wang, Ning W <[email protected]>wrote: > >> If you take a look at the log, you might have noticed that systemd was >> entering emergency mode due to failed udev service as following snippets >> shows:**** >> >> ** ** >> >> <31>systemd[1]: Got SIGCHLD for process 111 (udevd) >> <31>systemd[1]: Child 111 died (code=exited, status=0/SUCCESS) >> <31>systemd[1]: Child 111 belongs to udev.service >> <31>systemd[1]: udev.service: main process exited, code=exited, status=0 >> <31>systemd[1]: udev.service changed stop-sigterm -> dead >> <31>systemd[1]: Job udev.service/stop finished, result=done >> <31>systemd[1]: Got SIGCHLD for process 180 ((plymouth)) >> <31>systemd[1]: Child 180 died (code=exited, status=200/CHDIR) >> <31>systemd[1]: Child 180 belongs to emergency.service >> <31>systemd[1]: emergency.service: control process exited, code=exited >> status=200 >> <31>systemd[1]: emergency.service running next control command for state >> start-pre >> <31>systemd[1]: About to execute: /bin/echo 'Welcome to emergency mode. >> Use "systemctl default" or ^D to activate default mode.' >> >> **** >> >> To narrow down the problem, you might need to boot with "init=/bin/bash" >> command line, then check if any devices on your board worked as expected* >> *** >> >> by checking your dmesg and so on..**** >> >> ** ** >> >> -Ning**** >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *abhishek tejaswi >> *Sent:* Friday, February 01, 2013 5:30 PM >> *To:* [email protected] >> *Subject:* [Tizen General] Booting tizen on ti platform : Issue with >> File system init**** >> >> ** ** >> >> Hi all, >> I am trying to bring up Tizen on Ti platform. Currently I am able to >> compile the linux 2.6.37 kernel, create fs image. Kernel loads properly >> but file system initialization is not happening properly and hangs. After >> giving message. >> <31>systemd[1]: sys-devices-virtual-tty-ttyprintk.device changed dead -> >> plugged >> I have attached the file for reference. >> Please help me solve the issue. >> >> Thanks**** >> > >
_______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
