From: Ubaldo Porcheddu <ubaldo@eja.it>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Preliminary support for Raspberry Pi 3 with symlink
Date: Mon, 25 Apr 2016 16:10:05 +0100 [thread overview]
Message-ID: <ec8ee5807de2689a472b1c402ede6709@eja.it> (raw)
In-Reply-To: <87oa8xpx9j.fsf@dell.be.48ers.dk>
Hi,
Il 2016-04-25 15:40 Peter Korsgaard ha scritto:
>>>>>> "Ubaldo" == Ubaldo Porcheddu <ubaldo@eja.it> writes:
>
> Hi,
>
>>>> I just tested the new kernel version but it doesn't give me the
>>>> login
> >>> prompt, the kernel seems to be booting fine as it can recognize my
> >>> keyboard but it doesn't accept any input.
> >>>
> >>
> >> I had something similar, removed the 'console=ttyAMA0...' from the
> >> cmdline.txt file, and it booted through. Mine was not able to
> recognize
> >> my keyboard, but with dropbear and an extra user I was able to
> login.
>
> > after removing the extra console declaration I can also get the
> login,
> > my keyboard get recognized by the kernel but it doesn't work
> properly,
> > seems to be adding extra characters after any key press.
>
> Funky. Removing console=ttyAMA0 (or console=ttyS0) would mean that tty1
> becomes /dev/console, so we end up having two gettys running on tty1
> which could explain the double characters.
>
> I'm not sure why it doesn't work with console= pointing at the serial
> port. Luca, you added the serial console handling, any idea what might
> be going wrong?
You are right about the double getty, indeed if I set console=tty2 I end
up with a working getty/login on tty1 and tty2 and error messages on
tty2.
Maybe the problem is in /etc/inittab using "console" in place of ttyS0?
next prev parent reply other threads:[~2016-04-25 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 20:12 [Buildroot] [PATCH 1/1] Preliminary support for Raspberry Pi 3 with symlink Ubaldo Porcheddu
2016-04-25 12:07 ` Peter Korsgaard
2016-04-25 14:06 ` Ubaldo Porcheddu
2016-04-25 14:14 ` Peter Korsgaard
2016-04-25 14:22 ` Ubaldo Porcheddu
2016-04-25 19:07 ` Peter Korsgaard
2016-04-25 14:16 ` Benoît Allard
2016-04-25 14:34 ` Ubaldo Porcheddu
2016-04-25 14:40 ` Peter Korsgaard
2016-04-25 15:10 ` Ubaldo Porcheddu [this message]
2016-04-26 14:22 ` Luca Ceresoli
2016-04-25 19:19 ` Peter Seiderer
2016-04-25 19:32 ` Peter Korsgaard
2016-04-25 19:55 ` Peter Seiderer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ec8ee5807de2689a472b1c402ede6709@eja.it \
--to=ubaldo@eja.it \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox