wimboot using grub2 on EFI
|
2018-04-09, 05:55
Post: #7
|
|||
|
|||
RE: wimboot using grub2 on EFI
(2018-04-09 02:06)sherpya Wrote: I've tested it and it works, looks like you need to wait the second ctrl+b prompt, maybe after the first one ipxe opens the snp device That is one solution that works without understanding why .. This is what I wrote: Quote:make sure you have at least one open network interface for iPXE to bind to when you run boot Now to explain why the other solution works ... The "first" Ctrl-B is before autoboot have run, which means before ifopen/dhcp. If autoboot fails to find information for booting, such as tftp server and filename, then it will present you with the "second" Ctrl-B. And in that case ifopen has already run. So to summarize: * Enter shell and run ifopen for it to work in both cases (it still requires the presence of a NIC) * If you have a DHCP server that gives out boot information there will not be a second Ctrl-B Use GitHub Discussions VRAM bin |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
wimboot using grub2 on EFI - sherpya - 2017-12-25, 22:07
RE: wimboot using grub2 on EFI - sherpya - 2017-12-28, 20:03
RE: wimboot using grub2 on EFI - Deoptim - 2018-02-18, 22:26
RE: wimboot using grub2 on EFI - sherpya - 2018-03-27, 02:50
RE: wimboot using grub2 on EFI - NiKiZe - 2018-03-28, 19:43
RE: wimboot using grub2 on EFI - sherpya - 2018-04-09, 02:06
RE: wimboot using grub2 on EFI - NiKiZe - 2018-04-09 05:55
RE: wimboot using grub2 on EFI - sherpya - 2019-05-01, 12:35
RE: wimboot using grub2 on EFI - NiKiZe - 2019-05-01, 17:57
RE: wimboot using grub2 on EFI - sherpya - 2019-05-01, 20:26
|
User(s) browsing this thread: 2 Guest(s)