Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jigar SOLANKI <jigar.solanki@labri.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Cant type anything into Serial Console login
Date: Wed, 11 Jan 2012 16:35:44 +0100	[thread overview]
Message-ID: <4F0DAC50.7080602@labri.fr> (raw)
In-Reply-To: <87hb029s3c.fsf@macbook.be.48ers.dk>

Le 11/01/2012 16:28, Peter Korsgaard a ?crit :
>>>>>> "Jigar" == Jigar SOLANKI <jigar.solanki@labri.fr> writes:
> 
>  >> That doesn't seem to match your first mail:
>  >> 
>  >> # Put a getty on the serial port
>  >> ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL
>  >> 
> 
>  Jigar> Yep, sorry, I was just testing every ttySx at random. The command line
>  Jigar> indeed was with ttyS0 of course, everything in kernel command/serial
>  Jigar> console client/inittab/security is coherent with the ttySx I choose.
> 
>  Jigar> Same result with both.
> 
> What do you mean with 'same result'? From your first mail you mentioned
> you got 'Welcome to Buildroot' and a Login prompt. If you boot with
> init=/bin/sh you shouldn't get any of that.
> 
> I notice you don't provide any root=. What kind of file system are you
> trying to boot?
> 
> Perhaps just paste the entire boot log.
> 

Yes, I didn't get anything of that.

So, with ttyS0, with complete command = console=ttyS0,38400,
I get to the boot prompt, where I can't type anything, the keyboard
doesnt respond.

And with complete command = console=ttyS0,38400 init=/bin/sh
The boot process hangs on the first line which is Booting Linux....
and then..nothing. If I tried to type anything with my keyboard at that
time, same result, which is : nothing happens, the keyboard still doesnt
responding at all.

I also tried with a USB<->Serial converter (so, with ttyUSB0 then) and
had the same result without init=/bin/sh, I get to the Buildroot boot
prompt and then cannot login because I can't type anything ; and also
wiith init=/bin/sh where the boot process stops at Booting Linux...and
then nothing happens, even if I type something. Even with ENTER key, the
output doesnt go to the next blank line...

Sigh...
-- 
Jigar SOLANKI

LaBRI - UMR 5800
Universit? Bordeaux 1
351 Cours de la Lib?ration
F-33405 Talence Cedex
Phone : (+33) 5 4000 24 87
Fax   : (+33) 5 4000 66 69
Web   : http://www.labri.fr/perso/solanki

* Please do not print this e-mail unless it's really necessary *
---


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 554 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120111/9d1110fd/attachment.asc>

  reply	other threads:[~2012-01-11 15:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 11:46 [Buildroot] Cant type anything into Serial Console login Jigar SOLANKI
2012-01-11 11:56 ` Will Newton
2012-01-11 13:52 ` Peter Korsgaard
2012-01-11 14:22   ` Jigar SOLANKI
2012-01-11 14:26     ` Peter Korsgaard
2012-01-11 14:30       ` Jigar SOLANKI
2012-01-11 15:17         ` Peter Korsgaard
2012-01-11 15:22           ` Jigar SOLANKI
2012-01-11 15:28             ` Peter Korsgaard
2012-01-11 15:35               ` Jigar SOLANKI [this message]
2012-01-11 15:38                 ` Jigar SOLANKI

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=4F0DAC50.7080602@labri.fr \
    --to=jigar.solanki@labri.fr \
    --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