All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nivedita Pitre" <Nivedita.Pitre@p-com.com>
To: <wd@denx.de>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Linux booting problems in the IBM Bubinga Board
Date: Wed, 04 Aug 2004 17:22:13 -0700	[thread overview]
Message-ID: <s1111b54.006@gateway.p-com.com> (raw)


Yes, I tried both with and without the console= argument,
selecting ttyS0 and baud 9600. Same result.

>>> Wolfgang Denk <wd@denx.de> 08/04/04 05:03PM >>>
In message <s1110fc4.060@gateway.p-com.com> you wrote:
>
> I am using U-boot to boot linux kernel on the IBM Bubinga (405EP board). Using kernel version 2.6.7, which has a default config file for this board. Changed the board info structure to match u-boot's board information structure. Using the mkimage utilit

PLEASE don't use such long lines. Press ENTER after some 60...70
characters or so.

> ach_dep calls output some messages. This tells me that code reaches in start_kernel, however, after console_init, the serial port dies. I assume this is because we initialize the serial port, and turn off early debug. I commented o

Did you pass some "console=..." boot argument?

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
One difference between a man and a machine is that a machine is quiet
when well oiled.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2004-08-05  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  0:22 Nivedita Pitre [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-04 23:32 Linux booting problems in the IBM Bubinga Board Nivedita Pitre
2004-08-05  0:03 ` Wolfgang Denk

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=s1111b54.006@gateway.p-com.com \
    --to=nivedita.pitre@p-com.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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.