All of lore.kernel.org
 help / color / mirror / Atom feed
From: michaelm <admin@www0.org>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc
Date: Mon, 21 Jul 2003 19:35:17 +0300	[thread overview]
Message-ID: <20030721163517.GA597@www0.org> (raw)

.config: http://www0.org/config

That is on a p1 150MMX 32MB PC, specifically an IBM ThinkPad 560E. It
will keep showing "booting the kernel, uncompressing" without going
any further. There will be some disk activity for at least 5-7 minutes
after that on a 5-10 seconds interval period, without change on the
screen. I tried removing framebuffer support or keep it but set
CONFIG_VIDEO_SELECT to 'n', but there is still the same output.

The bzimage is around 919Kb, I tried to make it as modular and small
as it gets to be "usefull" since I suspect this is too old to run 2.5,
but the bzimage still can't be less than 800-810 kilobytes.

-michael

             reply	other threads:[~2003-07-21 16:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-21 16:35 michaelm [this message]
2003-07-21 16:49 ` 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc James Simmons
2003-07-21 17:02 ` Charles Lepple
2003-07-22  0:37   ` Samuel Flory
2003-07-22  0:42     ` Make menuconfig broken Samuel Flory
2003-07-22  7:19       ` Sam Ravnborg
2003-07-22  9:50       ` Roman Zippel
2003-07-22 13:24         ` Vojtech Pavlik
2003-07-22 16:47         ` James Simmons
2003-07-22 18:17           ` Christoph Hellwig
2003-07-22 19:16             ` Sam Ravnborg
2003-07-22 19:35               ` Samuel Flory
2003-07-22 19:46                 ` Charles Lepple
2003-07-22 20:30                 ` James Simmons
2003-07-23 22:53                   ` bill davidsen
2003-07-23 22:48             ` bill davidsen
2003-07-22 18:00         ` Samuel Flory
2003-07-22 19:21           ` michaelm
2003-07-22  2:49     ` 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc Thomas Molina

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=20030721163517.GA597@www0.org \
    --to=admin@www0.org \
    --cc=linux-kernel@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.