[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Is this a KDM bug ? (And how can I find out :p)
From: "A.J. Venter" <aj () outkastsolutions ! co ! za>
Date: 2008-10-27 7:33:04
Message-ID: 868cfe70810270033i1e6ca568x9c7e9791b9476836 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
> Do you have dri? Try glxinfo | grep direct.
> >
> > Hence my suspicion that this may be an incompatibillity
> with nouveau from
> > the KDM side. But since I am not absolutely sure, I thought I
> would first
> > ask the developers for insight before logging a bug report
> with either
> > project.
> >
> > Ciao
> > A.J.
> I can't see how this could be possibly be caused from KDM.
> However, I can't see how it could not be caused by KDM. Have
> you got it set to use XGL or something similar?
> >
I went digging further and found the answer, it's not a KDM problem but a
lesser-known caveat of the nouveau driver itself. Nouveau's built-in 3D
support is limited to xorg 1.5 and higher, to get it going on 1.4 you need
to also install the gallium driver (which is still very unstable). That
provides the missing nouveau_dri.so file.
I'm not sure why from kdm XFCE also tried to load it but once I added
gallium (as per the nouveau wiki I didn't install it in the system but
rather added ld.so.conf entries for it and just symlinked the dri_file into
the xorg tree) things loaded right.
At that stage KDE and XFCE could load, but there is one glitch which other
nouveau users should know about: at least for now no GL functions work on
the 2D level with it. It causes a completely lockup (so completely I suspect
there's a kernel panic behind the scenes) if you are lucky, and a xorg crash
if you're not.
This means you need to hand-remove any compositing entries from your kwinrc
file if they are there before KDE will load, and you cannot open the
screensaver or desktop entries in control center (the compositing test in
the latter and the GL screensavers in the former cause crashes).
That said, without compositing and avoiding those entries, KDE under nouveau
with remarkably faster and more stable than under proprietory nvidia driver.
Nouveau has a ways to go before it will be a real replacement (tv-out is
barely even started) but it's coming along and it may already provide a
better KDE experience than the nvidia driver for many users (at least, if
you don't miss 3D acceleration for stuff like games). Twinview and
nvidia-style xinerama doesn't work, but the xrandr 1.2 support solved that
easily enough and I could get full dual-head support with just a few changes
to my xorg.conf file.
I had previously used the fbdev driver with the vesafb kernel driver with
some success, but it doesn't support dual-screen even with plain xinerama
and it's set of available resolutions is rather limited. Though it lacks any
compositing support it was by far the fastest KDE4 I have yet had. I would
still like to test the rivafb kernel driver with fbdev and see how that
compares as well.
Ciao
A.J.
--
A.J. Venter
Tel.: +27 21 554 5059
Fax: +27 11 252 9197
Outkast Solutions IT
www.outkastsolutions.co.za
A division of Global Pact Trading Pty Ltd.
www.silentcoder.co.za - Blog
scartoonz.silentcoder.co.za - ScarToonz webcomic
[Attachment #5 (text/html)]
<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex;">Do you have dri? Try glxinfo | \
grep direct.<br> <div class="Ih2E3d">><br>
> Hence my suspicion that this may be an incompatibillity<br>
with nouveau from<br>
> the KDM side. But since I am not absolutely sure, I thought I<br>
would first<br>
> ask the developers for insight before logging a bug report<br>
with either<br>
> project.<br>
><br>
> Ciao<br>
> A.J.<br>
</div>I can't see how this could be possibly be caused from KDM.<br>
However, I can't see how it could not be caused by KDM. Have<br>
you got it set to use XGL or something similar?<br>
></blockquote><div>I went digging further and found the answer, it's not a KDM \
problem but a lesser-known caveat of the nouveau driver itself. Nouveau's \
built-in 3D support is limited to xorg 1.5 and higher, to get it going on 1.4 you \
need to also install the gallium driver (which is still very unstable). That provides \
the missing nouveau_dri.so file. </div> <div>I'm not sure why from kdm XFCE \
also tried to load it but once I added gallium (as per the nouveau wiki I didn't \
install it in the system but rather added ld.so.conf entries for it and just \
symlinked the dri_file into the xorg tree) things loaded right.</div> \
<div><br></div><div>At that stage KDE and XFCE could load, but there is one glitch \
which other nouveau users should know about: at least for now no GL functions work on \
the 2D level with it. It causes a completely lockup (so completely I suspect \
there's a kernel panic behind the scenes) if you are lucky, and a xorg crash if \
you're not. </div> <div>This means you need to hand-remove any compositing \
entries from your kwinrc file if they are there before KDE will load, and you cannot \
open the screensaver or desktop entries in control center (the compositing test in \
the latter and the GL screensavers in the former cause crashes).</div> \
<div><br></div><div>That said, without compositing and avoiding those entries, KDE \
under nouveau with remarkably faster and more stable than under proprietory nvidia \
driver. Nouveau has a ways to go before it will be a real replacement (tv-out is \
barely even started) but it's coming along and it may already provide a \
better KDE experience than the nvidia driver for many users (at least, if you \
don't miss 3D acceleration for stuff like games). Twinview and nvidia-style \
xinerama doesn't work, but the xrandr 1.2 support solved that easily enough and I \
could get full dual-head support with just a few changes to my xorg.conf file.</div> \
<div><br></div><div>I had previously used the fbdev driver with the vesafb kernel \
driver with some success, but it doesn't support dual-screen even with plain \
xinerama and it's set of available resolutions is rather limited. Though it lacks \
any compositing support it was by far the fastest KDE4 I have yet had. I would still \
like to test the rivafb kernel driver with fbdev and see how that compares as \
well.</div> <div><br></div><div>Ciao</div><div>A.J.</div></div>-- <br>A.J. \
Venter<br>Tel.: +27 21 554 5059<br>Fax: +27 11 252 9197<br>Outkast Solutions IT<br><a \
href="http://www.outkastsolutions.co.za">www.outkastsolutions.co.za</a><br> A \
division of Global Pact Trading Pty Ltd.<br><br><a \
href="http://www.silentcoder.co.za">www.silentcoder.co.za</a> - Blog<br><a \
href="http://scartoonz.silentcoder.co.za">scartoonz.silentcoder.co.za</a> - ScarToonz \
webcomic<br>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic