Why do I not get a console with systemd?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












2














I'm trying to get a login prompt on an embedded system using Debian and systemd. The system is connected via a physical serial console to a host PC. If I start the kernel with the cmdline parameters console=ttyS5,115200 console=tty1 systemd.journald.forward_to_console=1 I do see all the kernel messages from /dev/kmsg and systemd logs, but I never see a login prompt. If I omit console=tty1 the kernel log is still beeing printed, but the systemd logs appear with a 30 seconds timeout for each line.



What's the problem here? The same root file system works just fine for a similar embedded system.










share|improve this question



















  • 1




    You say it's an embedded system. Is it an x86 system or something else? The name ttyS5 would indicate that there are 5 other serial ports (ttyS0 .. ttyS4). In a regular x86 system, only up to four classic 8250-compatible serial ports are expected by default; have you made any kernel configuration changes? What is the output of setserial -g /dev/ttyS*? If the serial port is not 8250-compatible, is the appropriate hardware support built into the kernel?
    – telcoM
    Dec 12 at 14:11










  • You say "If I omit console=tty1 the kernel log is still beeing printed, but the systemd logs appear with a 30 seconds timeout for each line." But do you get a console prompt that way? The 30s delay, is it really for each line? Or does it look like the lines are "batched" together, so you get multiple lines at once every so often?
    – Filipe Brandenburger
    Dec 12 at 14:35










  • Also posted at: github.com/systemd/systemd/issues/11133
    – Filipe Brandenburger
    Dec 12 at 19:11















2














I'm trying to get a login prompt on an embedded system using Debian and systemd. The system is connected via a physical serial console to a host PC. If I start the kernel with the cmdline parameters console=ttyS5,115200 console=tty1 systemd.journald.forward_to_console=1 I do see all the kernel messages from /dev/kmsg and systemd logs, but I never see a login prompt. If I omit console=tty1 the kernel log is still beeing printed, but the systemd logs appear with a 30 seconds timeout for each line.



What's the problem here? The same root file system works just fine for a similar embedded system.










share|improve this question



















  • 1




    You say it's an embedded system. Is it an x86 system or something else? The name ttyS5 would indicate that there are 5 other serial ports (ttyS0 .. ttyS4). In a regular x86 system, only up to four classic 8250-compatible serial ports are expected by default; have you made any kernel configuration changes? What is the output of setserial -g /dev/ttyS*? If the serial port is not 8250-compatible, is the appropriate hardware support built into the kernel?
    – telcoM
    Dec 12 at 14:11










  • You say "If I omit console=tty1 the kernel log is still beeing printed, but the systemd logs appear with a 30 seconds timeout for each line." But do you get a console prompt that way? The 30s delay, is it really for each line? Or does it look like the lines are "batched" together, so you get multiple lines at once every so often?
    – Filipe Brandenburger
    Dec 12 at 14:35










  • Also posted at: github.com/systemd/systemd/issues/11133
    – Filipe Brandenburger
    Dec 12 at 19:11













2












2








2







I'm trying to get a login prompt on an embedded system using Debian and systemd. The system is connected via a physical serial console to a host PC. If I start the kernel with the cmdline parameters console=ttyS5,115200 console=tty1 systemd.journald.forward_to_console=1 I do see all the kernel messages from /dev/kmsg and systemd logs, but I never see a login prompt. If I omit console=tty1 the kernel log is still beeing printed, but the systemd logs appear with a 30 seconds timeout for each line.



What's the problem here? The same root file system works just fine for a similar embedded system.










share|improve this question















I'm trying to get a login prompt on an embedded system using Debian and systemd. The system is connected via a physical serial console to a host PC. If I start the kernel with the cmdline parameters console=ttyS5,115200 console=tty1 systemd.journald.forward_to_console=1 I do see all the kernel messages from /dev/kmsg and systemd logs, but I never see a login prompt. If I omit console=tty1 the kernel log is still beeing printed, but the systemd logs appear with a 30 seconds timeout for each line.



What's the problem here? The same root file system works just fine for a similar embedded system.







systemd tty serial-console getty agetty






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 12 at 13:43

























asked Dec 12 at 13:17









JohnnyFromBF

1,30792034




1,30792034







  • 1




    You say it's an embedded system. Is it an x86 system or something else? The name ttyS5 would indicate that there are 5 other serial ports (ttyS0 .. ttyS4). In a regular x86 system, only up to four classic 8250-compatible serial ports are expected by default; have you made any kernel configuration changes? What is the output of setserial -g /dev/ttyS*? If the serial port is not 8250-compatible, is the appropriate hardware support built into the kernel?
    – telcoM
    Dec 12 at 14:11










  • You say "If I omit console=tty1 the kernel log is still beeing printed, but the systemd logs appear with a 30 seconds timeout for each line." But do you get a console prompt that way? The 30s delay, is it really for each line? Or does it look like the lines are "batched" together, so you get multiple lines at once every so often?
    – Filipe Brandenburger
    Dec 12 at 14:35










  • Also posted at: github.com/systemd/systemd/issues/11133
    – Filipe Brandenburger
    Dec 12 at 19:11












  • 1




    You say it's an embedded system. Is it an x86 system or something else? The name ttyS5 would indicate that there are 5 other serial ports (ttyS0 .. ttyS4). In a regular x86 system, only up to four classic 8250-compatible serial ports are expected by default; have you made any kernel configuration changes? What is the output of setserial -g /dev/ttyS*? If the serial port is not 8250-compatible, is the appropriate hardware support built into the kernel?
    – telcoM
    Dec 12 at 14:11










  • You say "If I omit console=tty1 the kernel log is still beeing printed, but the systemd logs appear with a 30 seconds timeout for each line." But do you get a console prompt that way? The 30s delay, is it really for each line? Or does it look like the lines are "batched" together, so you get multiple lines at once every so often?
    – Filipe Brandenburger
    Dec 12 at 14:35










  • Also posted at: github.com/systemd/systemd/issues/11133
    – Filipe Brandenburger
    Dec 12 at 19:11







1




1




You say it's an embedded system. Is it an x86 system or something else? The name ttyS5 would indicate that there are 5 other serial ports (ttyS0 .. ttyS4). In a regular x86 system, only up to four classic 8250-compatible serial ports are expected by default; have you made any kernel configuration changes? What is the output of setserial -g /dev/ttyS*? If the serial port is not 8250-compatible, is the appropriate hardware support built into the kernel?
– telcoM
Dec 12 at 14:11




You say it's an embedded system. Is it an x86 system or something else? The name ttyS5 would indicate that there are 5 other serial ports (ttyS0 .. ttyS4). In a regular x86 system, only up to four classic 8250-compatible serial ports are expected by default; have you made any kernel configuration changes? What is the output of setserial -g /dev/ttyS*? If the serial port is not 8250-compatible, is the appropriate hardware support built into the kernel?
– telcoM
Dec 12 at 14:11












You say "If I omit console=tty1 the kernel log is still beeing printed, but the systemd logs appear with a 30 seconds timeout for each line." But do you get a console prompt that way? The 30s delay, is it really for each line? Or does it look like the lines are "batched" together, so you get multiple lines at once every so often?
– Filipe Brandenburger
Dec 12 at 14:35




You say "If I omit console=tty1 the kernel log is still beeing printed, but the systemd logs appear with a 30 seconds timeout for each line." But do you get a console prompt that way? The 30s delay, is it really for each line? Or does it look like the lines are "batched" together, so you get multiple lines at once every so often?
– Filipe Brandenburger
Dec 12 at 14:35












Also posted at: github.com/systemd/systemd/issues/11133
– Filipe Brandenburger
Dec 12 at 19:11




Also posted at: github.com/systemd/systemd/issues/11133
– Filipe Brandenburger
Dec 12 at 19:11















active

oldest

votes











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f487575%2fwhy-do-i-not-get-a-console-with-systemd%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f487575%2fwhy-do-i-not-get-a-console-with-systemd%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay