All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edwin Kremer <edwin@cs.uu.nl>
To: ultralinux@vger.kernel.org
Subject: Re: Mach64 problems in UltraPenguin 1.1.9
Date: Tue, 27 Apr 1999 14:14:09 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-92522264407826@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-92522154306389@msgid-missing>

On Tue, Apr 27, 1999 at 09:58:08AM -0400, Steve Dunham wrote:

  : > XFree86-3.3.3.1-5	further FFB fixes, Mach64 fixes (requires the above
  : > 			kernel), Leo/ZX support (including acceleration).
  : 
  : Ther kernel is the latest CVS kernel (numbered 2.2.7).  The card is
  : 2MB, and I am running the server in 16bit mode. The colors come out
  : very wrong, and the cursor is mangled.  (In 8-bit mode, the colors are
  : correct, but the cursor is still mangled. - and, yes, the cursor does
  : look like it has an endian problem.)

I've installed using the Apr 14 tftpboot.img and the same XFree86 on a
brand new Ultra 5 that comes with PGX24 graphics (that is Mach64 but
with 4MB memory) and I'm having similar problems (kernel 2.2.5).

8-bit color is fine, but at 16 or 24 everything looks very purple and
the mouse pointer must be artwork :-)

Until I saw your message, I figured it had something to do with the
new PGX24 graphics.


Best regards,

-- 
Edwin H. Kremer, senior systems- and network administrator.   <edwin@cs.uu.nl>
Dept. of Computer Science,  Utrecht University, The Netherlands  [WHOIS: ehk3]
-------------------- http://www.cs.uu.nl/people/edwin/ -----------------------

  parent reply	other threads:[~1999-04-27 14:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-27 13:58 Mach64 problems in UltraPenguin 1.1.9 Steve Dunham
1999-04-27 14:11 ` David Miller
1999-04-27 14:14 ` Edwin Kremer [this message]
1999-04-27 14:16 ` Jakub Jelinek
1999-04-27 14:17 ` Steve Dunham
1999-04-27 14:54 ` Edwin Kremer

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=marc-linux-ultrasparc-92522264407826@msgid-missing \
    --to=edwin@cs.uu.nl \
    --cc=ultralinux@vger.kernel.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.