From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: caslivkoff@yahoo.com
Cc: xpert@XFree86.Org, parisc-linux@lists.parisc-linux.org
Subject: Re: [Xpert][parisc-linux] white is blue
Date: Sat, 18 Aug 2001 21:29:13 +0200 [thread overview]
Message-ID: <3B7EC209.87A159D2@iiic.ethz.ch> (raw)
In-Reply-To: 3B7EBE4A.B122B1FA@yahoo.com
caslivkoff@yahoo.com wrote:
> Michel Dänzer wrote:
> >
> > caslivkoff@yahoo.com wrote:
> >
> > > I posted this to the parisc-linux mailing list, but so far, no
> > > responses. Can anyone offer a suggestion? The fbdev driver is "supposed"
> > > to work with the graphics in the 712/60. I also tried this on a second
> > > 712 with the same behavior. What's wierd is that other colors appear OK.
> > > I'm attaching the XFree86.0.log.
> > >
> > > -----------------------------------------------------
> > >
> > > I just loaded the ISO on a 712/60 and setup XFree86 to use the fbdev
> > > driver. It seems to be OK, with the exception that "white" is "blue". If
> > > I xwd the root window dump and examine it on another X display, it
> > > looks fine.
> >
> > The fbdev driver uses the framebuffer device to set the colormap, which
> > works in general (at least for me ;), so I suspect there is a problem with
> > the framebuffer device.
>
> That's what I though too, but I've tried this on 2 different 712's and
> have the same behavior.
But I assume you use the same framebuffer device on both? (Note that when I
say framebuffer device, I refer to the Linux kernel driver)
> What is strange is that the framebuffer can display white text with no
> problem on the console (the default cursor is white). Also, under X,
> specifying #fefefe shows up as "almost white".
There are no known problems with the XFree86 fbdev colormap handling, but
maybe you have found one... :)
> Any other ideas? I thought that possibly the rgb.txt was not getting
> loaded, but I'm fairly certain that it is.
You can easily check with grep -i rgb /var/log/XFree86.0.log .
--
Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \ XFree86 and DRI project member
next prev parent reply other threads:[~2001-08-18 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B7DE89A.5A665A16@yahoo.com>
[not found] ` <3B7E9021.AA279076@iiic.ethz.ch>
2001-08-18 19:13 ` [Xpert][parisc-linux] white is blue caslivkoff
2001-08-18 19:29 ` Michel Dänzer [this message]
2001-08-18 19:46 ` Helge Deller
2001-08-21 7:09 ` Grant Grundler
2001-08-18 19:55 ` Dr Andrew C Aitchison
2001-08-18 23:42 ` caslivkoff
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=3B7EC209.87A159D2@iiic.ethz.ch \
--to=michdaen@iiic.ethz.ch \
--cc=caslivkoff@yahoo.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=xpert@XFree86.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