All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kris Boulez <kris@belbone.be>
To: ultralinux@vger.kernel.org
Subject: Decompression error with silo and new kernel
Date: Wed, 20 May 1998 12:03:59 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-90222356531054@msgid-missing> (raw)

After having installed the latest ultrapenguin release I wanted to
compile a new kernel. I couldn't find any (ultra)sparclinux specific
docs about this, so I used my Intel/PMac knowledge about Linux. I did 
the following

- make kernel as usual
- copy and gzip the resulting vmlinux file (tiens, it is not located somewhere 
  deep down in the arch hierarchy this time) to /boot
- edit /etc/silo.conf to add a new target
- reboot

I get the error "Decompression error: uncompressed image too large - 
		 wouldn't fit into destination"

/etc/silo.conf
timeoutP
partition=3
root=/dev/sda1
image=/boot/vmlinux-2.1.102
        label=linux102
        root=/dev/sda1
        read-only
image=/boot/vmlinux-2.1.99.gz
        label=linux
        root=/dev/sda1
        read-only

# ls -l /boot/vml*
-rwxr-xr-x   1 root     root       987827 May 20 08:31 /boot/vmlinux-2.1.102.gz
-rw-r--r--   1 root     root       938796 May  2 20:56 /boot/vmlinux-2.1.99.gz
-rw-r--r--   1 root     root       966315 May  2 21:20 /boot/vmlinux-smp-2.1.99.gz
lrwxrwxrwx   1 root     root           17 Feb 19 19:53 /boot/vmlinux.gz -> vmlinux-2.1.99.gz


Uncompressing the kernel by hand doesn't solve the problem : "Image too large
to fit in destination"

Kris,
-- 
Kris Boulez				kris@belbone.be

             reply	other threads:[~1998-05-20 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-20 12:03 Kris Boulez [this message]
1998-05-20 12:12 ` Decompression error with silo and new kernel David S. Miller
1998-05-20 12:20 ` Kris Boulez
1998-05-20 12:42 ` Jakub Jelinek
1998-05-20 19:54 ` John Gilmore

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=marc-linux-ultrasparc-90222356531054@msgid-missing \
    --to=kris@belbone.be \
    --cc=ultralinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.