| 1 |
On Saturday 20 January 2007 00:31, Jan Stępień wrote: |
| 2 |
> After launching X server with this setting it results in using Mesa |
| 3 |
> instead of fglrx, which means NO direct rendering, as proved by glxinfo. |
| 4 |
> Beryl cannot be launched because of lack of DRI. |
| 5 |
> |
| 6 |
> If I turn composite off, the X server is driven by fglrx, which gives me |
| 7 |
> direct rendering and Beryl's refusal to start because of lack of |
| 8 |
> composite extension. |
| 9 |
> |
| 10 |
> It's all quite suspicious, taking into account fact that Radeons are |
| 11 |
> listed at the website above as video cards able of running AIGLX. But |
| 12 |
> maybe only on FOSS drivers...? |
| 13 |
> |
| 14 |
It might be a proprietary drive issue. I use an intel chipset - composite on, |
| 15 |
direct rendering, AIGLX and Beryl all working together. Just as the wiki |
| 16 |
tells you to do. |
| 17 |
|
| 18 |
> Afterwards I've downloaded xlaunch. When trying to launch an app (in |
| 19 |
> this case armyops) starting xlaunch in a terminal in an existing X |
| 20 |
> server the screen blacks out, probably trying to launch new X session |
| 21 |
> and suddenly restarts GDM, meanwhile killing my original session. |
| 22 |
> |
| 23 |
|
| 24 |
> I've also tried to use xlaunch in a text console having my previous X |
| 25 |
> server turned on. Results are the same. |
| 26 |
> |
| 27 |
> Have you got any suggestions? |
| 28 |
> |
| 29 |
Try turning off GDM, logging in via console and then running startx. Then from |
| 30 |
inside that xserver use xlaunch to start the game, see if the results are any |
| 31 |
different. Xlaunch works perfectly for me from within KDE or enlightenment, |
| 32 |
although I've never had GDM running (or even installed) on this machine. |
| 33 |
|
| 34 |
- Noven |
| 35 |
-- |
| 36 |
>-- Novensiles divi Flamen --< |
| 37 |
>---- Miles Militis Fons ----< |
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-user@g.o mailing list |
Archives