From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Justin Mattock" <justinmattock@gmail.com>
Cc: "Adrian Bunk" <bunk@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: completely lost as to what to do, or where to look.
Date: Wed, 21 May 2008 07:48:51 -0700 [thread overview]
Message-ID: <2c0942db0805210748j2429f6f4k4afbd1eebef6d60c@mail.gmail.com> (raw)
In-Reply-To: <dd18b0c30805210733m6d853709xf59331cfed3bfea@mail.gmail.com>
On Wed, May 21, 2008 at 7:33 AM, Justin Mattock <justinmattock@gmail.com> wrote:
>>> Thanks for the help, From what I can remember I noticed this around
>>> 2.6.26-rc1.
[...]
> if I remove
> libdri.so everything starts up as usual so with that in mind since I
> received
> a post about DRI being all F*&^ked up then maybee that is the culprit,
> I think All I really need right now is info on the xserver and the
> kernel.
> What mechanisms are used or files that are responsible for the two too coexist.
> regards;
First, you really need to try the latest kernel from the git
repository (or latest nightly snapshot). The DRI 'mechanisms' you're
asking about were broken in 2.6.26-rc1. They got fixed very, very
recently (past 24 hours). So if you haven't tried the latest kernel
from -git yet, then, respectfully, you're not going to get very far.
Please try the latest kernel first, and then let us know what happens
-- given your description there's a good chance the problem is already
fixed. Also, please report back with the output of `git describe` for
the version you try, so that everyone can see what exact version you
were having trouble with.
next prev parent reply other threads:[~2008-05-21 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 4:10 completely lost as to what to do, or where to look Justin Mattock
2008-05-21 5:34 ` Andrew Morton
2008-05-21 6:51 ` Justin Mattock
2008-05-21 7:59 ` Adrian Bunk
2008-05-21 14:33 ` Justin Mattock
2008-05-21 14:48 ` Ray Lee [this message]
2008-05-21 14:51 ` Oliver Pinter
2008-05-21 17:04 ` Justin Mattock
2008-05-21 20:03 ` Justin Mattock
2008-05-21 20:09 ` Ray Lee
2008-05-21 20:31 ` Lee Revell
2008-05-21 20:40 ` Justin Mattock
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=2c0942db0805210748j2429f6f4k4afbd1eebef6d60c@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=justinmattock@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