grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Loading DSDT table using 'acpi' or some memory write command?
Date: Mon, 27 Feb 2017 16:42:32 +0300	[thread overview]
Message-ID: <CAA91j0W++RPBGF3f67=8q7W06RqT8p9ox2mLxeRfBMraNCRhcg@mail.gmail.com> (raw)
In-Reply-To: <229125734.2281203.1488194973248@mail.yahoo.com>

On Mon, Feb 27, 2017 at 2:29 PM, Nando Eva <nando4eva@ymail.com> wrote:
> @Andrei Borzenkov, I've confirmed that any of the following do not alter the
> Win10 DSDT table across numerous Macbooks and my Dell E6540.
>
> acpi dsdt.aml
> acpi --load-only dsdt dsdt.aml
> acpi -2 dsdt.aml
>
> Followed by:
> chainloader /efi/Microsoft/Boot/bootmgfw.efi
>
> Clover has a DSDT override function and using it works on my Dell E6540.
> However it does it by writing to the UEFI firmware volume, which for
> Macbooks, has had one test instance of bricking the system.
>
> Any chance of a simple  'load_dsdt [file]' command that acquires the
> in-memory DSDT table address, checks it's size, then overwrites it with the
> file name specified if it's the same size or smaller?
>

That's more or less what grub tries to do. We cannot really overwrite
ACPI tables because they may be located in read-only memory, but it
attempts to create EBDA and place new RSDP there and update EBDA
address as well as update RSDP pointer in EFI system table. I would
suggest trying to load something else (like Linux) and check whether
it sees new or old table.


  reply	other threads:[~2017-02-27 13:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1736729449.4676062.1487865639993.ref@mail.yahoo.com>
2017-02-23 16:00 ` Loading DSDT table using 'acpi' or some memory write command? Nando Eva
2017-02-24 16:32   ` Andrei Borzenkov
2017-02-27 11:29   ` Nando Eva
2017-02-27 13:42     ` Andrei Borzenkov [this message]
2017-02-27 15:13       ` Vladimir 'phcoder' Serbinenko
2017-02-27 15:31         ` Vladimir 'phcoder' Serbinenko
2017-02-27 15:13     ` Nando Eva
2017-02-27 18:21       ` Nando Eva
2017-03-27 14:12         ` Nando Eva
2017-03-27 16:55           ` Andrei Borzenkov
2017-03-29 17:45           ` Nando Eva
2017-03-30  4:03             ` Andrei Borzenkov
2017-04-01  9:09             ` Andrei Borzenkov
2017-04-01 15:24               ` [PATCH] acpi: add missing efi_call wrapper to acpi command Andrei Borzenkov
2017-04-02  8:27                 ` Vladimir 'phcoder' Serbinenko
2017-04-04 18:18               ` [PATCH] acpi: do not attempt to create EBDA on EFI (was: Loading DSDT table using 'acpi' or some memory write command?) Andrei Borzenkov

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='CAA91j0W++RPBGF3f67=8q7W06RqT8p9ox2mLxeRfBMraNCRhcg@mail.gmail.com' \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).