Re: Possible bug with kernel decompressor.
From: Matthew Schumacher (matt.s_at_aptalaska.net)
Date: 07/15/04
- Previous message: Adrian Bunk: "[patch] remove bouncing email addresses of Marko Kiiskila"
- In reply to: H. Peter Anvin: "Re: [syslinux] Re: Possible bug with kernel decompressor."
- Next in thread: H. Peter Anvin: "Re: Possible bug with kernel decompressor."
- Reply: H. Peter Anvin: "Re: Possible bug with kernel decompressor."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 15 Jul 2004 12:40:38 -0800 To: "H. Peter Anvin" <hpa@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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Adrian Bunk: "[patch] remove bouncing email addresses of Marko Kiiskila"
- In reply to: H. Peter Anvin: "Re: [syslinux] Re: Possible bug with kernel decompressor."
- Next in thread: H. Peter Anvin: "Re: Possible bug with kernel decompressor."
- Reply: H. Peter Anvin: "Re: Possible bug with kernel decompressor."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]