[Buildroot] [DEPEND] Dependency failed for Serial Getty on ttyS0.

Karoly Pados kp at tec4data.at
Mon Mar 13 20:22:55 UTC 2017


Hello,

The config I attached was without agetty, because I already tried enabling it without success (with
the same reasoning: I thought to myself "maybe buildroot has no getty if I don't enable agetty").
Unfortunately that didn't solve te problem, so my conclusion was missing agetty was the not the
cause of the problem, and I went back to my original config.

Based on what you say I do need agetty, but I am sure I also need something else, because even with
agetty, I got the same problem. Could you please advise what else could be missing?

Any help appreciated, 

Greetings,
Károly Pados

This email and any associated attachment are confidential.
Unless you belong to the specified recipients, immediately notify the sender.
The content may not be copied and given to third parties.
___________________________________________________________________

March 13, 2017 6:28 PM, "Arnout Vandecappelle" <arnout at mind.be> wrote:

> On 13-03-17 12:13, Karoly Pados wrote:
> 
>> Hello!
>> 
>> I built a buildroot image, using systemd as the init system. The kernel is built using buildroot
>> too, using a custom kernel-.config that is known to work on same hardware when used outside of
>> buildroot.
>> 
>> Most of the booting process succeeds, but towards the end systemd repeatedly tries to stop and
>> start getty, then after a minute or two outputs:
>> [DEPEND] Dependency failed for Serial Getty on ttyS0.
>> 
>> Booting then continues with UTMP, but no login prompt is shown. Not on UART and neither on VGA.
>> I've found out that others who got this same phenomenon had to enable CONFIG_FHANDLE for the
>> kernel, but for me it is already enabled.
>> 
>> Steps I used:
>> - clone buildroot from git
>> - checkout 2017.02.x branch
>> - make menuconfig (enabled systemd, disabled busybox, added a whole lot of other stuff)
> 
> ^^^^^^^^^^^^^^^^
> When you do this, you'll see the following warning appear:
> 
> You may need to enable other packages to get a working system
> You better know what you're doing!
> 
> From a quick look through your .config, I see that you don't have a getty
> package enabled. Without getty, systemd can't start getty. So you need to enable
> the agetty package.
> 
> Also note that systemd isn't thoroughly tested in Buildroot, even if you do
> enable busybox. So it is possible that you may run into other issues. Starting a
> getty should work, however.
> 
> Regards,
> Arnout
> 
>> - make
>> - flashed/installed images from output/images/
>> 
>> Here is a link to my buildroot-config: http://pastebin.com/W8KnZccU
>> 
>> Any help is appreciated.
>> 
>> Greetings,
>> Karoly
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
> 
> --
> Arnout Vandecappelle arnout at mind be
> Senior Embedded Software Architect +32-16-286500
> Essensium/Mind http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF



More information about the buildroot mailing list