After running a SMP 2.4.21 kernel on my Dell Dimension 8300, the BIOS
thinks that the amount of memory has changed. When the box is
rebooted, I get the following message at the end of BIOS
initialization:
The amount of system memory has changed.
Alert! OS Install Mode enabled. Amount of available memory limited to 256MB.
At this point the bootup hangs, waiting for someone to press F1
(resume) or F2 (setup). Any idea what's triggering this behaviour, and
what I can do to squash it? This issue doesn't occur when using a UP
kernel (basically identical, except for SMP/ACPI being disabled).
Thanx!
I still haven't figured this one out, but for whatever it's worth
2.5.72 doesn't appear to trigger the problem. Guess I won't worry
about it too much. ;-)
On Sun, Jun 15, 2003 at 09:10:59PM -0500, Greg Norris wrote:
> After running a SMP 2.4.21 kernel on my Dell Dimension 8300, the BIOS
> thinks that the amount of memory has changed. When the box is
> rebooted, I get the following message at the end of BIOS
> initialization:
>
> The amount of system memory has changed.
> Alert! OS Install Mode enabled. Amount of available memory limited to 256MB.
>
> At this point the bootup hangs, waiting for someone to press F1
> (resume) or F2 (setup). Any idea what's triggering this behaviour, and
> what I can do to squash it? This issue doesn't occur when using a UP
> kernel (basically identical, except for SMP/ACPI being disabled).
>
> Thanx!
On Fri, 2003-06-20 at 03:24, Greg Norris wrote:
> I still haven't figured this one out, but for whatever it's worth
> 2.5.72 doesn't appear to trigger the problem. Guess I won't worry
> about it too much. ;-)
>
> On Sun, Jun 15, 2003 at 09:10:59PM -0500, Greg Norris wrote:
> > After running a SMP 2.4.21 kernel on my Dell Dimension 8300, the BIOS
> > thinks that the amount of memory has changed. When the box is
> > rebooted, I get the following message at the end of BIOS
> > initialization:
> >
> > The amount of system memory has changed.
> > Alert! OS Install Mode enabled. Amount of available memory limited to 256MB.
> >
This is something related to/triggered by the ACPI code, booting with
acpi=off makes it go away (2.4.21).
--matti
On Fri, Jun 20, 2003 at 09:01:25AM +0200, Matti Rendahl wrote:
> This is something related to/triggered by the ACPI code, booting with
> acpi=off makes it go away (2.4.21).
I was starting to suspect ACPI, but hadn't yet verified this.
Unfortunately I need ACPI in order to enable hyperthreading, so I guess
it's time to check out the current patches. Thanx for the info!
On Fri, Jun 20, 2003 at 04:54:37PM -0500, Greg Norris wrote:
> On Fri, Jun 20, 2003 at 09:01:25AM +0200, Matti Rendahl wrote:
> > This is something related to/triggered by the ACPI code, booting with
> > acpi=off makes it go away (2.4.21).
>
> I was starting to suspect ACPI, but hadn't yet verified this.
> Unfortunately I need ACPI in order to enable hyperthreading, so I guess
> it's time to check out the current patches. Thanx for the info!
The ACPI update does indeed squash this problem. THANX!!!
On Fri, Jun 20, 2003 at 06:48:25PM -0500, Greg Norris wrote:
> The ACPI update does indeed squash this problem. THANX!!!
Unfortunately I was mistaken... :-( I had enabled CONFIG_ACPI_HT_ONLY,
and wasn't aware of the requirement for the "acpismp=force" kernel
parameter.