From: "alayrac" <christophe.alayrac@cresitt.com>
To: "'Peter Mendham'" <petermendham@computing.dundee.ac.uk>,
<linuxppc-embedded@ozlabs.org>
Subject: RE : Kernel Panic During Linux Boot on ML405
Date: Thu, 30 Nov 2006 14:21:43 +0100 [thread overview]
Message-ID: <000001c71482$7d8ff980$c900a8c0@CRESITTLAB> (raw)
In-Reply-To: <456ECDE9.2060506@computing.dundee.ac.uk>
Hi Peter,
Is there system ace interface in your hardware?
Your kernel boot command is=20
console=3Dttl0 root=3D/dev/xsysace/disc0/part2 rw ip=3Doff
so thta after kernel start it will look for any init file ine the root
file system suppose to be on /dev/xsysace/disc0/part2
regards
Chris
CRESITT INDUSTRIE
12 Rue de Blois, BP6744
45067 ORLEANS Cedex 2
Tel : 02.38.49.45.59
Fax :02.38.49.45.55
Email : christophe.alayrac@cresitt.com=20
Web : http://www.cresitt.com
<----> -----Message d'origine-----
<----> De=A0: linuxppc-embedded-
<----> bounces+christophe.alayrac=3Dcresitt.com@ozlabs.org
[mailto:linuxppc-
<----> embedded-bounces+christophe.alayrac=3Dcresitt.com@ozlabs.org] De =
la
<----> part de Peter Mendham
<----> Envoy=E9=A0: jeudi 30 novembre 2006 13:26
<----> =C0=A0: linuxppc-embedded@ozlabs.org
<----> Objet=A0: Kernel Panic During Linux Boot on ML405
<---->=20
<----> I'm trying to make an uber-simple system on an ML405 board. I
used
<----> the
<----> BSB to create a straight forward system with a PPC, DDR RAM,
<----> opb_ethernet, a uartlite, and pretty much nothing else. The BSB
<----> threw
<----> in an interrupt controller, some DCMs and some bridges for me.
<----> That's
<----> all I have hardware-wise. I compiled a 2.4.26 kernel because
I've
<----> had
<----> one working already on the default hardware setup. I chose what
I
<----> think
<----> is the right options for the kernel, I've cut pretty much
everything
<----> out
<----> that I don't need. The BSP the EDK generated was *extremely*
<----> lacking.
<----> It only generated an xparameters_ml300.h (no other files) which
was
<----> missing all the redefines. I added these in myself by hand (this
may
<----> be
<----> the cause of my woes). A boot log is given below. I would
<----> appreciate
<----> any tips that anyone can give me. Where should I start looking?
<---->=20
<----> Thanks in advance,
next prev parent reply other threads:[~2006-11-30 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 12:26 Kernel Panic During Linux Boot on ML405 Peter Mendham
2006-11-30 13:21 ` alayrac [this message]
2006-11-30 14:31 ` RE : " Peter Mendham
2006-11-30 15:08 ` RE : " alayrac
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='000001c71482$7d8ff980$c900a8c0@CRESITTLAB' \
--to=christophe.alayrac@cresitt.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=petermendham@computing.dundee.ac.uk \
/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;
as well as URLs for NNTP newsgroup(s).