From: "Juergen Sievers" <JSievers@NADINE-Software.com>
To: 'Nishanth Menon' <menon.nishanth@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: AW: AW: Help: OMAP5912 RS232 dies after kernel uncompressing.
Date: Tue, 16 Jan 2007 13:01:51 +0100 [thread overview]
Message-ID: <000101c73966$1d1f33a0$0700a8c0@NADHHLT01> (raw)
In-Reply-To: <45AC231B.5030507@gmail.com>
Hi Nishanth.
That is a good hint and I did this already but it was not the reason.
Normal, before the ttyS0 was missing, the kernel's initializing messages
were shown on the rs323 line. But now - nothing appears after the kernel
code gets control.
I will try to reset the whole environment block to create a new and well
formatted environment. It seems to me something is wrong on these persistent
environment settings. Possible I have typed in an invisible control
character in one of these settings.
Mfg.
Juergen
> Opinion: check your /etc/inittab in the filesystem. maybe you have told
> getty to hook on to the wrong terminal... some common issues is the
> getty given wrong baud rate OR given tty0 while ttyS0 is being used
> etc.. that is a nice place to check.. but do try this: give
> "init=/bin/sh" along with ur boot options(given the rest of the
> symptoms, this should work).. if u manage to boot off that.. u need to
> look deep into ur boot sequence of filesystem -such as rc scripts etc if
> you have any.
>
> Regards,
> Nishanth Menon
next prev parent reply other threads:[~2007-01-16 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 16:34 [Howto] 2430 kernel,uboot and filesystem Nishanth Menon
2007-01-15 15:22 ` Help: OMAP5912 RS232 dies after kernel uncompressing Juergen Sievers
2007-01-15 15:53 ` Abot Botbot
2007-01-15 20:50 ` AW: " Juergen Sievers
2007-01-16 0:58 ` Nishanth Menon
2007-01-16 12:01 ` Juergen Sievers [this message]
2007-01-15 16:05 ` Liem Pham Tan
2007-01-15 18:00 ` [Howto] 2430 kernel,uboot and filesystem Dirk Behme
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='000101c73966$1d1f33a0$0700a8c0@NADHHLT01' \
--to=jsievers@nadine-software.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=menon.nishanth@gmail.com \
/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