From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Addison Baldwin <addison.baldwin@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Unable to open an initial console
Date: Fri, 16 Dec 2005 23:09:05 +0300 [thread overview]
Message-ID: <43A31EE1.3030101@ru.mvista.com> (raw)
In-Reply-To: <af313df20512161201u39280d30kdf1ace1c4569d50a@mail.gmail.com>
Addison Baldwin wrote:
> I was sucessful to port U-Boot to our 8272 board. Now I'm experiencing
> a problem:
>
> Our Kernel hangs with the message that says it was trasnferring
> control to linux. A post morten analyzes indicated that it stopped at
> "Unable to open an initial console" in the memory sapce where console
> output should be out (in the sdram, like I had found somewhere in this
> list, how to do it).
>
> I have checked the bootargs values, it is ok:
> bootargs root=/dev/ram console=ttyS0,115200
>
Only for 2.4, 2.6 is different for this.
console=ttyCPM0 should be there, and that device does have different major/minor comparing to ttyS0.
Note that the UART has to be enabled explicitly in kernel config, for more info, search this list archives.
> We also checked our "/dev" and there was a link to console, pointing
> ttyS0. Also, ttyS0 was there too.
>
> Does anyone have any idea how to fix it?
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
--
Sincerely,
Vitaly
next prev parent reply other threads:[~2005-12-16 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 20:01 Unable to open an initial console Addison Baldwin
2005-12-16 20:09 ` Vitaly Bordug [this message]
2005-12-19 12:17 ` Addison Baldwin
2005-12-17 5:23 ` Nigel Cunningham
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=43A31EE1.3030101@ru.mvista.com \
--to=vbordug@ru.mvista.com \
--cc=addison.baldwin@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.