Hi, On Mon, Mar 21, 2011 at 02:58:22PM +0100, Jan Engelhardt wrote: > On Monday 2011-03-21 12:26, Michael Olbrich wrote: > >I've been playing with systemd. So far I have been unable to get a login > >prompt. The problem is this: > > > >[...] > >systemd[1]: Job dev-ttyAMA0.device/start timed out. > >systemd[1]: Job dev-ttyAMA0.device/start finished, result=timeout > >systemd[1]: Job serial-getty@ttyAMA0.service/start finished, > >result=dependency > >[...] > > This is reminiscient of > https://bugzilla.novell.com/show_bug.cgi?id=679165
You are both correct. After getting udev to start (thanks Kay) it worked on qemu/x86 but not qemu/arm. After modifying src/99-systemd.rules it worked for arm as well. > The default systemd files only start getties on a handful of ttys. Since > it seems impossible to distinguish between display ttys and e.g. modem > ttys, one can't just simply start gettys on all tty*, thus necessiting > manual addition for further ttys in the udev rules. hmmm, that is unfortunate. There are a lot of different names for the serial ports on embedded systems. And using a serial console here is rather common. Maybe the tty from /sys/class/tty/console/active can always be added somehow? Regards, Michael Olbrich -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
