Hello Alan, hello linux-kernel,
> > No, your code is all right, I have found the cause of this behaviour:
> > it's because I boot with GRUB and not with LILO. So, you might say "What
> > the hell does the bootloader matter", and this is what I also thought in
> > the first hours, until I noticed that GRUB was adding a "mem=524288K"
> > entry to my
>
> This is a known problem with old versions of GRUB. Up to date versions of
> grub shouldnt be passing mem= lines.
So I'll try to get a newer GRUB, the --no-mem-option suggestion from Jan
Niehusmann didn't work for me (using GRUB version 0.5.96.1). But,
nevertheless, shouldn't this be fixed (not reserving ACPI memory when a mem=
commandline is passed)? Or, at least documented somewhere?
Greetings,
Andreas
-
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/
This archive was generated by hypermail 2b29 : Fri Aug 31 2001 - 21:00:34 EST