From: "Claudio Roberto França Pereira" <spideybr@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems starting KDE
Date: Sat, 31 Dec 2011 14:59:26 -0200 [thread overview]
Message-ID: <CAGo3Wep+pVjOM1O5Vp09PVU8AbkQZre4OHEb_98-qP5dbr-ryA@mail.gmail.com> (raw)
In-Reply-To: <1325346805.15973.36.camel@laptop.limeyworld>
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.
>
> 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.
> 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.
>
> Any assistance gratefully received.
>
> Thanks
>
> Jeff
>
>
>
next prev parent reply other threads:[~2011-12-31 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 15:53 [gentoo-user] Problems starting KDE Jeff Cranmer
2011-12-31 16:59 ` Claudio Roberto França Pereira [this message]
2011-12-31 18:37 ` Jeff Cranmer
2012-01-01 14:54 ` Jeff Cranmer
2012-01-01 15:30 ` Mick
2012-01-01 16:13 ` Jeff Cranmer
2012-01-01 16:23 ` Peter Humphrey
2012-01-01 20:53 ` Alan McKinnon
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=CAGo3Wep+pVjOM1O5Vp09PVU8AbkQZre4OHEb_98-qP5dbr-ryA@mail.gmail.com \
--to=spideybr@gmail.com \
--cc=gentoo-user@lists.gentoo.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