From: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] NT4 white mouse pointer using Cirrus 5446 driver under 0.9.1
Date: Thu, 22 May 2008 10:28:50 +0100 [thread overview]
Message-ID: <48353CD2.20508@siriusit.co.uk> (raw)
In-Reply-To: <e71790db0805211811t5a0c7d15r579a5ad61d0cd628@mail.gmail.com>
Carlos A. M. dos Santos wrote:
>> Can anyone explain why this is happening? I can provide some debug
>> information if people can point me in the right direction.
>
> It seems that you are running out of colormap entries. Try to use 16
> bits per pixel.
Hi Carlos,
Thanks for the hint. I've tried 8bpp and 16bpp, but it doesn't make a
difference at all :(
After some experimentation here, I'm wondering if it is some kind of
quirk within the NT4 driver related to alignment issues within the qemu
code. The server for this qemu instance is running 32-bit Debian etch
with 0.9.1, and I always see a white pointer whenever I connect.
Interestingly though, I temporarily mapped the NT4 partition to my local
laptop which is 64-bit Debian lenny with 0.9.1, and the mouse pointer
appears correctly! So it appears that this could be a 32/64-bit related
issue?
On another note, I have now managed to get the mouse pointer appearing
correctly on the original 32-bit server by using the ReactOS video
drivers here: http://www.bearwindows.boot-land.net/vbemp.htm instead of
the Cirrus drivers. Thus I have a found a cure that works for me, but it
looks like I am not the only person to experience this issue:
http://www.debian-administration.org/users/ajt/weblog/115.
ATB,
Mark.
--
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063
prev parent reply other threads:[~2008-05-22 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 14:27 [Qemu-devel] NT4 white mouse pointer using Cirrus 5446 driver under 0.9.1 Mark Cave-Ayland
2008-05-22 1:11 ` Carlos A. M. dos Santos
2008-05-22 9:28 ` Mark Cave-Ayland [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=48353CD2.20508@siriusit.co.uk \
--to=mark.cave-ayland@siriusit.co.uk \
--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 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).