lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 21 May 2008 14:33:57 +0000
From:	"Justin Mattock" <justinmattock@...il.com>
To:	"Adrian Bunk" <bunk@...nel.org>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: completely lost as to what to do, or where to look.

On Wed, May 21, 2008 at 7:59 AM, Adrian Bunk <bunk@...nel.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@...ux-foundation.org> wrote:
>> > On Wed, 21 May 2008 04:10:16 +0000 "Justin Mattock" <justinmattock@...il.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ