<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>k3mist™ &#187; fglrx</title>
	<atom:link href="http://k3mist.com/category/fglrx/feed/" rel="self" type="application/rss+xml" />
	<link>http://k3mist.com</link>
	<description>Development, Design &#38; System Administration</description>
	<lastBuildDate>Sat, 12 Sep 2009 15:40:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>ATI Catalyst 9.9 / fglrx 8.650 Installation</title>
		<link>http://k3mist.com/linux/ati-catalyst-9-9-fglrx-8-650-installation/</link>
		<comments>http://k3mist.com/linux/ati-catalyst-9-9-fglrx-8-650-installation/#comments</comments>
		<pubDate>Sat, 12 Sep 2009 15:27:33 +0000</pubDate>
		<dc:creator>k3mist</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[fglrx]]></category>
		<category><![CDATA[ati catalyst]]></category>
		<category><![CDATA[fglrx installation]]></category>
		<category><![CDATA[fglrx removal]]></category>

		<guid isPermaLink="false">http://k3mist.com/?p=188</guid>
		<description><![CDATA[<p>When upgrading the fglrx driver, <em><strong>don&#8217;t get lazy</strong></em> about removing the previous version. Besides the old configuration possibly still in use after a reboot, you get <a href="http://k3mist.com/linux/xorg-memory-leak-fix-for-jaunty-904-ati-proprietary-fglrx/">serious memory leaks in Xorg caused by the ATI Catalyst driver</a> that resemble the same leak you get when using the driver provided by envyng.</p>
<p>Removal and installation is really straight forward and there is only a few extra steps. I keep my drivers in separate folders for each version. All commands are displayed as if you were in the working folder for that driver and ONLY that driver version.</p>
<p><strong>Generate the fglrx/catalyst drivers for your distribution</strong><br />
<a href="http://wiki.cchtml.com/index.php/Category:Distributions" target="_blank">Supported distro&#8217;s found here.</a><br />
<code>sh ati-driver-installer-* --buildpkg Distribution/codename</code></p>
<p><strong>Backup your xorg.conf (just in case, re-configuring xorg sucks!) and remove the previous fglrx drivers</strong><br />
<code>sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.bak<br />
sudo apt-get purge xorg-driver-fglrx fglrx-kernel-source fglrx-modaliases fglrx-amdcccle<br />
# if /etc/ati still exists, remove it!<br />
sudo rm -rf /etc/ati/</code></p>
<p>Now reboot and when restarting <strong>do not boot into the GUI</strong>. Xorg will be looking for your fglrx driver and it is now obviously gone, so you will either lock-up or it may recover nicely and allow you to enter into a low graphics mode. Either way, boot into a terminal window. On Ubuntu you can enter the recovery console.</p>
<p><strong>Now from terminal install the new fglrx/catalyst driver</strong><br />
<code>sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb </code></p>
<p>Now reboot from terminal and enter the GUI. You will have to reconfigure any settings you made in the previous Catalyst driver. <a href="http://k3mist.com/linux/contrast-brightness-gamma-linux/">fglrx/catalyst brightness, contrast, gamma howto.</a></p>
<p>If you happen to have any issues booting back into the GUI. Go back to the terminal and remove your previous xorg.conf. and <a href="http://wiki.cchtml.com/index.php/Ubuntu_Jaunty_Installation_Guide#6._Generate_a_new_.2Fetc.2FXorg.conf_file" target="_blank">follow these instructions for generating a new one.</a></p>
<p>A more detailed walk-through can always be found at <a href="http://wiki.cchtml.com/" target="_blank">http://wiki.cchtml.com/</a></p>
]]></description>
			<content:encoded><![CDATA[<p>When upgrading the fglrx driver, <em><strong>don&#8217;t get lazy</strong></em> about removing the previous version. Besides the old configuration possibly still in use after a reboot, you get <a href="http://k3mist.com/linux/xorg-memory-leak-fix-for-jaunty-904-ati-proprietary-fglrx/">serious memory leaks in Xorg caused by the ATI Catalyst driver</a> that resemble the same leak you get when using the driver provided by envyng.</p>
<p>Removal and installation is really straight forward and there is only a few extra steps. I keep my drivers in separate folders for each version. All commands are displayed as if you were in the working folder for that driver and ONLY that driver version.</p>
<p><strong>Generate the fglrx/catalyst drivers for your distribution</strong><br />
<a href="http://wiki.cchtml.com/index.php/Category:Distributions" target="_blank">Supported distro&#8217;s found here.</a><br />
<code>sh ati-driver-installer-* --buildpkg Distribution/codename</code></p>
<p><strong>Backup your xorg.conf (just in case, re-configuring xorg sucks!) and remove the previous fglrx drivers</strong><br />
<code>sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.bak<br />
sudo apt-get purge xorg-driver-fglrx fglrx-kernel-source fglrx-modaliases fglrx-amdcccle<br />
# if /etc/ati still exists, remove it!<br />
sudo rm -rf /etc/ati/</code></p>
<p>Now reboot and when restarting <strong>do not boot into the GUI</strong>. Xorg will be looking for your fglrx driver and it is now obviously gone, so you will either lock-up or it may recover nicely and allow you to enter into a low graphics mode. Either way, boot into a terminal window. On Ubuntu you can enter the recovery console.</p>
<p><strong>Now from terminal install the new fglrx/catalyst driver</strong><br />
<code>sudo dpkg -i xorg-driver-fglrx_*.deb fglrx-kernel-source_*.deb fglrx-amdcccle_*.deb </code></p>
<p>Now reboot from terminal and enter the GUI. You will have to reconfigure any settings you made in the previous Catalyst driver. <a href="http://k3mist.com/linux/contrast-brightness-gamma-linux/">fglrx/catalyst brightness, contrast, gamma howto.</a></p>
<p>If you happen to have any issues booting back into the GUI. Go back to the terminal and remove your previous xorg.conf. and <a href="http://wiki.cchtml.com/index.php/Ubuntu_Jaunty_Installation_Guide#6._Generate_a_new_.2Fetc.2FXorg.conf_file" target="_blank">follow these instructions for generating a new one.</a></p>
<p>A more detailed walk-through can always be found at <a href="http://wiki.cchtml.com/" target="_blank">http://wiki.cchtml.com/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://k3mist.com/linux/ati-catalyst-9-9-fglrx-8-650-installation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adjusting Contrast, Brightness and Gamma on fglrx 9.5+</title>
		<link>http://k3mist.com/linux/adjusting-contrast-brightness-and-gamma-on-fglrx-95/</link>
		<comments>http://k3mist.com/linux/adjusting-contrast-brightness-and-gamma-on-fglrx-95/#comments</comments>
		<pubDate>Wed, 12 Aug 2009 19:01:59 +0000</pubDate>
		<dc:creator>k3mist</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[fglrx]]></category>
		<category><![CDATA[ati proprietary]]></category>
		<category><![CDATA[brightness]]></category>
		<category><![CDATA[contrast]]></category>
		<category><![CDATA[fglrx_xgamma]]></category>
		<category><![CDATA[gamma]]></category>
		<category><![CDATA[jaunty 9.04]]></category>
		<category><![CDATA[xgamma]]></category>

		<guid isPermaLink="false">http://k3mist.com/?p=162</guid>
		<description><![CDATA[<p>ATI has made a change in their fglrx catalyst drivers (9.5+) where setting the gamma in xorg.conf no longer works and is ignored when starting.</p>
<p>In my <a href="http://k3mist.com/linux/contrast-brightness-gamma-linux/">previous post</a> I went over setting and making these adjustments. The previous methods for Contrast and Brightness remain. However for gamma, the only way and previously existing method is now using fglrx_xgamma.</p>
<p>In terminal;</p>
<p><code>fglrx_xgamma -c 0 -gamma .85</code></p>
<p>This setting will be immediately applied and also after restarting.</p>
]]></description>
			<content:encoded><![CDATA[<p>ATI has made a change in their fglrx catalyst drivers (9.5+) where setting the gamma in xorg.conf no longer works and is ignored when starting.</p>
<p>In my <a href="http://k3mist.com/linux/contrast-brightness-gamma-linux/">previous post</a> I went over setting and making these adjustments. The previous methods for Contrast and Brightness remain. However for gamma, the only way and previously existing method is now using fglrx_xgamma.</p>
<p>In terminal;</p>
<p><code>fglrx_xgamma -c 0 -gamma .85</code></p>
<p>This setting will be immediately applied and also after restarting.</p>
]]></content:encoded>
			<wfw:commentRss>http://k3mist.com/linux/adjusting-contrast-brightness-and-gamma-on-fglrx-95/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Xorg Memory Leak Fix for Jaunty 9.04 ATI Proprietary fglrx</title>
		<link>http://k3mist.com/linux/xorg-memory-leak-fix-for-jaunty-904-ati-proprietary-fglrx/</link>
		<comments>http://k3mist.com/linux/xorg-memory-leak-fix-for-jaunty-904-ati-proprietary-fglrx/#comments</comments>
		<pubDate>Wed, 13 May 2009 21:48:04 +0000</pubDate>
		<dc:creator>k3mist</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[fglrx]]></category>
		<category><![CDATA[ati proprietary]]></category>
		<category><![CDATA[jaunty 9.04]]></category>
		<category><![CDATA[xorg memory leak fix]]></category>

		<guid isPermaLink="false">http://k3mist.com/?p=84</guid>
		<description><![CDATA[<p>Memory leak fixed on my sony vaio laptop with an HD3400 series. NOT completely, xorg will still leak over time (about 60mb over 8 hours and I think some of this memory is re-used for effects which will not increase the memory any further when opening, closing, etc). The change is DRASTIC compared to what I was seeing. Before this xorg would leak anywhere between 500-700mb over 4 hours of use. <a href="https://bugs.launchpad.net/ubuntu/+bug/353800/comments/20" target="_blank"></a></p>
<p><span id="more-84"></span>I downloaded the official driver from ATI&#8217;s website. 9.4 catalyst.</p>
<p>I followed the instructions to install the drivers manually from the link below line for line;<br />
When I built the packages I had the previous driver still installed from envyng. I also left compiz running with all my desktop effects enabled. I&#8217;m not sure how relevant that is, but it is what I did.</p>
<p>This is really not for the faint of heart! Be cautious and patient, READ CAREFULLY and follow the instructions word for word! If you mess this up, ubuntu will more than likely not be bootable into the GUI after. If something is wrong, ubuntu will freeze at boot probably with some messed up crap on the screen. You will have to remove the fglrx packages from the recovery terminal. (which happened to me once already).<br />
<a href="http://wiki.cchtml.com/index.php/Ubuntu_Jaunty_Installation_Guide#Installing_the_drivers_manually" target="_blank">http://wiki.cchtml.com/index.php/Ubuntu_Jaunty_Installation_Guide#Installing_the_drivers_manually</a></p>
<p>After installation was complete, I did not reboot immediately.<br />
I backed up first <code>/etc/ati/amdpcsdb</code> and then removed it from that directory.<br />
Then I rebooted&#8230;</p>
<p>After reboot, i DID NOT do <code>aticonfig --initial</code> OR <code>aticonfig --input=/etc/X11/xorg.conf</code>. And I don&#8217;t plan on it.</p>
<p><a href="http://launchpadlibrarian.net/26487650/xorg.conf" target="_blank">My xorg.conf</a> is a mess at the moment and not complete, but I attached it anyway since the video card driver settings I am using are there and <em>are</em> complete. But I&#8217;ve read that without running <code>aticonfig --input=/etc/X11/xorg.conf</code>, the ati driver doesn&#8217;t read the xorg.conf settings. Not sure one way or the other right now honestly. But I&#8217;m not running it.</p>
<p>For testing, I opened firefox which had 12 tabs, system monitor, nautilus, terminal with transparency, netbeans 6.7 beta and evolution. I also ran glxgears and I am seeing 500-600 FPS more! glxgears is now up to 1500-1600 on HD3400 Series.</p>
<p>I booted with Xorg at 65mb, after running these applications and glxgears. Also maximizing and minimizing each window repeatedly since this clearly showed the leak the most, Xorg is freeing up memory and garbage collecting quite well! Xorg is now at 76-77mb. Open is firefox with 5 tabs and system monitor. Normally before, Xorg would be at 130-170mb at least after this. Especially after minimize and maximize so many times. So at this point, an 11-12mb increase after all that with windows still open is VERY acceptable compared to before.</p>
<p><a href="https://bugs.launchpad.net/ubuntu/+bug/353800/comments/20" target="_blank">I posted this info on launchpad a couple days ago.</a></p>
<p>Anyway, Good luck!</p>
<p>Launchpad Link for this bug;<br />
<a href="https://bugs.launchpad.net/ubuntu/+bug/353800/" target="_blank">https://bugs.launchpad.net/ubuntu/+bug/353800/</a></p>
]]></description>
			<content:encoded><![CDATA[<p>Memory leak fixed on my sony vaio laptop with an HD3400 series. NOT completely, xorg will still leak over time (about 60mb over 8 hours and I think some of this memory is re-used for effects which will not increase the memory any further when opening, closing, etc). The change is DRASTIC compared to what I was seeing. Before this xorg would leak anywhere between 500-700mb over 4 hours of use. <a href="https://bugs.launchpad.net/ubuntu/+bug/353800/comments/20" target="_blank"></a></p>
<p><span id="more-84"></span>I downloaded the official driver from ATI&#8217;s website. 9.4 catalyst.</p>
<p>I followed the instructions to install the drivers manually from the link below line for line;<br />
When I built the packages I had the previous driver still installed from envyng. I also left compiz running with all my desktop effects enabled. I&#8217;m not sure how relevant that is, but it is what I did.</p>
<p>This is really not for the faint of heart! Be cautious and patient, READ CAREFULLY and follow the instructions word for word! If you mess this up, ubuntu will more than likely not be bootable into the GUI after. If something is wrong, ubuntu will freeze at boot probably with some messed up crap on the screen. You will have to remove the fglrx packages from the recovery terminal. (which happened to me once already).<br />
<a href="http://wiki.cchtml.com/index.php/Ubuntu_Jaunty_Installation_Guide#Installing_the_drivers_manually" target="_blank">http://wiki.cchtml.com/index.php/Ubuntu_Jaunty_Installation_Guide#Installing_the_drivers_manually</a></p>
<p>After installation was complete, I did not reboot immediately.<br />
I backed up first <code>/etc/ati/amdpcsdb</code> and then removed it from that directory.<br />
Then I rebooted&#8230;</p>
<p>After reboot, i DID NOT do <code>aticonfig --initial</code> OR <code>aticonfig --input=/etc/X11/xorg.conf</code>. And I don&#8217;t plan on it.</p>
<p><a href="http://launchpadlibrarian.net/26487650/xorg.conf" target="_blank">My xorg.conf</a> is a mess at the moment and not complete, but I attached it anyway since the video card driver settings I am using are there and <em>are</em> complete. But I&#8217;ve read that without running <code>aticonfig --input=/etc/X11/xorg.conf</code>, the ati driver doesn&#8217;t read the xorg.conf settings. Not sure one way or the other right now honestly. But I&#8217;m not running it.</p>
<p>For testing, I opened firefox which had 12 tabs, system monitor, nautilus, terminal with transparency, netbeans 6.7 beta and evolution. I also ran glxgears and I am seeing 500-600 FPS more! glxgears is now up to 1500-1600 on HD3400 Series.</p>
<p>I booted with Xorg at 65mb, after running these applications and glxgears. Also maximizing and minimizing each window repeatedly since this clearly showed the leak the most, Xorg is freeing up memory and garbage collecting quite well! Xorg is now at 76-77mb. Open is firefox with 5 tabs and system monitor. Normally before, Xorg would be at 130-170mb at least after this. Especially after minimize and maximize so many times. So at this point, an 11-12mb increase after all that with windows still open is VERY acceptable compared to before.</p>
<p><a href="https://bugs.launchpad.net/ubuntu/+bug/353800/comments/20" target="_blank">I posted this info on launchpad a couple days ago.</a></p>
<p>Anyway, Good luck!</p>
<p>Launchpad Link for this bug;<br />
<a href="https://bugs.launchpad.net/ubuntu/+bug/353800/" target="_blank">https://bugs.launchpad.net/ubuntu/+bug/353800/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://k3mist.com/linux/xorg-memory-leak-fix-for-jaunty-904-ati-proprietary-fglrx/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>ATI Proprietary fglrx Minimize/Maximize Fix for Jaunty 9.04</title>
		<link>http://k3mist.com/linux/ati-proprietary-fglrx-minimizemaximize-fix-for-jaunty-904/</link>
		<comments>http://k3mist.com/linux/ati-proprietary-fglrx-minimizemaximize-fix-for-jaunty-904/#comments</comments>
		<pubDate>Wed, 13 May 2009 21:34:16 +0000</pubDate>
		<dc:creator>k3mist</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[fglrx]]></category>
		<category><![CDATA[ati proprietary]]></category>
		<category><![CDATA[fglrx lag fix]]></category>
		<category><![CDATA[jaunty 9.04]]></category>

		<guid isPermaLink="false">http://k3mist.com/?p=79</guid>
		<description><![CDATA[<p>After a few weeks, a patch has been released a few days ago that fixes the fglrx lag when minimizing, maximizing or opening a window on ubuntu jaunty 9.04. The lag was severe freezing the entire desktop for 1-3 seconds, almost making desktop effects unbearable to use.</p>
<p>For those who would prefer to compile xorg;<br />
<a href="http://launchpadlibrarian.net/26424345/107_fedora_dont_backfill_bg_none.patch">http://launchpadlibrarian.net/26424345/107_fedora_dont_backfill_bg_none.patch</a></p>
<p>PPA is available here;<br />
<a href="https://edge.launchpad.net/~ubuntu-x-swat/+archive/xserver-no-backfill" target="_blank">https://edge.launchpad.net/~ubuntu-x-swat/+archive/xserver-no-backfill</a></p>
<p>Launchpad link for this bug;<br />
<a href="https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/351186" target="_blank">https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/351186</a></p>
]]></description>
			<content:encoded><![CDATA[<p>After a few weeks, a patch has been released a few days ago that fixes the fglrx lag when minimizing, maximizing or opening a window on ubuntu jaunty 9.04. The lag was severe freezing the entire desktop for 1-3 seconds, almost making desktop effects unbearable to use.</p>
<p>For those who would prefer to compile xorg;<br />
<a href="http://launchpadlibrarian.net/26424345/107_fedora_dont_backfill_bg_none.patch">http://launchpadlibrarian.net/26424345/107_fedora_dont_backfill_bg_none.patch</a></p>
<p>PPA is available here;<br />
<a href="https://edge.launchpad.net/~ubuntu-x-swat/+archive/xserver-no-backfill" target="_blank">https://edge.launchpad.net/~ubuntu-x-swat/+archive/xserver-no-backfill</a></p>
<p>Launchpad link for this bug;<br />
<a href="https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/351186" target="_blank">https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/351186</a></p>
]]></content:encoded>
			<wfw:commentRss>http://k3mist.com/linux/ati-proprietary-fglrx-minimizemaximize-fix-for-jaunty-904/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adjusting Contrast, Brightness and Gamma on Linux. ATI Proprietary Driver (fglrx).</title>
		<link>http://k3mist.com/linux/contrast-brightness-gamma-linux/</link>
		<comments>http://k3mist.com/linux/contrast-brightness-gamma-linux/#comments</comments>
		<pubDate>Mon, 11 May 2009 20:46:20 +0000</pubDate>
		<dc:creator>k3mist</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[fglrx]]></category>
		<category><![CDATA[ati proprietary]]></category>
		<category><![CDATA[brightness]]></category>
		<category><![CDATA[contrast]]></category>
		<category><![CDATA[gamma]]></category>
		<category><![CDATA[jaunty 9.04]]></category>
		<category><![CDATA[xgamma]]></category>

		<guid isPermaLink="false">http://k3mist.com/?p=69</guid>
		<description><![CDATA[<p>If you have the ati driver installed correctly and have xorg setup correctly, you can easily change the brightness, contrast and gamma on linux.</p>
<p>I could not find anywhere on google a single search result except for setting gamma, so I post this here.<br />
<span id="more-69"></span><br />
To change brightness and contrast you do this through aticonfig. These settings are saved as you change them and are irreversible without deleting <code>/etc/ati/amdpcsdb</code> first. I recommend making small increments and make sure your syntax is correct.</p>
<p>First you need to determine what monitor(s) types are connected. With aticonfig in terminal try <code>aticonfig --query-monitor</code>. If you get the error it is not supported when RandR is enabled. You can then try <code>xrandr</code>. This will return the screen # and types. From xrandr you should be able to pick out what display type you need for aticonfig, the naming will be different.</p>
<p>aticonfig requires the following display type options in the string <code>crt1, lvds, tv, cv, tmds1, crt2, tmds2, tmds2i, dfp3, dfp4, dfp5, dfp6</code>. So you can try one of these until you get the right one. Querying incorrect display type does no harm. Typically, lvds is going to be your LCD.</p>
<p>To determine the contrast and brightness you are using type the following below in a terminal, lvds is the display type and in the output, value is the current setting;</p>
<p>Contrast<br />
<code>aticonfig --query-dispattrib=lvds,contrast</code><br />
Which outputs for me:<br />
<code> contrast attribute information of monitor lvds :<br />
default:100, value:85, min:0, max:200, step:1</code></p>
<p>Brightness<br />
<code>aticonfig --query-dispattrib=lvds,brightness</code><br />
Which outputs for me:<br />
<code> brightness attribute information of monitor lvds :<br />
default:0, value:-3, min:-100, max:100, step:1</code></p>
<p>Notice how brightness is min value of -100 and max 100 while contrast is a min value of 0 and max 200. So be careful.</p>
<p>To set these, be very careful of typos or accidentally setting a null value. Your screen could very easily go black:<br />
<code>aticonfig --set-dispattrib=lvds,contrast:100</code><br />
Where 100 is the contrast value you are setting. And the same goes for brightness:<br />
<code>aticonfig --set-dispattrib=lvds,brightness:0</code></p>
<p><strong>UPDATE:</strong> <a href="http://k3mist.com/linux/adjusting-contrast-brightness-and-gamma-on-fglrx-95/">Use fglrx_xgamma for setting gamma.</a> Xorg.conf gamma no longer works in fglrx versions 9.5 and later.</p>
<p><span style="text-decoration: line-through;">Gamma is not supported anywhere I can see in the man for aticonfig. So for gamma you can see the current setting through xserver by typing <code>xgamma</code>. It should return values for red, blue and green.</span></p>
<p><span style="text-decoration: line-through;">xgamma supports decimal values like 0.85 or 1.0. 1.0 being default. If you want to change the gamma for all 3, type <code>xgamma -gamma 0.85</code> or whatever value you want. If you want to change individual colors, you have to do it one by one. Replace -gamma with <code>-rgamma, -ggamma or -bgamma</code>. Red, green, blue respectively.</span></p>
<p><span style="text-decoration: line-through;">The thing about xgamma, these settings are only stored and saved for your current user/boot session. To make these settings permanent, you will need to edit /etc/X11/xorg.conf. If your xorg.conf is not setup, you should <a href="http://www.x.org/archive/X11R6.9.0/doc/html/xorg.conf.5.html" target="_blank">get started reading here</a>.</span></p>
<p><span style="text-decoration: line-through;">So open xorg.conf as sudo in your text editor of choice. For gnome users, one of my fav commands is <code>gksu gedit /ect/X11/xorg.conf &amp;disown</code>.</span></p>
<p><span style="text-decoration: line-through;">Next goto <code>Section "Monitor"</code>. Inside this section simply add your gamma setting with, <code>Gamma 0.85 0.85 0.85 </code> (red, blue, green). Or you can put a single value for all 3. Save and exit.</span></p>
<p>That&#8217;s it, pretty straight forward I hope.</p>
]]></description>
			<content:encoded><![CDATA[<p>If you have the ati driver installed correctly and have xorg setup correctly, you can easily change the brightness, contrast and gamma on linux.</p>
<p>I could not find anywhere on google a single search result except for setting gamma, so I post this here.<br />
<span id="more-69"></span><br />
To change brightness and contrast you do this through aticonfig. These settings are saved as you change them and are irreversible without deleting <code>/etc/ati/amdpcsdb</code> first. I recommend making small increments and make sure your syntax is correct.</p>
<p>First you need to determine what monitor(s) types are connected. With aticonfig in terminal try <code>aticonfig --query-monitor</code>. If you get the error it is not supported when RandR is enabled. You can then try <code>xrandr</code>. This will return the screen # and types. From xrandr you should be able to pick out what display type you need for aticonfig, the naming will be different.</p>
<p>aticonfig requires the following display type options in the string <code>crt1, lvds, tv, cv, tmds1, crt2, tmds2, tmds2i, dfp3, dfp4, dfp5, dfp6</code>. So you can try one of these until you get the right one. Querying incorrect display type does no harm. Typically, lvds is going to be your LCD.</p>
<p>To determine the contrast and brightness you are using type the following below in a terminal, lvds is the display type and in the output, value is the current setting;</p>
<p>Contrast<br />
<code>aticonfig --query-dispattrib=lvds,contrast</code><br />
Which outputs for me:<br />
<code> contrast attribute information of monitor lvds :<br />
default:100, value:85, min:0, max:200, step:1</code></p>
<p>Brightness<br />
<code>aticonfig --query-dispattrib=lvds,brightness</code><br />
Which outputs for me:<br />
<code> brightness attribute information of monitor lvds :<br />
default:0, value:-3, min:-100, max:100, step:1</code></p>
<p>Notice how brightness is min value of -100 and max 100 while contrast is a min value of 0 and max 200. So be careful.</p>
<p>To set these, be very careful of typos or accidentally setting a null value. Your screen could very easily go black:<br />
<code>aticonfig --set-dispattrib=lvds,contrast:100</code><br />
Where 100 is the contrast value you are setting. And the same goes for brightness:<br />
<code>aticonfig --set-dispattrib=lvds,brightness:0</code></p>
<p><strong>UPDATE:</strong> <a href="http://k3mist.com/linux/adjusting-contrast-brightness-and-gamma-on-fglrx-95/">Use fglrx_xgamma for setting gamma.</a> Xorg.conf gamma no longer works in fglrx versions 9.5 and later.</p>
<p><span style="text-decoration: line-through;">Gamma is not supported anywhere I can see in the man for aticonfig. So for gamma you can see the current setting through xserver by typing <code>xgamma</code>. It should return values for red, blue and green.</span></p>
<p><span style="text-decoration: line-through;">xgamma supports decimal values like 0.85 or 1.0. 1.0 being default. If you want to change the gamma for all 3, type <code>xgamma -gamma 0.85</code> or whatever value you want. If you want to change individual colors, you have to do it one by one. Replace -gamma with <code>-rgamma, -ggamma or -bgamma</code>. Red, green, blue respectively.</span></p>
<p><span style="text-decoration: line-through;">The thing about xgamma, these settings are only stored and saved for your current user/boot session. To make these settings permanent, you will need to edit /etc/X11/xorg.conf. If your xorg.conf is not setup, you should <a href="http://www.x.org/archive/X11R6.9.0/doc/html/xorg.conf.5.html" target="_blank">get started reading here</a>.</span></p>
<p><span style="text-decoration: line-through;">So open xorg.conf as sudo in your text editor of choice. For gnome users, one of my fav commands is <code>gksu gedit /ect/X11/xorg.conf &amp;disown</code>.</span></p>
<p><span style="text-decoration: line-through;">Next goto <code>Section "Monitor"</code>. Inside this section simply add your gamma setting with, <code>Gamma 0.85 0.85 0.85 </code> (red, blue, green). Or you can put a single value for all 3. Save and exit.</span></p>
<p>That&#8217;s it, pretty straight forward I hope.</p>
]]></content:encoded>
			<wfw:commentRss>http://k3mist.com/linux/contrast-brightness-gamma-linux/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Ubuntu Jaunty: ATI Restricted Proprietary FGLRX Driver, Direct Rendering, Mobility Radeon HD Series</title>
		<link>http://k3mist.com/linux/ubuntu-jaunty-ati-restricted-proprietary-fglrx-driver-direct-rendering-mobility-radeon-hd-series/</link>
		<comments>http://k3mist.com/linux/ubuntu-jaunty-ati-restricted-proprietary-fglrx-driver-direct-rendering-mobility-radeon-hd-series/#comments</comments>
		<pubDate>Sat, 02 May 2009 14:43:38 +0000</pubDate>
		<dc:creator>k3mist</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[fglrx]]></category>
		<category><![CDATA[ati proprietary]]></category>
		<category><![CDATA[direct rendering]]></category>
		<category><![CDATA[jaunty 9.04]]></category>
		<category><![CDATA[ubuntu jaunty]]></category>

		<guid isPermaLink="false">http://k3mist.com/?p=50</guid>
		<description><![CDATA[<p>To start off I am no expert. I am a windows convert about a week ago now. However, I&#8217;m grabbing Linux by the horns and loving it!</p>
<p>The reason I am posting this is because it took me several hours to figure this out. I could not find in one place an organized concise approach. I&#8217;d imagine the experts already know this info but for the new Linux users, I can see this being helpful and also as a reference for me in the future <img src='http://k3mist.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>This does not fix the current <a href="https://bugs.launchpad.net/ubuntu/+bug/353800/" target="_blank">memory leak in Xorg</a> or the <a href="https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/351186" target="_blank">slow sluggishness of compiz when minimizing, maximizing or resizing</a>. Sadly, I&#8217;m experiencing both of these issues on Jaunty with the ATI Driver, I have not tried the open source ATI Driver yet.</p>
<p>I went through many installations and removals of the ati driver during this process. I will only explain how and what I did to actually get the driver working with direct rendering enabled.</p>
<p><span id="more-50"></span><strong>Let&#8217;s begin:</strong></p>
<p>You can see if you have direct rendering working by typing:</p>
<pre>glxinfo | grep direct</pre>
<p>If you get &#8220;direct rendering: Yes&#8221; you do not need to do this and your drivers and card are configured correctly. Otherwise, if it says no and possibly one of two messages after the &#8220;no&#8221;. Your xorg and driver settings are not configured correctly.</p>
<p>After a complete failure of the drivers off ATI&#8217;s website not working, even after compiling the .deb packages and installing everything that was necessary, my Linux installation no longer booted in the GUI.</p>
<p>The first thing I did was boot into recovery and remove ALL FGLRX packages from my installation. If you get permission denied for any commands, use sudo. You can see what packages are installed by typing this:</p>
<pre>dpkg -l | grep fglrx</pre>
<p>If any of the following packages are installed they will need removed:<br />
<strong>xorg-driver-fglrx, fglrx-kernel-source, fglrx-modaliases, fglrx-amdcccle</strong></p>
<p>You can remove these with the following command, leave out any packages that are not installed;</p>
<pre>apt-get purge xorg-driver-fglrx fglrx-kernel-source fglrx-modaliases fglrx-amdcccle</pre>
<p>Purge ensures that all files and directories created by the packages are removed. After successful purge I typed reboot. I was back in the GUI now in an 800&#215;600 screen, which was great since I could not boot into the GUI before! This also told me that all previous flgrx drivers were definitely gone =)</p>
<p>After I rebooted I started envyng.</p>
<pre>envyng -t</pre>
<p>This takes us to the text based version of the installer. If you do not have envyng, I highly recommend it, download it via;</p>
<pre>sudo apt-get install envyng-core</pre>
<p>After you go through the text based wizard, it will ask you to reboot. Do that. You should come back to your login with your native screen resolution. Envyng never failed me through about 6-7 manual package removals and re-installing again everytime.</p>
<p>You can check if your drivers are working and installed correctly by typing the following &#8220;fglrxinfo&#8221;, you should see something like this:</p>
<pre>display: :0.0  screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon HD 3400 Series
OpenGL version string: 2.1.8575</pre>
<p>Next we will update xorg.conf. This creates a new xorg.conf and backups your old.</p>
<pre>aticonfig --initial -f</pre>
<p>To update your xorg.cong, type;</p>
<pre>sudo vim /etc/X11/xorg.conf</pre>
<p>If you don&#8217;t have vim, you can use vi instead. This is my xorg.conf file after researching and looking at other Linux users xorg.conf files for my series card.</p>
<pre>Section "ServerLayout"

#  InputDevice   "Synaptics Touchpad"
	Identifier     "Default Layout"
	Screen      0  "aticonfig-Screen[0]-0" 0 0
	InputDevice    "Generic Keyboard"
	InputDevice    "Configured Mouse"
	Option	    "AIGLX" "on"
EndSection

Section "Files"
EndSection

Section "Module"

#	Disable	"dri2"
	Load  "glx"
	Load  "dri"
#Load  "synaptics"
EndSection

Section "InputDevice"
	Identifier  "Generic Keyboard"
	Driver      "kbd"
	Option	    "CoreKeyboard"
	Option	    "XkbRules" "xorg"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "InputDevice"

  # Option "CorePointer"
  # Option "Device" "/dev/input/mice"
  # Option "Protocol" "ImPS/2"
  # Option "ZAxisMapping" "4 5"
  # Option "Emulate3Buttons" "true"
	Identifier  "Configured Mouse"
	Driver      "mouse"
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]-0"
	Gamma        0.85
EndSection

Section "Device"
	Identifier  "Mobility Radeon HD 3400 Series"
	Driver      "fglrx"
	Option	    "DynamicClocks" "on"
	Option	    "mtrr" "on"
	Option	    "DesktopSetup" "Single"
	Option	    "ScreenOverlap" "0"
	Option	    "VideoOverlay" "on"
	Option	    "OpenGLOverlay" "off"
	Option	    "Stereo" "off"
	Option	    "StereoSyncEnable" "1"
	Option	    "FSAAEnable" "no"
	Option	    "FSAAScale" "1"
	Option	    "FSAADisableGamma" "no"
	Option	    "FSAACustomizeMSPos" "no"
	Option	    "UseFastTLS" "0"
	Option	    "BlockSignalsOnLock" "on"
	Option	    "XAANoOffscreenPixmaps"
	Option	    "AccelMethod" "XAA"
	BusID       "PCI:1:0:0"
EndSection

Section "Screen"
	Identifier "aticonfig-Screen[0]-0"
	Device     "Mobility Radeon HD 3400 Series"
	Monitor    "aticonfig-Monitor[0]-0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Section "DRI"

  #Group "Video"
	Mode         0666
EndSection

Section "Extensions"
	Option	    "RENDER" "Enable"
	Option	    "DAMAGE" "Enable"
	Option	    "Composite" "Enable"
EndSection
</pre>
<p>The trick in this file that got my direct rendering enabled was setting the name of my actual video card under Section &#8220;Device&#8221; and Section &#8220;Screen&#8221;. To get the name of your video card as linux sees it, type the following;</p>
<pre>lspci | grep VGA</pre>
<p>Once you have updated your xorg.conf file, these settings are NOT actually set at this point. Even after a reboot! You must now type following to enable these settings.</p>
<pre>sudo aticonfig --input=/etc/X11/xorg.conf</pre>
<p>You should see a message that it was updated. Now reboot again and type the following to see if your direct rendering is enabled.</p>
<pre>glxinfo | grep direct</pre>
<p>You should get &#8220;direct rendering: Yes&#8221;</p>
]]></description>
			<content:encoded><![CDATA[<p>To start off I am no expert. I am a windows convert about a week ago now. However, I&#8217;m grabbing Linux by the horns and loving it!</p>
<p>The reason I am posting this is because it took me several hours to figure this out. I could not find in one place an organized concise approach. I&#8217;d imagine the experts already know this info but for the new Linux users, I can see this being helpful and also as a reference for me in the future <img src='http://k3mist.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>This does not fix the current <a href="https://bugs.launchpad.net/ubuntu/+bug/353800/" target="_blank">memory leak in Xorg</a> or the <a href="https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/351186" target="_blank">slow sluggishness of compiz when minimizing, maximizing or resizing</a>. Sadly, I&#8217;m experiencing both of these issues on Jaunty with the ATI Driver, I have not tried the open source ATI Driver yet.</p>
<p>I went through many installations and removals of the ati driver during this process. I will only explain how and what I did to actually get the driver working with direct rendering enabled.</p>
<p><span id="more-50"></span><strong>Let&#8217;s begin:</strong></p>
<p>You can see if you have direct rendering working by typing:</p>
<pre>glxinfo | grep direct</pre>
<p>If you get &#8220;direct rendering: Yes&#8221; you do not need to do this and your drivers and card are configured correctly. Otherwise, if it says no and possibly one of two messages after the &#8220;no&#8221;. Your xorg and driver settings are not configured correctly.</p>
<p>After a complete failure of the drivers off ATI&#8217;s website not working, even after compiling the .deb packages and installing everything that was necessary, my Linux installation no longer booted in the GUI.</p>
<p>The first thing I did was boot into recovery and remove ALL FGLRX packages from my installation. If you get permission denied for any commands, use sudo. You can see what packages are installed by typing this:</p>
<pre>dpkg -l | grep fglrx</pre>
<p>If any of the following packages are installed they will need removed:<br />
<strong>xorg-driver-fglrx, fglrx-kernel-source, fglrx-modaliases, fglrx-amdcccle</strong></p>
<p>You can remove these with the following command, leave out any packages that are not installed;</p>
<pre>apt-get purge xorg-driver-fglrx fglrx-kernel-source fglrx-modaliases fglrx-amdcccle</pre>
<p>Purge ensures that all files and directories created by the packages are removed. After successful purge I typed reboot. I was back in the GUI now in an 800&#215;600 screen, which was great since I could not boot into the GUI before! This also told me that all previous flgrx drivers were definitely gone =)</p>
<p>After I rebooted I started envyng.</p>
<pre>envyng -t</pre>
<p>This takes us to the text based version of the installer. If you do not have envyng, I highly recommend it, download it via;</p>
<pre>sudo apt-get install envyng-core</pre>
<p>After you go through the text based wizard, it will ask you to reboot. Do that. You should come back to your login with your native screen resolution. Envyng never failed me through about 6-7 manual package removals and re-installing again everytime.</p>
<p>You can check if your drivers are working and installed correctly by typing the following &#8220;fglrxinfo&#8221;, you should see something like this:</p>
<pre>display: :0.0  screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Mobility Radeon HD 3400 Series
OpenGL version string: 2.1.8575</pre>
<p>Next we will update xorg.conf. This creates a new xorg.conf and backups your old.</p>
<pre>aticonfig --initial -f</pre>
<p>To update your xorg.cong, type;</p>
<pre>sudo vim /etc/X11/xorg.conf</pre>
<p>If you don&#8217;t have vim, you can use vi instead. This is my xorg.conf file after researching and looking at other Linux users xorg.conf files for my series card.</p>
<pre>Section "ServerLayout"

#  InputDevice   "Synaptics Touchpad"
	Identifier     "Default Layout"
	Screen      0  "aticonfig-Screen[0]-0" 0 0
	InputDevice    "Generic Keyboard"
	InputDevice    "Configured Mouse"
	Option	    "AIGLX" "on"
EndSection

Section "Files"
EndSection

Section "Module"

#	Disable	"dri2"
	Load  "glx"
	Load  "dri"
#Load  "synaptics"
EndSection

Section "InputDevice"
	Identifier  "Generic Keyboard"
	Driver      "kbd"
	Option	    "CoreKeyboard"
	Option	    "XkbRules" "xorg"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "InputDevice"

  # Option "CorePointer"
  # Option "Device" "/dev/input/mice"
  # Option "Protocol" "ImPS/2"
  # Option "ZAxisMapping" "4 5"
  # Option "Emulate3Buttons" "true"
	Identifier  "Configured Mouse"
	Driver      "mouse"
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]-0"
	Gamma        0.85
EndSection

Section "Device"
	Identifier  "Mobility Radeon HD 3400 Series"
	Driver      "fglrx"
	Option	    "DynamicClocks" "on"
	Option	    "mtrr" "on"
	Option	    "DesktopSetup" "Single"
	Option	    "ScreenOverlap" "0"
	Option	    "VideoOverlay" "on"
	Option	    "OpenGLOverlay" "off"
	Option	    "Stereo" "off"
	Option	    "StereoSyncEnable" "1"
	Option	    "FSAAEnable" "no"
	Option	    "FSAAScale" "1"
	Option	    "FSAADisableGamma" "no"
	Option	    "FSAACustomizeMSPos" "no"
	Option	    "UseFastTLS" "0"
	Option	    "BlockSignalsOnLock" "on"
	Option	    "XAANoOffscreenPixmaps"
	Option	    "AccelMethod" "XAA"
	BusID       "PCI:1:0:0"
EndSection

Section "Screen"
	Identifier "aticonfig-Screen[0]-0"
	Device     "Mobility Radeon HD 3400 Series"
	Monitor    "aticonfig-Monitor[0]-0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Section "DRI"

  #Group "Video"
	Mode         0666
EndSection

Section "Extensions"
	Option	    "RENDER" "Enable"
	Option	    "DAMAGE" "Enable"
	Option	    "Composite" "Enable"
EndSection
</pre>
<p>The trick in this file that got my direct rendering enabled was setting the name of my actual video card under Section &#8220;Device&#8221; and Section &#8220;Screen&#8221;. To get the name of your video card as linux sees it, type the following;</p>
<pre>lspci | grep VGA</pre>
<p>Once you have updated your xorg.conf file, these settings are NOT actually set at this point. Even after a reboot! You must now type following to enable these settings.</p>
<pre>sudo aticonfig --input=/etc/X11/xorg.conf</pre>
<p>You should see a message that it was updated. Now reboot again and type the following to see if your direct rendering is enabled.</p>
<pre>glxinfo | grep direct</pre>
<p>You should get &#8220;direct rendering: Yes&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://k3mist.com/linux/ubuntu-jaunty-ati-restricted-proprietary-fglrx-driver-direct-rendering-mobility-radeon-hd-series/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
