From: Johnnie Peters <jpeters@phx.mcd.mot.com>
To: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200)
Date: Fri, 15 Jan 1999 19:23:38 -0700 [thread overview]
Message-ID: <369FF829.9BF97E11@phx.mcd.mot.com> (raw)
I think this is the same problem I was seeing. This machine is also the
known as
the Utah. I fixed this in arch/ppc/boot/misc.c. Here is the diff:
454c454
< if (( (unsigned long)zimage_start <= 0x01000000 ) &&
initrd_start)
---
> if ( (unsigned long)zimage_start <= 0x01000000 )
Johnnie
Michael Meissner wrote:
> On Fri, Jan 15, 1999 at 04:28:55PM +0100, Alois Fertl wrote:
> > Cort Dougan wrote:
> > >
> > > It looks like your zImage is being stomped on before it can be
> > > decompressed. I'll take a look at the boot loader code and see
why it
> > > isn't adjusting your free ram section. You might want to try
changing to
> > > load address in the PPCBug to be near the top of memory in the
mean time.
> > I guess this system is running "PowerPC Open Firmware". You can
change the
> > load address via the firmware menu:
> > Administrative Options...
> > ---> Modify the Configuration Settings...
> > ---> Edit Configuration Variables
> > step to the parameter "load-base" and enter a new value (decimal).
> > One other problem is the this firmware version obviously does not
provide
> > residual data. So Linux will probably not find the PCI devices
correctly.
>
> I tried setting the load-base to various values, and all of them
caused dumps
> within the monitor (I tried 10 meg, 64 meg, 3 meg, 120 meg, and even 4
meg + 4
> all to no avail).
>
> Also, Gary Thomas's 2.0.32 kernel seemed to have no problem in sizing
memory,
> so I presume it is able to pick up the residual data.
>
> > >
> > > } loaded at: 00400400 00415FD0
> > > } relocated to: 00600000 00615BD0
> > > } zimage at: 0040A400 0049A889
> > > } avail ram: 00400000 00600000
> > > }
> > > } Linux/PPC load: console=tty0 console=ttyS0,9600n8
root=/dev/sda2 mem=127M
> > > } Uncompressing Linux...done.
> > > } Now booting the kernel
>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next reply other threads:[~1999-01-16 2:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-16 2:23 Johnnie Peters [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-01-12 22:43 Booting 2.2.0-pre6 on a PowerStack-II (Net 4000/200) Michael Meissner
1999-01-13 20:10 ` Cort Dougan
1999-01-15 15:28 ` Alois Fertl
1999-01-15 20:10 ` Cort Dougan
1999-01-15 21:58 ` Michael Meissner
1999-01-15 22:04 ` Cort Dougan
1999-01-15 23:33 ` Michael Meissner
1999-01-18 8:51 ` Alois Fertl
1999-01-16 1:49 ` Johnnie Peters
1999-01-16 18:54 ` Dan Malek
1999-01-17 18:58 ` Cort Dougan
1999-01-18 9:21 ` Gabriel Paubert
1999-01-18 13:01 ` Gary Thomas
1999-01-18 16:54 ` Cort Dougan
1999-01-18 17:58 ` Michael Meissner
1999-01-19 22:43 ` Michael Meissner
1999-01-20 0:18 ` Johnnie Peters
1999-01-20 15:21 ` Gary Thomas
1999-01-20 15:31 ` Johnnie Peters
1999-01-21 23:46 ` Johnnie Peters
1999-01-22 1:52 ` Michael Meissner
1999-01-22 2:04 ` Cort Dougan
1999-01-22 7:54 ` Gary Thomas
1999-01-22 8:19 ` Cort Dougan
1999-01-22 11:07 ` Gary Thomas
1999-01-22 15:17 ` Johnnie Peters
1999-02-01 15:58 ` Michael Meissner
1999-02-01 16:18 ` Gary Thomas
1999-02-04 19:09 ` Michael Meissner
1999-02-04 19:21 ` Gary Thomas
1999-02-04 20:23 ` Michael Meissner
[not found] ` <XFMail.990119102730.gdt@linuxppc.org>
1999-01-19 13:13 ` Michael Meissner
1999-01-19 13:28 ` Gary Thomas
1999-01-19 18:54 ` Dan Malek
1999-01-20 13:56 ` Loic Prylli
1999-01-18 18:11 ` Dan Malek
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=369FF829.9BF97E11@phx.mcd.mot.com \
--to=jpeters@phx.mcd.mot.com \
--cc=linuxppc-dev@lists.linuxppc.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).