All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Young <solid@youngdev.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] strange graphics message
Date: Sat, 06 Oct 2007 12:24:51 -0400	[thread overview]
Message-ID: <4707B6D3.5010606@youngdev.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

does anyone know what this screen means?

     =======================|  DirectFB 1.0.0  |=======================
          (c) 2001-2007  The DirectFB Organization (directfb.org)
          (c) 2000-2004  Convergence (integrated media) GmbH
        ------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2007-09-07 00:13)
(*) Direct/Memcpy: Using Generic 64bit memcpy()

     =======================|  DirectFB 1.0.0  |=======================
          (c) 2001-2007  The DirectFB Organization (directfb.org)
          (c) 2000-2004  Convergence (integrated media) GmbH
        ------------------------------------------------------------


The host os is running the NVidia proprietary driver on AMD64.  A while
ago (maybe a year or so) I ran this same OS install disk under qemu and
it ran.  But on my AMD64/NVidia box, I am getting this bizarre message
and the console does not come back.  I have to ctrl+c to escape out.
What is the problem/solution here?
- --

Cheers,
Matt Young
solid@youngdev.net
GPG Public Key: http://youngdev.net/?page=gpg
GPG Fingerprint: 980C 032B 272D 848D B2F7 ED85 38B3 EDCB 3C5D 7106
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFHB7bTOLPtyzxdcQYRAqa9AKCKVJqmolcENmmkG57ksUg8v4ftogCgli42
Ci4FfuJ+D8buK0IW4Sjum5M=
=vLYG
-----END PGP SIGNATURE-----

                 reply	other threads:[~2007-10-06 16:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4707B6D3.5010606@youngdev.net \
    --to=solid@youngdev.net \
    --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.