From: "Steve Kieu" <haiquy@yahoo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: kernel <linux-kernel@vger.kernel.org>
Subject: Re: Status of DRI modules for i810 with > 2.4.19-pre6
Date: Mon, 15 Jul 2002 21:11:09 +1000 (EST) [thread overview]
Message-ID: <20020715111109.48830.qmail@web10406.mail.yahoo.com> (raw)
In-Reply-To: <1026693715.13886.97.camel@irongate.swansea.linux.org.uk>
>
> Duplicate the problem with a 2.4.19-rc1-ac3 kernel
> (not one with random
> pre-empt patches). Then get a traceback. Also be
> sure to use XFree86 4.2
> or later
>
The OOPS nolonger happened BUT it is useless as
XFree86-4.2.0 has problem with dri for i810; in the
XFree86 log file it says Direct rendering is enabled.
But run glxinfo shows that no other software can use
it!. I have searched and found a lot users have the
same thing. although I am quite sure that I installed
it properly (rm all old libGl etc...)
Go back to XFree86-4.1.0 compile 2.4.19-rc1-ac3 with
new dri modules; the oop also disappear. (That oops I
reported last time is with the old dri modules); I
thought wow it should be fine, but still no luck. run
glxinfo is fine; but run real application like
bzflags; bzflags can not run, it hang forever. No
OOPS, nothing, everything seems to be normal. Have to
killall -9 bzflag (15 doesn't stop it). Not sure what
caused this; Go back to use kernel 2.4.18-ck4
everything is in order :-)
Regards,
=====
Steve Kieu
http://www.sold.com.au - SOLD.com.au
- Find yourself a bargain!
next prev parent reply other threads:[~2002-07-15 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 22:09 Steve Kieu
2002-07-15 0:41 ` Alan Cox
2002-07-15 6:57 ` Steve Kieu
2002-07-15 13:28 ` Alan Cox
2002-07-15 11:11 ` Steve Kieu [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-13 21:02 Steve Kieu
2002-07-14 1:45 ` Alan Cox
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=20020715111109.48830.qmail@web10406.mail.yahoo.com \
--to=haiquy@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®