On Sat, 2011-12-31 at 14:59 -0200, Claudio Roberto França Pereira wrote:
> On Sat, Dec 31, 2011 at 13:53, Jeff Cranmer <jeff@lotussevencars.com> wrote:
> > I'm attempting to bring up a new system.  Processor is AMD Phenom 1055,
> > running on a Sabertooth 990FX motherboard.  Graphics card is an NVIDIA
> > GEForce GTX550Ti.
> >
> > If I start X with twm, the xserver connection is made, and TWM comes up
> > correctly with three Xterm windows.
> >
> > I note that I get two errors reported,
> > (EE) NVIDIA: Failed to load module "dri2" (Module does not exist, 0)
> > /etc/X11/xinit/xinitrc: line 62: xclock: command not found
> 
> This is normal behavior. Don't know why, but nVidia drivers doesn't
> use the dri2 module, I think it has it's own implementation or
> something, you can safely ignore that, even if your 20-nvidia.conf
> disables (or tries to) dri2.
> The xclock error is also ok, you probably have twm emerged, but not
> xclock. The default xinitrc (in /etc/X11/xinit/xinitrc) tries to run
> twm, 3 xterms and xclock.
> 
OK, thanks - that explains that problem.
> >
> > The first error is definitely on startup, but the latter could have
> > appeared on exit.
> >
> > I have a file 20-nvidia.conf in the /usr/share/X11/xorg.conf.d directory
> > with the following information
> >
> > Section "Device"
> >  Identifier "Device0"
> >  Driver "nvidia"
> >  VendorName "NVIDIA Corporation"
> >  BoardName "GeForce GTX550 Ti"
> >  BusID "PCI:5:0:0"
> >  Screen 0
> > EndSection
> >
> > Section "Module"
> >  Disable "dri"
> >  Disable "dri2"
> >  Load "glx"
> > EndSection
> >
> > If I add exec startkde to the top of the /etc/X11/xinit/xinitrc file,
> > then startx fails to start.  I get the same dri2 error as above, but
> > also get
> >
> > startkde: Starting up...
> > Connecting to deprecated signal
> > QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> > kded(13865): Communication Problem with "kded", it probably crashed.
> > Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did
> > not receive a reply (timeout by message bus)" "
> 
> You should not edit this file, you should create a ~/.xinitrc and add
> startkde to that. Try again without messing with the default system
> xinitrc and using your own. You need to let the system xinitrc run, it
> will call yours afterwards.
> 
> 
Thanks - I made this change, but it didn't fix the problem.

> > I verified using /etc/init.d/dbus status that the dbus service is
> > running.  Same for consolekit.
> >
> > /var/log/kdm.log shows one error, repeated for each startup attempt.
> > KCrash: Appication 'kdmgreet' crashing....
> > KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi directly
> > Server Terminated successfully (0).  Closing log file.
> >

After a little bit of further investigation, I discovered that the
kdm.log file was full of old error messages.  Deleting this log file did
not result in a replacement file when I retried startx

dmesg, however, was reporting some 'invalid opcode' errors.  After
finding a 2-page pdf on the correct compile flags to use with and
amdfam10 processors (attached), I had enabled a couple of extra compile
flags, -mabm and -msse4a, as well as setting -march=amdfam10.

I've deleted the -mabm and -msse4a compile flag options from make.conf
and I'm now running a full recompile (emerge -Dav system, emerge -Dav
world).  If that doesn't work, I'll try changing the architecture flag
to -march=amd64 and recompile once more.

Thanks

Jeff