View previous topic :: View next topic |
Author |
Message |
RoninTT n00b
Joined: 28 Feb 2006 Posts: 7
|
Posted: Thu Mar 09, 2006 11:37 am Post subject: |
|
|
I have no probs with revision 55, do you get some error when trying to run XGL?
Have you also changed to the "new" version of libshadow.so you can get from http://www.fairlite.demon.co.uk/intel.html?
|
|
Back to top |
|
|
plesho n00b
Joined: 27 Dec 2005 Posts: 10
|
Posted: Thu Mar 09, 2006 1:21 pm Post subject: |
|
|
RoninTT wrote: | I have no probs with revision 55, do you get some error when trying to run XGL? |
Just to clear things out:
1. You are using the CoffeeBuzz overlay - 55 revision at the present time
2. You are copying i810_drv.so from http://www.fairlite.demon.co.uk/intel.html to
Code: | /usr/lib/xorg/modules/drivers |
3. The libshadow.so from http://www.fairlite.demon.co.uk/intel.html to
Code: | /usr/lib/xorg/modules |
4. You get DRI working
Am I missing something? _________________ Once upon a time a wise guy who said:
Two things are infinite: the universe and human stupidity;
and I'm not sure about the universe
Last edited by plesho on Fri Mar 10, 2006 9:53 am; edited 1 time in total |
|
Back to top |
|
|
RoninTT n00b
Joined: 28 Feb 2006 Posts: 7
|
Posted: Thu Mar 09, 2006 1:42 pm Post subject: |
|
|
Yep that is the way I do it.
plesho wrote: | RoninTT wrote: | I have no probs with revision 55, do you get some error when trying to run XGL? |
Just to clear things out:
1. You are using the CoffeeBuzz overlay - 55 revision at the present time
2. You are copying i810_drv.so from http://www.fairlite.demon.co.uk/intel.html to
Code: | /usr/lib/xorg/modules/drivers |
3. The libshadow.so from http://www.fairlite.demon.co.uk/intel.html to
Code: | /usr/lib/xorg/modules |
4. You get DRI working
Am I missing something? |
|
|
Back to top |
|
|
plesho n00b
Joined: 27 Dec 2005 Posts: 10
|
Posted: Thu Mar 09, 2006 2:06 pm Post subject: |
|
|
RoninTT wrote: | Yep that is the way I do it. |
I think I'm getting closer - I remember now that you said that although you get
Code: | direct rendering: No |
it is working decently fast - 600 - 700 fps in glxgear.
I can confirm that now, but unfortunately I am not able to start Xgl:
Code: |
$ Xgl :1
X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 158 (GLX)
Minor opcode of failed request: 1 (X_GLXRender)
Serial number of failed request: 93
Current serial number in output stream: 94
|
EDIT:
I saw the proposed solution in the XGL Wiki Howto and it does not help, Xgl continues to give the same error
Now I'm syncing portage and will update to see if that will help. Maybe it is worth to mention that the profile is 2006.0.
EDIT2:
I saw a thread in kororaa.org forums where a guy after enabling DRI on his i915 card resulted in a boost from 800 to 1800fps. It seems that these cards may do even better than we think
Still hoping to get it working fast enough ... _________________ Once upon a time a wise guy who said:
Two things are infinite: the universe and human stupidity;
and I'm not sure about the universe
Last edited by plesho on Fri Mar 10, 2006 9:54 am; edited 2 times in total |
|
Back to top |
|
|
kanttu n00b
Joined: 31 Aug 2005 Posts: 58
|
Posted: Thu Mar 09, 2006 4:25 pm Post subject: |
|
|
I'd like to know what is your glxgear result without xgl and with dri _________________ AMD Athlon64 3500+
ASUS A8N-SLI deluxe
PNY GeForce 6800GT |
|
Back to top |
|
|
CoffeeBuzz Apprentice
Joined: 15 Jun 2005 Posts: 269 Location: Canada Eh.
|
Posted: Thu Mar 09, 2006 7:23 pm Post subject: |
|
|
plesho wrote: | RoninTT wrote: | I have no probs with revision 55, do you get some error when trying to run XGL? |
Just to clear things out:
1. You are using the CoffeeBuzz overlay - 55 revision at the present time
2. You are copying i810_drv.so from http://www.fairlite.demon.co.uk/intel.html to
Code: | /usr/lib/xorg/modules/drivers |
3. The libshadow.so from http://www.fairlite.demon.co.uk/intel.html to
Code: | /usr/lib/xorg/modules |
4. You get DRI working
Am I missing something? |
If this works, I'll add a USE flag to the Mesa ebuild i810_dri which will copy these libs automagically. Your thoughts? _________________ HP Pavilion zd7260us
Xgl Overlay: http://svn.xgl-coffee.org/xgl-coffee/trunk
Xgl Forums: http://forums.xgl-coffee.org |
|
Back to top |
|
|
plesho n00b
Joined: 27 Dec 2005 Posts: 10
|
Posted: Thu Mar 09, 2006 8:44 pm Post subject: |
|
|
From what I understand the drivers from http://www.fairlite.demon.co.uk/intel.html are maybe better, but does not get DRI working with the latest mesa.
But may be it is just me ...
kanttu wrote: | I'd like to know what is your glxgear result without xgl and with dri |
Unfotunately I cannot give you such information ... because I am not able to get DRI working with the latest MESA from the overlay.
This is the main problem I think - nomather with or without Xgl, DRI is not working for me. As I said - from what I know it should be around 1800fps with DRI
EDIT
CoffeeBuzz - may it will be better to create a new ebuild x11-drivers/xf86-video-i810-bin which will be blocked by the x11-drivers/xf86-video-i810 package. _________________ Once upon a time a wise guy who said:
Two things are infinite: the universe and human stupidity;
and I'm not sure about the universe
Last edited by plesho on Fri Mar 10, 2006 5:12 pm; edited 1 time in total |
|
Back to top |
|
|
RoninTT n00b
Joined: 28 Feb 2006 Posts: 7
|
Posted: Fri Mar 10, 2006 10:56 am Post subject: |
|
|
When I run with the lastest stable Mesa I will get about 1200 FPS with Glxgears and no problems with DRI.
When I switch from the stable to cvs Mesa I can't get DRI, without using the old driver instead of the new. If I do this I still get about 1200 FPS from glxgears. But XGL is very slow with wobbly and switcher, and firefox runs extremly slow.
If use the cvs Mesa and the drivers from fairlite, I get DRI without any problems in normal X, and about 700-800 FPS from glxgears. XGL runs better but it fells like its more CPU heavy than before. Plus the pugin for F12 (I've forgotten what its called) is running extremly slow.
Hope this helps. |
|
Back to top |
|
|
alanic n00b
Joined: 13 Jan 2006 Posts: 41
|
Posted: Fri Mar 10, 2006 6:55 pm Post subject: |
|
|
Hey RoninTT, how did you overcome this?
Code: |
$ glxgears
libGL warning: 3D driver returned no fbconfigs.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering |
I think the newest mesa (mesa-6.5.0_alpha20060308) screwed my direct rendering. Were we supposed to use an older mesa?
Edit: nevermind, I'll try the fairlite whatever drivers again, they gave me some error before. We'll see.
Last edited by alanic on Fri Mar 10, 2006 6:58 pm; edited 1 time in total |
|
Back to top |
|
|
x.para Apprentice
Joined: 22 May 2005 Posts: 174 Location: CZ
|
Posted: Fri Mar 10, 2006 6:55 pm Post subject: broken fonts and xgl server crashes |
|
|
Hi every body here. I'd like to share again where I moved so far. I have working Xgl server and fully working drm. Wow cube rotates smoothly, does not break and chops. To achive this I used drivers that I posted later means I can use drivers from:
http://dri.freedesktop.org/snapshots/
and also from here:
http://www.fairlite.demon.co.uk/intel.html
with basically same result. But some new bugs appered to me:
- My fonts in xterm are broken and unreadible, also I can not see what I am writting until I change desktop over, snapshot here: http://paraweb.czweb.org/image/xglfonts.png
- As soon as I move any window (not the cube rotation) Xgl crashes with the message: memory violation access in detail like this:
Code: |
libGL warning: 3D driver claims to not support visual 0x27
libGL warning: 3D driver claims to not support visual 0x29
libGL warning: 3D driver claims to not support visual 0x2b
libGL warning: 3D driver claims to not support visual 0x2d
libGL warning: 3D driver claims to not support visual 0x2f
libGL warning: 3D driver claims to not support visual 0x31
Could not init font path element /usr/share/fonts/OTF, removing from list!
Could not init font path element /usr/share/fonts/CID/, removing from list! FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 2, should be 1; fixing.
Neopr vnný p¡stup do pamti (SIGSEGV)
|
and also
Code: |
fatal IO error 104 (Spojen¡ zrueno druhou stranou) or KillClient on X server ":1.0"
xterm: fatal IO error 32 (Peruena roura (SIGPIPE)) or KillClient on X server ":1.0" [1]- Exit 84
|
Does anybody has similar problems? I am sure that this is related to drm because if it is deactivated Xgl works ok. but very very very slow.
Thanks for sharing.
Last edited by x.para on Sat Mar 11, 2006 10:22 am; edited 1 time in total |
|
Back to top |
|
|
zcw100 n00b
Joined: 07 Mar 2006 Posts: 3
|
Posted: Fri Mar 10, 2006 9:37 pm Post subject: |
|
|
I've managed to get DRI working on a copaq v2000t with a 945gm (i915_drv)
glxgears is reporting 800-900 fps but when I go to start Xgl it returns with "no screens found"....so close, grrr!!!! |
|
Back to top |
|
|
zapata Tux's lil' helper
Joined: 26 Jun 2005 Posts: 82 Location: Hamburg / Germany
|
Posted: Sat Mar 11, 2006 2:43 am Post subject: |
|
|
Hi,
(first, sorry for my english)
I can install the newest coffee-overlay without any problems. Only I have to do, to get DRI workig, is to use the drivers from:
Code: | http://www.fairlite.demon.co.uk/intel.html |
when I restart gdm, it seem to run with xgl (ps -ax shows the Xgl process and the screen comes delayed), but when I start the gnome-session, he kicks me out, after loading the panel and I went back to gdm.
I reveice the following message:
Code: | >Starting XGL at Display: 1
========= XGL ============
libGL warning: 3D driver claims to not support visual 0x23
libGL warning: 3D driver claims to not support visual 0x25
libGL warning: 3D driver claims to not support visual 0x27
libGL warning: 3D driver claims to not support visual 0x29
libGL warning: 3D driver claims to not support visual 0x2b
libGL warning: 3D driver claims to not support visual 0x2d
libGL warning: 3D driver claims to not support visual 0x2f
libGL warning: 3D driver claims to not support visual 0x31
expected keysym, got dead_diaresis: line 143 of pc/de
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Could not init font path element /usr/share/fonts/OTF, removing from list!
Could not init font path element /usr/share/fonts/CID/, removing from list!
======= COMPIZ ===========
SmcOpenConnection failed: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
====== DECORATIONS =======
======= GNOME ============
[root@zapata] ~/skripte (1,7G free) # -=Sa 11.03.2006 3:38:48=-
(gnome-window-decorator:9589): Gtk-WARNING **: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
(gnome-window-decorator:9589): Gtk-WARNING **: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
(nautilus:9591): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
(gnome-panel:9592): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Bonobo-Activation-Message: Make registration id from 'OAFIID:GNOME_PanelShell' ':1'
Bonobo-Activation-Message: Registering iid 'OAFIID:GNOME_PanelShell' with display ':1'
Bonobo-Activation-Message: About to register 'OAFIID:GNOME_PanelShell': 0x80df340
Bonobo-Activation-Message: Registration environment for 'DISPLAY' = ':1'
Bonobo-Activation-Message: registration of 'OAFIID:GNOME_PanelShell' returns (success)
Bonobo-Activation-Message: Successfully registered `OAFIID:GNOME_PanelShell'
(nautilus:9591): Gtk-WARNING **: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
(nautilus:9591): Gtk-WARNING **: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
(gnome-panel:9592): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80eab90
(gnome-panel:9592): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80eab90
(gnome-panel:9592): Gtk-WARNING **: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
(gnome-panel:9592): Gtk-WARNING **: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
(gnome-window-decorator:9589): Gtk-WARNING **: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
(gnome-settings-daemon:9590): Gtk-WARNING **: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
(gnome-settings-daemon:9590): Gtk-WARNING **: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
Bonobo-Activation-Message: About to register 'OAFIID:GNOME_SettingsDaemon': 0x80902a8
Bonobo-Activation-Message: registration of 'OAFIID:GNOME_SettingsDaemon' returns (success)
Bonobo-Activation-Message: Successfully registered `OAFIID:GNOME_SettingsDaemon'
(gnome-settings-daemon:9590): Gtk-WARNING **: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
(gnome-panel:9592): Gtk-WARNING **: Im Modulpfad »hcengine« konnte keine Themen-Engine gefunden werden,
X connection to :1.0 broken (explicit kill or server shutdown).
gnome-panel: Fatal IO error 104 (Die Verbindung wurde vom Kommunikationspartner zurÃckgesetzt) on X server :1.0.
The application 'gnome-settings-daemon' lost its connection to the display :1.0;
most likely the X server was shut down or you killed/destroyed
the application.
[1142048329,000,xklavier.c:XklStartListen/] The backend does not require manual layout management - but it is provided by the applicationBonobo-Activation-Message: About to register 'OAFIID:Nautilus_Factory': 0x8140b10
Bonobo-Activation-Message: Registration environment for 'DISPLAY' = ':1.0'
The application 'gnome-window-decorator' lost its connection to the display :1.0;
most likely the X server was shut down or you killed/destroyed
the application.
Bonobo-Activation-Message: registration of 'OAFIID:Nautilus_Factory' returns (success)
Bonobo-Activation-Message: Successfully registered `OAFIID:Nautilus_Factory'
The application 'nautilus' lost its connection to the display :1.0;
most likely the X server was shut down or you killed/destroyed
the application. |
I hope, that someone can help,
thanks!
zapata |
|
Back to top |
|
|
evolusion n00b
Joined: 16 Feb 2006 Posts: 7
|
Posted: Sat Mar 11, 2006 11:47 am Post subject: |
|
|
I'm back trying to get this working again and seem to be hitting the same brick wall as before, everything compiles fine and I have tried all the different tricks I can find, so does anyone know what could be causing this? _________________ -evolusion- |
|
Back to top |
|
|
x.para Apprentice
Joined: 22 May 2005 Posts: 174 Location: CZ
|
Posted: Sat Mar 11, 2006 11:59 am Post subject: |
|
|
evolusion wrote: | I'm back trying to get this working again and seem to be hitting the same brick wall as before, everything compiles fine and I have tried all the different tricks I can find, so does anyone know what could be causing this? |
It looks that you are running on ColorDept 16. Try to change to 24. |
|
Back to top |
|
|
evolusion n00b
Joined: 16 Feb 2006 Posts: 7
|
Posted: Sat Mar 11, 2006 1:10 pm Post subject: |
|
|
That seems to have solved that problem, thanks =)
Now I seem to be crashing when Nautilus launches, i shall investigate and no doubt post again soon asking for help! _________________ -evolusion- |
|
Back to top |
|
|
plesho n00b
Joined: 27 Dec 2005 Posts: 10
|
Posted: Mon Mar 13, 2006 9:09 am Post subject: |
|
|
zapata wrote: | I can install the newest coffee-overlay without any problems. Only I have to do, to get DRI workig, is to use the drivers from:
Code: | http://www.fairlite.demon.co.uk/intel.html |
|
Can you tell us what kernel version are you using? _________________ Once upon a time a wise guy who said:
Two things are infinite: the universe and human stupidity;
and I'm not sure about the universe |
|
Back to top |
|
|
zapata Tux's lil' helper
Joined: 26 Jun 2005 Posts: 82 Location: Hamburg / Germany
|
Posted: Mon Mar 13, 2006 8:08 pm Post subject: |
|
|
plesho wrote: | zapata wrote: | I can install the newest coffee-overlay without any problems. Only I have to do, to get DRI workig, is to use the drivers from:
Code: | http://www.fairlite.demon.co.uk/intel.html |
|
Can you tell us what kernel version are you using? |
sorry ...
I use kernel-2.6.16-rc3-nitro1.
Now I have change the startXgl-script (the parms for compiz) and I receive this message when starting from a VT:
Code: | >Starting XGL at Display: 0
========= XGL ============
X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.16-rc3-nitro1 i686
Current Operating System: Linux zapatta 2.6.16-rc3-nitro1 #4 SMP PREEMPT Tue Mar 7 02:33:54 GMT 2006 i686
Build Date: 08 March 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.93.log", Time: Sun Mar 12 22:15:44 2006
(==) Using config file: "/etc/X11/xorg.conf"
Could not init font path element /usr/share/fonts/CID/, removing from list!
libGL warning: 3D driver claims to not support visual 0x23
libGL warning: 3D driver claims to not support visual 0x25
libGL warning: 3D driver claims to not support visual 0x27
libGL warning: 3D driver claims to not support visual 0x29
libGL warning: 3D driver claims to not support visual 0x2b
libGL warning: 3D driver claims to not support visual 0x2d
libGL warning: 3D driver claims to not support visual 0x2f
libGL warning: 3D driver claims to not support visual 0x31
expected keysym, got dead_diaresis: line 143 of pc/de
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Could not init font path element /usr/share/fonts/OTF, removing from list!
Could not init font path element /usr/share/fonts/CID/, removing from list!
======= COMPIZ ===========
====== DECORATIONS =======
======= GNOME ============
expected keysym, got dead_diaresis: line 143 of pc/de
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(gnome-window-decorator:10454): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
(gnome-window-decorator:10454): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
Bonobo-Activation-Message: Make registration id from 'OAFIID:GNOME_PanelShell' ':0'
Bonobo-Activation-Message: Registering iid 'OAFIID:GNOME_PanelShell' with display ':0'
Bonobo-Activation-Message: About to register 'OAFIID:GNOME_PanelShell': 0x80d6a48
(nautilus:10456): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
(nautilus:10456): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
Bonobo-Activation-Message: Registration environment for 'DISPLAY' = ':0'
Bonobo-Activation-Message: registration of 'OAFIID:GNOME_PanelShell' returns (success)
Bonobo-Activation-Message: Successfully registered `OAFIID:GNOME_PanelShell'
(gnome-panel:10457): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x80e8358
(gnome-panel:10457): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80e8358
(gnome-panel:10457): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
(gnome-panel:10457): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
(gnome-settings-daemon:10455): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
(gnome-settings-daemon:10455): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
Bonobo-Activation-Message: About to register 'OAFIID:GNOME_SettingsDaemon': 0x80879a0
Bonobo-Activation-Message: registration of 'OAFIID:GNOME_SettingsDaemon' returns (success)
Bonobo-Activation-Message: Successfully registered `OAFIID:GNOME_SettingsDaemon'
(gnome-settings-daemon:10455): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
<stdin>:494:31: warning: no newline at end of file
xrdb: "XTerm*background" on line 477 overrides entry on line 286
xrdb: "XTerm*foreground" on line 478 overrides entry on line 287
xrdb: "XTerm*color0" on line 479 overrides entry on line 311
xrdb: "XTerm*color1" on line 480 overrides entry on line 312
xrdb: "XTerm*color2" on line 481 overrides entry on line 313
xrdb: "XTerm*color3" on line 482 overrides entry on line 314
xrdb: "XTerm*color4" on line 483 overrides entry on line 315
xrdb: "XTerm*color5" on line 484 overrides entry on line 316
xrdb: "XTerm*color6" on line 485 overrides entry on line 317
xrdb: "XTerm*color7" on line 486 overrides entry on line 318
xrdb: "XTerm*color8" on line 487 overrides entry on line 319
xrdb: "XTerm*color9" on line 488 overrides entry on line 320
xrdb: "XTerm*color10" on line 489 overrides entry on line 321
xrdb: "XTerm*color11" on line 490 overrides entry on line 322
xrdb: "XTerm*color12" on line 491 overrides entry on line 323
xrdb: "XTerm*color13" on line 492 overrides entry on line 324
xrdb: "XTerm*color14" on line 493 overrides entry on line 325
xrdb: "XTerm*color15" on line 494 overrides entry on line 326
<stdin>:494:31: warning: no newline at end of file
xrdb: "XTerm*background" on line 477 overrides entry on line 286
xrdb: "XTerm*foreground" on line 478 overrides entry on line 287
xrdb: "XTerm*color0" on line 479 overrides entry on line 311
xrdb: "XTerm*color1" on line 480 overrides entry on line 312
xrdb: "XTerm*color2" on line 481 overrides entry on line 313
xrdb: "XTerm*color3" on line 482 overrides entry on line 314
xrdb: "XTerm*color4" on line 483 overrides entry on line 315
xrdb: "XTerm*color5" on line 484 overrides entry on line 316
xrdb: "XTerm*color6" on line 485 overrides entry on line 317
xrdb: "XTerm*color7" on line 486 overrides entry on line 318
xrdb: "XTerm*color8" on line 487 overrides entry on line 319
xrdb: "XTerm*color9" on line 488 overrides entry on line 320
xrdb: "XTerm*color10" on line 489 overrides entry on line 321
xrdb: "XTerm*color11" on line 490 overrides entry on line 322
xrdb: "XTerm*color12" on line 491 overrides entry on line 323
xrdb: "XTerm*color13" on line 492 overrides entry on line 324
xrdb: "XTerm*color14" on line 493 overrides entry on line 325
xrdb: "XTerm*color15" on line 494 overrides entry on line 326
Bonobo-Activation-Message: About to register 'OAFIID:Nautilus_Factory': 0x814bff8
Bonobo-Activation-Message: Registration environment for 'DISPLAY' = ':0.0'
Bonobo-Activation-Message: registration of 'OAFIID:Nautilus_Factory' returns (success)
Bonobo-Activation-Message: Successfully registered `OAFIID:Nautilus_Factory'
(nautilus:10456): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
(gnome-window-decorator:10454): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
(gnome-panel:10457): Gtk-WARNING **: Unable to locate theme engine in module_path: "hcengine",
X connection to :0.0 broken (explicit kill or server shutdown).
The application 'gnome-settings-daemon' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
[1142201751,000,xklavier.c:XklStartListen/] The backend does not require manual layout management - but it is provided by the applicationThe application 'gnome-window-decorator' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
gnome-panel: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
The application 'nautilus' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application. |
The sreen is now not crashing. I see for a moment my background-picture, and then a blue background. I can only move the mouse and nothing else.
shows, that Xgl ist started.
EDIT:
startXgl:
Code: | #!/bin/bash
echo ">Starting XGL at Display: $1"
echo "========= XGL ============"
Xgl :$1 -ac -accel xv -accel glx:pbuffer &
sleep 3
echo "======= COMPIZ ==========="
DISPLAY=:$1 LD_LIBRARY_PATH=/usr/lib/opengl/xorg-x11/lib/ compiz --replace decoration wobbly fade minimize cube rotate zoom scale move resize place &
sleep 3
echo "====== DECORATIONS ======="
DISPLAY=:$1 gnome-window-decorator &
# sleep 3
echo "======= GNOME ============"
DISPLAY=:$1 /usr/libexec/gnome-settings-daemon &
DISPLAY=:$1 nautilus -n --sync &
DISPLAY=:$1 gnome-panel &
DISPLAY=:$1 setxkbmap -model pc105 -layout de -variant basic &
#echo "======= LOGOUT ============"
#killall Xgl
# Adding the line above,if you can't logout Gnome correctly. |
Thanks for help! |
|
Back to top |
|
|
evolusion n00b
Joined: 16 Feb 2006 Posts: 7
|
Posted: Mon Mar 13, 2006 8:48 pm Post subject: |
|
|
Sounds very similar to what is happening to me now zapata and the output also looks very familiar, I have also just tried vanilla-sources 2.6.16-rc6 with no luck
I swear I'll get this working one day =) _________________ -evolusion- |
|
Back to top |
|
|
stable n00b
Joined: 05 Mar 2006 Posts: 5
|
Posted: Mon Mar 13, 2006 11:56 pm Post subject: Step by step guide |
|
|
Alright I decided to write this guide in an attempt to help people getting Xgl+compiz running on their i915 chips.
First of all I would like to remind you all that the i915 is not exactly known for its performance (if you've tried to play recent games on it you know what I'm talking about), and therefore, don't expect a miracle. Compiz is usable on the i915 but probably not as fast as you'd like. I am currently using compiz in replacement for metacity, but after a few days I'm beginning to get tired of the scrolling slowdowns on large windows.
Second: Xgl acts like a proxy between your programs and the real Xorg server, so don't expect to have direct rendering inside Xgl, and this is not a problem as long as you still have direct rendering outside of Xgl.
Third: Ignore the frame rate reported by glxgears. The reason glxgears reports a much higher frame rate is because when using composite extensions all rendering is performed in the background and is only flushed every once in a while, so running glxgears inside Xgl is the same as running it outside of Xgl with something covering its window.
Fourth: I can only troubleshoot people who install Xgl and compiz the way I describe here and I will only cover the necessary steps to get Xgl+compiz running on your computers. For further instructions, please read the Xgl HowTo.
Fifth: I will assume you already have Xorg 7 installed. If not, please read this tutorial first.
Fetch coffeebuzz's overlay:
Code: | cd /usr/local
svn co http://www.tripthelight.net/xgloverlay |
Then add /usr/local/xgloverlay to your PORTDIR_OVERLAY in make.conf.
Edit your /etc/portage/package.keywords and add the following:
Code: | x11-libs/cairo ~x86
media-libs/glitz ~x86
media-libs/mesa ~x86
x11-base/xgl ~x86
x11-wm/compiz ~x86
x11-proto/glproto ~x86
x11-plugins/compiz-plugin-opacity ~x86
x11-misc/transset ~x86
x11-misc/trans-inactive ~x86 |
Edit your /etc/portage/package.unmask and add the following:
Emerge glitz and glproto:
Code: | emerge glitz glproto |
Emerge a copy of the vanilla 2.6.16 release candidate kernel:
Code: | ACCEPT_KEYWORDS="~x86" USE="-doc -symlink -build" emerge -1 =vanilla-sources-2.6.16_rc5 |
Replace the i915_drm.h header (this is necessary to compile mesa):
Code: | mv /usr/include/drm/i915_drm.h /usr/include/drm/i915_drm.h.old
cp /usr/src/linux-2.6.16-rc5/drivers/char/drm/i915_drm.h /usr/include/drm |
Backup the current mesa DRI drivers:
Code: | cp -r /usr/lib/xorg/modules/dri/ ~/dri-backup/ |
Emerge mesa:
Replace the new (buggy) drivers with the old ones (thanks to RoninTT for this tip):
Code: | cp -f ~/dri-backup/* /usr/lib/xorg/modules/dri/ |
Make sure you still have direct rendering now by running glxinfo on a terminal. If direct rendering is not available at this point, something went wrong.
Emerge Xgl and compiz:
Start a regular X session, open a terminal, and launch Xgl as follows:
Code: | Xgl :1 -ac -accel glx:pbuffer -accel xv:pbuffer & |
You should now have a new window on your screen. Alt+tab back to your terminal and type:
Code: | DISPLAY=:1 gnome-window-decorator &
DISPLAY=:1 compiz gconf & |
You will notice at this point that the Xgl window will turn black. This is a glitch, and it goes away if you switch to another workspace or cover it with another window. Try using the terminal from which you launched Xgl to force it to flush, notice how the window turns blue (the default compiz's background color) as your terminal passes over it. If you got to this point and you still have direct rendering outside of the Xgl window, congratulations, you've made it.
Now close the Xgl window and emerge the opacity plugin:
Code: | emerge compiz-plugin-opacity |
Press Alt+F2 and type "gconf-editor" (or run it from the terminal window WITH YOUR OWN PRIVILEGES, NOT ROOT'S), expand apps->compiz->general->allscreens->options, double click on active_plugins and start adding plugins in the following order: decoration, wobbly, fade, minimize, cube, rotate, zoom, scale, move, resize, place, switcher, and opacity.
At this point you won't need any additional help from me as the rest you can find on the Xgl HowTo.
Good luck, and if you have any questions, feel free to post them.
EDIT 14/03/06
- Modified the Xgl command line (had -accel xgl:pbuffer instead of glx:pbuffer).
Last edited by stable on Tue Mar 14, 2006 8:53 pm; edited 1 time in total |
|
Back to top |
|
|
zapata Tux's lil' helper
Joined: 26 Jun 2005 Posts: 82 Location: Hamburg / Germany
|
Posted: Tue Mar 14, 2006 1:09 am Post subject: |
|
|
@stable
first, thanks for your advice!
I try to do it your way, but when I start gconf-editor as normal user compiz is not in the menu. Only as root.
do you have an idea? |
|
Back to top |
|
|
stable n00b
Joined: 05 Mar 2006 Posts: 5
|
Posted: Tue Mar 14, 2006 10:48 am Post subject: |
|
|
Quote: | I try to do it your way, but when I start gconf-editor as normal user compiz is not in the menu. Only as root. |
Start Xgl and compiz with your own privileges, not root's. Xgl doesn't need root privileges to run. |
|
Back to top |
|
|
zapata Tux's lil' helper
Joined: 26 Jun 2005 Posts: 82 Location: Hamburg / Germany
|
Posted: Tue Mar 14, 2006 9:00 pm Post subject: |
|
|
It woks now fine with the newest coffee-overlay
I have problems wth some apps, but will see ...
thanks all for help!
Last edited by zapata on Wed Mar 15, 2006 5:15 pm; edited 1 time in total |
|
Back to top |
|
|
x.para Apprentice
Joined: 22 May 2005 Posts: 174 Location: CZ
|
Posted: Tue Mar 14, 2006 9:09 pm Post subject: |
|
|
Thanks Stable. Can you also tell what kernel version you are using? I don't mean linux-2.6.16-rc5 that is used for kernel heders. |
|
Back to top |
|
|
zcw100 n00b
Joined: 07 Mar 2006 Posts: 3
|
Posted: Tue Mar 14, 2006 10:24 pm Post subject: |
|
|
DRI => working
Xgl :1 -ac -accel xv:pbuffer -accel -glx:pbuffer & => works
DISPLAY=:1 gnome-window-decorator & => works
DISPLAY=:1 compiz gconf & => works
DISPLAY=:1 gnome-terminal & =>CRASH
XIO: fatal IO error 104 (Connection reset by peer) on X server ":1.0"
after 415 requests (410 known processed) with 0 events remaining.
gnome-window-decorator: Fatal IO error 104 (Connection reset by peer) on X server :1.0.
gnome-terminal: Fatal IO error 104 (Connection reset by peer) on X server :1.0.
[1] Segmentation fault Xgl :1 -ac -accel xgl:pbuffer -accel xv:pbuffer
[2]- Exit 1 DISPLAY=:1 gnome-window-decorator
[3]+ Exit 1 DISPLAY=:1 compiz gconf |
|
Back to top |
|
|
stable n00b
Joined: 05 Mar 2006 Posts: 5
|
Posted: Wed Mar 15, 2006 11:24 am Post subject: |
|
|
The latest releases of coffee's overlay seem to have problems, please avoid coffee's overlay releases 66 to at least 70. I don't know if those problems are in any way related with the reported crashes, but I had rendering problems with the latest Xgl snapshots on my desktop (radeon 9600 pro). Try rolling back to release 65 until these problems go away. To rollback, run:
Code: | cd /usr/local/xgloverlay
svn up -r 65 |
Then re-emerge libdrm, mesa, xgl, compiz, and compiz-plugin-opacity by this order.
About the kernel, I'm running Linux 2.6.15-suspend2-r6. The only thing you need from linux 2.6.16 is the header file.
Also please correct your Xgl command lines, it's -accel glx:pbuffer, not xgl:pbuffer (this was my fault). |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|