Hmm, I guess that would be bad.
>Can you try one of a) LILO b) a fixed version of grub c) this patch ?
I tried LILO and the problem did indeed go away when using that. I
guess I'll stick with LILO until Linux or grub (whichever is broken)
is fixed. There is just something appealing about a proper boot
console on a PC...
BIOS-provided physical RAM map:
BIOS-e820: 000000000009f800 @ 0000000000000000 (usable)
BIOS-e820: 0000000000000800 @ 000000000009f800 (reserved)
BIOS-e820: 0000000000019800 @ 00000000000e6800 (reserved)
BIOS-e820: 0000000013ef0000 @ 0000000000100000 (usable)
BIOS-e820: 000000000000fc00 @ 0000000013ff0000 (ACPI data)
BIOS-e820: 0000000000000400 @ 0000000013fffc00 (ACPI NVS)
BIOS-e820: 0000000000080000 @ 00000000fff80000 (reserved)
On node 0 totalpages: 81904
zone(0): 4096 pages.
zone(1): 77808 pages.
zone(2): 0 pages.
Kernel command line: auto BOOT_IMAGE=Linux ro root=301
-
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/