From: Animeshz <Animeshz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: Tianocore/OVMF
Date: Tue, 09 May 2023 18:50:23 +0200 [thread overview]
Message-ID: <20230509165023.w6ANFmV9R4lvtWQvr23vOI3azirtl89ndT0lHBYyE1A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11243@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
New comment by Animeshz on void-packages repository
https://github.com/void-linux/void-packages/issues/11243#issuecomment-1540508132
Comment:
@hartwork yeah it does work, though I had to introduce some changes, namely,
```diff
diff --git a/grub2_theme_preview/__main__.py b/grub2_theme_preview/__main__.py
index 15c31b1..d40ecaa 100644
--- a/grub2_theme_preview/__main__.py
+++ b/grub2_theme_preview/__main__.py
@@ -525,8 +525,8 @@ def _inner_main(options):
run_command.append('-full-screen')
if is_efi_host:
run_command += [
- '-bios',
- omvf_image_path,
+ '-drive',
+ 'if=pflash,format=raw,file=' + omvf_image_path
]
print('INFO: Please give GRUB a moment to show up in QEMU...')
```
With the old `-bios` option, it was `qemu: could not load PC BIOS '/usr/share/qemu/edk2-x86_64-code.fd'`.
I believe I found this format of specifying uefi image from [this article](https://krinkinmu.github.io/2020/10/11/efi-getting-started.html).
---
Example:
next prev parent reply other threads:[~2023-05-09 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11243@inbox.vuxu.org>
2021-03-22 13:18 ` hartwork
2023-05-09 7:27 ` Animeshz
2023-05-09 9:39 ` hartwork
2023-05-09 16:35 ` Animeshz
2023-05-09 16:38 ` Animeshz
2023-05-09 16:50 ` Animeshz [this message]
2023-05-09 16:51 ` Animeshz
2023-05-09 16:58 ` Animeshz
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=20230509165023.w6ANFmV9R4lvtWQvr23vOI3azirtl89ndT0lHBYyE1A@z \
--to=animeshz@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).