> Do you have the failed DSDT table dumped? Even there's recent change around
> NVSA, but looks that's different.
Here is the DSDT before any of my changes: https://0paste.com/158902
> Do you see any ways to preempt this entire class of errors (Windows
> unhappy with ACPI tables) within coreboot
Hi Raul,
Raul Rangel wrote:
> With all that I was finally able to boot into Windows!
Thank you very much for documenting your findings and much of your method!
Do you see any ways to preempt this entire class of errors (Windows
unhappy with ACPI tables) within coreboot in a systematic manner?
Y
Do you have the failed DSDT table dumped? Even there's recent change around
NVSA, but looks that's different.
Raul Rangel 于2021年1月21日周四 上午4:24写道：
> Over the weekend I had the realization that SMI logging was enabled
> and interfering with WinDbg. Once I flashed a non-serial firmware
> WinDbg bec
Over the weekend I had the realization that SMI logging was enabled
and interfering with WinDbg. Once I flashed a non-serial firmware
WinDbg became a lot more stable and I was able to reliably attach to
the boot loader debugger i.e., `/bootdebug {default}`. The OS debugger
(`/debug {default} on`) w
Forgot to add that to find out what the cause is the easiest way is
probably having the installed image configured in a way that it'll write
full kernel memory dumps to disk and then use !analyze -v in WinDbg on
that generated kernel dump. At least that's what I remember from more
than 1.5 year
Hi Raul,
The installer behaves differently than the installed Windows OS, so I'd
only try on an already installed OS at first. If you need to do some
in-depth debugging, I'd also recommend using a checked build that has
debug symbols available. Beware that the installed version is very picky
> Stoney has the same issue, pretty sure it's related to a memory address
range being incorrectly marked or something similar (based on the DWORD
output of the BSOD), but never bothered to troubleshoot
How did you come to that conclusion?
> Highly possible you don't need to connect live sessions
Highly possible you don't need to connect live sessions using windbg, you
can analysis the generated dump file to simply open with windbg.
Raul Rangel 于2021年1月14日周四 上午6:21写道：
> I'm trying to boot the Windows 10 Installer on a picasso based device
> using coreboot + tianocore. I keep getting a B
Stoney has the same issue, pretty sure it's related to a memory
address range being incorrectly marked or something similar (based on
the DWORD output of the BSOD), but never bothered to troubleshoot
On Wed, Jan 13, 2021 at 4:21 PM Raul Rangel wrote:
>
> I'm trying to boot the Windows 10 Installe
9 matches
Mail list logo
