From: Pavel Machek <pavel@suse.cz>
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: Robert Woerle Paceblade/Support <robert@paceblade.com>,
"Grover, Andrew" <andrew.grover@intel.com>,
ACPI mailing list <acpi-devel@lists.sourceforge.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] Re: mem= option for broken bioses
Date: Thu, 27 Feb 2003 17:12:04 +0100 [thread overview]
Message-ID: <20030227161203.GF12434@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20030227154922.GY13404@poup.poupinou.org>
Hi!
> > > >>OK, looks reasonable. Can you also gen up a patch documenting this in
> > > >>kernel-parameters.txt?
> > > >>
> > > >>
> > > >
> > > >You can, assuming you took the patch ;-).
> > > >
> > > >
> > > well how can i find the correct value`s to put in ??
> >
> > Well, similar method to how you use mem=123@456 parameters. You just
> > guess them. [Given kernel messages, it is actually quite easy.]
> >
>
> If I understand you, you then just have to mem= with the correct
> value reported via, for example:
>
> ducrot@novae:~$ dmesg | grep 'ACPI data'
> BIOS-e820: 000000000fef0000 - 000000000feff000 (ACPI data)
Well, for you bios map is okay and you don't need mem= parameter.
> But big problem though. It is really really strange that the
> BIOS mainteners have broken e820 call, are you sure you have
> enabled acpi in BIOS, and/or power management ?
Yes, what I needed was bios update. If you downgrade your bios you can
provoke same bug I saw.
--
Horseback riding is like software...
...vgf orggre jura vgf serr.
next prev parent reply other threads:[~2003-02-27 16:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 22:39 Grover, Andrew
2003-02-26 22:44 ` Pavel Machek
2003-02-27 14:27 ` [ACPI] " Robert Woerle Paceblade/Support
2003-02-27 15:19 ` Pavel Machek
2003-02-27 15:49 ` Ducrot Bruno
2003-02-27 16:12 ` Pavel Machek [this message]
2003-02-27 15:53 ` Robert Woerle Paceblade/Support
2003-02-27 16:16 ` Pavel Machek
2003-02-27 23:48 ` H. Peter Anvin
[not found] ` <b3m840_5e4_1@cesium.transmeta.com>
2003-03-04 13:18 ` Pavel Machek
2003-03-04 14:21 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030227161203.GF12434@atrey.karlin.mff.cuni.cz \
--to=pavel@suse.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=andrew.grover@intel.com \
--cc=ducrot@poupinou.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert@paceblade.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®