Verifying - Revision history

Mooninite: Protected "Verifying": Excessive vandalism (‎[edit=autoconfirmed] (expires 05:19, 31 March 2013 (UTC)) ‎[move=autoconfirmed] (expires 05:19, 31 March 2013 (UTC)))

2013-03-17T05:19:45Z

Protected "Verifying": Excessive vandalism (‎[edit=autoconfirmed] (expires 05:19, 31 March 2013 (UTC)) ‎[move=autoconfirmed] (expires 05:19, 31 March 2013 (UTC)))

Mooninite at 05:19, 17 March 2013

2013-03-17T05:19:30Z

217.167.129.14: /* fgl_glxgears */

2013-03-16T22:19:35Z

‎fgl_glxgears

46.137.18.7: /* fglrxinfo */

2013-03-16T22:19:33Z

‎fglrxinfo

Mooninite: Protected "Verifying": Excessive vandalism ([edit=autoconfirmed] (expires 00:03, 2 October 2012 (UTC)) [move=autoconfirmed] (expires 00:03, 2 October 2012 (UTC)))

2012-09-02T00:03:44Z

Protected "Verifying": Excessive vandalism ([edit=autoconfirmed] (expires 00:03, 2 October 2012 (UTC)) [move=autoconfirmed] (expires 00:03, 2 October 2012 (UTC)))

Mooninite: Reverted edits by 203.175.70.3 (talk) to last revision by Mooninite

2012-09-02T00:03:28Z

Reverted edits by 203.175.70.3 (talk) to last revision by Mooninite

203.175.70.3: /* glxinfo */

2012-09-01T22:59:01Z

‎glxinfo

Mooninite: Protected "Verifying": Excessive vandalism ([edit=autoconfirmed] (expires 22:35, 15 November 2011 (UTC)) [move=autoconfirmed] (expires 22:35, 15 November 2011 (UTC)))

2011-11-08T22:35:00Z

Protected "Verifying": Excessive vandalism ([edit=autoconfirmed] (expires 22:35, 15 November 2011 (UTC)) [move=autoconfirmed] (expires 22:35, 15 November 2011 (UTC)))

Mooninite: Reverted edits by 109.230.216.60 (talk) to last revision by Mooninite

2011-11-08T22:34:51Z

Reverted edits by 109.230.216.60 (talk) to last revision by Mooninite

109.230.216.60: /* Xorg.0.log */

2011-11-08T22:03:19Z

‎Xorg.0.log

@@ Line 3: / Line 3: @@
 ==Verify with ATI tools==
 If the installation has worked, then any 3D application should work without issue.  A simple way to verify without any possibility of failure is to verify the following occurs.  Please note that you may have needed to go through [[:Category:Distributions|distribution specific]] process to enable the 3D support.
-> I don’t know if it’s me, but on the wall display with 9 dlsipays, it seems the parallel renderer is struggling…It's actually not the renderer, but the image capture tool which is struggling to record almost full-screen. With larger models this configuration does indeed struggle, which is not surprising considering you have 9 GL context and 4 processes on a single GPU .I am using Capture Me on Mac OS X   anybody knows a better tool?
+===fglrxinfo===
-I feel so much happier now I udnesrtand all this. Thanks!
+If the vendor string is "Mesa", the driver wouldn't configure properly the /etc/X11/xorg.conf .Please see the [[Troubleshooting|Troubleshooting]] page.
 ===Links===

@@ Line 5: / Line 5: @@
 > I don’t know if it’s me, but on the wall display with 9 dlsipays, it seems the parallel renderer is struggling…It's actually not the renderer, but the image capture tool which is struggling to record almost full-screen. With larger models this configuration does indeed struggle, which is not surprising considering you have 9 GL context and 4 processes on a single GPU .I am using Capture Me on Mac OS X   anybody knows a better tool?
-===fgl_glxgears===
+I feel so much happier now I udnesrtand all this. Thanks!
-You can also run the ATI provided application called fgl_glxgears which should show a spinning cube with the venerable glxgears running on each face.
-−
-<b>If you run fgl_glxgears and the cube spins but is lacking any cogs on the faces, the faces being instead various shades of blue and/or you get an error message like:</b>
-−
-<pre>
-Using GLX_SGIX_pbuffer
-frames in 5.0 seconds = 182.600 FPS
-frames in 5.0 seconds = 156.600 FPS
-X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
-  Major opcode of failed request:  14 (X_GetGeometry)
-  Resource id in failed request:  0x0
-  Serial number of failed request:  51
-  Current serial number in output stream:  51
-</pre>
-−
-<b>Then your installation most presumably failed!</b>
 ===Links===

@@ Line 3: / Line 3: @@
 ==Verify with ATI tools==
 If the installation has worked, then any 3D application should work without issue.  A simple way to verify without any possibility of failure is to verify the following occurs.  Please note that you may have needed to go through [[:Category:Distributions|distribution specific]] process to enable the 3D support.
-===fglrxinfo===
+> I don’t know if it’s me, but on the wall display with 9 dlsipays, it seems the parallel renderer is struggling…It's actually not the renderer, but the image capture tool which is struggling to record almost full-screen. With larger models this configuration does indeed struggle, which is not surprising considering you have 9 GL context and 4 processes on a single GPU .I am using Capture Me on Mac OS X   anybody knows a better tool?
-<pre>
-$ fglrxinfo
-display: :0.0  screen: 0
-OpenGL vendor string: ATI Technologies Inc.
-OpenGL renderer string: Radeon X1600 Series
-OpenGL version string: 2.1.7415 Release
-</pre>
-−
-If the vendor string is "Mesa", the driver wouldn't configure properly the /etc/X11/xorg.conf .Please see the [[Troubleshooting|Troubleshooting]] page.
 ===fgl_glxgears===

@@ Line 36: / Line 36: @@
 http://m.domaindlx.com/LinuxHelp/ati/ati.htm (mirror)
 ==Verify with Linux tools==
-We need more insights like this in this therad.
+===glxinfo===
 ===Xorg.0.log===

@@ Line 36: / Line 36: @@
 http://m.domaindlx.com/LinuxHelp/ati/ati.htm (mirror)
 ==Verify with Linux tools==
-===glxinfo===
+We need more insights like this in this therad.
-This command line option should report "direct" rendering.
- $ glxinfo | grep direct
-−
-(For Debian 4.0, install the mesa-utils package to get glxinfo.)
 ===Xorg.0.log===

← Older revision		Revision as of 22:34, 8 November 2011
Line 42:		Line 42:
	(For Debian 4.0, install the mesa-utils package to get glxinfo.)		(For Debian 4.0, install the mesa-utils package to get glxinfo.)

−	~~That's 2 celver by half~~ and ~~2x2 clever 4 me~~. ~~Thanks!~~	+	===Xorg.0.log===
		+	The X.org X server log file also contains useful information to verify installation was successful. It is located on most Linux distributions at <code>/var/log/Xorg.0.log</code> and can be opened by any text editor.
		+
		+
		+	'''You can now move on to [[Configuring\|configuring the driver]].'''
		+
		+	{{VCT}}
		+	[[Category:NeedsUpdating]]

@@ Line 42: / Line 42: @@
 (For Debian 4.0, install the mesa-utils package to get glxinfo.)
-===Xorg.0.log===
+That's 2 celver by half and 2x2 clever 4 me. Thanks!
-The X.org X server log file also contains useful information to verify installation was successful. It is located on most Linux distributions at <code>/var/log/Xorg.0.log</code> and can be opened by any text editor.
-−
-−
-'''You can now move on to [[Configuring|configuring the driver]].'''
-−
-{{VCT}}
-[[Category:NeedsUpdating]]