On Sun, Feb 20, 2005 at 10:52:12AM +0100, David Härdeman wrote:
> e820 map:
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
> BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000ce000 - 00000000000d0000 (reserved)
> BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000000f6f0000 (usable)
> BIOS-e820: 000000000f6f0000 - 000000000f700000 (reserved)
> BIOS-e820: 000000000f700000 - 000000003f6f0000 (usable)
> BIOS-e820: 000000003f6f0000 - 000000003f6f8000 (ACPI data)
> BIOS-e820: 000000003f6f8000 - 000000003f6fa000 (ACPI NVS)
> BIOS-e820: 000000003f700000 - 0000000040000000 (reserved)
> BIOS-e820: 00000000ff800000 - 0000000100000000 (reserved)
> 118MB HIGHMEM available.
> 896MB LOWMEM available.
>
> Is the hole between 0x36f6fa000 and 0x3f700000?
Looks like it.
> And what would be the proper way of fixing it (assuming that IBM won't
> issue a fixed BIOS)?
Try passing:
reserve=0x3f6fa000,0x6000
to the kernel.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
