From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 52121] mgag200 driver does not work properly with Xen in new Intel Server Board
Date: Wed, 23 Jan 2013 04:15:43 +0000 (UTC) [thread overview]
Message-ID: <20130123041543.126C211FE02@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-52121-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=52121
--- Comment #19 from Fernando Chaves <fernando@supergg.com.br> 2013-01-23 04:15:42 ---
I would like to inform that this motherboard uses UEFI.
And, obviously, I'm using Legacy Boot.
This requires some [video] emulation, right?
There is any known issue with Xen about motherboards that uses UEFI? If I
install an UEFI-aware bootloader, like rEFInd or grub-efi, can I boot the
hypervisor?
Big observations made since last message sent:
- BIOS-aware bootloaders (GRUB Legacy, GRUB 2, ISOLINUX, PXELINUX) have a
slower keyboard response AND very slow screen refresh. keystrokes under those
bootloaders have a ~500ms response delay. Also screen refresh is [much] slower,
when entering submenus.
- All behaviors previously mentioned disappears when adding an video card.
Tested with a 10 year-old ATI Rage XL 16MB PCI.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-01-23 4:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-52121-2300@https.bugzilla.kernel.org/>
2013-01-02 14:54 ` [Bug 52121] mgag200 driver does not work properly with Xen in new Intel Server Board bugzilla-daemon
2013-01-02 15:02 ` bugzilla-daemon
2013-01-02 17:14 ` bugzilla-daemon
2013-01-02 17:31 ` bugzilla-daemon
2013-01-02 17:31 ` bugzilla-daemon
2013-01-02 17:32 ` bugzilla-daemon
2013-01-02 18:10 ` bugzilla-daemon
2013-01-02 22:01 ` bugzilla-daemon
2013-01-02 22:01 ` bugzilla-daemon
2013-01-02 22:01 ` bugzilla-daemon
2013-01-02 22:03 ` bugzilla-daemon
2013-01-02 23:31 ` bugzilla-daemon
2013-01-02 23:33 ` bugzilla-daemon
2013-01-02 23:35 ` bugzilla-daemon
2013-01-02 23:36 ` bugzilla-daemon
2013-01-03 18:04 ` bugzilla-daemon
2013-01-03 22:13 ` bugzilla-daemon
2013-01-04 16:00 ` bugzilla-daemon
2013-01-04 16:35 ` bugzilla-daemon
2013-01-04 19:26 ` bugzilla-daemon
2013-01-04 19:34 ` bugzilla-daemon
2013-01-23 4:15 ` bugzilla-daemon [this message]
2013-01-30 2:08 ` bugzilla-daemon
2013-03-05 20:16 ` bugzilla-daemon
2013-03-06 9:15 ` bugzilla-daemon
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=20130123041543.126C211FE02@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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).