<?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>Jeremy Visser &#187; xorg</title>
	<atom:link href="http://jeremy.visser.name/tag/xorg/feed/" rel="self" type="application/rss+xml" />
	<link>https://jeremy.visser.name</link>
	<description></description>
	<lastBuildDate>Fri, 16 Jul 2010 03:39:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<atom:link rel='hub' href='https://jeremy.visser.name/?pushpress=hub'/>
<cloud domain='jeremy.visser.name' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
		<item>
		<title>No DRI on X.Org with a Radeon? Check your Virtual size.</title>
		<link>https://jeremy.visser.name/2009/10/28/no-dri-on-x-org-with-a-radeon-check-your-virtual-size/</link>
		<comments>https://jeremy.visser.name/2009/10/28/no-dri-on-x-org-with-a-radeon-check-your-virtual-size/#comments</comments>
		<pubDate>Wed, 28 Oct 2009 03:52:25 +0000</pubDate>
		<dc:creator>Jeremy</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[ati]]></category>
		<category><![CDATA[emac]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[hacks]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[xorg]]></category>

		<guid isPermaLink="false">http://jeremy.visser.name/?p=1303</guid>
		<description><![CDATA[After I installed Fedora Rawhide on the eMac this week, I fired up X.Org, only to discover that&#8230; (II) AIGLX: Screen 0 is not DRI2 capable (II) AIGLX: Screen 0 is not DRI capable So it had fallen back to a software 3D renderer, which is pretty crap. So to make a long story short, [...]]]></description>
			<content:encoded><![CDATA[<p>After I installed Fedora Rawhide on the eMac this week, I fired up X.Org, only to discover that&#8230;</p>
<blockquote><pre>(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable</pre>
</blockquote>
<p>So it had fallen back to a software 3D renderer, which is pretty crap. So to make a long story short, it was because my &#8216;Virtual&#8217; screen size was too big. I typed <code>xrandr</code>, and got the following:</p>
<blockquote><pre>$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 960, <strong>maximum 2048 x 2048</strong></pre>
</blockquote>
<p>Because of various technical reasons, when the Virtual size is too big (which, evidently, 2048&#215;2048 is), DRI gets disabled. So, to re-enable it, I put this into my xorg.conf:</p>
<blockquote><pre>Section "Screen"
        Identifier "Main Screen"
        Device "Radeon 7500"
        Monitor "eMac CRT"
        SubSection "Display"
                <strong>Virtual 1280 960</strong> # put the highest resolution you intend to use here
        EndSubSection
EndSection</pre>
</blockquote>
<p>Obviously, edit the values to suit.</p>
]]></content:encoded>
			<wfw:commentRss>https://jeremy.visser.name/2009/10/28/no-dri-on-x-org-with-a-radeon-check-your-virtual-size/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Multiseat tips</title>
		<link>https://jeremy.visser.name/2009/08/03/multiseat-tips/</link>
		<comments>https://jeremy.visser.name/2009/08/03/multiseat-tips/#comments</comments>
		<pubDate>Mon, 03 Aug 2009 13:09:08 +0000</pubDate>
		<dc:creator>Jeremy</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[hacks]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[xorg]]></category>

		<guid isPermaLink="false">http://jeremy.visser.name/?p=1145</guid>
		<description><![CDATA[Recently, I&#8217;ve set up multiseat on my system, which means that, unlike multihead, where the desktop is expanded to two monitors, two sets of monitors, keyboards, and mice are attached to the computer, but run separate desktop sessions, meaning the computer is acting like two separate computers. The setup is very neat, and performance is [...]]]></description>
			<content:encoded><![CDATA[<p>Recently, I&#8217;ve set up multiseat on my system, which means that, unlike multihead, where the desktop is expanded to two monitors, two sets of monitors, keyboards, and mice are attached to the computer, but run separate desktop sessions, meaning the computer is acting like two separate computers.</p>
<p>The setup is very neat, and performance is surprisingly good. For all but the most graphically and processor-intensive applications, the fact two people are logged on to the machine is not even noticeable, from a performance point of view.</p>
<p>Some helpful guides on setting such a system up are:</p>
<ul>
<li><a href="http://linuxgazette.net/124/smith.html">Build a Six-headed, Six-user Linux System</a></li>
<li><a href="https://help.ubuntu.com/community/MultiseatX">MultiseatX &#8212; Community Ubuntu Documentation</a></li>
<li><a href="http://blog.chris.tylers.info/index.php?/archives/14-Multiseat-X-Under-X11R6.97.0.html">Multiseat X Under X11R6.9/7.0</a></li>
</ul>
<p>However, there are a few gotchas when setting it up. Hopefully this list will be of help.</p>
<ul>
<li>Multiseat is very buggy. Test one X server at a time (by manually launching it with the right parameters), and do it from a remote computer over an SSH session, because your display will probably get corrupted, making your console temporarily unusable if you make even the slightest mistake.</li>
<li>If the display is corrupted, and you are restarting X several times, and it doesn&#8217;t look like it&#8217;s going to work, it&#8217;s probably a good idea to reboot (do it safely, by either remotely rebooting, hitting Ctrl+Alt+Delete, or by using the <a href="http://www.brunolinux.com/01-First_Things_To_Know/Skinny_Elephants.html">Raising Skinny Elephants</a> trick), because there&#8217;s a good chance your problems will be solved after a reboot.</li>
<li>If you are using NVIDIA cards with the <code>nv</code> or <code>nouveau</code> driver, while I commend you for supporting free software, I have never got those drivers working with multiseat. I recommend running the proprietary driver (and different driver versions have different glitches with multiseat &#8212; if you are having problems, try an older &#8212; or newer &#8212; driver).</li>
<li>Don&#8217;t mix-and-match video cards of different brands. A 3Dfx and NVIDIA card won&#8217;t play nicely, for example, but an NVIDIA and NVIDIA card may. Also, there are weird bugs with certain models. For example, my GeForce 7600GT and GeForce 6200 don&#8217;t work well together, but the GeForce Go 6150 and GeForce 6200 work fine.</li>
<li>If you are using an ATI Radeon, then use the Xephyr method. Radeons cannot support the use of the Screen keyword in separate layouts.</li>
<li>If you are getting issues with the screen scrolling or rotating of sorts (like a sideways badly tuned old-style television), then try adding <code>no-scroll</code> to your kernel boot parameters.</li>
<li>When launching X.Org (or in your <code>gdm.conf</code> configuration), the <code>-novtswitch</code> and <code>-sharevts</code> options that are described in all multiseat tutorials can sometimes cause more harm than good, and may even be unnecessary. For example, if you use <code>-sharevts</code>, your keystrokes may silently be duplicated to a hidden login prompt which could wreak havoc on your system.</li>
<li>In the <code>[daemon]</code> section of <code>gdm.conf</code>, set <code>VTAllocation=false</code> to stop GDM from appending its own arguments to the X.Org command line. Specify <code>vt7</code> (or whatever VT you want X.Org to run on) manually on the X command line &#8212; and make sure both X servers are set to the same VT.</li>
<li>Add <code>Option "GrabDevice" "yes"</code> to your input devices in <code>xorg.conf</code> to <a href="https://launchpad.net/bugs/153425">fix a bug</a> where the display scrolls randomly or when you press enter.</li>
<li>Sound is a pain to get working. Make sure PulseAudio is either running system-wide, or make PulseAudio use dmix:0 instead of hw:0 as a device (yes, I know Lennart would cringe, but at least it&#8217;s more reliable). If you created a second user to test with, don&#8217;t forget to add him/her to the <code>audio</code> group!</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>https://jeremy.visser.name/2009/08/03/multiseat-tips/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Does this web page crash X for you?</title>
		<link>https://jeremy.visser.name/2009/01/11/does-this-web-page-crash-x-for-you/</link>
		<comments>https://jeremy.visser.name/2009/01/11/does-this-web-page-crash-x-for-you/#comments</comments>
		<pubDate>Sun, 11 Jan 2009 12:49:17 +0000</pubDate>
		<dc:creator>Jeremy</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[aargh]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[NVIDIA]]></category>
		<category><![CDATA[xorg]]></category>

		<guid isPermaLink="false">http://jeremy.visser.name/?p=941</guid>
		<description><![CDATA[I would like to ask a quick favour of my loyal readership (insert cricket chirping sound effect here). Whenever, I load this page in Firefox 3.0.4, which is a perfectly innocuous page on the OSx86 wiki, my X server crashes, just as if I hit Ctrl+Alt+Backspace. I have an NVIDIA GeForce 7600GT, running on Linux [...]]]></description>
			<content:encoded><![CDATA[<p>I would like to ask a quick favour of my loyal readership <em>(insert cricket chirping sound effect here)</em>.</p>
<p>Whenever, I load <a href="http://wiki.osx86project.org/wiki/index.php/HCL_10.5.2">this page</a> in Firefox 3.0.4, which is a perfectly innocuous page on the OSx86 wiki, <strong>my X server crashes</strong>, just as if I hit Ctrl+Alt+Backspace.</p>
<p>I have an NVIDIA GeForce 7600GT, running on Linux 2.6.27-gentoo, with both the open source <code>nv</code> driver, as well as the proprietary driver version 177.82 (also occurs on 177.80).</p>
<p>Does it happen to anybody else? I strongly suspect a video driver bug, as it doesn&#8217;t occur on my Eee 901, which is GMA950&ndash;based.</p>
]]></content:encoded>
			<wfw:commentRss>https://jeremy.visser.name/2009/01/11/does-this-web-page-crash-x-for-you/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>
