Bug 147216 - No DRI with S3 Unichrome KM400
Summary: No DRI with S3 Unichrome KM400
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Beta 2
Hardware: i686 SUSE Other
: P5 - None : Normal with 5 votes (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-01 10:22 UTC by Felix Rommel
Modified: 2006-02-20 11:25 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
lspci -v (4.49 KB, application/octet-stream)
2006-02-01 10:23 UTC, Felix Rommel
Details
glxinfo -v (4.66 KB, application/octet-stream)
2006-02-01 10:25 UTC, Felix Rommel
Details
hwinfo --gfx (952 bytes, application/octet-stream)
2006-02-01 10:25 UTC, Felix Rommel
Details
hwinfo --gfx (372 bytes, application/octet-stream)
2006-02-01 10:25 UTC, Felix Rommel
Details
Xorg.0.log (50.91 KB, text/x-log)
2006-02-01 10:27 UTC, Felix Rommel
Details
SUSE 10.1 Beta2 xorg.conf (4.84 KB, application/octet-stream)
2006-02-01 10:28 UTC, Felix Rommel
Details
Ubuntu Dapper beta xorg.conf file (2.46 KB, application/octet-stream)
2006-02-01 10:29 UTC, Felix Rommel
Details
LIBGL_DEBUG=1 glxinfo (3.61 KB, application/octet-stream)
2006-02-01 15:14 UTC, Felix Rommel
Details
LIBGL_DEBUG=1 glxinfo -v (4.66 KB, application/octet-stream)
2006-02-01 17:32 UTC, Felix Rommel
Details
SUSE 10 Xorg.0.log (55.69 KB, application/octet-stream)
2006-02-06 21:12 UTC, Felix Rommel
Details
SUSE 10 xorg.conf (5.40 KB, application/octet-stream)
2006-02-06 21:13 UTC, Felix Rommel
Details
SUSE 10 glxinfo -v (6.78 KB, application/octet-stream)
2006-02-06 21:15 UTC, Felix Rommel
Details
SUSE 10.1 Beta3 hwinfo --gfx (953 bytes, application/octet-stream)
2006-02-06 22:00 UTC, Felix Rommel
Details
SUSE 10.1 Beta3 xorg.conf (5.34 KB, text/plain)
2006-02-06 22:02 UTC, Felix Rommel
Details
SUSE 10.1 Beta3 xorg.conf WORKS! (5.38 KB, text/plain)
2006-02-06 22:35 UTC, Felix Rommel
Details
SUSE 10.1 Beta3 glxinfo -v DIRECT RENDERING YES (6.78 KB, application/octet-stream)
2006-02-06 22:38 UTC, Felix Rommel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Rommel 2006-02-01 10:22:41 UTC
After getting my graphic card to work with "VBEModes" "true" I tried DRI.

But with gfxinfo I get the message:

direct rendering: no

I tried the composite shadow effects in KDE but they don't work although I enabled Composite in xorg.conf.

With Ubuntu Dapper Beta I get DRI support without problems. I will attach all relevant files - my Ubuntu Dapper xorg.conf file included.
Comment 1 Felix Rommel 2006-02-01 10:23:14 UTC
Created attachment 65997 [details]
lspci -v
Comment 2 Felix Rommel 2006-02-01 10:25:14 UTC
Created attachment 65999 [details]
glxinfo -v
Comment 3 Felix Rommel 2006-02-01 10:25:43 UTC
Created attachment 66000 [details]
hwinfo --gfx
Comment 4 Felix Rommel 2006-02-01 10:25:58 UTC
Created attachment 66001 [details]
hwinfo --gfx
Comment 5 Felix Rommel 2006-02-01 10:27:00 UTC
Created attachment 66003 [details]
Xorg.0.log
Comment 6 Felix Rommel 2006-02-01 10:28:16 UTC
Created attachment 66004 [details]
SUSE 10.1 Beta2 xorg.conf
Comment 7 Stefan Dirsch 2006-02-01 10:28:37 UTC
DRI is disabled for via by default because it has been broken in the past.

--> /etc/profile.d/via.sh
--> /etc/profile.d/via.csh

Does unsetting LIBGL_ALWAYS_INDIRECT ("unset LIBGL_ALWAYS_INDIRECT") work for you?
Comment 8 Felix Rommel 2006-02-01 10:29:13 UTC
Created attachment 66006 [details]
Ubuntu Dapper beta xorg.conf file
Comment 9 Felix Rommel 2006-02-01 10:48:25 UTC
Composite effects in KDE work now! :) But I wonder why glxinfo still has the message:

direct rendering: no!??

But how fast is that - now it's faster than under Kubuntu Dapper beta. Really great work! The Vista killer is here - now! ;)

You should make a check button in SAX2 for S3 Unichrome cards which disables the environment variable LIBGL_ALWAYS_INDIRECT and add the composite section to xorg.conf so that users get great desktop effects with KDE.

I will work a little bit with it and see if something crashes... Hope SUSE 10.1 comes out soon :)

Comment 10 Stefan Dirsch 2006-02-01 11:12:06 UTC
Could you try

  LIBGL_DEBUG=1 glxinfo

and add/attach the output? Thanks.
Comment 11 Felix Rommel 2006-02-01 15:14:07 UTC
Created attachment 66037 [details]
LIBGL_DEBUG=1 glxinfo
Comment 12 Stefan Dirsch 2006-02-01 15:45:21 UTC
Hmm. No additional information. :-( Strange ...
Comment 13 Felix Rommel 2006-02-01 17:32:08 UTC
Created attachment 66057 [details]
LIBGL_DEBUG=1 glxinfo -v

How about that? I added a -v option.
Comment 14 Stefan Dirsch 2006-02-01 17:34:27 UTC
No, does not help. I expected a different output. :-(
Comment 15 Felix Rommel 2006-02-04 01:19:47 UTC
In SUSE 10 I just moved the files via.sh and via.csh to another place. After that I got direct rendering there.

I tried the same thing on 10.1 Beta3 but stil glxinfo says no direct rendering.
Comment 16 Stefan Dirsch 2006-02-06 04:24:04 UTC
Hmm ... still using the "vesa" driver? See comment #5.
Comment 17 Felix Rommel 2006-02-06 21:11:27 UTC
No:

SUSE 10:

With SUSE 10 everything works now with "via" driver and the option "VBEModes" "true". There I also have glxinfo: direct rendering on.

BUT I have updated to Xorg 6.9 from your supplementary offer.

I just moved /etc/profile.d/via.sh and .../via.csh to another place to get direct rendering.

SUSE 10.1:

In SUSE 10.1 Beta3 I also made the same settings like in 10. But moving .../via.sh and .../via.csh was not successfull...

Now I can enable composite effects in KDE with shadows, translucent windows etc.  moving windows is very smooth and fast but glxinfo still tells me no direct rendering...

If you can manage to bring back the direct rendering like it was in 10, I can test it in Beta4 if it's working stable. Then I will test it with glxgears, Tuxracer and 3D screen savers to see if it's fast and also stable.

I attach my SUSE 10 Xorg.0.log and my SUSE 10 xorg.conf.

Comment 18 Felix Rommel 2006-02-06 21:12:19 UTC
Created attachment 66612 [details]
SUSE 10 Xorg.0.log
Comment 19 Felix Rommel 2006-02-06 21:13:05 UTC
Created attachment 66613 [details]
SUSE 10 xorg.conf
Comment 20 Felix Rommel 2006-02-06 21:15:00 UTC
Created attachment 66614 [details]
SUSE 10 glxinfo -v
Comment 21 Stefan Dirsch 2006-02-06 21:27:45 UTC
Read again my comment #16. You need to use the "via" driver instead.
Comment 22 Felix Rommel 2006-02-06 21:59:51 UTC
Sorry, seems to be that I attached the the xorg.conf with enabled vesa driver.

I'm in Beta3 now and I created all the information again and marked it as Beta3.

I moved the files via.csh and via.sh from /etc/profile.d to / so that 

LIBGL_ALWAYS_INDIRECT=1

is NOT set. Hope that's not the problem that I moved it to / instead of setting it to 0 for example. But I wanted be sure 100% that this variable isn't set.

That's all information I can give at the moment. I will test Beta4 when it comes out on thursday. I have to learn for exam now ;)
Comment 23 Felix Rommel 2006-02-06 22:00:57 UTC
Created attachment 66623 [details]
SUSE 10.1 Beta3 hwinfo --gfx
Comment 24 Felix Rommel 2006-02-06 22:02:03 UTC
Created attachment 66624 [details]
SUSE 10.1 Beta3 xorg.conf
Comment 25 Felix Rommel 2006-02-06 22:33:09 UTC
IT WORKS NOW!!!

Don't know what happened to my xorg.conf - it was a complete mess...

So what I did: I copied the xorg.conf from SUSE 10 installation to 10.1 installation.

Now it works! I attach the currently used xorg.conf file which I copied from 10 and now use in 10.1 Beta3. Plus the output of glxinfo -v which shows me direct rendering now.

I will test everything with Beta4 again. Have to learn now ;)
Comment 26 Felix Rommel 2006-02-06 22:35:17 UTC
Created attachment 66637 [details]
SUSE 10.1 Beta3 xorg.conf WORKS!
Comment 27 Felix Rommel 2006-02-06 22:38:43 UTC
Created attachment 66639 [details]
SUSE 10.1 Beta3 glxinfo -v DIRECT RENDERING YES
Comment 28 Stefan Dirsch 2006-02-20 11:25:15 UTC
Ok. Closing as fixed since DRI works now, when removing the profile scripts.