On Tue, Apr 17, 2012 at 22:50, Joshua Murphy <poiso...@gmail.com> wrote:
> Two things come to mind, given some recent trouble I've had on the
> radeon side of the coin here, and with an intel system or two in the
> past. The DRM related drivers seem to be prone to misbehaving when
> they're not configured as modules. I haven't managed to sort out why,
> so you may see if a change there helps, though it'll likely cause mode
> changes throughout the booting process. The second thing that comes to
> mind is that you don't include any relevant entries from glxinfo
> (glxinfo | grep ender) or Xorg.?.log (notably anything flagged as an
> error, 'grep EE /var/log/Xorg.0.log' grabs that, plus a bit of cruft),
> notably from a session where things aren't working properly, as the
> majority of issues trace back to direct rendering being disabled due
> to some incompatibility that gets noted in the log (often in
> delightfully cryptic prose).

I converted nouveau to a kernel module:
$ lsmod
Module                  Size  Used by
nouveau               579746  -2
cfbfillrect            12485  -2
cfbimgblt              12313  -2
cfbcopyarea            12313  -2
drm_kms_helper         27209  -2
ttm                    57762  -2

switched the kwinrc to OpenGL, ran startx. KDE loaded (I saw the
splash screen and heard the startup noise) but then nothing was shown
on the desktop (so I couldnt run glxinfo as I couldnt see anything)

Ive attached Xorg.0.log and xsession-errors herein. Bad.tgz has
versions of these files from OpenGL whereas good.tgz has versions from
XRender.

FWIW, the only 'EE' in the Xorg log is missing 'fb' and 'vesa' modules

Also  I do not have an xorg.conf if that makes a difference

-- 
Douglas J Hunley (doug.hun...@gmail.com)
Twitter: @hunleyd                                               Web:
douglasjhunley.com
G+: http://goo.gl/sajR3

Attachment: bad.tgz
Description: GNU Zip compressed data

Attachment: good.tgz
Description: GNU Zip compressed data

Reply via email to