From: Jean-Michel POURE <jm@poure.com>
To: Hetz Ben Hamo <hetz@witch.dyndns.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Cirrusvga framebuffer mode?
Date: Sun, 13 Jun 2004 14:11:31 +0200 [thread overview]
Message-ID: <200406131411.31669.jm@poure.com> (raw)
In-Reply-To: <40CC3C85.6080603@witch.dyndns.org>
Le dimanche 13 Juin 2004 13:37, Hetz Ben Hamo a écrit :
> I belive this is a Mandrake 10 installation problem and not QEMU's
> problem, since the Mandrake installation doesn't really check for Cirrus
> Logic stuff probably (no problem with Fedora core 2)
Dear Hetz,
During Stage 1, Fedora boots in text mode. Then, Fedora Core 2 switches to
graphical mode when reaching stage 2. In the case of Fedora, I agree that
this works for both "-pci" and "-pci -cirrusvga".
On the converse, SuSE 9.0 and Mandrake 10 are supposed to install in
graphical mode from stage 1 (probably in framebuffer mode, although I did not
read the source code of the installers). And graphical mode does not work for
"-pci -cirrusvga" mode.
Here are some screenshots:
1) Mandrake 10
qemu -cdrom Mandrakelinux10.0-CD1.i586.iso -boot d -m 128 -pci -cirrusvga
Screenshot : http://www.poure.com/screenshots/qemu_temp_2.png
qemu -cdrom Mandrakelinux10.0-CD1.i586.iso -boot d -m 128 -pci
Screenshot : http://www.poure.com/screenshots/qemu_temp_1.png
2) SuSE 9.1
qemu -cdrom SuSE-9.1-iso.disk1 -boot d -m 128 -pci -cirrusvga
Screenshot : http://www.poure.com/screenshots/qemu_temp_3.png
qemu -cdrom SuSE-9.1-iso.disk1 -boot d -m 128 -pci
Screenshot : http://www.poure.com/screenshots/qemu_temp_4.png
It seems like Cirrus SVGA framebuffer mode is not detected well.
Kindest regards,
Jean-Michel
prev parent reply other threads:[~2004-06-13 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-13 9:51 [Qemu-devel] Cirrusvga framebuffer mode? Jean-Michel POURE
2004-06-13 11:37 ` Hetz Ben Hamo
2004-06-13 12:11 ` Jean-Michel POURE [this message]
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=200406131411.31669.jm@poure.com \
--to=jm@poure.com \
--cc=hetz@witch.dyndns.org \
--cc=qemu-devel@nongnu.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.