[systemd-devel] systemd not initializing

Andrey Borzenkov arvidjaar at gmail.com
Mon Jun 16 04:33:00 PDT 2014


On Mon, Jun 16, 2014 at 3:27 PM, Mantas Mikulėnas <grawity at gmail.com> wrote:
> On Jun 16, 2014 2:12 PM, "Jay D Bhatt" <jay.bhatt at igate.com> wrote:
>>
>> Hi Andrey,
>>
>> I also think getty is missing. There was no sbin/getty, it was agetty, so
>> I created soft link to make sbin/getty.
>
> Hmm, I thought getty at .service actually invokes "agetty" directly, no?
>
>> Secondly, "cat /sys/class/tty/console/active" was not possible as there
>> was no folders structure inside /sys/.
>

Which likely explains why systemd did not auto-start getty on console.

> No tty/console stuff, or absolutely empty?
>
> An empty /sys might mean that systemd failed to mount sysfs. (I should
> re-read the earlier logs you posted.) It's again a kernel option,
> CONFIG_SYSFS if I remember correctly. I wonder how well udev and systemd
> even work without sysfs.
>
>> I didn't got your below question " I see ssh service - are you able to ssh
>> into it?" How do I do ssh into it? Please guide.
>
> By using `ssh root at ip-address`, with the IP address of the device. (Of
> course that only works if the device has networking configured as well, so
> not always useful...)
>
>> Other interesting thing I found was systemd rules were not set for ttymxc*
>> . I set the rules for it, since I am using console=ttymxc3.
>
> Hmm, I think systemd automatically starts a getty on the console device too,
> no?
>

Sure, by looking in /sys ...

> If ttymxc* is common, maybe it would be useful to send a patch for including
> it along with systemd's default rules...
>


More information about the systemd-devel mailing list