From: John McGowan <jmcgowan@inch.com>
To: Dave Airlie <airlied@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: (non) "bug" in 810 (kernel 2.6.9)
Date: Sun, 7 Nov 2004 19:46:43 -0500 (EST) [thread overview]
Message-ID: <20041107193648.H67112@shell.inch.com> (raw)
In-Reply-To: <21d7e99704110714276228ff9b@mail.gmail.com>
On Mon, 8 Nov 2004, Dave Airlie wrote:
> > I had reported a problem with getting a working screen in X with kernel
> > 2.6.9. It is not a bug, but a change.
> >
>
> I can't reproduce this on my system at all, I've got an i815 (slightly
> newer chipset than i810 - maybe something in that...) but I've just
> compiled a kernel with the i810 drm built in and started X in 24-bit
> color on 2.6.9 without incident...
I have been finding more problems. Even with DRM not configured in the
kernel, I have explicitly to kill (NoAccel) all 2D acceleration to
get things working.
I put DRM back in.
I have managed to avoid having to kill ALL 2D acceleration by selectively
disabling parts of it. My xorg.conf now has:
Option "XaaNoScanlineCPUToScreenColorExpandFill" "true"
Option "XaaNoSolidFillRect" "true"
Option "XaaNoScreenToScreenCopy" "true"
Option "XaaNoMono8x8PatternFillRect" "true"
(the first blocked access to the xterm windows ice put up,
the second caused the junk on the screen,
the third was to get text inside Mozilla to scroll and
the last was to get the MonoPattern in the xterm scrollbar)
(perhaps there will be more things I have to disable)
(I found that disabling all individual options worked and so
then enabled then one at a time until a problem arose to find
out what had to be disabled to get things working)
I can then get DRI working in 16 bit mode (actually I can get it
working with just the first two disabling options but put in the
others for general use).
This is for xorg-x11-6.8.1-12 (rpm, fedora core2 development branch,
rebuilt under kernel 2.6.9).
> I'm running Xorg 6.8.0-rc3.... its wierd I've no idea what could be
> causing it ...
Nor I.
Maybe that's why they brought out the 815 chipset :-)
Regards from:
John McGowan | jmcgowan@inch.com [Internet Channel]
| jmcgowan@coin.org [COIN]
--------------+-----------------------------------------------------
prev parent reply other threads:[~2004-11-08 0:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-06 21:23 (non) "bug" in 810 (kernel 2.6.9) John McGowan
2004-11-07 22:27 ` Dave Airlie
2004-11-08 0:46 ` John McGowan [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=20041107193648.H67112@shell.inch.com \
--to=jmcgowan@inch.com \
--cc=airlied@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox