http://wiki.cchtml.com/api.php?action=feedcontributions&user=129.49.109.182&feedformat=atomcchtml.com - User contributions [en]2024-03-28T16:07:30ZUser contributionsMediaWiki 1.39.4http://wiki.cchtml.com/index.php?title=Frequently_Asked_Questions&diff=876Frequently Asked Questions2007-10-28T08:12:20Z<p>129.49.109.182: </p>
<hr />
<div>c4tracmon<br />
elrice<br />
cogeterlad<br />
==Installation==<br />
===How do I know fglrx is installed correctly?===<br />
There are several ways to check if fglrx is loaded and running.<br />
<br>1. Check your X.org or XFree86 log. You should see "DRI Initialization Successful."<br />
# less /var/log/Xorg.0.log<br />
or<br />
# less /var/log/XFree86.0.log<br />
2. Check glxinfo. You should see "direct" and not "indirect."<br />
# glxinfo | grep direct<br />
3. Check your kernel log. You should see fglrx messages near the bottom.<br />
# dmesg<br />
4. Check your modules. You should see fglrx loaded.<br />
# lsmod | grep fglrx<br />
*NOTE: [[Glxgears is not a Benchmark|glxgears]] is not a definite way of checking the installation of fglrx.<br />
<br />
=== Is the rebooting really necessary? ===<br />
<br />
No.<br />
<br />
However, rebooting is the easiest method to ensure that the kernel module(s) from the old driver are unloaded and the fglrx module is loaded instead. If you don't want to reboot for some reason, you may manually shut down Xorg, unload any old "drm", "radeon" or "fglrx" modules and then start Xorg again.<br />
<br />
==Kernel==<br />
===Why does fglrx not work for my bleeding-edge kernel?===<br />
The development process of the fglrx driver and the Linux kernel are not on the same level. The fglrx driver requires some special interactions with the kernel memory API and these tend to change between kernel versions. <br />
<br />
There is also an 11-12 week cycle required to develop, validate and test each release of an ATI driver <ref>http://www.phoronix.com/scan.php?page=article&item=735&num=1</ref>. ATI will only look to support the latest kernel that is officially out (no -rc or -git releases are supported) at the time they release a driver. Example: fglrx version A comes out Monday, but kernel version B comes out Tuesday. Kernel version B is not supported by fglrx version A. (but might be able to work anyway by doing a 'modprobe -f fglrx' in a shell)<br />
<br />
The binary part of ATI's kernel module has no explicit dependency on the Linux kernel. There are a set of source files that provide the glue to the kernel. This is where the dependency to different kernels exist. As a result, user contributed patches for newer kernels can often be found by searching [http://ati.cchtml.com Bugzilla].<br />
<br />
==X Configuration==<br />
===Composite Extension===<br />
If you've enabled transparency, and you've added the Composite extension to the xorg.conf file, the ATI driver will disable DRI.<br />
<br />
The only way to use 3D and the ATI OpenGL drivers is commenting the Option "Composite" "Enable" line.<br />
<br />
It may be necessary to put the following lines into xorg.conf:<br />
<br />
Section "Extensions"<br />
Option "Composite" "Disable"<br />
EndSection<br />
<br />
==Troubleshooting==<br />
* See [[Troubleshooting]] page.<br />
<br />
==See Also==<br />
*[http://ati.amd.com/products/catalyst/linux.html Official ATI Linux Driver FAQ]<br />
<br />
==References==<br />
<references/></div>129.49.109.182http://wiki.cchtml.com/index.php?title=XGL-Ubuntu&diff=3122XGL-Ubuntu2007-10-28T03:51:53Z<p>129.49.109.182: </p>
<hr />
<div>eltdarrololo<br />
== Xgl/Beryl on Ubuntu/Gnome - the Kombatant Way [updated 6/10/2006] ==<br />
<br />
So here we are, rewriting the whole guide, just because I found out a more bullet-proof way to do it. I've updated it too, and now instead of Compiz it uses Beryl, which imo is much better and has much more potential. <br />
<br />
Before we start, I want to make clear that these instructions are targeted for those people using the ATI Proprietary Driver ("fglrx") and having '''WORKING 3D ACCELERATION'''. This is configured in your xorg.conf. To make sure you are "accelerated", running with the new driver, try typing fglrxinfo in a terminal and see what you get. If it talks about ATI then awesome... if it talks about Mesa, you still don't have your driver setup properly (xorg.conf). We have an excellent how-to here in the wiki (here: [[Ubuntu]]), which works - try it out!<br />
<br />
* If you want the absolute newest stuff, then you're going to have to add some lines to your repositories. So open the /etc/apt/sources.list file as root, and add these lines in order to add the two repositories that are of interest here.<br />
<br />
#Beryl Repositories for Dapper Drake (Ubuntu 6.06)<br />
deb http://ubuntu.beryl-project.org/ dapper main<br />
<br />
or <br />
<br />
#Beryl Repositories for Edgy Eft (Ubuntu 6.10)<br />
deb http://ubuntu.beryl-project.org/ edgy main<br />
<br />
* To use the Ubuntu Dapper Drake Beryl SVN daily snapshots, add (also) those repositories:<br />
<br />
# Treviño's Beryl-SVN Ubuntu Repository<br />
# GPG key: 81836EBF<br />
deb http://3v1n0.tuxfamily.org dapper beryl-svn<br />
<br />
or<br />
<br />
# Treviño's Beryl-SVN Ubuntu Edgy Eft Repository<br />
# GPG key: 81836EBF<br />
deb http://3v1n0.tuxfamily.org edgy beryl-svn<br />
<br />
<br />
* After you add the repos in the sources.list file, issue the following commands:<br />
<br />
wget http://ubuntu.beryl-project.org/root@lupine.me.uk.gpg -O- | sudo apt-key add -<br />
<br />
sudo apt-get update<br />
<br />
sudo apt-get install xserver-xgl libgl1-mesa xserver-xorg libglitz-glx1 beryl emerald-themes<br />
<br />
* If during the apt-get installation you get the error ''"trying to overwrite `/usr/share/man/man1/Xserver.1x.gz', which is also in package xserver-xorg-core"'' issue the following two commands to continue:<br />
<br />
sudo dpkg-divert --package xserver-xorg-core --divert /usr/share/man/man1/Xserver.1x.gz.xgl --rename /usr/share/man/man1/Xserver.1x.gz<br />
<br />
sudo apt-get -f install<br />
<br />
* Instead of messing with gdm.conf and gdm.conf-custom, we're going to do something better. From the terminal, issue the command:<br />
<br />
sudo gedit /usr/bin/startxgl.sh<br />
<br />
and add these as contents:<br />
<br />
Xgl -fullscreen :1 -ac -accel glx:pbuffer -accel xv:pbuffer & <br />
sleep 2 && DISPLAY=:1 exec gnome-session<br />
<br />
Save it, and then issue the command:<br />
<br />
sudo chmod 755 /usr/bin/startxgl.sh<br />
<br />
* From the terminal again:<br />
<br />
sudo gedit /usr/share/xsessions/xgl.desktop<br />
<br />
and add this as its contents:<br />
<br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Name=XGL<br />
Exec=/usr/bin/startxgl.sh<br />
Icon=<br />
Type=Application<br />
<br />
* So here's the trick. What we've done is to add a new session in GDM. This means that, when GDM loads, you can select the "Xgl" session instead of the normal session you usually use, and it'll load XGL. That way, if something goes horribly wrong, you can simply reboot, and when gdm loads , you will be able to select your normal (and working) session again without editing files all the time. <br />
<br />
* After all that, we are ready. Reboot your machine (yes, reboot) and when GDM loads, look at the sessions; if you see an "XGL" session there, everything's going according to plan. Load it up (make it your default session, if you want to), and hopefully everything will be working. We're half-way there anyway. All you need to do now, is open the System->Preferences->Sessions->Startup Programs and add the following:<br />
<br />
xmodmap /usr/share/xmodmap/xmodmap.us<br />
gnome-settings-daemon<br />
beryl-manager<br />
<br />
Of course, if you are using a different locale, you can substitute xmodmap.us with your appropriate file. <br />
<br />
* Logout and login again. If everything is running along happily, you'll see the beryl splash screen, and the emerald-like icon of beryl in your tray. If beryl doesn't load initially, just right click the icon, and Select Window Manager->Beryl. Now right click the icon again, and load up Emerald (the window decorator) and choose the theme that you like best. You can also tinker with the settings at your heart's content.<br />
<br />
Hopefully somebody will find all these useful - I will also update this with more suggested information and tips, to cover more potential problems/configurations.<br />
Any additional suggestions will be more than welcome.<br />
-----------------<br />
<br />
=== Has anyone got this working on feisty herd 4 ? ===<br />
yes<br />
<br />
yes: after first reboot<br />
no: since then.<br />
and yes: again then. you need to activate desktop effects in ubuntu. this does the job.<br />
<br />
=== Feedback (7.04) ===<br />
Newbie: The Part about the Session Manager is unclear and I think my error (the No above) is related to it.<br />
<br />
Newbie: How can you prove if the installation has been done right to a certain extend? My Problem is, after the first reboot it worked. Then while starting over again it did not.<br />
<br />
Newbie: How can I remove a compelte Sesssion so I am able to start over again?</div>129.49.109.182