Declan Moriarty wrote:
> It's a permissions thing, or perhaps a video one. Are you loading
> irrelevant/conflicting video modules?
Kernel is non-modular, and the same one as was running LFS before
(where X was fine); Xorg is only compiled with support for i810, which
seems to be the right driver for my onboard Intel graphics (it's the
only one that lets me run Xorg -configure, and Ubuntu agreed that
that's what it should be).

> I would check : loopback networking;
How does one check loopback networking?

> permissions on /etc/X11; 


I don't
> like the compiler flags, but then it's a favourite target of those who
> know little.
And I just found I told a lie about the compiler flags I used - I was
quoting the ones from my environment (which I actually unset while
building Xorg). The ones from host.def are more conservative (and, I
think, the defaults there):

-O2 -fno-strength-reduce -fno-strict-aliasing -march=pentium4
 
> Try as user
> 
> startx > somefile 2>&1  && init 3
&& init 3 didn't recover me - I missed the redirect when I scanned
this mail before.. I'll try the redirect and || momentarily and post
my results (I think || has more chance of recovering than && by the
way: it will execute init if startx crashes, whereas && will only run
init if Xorg exits with no error).

> /var/log/Xorg.0.log and/or stdout (on the console you started X from)
Xorg.0.log shows nothing (as reported in my original post, BTW). I'll
look at the STDOUT next attempt. :)

Stephen Liu wrote:
>As 'root' please try;
># chmod u+s /usr/X11R6/bin/Xorg
As I mentioned in the original post, Xorg is already suid root. This
is necesary for Xorg to run as user in the first place - without this,
it complains about not being able to move the log, and startx crashes
before Xorg is launched. In my situation, Xorg lanches (and I get to
an empty environment with my cursor in the middle), but then promptly
crashes.

-- 
Lennon Victor Cook
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to