Hello,
On Wed, 26 Nov 2003, Peter Keel wrote:
* on the Tue, Nov 25, 2003 at 06:44:23AM -0800, David S. Miller wrote:
On Tue, 25 Nov 2003 15:34:58 +0100
Thomas Habets [EMAIL PROTECTED] wrote:
I thought that was what mattered, but is it fixable? 3MB is not enough for
everybody. I'd
On Tue, 25 Nov 2003 15:34:58 +0100
Thomas Habets [EMAIL PROTECTED] wrote:
I thought that was what mattered, but is it fixable? 3MB is not enough for
everybody. I'd say it's hardly enough for anybody actually.
It's more than enough, it's enough to fit the build that
results from using
Is it SILO or the kernel that needs to be fixed? Is it like the zImage/bzImage
issue of where in memory the kernel is placed, and if so, can it be made to
load elsewhere?
There's nothing to fix. This limitation comes from the OBP firmware.
I've been building kernels just fine for a long time,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 19 November 2003 16:59, Ben Collins wrote:
Unstripped arch/sparc/boot/image:
2.9M Nov 19 01:57 /boot/vmlinux-2.6.0-test9
1.2M Nov 19 01:58 /boot/vmlinuz-2.6.0-test
2.9M should be perfectly fine to boot. I can't imagine SILO
On Wed, Nov 19, 2003 at 05:35:21PM +0100, Thomas Habets wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 19 November 2003 16:59, Ben Collins wrote:
Unstripped arch/sparc/boot/image:
2.9M Nov 19 01:57 /boot/vmlinux-2.6.0-test9
1.2M Nov 19 01:58
On 19/11/2003 at 17.35 Thomas Habets wrote:
2.9M should be perfectly fine to boot. I can't imagine SILO rejecting
that as too big.
I can, since it did.
Happened to me, too. It starts complaining at about 2 megabytes. SILO is
the Unstable package, but it didn't help.
Bye
Antonello
P.s.:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm sure you know from the subject what this is about.
Yes, everything that can be a module is a module, and only things I need are
compiled in. Still I get the above message.
I've tried booting:
vmlinux
gzip vmlinux
gzip -9 vmlinux
Thomas,
Silo has gzip built in. You can just gzip the kernel image, and then
just point silo at the .gz file, and it'll do all the rest for you.
--Adam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm sure you know from the subject what this is about.
Yes, everything that can be a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 November 2003 17:34, [EMAIL PROTECTED] wrote:
Silo has gzip built in. You can just gzip the kernel image, and then
just point silo at the .gz file, and it'll do all the rest for you.
That's what I meant I tried with the
On Tue, Nov 18, 2003 at 05:55:31PM +0100, Thomas Habets wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 November 2003 17:34, [EMAIL PROTECTED] wrote:
Silo has gzip built in. You can just gzip the kernel image, and then
just point silo at the .gz file, and it'll do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 November 2003 18:10, Otto Solares wrote:
you must 'make image' first then use arch/sparc64/boot/image for silo.
You mean sparc, not sparc64? It's a sparcstation 4, not an ultrasparc.
Like I said, I tried arch/sparc/boot/image. I tried
On Tue, Nov 18, 2003 at 07:57:27PM +0100, Thomas Habets wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 November 2003 18:10, Otto Solares wrote:
you must 'make image' first then use arch/sparc64/boot/image for silo.
You mean sparc, not sparc64? It's a sparcstation 4,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 November 2003 20:40, Otto Solares wrote:
these are the steps i do to compile a 2.6 kernel on my ss4:
...
cp arch/sparc/boot/image /boot/vmlinuz
That doesn't work for me. Maybe I'm using too many features. But since I
removed all but
On Tue, Nov 18, 2003 at 07:57:27PM +0100, Thomas Habets wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 November 2003 18:10, Otto Solares wrote:
you must 'make image' first then use arch/sparc64/boot/image for silo.
You mean sparc, not sparc64? It's a sparcstation 4,
14 matches
Mail list logo
