From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Completely disable graphics support in grub2 x86_64-efi
Date: Thu, 26 Aug 2010 14:26:03 +0200 [thread overview]
Message-ID: <AANLkTikdL8J=nrni6Lbh9k86HWO7SNXro7M-6x5Fkbcu@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimQ20Q6_Ag8+kXNa34r+pFW-8jTHZSJYAx5kXsj@mail.gmail.com>
On Thu, Aug 26, 2010 at 2:02 PM, KESHAV P.R. <skodabenz@gmail.com> wrote:
> On Thu, Aug 26, 2010 at 17:17, Vladimir 'phcoder' Serbinenko
> <phcoder@gmail.com> wrote:
>
>> Nicest way would be to implement multiboot for efildr. If I had more time I'd do it myself
>> (and I still might).
> If you plan to implement this I can test it for you in real hardware.
Setting the environment to compile DUET is painful
>
> I have known about coreboot but I do not want to mess up my bios. DUET
> acts like a uefi wrapper for bios. I used it because no "flashing the
> motherboard" was involved. I do not want to try flashing coreboot to
> my motherboard.
>
I wouldn't recommend flashing if you don't have a way to recover the
original firmware.
> grub2 efi works fine in my VirtualBox 3.2.8 PUEL. IN edk1 duet it has
> these graphics problems. It works fine in edk2 duet.
I'm a bit lost. Are there any issues with edk2 duet on real hardware?
> Sorry, but i do not have a qemu image because I am using actual
> hardware. I guess you are asking for qemu image of my DUET USB
> pendrive. Can you provide link to instructions on how to create one?
dd if=/dev/sdX of=- bs=1M | bzip2 > usb.img.bz2
--
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git
next prev parent reply other threads:[~2010-08-26 12:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 14:11 Completely disable graphics support in grub2 x86_64-efi KESHAV P.R.
2010-08-25 1:30 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-08-25 6:44 ` KESHAV P.R.
2010-08-25 9:44 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-08-25 12:13 ` KESHAV P.R.
2010-08-26 8:02 ` KESHAV P.R.
2010-08-26 8:30 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-08-26 10:04 ` KESHAV P.R.
2010-08-26 10:26 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-08-26 11:25 ` KESHAV P.R.
2010-08-26 11:47 ` Vladimir 'phcoder' Serbinenko
2010-08-26 12:02 ` KESHAV P.R.
2010-08-26 12:26 ` Vladimir 'phcoder' Serbinenko [this message]
[not found] ` <AANLkTi=MYggKu3svrGPxCSdRqvmXEPaGS8qW8baSEOVu@mail.gmail.com>
2010-09-08 12:53 ` KESHAV P.R.
-- strict thread matches above, loose matches on Subject: below --
2010-08-21 14:56 KESHAV P.R.
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='AANLkTikdL8J=nrni6Lbh9k86HWO7SNXro7M-6x5Fkbcu@mail.gmail.com' \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.