From: Matt Mackall <mpm@selenic.com>
To: Alexander Simon <Al.Simon@t-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Changing kernel uncompressing address
Date: Mon, 22 Mar 2004 12:38:36 -0600 [thread overview]
Message-ID: <20040322183836.GB8366@waste.org> (raw)
In-Reply-To: <405D73D7.70905@t-online.de>
On Sun, Mar 21, 2004 at 11:52:07AM +0100, Alexander Simon wrote:
> Hi!
>
> I have an old Toshiba Satellie Pro Laptop with broken RAM.
> I thought it could be no problem getting it to work with the BadRAM patch.
> But first RAM Errors occur at 2M and last until 32M
> Unfornately, the RAM Chips are on board, so no chance of replacing them.
> When I try to load a kernel image from diskette, it unpacks the kernel
> image without errors. But when it tries to start that kernel it stops or
> reboots.
> If I keep the kernel very very small, it starts, but I would have to
> exclude TCP/IP code, causing the system unusable.
>
> After studying arch/i386/boot/compressed/head.S and misc.c of 2.4.24 for
> a long time, i found out that the kernel is uncompressed to 0x100000.
> Stupidly, I'm not familiar with assembler code. So I just changed the
> 0x100000 to 0xF00000 (should be 16M?!? memtest86 reported the range
> 15M-18M OK, however...) in line 77 in head.S and line 309 in misc.c.
> Of couse it did NOT work :[.
> I would need to high loaded kernel anyway, again because of TCP/IP.
That's part of it, you'll also need to tweak the boot-time page tables
and whatnot to cover all of the space you need.
--
Matt Mackall : http://www.selenic.com : Linux development and consulting
prev parent reply other threads:[~2004-03-22 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 10:52 Changing kernel uncompressing address Alexander Simon
2004-03-22 18:38 ` Matt Mackall [this message]
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=20040322183836.GB8366@waste.org \
--to=mpm@selenic.com \
--cc=Al.Simon@t-online.de \
--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.