public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Schumacher <matt.s@aptalaska.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Tim Bird <tim.bird@am.sony.com>,
	linux-kernel@vger.kernel.org, syslinux@zytor.com
Subject: Re: Possible bug with kernel decompressor.
Date: Thu, 15 Jul 2004 12:40:38 -0800	[thread overview]
Message-ID: <40F6EBC6.7060205@aptalaska.net> (raw)
In-Reply-To: <40F6DD54.5040308@zytor.com>

H. Peter Anvin wrote:
> Matthew Schumacher wrote:
> 
>>
>> I should note that this hardware requires the linux mem/memmap= params 
>> because of the buggy memory detection in the bios so I was required to 
>> use the uppermem command in grub to make it detect the memory and put 
>> the initrd image in the right place.
>>
> 
> Specify, please.
> 
>     -hpa

This is what I am using in grub and it works:

title Linux (2.6.8)
         root (hd0,0)
         uppermem 62464k
         kernel /linux26 memmap=exactmap memmap=640K@0 memmap=63M@1M 
console=ttyS0,9600n8 load_ramdisk=1 root=/dev/root ramdisk_size=32768 
ether=9,0x320,0,0x3c509,eth0 ether=10,0x330,0,0x3c509,eth1 ide0=ali14xx
	initrd /rootfs.gz

This is what I was using in syslinux that broke with "invalid compressed 
format (err=2)" after a improper shutdown (only ramdisk mounted).

  LABEL linux
   KERNEL linux26
   APPEND memmap=exactmap memmap=640K@0 memmap=63M@1M 
console=ttyS0,9600n8 load_ramdisk=1 initrd=rootfs.gz root=/dev/root 
ramdisk_size=32768 ether=9,0x320,0,0x3c509,eth0 
ether=10,0x330,0,0x3c509,eth1 ide0=ali14xx

hope that helps,

schu


  reply	other threads:[~2004-07-15 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14  1:47 Possible bug with kernel decompressor Matthew Schumacher
     [not found] ` <40F5AE63.5010505@am.sony.com>
2004-07-15 17:55   ` Matthew Schumacher
2004-07-15 19:39     ` [syslinux] " H. Peter Anvin
2004-07-15 20:40       ` Matthew Schumacher [this message]
2004-07-15 20:58         ` H. Peter Anvin
2004-07-16 15:57 ` Meelis Roos

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=40F6EBC6.7060205@aptalaska.net \
    --to=matt.s@aptalaska.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syslinux@zytor.com \
    --cc=tim.bird@am.sony.com \
    /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