From: "Oliver Pinter" <oliver.pntr@gmail.com>
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 16:51:37 +0200 [thread overview]
Message-ID: <6101e8c40805210751y350e3513ndd48621ac9d2b5d3@mail.gmail.com> (raw)
In-Reply-To: <dd18b0c30805210733m6d853709xf59331cfed3bfea@mail.gmail.com>
you use ati or nvidia binary driver?
On 5/21/08, Justin Mattock <justinmattock@gmail.com> wrote:
> On Wed, May 21, 2008 at 7:59 AM, Adrian Bunk <bunk@kernel.org> wrote:
>> On Wed, May 21, 2008 at 06:51:24AM +0000, Justin Mattock wrote:
>>> On Wed, May 21, 2008 at 5:34 AM, Andrew Morton
>>> <akpm@linux-foundation.org> wrote:
>>> > On Wed, 21 May 2008 04:10:16 +0000 "Justin Mattock"
>>> > <justinmattock@gmail.com> wrote:
>>> >
>>> >> Hello; I'm lost as to where to look in the kernel, as to why I'm
>>> >> receiving a black screen with startx
>>> >> DRI seems to be fine, I'm noticing a sema_init but am not sure if this
>>> >> is the cause of the blackness.
>>> >> any direction as to where I might look would be helpful.
>>> >
>>> > Kernel version?
>>> >
>>> > A git-bisect should get you down the the offending commit within an
>>> > hour or three. http://www.kernel.org/doc/local/git-quick.html has some
>>> > instructions.
>>> >
>>> > But if you're on 2.6.26-rcX, be sure to use the very latest - a pile of
>>> > bad DRI code got reverted recently. This morning, I think.
>>> >
>>>
>>> Thanks for the help, From what I can remember I noticed this around
>>> 2.6.26-rc1. It could be an issue with DRI, but then again it could be
>>> something else. With running some more tests I'm noticing a conflict
>>> with libdri.so, not recognizing the module or the module not
>>> recognizing libdri.so.
>>>...
>>
>> Which X video driver are you using?
>>
>> What exactly is the error message?
>>
>>> regards;
>>> Justin P. Mattock
>>
>> cu
>> Adrian
>>
>> --
>>
>> "Is there not promise of rain?" Ling Tan asked suddenly out
>> of the darkness. There had been need of rain for many days.
>> "Only a promise," Lao Er said.
>> Pearl S. Buck - Dragon Seed
>>
>>
>
> Hello; thanks for the feedback, from previous posts, you know what
> module I'm talking about, So with that in mind I'm going to go
> to the next question: From error messages "there isn't"
> the only leeway or light at the end of the tunnel I see is with
> libdri.so i.g. If I boot the system up with out messing with anything
> I will receive
> a black screen after issueing startx, (from looking at what I see, the
> screen will flash one time then black, it should flash or blink two
> times
> before giving me my lovely picture(wallpaper) then 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;
>
> --
> Justin P. Mattock
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Thanks,
Oliver
next prev parent reply other threads:[~2008-05-21 14:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 4:10 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
2008-05-21 14:51 ` Oliver Pinter [this message]
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=6101e8c40805210751y350e3513ndd48621ac9d2b5d3@mail.gmail.com \
--to=oliver.pntr@gmail.com \
--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
all inboxes | Powered by JetHome®