Chainloading Windows 7 EFI Bootloader

[Florian Wagner]

Hi,

please keep me CC'd as I'm not subscribed to the list!

I'm currently setting up a new system supporting EFI-boot with Linux
and Windows 7 dual-boot. I'd like to chainload Windows from GRUB2
(2.00-1 from Arch Linux repositories) as this is much more convenient
than using the EFI boot menu. The menu entry is set up like follows
with inspiration from the Arch wiki:

  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.

Might this have anything to do with hd0 being a Intel Matrix RAID
volume? Perhaps the EFI equivalent of the OptionROM gets lost somewhere
during the chainloading process?

From lspci:

  00:1f.2 RAID bus controller: Intel Corporation 82801 SATA Controller [RAID 
mode] (rev 04)
        Subsystem: Giga-byte Technology Device b005
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 40
        Region 0: I/O ports at f0d0 [size=8]
        Region 1: I/O ports at f0c0 [size=4]
        Region 2: I/O ports at f0b0 [size=8]
        Region 3: I/O ports at f0a0 [size=4]
        Region 4: I/O ports at f060 [size=32]
        Region 5: Memory at f7c26000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0f00c  Data: 4191
        Capabilities: [70] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot+,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
        Capabilities: [b0] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-
        Kernel driver in use: ahci

Thanks and regards
Florian Wagner

signature.asc
Description: PGP signature