c95bf441a6
When trying to run a buildroot system configured with BR2_TARGET_GENERIC_GETTY_PORT="tty1" (x86_64), the boot process hangs with the following message: "A start job is running for dev-tty1.device (<time> / 1min 30s)" Replacing /etc/systemd/system/getty.target.wants/serial-getty@tty1.service (linking to serial-getty@) with getty@tty1.service (-> getty@) fixes the issue. This patch adds a check that "detects" the tty type by removing digits at the end of BR2_TARGET_GENERIC_GETTY_PORT and comparing the resulting base name. An instance of getty@service gets created if the name matches "tty", otherwise serial-getty@ gets instantiated (as before). So, tty1,tty2,... are created as links getty@tty1.service -> getty@, while ttyS0, ttyAMA0, ... are created as instances of serial-getty@. [Peter: simplify logic] Signed-off-by: André Erdmann <dywi@mailerd.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> |
||
|---|---|---|
| .. | ||
| Config.in | ||
| network.service | ||
| systemd-01-fix-getty-unit.patch | ||
| systemd-02-build-sys-revert-use-of-ln-relative-option.patch | ||
| systemd-03-fix-am-path-libgcrypt-no-found.patch | ||
| systemd.mk | ||