From: Sven Luther <sven.luther@wanadoo.fr>
To: Leigh Brown <leigh@solinno.co.uk>
Cc: Ulrich Teichert <krypton@ulrich-teichert.org>,
Philippe Guyot <pguyot@cvf.fr>,
linuxppc-dev@ozlabs.org, debian-powerpc@lists.debian.org,
mikemartin@linux.ca
Subject: Re: 43p-140 install issues
Date: Wed, 5 Jan 2005 18:00:13 +0100 [thread overview]
Message-ID: <20050105170013.GB29287@pegasos> (raw)
In-Reply-To: <25607.195.212.29.91.1104942605.squirrel@195.212.29.91>
On Wed, Jan 05, 2005 at 04:30:05PM -0000, Leigh Brown wrote:
> Sven Luther said:
> > On Wed, Jan 05, 2005 at 09:45:13AM -0600, Hollis Blanchard wrote:
> >> On Jan 5, 2005, at 5:47 AM, Sven Luther wrote:
> >> >On Wed, Jan 05, 2005 at 10:49:19AM +0100, Philippe Guyot wrote:
> >> >>>BTW, i have another question. I am trying to fix debian-installer
> >> >>>to create the prep partition, but i would like to have some info
> >> >>>on the expected constraints of said partition. Some tell it has
> >> >>>to be entirely in the first 8MB, others the first 5MB, and my
> >> >>>powerstack has a 17MB boot partition right now.
> >> >>
> >> >>All I can say, it's that my boot PReP partition is the 1st and about
> >> >>4 MB in size (cannot size it less than 1% of the disk.....)
> >> >>second partition is /
> >> >>third is swap.
> >> >
> >> >BTW, for debian, it makes more sense to have the second partition
> >> >as swap, and the third as /, i think, since it was decided some
> >> >time back to default to root=/dev/sda3, and not sda2.
> >> >
> >> >>That works for me.
> >> >
> >> >Until the kernel grows beyond 4MB.
> >>
> >> The size of that partition depends on firmware limitations. I have
> >> definitely seen reports of systems not booting when the PReP boot
> >> partition was too large. I think on some systems that has even happened
> >> at 8MB.
> >
> > Is the problem really the size of the partition, or the space used by
> > the kernel. I mean we could make a 100MB partition at start, and since
> > we just dd the kernel to it, the kernel would be found at the start of
> > the partition, and the firmware probably doesn't care about the real
> > size of the partition, as long as it can access all the kernel data we
> > added to it, no ?
> >
> > Do we have some documentation of the firmware limitations ?
> >
> >> In other words, should you need more space than 4-5MB at some point in
> >> the future, you cannot simply make a bigger boot partition.
> >
> > 8MB would be good, 4-5MB only would probably be a bit just.
>
> Surely if you make the default mkinitrd behaviour a bit more sensible
> there won't be a problem. A compressed 2.6 kernel is about 1.5MB, and
The compressed kernel should be arounf 1.0MB only.
> an initrd using MODULES=dep is about 1.5MB, which makes about 3MB,
> giving a comfortable amount of space for future growth...
well, when i use MODULES=dep, i still get all the filesystem and a bunch of
extra ide drivers, so it is no less than 4MB. Mmm, you are right about this
one, it is only 1499136 now, which makes a total of 2856844, quite reasonable.
Mmm, i wonder it may even boot on the pegasos 1 with the broken OF now.
Still, partman-prep is currently written to make sure the prep partition is in
the first 8MB.
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-01-05 16:51 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <855e88d00412291051792d3daa@mail.gmail.com>
2004-12-31 9:53 ` 43p-140 install issues Sven Luther
2005-01-01 0:54 ` Mike Martin
2005-01-01 13:15 ` Ulrich Teichert
2005-01-01 15:00 ` Sven Luther
2005-01-01 16:30 ` Ulrich Teichert
2005-01-01 16:57 ` Sven Luther
2005-01-02 1:15 ` Mike Martin
2005-01-02 9:43 ` Sven Luther
2005-01-03 4:15 ` Mike Martin
2005-01-03 7:05 ` Sven Luther
2005-01-03 13:39 ` Mike Martin
2005-01-03 14:01 ` Sven Luther
2005-01-03 14:07 ` Mike Martin
2005-01-03 14:30 ` Sven Luther
2005-01-03 14:30 ` Philippe Guyot
2005-01-03 14:43 ` Mike Martin
2005-01-03 15:47 ` vinai
2005-01-03 14:45 ` Sven Luther
2005-01-04 4:03 ` Mike Martin
2005-01-04 8:20 ` Ulrich Teichert
2005-01-04 9:23 ` Philippe Guyot
2005-01-04 11:19 ` Ulrich Teichert
2005-01-04 11:23 ` Mike Martin
2005-01-04 13:41 ` Mike Martin
2005-01-04 15:23 ` Ulrich Teichert
2005-01-04 15:39 ` Mike Martin
2005-01-05 4:36 ` Mike Martin
2005-01-05 8:07 ` Ulrich Teichert
2005-01-05 22:09 ` Ulrich Teichert
2005-01-05 11:17 ` Leigh Brown
2005-01-06 3:35 ` Mike Martin
2005-01-06 8:15 ` Sven Luther
2005-01-07 5:10 ` Mike Martin
2005-01-07 7:57 ` Sven Luther
2005-01-03 15:51 ` Ulrich Teichert
2005-01-03 16:50 ` Leigh Brown
2005-01-03 17:28 ` Sven Luther
2005-01-03 19:32 ` Ulrich Teichert
2005-01-03 19:42 ` Leigh Brown
2005-01-03 22:11 ` Ulrich Teichert
2005-01-04 22:28 ` Sven Luther
2005-01-04 22:39 ` Leigh Brown
2005-01-05 9:03 ` Sven Luther
2005-01-05 9:49 ` Philippe Guyot
2005-01-05 10:00 ` Leigh Brown
2005-01-05 11:47 ` Sven Luther
2005-01-05 14:02 ` Philippe Guyot
2005-01-05 15:45 ` Hollis Blanchard
2005-01-05 16:08 ` Sven Luther
2005-01-05 16:18 ` Philippe Guyot
2005-01-05 16:52 ` Hollis Blanchard
2005-01-05 16:30 ` Leigh Brown
2005-01-05 17:00 ` Sven Luther [this message]
2005-01-03 9:56 ` Philippe Guyot
2005-01-03 10:48 ` Sven Luther
2005-01-03 10:56 ` Philippe Guyot
2005-01-03 11:17 ` Sven Luther
2005-01-03 11:57 ` Michael Schmitz
2005-01-03 12:47 ` Sven Luther
2005-01-03 15:24 ` Michael Schmitz
2005-01-03 16:04 ` Sven Luther
2005-01-06 12:19 ` Michael Schmitz
2005-01-06 14:02 ` Sven Luther
2005-01-02 15:38 ` Ulrich Teichert
2005-01-02 16:41 ` Sven Luther
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=20050105170013.GB29287@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=debian-powerpc@lists.debian.org \
--cc=krypton@ulrich-teichert.org \
--cc=leigh@solinno.co.uk \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikemartin@linux.ca \
--cc=pguyot@cvf.fr \
/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).