Wed 05 Dec 2012 09:34:58 AM UTC, original submission:
I'd like to chainload Windows from GRUB2 (2.00-1 from Arch Linux repositories) and am using the following menu entry:
menuentry "Windows 7" --class windows --class os {
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --fs-uuid --no-floppy --set=root 12c9-86c3
set debug=all
chainloader /efi/Microsoft/Boot/bootmgfw.efi
}
Booting this results in the following output. This transcribed from screen, if you require the full output, please say so and I will attach a serial cable to be able to capture it.
script/script.c:50: malloc 0x8d1b4600
script/script.c:50: malloc 0x8d1b45c0
script/script.c:198: cmdline
script/script.c:50: malloc 0x8d1b4560
script/lexer.c:318: token 0 text []
script/script.c:50: malloc 0x8d1b4b00
script/script.c:50: malloc 0x8d1b4900
script/script.c:294: append command
script/script.c:50: malloc 0x8d1b48c0
kern/disk.c:230: Opening `hd0,gpt1'...
disk/efi/efidisk.c:489: opening hd0
disk/efi/efidisk.c:519: m = 0x91301048, last block = 1dcf1fff, block size = 200
disk/efi/efidisk.c:529: opening hd0 succeeded
partmap/gpt.c:90: Reading a valid GPT header
partmap/gpt.c:114: GPT entry 0: start=2048, length=262144
kern/fs.c:55: Detecting fat...
kern/disk.c:230: Opening `hd0,gpt1'...
disk/efi/efidisk.c:489: opening hd0
disk/efi/efidisk.c:519: m = 0x91301058, last block = 1dcf1fff, block size = 200
disk/efi/efidisk.c:529: opening hd0 succeeded
partmap/gpt.c:90: Reading a valid GPT header
partmap/gpt.c:114: GPT entry 0: start=2048, length=262144
/EndEntire
file path: /ACPI(a0341d0,0)/PCI(2,1f)
And then the system just stands there with blinking cursor and doesn't accept any input (this could be because of my USB keyboard, perhaps).
For reference: Windows boots without issue if I select it directly from the EFI boot selection menu.
The hd0 is a Intel Matrix FakeRAID volume.
On help-grub Jordan Uggla said that he remembers "[...] seeing a problem a while ago with Windows' UEFI boot manager failing when there was memory pressure, and FakeRAID often uses a lot of memory, with the additional memory used by grub pushing it over the edge to where Windows' boot manager fails."
|