linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pradeep Sampath <pradeepsampath@yahoo.com>
To: Ameet Patil <ammubhai@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: booting 2.6 kernel on ML403
Date: Thu, 5 Oct 2006 08:47:00 -0700 (PDT)	[thread overview]
Message-ID: <20061005154700.5018.qmail@web83212.mail.mud.yahoo.com> (raw)
In-Reply-To: <4524C290.3090702@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

Hi Ameet,
   
  As soon as i apply the sysace driver and temac drivers and copy the xparameters_ml300.h (from EDK) to xparameters_ml403.h all i get is this... meaning kernel hangs after displaying "Now booting the kernel".
   
  When i disable sysace and TEMAC drivers, the system goes further till "root=" option and then tries to "Kernel Rebooting in 180 seconds". Yesterday i tried root=/dev/xsysace2 rw and creating block device files in /dev of the CF card. But it ran into the same problem.Is there a sysace driver patch that i can apply without applying the TEMAC driver patch? 
   
  So far i was using the EDK 8.1 SP2 (latest) which has the IP core TEMAC version 3.00. Now i downgraded to EDK 8.1 to get the version 2.00 (please see John Bonesio's post). 
   
  I thought the first step is to get the sysace driver running before applying the TEMAC drivers.

  thanks very much!
  Pradeep

Ameet Patil <ammubhai@gmail.com> wrote:
  Pradeep,
What you have pasted is only part of the messages displayed. I can't 
tell anything from this apart from you 'root=' option. It would be nice 
if you could paste the entire log of the boot messages right from 
'loaded at: xxxxxxx xxxxxxxx' to 'Kernel Rebooting in 150 seconds'.

-Ameet

Pradeep Sampath wrote:
> Ameet,
> 
> loaded at: 00400000 0051513C
> board data at: 00513124 0051313C
> relocated to: 004050E8 00405100
> zimage at: 004057FD 0051230A
> avail ram: 00516000 04000000
> Linux/PPC load: console=ttyS0,9600 root=/dev/xsa2
> Uncompressing Linux...done.
> Now booting the kernel
>
>
> Please could send me all the boot messages until the point where it
> stops. This will help me better identify the problem.
>
> Thanks,
> -Ameet
>
>



[-- Attachment #2: Type: text/html, Size: 2150 bytes --]

  reply	other threads:[~2006-10-05 15:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03  6:42 booting 2.6 kernel on ML403 Pradeep Sampath
2006-10-03  8:24 ` Ameet Patil
2006-10-03 21:46   ` Pradeep Sampath
2006-10-04  8:00     ` Ameet Patil
2006-10-04 16:47       ` Pradeep Sampath
2006-10-05  8:30         ` Ameet Patil
2006-10-05 15:47           ` Pradeep Sampath [this message]
2006-10-06  8:24             ` Ming Liu
2006-10-06  6:37           ` Pradeep Sampath
2006-10-04  8:11     ` Ming Liu
2006-10-04  8:35       ` Ameet Patil
2006-10-04  8:42         ` Ming Liu
2006-10-04 16:35           ` Pradeep Sampath
2006-10-05  8:27             ` Ameet Patil
2006-10-06  8:50           ` David H. Lynch Jr.
  -- strict thread matches above, loose matches on Subject: below --
2006-10-04 17:09 John Bonesio
2006-10-04 17:17 John Bonesio

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=20061005154700.5018.qmail@web83212.mail.mud.yahoo.com \
    --to=pradeepsampath@yahoo.com \
    --cc=ammubhai@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 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).