From: Daniel Lyons <fusion@storytotell.org>
To: 9fans <9fans@9fans.net>
Subject: [9fans] Parallels Vesa driver question
Date: Sun, 2 Aug 2009 03:36:48 -0600 [thread overview]
Message-ID: <22352E83-0CE0-406D-8D01-D3CC416EAE81@storytotell.org> (raw)
Hi,
I installed Plan 9 under Parallels 3 back in November of last year and
it worked without a hitch. I tried to install another copy tonight and
the bitmapped display isn't working in the new one, I just get a pure
black screen after any aux/vga command that it thinks will succeed. I
found I can reproduce that behavior by building and running a new
kernel in the old install. Any ideas what has happened since November
in the kernel with respect to Vesa and Parallels? I'd be more than
happy to debug this issue if I could get a little guidance. I didn't
see anything in the archives about this problem. Alternatively, does
anyone know if Parallels 4 works with a current kernel? If so I'll
probably just upgrade to that; I've been holding off for a good reason
to.
Thanks,
—
Daniel Lyons
next reply other threads:[~2009-08-02 9:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 9:36 Daniel Lyons [this message]
2009-08-02 17:06 ` erik quanstrom
2009-08-02 19:14 ` Daniel Lyons
2009-08-02 20:41 ` Steve Simon
2009-08-02 21:41 ` erik quanstrom
2009-08-03 6:57 ` Daniel Lyons
2009-08-03 9:26 ` Richard Miller
2009-08-03 11:20 ` erik quanstrom
2009-08-04 2:36 ` geoff
2009-08-04 3:12 ` David Leimbach
2009-08-04 7:18 ` Daniel Lyons
2009-08-04 7:25 ` Bakul Shah
2009-08-04 12:47 ` David Leimbach
2009-08-04 15:20 ` Bakul Shah
2009-08-04 15:25 ` David Leimbach
2009-08-04 16:24 ` Bakul Shah
2009-08-04 17:46 ` erik quanstrom
2009-08-12 6:18 ` Bakul Shah
2009-08-04 8:54 ` Daniel Lyons
2009-08-04 9:04 ` erik quanstrom
2009-08-03 16:30 ` ron minnich
2009-08-04 7:15 ` Daniel Lyons
2009-08-04 15:26 ` ron minnich
2009-08-03 9:13 ` Balwinder S Dheeman
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=22352E83-0CE0-406D-8D01-D3CC416EAE81@storytotell.org \
--to=fusion@storytotell.org \
--cc=9fans@9fans.net \
/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).